1 / 38

UID Breakout Session

UID Breakout Session. Bruce Propert bruce.propert@saalt.army.mil. UID Critical Issues. Critical Issues. UID Registry Concept Definition Brainstorming Session Integrate with Logistics, Property, Finance, and Acquisition Data Capture

conway
Download Presentation

UID Breakout Session

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.

E N D

Presentation Transcript

  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. The UID Common Key The UID Common Key The UID Common Key UID Registry (The Rules) UID Registry Top Level Second Level People Registry Places Registry Assets Registry (Things) Keys Services Registry Groups Registry Events Registry Lower Levels Acquisition Property Accountability Equipment Parts Materials Full Cost Accounting GFP Asset Registry Parent Child Master Property Plans Parent Child DMLS FMS Country Depots

  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. COI’s COI’s DoD(Title 10) IC(Title 50) Business Domains National Intelligence Domain Warfighter Domains Users Users IC Org Spaces Domain/ COI Capabilities Battlespace Awareness Command & Command Installation & Environment Human Resource Management Strategic Planning & Budget Force Application Protection Precision Logistics Acquisition Logistics Accounting & Finance Levels of Services Above Core Level Warfighter Lead Business Lead ICSIS Community Space Storage User Assistant Messaging IA/Security Application IA/Security ESM ESM Discovery Collaboration Mediation Enterprise Service Management (ESM) Technical Infrastructure Domain IA/Security IA/Security IA/Security IA/Security IA/Security IA/Security IA/Security ESM ESM ESM ESM ESM ESM Core Enterprise Services (CES) Transformational Communications (TC) & Computing Infrastructure 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. 1 1 1 2 3 3 3 UID and RFID Integration 2004 Actions – Supplier Focus

  11. 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: Involveswarehousing, transportation, and maintenance • 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 Integration of MIL-STD-129 & -130 & Defense Transportation Regulation

  12. DFARS

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

  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. Item Marking, Reading, Scanning • Marking Standards Update • UID Equivalents Process • Interoperable UID Algorithm • UID Process Views • Vendor Perspective • Receipt & Acceptance

  18. Marking Standards Update 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. 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. DoD UID Equivalents – Process Steps 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 Nomination submitted to: Mr. Robert Leibrandt OUSD(AT&L)/DPAP Room 3C128 3620 Defense Pentagon Washington, DC 20301 robert.leibrandt@osd.mil UID Equivalent description posted to UID Web Site UID Type assigned to Equivalent in MI&R* Report UID – Unique Identification MI&R – Materiel Inspection & Receiving

  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. DoD UID Equivalents 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.

  22. Interoperable UID Programming Algorithm 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 Add the IAC for CAGE to Form the Complete UID DD 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.

  23. 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.

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

  25. End To End Process

  26. Leveraging UID Data Capture/Use User Disposal/ Sale Inspection/Acceptance/ Receipt Transportation/ Transfer of Ownership Systems Design, Development and Manufacture Requirements Acquisition M,R&O Level 1 Processes Configuration Mgmt Inventory Mgmt Manufacturing Part Marking Assembly Packaging Distribution/Shipping Requirements Mgmt Supplier Mgmt Procurement Inventory Mgmt Contracts Mgmt 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 Level 2 Processes Mark Scan Populate Ship Notice Populate DID/CDRL Populate CM system Identify UID items Solicitations Contracts Trace-ability Populate Registry Update Inventory Update PM system 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

  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. Leveraging UID Data Capture/Use in the Systems Engineering Environment User Disposal/ Sale Inspection/Acceptance/ Receipt Transportation/ Transfer of Ownership Systems Design, Development and Manufacture Requirements Acquisition M,R&O Level 1 Processes Configuration Mgmt Inventory Mgmt Manufacturing Part Marking Assembly Packaging Distribution/Shipping Requirements Mgmt Supplier Mgmt Procurement Inventory Mgmt Contracts Mgmt 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 Level 2 Processes Mark Scan Populate Ship Notice Populate DID/CDRL Populate CM system Identify UID items Solicitations Contracts Trace-ability Populate Registry Update Inventory Update PM system 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

  30. Leveraging UID Data Capture/Use in the Systems Engineering Environment • Work with GEIA on the prior process model resulted in the following matrix of UID policy impact areas:

  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. UID Maintenance Implementation 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

  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

More Related