SEMI International Standards
Standards New Activity Report Form (SNARF)
Revised (if Applicable):
Line Item Revision to E142-XXXX: Specification for Substrate Mapping, E142.1-1016 XML Schema for Substrate Mapping and E142.2-1016 SECS II Protocol for Substrate Mapping
Originating Global Technical Committee:
Information & Control
Originating TC Chapter:
Task Force (TF) in which work is to be carried out:
Advanced Backend Factory Integration
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.)
Adding package path to layout - E142 provides a framework to describe the hierarchical layout of complex electronic assemblies. In many cases, multiple packages are assembled on a substrate, e.g. a wafer or a strip, that is later singulated to yield the functional part to be sold or assembled into a larger package. It is helpful to know which layout paths in the hierarchy represent an individual functional package, for example to allow a fail bin for one die in a multi-chip package to cause the entire package to be marked with a fail bin. This line item will add an attribute to the layout object to identify it as a package or not
Review the data model, XML examples and schema – There are some inconsistencies between the data model and the schema and the XML examples belong in the sub-document E142.1 alongside the XML schema rather than in the parent E142 document related information sections.
Comply with the Style Manual - SEMI E142 uses words that contradict the latest version of the Style Manual. (for example, use the word ‘must’ rather than ‘shall’). Changes to align with the latest version of the Style Manual will be made
Extending data transfer methods – With the addition of DeviceData to E142 the map data size may become too large for the SECS II messages defined. An alternative method will be proposed to use Stream 21 SECS-II messages to transfer maps.
b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information:
Packaging, Testing, Backend automation
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:
• To add package path to the layout. The schema in E142.1 and the XML examples in E142.2 will be updated to synchronize with the changes.
• Review and update E142 and E142.1 related information.
• SEMI E142 uses words that contradict the latest version of the Style Manual. (for example, use the word ‘must’ rather than ‘shall’). Changes to align with the latest version of the Style Manual will be made
• SEMI E5 supports Stream 21 messages to transfer data between the Host and Equipment. E142.2 will be updated to allow Stream 21 messages to transfer maps to and from the host. A new configuration switch will specify which mechanism (Stream 21 messages or S14F1/F2 and S6F11 messages) will be used to transfer maps.
• Make minor editorial changes and technical errors 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 as needed.)
Information & Control Global Technical Committee, Automation Technology Global Technical Committee, 3D Packaging and Integration Global Technical Committee
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 (see 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. (See
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: