SEMI International Standards
Standards New Activity Report Form (SNARF)
Date Prepared: 04/02/2019Revised (if Applicable):

Document Number: 6518
SNARF for: New Standard: Specification for Rich Interactive Test Database (RITdb)

Originating Global Technical Committee: Automated Test Equipment
Originating TC Chapter: North America
Task Force (TF) in which work is to be carried out: Rich Interactive Test Database (RITdb)
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.)

Many vendors in the ATE industry have adopted the SEMI Standard Test Data Format (STDF) for storing test result data, so much so it has become the de facto standard in the ATE industry. The STDF format was designed by Teradyne to address the lack of test result data compatibility between test systems. As this is a problem between systems of different manufacturers as well, the entire industry moved to STDF as the standard test data format.

The STDF was developed for storing test data results from semiconductor testers and trimmers. As the semiconductor industry has evolved, there is increasing need to store and manage additional data related to the test process. The proposed activity aims to establish a compact, flexible, and economical data format that can accommodate the advanced test environments of today as well as those to be defined in the future.

The resulting standard aims to enable the following capabilities:
- Allow data from multiple producers to be merged and synchronized and then delivered to consumers by ensuring portability, provenance and security
- Suitable for consumption in real-time on the test cell, as a near real-time streaming format across a network, and as a mass storage medium
- Support extending with new data types while maintaining backward compatibility with the existing format
- Simple to generate on test cells of differing complexities
- Integrate economically with legacy tools that do not natively support the RITdb specification
- Compatible with existing formats such as G85, E142 and STDF
- Use a modern high-performance, royalty-free, open format that does not require special tools to generate and consume



b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information: ATE users and equipment manufacturers

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:

Activities will include the development of the following contents:
- Standard Test Data Format (STDF) to RITdb translator
- Real Time worksheet demo
- Equipment Inventory implementation
- E142 Map to RITdb demo
- Contactor tester implementation
- Diag/Verify Prototype
- Stream and rule checking prototype/demo
- Board Tracking Application
- Analytics


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

_____________________________________________________________________________
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 as needed.)
None

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 (see Procedure Manual 7):


c. Intercommittee Ballots:
will be issued – identify the recipient global technical committee(s):

Identify the recipient global technical committee(s):
Automation Technology, 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:
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:
the incorporation of Copyrighted Item will NOT be required



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:

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

Member Review Start Date; 04/10/2019.
Member Review End Date: 04/24/2019.

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/29/2019
Recorded in TC Minutes

__________________________________________________________________________

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

Attach Pictures and Files here: