DoD Vision for Unique Item Marking

1. Unique Identification (UID)of Tangible ItemsMarch 16, 2004Defense Standardization Program ConferencePresented by: Rob LeibrandtDeputy Program Manager, UID

2. DoD Vision for Unique Item Marking To implement a policy establishing a strategic imperative for uniquely identifying tangible items relying to the maximum extent practical on international standards and commercial item markings and while not imposing unique government data requirements. Uniquely identified (UID) tangible items will facilitate item tracking in DoD business systems and provide reliable and accurate data for management, financial, accountability and asset management purposes. 2

3. EID 12V194532636 Orig. Part No. 1P1234 Serial No. S786950 Unique IDentification (UID) of Items is: . . . the set of data for tangible assets that is globally unique and unambiguous, ensures data integrity and data quality throughout life, and supports multi-faceted business applications and users. UID is . . . 3

4. UID & Network Centric Collaboration Industry Unique Identification People Item Location Enterprise Data Network Centric Collaboration U.S. Agencies & External Governments(e.g., UK, Australian, Canadian, Dutch) 4

5. Financial Management Property, Logistics, and Transportation 0001AA Bolt, Restraining, Rotorhead 4 ea $158.55 NSN 6625-99-617-9491 Line Item DoD Budget Submission Requisition Appropriations 2132020.00000 5X-6X20 123456.00000 662G 25POLI P68EY78945J145 POLI25 123456 Shipping Notice 2132020.00000 5X-6X20 123456.00000 662G 25POLI P68EY78945J123 POLI25 123456 Requirement Lines of Accounting Transportation Commitment Delivered Item Inspection Receiving Obligation Contract Acceptance Expenditure Enterprise UID Digital Data Flow Potential Need Property Log Acquisition 5

6. UID Role - Business Enterprise Architecture Enhance the Business Enterprise Architecture Enhance Total Asset Visibility Clean Audit Opinions on Property, Plant and Equipment & Operating Materials and Supplies 6

7. Defining the Scope of UID 7

8. Require the UID Which Items Require a Unique Identifier (UID)? 8 14

9. UID Construct #21 EID 12V194532636 Orig. Part No. 1P1234 Serial No. S786950 Create and Generate the UID • BUSINESS RULES • The UID shall be derived from its discrete component data elements. The UID is not required to be marked on the item as a separate data element.* UID Construct #11 EID 17V0CVA5 Serial No. S786950 UID Construct #1 D1 0CVA5786950 UID Construct #2 UN1945326361234786950 IAC CAGE + Serial No. IAC DUNS Orig. Part No. Serial No. 1 This example uses MH10.8.2 Data Identifiers. *If the enterprise chooses to mark the UID as a discrete data element on the item, the component data elements must also be marked on the item as discrete data elements, in addition to the UID. 9

10. Formats: Text Element Identifiers: [)>RSDDGSMFR 0CVA5GSSER 674A36458RSEoT EAN.UCC: Application Identifiers [)>RS05GS800406141411A0B9C3D6RSEoT MH 10.8.2: Data Identifiers [)>RS06GS17V0CVA5GS1P1234GSS786950RSEoT UID Collaborative Solution Issue • Using the syntax of ISO/IEC 15434, the collaborative solution provides for three interoperable formats: (2-digit numeric format code requested of SC 31 to replace DD) 17V0CVA5 1P1234 S786950 • Until SC 31 assigns a format code for use of TEIs use interim DoD format code “DD” in ISO/IEC 15434 syntax 10

11. Interoperable UID Programming Algorithm (1st DRAFT) 21 Construct the UIDUID = 01 + 21 Read Code 21, 8004, 8003, 8002 8004 Transfer the UID to AIS 05 Constructed UID equivalent (GIAI) 8003 Constructed UID equivalent (GRAI) 8002 Constructed UID equivalent (ESN) 18S Add the IAC for CAGE to Form the Complete UID Read Code 18S, 25S, S, I, 22S, 1B, or 5B Read Format Code 06 25S Constructed UID 17V or 12V Transfer the UID to AIS Construct the UIDUID = IAC + 17V/12V + 1P + S Read Code 17V, 12V, or 18V S Construct the UIDUID = 18V + 1P + S 18V Indicates UID Construct #1 I Constructed UID equivalent (VIN) Indicates UID Construct #2 22S Indicates a UID that requires only the addition of the IAC Constructed UID equivalent (ESN) Indicates a UID equivalent 1B Constructed UID equivalent (GIAI or GRAI) 5B Constructed UID equivalent (GRAI) SER Construct the UIDUID = IAC + MFR + SER Read Code SER, USN, or UCN Transfer the UID to AIS USN DD Add the IAC for CAGE to Form the Complete UID UCN Construct the UIDUID = IAC + SPL + UCN Issue: AIT devices/Computers must be able to distinguish between formats. Impact: Interoperable reading of alternative syntax codes. 11

