Semiconductor Equipment and Materials International
3081 Zanker Road
San Jose, CA 95134-2127
Phone:408.943.6900 Fax: 408.943.7943
hb khghgh1000A4542
Background Statement for SEMI Draft Document 4542
REVISION TO SEMI E133, PROVISIONAL SPECIFICATION FOR AUTOMATED PROCESS CONTROL SYSTEMS INTERFACE
Note: This background statement is not part of the balloted item. It is provided solely to assist the recipient in reaching an informed decision based on the rationale of the activity that preceded the creation of this document.
Note: Recipients of this document are invited to submit, with their comments, notification of any relevant patented technology or copyrighted items of which they are aware and to provide supporting documentation. In this context, “patented technology” is defined as technology for which a patent has been issued or has been applied for. In the latter case, only publicly available information on the contents of the patent application is to be provided.
PLEASE NOTE: This ballot contains a proposal for a revision to an existing standard.
Purpose
Line item adjustments to E133 to: (1) provide additional specification of services and behavior for the Fault Classification (FC) analysis engine type as well as adjustments to E133 to support these additional specifications.
Background
E133 “Provisional Specification for Automated Process Control Systems Interface” Provisional Standard documentation indicates that, as part of the requirement to remove the provisional status designation, detailed specification should be provided for each of the analysis engine types. Currently this has been accomplished for the R2R control, FD and SPC engine types. This Line Item ballot focuses on additional specification for the Fault Classification (FC) analysis engine type.
Impact
This ballot will only impact this provisional standard. It will (1), provide additional specification of data structure, services and behavior for the FC analysis engine type, (2), provide adjustments to E133 to support these additional specifications.
Proposal
Line Item 1: Provide additional specification of structure, services and behavior for the Fault Classification (FC) analysis engine type, as well as updates to E133 to support these additional specifications.
Note that throughout this ballot the string “XXX#” in a Figure or Table caption will be replaced by the appropriate figure or table number when incorporated into E133.
The ballot begins on the next page.
The results of this ballot will be discussed at the next NA I&C committee meeting on July 17, 2008 in conjunction withthe Standards meetings at SEMICON West in San Francisco, California.
SEMI Draft Document 4542
REVISION TO SEMI E133, PROVISIONAL SPECIFICATION FOR AUTOMATED PROCESS CONTROL SYSTEMS INTERFACE
1 Line Item 1: Provide additional specification for services and behavior of the Fault Classification (FC) Analysis Engine type
Background
The PCS task force is enhancing the provisional standard E133 “Provisional Specification for Automated Process Control Systems Interface” as part of the effort to remove the provisional standard designation. In doing so they determined that further definition of data structure, services and behavior requirements for the Fault Classification(FC) Analysis Engine type needed to be investigated and added to the standard. These enhancements provide support for additional specification of the FC analysis engine type.
Ballot
All of these updates must be implemented.
1.1 Make the following modifications to Table 20: “Additional FC Functional Capabilities”:
1.1.1 Change FCC.A.1 to Required (‘R’) and FCC.A.2 to Optional (‘O’). Delete the comments in the comment column for both.
1.1.2 Replace the description of FCC.A.4:
Replace:
“Ability to communicate references to troubleshooting guides (TSG)
“Classification should allow users to link to an existing TSG. The result may be a reference link or a description from a list of recommended actions.”
With:
“Ability to communicate references to agents that might make use of the information such as TroubleShooting Guides (TSGs), Out of Control Action Plan (OCAP) systems, and Computerized Maintenance Management Systems (CMMSs)
“Classification should allow users to link to outside agents such as TSG, OCAP systems and CMMSs. This means that, in addition to application-to-application communication, the classification information provided by the FC engine can be interpreted by the outside agent, e.g., a classification can be mapped to a maintenance activity in a CMMS or an action plan in an OCAP system.”
1.1.3 Replace the description of FCC.A.5
Replace:
Ability to tag unclassified faults for future classification
To avoid inline delays it is necessary to defer classification until further studies are made. This may be the result of automated, manual, and re-classification tasks.
With:
Ability to indicate that a fault cannot be classified, and to tag unclassified faults for future classification
In some cases, data analysis does not reveal a classification of a fault, or does not reveal a classification that is appropriatefor reporting. Also, to avoid inline delays it is often necessary to defer classification until further studies are made. This may be the result of automated, manual, or re-classification tasks.
1.1.4 Modify FCC.A.6 (“Produce list of classifications by a method such as confidence or probability”)
1.1.4.1 In the Description field, change “Some metric” to “Metric”.
1.1.4.2 Add the following to the Comments field:
“An example is a Pareto presentation, such as classification candidates along with their probability of being the source of the fault.”
1.1.5 Add the following rows to the table:
FCC.A.7 / Ability to provide for fault classification of a non-equipment systemFault classification does not have to be limited to classification of equipment faults. / N / Examples include fault classification of a R2R control AE or a software system.
FCC.A.8 / Ability to accept data on the fault that was classified, and adapt to or learn from this information
The classification system should accept feedback that provides the results of investigation of a particular fault classification that was communicated, and adapt or improve internal classification capabilities. The method for adapting or improving is beyond the scope of this standard. / N / As an example, if the FC AE reports a Pareto of possible fault classifications, the client of the FC system might report back the actual cause of the problem among the possibilities.
FCC.A.9 / Ability to support further investigation of a reported fault classification
The classification system should provide a capability for further inquiry into details associated with a reported fault classification. / N / This capability is often referred to as “drill-down” and could include reporting of raw and processed data associated with the classification, classification calculations, and data quality indicators. It could also include transactions to support step-wise decision-tree style analysis of classification information.
1.2 Add the following subsections to Section 9.5, “Fault Classification Functional Group”, with the following contents:
9.5.4 FC general capability description
9.5.4.1 An FC module should accept the following inputs and outputs using the common interface structure described in Figure 5. Not all inputs and outputs are required depending on the functionality needed by the FC AE
9.5.5 Inputs—The following data types and data values are used in FC input messages:
9.5.5.1 The FC analysis engine inherits the input data structure and data structure requirements from the PCS Analysis Engine.
9.5.5.2 The following data types and data type values shall be supported by a FC analysis engine when included in an input data structure, where supported means that the AE will be able to utilize the information provided by the data type and perform any indicated action associated with that data:
9.5.5.2.1 PCSAETarget Class
9.5.5.2.1.1 Attribute AEType with a value of “FCC”
9.5.5.2.1.2 A List element of attribute “Instructions” with a value of “PCSAnalyze”
9.5.5.2.1.3 (optional) A List element of attribute “Instructions” with a value of “PCSUpdateModel”
9.5.6 Outputs—The following data types and data type values are used in FC output messages:
9.5.6.1 The FC analysis engine inherits the output data structure and data structure requirements from the PCS Analysis Engine.
9.5.6.2 The following data types and data type values shall be supported by a FC analysis engine when included in an output data structure, where supported means that the AE will be able to provide these data types and values when behavioral conditions warrant, as indicated below.
SEMI E133 Code Attribute Value Definitions—The following additional Code attribute value definitions shall be supported (see Table 8 also).
Table XXX0 FC Functional Group Code Attribute Value Definitions
Source / Code / Description / ExtensionE133 / -32 / Unable to provide classification information / <manufacturer specific>
E133 / -33 / Unable to provide classification information at this time / <manufacturer specific>
9.5.6.2.1 DataCollection Class — The following DataItem Names or Name/Value pairs shall be supported for DataItems in the specified BinCategory.
Table XXX1 Data Types Required to be Supported by an Input Message for an Analysis Engine
BinCategory / DataItem Name / Value / Description / Role#1 / Req’d / FormCalculated
Outputs / FaultClassificationAdvice / N.A.#2 / The Fault Classification information. The structure of this attribute is beyond the scope of this standard. For example, the information could be an ordered list of a structure that contains the classification and the classification probability, as a Pareto report. Context associated with the AnalysisEngineDataSet Input may identify the system to which the FC information applies. / D / Y / any
#1 Where, in the Role column, ‘D’ indicates “data” and ‘C’ indicated “context”.
#2 N.A. indicates “not applicable”, because specification is on DataItem as opposed to a specific value of DataItem.
9.5.6.2.2 FaultClassificationAdvice — This attribute contains the fault classification information. The structure of this attribute as well as the method in which the Fault Classification advice is utilized is beyond the scope of this document.
9.5.7 FC Interface Services
9.5.7.1 The FC analysis engine inherits Common Interface Services as specified in Section 9.2.4.
9.5.7.2 The inherited PCSEvent service shall be required.
9.5.7.3 The FC analysis engine shall additionally support the following services.
Table XXX2 Additional FC AE Object Service Resource Definition*
Service / Req’d / Type** / DescriptionFCCClassification / N / N / Used to provide a fault classification capability through notification of a classification event as defined in Section 5 and Table 19. This notification service is only utilized if the FCC AE is operating in an Asynchronous behavioral mode, as defined in Section 9.2.5.
* Except as specified in Section 9.2.4.1.1 PCS AEs shall provide services by accepting and producing
messages that are compliant with the common interface data structure as defined in Section 9.2.3.
** See section 9.2.5.
9.5.7.3.1 The following parameters are specified for this service:
Table XXX3 FCCClassification Service Parameter Definition
Parameter#1 / Requirement / Form / DescriptionFaultClassificationAdvice / Y / See Table XXX1 / See Table XXX1
#1 Parameter provided in the Notification message if the AE can provide the appropriate classification information. See Section 9.5.8 for further information.
9.5.8 FC Interface Behavior
9.5.8.1 The FC analysis engine inherits Common Interface Behavior as specified in Section 9.2.5.
9.5.8.2 The FC analysis engine shall additionally support the following behavior.
9.5.8.3 The FC analysis engine shall support both the Synchronous PCSJob and optionally support Asynchronous PCSJob behavioral classes as specified in Section 9.2.5.4.2.
9.5.8.3.1 If the FC AE receives an input message of type AnalysisEngineDataSet for a process control job, and, in the PCSAETarget attribute of that message, one of the list of instructions in the Instructions attribute has a value of “PCSAnalyze”, then the FC AE shall provide capability FCC.I.1 (see Table 19). Specifically the AE shall provide an output message of type AnalysisEngineDataSet that contains the data item name “FaultClassificationaAdvice” in a DataCollection where BinCategory == “Calculated Outputs”.
9.5.8.3.2 If the FC AE receives an input message of type AnalysisEngineDataSet for a process control job, and, in the PCSAETarget attribute of that message, one of the list of instructions in the Instructions attribute has a value of “PCSUpdateModel”, and, further, if the FCC.I.8 or FCC.A.8 (see Tables 19 and 20) capabilities are supported, then the FC AE shall utilize the information provided as part of the associated PCS job to update classification models as necessary. The determination of the need to update models and the method in which these models are updated is beyond the scope of this standard.
9.5.8.3.3 If the FC AE supports Asynchronous PCS Job behavior it will utilize the FCCClassification notification service to report classification information associated with an open Asynchronous PCS Job. Specific classification information is reported utilizing the FaultClassificationAdvice service parameter. Indication of the lack of capability to provide classification information is communicated by utilizing the appropriate Status Element Code attribute value (see Table 8). The utilization of the FaultClassificationAdvice service parameter in this case is beyond the scope of the standard, though the parameter may be used to communicate details regarding the lack of ability to provide classification information.
1.3 Make the following changes to Table 8: SEMI E133 Code Attribute Value Definitions
Replace the row (header information included for clarity):
Source / Code / Description / ExtensionE133 / -8 to -99 / <Not specified: reserved> / <manufacturer specific>
With the following two rows:
Source / Code / Description / ExtensionE133 / -8 to -31 / <Not specified: reserved for future generic AE use> / <manufacturer specific>
E133 / -32 to -99 / <Reserved for specific AE type use; reserved unless otherwise indicated in AE functional group specification> / <manufacturer specific>
NOTICE: SEMI makes no warranties or representations as to the suitability of the standard(s) set forth herein for any particular application. The determination of the suitability of the standard(s) is solely the responsibility of the user. Users are cautioned to refer to manufacturer’s instructions, product labels, product data sheets, and other relevant literature respecting any materials or equipment mentioned herein. These standards are subject to change without notice.
By publication of this standard, Semiconductor Equipment and Materials International (SEMI) takes no position respecting the validity of any patent rights or copyrights asserted in connection with any item mentioned in this standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and the risk of infringement of such rights are entirely their own responsibility.
This is a draft document of the SEMI International Standards program. No material on this page is to be construed as an official or adopted standard. Permission is granted to reproduce and/or distribute this document, in whole or in part, only within the scope of SEMI International Standards committee (document development) activity. All other reproduction and/or distribution without the prior written consent of SEMI is prohibited.
Page 1Doc. 4542 SEMI