Item Unique Identification (IUID) - Update Defense Logistics Management Standards Office (DLMSO.IUID@dla.mil) October 19, 2016

ADC 1198 – Establishing and Maintaining Accountability for Service Owned Capital Equipment Stored at DLA Distribution Centers   Approved by ODASD (SCI) on October 6, 2016 Defines procedures to exchange serial number and unique item identifier (UII), when available, to support Financial Improvement and Audit Readiness (FIAR) compliance and accountability over service owned capital equipment stored at DLA Distribution Centers In the scope of this change, the following DLMS transactions require notification to DOD Component automated information systems (AIS) with serialized data: 527R Receipt (527R with 1/BR02/020 Transaction Type Code D4) 867I Issue 842A/W SDR Submission 842S/Q Storage Quality Control Report 846R Location Reconciliation 856R Shipment Status Materiel Returns 856S Shipment Status 945A Materiel Release Confirmation 947I Inventory Adjustment

At the September 15, 2016 DoD IUID Working Group meeting: Draft PDC 1244 – Revisions to DLMS Business Processes Supporting Management of Controlled Cryptographic Items (CCI) and Radiation Testing and Tracking System (RATTS) Items under DOD IUID Policy Scope is Service owned CCI/RATTS assets stored at DLA Distribution Centers CCI falls under DODM 4140.01, Volume 11 policy that directs that CCI will be inventoried by UII. Different from capital equipment which did not fall under DODM 4140.01. At the September 15, 2016 DoD IUID Working Group meeting: Army proposed changes to the DoD Integrated Requirements Set for IUID in Supply Business Processes to establish visibility for Service Owned Unique Item Tracking (UIT) Assets Stored at DLA Distribution Centers Army indicated RATTS UIT items (which include imbedded items with serial numbers) require no special DLMS processing. PDC 1244 will leverage ADC 1198 transactions/procedures FLIS IUID indicator Y, in combination with FLIS UIT Designator AAC (RATTS) and AAH (CCI) identify assets subject to PDC 1244 Under development; initial draft for SCI review estimated for early November

Integrated Requirements Set Potential Gaps List Disposition Services processing and required IUID Registry reporting iRAPT property transfer (GFP registry) processes and use of DLMS transactions via GEX mapping to update the Registry Life cycle event reporting and DLMS. Future work on definitions and determine level of detail needed Inventory by IUID for select items (DSS impact) Harmonizing GFP IUID reporting with non-GFP IUID (use of DLMS transactions/mapping at GEX) IUID/serialization requirements related to UIT programs Inter-Component IUID/serialization requirements (i.e. Army Total Package Fielding)

Draft ECP – Item Owner for Legacy Items Problem – IUID Registry records do not often have the asset owner identified, making it difficult to determine IUID populations by Service/Owner Solution: WAWF pull asset owner info from contract receipt and include that info in the data feed to IUID Registry. Benefits: Since the bulk of IUID Registry records are created upon contract receipt, and the contract has owner info available, having WAWF include the owner data element to IUID Registry updates is the most efficient way to populate this field in the Registry. The field already exists in the IUID Registry.

Serial Number Overview Bottom Line Up Front: Inform stakeholders about the issues with serial number field length/characteristics and facilitate information sharing Background: Not all serially-managed/IUID-required items have been marked; these items may be provided to contractors as Government-furnished property (GFP) WAWF/iRAPT Engineering Change Proposal (ECP) 0796 developed to add functionality to capture and transmit multiple serial numbers for property transfers involving non-UII’d serially-managed GFP Goal is to facilitate GFP tracking by serial number in the IUID Registry

Serial Number Formatting iRAPT: Serial number data field defined with two different field lengths Current: 30 characters represents value used for creation of the UII, no special characters (except hyphen and slash), no spaces Proposed: 50 characters for non-UII, with special characters/spaces IUID Registry: Mirrors above: 30-character serial number required for creation of birth record Optional human readable mark allows 50 mixed character serial number with special characters including spaces MIL-STD 130: Serial number used to construct UII, 30 characters with hyphen and forward slash; no specific guidance on human-readable field length and special characters DLMS IUID and Unique Item Tracking (UIT): Intent to capture human readable serial number; 30 characters, hyphen and slash allowed Small Arms/Light Weapons (SA/LW) legacy transactions: Serial number restricted to 11 characters; SA/LW Registry rules differ on special character use

Common X12 data elements for serial number DLMS Impact Selected DLMS transactions cannot accommodate the expanded field length without remapping or upgrading to a higher X12 version Common X12 data elements for serial number X12 Data Element Min/Max 4010 Min/Max 4030 LIN03 Product/Service ID 1/48 REF02 Reference Identification 1/30 1/50 N902 Reference Identification

DLMS Impact (continued) Multiple DLMS logistics transactions already upgraded to 4030 to support IUID: Shipment Status Shipment Status Materiel Returns Materiel Release Confirmation Inventory Adjustment Supply Discrepancy Report Storage Quality Control Report There is a programming cost for mapping changes or upgrade to higher version if necessary for remaining DLMS transactions associated with IUID procedures Receipt Issue SA/LW Reporting Others depending upon requirements

Serial Number Standardization No overarching guidance from authoritative source Inconsistency between iRAPT and DLMS guidance Field length Characteristics Which serial number: human readable or value used for creation of the unique item identifier (UII) iRAPT Status: In the interest of moving forward with ECP, iRAPT will restrict the field length at 30 characters (pending SCI policy) DLMSO requested IUID WG review and SCI documented guidance for standardization/harmonization across Components and business processes

Questions?