semi合集-English.pdf - 第3104页

SEMI E125-0305 © SEMI 2003, 2005 12 9.1.2.12 No tificationRequest — This class describ es the notificatio n preferences of the metadata client. 9.1.2.12 .1 NotificationRequest Attribute Definition Table Table 18 Notifica…

100%1 / 7923
SEMI E125-0305 © SEMI 2003, 2005 11
9.1.2.10 NotifyOnRevisions — Upon receiving this request, the equipment shall either enable or disable metadata
revision notices to the requesting client, based on the operation arguments provided by the client. The equipment
shall store the client’s preference in non-volatile memory.
9.1.2.10.1 NotifyOnRevisions Operation Arguments
Table 16 NotifyOnRevisions Argument Definitions
Argument Description Kind Form
notification Specifies the client’s notification
preference.
in Structured data of type NotificationRequest,
described in Section 9.1.2.12 .
9.1.2.10.2 Clients must invoke this operation with the ‘enable’ attribute of the notification argument set to ‘true’ in
order to receive notifications. The default behavior for revision notifications for a given client is disabled. The
equipment shall automatically disable notification for a client if the equipment is in an enabled communications
state and determines that the client is no longer accessible to receive such notifications. In this case, the client must
invoke this operation in order to re-enable notifications.
9.1.2.10.3 If the ‘enable’ attribute of the notification argument provided is ‘true’, the equipment shall begin
notifying the client (if it is not already doing so) whenever a change in the metadata is detected, starting with the
first detected change after the client invokes the operation. If the change is detected while the equipment is in a
disabled communications state, the equipment shall notify the interested clients at the first opportunity when its
communication status permits.
9.1.2.10.4 If the ‘enable’ attribute of the notification argument provided is ‘false’, the equipment shall cease
sending revision notifications to the client, if it is currently doing so. The equipment shall ignore duplicate
enable/disable requests from the same client (see limitations, Section 3 ).
Figure 5
Metadata Revision
9.1.2.11 MetadataRevision — This class describes the most recent metadata revision date and time.
9.1.2.11.1 MetadataRevision Attribute Definition Table
Table 17 MetadataRevision Attribute Definition
Attribute Name Definition Form
revisionDate The most recent date and time at which the
equipment metadata has changed.
Text, formatted according to ISO 8601.
Implementations may specify additional formatting
restrictions within the 8601 specification.
Figure 6
Notification Request
MetadataRevision
revisionDate
NotificationRequest
enable
SEMI E125-0305 © SEMI 2003, 2005 12
9.1.2.12 NotificationRequest — This class describes the notification preferences of the metadata client.
9.1.2.12.1 NotificationRequest Attribute Definition Table
Table 18 NotificationRequest Attribute Definition
Attribute Name Definition Form
enable The client’s preference for revision notification. Boolean. If true, the client’s preference is to be
notified of metadata revisions. If false, the
preference is to not be notified of metadata revisions.
9.2 Metadata Client
9.2.1 Figure 7 shows the interface and argument data types that clients must support in order to receive metadata
revision notifications.
Figure 7
Metadata Client Interface
9.2.2 MetadataClient Operations
Table 19 MetadataClient Operation Definition
Operation Description Type
MetadataRevised Notifies the client that the metadata has recently changed. FF
9.2.2.1 MetadataRevised — The equipment shall send this notification whenever it detects a change in the
metadata, if the client has requested to be notified through a prior invocation of the “NotifyOnRevisions” operation
of the EquipmentMetadataManager interface.
9.2.2.1.1 MetadataRevised Operation Arguments
Table 20 MetadataRevised Argument Definitions
Argument Description Kind Form
revision The date and time at which the metadata
change was detected by the equipment.
in Structured data of type RevisionNotice, described in
Section 9.2.2.2 .
MetadataRevised(in newRevision : RevisionNotice)
MetadataClient
«interface»
EquipmentElement
CEM::
equipment
RevisionNotice
11
1
newRevision
1
MetadataRevision
revisionDate
SEMI E125-0305 © SEMI 2003, 2005 13
9.2.2.2 RevisionNotice — This class provides the date and time of any metadata revision, and the equipment whose
metadata was changed.
9.2.2.2.1 RevisionNotice Association Definition Table
Table 21 RevisionNotice Association Definition
Association Role Name Definition Comments
equipment The root equipment node that represents the equipment as a
whole.
One and only one element of a type
derived from the SEMI E120 type
EquipmentElement.
newRevision The date and time at which the metadata was revised. Structured data, of type
MetadataRevision
9.2.2.2.2 equipment — Providing the root equipment node with a RevisionNotice should not be interpreted to mean
that the root equipment node’s metadata has changed. It is strictly provided as a means for clients to determine
which equipment has undergone the change.
10 Equipment Metadata
10.1 Management of Equipment Metadata
10.1.1 When equipment configuration changes result in a change to any information described using the classes in
Section 9.1.2.9 of this document or by the SEMI Common Equipment Model, the equipment shall update the
metadata description accordingly at the time of the change. If clients have requested revision notification (see
Sections 9.1.2.9 and 9.1.2.10 ), the equipment shall notify each interested client at the time of the change, or at the
first opportunity when its communication status permits. This includes reconfiguration of the equipment after its
introduction into the factory. Ensuring that all aspects of equipment metadata are kept up-to-date and available to
the factory is a critical aspect of maintaining equipment metadata.
10.2 Equipment Structure
10.2.1 The physical equipment structure shall be described according to the SEMI Common Equipment Model.
Suppliers shall provide a model of those elements of their equipment for which it is necessary and practical to
facilitate (at least) utilization tracking, process control, and technical support objectives.
10.3 Equipment Nodes
10.3.1 Equipment Node Description
10.3.1.1 Figure 8 shows how to describe the parameters, events, objTypes, and exceptions available from an
element (or node) of the equipment hierarchy. Providing this descriptions indicates that the specified node acts as
the source of all Events, Exceptions, ObjTypes, and Parameters that are included in the description. All Parameters,
Exceptions, ObjTypes, and Events associated with a given equipment node are independent of the Events,
Exceptions, ObjTypes, and Parameters associated with other equipment nodes.