SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 01/08/0218Revised (if Applicable):

Document Number: 6348
SNARF for: Revision to E30-0418: Specification for the Generic Model for Communications and Control of Manufacturing Equipment (GEM)

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

There are three categories of changes proposed to be made. Because the changes affect numerous text throughout the document, it seems best to tackle all of these changes as a major revision ballot.

1. E30 was created long before current SEMI regulations and procedures were developed and as a result E30 does not comply with current SEMI requirements.

a. Requirements are not allowed in footnotes; one appears in each of the footnotes: 18, Table 3 #3, and Table 8 #1.

b. Requirements are not allowed in the Limitations; in fact two are in 3.1. See the Procedure Manual Appendix 3-4.

c. Requirements are not allowed in definitions. One appears in 5.1.1.

d. Requirements are not allowed in Notes. One appears in Note 16 and one in Note 19

e. The word “must” appears almost 100 times throughout this document.

Most of the time, it is used in the sense of a requirement. Although this is not encouraged (see Style Manual Table 4-4), it might take considerable effort to properly replace it with shall. “Must” is also used several times in its other senses: as a strong recommendation or as a logical/necessary consequence. To avoid confusion, I recommend that the word be replaced, where used in these senses, with another word or phrase as suggested in the following paragraphs (there may be others):
i. 6.3 From: should be considered ‘must’ reading; To: should be read.
ii. 11.4.1 From: must precisely implement the GEM Process Program Management to be; To: that precisely implements the GEM Process Program Management is considered to be.
iii. A1-1.4 From: It must be verified; To: The operator should verify
iv. A1-6.1 From: A host system must have a view; To: A host system needs a view (Review all the paragraphs in A1-6, since this is just an Example).
v. A1-7.2.3.1 From: but the machine must be checked; To: but the machine needs to be checked.

f. Many of the definitions in the Terminology section do not follow the Style Manual (see 1-16, 1-27, & 1-28). In particular, a number of them start with: A [term] is [or other verb]…. This phrase should be deleted.

g. The second sentence in 7.7.3.1.4 is not actually a sentence.

h. For consistency, the definition in 7.9.2.1 should be in 5 and reference to it made here, as is done elsewhere.


2. Additionally, several issues have been reported.

a. The term DVID is not used but should be.
This has caused periodic confusion for readers.

b. S7,F17 confusion.
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, not for n>1.
(E30 assumes n=1)

c. The event “Operator Equipment Constant Change” requires ECID as data variable. ECID is missing in section 5.2 DVVAL’s.

d. The event “Operator Command Issued” requires OperatorCommand as data variable. OperatorCommand is missing in section 5.2 DVVAL’s.

e. The terms Data Values and Status Values are generally disliked, yet are used interchangeably with Data Variables and Status Variables.a E37 spec, section 5.6 state transition table. The state change for transition #6 should really be NOT SELECTED to NOT CONNECTED as shown in Figure 1. (instead of NOT CORRECTED)

f. In 9.2.2 it states, “There is a time limit on how long an entity is required to remain in the NOT_SELECTED state before entering the SELECTED state or by returning to the NOT CONNECTED state.” This sentence is a bit misleading and seemingly contradicts 9.2.2.1. It is not a time that the entity is “required to remain” but it is the time limit the entity is “allowed to remain.” Section 9.2.2.1 does clarify that it must transition to NOT CONNECTED if the T7 timeout is exceeded. While this text has been in place a long time and we have all done what is supposed to be done I feel that it would be nice to fix the text.
g. Where; 7.3.1.4.4.2 Host initiates Collection Event Namelist Request.

What: Please see following red underlined comment.
To be: COMMENTS should “Host Initiates CENR” instead “Host Initiates DVNR”.


3. Finally, it is proposed to remove RaP from E30 due to disinterest.





b. Estimate effect on industry.
4: Slight effect or effect not determinable
Sector or Company Information:

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:

All issues listed in section 1a above are expected to be addressed in the ballot, plus any other items identified that violate current SEMI regulations or procedures. Any obvious mistakes in the current text found during editing will also be corrected without changing implementation requirements.


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:
Specification

Miscellaneous (describe below):

___________________________________________________________________________
3. Projected Timetable for Completion:

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

_____________________________________________________________________________
4. Liaisons with other Global Technical Committees/TC Chapters/Subcommittees/TFs:
a.
List 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 as needed.)
Global I&C TC

b. 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:
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):
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:



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:
A copyright release letter has already been obtained by SEMI from the copyright owner.

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

Member Review Start Date; 01/12/2018.
Member Review End Date: 01/26/2018.

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. (See Regulations 8.2.1)
__________________________________________________________________________

9. SNARF Approval Dates:
TC Chapter or GCS04/11/2018
Recorded in TC Minutes

__________________________________________________________________________

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


Attach Pictures and Files here: