1 / 26

Global AIDC - Novi, MI - 23 August 2007

Global AIDC - Novi, MI - 23 August 2007 by: Craig K. Harmon, President & CEO Q.E.D. Systems Odette Presentation Company coding - situation today There is a clear need coming up for unique company coding in automotive applications for: RFID Parts marking Labelling of packaging

Télécharger la présentation

Global AIDC - Novi, MI - 23 August 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. Global AIDC - Novi, MI - 23 August 2007 by: Craig K. Harmon, President & CEOQ.E.D. Systems

  2. Odette Presentation

  3. Company coding - situation today • There is a clear need coming up for unique company coding in automotive applications for: • RFID • Parts marking • Labelling of packaging • Engineering Collaboration • and more • There are also several identification schemes in use, under review or proposed for the future that could be combined: • UPIK • PID • OFTP2 – security certificate exchanges • EDI messages • License Plate/Container Id

  4. Odette Company Coding – what are the ideas? • Scope of the service (I) • An Issuing Agency Service for company coding • Odette will deliver a solution which meets the requirements of Auto ID/RFID (License Plate, labelling, parts marking), OFTP, EDI and UPIK/PID. • An information service which allows access to detailed and up to date info (like UPIK) about business partners (This is probably where the main investment has to be made)

  5. Odette Company Coding – what are the ideas? • Scope of the service (II) • Odette will provide the guidelines for the information exchange of partner related data using EDI, XML or web services. • The solution will build on a centrally maintained database using globally recognised formats. • All data will be held securely

  6. Odette Company Coding – what are the ideas? • Data formats • Will be based upon the UPIK/PID structure. (T.B.C.) • Pricing • One price list • Administration • The Service will normally be directed through the NOs for European companies and through the CO for companies outside of NO territories. • Other regional automotive organisations could become part of the system

  7. Benefits of Odette compared to DUNS • Organisational/commercial aspects • Odette is neutral, non-profit • Odette could act globally as one single entity • Odette could maintain only one central database, this means more correct data and a more efficient maintenance procedure • User aspects • Flexible identification of business entities/locations (DUNS based on legal entities only) • The Odette code is shorter than the DUNS code • One source for company coding for several purposes (labeling, business information etc) • Odette could offer “Yellow Pages Services” • Odette could also offer automated partner data exchange services (EDI/XML)

  8. Business Case • Business Case – individual companies • There is a real need for unique identification • Odette can offer value-added services in addition to the code. • Business Case – automotive industry in Europe • Maintain control of automotive data formats • Future funding source for common sector projects through Odette (CO and NO.s) and even global projects provided other regional organizations would promote the concept

  9. ODETTE EUROPE • IAC of “OD” • One of 17 issued 2 character IACs (as of 2007-05-01) • Company Identification Number (CIN) is defined as 4 an (providing over 1.6 million unique company coding structures)

  10. A Prefatory Comment This is not a proposal to adopt GS1 and EPC data structures

  11. Current AIAG Conventions • Varying means by which to identify suppliers • DUNS number • Customer assigned identity of supplier • Customer assigned part number • Aids at receiving dock of customer • Adds to supply chain complexity when a single product is supplied to and marked for multiple customers • With shipping labels or labels applied when customer is known, this may not have been an issue, but with direct part marking the issue is more pronounced

  12. Global Identification • Need for globally unique automotive industry identity • Need for globally unique manufacturer identity • Need for globally unique part number • Need for globally unique serial number or lot/batch/heat number

  13. Need for Technology Neutral Metadata • Issuing Agency Code • Registration authority • Code length • Code character set • Company identification number (CIN) • Assigned by Issuing Agency • Code length • Code character set • Product code • Assigned by manufacturer • Code length • Code character set • Potential for “comprised of” and “component of” • Potential for form/fit/function generic and image • . . .

  14. Identification of Manufacturer • Identity of manufacturer to follow Odette’s four (4) character alphanumeric format • Each country/region responsible for their own management

  15. Identification of Product • Automotive industry begins to phase in the use of supplier part numbers • Automotive industry agrees to sunset the use of customer part numbers by 2010 • All part numbers are 10 characters (an) in length • Between 2007 and 2010, automotive industry begins the process of crossing referencing customer part numbers to supplier part numbers • UN/EDIFACT “PRICAT”/“ORDRSP” • ASC X12 “832”/“855” • Industry database

  16. Data compaction • 4 character (an) supplier code + 10 character (an) product code = 14 characters (an) • An encodable character set of 36 possible values (0-9 and A-Z) can be achieved in 6 bits (26 = 64 possible values) (better compaction schemes are possible) • 14 x 6 = 84 bits • Presuming a popular RF tag size of 96 bits, a non-optimized compaction, as noted above, would permit 212 = 4096 values for other uses, e.g. serial numbers. Optimizing compaction would significantly increase the availability of additional values.

  17. Industry Database • Cross-reference only • Catalog • eCommerce Portal • If trading partners were to agree on a different data structure, e.g. GS1 or EPCglobal, those structures could be supported as well

  18. Possible Cross Reference Function

  19. JAI / Database Function • Board comprised of two representatives of each country/region member, plus JAI chairman and database administrator • Common annual CIN fee, example $USD1500.00 • 75% to country/region member for marketing and education • 25% to database maintenance firm

  20. Issuing Agency Codes1 IACs A – J shall be reserved for organisations which are allocated a single character code. These organisations shall, in addition to the criteria for approval as set out in 4.2.1, meet the following criteria: 1) be multi-national and be represented in all of the national members countries of ISO/IEC JTC 1/SC 31; 2) have official external liaison status with ISO/IEC JTC 1/SC 31; 3) be a not for profit organisation; 4) have a formal, long term relationship with at least five thousand license plate issuers. —— 1 ISO/IEC 15459-2, §5.5a

  21. Automotive Industry Global Requirement • IAC to identify joint automotive industry under one umbrella (JAI) to meet the requirement for a single alpha identifier (“A” for automotive”??) • Each country/region to identify suffix to JAI • AC = China • AE = Europe • AJ = Japan • AK = Korea • AN = North America • All members agree to 4 character (alphanumeric) CIN

  22. Application to RA • Identify that there are CIN companies in each of the SC 31 member countries • Establish liaison between JAI and SC 31 • Apply for single character IAC, ask for “A”

  23. Questions ???

  24. Thank you !!!

More Related