SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 03/29/2021Revised (if Applicable):

Document Number: 6803

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 E179 defines common Protocol Buffers elements that are not specific to a single standard and are common across multiple SEMI standards using Protocol Buffers. 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 Line Item Revision will investigate some opportunities for performance benefits when sending parameter values using SEMI E179 Protocol Buffers messages, as well as defining a consistent way of reporting error exceptions from gRPC methods.

Several individuals have asked about serializing Protocol Buffer messages to file and extracting it. A common scenario is to support message logging (recording messages sent over a gRPC connection). Protocol Buffers messages do not contain descriptions of their own types. Given a raw message serialized to a file, it is difficult to extract useful data without knowing the corresponding .proto file used to define the message type. This Line Item Revision will investigate and develop a standardized way to serialize Protocol Buffers messages specified by SEMI Standards to a file and retrieve it. This procedure could be used to support the following scenarios:
- Implementations who wish to record Protocol Buffers messages sent and received from software applications.
- Record metadata from the equipment and share it with external software applications without the need to translate the data into a different format can be serialized to a file, and then converting it back again. (For example, results from SEMI E125 operations could be serialized to file, and a different implementation could read the data and process it as if it had come from the equipment

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:
This Line Item Revision will investigate:

Potential performance improvements on transferring parameter values. SEMI E179 defines Protocol Buffer Messages to represent parameter data (with various data types). Changing the structure of the Protocol Buffers messages could result in better performance transmitting the data over gRPC.

When an error occurs, gRPC methods can return a Remote Procedure Call (RPC) exception. Investigate a consistent way to provide error information using trailer gRPC metadata infrastructure when raising exceptions to the calling code from gRPC methods defined in SEMI Standards. This infrastructure could include information captured in the SEMI E179 Error structure (such as specify Source, Code, Description, and Extension information).

Protocol Buffers messages serialized to file are not self-describing (no information included that describes what the raw data represents). Implementing code needs to know the specific Protocol Buffer message that is serialized so that it knows how to deserialize it. Investigate a procedure to serialize / desearlize Protocol Buffers messages defined for SEMI Standards. This could include specifying a new Protocol Buffers message that identifies what Protocol Buffers message is serialized next in the file, and the data length of the message so that the implementation knows how much data to pull off the file stream and how to parse it.

b: Expected result of activity
Line-item 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

For Standards, identify the Standard Subtype below:

Miscellaneous (describe below):

3. Projected Timetable for Completion:

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

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.)
(Refer to SEMI Standards organization charts and global technical committee charters as needed.)

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:
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 no 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 FORthe 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 FORwill incorporate Copyrighted Item’: A copyright release letter must be obtained from the copyright owner prior to publication.

7. Comments, Special Circumstances:

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

Member Review Start Date; 4/15/2021
Member Review End Date: 4/29/2021

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 GCS05/18/2021
Recorded in TC Minutes


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

Attach Pictures and Files here: