SEMI International Standards
Standards New Activity Report Form (SNARF)
Revised (if Applicable):
Revision to E125 SPECIFICATION FOR EQUIPMENT SELF DESCRIPTION (EqSD)
Originating Global Technical Committee:
Information & Control
Originating TC Chapter:
Task Force (TF) in which work is to be carried out:
Diagnostic Data Acquisition Task Force NA
Note: If a new task force is needed, also submit a task force organization form (TFOF)
a. Describe the need or problem addressed by this activity.
(Indicate the customer, what benefits they will receive, and if possible, quantify the impact on the return on investment [ROI] if the Document is implemented.)
Note that most of the items listed were previously approved as part of SNARF 6527. It has been revised because certain voters claim that the proposed changes in ballot 6527C were out of scope. SEMI Regulations prevent revising the existing SNARF with new scope items. This revision also intends to make it clear that every proposed change cannot be predicted, yet still convey the intended changes and magnitude of the changes. This activity started in 2017.
During the implementation and adoption of EDA freeze versions 1 and 2, many lessons have been learned. The task force wishes to simplify EDA and resolve various issues that have emerged. This includes SimpleEvent and Parameters which are directly defined in Node Description, in spite of being referenced in StateMachine, SEMI Object and Exception. The proposed changes are intended to become an important portion of EDA freeze 3. In this proposal, Simple Event and Parameter define a separate web service as like StateMachine, SEMIObject and Exception. Units are unnecessarily complex and could be simplified. The concept of client and consumer is poorly developed and needs to be clarified. Some users have complained that SEMIObjects are too complex; therefore a simplified implementation of SEMIObjects might make it easier to use and implement.
Other changes are sure to be requested as these changes are designed, as E132 and E134 are concurrently modified and as more members contribute various ways to improve EDA.
In a few cases, E125 was written with SOAP/XML technology in mind. As EDA freeze 3 proposes to move to gRPC technology, E125 needs some modifications to abstract it from any specific technology. Specific technology should be clarified in a subordinate standard.
b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information:
Major effect on anyone implementing or adopting the EDA standards and choosing to upgrade.
c. Estimate technical difficulty of the activity.
II: Some Difficulty - Disagreements on known requirements exist but developing consensus is possible
Describe the technical areas to be covered or addressed by this Document development activity. For Subordinate Standards, list common concepts or criteria that the Subordinate Standard inherits from the Primary Standard, as well as differences from the Primary Standard:
Major and technical changes will be made to E125. The Changes to recognize Complementary Files and Materials will be made. Due to changes in E125, E164 should be changed after completion of this proposal. E164 is out of scope in this proposal.
1. Refine the definition of client, consumer and the equipment server.
2. Remove SOAP/XML specific details and make abstract references to technology that is resolved in a subordinate standard.
3. Add operation GetParameters to return parameter defintiions and have all other nodes using parameters reference the returned definitions to consolidate definitions into one location.
4. Add operation GetSimpleEvents to return simple event defintiions and have all other nodes using simple events reference the returned definitions to consolidate definitions into one location.
5. Change Association Definitions and attributes of EquipmentNodeDescription, StateMachine, SEMIObj, SEMIObj Attributes, Parameters and Exceptions.
6. Develop a method to distinguish between “all” instances of a state machine and a “specific” instance of a state machine for E134 event reports.
7. Refine Parameter Attribute and Association Definition.
8. Refine SimpleEvent Attribute and Association Definition.
9. Simplify the SEMIObj implementation. Make attributes a separate class from parameters.
10. Change Attributes for Node Description.
11. Add new parameter attributes to support “cached data sample” properties.
12. Simplify the representation of Units used by Attributes and Parameters
13. Any other changes to keep E125 consistent and compatible with changes proposed in E132 and E134 ballots.
14. Define Notification Message and Operational Message concepts and clarify when they will be sent and how errors are handled.
15. Integrate Client Session and Consumer Session concepts
16. Removing implementation specific details in the primary standard (for example SOAP/XML)
17. Make error handling consistent.
As a major revision ballot, this ballot may include other changes to address features or defects raised by task force members during the review and development of the proposed changes listed above and that are desired to be part of EDA freeze 3. Significant changes in scope still require a SNARF revision in compliance with SEMI regulations.
b: Expected result of activity
Major revision to an existing Standard or Safety Guideline
For a new Subordinate Standard, identify the Primary Standard here:
Modification of an existing part of Standard(s) or Safety Guideline(s) including Appendices, Complementary Files, and Supplementary Materials
For Standards, identify the Standard Subtype below:
3. Projected Timetable for Completion:
a: General Milestones
a. Activity Start:
b. 1st Draft by:
c. (Optional) Informational Ballot by:
d. Letter Ballot by:
e. TC Chapter Approval By:
4. Liaisons with other Global Technical Committees/TC Chapters/Subcommittees/TFs:
List SEMI global technical committees, TC Chapters, subcommittees, or task forces in your or other Regions/Locales that should be kept informed regarding the progress of this activity. (Refer to SEMI Standards organization charts and global technical committee charters and scopes as needed.)
Global I&C Technical Committee
List any planned Type I Liaisons with external nonprofit organizations (e.g., SDO) that should receive Draft Documents from Standards staff for feedback during this activity and be notified when the Letter Ballot is issued (refer to Procedure Manual § 7):
will not be issued
Identify the recipient global technical committee(s):
5. Safety Considerations:
The resulting document is expected:
NOT to be a Safety Guideline
to be a Safety Guideline
": When all safety-related information is removed from the Document, the Document is NOT technically sound and complete - Refer to Section 15.1 of the
for special procedures to be followed.
NOT to be a Safety Guideline
": When all safety-related information is removed from the Document, the Document is still technically sound and complete.
6. Intellectual Property Considerations:
For a new Standard or Safety Guideline and for any part to be modified or added in a Revision of published Standards and Safety Guidelines
patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s).
If "patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s) " is selected above, then also check one:
Letter of Intent received
For Revision, Reapproval, Reinstatement, or Withdrawal of existing Standard(s) and Safety Guideline(s):
there is previously known material patented technology necessary to use or implement the Standard(s) and Safety Guideline(s)
The body of the Document and any Appendices, Complementary Files, Related Information sections, or Various Materials that may or may not be a part of the Document by reference:
the incorporation of Copyrighted Item will NOT be required
the use of patented technology or the incorporation of Copyrighted Item(s) is NOT required’
: If in the course of developing the Document, it is determined that the use of patented technology or Copyrighted Item(s) is necessary for the Document, the provisions of
§ 16 must be followed.
will incorporate Copyrighted Item’
: A copyright release letter must be obtained from the copyright owner prior to publication.
7. Comments, Special Circumstances:
TC Member Review:
took place between (put dates below) before approval by the GCS, or
Member Review Start Date;
Member Review End Date:
‘TC Member Review’ is required by the
for a period of at least two weeks
before approval of a new, or a major revision of an existing, Standard or Safety Guideline. (Refer to
9. SNARF Approval Dates:
TC Chapter or GCS
Recorded in TC Minutes
10. SNARF Extension Dates:
TC Chapter Extension Granted on
Extension Expires on
Attach Pictures and Files here: