SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 12/17/2015Revised (if Applicable): 06/16/2016

Document Number: 5973
SNARF for: Line Item Revision to SEMI E170-0416: SPECIFICATION FOR SECURED FOUNDATION OF RECIPE MANAGEMENT SYSTEM (SFORMS) and SEMI E170.1-0416: SPECIFICATION FOR SECS-II PROTOCOL FOR SECURED FOUNDATION OF RECIPE MANAGEMENT SYSTEM

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

___________________________________________________________________________
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 Doc. #5888 was published as SEMI E170-0416. And, through its application studies, documentation quality issues (such as editorial errors, explanation/readability insufficiencies, and technical consistencies) and minor technical issues are being reported. Those issues should be improved.


b. Estimate effect on industry.
4: Slight effect or effect not determinable
Sector or Company Information: Factory Automation of Semiconductor Industry

c. Estimate technical difficulty of the activity.
I: No Difficulty - Proven concepts and techniques exist or quick agreement is anticipated

___________________________________________________________________________
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:
Per rationale, improve document quality issues and technical issues found.
Such as:
- Put prefix which indicates Standard-defined Mnemonic to Security Class etc.
- Introduce incremental implementation steps to the compliance table
- Introduce Standard-defined type to TypeID


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

For Standards, identify the Standard Subtype below:
Specification

Miscellaneous (describe below):

___________________________________________________________________________
3. Projected Timetable for Completion:

a: General Milestones
a. Activity Start: 12/17/2015b. 1st Draft by: 02/28/2016
c. (Optional) Informational Ballot by: d. Letter Ballot by: 04/30/2016
e. TC Chapter Approval By:06/30/2016

_____________________________________________________________________________
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.)
Global Information & Control Technical Committee
NA GEM300 TF
Korea GEM300 TF
Taiwan GEM300 TF

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:


If "patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s) " is selected above, then also check one:


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:
will NOT include reproduced copyrighted material



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:
None.

__________________________________________________________________________
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 GCS12/18/2015
Recorded in TC Minutes12/18/2015

__________________________________________________________________________

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