SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 10/20/2016Revised (if Applicable):

Document Number: 6092
SNARF for: New Standard: Specification for Centralized User Authentication and Role Authorization Management (CUARAM)

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.)
Increasing process steps due to the complexity of semiconductor process require so many equipment groups to support required process steps.
In addition, increasing production volume of semiconductor factory for cost reduction requires so many same (or similar) equipment in each equipment group used in parallel in order to achieve required throughput of the factory.
On the other hand, security and safety managements of equipment have been becoming so crucial.
This results with a lot of work to manage required number of human users on such a big number of equipment.
- Registration, Role setting, Qualification setting, etc.

To reduce this work load, “Centralized User Authentication and Role Authorization Management scheme” is expected to be standardized.

Note 1: As described in 5.1.5, SEMI E132 refers only to the authentication of application processes, and does not support or address authentication of human users.

Note 2: This SNARF is raised based on the observations and assumptions from equipment supplier.
As there is no other formal place or way to ask necessity for the industry, this SNARF is proposed to see device manufacturers’ opinions first.


b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information: User management of Semiconductor Industry

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 document covers following functions which support Centralized User Authentication and Role Authorization Management.
- User management
--- such as registration of Username, Password, Roles, Qualifications, and other required user information
- User authentication service
--- such as authentication service of a user upon a request from equipment
- Role management (Security (user role in organization) aspect)
--- such as definition of user Roles in the factory, registration and service of equipment type specific Role definitions
- Qualification management (Safety (user ability in technical work) aspect)
--- such as definition of user Qualifications (handling licenses such as toxic gas, liquefied nitrogen, vacuum subsystem, etc.) in the factory, registration and service of equipment type specific user Qualification definitions
- Equipment Mode definition
--- such as Production or Maintenance to be used for modification of permission per Equipment Mode
- Permission management
--- such as registration and service of equipment specific Role-Permission Descriptor per equipment type
- Access log service
--- such as a log with login in/out date, time, and equipment
- Other related functions which support above functionalities

b: Expected result of activity
New Standard or Safety Guideline (including replacement of an existing Standard or Safety Guideline)

For a new Subordinate Standard, identify the Primary Standard here:




For Standards, identify the Standard Subtype below:
Specification

Miscellaneous (describe below):

___________________________________________________________________________
3. Projected Timetable for Completion:

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

_____________________________________________________________________________
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
EISS 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:
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:


b. For Revision, Reapproval, Reinstatement, or Withdrawal of existing 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:



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

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

Member Review Start Date; 10/05/2016
Member Review End Date: 10/18/2016

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 GCS10/21/2016
Recorded in TC Minutes10/21/2016

__________________________________________________________________________

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