SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 08/01/2024Revised (if Applicable):

Document Number: 7288
SNARF for: Line Item Revision to
SEMI E120-0922 (Reapproved 0823) Specification for the Common Equipment Model (CEM),
SEMI E120.2-0823 Specification for Protocol Buffers for Common Equipment Model (CEM),
SEMI E125-0923, Specification for Equipment Self Description (EqSD) and SEMI E125.2-0923 Specification for Protocol Buffers for Equipment Self Description (EqSD),
SEMI E132-0624 Specification for Equipment Client Authentication and Authorization,
SEMI E132.2-0624 SPECIFICATION FOR PROTOCOL BUFFERS FOR EQUIPMENT CLIENT AUTHENTICATION AND AUTHORIZATION (ECA),
SEMI E134-0624 Specification for Data Collection Management,
SEMI E134.2-0624 Specification for Protocol Buffers of Data Collection Management,
SEMI E179-0624 Specification for Protocol Buffers Common Components

Originating Global Technical Committee: Information & Control
Originating TC Chapter: North America
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)

___________________________________________________________________________
1. Rationale:
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.)
Since the DDA task force initiated the freeze 3 work, the style recommendations for protocol buffer files changed. Adherence to the style guide makes protocol buffer technology easier to use in some software programming environments. Proposed changes to the E120, E125, E132 and E134 protocol buffer files are all related and all depend on changes in the E179 protocol buffer file. Therefore, as required by SEMI Regulations section 3.7.1, it is necessary to use a single line-item ballot for the proposed changes to all of these standards.

DDA task force is planning to conduct another vender test focused on E134 data collection. As participants prepare for this testing, software engineers may encounter issues that need to be resolved. In preparation for this test, feedback has already been received by some participants and task force members. For example, there is a technical issue with the E134 operations GetObjTypeInstanceIds and GetObjTypeAttributes.

This SNARF replaces the individual SNARFs previously approved for E120, E125, E132, E134 and E179, including SNARF 7227 which failed at the SEMICON West 2024 I&CC meeting.


b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information: Anyone implementing EDA

c. Estimate technical difficulty of the activity.
II: Some Difficulty - Disagreements on known requirements exist but developing consensus is possible

___________________________________________________________________________
2. Scope:
a: 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:
As part of the work on this Line-Item Revision, the task force will investigate:

· Propose changes to all of the .proto files to better align with the current protocol buffer style guide: https://protobuf.dev/programming-guides/style/
· Modify E134 operations GetObjTypeInstanceIds and GetObjTypeAttributes to handle multiple object types. The current list of text return values are insufficient.
· Consider handling invalid request IDs in E134
· Review how trace triggers are defined in the E134 .proto files
· Modify the protocol buffer style guide deviation explanations in the E179 Related Information
· Address additional member feedback, including whether E125 VID data types are defined correct and messages related to SEMIObjType are defined correctly.
· Changing data format for date and time information to be specified by Subordinate standards, based on the implementation technology, rather than be a text data format. (for SEMI E125.2, it is the google.protobuf.Timestamp message data type
· In E125, update Equipment Nodes Description – added equipmentNodeId, remove CEM:Nameable object and reference.
· In E125, update Unit to match Units defined generically and the associated example.
· In E125, move SECS identification for Events and Exceptions out of EquipmentNodeDescription into SimpleEvents and Exceptions objects
· In E125, update State Machine Reference to move SECS information into its own class to be consistent with how SECS information is organized

All proposed changes to .proto files will be in one line item. The proposed protocol buffer files will be used in the Vender Test session.

Any other changes to address features or defects, or issues with the SEMI Style Guide raised by Task Force members during the development and review of the proposed changes related to these line item topics. This includes items discovered by Task Force members during planned EDA Software Vendor Test Session #2 and #3 organized by the North America DDA Task Force. Significant changes in scope still require a SNARF revision in compliance with SEMI Regulations.

b: Expected result of activity
Line-item revision to two or more existing Standards or Safety Guidelines

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, Addition of one or more Related Information sections or Various Materials to an existing Standard or Safety Guideline, Revision or addition of one or more Subordinate Standards to an existing Primary Standard

For Standards, identify the Standard Subtype below:
Specification

Miscellaneous (describe below):

___________________________________________________________________________
3. Projected Timetable for Completion:

a: General Milestones
a. Activity Start: 08/01/2024b. 1st Draft by: 08/01/2024
c. (Optional) Informational Ballot by: d. Letter Ballot by: 09/01/2024
e. TC Chapter Approval By:11/01/2024

_____________________________________________________________________________
4. Liaisons with other Global Technical Committees/TC Chapters/Subcommittees/TFs:
a. 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.)
/I&C Global Technical Committee

b. 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):


c. Intercommittee Ballots:
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

NOTE FOR "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 Regulations for special procedures to be followed.

NOTE FOR "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:
Note: Both a: and b: below should be checked for Revision of existing Standard(s) and Safety Guideline(s).

a. 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, other than previously known patented technology identified in b: below, 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

b. 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)

c. 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



NOTE FOR ‘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 Regulations § 16 must be followed.

NOTE FOR ’will incorporate Copyrighted Item’: A copyright release letter must be obtained from the copyright owner prior to publication.

___________________________________________________________________________
7. Comments, Special Circumstances:
SEMI E120, E120.2, E132, E132.2, E125, E125.2, E134, E134.2 and E179 included patent material and is covered by NON-ASSERTION AGREEMENT (LOA) between SEMI and Asyst Technologies has been signed with for US Patents #11/340101, #11/107508, #09/899833, and 09/496009, in 2007. This agreement is maintained by PEER Group, who has acquired the patents and patent applications previously owned by Asyst Technologies

No intent to add new patent material as part of this Line Item Revision.

__________________________________________________________________________
8. TC Member Review:
is not required for this SNARF.

Member Review Start Date; None.
Member Review End Date: None.

NOTE FOR ‘TC Member Review’ is required by the Regulations 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 Regulations ¶ 8.2.1)
__________________________________________________________________________

9. SNARF Approval Dates:
TC Chapter or GCS08/13/2024
Recorded in TC Minutes

__________________________________________________________________________

10. SNARF Extension Dates:
TC Chapter Extension Granted on
Extension Expires on