12. Leveraging UID Data Capture/Use User Systems Design, Development and Manufacture Level 1 Processes Disposal/ Sale/ Change of Ownership Inspection/Acceptance/ Receipt Transportation MRO Configuration Mgmt Requirements Mgmt Supplier Mgmt Procurement Inventory Mgmt Manufacturing Part Marking Assembly Packaging Distribution/Shipping Inspection Acceptance Receiving Payment Validation Loading Hauling Tracking Unloading Inventory Mgmt Repair Upgrade/Modification Preventative Maintenance Failure Analysis Inventory Mgmt Part Marking/Remarking Configuration Mgmt Consumption Demilitarize FMS Intra-gov’t transfer Inter-gov’t transfer Scrap Level 2 Processes Mark Scan Populate Ship Notice Populate DID/CDRL Populate CM system Populate Registry Update Inventory Update Inventory Populate Trans. Doc. Update Registry Update Inventory Update Maint. DB Update CM system Update PM system Update Registry Update Inventory Record in PM system Level 3 UID Transactions 12

13. Use Cases • Failure Reporting/Analysis & Targeted Repair (Reactive and Predictive) • Recall or Latent Defect Resolution • Maximizing Capability While Minimizing Logistics • Reliability studies to determine best equipment available • Tracking and redirecting as necessary in route • Planned Maintenance • Repair • Supplier Performance • Parts (end items and spares) • Logistics support 13

14. Contract Award Determine what items need to be marked Determine mark method and location Create MBOM and MPP Make Item Functional Inspect Buy Item Subcontract SOW with UID Requirements Receive Inspect & Store Retrieve from Stock Record UID, Integrate into end Product Mark Item, Capture UID(s) Record UID Data Delivery Requirements Final Inspection Ship, DD250 MBOM – Manufacturing Bill Of Materials MPP – Manufacturing Process Planning UID Vendor Perspective Issue: Existing marking processes must be able to accommodate UID requirements. Impact: Existing investments in marking infrastructure are leveraged. 14

15. UID in the Supply Chain Product Data Supply Chain Unique Items UID ** Item Markings Enterprise UN194532636200H0028003896 EI 194532636 PN 200H0028 SN 003896* Prime PN 200H0028 Delivery to Govt End Item Specs End Item Item Markings EI 040535536 PN 210H0611 SN 006392* UN040535536210H0611006392 Tier 1 PN 210H0611 Delivery to Govt Subassembly Specs Spares Item Markings EI 080907280 PN 216H1439 SN 020890* Tier 2 PN 216H1439 UN080907280216H1439020890 Delivery to Govt Component Specs Spares Item Markings EI 083949107 PN 218H2861 SN 105742* Tier 3 PN 218H2861 UN083949107218H2861105742 Delivery to Govt Part Specs **UN = Issuing Agency Code for DUNS * Serialized within the part number using DUNS UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number 15 Spares

16. UID Registry • The UID registry will serve as an acquisition gateway to… • Identify what the item is • Identify who owns the item originally • Identify the initial value of the item • Identify procuring activity and acceptance timing • Intersect with other systems (e.g., property management, logistics, inventory management) • Enable chaos; embrace multiple UID equivalents; allow multiple standards to thrive • The UID registry will not… • Track where the item is • Track who uses the item • Track on-going configuration management 16

17. End Item Data (15) UID (Concatenated) Descriptive Data UID Data Elements (5) Item Description Unit of measure Acquisition Data Contractor Contract Number CLIN/SLIN/ELIN Price Acceptance Code (identifies acceptor) Acceptance Date Ship to code Embedded Items of End Items (10) UID (Concatenated) Descriptive Data UID Data Elements (5) Item Description Unit of measure Parent UID as of delivery date GFP flag UID “Pedigree” Data Item Tracking (TBD) • Current parent • “As of” date 17

18. Contractor Contracting Officer Document Creation Financing Acceptance DCAA Voucher Approval DFAS Accounting Systems TransportationSystems DFAS Pay Systems LogisticsSystems PropertySystems Other Systems UIDRegistry CCR/DAASC EDA DCMA Office Source Inspection & Acceptance Wide Area Workflow Receiving Activity Destination Acceptance Local Processing Program Mgmt. Property Mgmt. Transporters Pay Official Logisticians Payment Processing Document Certification View Only View Only View Only Depot/Destination Receiving ANSI X12 EFT WAWF with UID Web, EDI, and FTP “Intake” 18 Email notices sent to next workflow user

19. Standardizing Item Description Brand Name Performance Specification Specific Item General Item Unknown Item Manufacturer’s Part Number Standard Description (e.g. NSN) Form, Fit, Function Performance Requirements Business Intelligence Use Commercial Registries as Source of Description (e.g. UCCNET) Map Commercial Items to Standard Descriptions (e.g. RosettaNet, UNSPC) Use In-House Registry Item Identification Methodology Increase Competition in Production Increase Use of Commercial Descriptions 19

20. UID Policy Implementation Timeline Policy • Final UID policy (Implementation effective Jan 2004) - July 2003 • UID Clarification - Nov 2003 • Issuing Agency Code (IAC) policy - Dec 2003 • UID Implementation for Contracts with Govt Furnished Property - Jan 2005 DFAR Cases • Advanced Notice of Public Rulemaking released - May 2003 • Public Meeting - May 2003 • Interim Rule Published - Oct 2003 • Public Meeting - Nov 2003 • Rule clarification (2nd Interim Rule) - Dec 2003 ISO 15434 Change Request • Submit “New Work Item Proposal” - Jan 2004 • Gather change request support - ongoing • ISO 15434 amendment issued - TBD WAWF Modifications • UID Capability IOC – Firm Fixed Price -2 May 2004 20

21. ISO Policy Update • Submitted proposal to US TAG Sept 03 • Withdrawn based on discussion with DoD Logistics AIT Office • US TAG strategy was to forward to ISO while not supporting the request • Debate must happen in US TAG before going to international community • Developing support • Meetings with AIA leadership on US TAG (US TAG still has little aerospace representation) • Met with Embassy staffs (Sweden, France, UK, Italy, Korea, Germany) • Briefed 21-member nation MOU group • Met with Canadian MOD and SC-31 representatives – Nov 17 • Met with GSA/DOE/UCC/FAA January 13 to synchronize U.S. Government wide-strategy • Mr. Mike Wynne met with AIA commercial suppliers to address marking interoperability issues- Jan 14 • Proposal resubmitted January 28 for US TAG meeting on March 2, 2004 (SC 31, May 18-20, 2004) • Secured agreement from ATA, AIDC committee to recommend acceptance of ISO wrapped TEIs within ATA Spec 2000 21

22. HOW YOU CAN HELP! • Support the Workforce • Learn • Inform • Engage • Enable • Become Proponents for Global UID Interoperability • ATA & ISO Standards Involvement • Share Implementation Experiences • Honestly Engage in Identifying and Solving Issues 22

23. DoD Stakeholders OSD All Services Joint Staff Defense Contract Management Agency Defense Logistics Information Service UK MoD Industry Stakeholders Aerospace Industries Association (AIA) Government Electronics Association (GEIA) Uniform Code Council (UCC) Air Transport Association (ATA) Various AIT suppliers New York City Transit Authority UK Council for Electronic Business Key DoD & External UID Stakeholders UID background materials and actions items are available www.acq.osd.mil/uid 23

24. Contact Information For further information or questions, please contact: • Ms. LeAntha Sumpter at LeAntha.Sumpter@osd.mil or at (703) 681-7564 • Mr. Robert Leibrandt at Robert.Leibrandt@osd.mil or at (703) 695-1099 A variety of UID background materials and previous UID policy memos can be found at www.uniqueid.org Note: For inquiries regarding the standards effort, please contact Lt Col Gregory Redick at gregory.redick@dcma.mil, (201) 393-3273 24

25. Backup Slides

26. UID Constructs The components that make up the UID are identified in the table below. Each enterprise has two options for creating the UID. 26

27. CAG*, MFR or SPL DUN* EUC* SEQ* PNO* * * USN or UST Create and Generate the UID • Data qualifiers (semantics) will define each machine-readable data element marked on the item. • The data qualifier associated with the serial number will identify which UID construct is used to build the UID. Semantics Translation Between Data Identifiers (DI), Application Identifiers (AI), and Text Element Identifiers (TEI)1 * Pending approval or publication • Blank boxes indicate the need for updates to the standards. 27

28. UID Receipt and Acceptance Process Issue: Existing marking processes must be able to accommodate UID requirements. Impact: Existing investments in marking infrastructure are leveraged. 28