SEMI International Standards
Standards New Activity Report Form (SNARF)
Revised (if Applicable):
Line Item Revision to SEMI E5-0219: Specification For SEMI Equipment Communications Standard 2 Message Content (SECS-II)
Originating Global Technical Committee:
Information & Control
Originating TC Chapter:
Task Force (TF) in which work is to be carried out:
GEM 300 Task Force
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. When a host first connects, it cannot know the current GEM data collection setup.
a. There is no SECS-II message to identify the current list of defined report IDs and whether each report can be deleted or not.
b. There is no SECS-II message to identify the list of reports linked to each collection event and whether the link can be deleted or not.
c. There is no SECS-II message to identify the list of currently defined trace request and the list of VIDs for each trace request.
d. There is no SECS-II message to query Spooling configuration.
2. The terminology for Data Variables, Status Variables and Equipment Constants is sometimes confusing and should be consistent with E30 as clarified in ballot 6348.
3. S7,F17 defines a list with n elements to delete n PPs. S7,F18 answers with ACKC7.
ACKC7 = 4 (PPID not found) works for n=1, but not for n>1. (E30 assumes n=1). Clarification needed.
b. Estimate effect on industry.
1: Major effect on entire industry or on multiple important industry sectors - identify the relevant sectors
Sector or Company Information:
Anyone implementing or using GEM
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 E5 as follows:
1) Add SECS-II messages to fill the gaps of missing information with regards to reports, report to collection event links, trace requests and spooling configuration.
2) Make changes to clarify the terminology related to Data Variables, Status Variables, and Equipment Constants like ballot 6348.
3) Clarify message S7,F17 and F18 to be clear when n>1. Consider a new stream & function.
The ballot will also include any minor changes identified during the ballot creation.
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
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
the use of patented technology is NOT required.
If "patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s) " is selected above, then also check one:
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)
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:
is not required for this SNARF.
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: