semi合集-English.pdf - 第7730页

SEMI T12-0305 © SEMI 2004, 2005 9 VA L I D EXPIRED EXPIRY 1 2 3 Figure 6 Expiry State Table 2 Transition De finition Table of Expiry # Previous State Trigger Ne w State Actions Comments 1 (No state) Expiry object is crea…

100%1 / 7923
SEMI T12-0305 © SEMI 2004, 2005 8
Table 1 Transition Definition Table of Exception
# Previous State Trigger New State Actions Comments
1 (No state) Unusual situation happens. SET
2 SET Unusual Condition has been
removed.
CLEARED Exception information may be
added to history.
It’s not always
termination.
3 CLEARED Termination is instructed. (No state)
9.4 Expiry — Expiry represents a kind of nature of a Jig or Implement which has explicit valid duration: processed
time period, critical process time, cycle and so on. An Expiry is prepared for a specific duration to allow special
action on the Attachment when it has expired.
9.4.1 Expiry Object — Expiry object encapsulates a series of information about one of expiry conditions on an
Attachment. It is created at the time Secondment, a representation of an Attachment on equipment, is created or an
instruction to specify the expiry is accepted by the Secondment and destructed when the Secondment is removed
from equipment. It is also destructed to withdraw expiration after special action is invoked when it fires the
expiration. Expiry object is an instance of Expiry class defined later. This object is abbreviated as “Expiry” in this
document and often ‘object’ is omitted.
Expiry
showId
showExpiration
changeExpiration
showAction
changeAction
showDescription
changeDescription
showSubject
showState
destruct
Figure 5
Expiry Class
9.4.2 Expiry Class — Expiry Class defines its inherent data, behavior and services. This class is illustrated as
above for reference.
9.4.2.1 Responsibility of Expiry — This class is responsible for maintaining expiration of such subject as Jigs or
Implements.
9.4.2.1.1 To complete the responsibility it checks expiration subject of the Attachment. This is started at the time it
is created. Services to help the responsibility are defined in this specification. Service names may be different from
capabilities above.
9.4.2.1.2 Inherent data is used to complete the responsibility. The data is also referred to as attributes and they have
to be defined in some way. This document doesn’t define attributes directly with attribute definition table shown in
some SEMI standard documents but defines them indirectly as service parameters.
9.4.2.1.3 Behavior is also defined to complete the responsibility. Behavior is often represented by collaboration
with outside of this class and state model. Collaboration reflects a part of associations of this class with others.
Collaboration works by asking services defined on accompanying object which is the other end of association on
class diagram. State model is representation of the other part of behavior of this class. Because this class has
explicit state, it defines following states and state model by state chart and transition definition table.
9.4.2.1.3.1 VALID — Attachment is valid for a subject.
9.4.2.1.3.2 EXPIRED — Attachment is invalid because of expiration of specified duration.
SEMI T12-0305 © SEMI 2004, 2005 9
VALID
EXPIRED
EXPIRY
1
2
3
Figure 6
Expiry State
Table 2 Transition Definition Table of Expiry
# Previous State Trigger New State Actions Comments
1 (No state) Expiry object is created. VALID Watchdog is started.
2 VALID Subject has been expired. EXPIRED Registered special action is
carried out.
3 EXPIRED The action is started. (No state)
9.5 History — History is the concept to track what happens on Jigs and/or Implements and how they are used. A
few object classes are modeled to complete this capability.
9.6 HistoryBuffer — HistoryBuffer is tentative history information of a Jig or Implement on equipment. The
information is reported to Inventory periodically or at some milestones. When it is reported, the information is
cleared for new information.
9.6.1 HistoryBuffer Object — HistoryBuffer object represents buffer area of tentative history information of an
attachment on equipment. It is created at the time an attachment is created and destructed after the attachment is
removed. HistoryBuffer object is an instance of HistoryBuffer class defined later. This object is abbreviated as
“HistoryBuffer” in this document and often ‘object’ is omitted.
HistorBuffer
show
A
ttachment
showHistory
updateHistory
showReleaseCondition
setReleaseCondition
showState
destruct
Figure 7
HistoryBuffer Class
9.6.2 HistoryBuffer Class — HistoryBuffer Class defines its inherent data, behavior and services. This class is
illustrated as above for reference.
9.6.2.1 Responsibility of HistoryBuffer — This class is responsible for keeping temporary history information of Jig
or Implement on equipment and clear the information after it is reported to Inventory.
9.6.2.1.1 To complete the responsibility it accepts information what happens on an attachment or how it is used
including period or cycle. It also accepts inquiries. They are defined as services of HistoryBuffer in this
specification. Service names may be different from capabilities above.
9.6.2.1.2 Inherent data is used to complete the responsibility. The data is also referred to as attributes and they have
to be defined in some way. This document doesn’t define attributes directly with attribute definition table shown in
some SEMI standard documents but defines them indirectly as service parameters.
SEMI T12-0305 © SEMI 2004, 2005 10
9.6.2.1.3 Behavior is also defined to complete the responsibility. Behavior is often represented by collaboration
with outside of this class and state model. Collaboration reflects a part of associations of this class with others.
Collaboration works by asking services defined on accompanying object which is the other end of association on
class diagram. State model is representation of the other part of behavior of this class. Because this class has
explicit state, it defines following states and state model by state chart and transition definition table.
9.6.2.1.3.1 Empty — No history information is accumulated.
9.6.2.1.3.2 Buffered — Some history information are accumulated and they are not reported.
EMPTY BUFFERED
HISTORYBUFFER
1
2
4
3
Figure 8
HistoryBuffer State
Table 3 Transition Definition Table of HistoryBuffer State
# Previous State Trigger New State Actions Comments
1 (No state) A Secondment has been
created.
EMPTY
2 EMPTY History information is put. BUFFERED The information has to be
reported at some moment.
3 BUFFERED History information is
reported and buffer area is
cleared.
EMPTY The information has to be
reported before it is cleared.
4 EMPTY Corresponding Attachment
has been removed.
(No state)
9.7 History Data Base — HistoryDB is an interface of whole history information for application.
9.7.1 History Data Base object — History Data Base object keeps history data of all Jigs and Implements in a
Inventory. History Data Base object is an instance of History Data Base class defined later. There is just one
History Data Base object corresponding to a Inventory. This object is abbreviated as “HistoryDB” in this document
and often ‘object’ is omitted.
HistoryDB
update
reset
adopt
disown
listRecord
showHistor
y
Figure 9
HistoryDB Class
9.7.2 History Data Base Class — HistoryDB Class defines its inherent data, behavior and services. This class
manages history of all Jigs and Implements in an Inventory. This class is illustrated as above for reference.
9.7.2.1 Responsibility of HistoryDB — This class is responsible for managing and organizing history information
for all Jigs and/or Implements registered in an Inventory.