SEMI International Standards
Standards New Activity Report Form (SNARF)
Revised (if Applicable):
Revision to SEMI E134-0319 Specification for Data Collection Management
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.)
1) Higher Data Collection Frequency
Using the current trace data collection techniques, where collected data samples are collected and reported one at a time, the data collection frequency is limited to about 40 Hz. For some data collection applications, much higher frequencies are needed. This can only be accomplished by allowing data to be cached at a low level, and then reported in batches.
2) Move items from E134.1
A few items that are currently in E134.1 should have been in E134. For example, the details on specifying SEMI object items for data collection. These must be moved into E134.
3) Changes related the protocol change
As part of supporting HTTP/2 in the EDA Standards with gRPC and Protocol Buffers, some changes may be required to SEMI E134 to accommodate new better ways of organizing information.
Note that initially SNARF 6437 was approved to submit this as a line item ballot with 1 and 2. However, while creating the ballot it became apparent that the line item ballot was too long and complicated. Therefore the same changes are proposed as a major revision ballot.
b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information:
Anyone implementing EDA that upgrades to the next version
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:
This proposal suggests updating E134 as follows:
1) Add a new type of trace request and report that allows for higher speed data collection by caching the data at a low level and reporting the data as an array. We are calling this a “cached data sample” request and report.
2) Copy items from E134.1 into E134 which really belonged in E134 in the first place. For example, the explanation about the syntax for SEMI objects items in a data collection plan.
3) Make any changes as necessary as related to the protocol changes that are under development in other ballots. Allow changes to support and best leverage HTTP/2 integration with gRPC and Protocol Buffers, and general interface improvement. For example:
a. Update InvalidInterval class to include an invalidInterval attribute to report the trace interval specified that is not valid. The class currently reports just ValidInterval, which is the valid trace interval closest to the requested interval.
b. Update InvalidGroupSizeForInterval class to include invalidGroupSize attribute to report the group size that is not valid. The class currently reports just ValidGroupSize, which is the smallest groupSize value allowed for the requested IntervalInSeconds.
c. Consider splitting the DCPConsumer interface into two interfaces.
The ballot will also include any minor editorial changes and technical errors identified during the ballot creation.
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.)
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 at the TC Chapter Meeting, 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: