SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 11/06/2022Revised (if Applicable):

Document Number: 7003
SNARF for: Revision to SEMI E134-1022 Specification for Data Collection Management and SEMI E134.2-1022 Specification for Protocol Buffers of Data Collection Management

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.)
SEMI E134 defines data collection management. As implementers work on solutions using gRPC and Protocol Buffers technology to support EDA Freeze 3 standards being developed by the DDA Task Force, some new requirements and gaps are identified.

This Revision is to address these issues and clarify things to help the reader.


One of the proposed changes is to modify Client Session and Consumer Session terminology to Client and Consumer terminology with new definitions. Although this is a self-contained change, the terminology is used extensively throughout the documents, and the authors feel it would be better for all the changes to be contained in one revision ballot, rather than in separate line item revisions (as was originally proposed in a different Line Item Revision SNARF).


SEMI E134.2 is updated in the same Revision Ballot to ensure consistency between the two standards.
SEMI E134.1 is an inactive Standard and will not be updated.


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 Revision Ballot, the task force will investigate:

SEMI E134
· Replace the terms Client Session and Consumer Session with Client and Consumer terminology and specify definitions where Client and Consumer are defined based on who initiates the connection with the entity.

· Address TF Member feedback, including, but not limited to:
o Remove reference to removed ObjTypeResult class from 9.9.4.1 objIds
o In Table 40 – GetObjTypeInstanceIds Argument Definitions should have a new row for argument error that is “Element of type ObjTypeRequestError, described in Section 9.9.6”
o Could add in a figure of the ObjTypeRequestError class to be consistent with other class definitions.
o Fix incorrect references to limitation in attribute definitions.


SEMI E134.2
· Synchronize with changes in the primary standard, including but not limited to:
o Changing Client Session and Consumer Session terminology to updated Client and Consumer definitions
o Update GetObjTypeInstanceIdsResponseType message definition in the .proto file to match change to support argument error of type ObjTypeRequestError.

· Address TF Member feedback, including, but not limited to:
o Fix spelling and errors in .proto file comments.
o Update gRPC service definition names to remove redundant information.
o Investigate if we need multiple Trigger Groupings in the TraceRequestType message.
§ TraceRequestType.StartsOn could change to a single TriggerSelectorType message, not repeated. (Same for TraceRequestType.StopsOn).
o Investigate if we need to specify the parameter data type when the NoValueType field is set. (so implementations know if parameter data type is I4 or U4 so it can report the data type as part of an implementation’s logging).

· Investigate expanding use case scenarios in Related Information for clarity.

Changes to address any bias terminology to avoid in the Specification, Complementary File or Supplemental Material file.

Any other changes to address features or defects, or issues with the Style Guide raised by Task Force members during the development and review of the proposed changes related to these revision topics. Significant changes in scope still require a SNARF revision in compliance with SEMI Regulations.

Many of these items were previously authorized under SNARF 6929 – Line Item Revisions to SEMI E134 and SEMI E134.2. SEMI Regulations do not allow a Line Item Revision SNARF to be converted to a Revision SNARF, so this new SNARF is proposed.

SNARF 6929 will be abolished as this SNARF duplicates the proposed changes.

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, Addition of one or more Appendices or Complementary Files to an existing Standard or Safety Guideline, 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: 11/01/2022b. 1st Draft by: 01/01/2023
c. (Optional) Informational Ballot by: d. Letter Ballot by: 02/01/2023
e. TC Chapter Approval By:04/01/2023

_____________________________________________________________________________
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 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 E134 and subordinate standards 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 Revision.

__________________________________________________________________________
8. TC Member Review:
took place between (put dates below) before approval by the GCS, or

Member Review Start Date; 11/15/2022
Member Review End Date: 11/29/2022

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 GCS01/03/2023
Recorded in TC Minutes01/03/2023

__________________________________________________________________________

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