1. UID Breakout Session Bruce Propert bruce.propert@saalt.army.mil

2. UID Critical Issues

3. Critical Issues  UID Registry Concept Definition –Brainstorming Session –Integrate with Logistics, Property, Finance, and Acquisition  Data Capture –Develop a strategy to build support for data capture requirements in relation to other initiatives  Enabling an Integrated Digital Environment with Industry for Government Furnished Property –Brainstorming Session with AIA –Industry Collaboration Meeting (AIA, GEIA. NDIA, other Industry Assns.)  UID End to End Process –Data and Process View –Systems View  Coordination of Military and Intra-DoD Emerging UID Policies  Development of Program Strategies for Deployment to Legacy

4. UID Registry People Registry Places Registry Assets Registry (Things) Keys Services Registry Groups Registry GFP Asset Registry Events Registry Property Accountability Equipment Parts Materials UID Registry The UID Common Key AcquisitionFull Cost Accounting The UID Common Key The UID Common Key (The Rules) FMS Country DMLS Master Property Plans Depots Parent Child Parent Child Top Level Second Level Lower Levels

5. UID and the Network and Information Integration (NII) Initiative

6. NII Vision Power to the Edge People throughout the trusted, dependable and ubiquitous network are empowered by their ability to access information and recognized for the inputs they provide. Three goals: –Build the net –Populate it –Protect it

7. Net-Centric Enterprise Services Support real-time & near-real-time warrior needs, and business users

8. A Net-Centric DoD  An engineered, DoD-wide infrastructure (robust, COTS-based, sustainable environment) supporting:  Faster application implementation –Fewer dollars for application integration  (Technical) ability to access the data you need anytime and anyplace –Less dependency on others and/or software to “find” or translate information  Collaboration –Better understanding of how to collaborate effectively –Tools that meet organizational needs  Shortened timelines between recognizing the need for change and integrating a new capability into the operational force (agility) –IT isn’t the long-pole on organizational change/implementing new capabilities

9. RFID/UID Process Integration

10. UID and RFID Integration PriorityTask #Task Description 1Develop a joint set of RFID & UID scenarios/trigger events separate from the RFID-unique events 2Explore additional refinements to re-engineering of receipt, inspection, acceptance & pay to add RFID requirements & explore architecture solutions for the scenarios 2aExplore value in capturing RFID data traceability as part of WAWF requirements 3Develop a tighter integration between MIL-STD-129 and -130L 4Scenarios need to address nesting of shipment data 5Develop an integrated data flow to connect UID to RFID. Goal is to streamline RFID adoption by industry 6Explore solutions & business rules to operationalize the above 2004 Actions – Supplier Focus 1 1 2 3 3 3 1

11. Integration of MIL-STD-129 & -130 & Defense Transportation Regulation Concerns  Intersection with engineering and configuration management - Confusion introduced with UID – Design Agent versus Manufacturer  Not a guaranteed data environment - PM discretion widely applied  Human readable requirements unconstrained  Some examples are confusing: -130 is not strategic but focuses on tactical  Separating policy, policy source, guidance: need integration across receipt, inspection, acceptance and pay process Ideas  Need to design new “to be” process - Consistent use of enterprise identifier & part identifying number  Standardize vendor flow down - Establish Joint govt/industry working group)  Move Guidance from -130 to DFAR Clause  Recognize & rationalize interests of Property, Packaging & Configuration Management stakeholders: Involves warehousing, transportation, and maintenance

12. DFARS

13. FAR/DFAR Spiral 1/04 2/04 3/04 4/04 5/04 6/04 7/04 8/04 9/04 10/04 11/04 12/04 January ‘05 Dec 04 June 04 Final Rule Interim DFARS Rule UID 2003-D081 Proposed DFARS Rule Final Rule RFID Final Rule Proposed DFARS Rule August 04 UID Wide Area Work Flow Proposed DFARS Rule UID Legacy Govt Property Final Rule August 04 May 04 Final Rule FAR 45 and 52 re-write Proposed FAR Rule Oct 04 Dec 04

14. Commercial Products and UID UID Required  Explore UID equivalent possibilities  Explore application of the physical marks by –Prime contractor –Government  Outsource marking capability No UID Required  Commercially acceptable mark required

15. Embedded UIDs Step 1 – Systems engineering, logistics, program management experts identify items requiring UID* Step 2 – UID migration strategy is negotiated with contractor Step 3 – UID is an enabler to integrate configuration management, supply chain, maintenance etc. information *Consider Plant-wide Single Process Initiative

16. Item Marking, Reading, Scanning

17.  Marking Standards Update  UID Equivalents Process  Interoperable UID Algorithm  UID Process Views –Vendor Perspective –Receipt & Acceptance

18. Problem: Solution: Seek incorporation of Text Element Identifiers in ISO/IEC 15434  28 January 2004 – DoD New Work Item Proposal submitted to the U. S. TAG specifically asks a new format code be added to ISO/IEC 15434 to support the use of Text Element Identifiers  Request was made specifically to facilitate the Department's UID initiative and bring about interoperability in the marking of tangible items with its aerospace suppliers. AREADoD UID POLICYATA SPEC 2000 SyntaxUses ISO/IEC 15434 headers, separators and trailers for unambiguous message string – no ambiguity Only uses field separator in message string – ambiguity exists for beginning and end of message Marking Standards Update Issue: Will Defense aerospace companies use the DoD interim format code of “DD” or a new format code if approved by JTC1 Subcommittee 31? Impact: Might eventually require redundant marking of some items also sold to commercial customer by aerospace suppliers.

19. UID – Unique Identification MI&R – Materiel Inspection & Receiving Biennial review of continued need for UID equivalents Identifier is nominated by sponsor Verification that identifier meets equivalence criteria UID Equivalent approved for use/ continued use UID Equivalent description posted to UID Web Site UID Type assigned to Equivalent in MI&R* Report Nomination submitted to: Mr. Robert Leibrandt OUSD(AT&L)/DPAP Room 3C128 3620 Defense Pentagon Washington, DC 20301 robert.leibrandt@osd.mil DoD UID Equivalents – Process Steps

20. DoD UID Equivalents – Criteria Criteria for Determining DoD UID Equivalence  Must contain an enterprise identifier, which is assigned by a registration or controlling authority  Must uniquely identify an individual item within an enterprise identifier, product or part number  Must have an existing Data Identifier (DI) or Application Identifier (AI) listed in ANSI MH10.8.2, Data Identifier and Application Identifier Standard

21. Identifiers Meeting the Equivalence Criteria  Global Individual Asset Identifier (GIAI), EAN.UCC (Application Identifier: 8004; Data Identifier: 1B)  Global Returnable Asset Identifier (GRAI), EAN.UCC (Application Identifier: 8003; Data Identifier: 1B or 5B)  Vehicle Identification Number (VIN), ISO 3779 (Data Identifier: I)  Electronic Serial Number (ESN, for cellular telephones only), TIA (Data Identifier: 22S; Application Identifier: 8002) Issue: None Impact: Enables the use of existing unique identifiers in commercial use. DoD UID Equivalents

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

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

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

25. End To End Process

26. Leveraging UID Data Capture/Use Level 1 Processes Level 2 Processes Level 3 UID Transactions Systems Design, Development and Manufacture Inspection/ Acceptance/ Receipt Transportation/ Transfer of Ownership M,R&O Disposal/ Sale Configuration Mgmt Inventory Mgmt Manufacturing Part Marking Assembly Packaging Distribution/Shipping Inspection Acceptance Receiving Payment Validation Loading Hauling Tracking Unloading Inventory Mgmt Property Mgmt X-fer Ownership Repair Upgrade/Modification Preventative Maint. Failure Analysis Inventory Mgmt Marking/Remarking Configuration Mgmt Consumption Demilitarize FMS Intra-gov’t transfer Inter-gov’t transfer Scrap Populate Registry Update Inventory Update Registry Update Inventory Record in PM system Update Registry Update Inventory Update Maint. DB Update CM system Update PM system Mark Scan Populate Ship Notice Populate DID/CDRL Populate CM system Update PM system Update Inventory Populate Trans. Doc. User Acquisition Requirements Requirements MgmtSupplier Mgmt Procurement Inventory Mgmt Contracts Mgmt Identify UID itemsSolicitations Contracts Trace-ability

27. Systems Engineering

28. Systems Engineering Guidance  Updating list of Government/Industry standards, handbooks, DoD Acquisition Guide, and Data Item Descriptions that affect UID.  Working guidance issue with GEIA on GEIA Handbook 649 –Projected completion in December 2005 unacceptable –Estimated cost to pay for the rewrite also considered excessive burden on the government

29. Level 1 Processes Level 2 Processes Level 3 UID Transactions Systems Design, Development and Manufacture Inspection/ Acceptance/ Receipt Transportation/ Transfer of Ownership M,R&O Disposal/ Sale Configuration Mgmt Inventory Mgmt Manufacturing Part Marking Assembly Packaging Distribution/Shipping Inspection Acceptance Receiving Payment Validation Loading Hauling Tracking Unloading Inventory Mgmt Property Mgmt X-fer Ownership Repair Upgrade/Modification Preventative Maint. Failure Analysis Inventory Mgmt Marking/Remarking Configuration Mgmt Consumption Demilitarize FMS Intra-gov’t transfer Inter-gov’t transfer Scrap Populate Registry Update Inventory Update Registry Update Inventory Record in PM system Update Registry Update Inventory Update Maint. DB Update CM system Update PM system Mark Scan Populate Ship Notice Populate DID/CDRL Populate CM system Update PM system Update Inventory Populate Trans. Doc. User Acquisition Requirements Requirements MgmtSupplier Mgmt Procurement Inventory Mgmt Contracts Mgmt Identify UID itemsSolicitations Contracts Trace-ability Leveraging UID Data Capture/Use in the Systems Engineering Environment

30.  Work with GEIA on the prior process model resulted in the following matrix of UID policy impact areas: Process AreaMandatory Considerations Optional Considerations Manufacturing, Assembly and Part Marking72 Requirements Management71 Supplier Management43 Configuration Management33 Inventory Management43 Packaging, Distribution and Shipment30 Repair and Preventative Maintenance22 Modification and Upgrade21 Failure Analysis12

31. Maintenance

32. UID Maintenance Implementation Description of Effort  Define a methodology for implementing UID in the maintenance environment.  Operate as a sub-group to the Maintenance Senior Steering Group (MSSG) (JRIB-UID Charter).  Briefing to Service logisticians at MTSSG, January 7, 2004.  Taskers to Services/Depot Activities signed by Mr. Mason to provide feedback assessment of capabilities to institute UID by January 2005. (Manufactured items only).  MPP&R as part of UID and RFID implementation is working to coordinate and facilitate depot maintenance actions.  MPP&R reports back to JRIB-UID depot maintenance status.

33. Deliverables/Timeline/Status  Services/Depots Activities assessments – February 2004  Initial Depot Maintenance IPT – March 9, 2004 –ICW UID Workshop  Quarterly reports of Depots UID efforts will be provided to JRIB  Depot Activities Implement UID – January 2005 –Manufactured Items Only  Approved Logistics Decision/Policy Memorandum – TBD  Depot Activities Implement Full-up UID of all candidates – TBD UID Maintenance Implementation

34. Next Steps

35. Communication and Outreach  Currently working on a more comprehensive communication and outreach plan –Improve international involvement with regular, focused conference calls to educate and increase presence of UID –International UID communication and outreach to date or planned: UK Canada Korea Australia  US-based industry and professional associations are engaged  Efforts are underway to reach international associations  How can the JRIB members help promote communication and outreach? Sweden France 21 Nation Memorandum of Understanding (MOU) Group

36. UID Policy Implementation Timeline Communication and Outreach Events  Implementation Working Group (IWG) Conference Call- 25 February 2004  National Defense Industrial Association (NDIA) Panel Discussion- 01 March 2004  Association for Automatic Identification and Mobility (AIM) Conference- 09 March 2004  Defense Logistics Management Standards Office (DLMSO) MILS Conference- 09-10 March 2004  UID International Conference Call- March 2004  UID Industry Roundtable- March 2004  DoD RFID Summit for Industry 2004- April 2004  UID Industry Forum- April 2004  MoD/DoD Discussions – UID Collaboration- April 2004 A summary of all past communication and outreach events is available on the UID website: www.uniqueid.org

37. SubGroups

38. Four UID Breakout Groups  UID Readers, Printers, Scanners –Language of the Mark –Acquisition Infrastructure –Hardware  Systems Engineering/Configuration Management  Draft UID Legacy Equipment Policy  Receipt/Accept/Inspect/Pay Process Re-engineering