SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 12/16/2020Revised (if Applicable):

Document Number: 6704
SNARF for: Line Item Revisions to SEMI A3-0819 SPECIFICATION FOR PRINTED CIRCUIT BOARD EQUIPMENT COMMUNICATION INTERFACES (PCBECI)

Originating Global Technical Committee: Automation Technology
Originating TC Chapter: Taiwan
Task Force (TF) in which work is to be carried out: Printed Circuit Board Equipment Communication Interface (PCBECI) 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 A3 is an equipment communication interface standard for printed circuit board (PCB) manufacturing. It is based on the SEMI SECS/GEM communication specification, taking into consideration the automation needs of the PCB industry. Some functionality of the SECS/GEM has been limited to simplify data management and communication procedures.

Implementers have identified some gaps and contradictions which should be corrected to ensure a consistent application of the specification so systems can communicate with each other.



b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
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:
The following gaps and issues have been identified and will be addressed in the ballot:
A) Section 9.3.3.1 states: [A003.00-RQ-00007-00] The supplier shall document when data values (DVVALs) are current and valid. A comma-separated list of DVNAMEs is required for each CEID to show what DVVALs are current and valid at the occurrence of the event. [/RQ]

If the implementer chooses XML as the electronic format (as allowed for by RQ-00006), the format of this list will not be comma-separated. For example, if the documentation is compliant with SEMI E172.

One potential way to address this is to specify if an implementer chooses XML as the electronic format, this will be a list of DVNames entries. If you are using a different electronic format, then this will be a comma-separated list of DVNAMEs.

B) In Table 3 – Data Variables, it lists the Data Variable ALID.

The data variable should be defined as AlarmID to be consistent and include a comment to indicate when the DV is valid. (for example, something like ‘This DV shall be updated with the contents of AlarmID of the associated alarm at the occurrence of either AlarmDetected or AlarmCleared events’).

C) In Table 5 - SEMI E30 Defined SECS-II Messages not Required in PCB Equipment, it lists the following item:
S7F29/30 (Process Program Verification Inquire) – HSMS required

SEMI A3 requires the S7F29/F30 message, so this item needs to be deleted from Table 5.

D) Section 8.1 states: [A003.00-RQ-00002-00] PCB equipment shall provide an implementation of the application layer compliant to SEMI E37.1 (HSMS-SS). For some simple PCB equipment to transfer small amount of data purpose, PCB equipment may provide an implementation of the application layer compliant to SEMI E4 (SECS-I) only. [/RQ]

The intention is that it is a SEMI A3 implementation can support just support SEMI E4. The current requirement can be reworded to make it clear that it does not have to provide a SEMI E37.1 implementation.

E) Section A1-2.1, requirement A003.00-RQ-90002-00 uses the NA (Not Applicable) option, but it is not defined in the standard. It needs to be defined (for example, in other standards such as SEMI E173 it is defined)


The ballot will also include any minor editorial changes identified during the ballot creation plus items identified that violate current SEMI regulations or procedures.

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:
SEMI A3

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: 01/01/2021b. 1st Draft by: 03/01/2021
c. (Optional) Informational Ballot by: d. Letter Ballot by: 04/28/2021
e. TC Chapter Approval By:10/01/2021

_____________________________________________________________________________
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.)
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 be issued – identify the recipient global technical committee(s):

Identify the recipient global technical committee(s):
Information & Control
___________________________________________________________________________
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):
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:
the incorporation of Copyrighted Item will NOT be required



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:
is not required for this SNARF.

Member Review Start Date; 2021/01/01
Member Review End Date: 2021/02/28

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/25/2020
Recorded in TC Minutes12/25/2020

__________________________________________________________________________

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