semi合集-English.pdf - 第3433页
SEMI E133-0705 © SEMI 2004, 2005 14 9.2.3.3. 4 In each DataCollection all DataIte ms whose role is “C ontext” shall occur before the first DataItem whose role is “Data” occurs. Figure 6 Illustration o f Ordering of I nfo…
SEMI E133-0705 © SEMI 2004, 2005 13
The message is a response to a request for service(s) from that AE, e.g., a reply message.
9.2.3.2.2 DataCollection — A set of data and associated context for that data that conforms to the PCS AE common
input/output structure as defined in ¶9.2.2.1
Table 9 Attributes of DataCollection
Attribute Name Description Access Reqd Form
BinCategory An enumerated identifier of the type of data collection among the
possible types defined in the collection type enumeration, listed in Table
4.
NA Y CollectionType — As
defined.
9.2.3.2.2.1 CollectionType — An enumeration of BinCategory as defined in Table 4.
9.2.3.2.3 DataItem — An individual component of a data collection that has meaning in the PCS environment.
Each data item has a role of either “context” or “data” as determined by the client of the PCS AE.
Table 10 Attributes of DataItem
Attribute Name Description Access Reqd Form
Name Human-readable name for DataItem NA Y StringValue — See
rules for naming
below.
Value An assigned or calculated quantity NA Y AbstractValue — As
defined in SEMI
E134.
9.2.3.2.3.1 Name — This attribute is used to provide a level of understanding of the meaning and purpose of the
DataItem. Names shall consist of alphanumeric characters, spaces, hyphens and underscores. Names shall start
with an alpha character, and shall not contain leading or trailing spaces.
9.2.3.2.3.2 Value — AbstractValue as defined in SEMI E134 is an abstract base class that is used to represent
standard types including: Integer, Real, Boolean, String, Binary, Structure, Array, and Enumerations. In this way,
parameter values collected via SEMI E134 may be passed directly into the PCS compliant AE via the value attribute
of a DataItem. Refer to SEMI E134 for further definition of the AbstractValue type. AbstractValue base class
allows for arbitrarily complex data items to be passed into the AE.
9.2.3.2.3.3 A DataItem that belongs to a DataCollection whose CollectionType is “Globals” may not serve a role of
data (i.e., it can only serve the role of context).
9.2.3.2.3.4 It is not required that the PCS AE utilize a data item in the same role (Data or Context) as is specified by
the PCS AE client, however the PCS AE is required to maintain the role representation in I/O data structures
produced or consumed across a PCS AE interface.
9.2.3.3 Ordering of Elements Within An AnalysisEngineDataSet — In addition to compliance with a data structure
model, this standard also defines rules governing ordering of classes and attributes within each
AnalysisEngineDataSet instance, corresponding to the data content of an AE I/O message. Figure 4 provides a
general illustration of this ordering. The following are rules governing that ordering.
9.2.3.3.1 The first attribute of any AnalysisEngineDataSet shall be the Process Control System Job ID (PCSJobID),
if the PCSJobID value has been determined as defined in ¶9.2.3.2.1.
9.2.3.3.2 The first attribute of any DataCollection shall be BinCategory.
9.2.3.3.3 The first DataCollection shall be of BinCategory “Globals” if the AnalysisEngineDataSet contains a
DataCollection of that kind. At most one DataCollection shall be of BinCategory “Globals” in any
AnalysisEngineDataSet.
SEMI E133-0705 © SEMI 2004, 2005 14
9.2.3.3.4 In each DataCollection all DataItems whose role is “Context” shall occur before the first DataItem whose
role is “Data” occurs.
Figure 6
Illustration of Ordering of Information in an AnalysisEngineDataSet Instance
(Partial example; “…” is used to indicate possible continuation in the listed format; PCSJobID in this
example is aligned with specifications in SEMI E120.1)
PCSJobID == “[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}”
PCSAETargets
APCSAETarget: PCSAETarget
AEType == “R2R”
AEInstance == 1
Instructions
Instruction == “R2RCalculateControlAdvice”
Extension == “execute serially”
Status
AStatusElement: StatusElement
Source == “urn:semi-org:E132”
Code == 0
ADataCollection: DataCollection
BinCategory == “Globals”
Role == “Context”
ADataItem: DataItem
AName: (type == text)
AValue: (type == any)
ADataItem
AName: (type == text)
AValue: (type == any)
BinCategory == “ModuleData”
Role == “Context”
ADataItem: DataItem
AName: (type == text)
AValue: (type == any)
…
Role == “Data”
ADataItem: DataItem
AName: (type == text)
AValue: (type == any)
…
BinCategory == “ProcessData”
Role == “Context”
ADataItem: DataItem
AName: (type == text)
AValue: (type == any)
…
Role == “Data”
ADataItem: DataItem
AName: (type == text)
AValue: (type == any)
…
…
SEMI E133-0705 © SEMI 2004, 2005 15
9.2.3.4 Additional Requirements of an AnalysisEngineDataSet
9.2.3.4.1 If multiple AnalysisEngineDataSet instances are “related”, as defined in ¶9.2.3.2.1 and both contain the
same DataCollection with the same value of BinCategory, and further contain the same DataItem (with the same
“Name”) within that DataCollection, the last DataItem shall be assumed to be correct. The interpretation of ordering
of information as communicated by the underlying protocol is beyond the scope of this document.
9.2.3.4.2 Within an AnalysisEngineDataSet instance or a group of instances that are “related”, as defined in
¶9.2.2.1, a DataItem may exist within multiple DataCollections that has a role of context. If this condition exists,
the following rules shall apply.
9.2.3.4.2.1 Any Context DataItems defined in a DataCollection with BinCategory = “Globals” should be used as
Context DataItems for all other BinCategorys in any related message except as defined in ¶9.2.3.3.2.2 below.
9.2.3.4.2.2 If a DataCollection with a BinCategory other than “Globals” defines a Context DataItem that is also
defined in the Global BinCategory of the current message or a related message, the local BinCategory DataItem
value should be used as context, i.e., the local Context DataItem overrides the Global value inside this
DataCollection.
9.2.3.5 Utilizing multiple application-to-applications to communicate a PCS — A PCS message may be broken into
a number of application-to-application communications or partitions, however it is not required that a PCS AE
support this partitioning capability. Each of these communication partitions must conform to the data model of
Figure 3, with the following modifications:
9.2.3.5.1 PCSAETarget minimum cardinality is zero.
9.2.4 Common Interface Services
9.2.4.1 All PCS Analysis Engines shall support the following common interface services:
A set of services shall exist to support input of data into the engine,
A set of services shall exist to support access to data from the engine,
A set of services shall exist to support logging and exception handling, and
A set of services shall exist to support execution and model update.
9.2.4.2 These services will be defined further in §10. Each class in the interface could be part of an input or an
output message.
9.2.5 Common Behavior
9.2.5.1 All PCS Analysis Engines shall support the following common behavior:
Accept inputs, and
Provide outputs.
9.2.6 Analysis Engine General Capability Description
9.2.6.1 An AE module should accept the following inputs and outputs using the common interface structure
described in Figure 3. Not all inputs and outputs are required depending on the functionality needed by the AE.
9.2.7 Inputs—The following data types and data values are used in AE input messages.
9.2.7.1 No data types or data values are specified for the general AE.
9.2.8 Outputs—The following data types and data values are used in AE output messages.
9.2.8.1 No data types or data values are specified for the general AE.
9.3 Run-to-Run Control Functional Group
9.3.1 This section defines the common capabilities and interface data structures of the R2R Control functional
group.