Dec 14, 2006

From STDFGroup

Jump to: navigation, search

STDF Scan datalog meeting Notes Date: 14 Dec 2006


Attendees:

Andreas Leininger - Infineon

Glenn Plowman - Qualcomm

Ajay Khoche - Verigy

Joe Sventon - Cadence

Phil Burlinson - Inovys

Mary Israni - BCS

Karl Ruetz - Soto Technologies


Agenda:

  1. New member introductions
  2. PR activities/contacts
  3. Requirements & Drafts discussions
  4. Next meeting


Minutes:

New Members:

  • Following new members joined the working group
    • Karl Ruetz: Soto Technologies
    • Phil Burlinson \- Inovys
    • Joe Swenton – Cadence (For Tom Jackson)

PR Activities:

  • we may need to do some PR to spread the message out and have broader reach.
  • Jana Knezovich from Verigy will coordinate any PR activities for the group and will close the loop with PR contacts in the member companies.
  • WG member to provide PR contact information to Ajay and Jana

Requirements and Draft discussions

  • Started reviewing the Infineon, Verigy & Mentor draft
  • The Group agreed on the following attributes to be the guiding principles while developing the standard.
    • *Data sufficiency*: Provide ability to store "raw" data as well as all the necessary data for the downstream diagnosis tool to perform its function.
    • *Data Efficiency*: Right data with minimum overhead
    • Low/No manufacturing Throughput impact: To reduce the size of data necessary to convey the requisite information
    • *Data Integrity*: Provide means to check for data validity, to perform data synchronization and to uniquely identify a data set.
    • *Flexibility*: So that multi\-tool, multi\-vendor environment can be supported
    • *Ease\-of\-adoption*: To enable fast adoption through easy integration with IT


  • The current focus is on discussing requirements. The WG discussed the classes of information that need to be stored. The group agreed that classes in the proposal cover the required information. Detail discussion on the items in each of those classes to continue in the future meetings
  • Suggestions/requirements:
    • *Number of fail cycles to be logged*: The standard should not limit the number of fail cycles as millions of cycles may need to logged now and also in future. Multiple GDR records can be used to overcome the size limitation of a single GDR record.
    • *Test identification*: We may need to store references to original STIL file
    • *Bit storage convention*: STDF has a way to indicate binday storage format (little endian vs Big endian)
    • Standalone Fail information structure: The issue is whether to replicate some of the information e.g. operating temp, voltage in the diagnosis fail records to make it standalone or have the tools get the information from the other records in STDF.
    • Standalone structure allows storing the fail information in their own IT servers(diagnosis database v/s full production database) which will allow efficient accecss to the tools that only need to use this information and not care about the rest of the STDF information
    • The downside of the replication is the extra validation for consistency in the tools that deal with both records.
    • Efficiency of the flow to enable volume diagnosis where up to 100K dice may need to be diagnosed a day needs to taken into account before making any decision. Efficiency discussion should include the FTP efficiency as well.
    • Use cases:
    • (Qualcomm) Production logging not possible for all the dice. All production data is stored for sampled dice. .5 G is the data limit for the partner tools. GZIP on the STDF binary data does not yield high compression (max 5:1). Parametric data compresses better up to 10:1
  • No decision was made in the group and will be taken for discussions in the next meeting.


Next Meeting:

  • In view of Christmas and New year's holidays, the next meeting is schedule to be on Jan 11^th^ at 8.00AM PST.
    • Same conf call number
    • Ajay to send invitation for the web conferencing before the meeting


Action Items Update:

  • Send the Wiki and email information to the group (Ajay) \- Done
  • Get the Inovys proposal and make it available to the group (Ajay) – Inovys is considering sharing the draft.
  • Review the draft proposals (All) – On going activity
  • Get other important players in the working group (Ajay) – Got Inovys, Synopsys and Yield Dynamics to join soon.


New Action Items:

  • Review the draft proposals and focus on the requirements. Collect the requirements from your own company or your customers in case of vendors. - All
Retrieved from "http://stdf.nanoisi.com/index.php/Dec_14%2C_2006"
Views
Personal tools