semi合集-English.pdf - 第3430页
SEMI E133-0705 © SEMI 2004, 2005 11 If the application communicatin g with the AE is managing a PCSJo bID for a PCS job, then that PCSJobID shall be provided as the value of th e PCSJobID attribute for all inte rface d…
SEMI E133-0705 © SEMI 2004, 2005 10
PCSJobID: text
AnalysisEngineDataSet
Name: text
Value: any
DataItem
Data Context
0..* 0..*
At least one of
Data or Context
DataCollections
0..*
PCSAETarget
AEType: Enumeration
AEInstance: Integer
Instructions: text
Extension: any
PCSAETargets
0..
BinCategory: Enumeration
DataCollection
{ordered}
StatusElement
Source: text
Code: Integer
Description: text
Extension: any
Status
0..*
Figure 3
Analysis Engine Data Structure Model for a Complete Message Associated with a PCS Job
9.2.3.2 Class Definitions — Class definitions consist of a brief description of each class, a table defining any
attributes belonging to that class, and further text as necessary to fully define the class.
9.2.3.2.1 AnalysisEngineDataSet — A composite data structure that represents the data associated with a single
input or output message of an AE.
Table 6 Attributes of AnalysisEngineDataSet
Attribute Name Description Access Reqd Form
PCSJobID A unique identifier of a Process Control System Job. NA C ObjID—reference
SEMI E39
PCSAETargets An attribute that indicates a list of AE types targeted by the
A
nalysisEngineDataSet
NA Y An ordered list of
structured data of
type PCSAETarget;
see below.
Status An attribute formatted as an extensible data structure that relates
p
roperties of the success or failure of a PCS AE, identified in
P
CSAETargets, to execute a PCSJob
NA C An unordered list of
structured data of
type StatusElement;
see below.
9.2.3.2.1.1 PCSJobID — The specification that PCSJobID is a required attribute of AnalysisEngineDataSet along
with the specification that it is a unique identifier of a PCS Job means that a unique PCSJobID shall be associated
with each PCS Job. The management of the uniqueness of the PCSJobID can be performed by an AE or by an
application that wishes to utilize the capabilities of an AE. The application communicating with the AE is assumed
to generate and manage PCSJobIDs for all PCS jobs, however the AE is required to provide this functionality in the
event that the application does not wish to provide it. The existence of the PCSJobID attribute is conditional upon
the following:
SEMI E133-0705 © SEMI 2004, 2005 11
If the application communicating with the AE is managing a PCSJobID for a PCS job, then that PCSJobID shall
be provided as the value of the PCSJobID attribute for all interface data structures of type
AnalysisEngineDataSet associated with that PCS Job.
If the AE is providing the functionality of generating a PCSJobID for a PCS job, then the PCSJobID shall be
provided in the first communication from the AE (to any consuming application) for this job and all subsequent
communications associated with this job.
The PCSJobID is not required for transactions that do not involve the AE executing a Process Control Job such
as status checks, or pre-processing queries.
9.2.3.2.1.2 PCSAETargets — This attribute indicates a list of AE types targeted by the AnalysisEngineDataSet; it is
structured as an ordered list of type PCSAETarget (see below). At most one PCSAETargets value shall be
associated with Each PCSJobID. Thus any two messages received by a PCS AE with the same PCSJobID will have
at most one value for PCSAETargets, which could be provided in either or both messages. Each AE that receives
this parameter in an input AnalysisEngineDataSet will echo the parameter and its value for all output
AnalysisEngineDataSet messages with that PCSJobID.
9.2.3.2.1.2.1 PCSAETarget — This attribute class represents an AE targeted by the current PCSJob. The
PCSAETarget attribute is used to differentiate PCS AE targets when a single message travels between multiple AE’s
(often referred to as a “daisy chain”). In this case the AEType and AEInstance attributes of the PCSAETarget (see
below) can be utilized to identify a particular consumer for the AnalysisEngineDataSet data. Note that in many
cases, such as point-to-point communications between an AE client and a single AE, the PCSAETarget attribute
may not be necessary.
9.2.3.2.1.2.1.1 This attribute has the following form:
PCSAETarget
AEType
AEInstance
Instructions
Extension
Figure 4
PCSAETarget Data Structure
Table 7 PCSAETarget Attribute Definition
Attribute Name Description Access Reqd Form
AEType An enumeration that represents the analysis engine type to which the
instruction is targeted.
NA N Enumeration, with
possible values being
(“FDD”—Fault
Detection, “FCC”—
Fault Classification,
“FPP”—Fault
Prediction, “R2R”—
Run-to-Run Control,
“SPC”—Statistical
Process Control,
“PCS”—Process
Control System).
AEInstance A number indicating the specific instance of an analysis engine within a
type that is targeted.
NA N Integer
Instructions An ordered list of Instructions, where each instruction is of type text. NA Y Ordered list of
elements of type text
Extension This attribute allows the supplier to include additional information
regarding the targeted AE instance.
NA N Any
SEMI E133-0705 © SEMI 2004, 2005 12
9.2.3.2.1.2.1.2 The specification of how the AEs will consume the information is beyond the scope of this standard.
9.2.3.2.1.2.1.3 The AEType enumeration of “PCS” is used to indicate a generic PCS type, or is an unspecified type.
9.2.3.2.1.2.1.4 An AEInstance value is not specified indicates that the instance of AEType is unspecified.
9.2.3.2.1.2.1.5 When multiple PCSAETarget instance values are specified, the target PCS application to which
these values refer should execute the PCSJob associated with the PCSJobID in sequence. The mechanism for
ensuring this behavior is beyond the scope of this standard.
9.2.3.2.1.2.1.6 Instructions is an ordered list of elements, each of which is an instruction and is of type text. Note
that no two elements in the ordered list can have the same value. An instruction is an attribute that relates a specific
task that is being requested to be carried out by a targeted AEInstance.
9.2.3.2.1.3 Status — This conditional attribute class relates properties of the success or failure of a PCS AE,
identified in PCSAETargets, to execute a PCSJob. The attribute has the following form:
StatusElement
Source
Code
Description
Extension
Figure 5
StatusElement Data Structure
Table 8 StatusElement Attribute Definition
Attribute Name Description Access Reqd Form
Source Represents the document from where the attribute code value is defined.
For example “Source” could identify a SEMI standards document. For
status codes defined by SEMI standards, the content of Source is the urn
representation of the standard number. For status codes defined by a
supplier, it is the urn representation of the supplier’s name. (e.g., for
SEMI E132 errors, the content of “Source” is: urn:semi-org:E132; for
supplier company errors, for instance, where company name is “Acme”,
the content is: urn:Acme-com) Additional information may be included
by the supplier by adding such information after the “:” colon symbol and
separating the fields with a “.” period symbol. Please refer to SEMI
E121 for additional information.
NA N Text.
Code A value that directly maps to a particular specification status code list.
The source of this list is beyond the specification of this document. A
status code of zero indicates that no error has occurred, while any non-
zero status indicates an error has occurred.
NA Y Integer.
Description A human readable description of the corresponding code attribute being
reported. It maps directly to the definition of the Code attribute.
NA N An unordered list of
structured data; see
below.
Extension This attribute allows the supplier to include additional information
regarding the status code encountered. Additional information may be
supplied in this attribute to provide more detail about any error (Ex.
Common Component, Code 5001, “Insufficient Arguments
Provided:Argument “SessionID” missing”).
NA N Any.
9.2.3.2.1.3.1 The existence of the StatusElement attribute is conditional on the properties of the message containing
a data structure of type AnalysisEngineDataSet. The StatusElement attribute shall exist if and only if the following
conditions apply:
The message is an output from an AE.