semi合集-English.pdf - 第7728页

SEMI T12-0305 © SEMI 2004, 2005 7 9.3 Exception — Exception is unusual state on any Jig and/or Implement or on the tracking capability includ ing hazardous situation: potential or alread y destroy materials, attachments,…

100%1 / 7923
SEMI T12-0305 © SEMI 2004, 2005 6
9.1.2.5 Further Application Interface — Final purposes of tracking such attachments as Jigs and Implements are
controlling life time of attachments, increasing effectiveness of attachments, preventing falt process and achieve
good quality of products. In this regard this interface capability helps applications. Green light shadowed class
(HistoryDB) corresponds this capability. This capability may be installed on the host or application server.
9.1.3 Collaboration in Class Modeling — An example of collaboration is as follows.
9.1.3.1 Application seeks certain type of jigs through HistoryDB. It finds good ones to produce expensive products.
It asks Inventory where they are.
9.1.3.2 It picks up the ones and delivers them to target equipments. It updates Inventory and Inventory sends
invoices to JitMachines. Invoice object is created on each JitMachine. At the time each jig arrives at each piece of
target equipment, the Invoice verifies. If verification succeeds, this fact is notified to Inventory, location is updated,
Secondment is created and JitMachine identifies what the sent jigs are. At the same time HistoryBuffer is also
created by the Secondment.
9.1.3.3 Equipment runs. HistoryBuffer accumulates events, process conditions and cycle. At some moment, it
reports the buffer content to Inventory. The Inventory manages HistoryRecord.
9.2 Attachment — Attachment represents a Jig or an Implement. This concept is used to handle common nature of
the both items.
9.2.1 Attachment object — Attachment object represents such supporting resource as Jig or Implement logically.
Attachment object is an instance of Attachment class defined later. Attachment object identifies corresponding
physical attachment and its information. This object is abbreviated as “Attachment” in this document and often
‘object’ is omitted.
Attachment
showId
showName
changeName
showType
showHistory
updateHistory
showLocation
updateLocation
Figure 2
Attachment Class
9.2.2 Attachment Class — Attachment Class defines its inherent data, behavior and services. This class generalizes
Jig and Implement registered in an Inventory. This class is illustrated as above for reference.
9.2.2.1 Responsibility of Attachment — This class is responsible for holding and organizing such information as
history for a Jig or Implement belonging to an Inventory.
9.2.2.1.1 To complete the responsibility it accepts creation/removal of a HistoryRecord, adding events or increment
time/duration requests and inquiry. They are defined as services of Attachment in this specification. Service names
may be different from capabilities above.
9.2.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.2.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. However it has to be defined
if this class has explicit state, state model is not defined here because this class is stateless.
SEMI T12-0305 © SEMI 2004, 2005 7
9.3 Exception — Exception is unusual state on any Jig and/or Implement or on the tracking capability including
hazardous situation: potential or already destroy materials, attachments, equipment, explosive or insure/kill human.
Exception happens on equipment or may be storage capability of corresponding inventory. This fact may be added
to history.
9.3.1 Exception Object — Exception object represents unusual situation happened usually on equipment. It is
created at the time it is raised. It is destructed after normal condition is recovered from the situation. Exception
object is an instance of Exception class defined later. This object is abbreviated as “Exception” in this document
and often ‘object’ is omitted.
Exception
showId
showCategory
showCode
showDescription
showSubject
showState
updateState
destruct
Figure 3
Exception Class
9.3.2 Exception Class — Exception Class defines its inherent data, behavior and services. This class is illustrated
as above for reference.
9.3.2.1 Responsibility of Exception — This class is responsible for identifying situation, its status and such subject
as Jigs or Implements.
9.3.2.1.1 To complete the responsibility it accepts notification of state change or adding appendix for the state.
They are defined as services of Exception in this specification. Service names may be different from capabilities
above.
9.3.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.3.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.3.2.1.3.1 SET — Unusual situation is still effective.
9.3.2.1.3.2 CLEARED — Unusual situation is removed and it is normal condition about the cause of exception.
SET
CLEARED
EXCEPTION
1
2
3
Figure 4
Exception State
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.