semi合集-English.pdf - 第2691页

SEMI E97-0200A © SEMI 2000 11 There is n o limit to the num ber of levels th at may be addressed th is way . Based on the impl e mentati ons of nameQualifiedTo (string); a n a me need not always be concatenated, if a par…

100%1 / 7923
SEMI E97-0200A © SEMI 2000 10
Description: Resource is an abstract inherited interface for any entity in the factory that takes an active
role in advancing a product along its manufacturing life cycle (adds value). This includes
the factory itself, personnel, production, planning and scheduling resources, and all of the
machines used for processing, transporting, and storing materials. Resource provides a
common set of services for monitoring and control. Resource uses the NamedEntity and
OwnedEntity characteristics together to allow for the building of resource hierarchies.
There must be a clear division between the state of the Resource and the condition of the
physical entity which the Resource represents. For instance, a Machine is a resource, but
the fact that it is “Out of Service” may not mean the physical equipment is shutdown on
the shop floor. In fact, the equipment may be operating in manual mode. The Resource
state represents the availability of the Resource object to accept work for the factory
system.
Exceptions: None.
Published Events: None.
Provided Services:
interface Resource : OwnedEntity {
/* Perform the startup activities for this Resource. Should be implemented by Resource specializations. */
void startUp ()
raises (Global::FrameworkErrorSignal);
/* Perform normal shutdown activities for this Resource. Normal is defined as allowing the Resource to complete
any current activities and “gracefully” shutdown. */
void shutdownNormal ()
raises (Global::FrameworkErrorSignal);
/* Perform immediate shutdown activities for this Resource. Immediate is defined as aborting or terminating any
current activities and stopping activity as soon as possible. This should be implemented by Resource specializations.
*/
void shutdownImmediate ()
raises (Global::FrameworkErrorSignal);
/* Respond with the receiver’s level in the Resource hierarchy. Resource specifies that each different type of
Resource provide a “resourceLevel” identifier.
string resourceLevel ()
raises (Global::FrameworkErrorSignal);
/* The following service provides name scoping for Resources. Resource name scoping makes use of the notion of
“Resource level” and the ownership hierarchy. For example, unique identification of MachineResources within a
Machine is possible, but to identify them outside the Machine additional information about their ownership will be
required.
Thus: nameQualifiedTo (“Machine”) sent to the ProcessResource named “Chamber” answers
“TestMachine>Chamber”.
If the Machine was owned by a Factory named “TestFactory”, then:
nameQualifiedTo (“Factory”) sent to the ProcessResource answers
“TestFactory>TestMachine>Chamber”
where the ProcessResource has now been uniquely identified for the given Factory.
SEMI E97-0200A © SEMI 200011
There is no limit to the number of levels that may be addressed this way. Based on the implementations of
nameQualifiedTo (string); a name need not always be concatenated, if a particular Resource level is not applicable
to identification. */
string nameQualifiedTo (in string resourceLevel)
raises (Global::FrameworkErrorSignal);
/* Returns the set of subordinate Resources for a given Resource. */
ResourceSequence subResources ()
raises (Global::FrameworkErrorSignal);
/* Answer if the resource is in service. In service means the resource is functional and ready to accept and perform
its normal tasks. Derivatives of Resource are expected to expand this state (e.g., add sub-interfaces) that explicitly
deal with such additional issues as capacity, “normal” work versus maintenance, etc. */
boolean isInService ();
/* Answer if the resource is out of service. Out of service means the resource is unable to accept or begin new tasks.
Previously begun tasks may continue in some cases. */
boolean isOutOfService ();
}; // Resource
Contracted Services: None.
Dynamic Model:
Implementations of Resource may extend the state model by providing additional sub-states that are wholly
contained within a state defined here. Extending the state model by the addition of state transitions is also an option
for subtypes of Resource.
IN SERVICE
OUT OF SERVICE
3 4
2
51
Figure 2
Resource Dynamic Model
SEMI E97-0200A © SEMI 2000 12
Table 1 Resource State Definitions and Query Table
State Definition Query for State via
IN SERVICE Resource is capable of interacting with other
resources with its full service interface.
boolean isInService ( ); sent to the instance of
Resource returns TRUE.
OUT OF SERVICE Resource is not able to provide services boolean isOutOfService ( ); sent to the instance of
Resource returns TRUE.
Table 2 Resource State Transitions
# Current State Trigger New State Action Comment
1 Non Existent Object creation. OUT OF
SERVICE
None. Default entry.
2 OUT OF
SERVICE
startUp ( ) or object
initialization.
IN SERVICE Initiate Resource and
subresources.
startUp() service initiates
the trigger.
3 IN SERVICE shutdownNormal ( ). OUT OF
SERVICE
Complete current
execution of resources
normally.
shutdownNormal() service
initiates the trigger.
4 IN SERVICE shutdownImmediate ( ).
Take resource out of
service.
OUT OF
SERVICE
Stop execution of
resource immediately.
shutdownImmediate()
service initiates the trigger.
5 OUT OF
SERVICE
Resource removed. Non Existent None.
6.5 Material Abstract Interface Gr oup
6.5.1 The CIM Framework uses a common architecture for identifying, grouping and locating materials. Any
material has an identification, history, location, and associations to any material containers that contain it. Material
can also be in multiple material groups that physically (same location or carrier) or logically (same lot, same process
batch, same product family, etc.) associate material. Specializations of material include products, durables and
consumables. Specializations of material groups include product groups, lots, and process groups.