SEMI International Standards
Standards New Activity Report Form (SNARF)
Revised (if Applicable):
New Standard: Specification for Counterfeit Prevention for the Electronics Manufacturing Supply Chain
Originating Global Technical Committee:
Originating TC Chapter:
Task Force (TF) in which work is to be carried out:
Single Device Traceability Task Force
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.)
There is no room for uncertainty in the genealogy of electronic parts that are part of just about everything we use. There are security, health and safety and brand value issues at stake. It should always be possible for stakeholders to query the genealogy of a part to verify its authenticity. This requirement is often addressed in specific supply chains by custom solutions driven by the final part manufacturer. It would be less expensive and more robust to have an industry wide solution which would also address the counterfeit risk downstream from the part manufacturer through a distributor and reseller network.
b. Estimate effect on industry.
1: Major effect on entire industry or on multiple important industry sectors - identify the relevant sectors
Sector or Company Information:
Any member of the supply chain including foundries, assembly and test, and printed circuit board assembly.
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:
The standard will define the immutable and secure recording and authentication of “assets” as they flow between members of an electronics manufacturing supply chain. An asset is any item of value shipped between one business entity in the supply chain and another. The term “assets” includes, but is not limited to, wafers, raw die, strips, trays, MCM and single die packages and PCBs.
It is expected, but not required, that the standard will be based on the Blockchain and HyperLedger open source technologies to record the chain of custody between business entities in the supply chain.
The standard will not define how the assets are processed within a business entity in the supply chain, or what materials and other assets they contain. This standard will, however, be aligned with other standards that do address these topics.
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:
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 and scopes as needed.)
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):
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
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):
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:
took place between (put dates below ) before approval at the TC Chapter Meeting, or
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. (Refer to
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: