semi合集-English.pdf - 第2764页
SEMI E98-1102 © SEMI 2000, 2002 29 10.5.6 AbstractEquipmentM odule Attribut es 10.5.6.1 The AbstractE quipmentModule Ob ject is show n in Figure 19. Mod el ModelRevision Nickname BehaviorState Previous BehaviorStat e Pro…

SEMI E98-1102 © SEMI 2000, 2002 28
State Name Superstate Definition
ACTIVE IN SERVICE The AbstractEquipmentModule is performing activities that change its physical state.
ACTIVE SERVICE ACTIVE While assigned to manufacturing, the AbstractEquipmentModule may only perform
its normal process.
PAUSE ACTIVE The AbstractEquipmentModule has received instructions to pause its activity.
PAUSING PAUSE The AbstractEquipmentModule is in the process of putting itself into a safe state.
PAUSED PAUSE The AbstractEquipmentModule is in a safe state.
STOPPING ACTIVE The AbstractEquipmentModule has begun the stop operation.
ABORTING ACTIVE The AbstractEquipmentModule has started the abort operation.
INACTIVE IN SERVICE The AbstractEquipmentModule has completed its stop or abort operation.
IDLE WITH ALARMS INACTIVE The AbstractEquipmentModule is idle but has a fault condition.
STOPPED INACTIVE The AbstractEquipmentModule has completed the stop operation.
ABORTED INACTIVE The AbstractEquipmentModule has completed the abort operation.
10.5.5.5 AbstractEquipment Module State Transition Table — Table 12 defines the state transitions for the
AbstractEquipmentModule Operations state model.
Table 12 AbstractEquipmentModule Behavior State Transitions
# Previous State Trigger New State Action(s) Comment
11 Any State model is initialized. depends on previous
state and current
condition
None See Section 9.5.2.2.
12 IDLE An activity changing the physical
state of the module is started.
ACTIVE SERVICE None Substates of ACTIVE
SERVICE are module
dependent.
13 ACTIVE
SERVICE
All activities changing the physical
state are completed without fault.
IDLE None IDLE is fault-free.
14 ACTIVE
SERVICE
The module received instructions to
pause its activity.
PAUSING None The module is responsible for
reaching a safe state.
15 PAUSING All activity is paused. PAUSED None
16 PAUSED The module has received instructions
to resume its activity.
ACTIVE SERVICE None
17 PAUSED The module has received instructions
to stop its activity.
STOPPING None The module is responsible for
reaching a safe state.
18 PAUSED The module has received instructions
to abort its activity.
ABORTING None
19 ACTIVE
SERVICE
The module has received instructions
to stop its activity.
STOPPING None
20 STOPPING The Stop operation has completed
and all material started has been
returned to its proper destination.
STOPPED None
21 ACTIVE
SERVICE
The module has received instructions
to abort its activity.
ABORTING None The module is responsible for
reaching a safe state.
22 ABORTING Completion of aborting activity. ABORTED None
23 Any Default entry into INACTIVE IDLE WITH ALARMS None One or more exceptions
detected during initialization.
24 INACTIVE The module received instructions to
return to IDLE.
IDLE None IDLE is fault-free.
25 INACTIVE The module returns to IDLE
automatically.
IDLE None IDLE is fault-free.

SEMI E98-1102 © SEMI 2000, 2002 29
10.5.6 AbstractEquipmentModule Attributes
10.5.6.1 The AbstractEquipmentModule Object is shown in Figure 19.
Model
ModelRevision
Nickname
BehaviorState
PreviousBehaviorState
ProcessSetup
ProcessType
ProcessCapabilitiesList
SoftwareVersions
AbstractEquipment
Module
Abort
AddProcessCapability
Pause
RemoveProcessCapability
Resume
Shutdown
Start
Startup
Stop
Figure 19
AbstractEquipmentModule Object Type
10.5.6.2 Attributes of the AbstractEquipmentModule are defined in Table 13.
Table 13 AbstractEquipmentModule Attribute Definition
Attribute Name Definition Access Reqd Form
ObjType Object type RO Y Text=“AbstractEquipmentModule”
ObjID Object identifier RO Y Text
Nickname User-assigned name RW Y Text
Model Model designator RO Y Text
ModelRevision Model Revision RO Y Text
BehaviorState Current substate of BEHAVIOR RO Y Enumerated
ProcessType Characterization of processes for user RW Y Text
ProcessCapabilityList One or more specific process capabilities RO Y List of text
PreviousBehaviorState The previous operations state RO Y Enumerated
ProcessSetup Name of current setup. RW Y Text
SoftwareVersions The set of software versions installed RO Y Ordered list of text
Units Type of material held RO Y Text
NOTE 1: Required if the AbstractEquipmentModule provides recipe execution services.
10.5.7 AbstractEquipmentModule Services — The AbstractEquipmentModule has one or more automated activities,
including its normal process (its intended function). The user shall be able to start, stop, abort, and resume the
activities of the module.
NOTE 4: Changing the operational state of an individual AbstractEquipmentModule within a multi-process Equipment during
automatic processing will affect both upstream and downstream operations. The Equipment is responsible for determining the
impact on other AbstractEquipmentModules.
NOTE 5: Directly changing the operational state of the AbstractEquipmentModule is not the same as changing the state of a job
or as changing the operational state of the Equipment. The equipment supplier shall document the relationships between the
operational state of the Equipment, the AbstractEquipmentModule, and the different job types that it supports.

SEMI E98-1102 © SEMI 2000, 2002 30
10.5.7.1 Abort
10.5.7.1.1 On receipt of an Abort request from the
user, the module shall stop all of its current activity as
soon as it is safe to do so. It should remove any
material in process within the module whenever
possible to do so safely.
10.5.7.1.2 A module may also self-abort when it
detects a dangerous condition.
10.5.7.1.3 In the Behavior State Model, the module
shall transition from ACTIVE SERVICE to
ABORTING when an abort occurs. When all activity
has ceased other than normal background activities for
environmental control, the module transitions to
ABORTED. The module shall not start a new activity
until it is instructed to do so by the user or the user
instructs it to return to IDLE.
10.5.7.2 Add Process Capability — ProcessCapabil-
ityList is an attribute of the equipment module and con-
sists of a list of text strings representing process capa-
bilities that are meaningful to the user. Individual capa-
bilities are added by the factory to recognize the type of
processes the equipment module may be able to run.
10.5.7.3 Pause
10.5.7.3.1 On receipt of a Pause request from the user,
the module shall suspend its activity at the next logical
point in the process from which it will be able to
resume activities at a later time and which will prevent
unintended change to the product. It shall not accept
new work while it is in this state.
10.5.7.3.2 In many cases, to avoid unintended change
to the product, the AbstractEquipmentModule should
wait until the current product has been removed and
then pause, preventing new product from entering.
10.5.7.4 Remove Process Capability — This allows the
factory to remove from the ProcessCapabilityList a
capability that is no longer required or one that can not
be performed by the equipment due to environment or
actual physical changes in the equipment.
10.5.7.5 Resume — When a Resume request is received
during a PAUSE state, the module shall resume its
activity from the point where it was paused.
10.5.7.6 Shutdown — The Shutdown request is used to
put an AbstractEquipmentModule in a state where it is
safe to turn off its power and remove it from the
equipment. The specific operations shall be
documented by the supplier.
10.5.7.7 Start
10.5.7.7.1 Some activities may require specific Start
instructions.
10.5.7.7.2 The user may issue a Start Activity request
to a specific AbstractEquipmentModule.
10.5.7.8 Startup — The Startup request is used when
an AbstractEquipmentModule has been shutdown. The
specific activities that result shall be documented by the
supplier.
10.5.7.9 Stop
10.5.7.9.1 On receipt of a Stop request from the user,
the module shall stop its current activity in an orderly
fashion as soon as it is safe to do so, with all product
material returned as would be expected had the activity
completed normally.
10.5.7.9.2 In the Behavior State Model, the module
shall transition from ACTIVE SERVICE to STOPPING
when a stop operation begins. When all activity has
ceased other than normal background activities for
environmental control, the module transitions to
STOPPED. The module shall not start a new activity
until it is instructed to do so by the user.
10.5.8 EquipmentModule Object — The Equipment-
Module is a type of AbstractEquipmentModule and
inherits all of its attributes, state models, relations, and
services. As shown in Figure 20, the Equipment-
Module may be an aggregate of EquipmentIODevice,
EquipmentSubsystem, and other EquipmentModule
objects.
Equipment
Module
M
PN
M + N + P >= 1
Equipment
I/ODevice
Equipment
Subsystem
Figure 20
EquipmentModule Aggregation
10.6 Equipment Object
10.6.1 The Equipment is a type of AbstractEquipment-
Module and supports all of the attributes, state models,
and services defined for the AbstractEquipmentModule.
10.6.2 Equipment is an aggregation of Equipment-
Modules, EquipmentSubsystems, and EquipmentIO-
Devices objects and owns all the objects of which it is