1 / 38

Overview of IUID Enabled SIM Supply PRC SDR Subcommittee Meeting 28 April, 2011

Overview of IUID Enabled SIM Supply PRC SDR Subcommittee Meeting 28 April, 2011. Kathy Smith ODASD(SCI). Agenda. Goals and Scope of Workshop JLB Task Force Recommendations Workshops Policy IUID Game Plan. 2. 2. JLB Task Force Analysis (April 2010). NWRM. Classified Items. CSI.

coy
Download Presentation

Overview of IUID Enabled SIM Supply PRC SDR Subcommittee Meeting 28 April, 2011

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. Overview of IUID Enabled SIMSupply PRC SDR Subcommittee Meeting28 April, 2011 Kathy Smith ODASD(SCI)

  2. Agenda Goals and Scope of Workshop JLB Task Force Recommendations Workshops Policy IUID Game Plan 2 2

  3. JLB Task Force Analysis (April 2010) NWRM Classified Items CSI Sensitive Property Book GFP MEV MDAP Tooling RCM / CBM Warranty Mgmt Configuration Mgmt Product Recall Counterfeit Parts Functional Requirements Intensive Item Management (IIM) Validated Requirements IIM -- 198 PA -- 231 PLM -- 305 Systemic Requirements Property Accountability (PA) Benefits Value Product Lifecycle Management (PLM) Costs 3

  4. Implementation of JLB Task Force Recommendations - Workshops

  5. Outside of Workshop Scope IUID Marking IUID Registry Internal Maintenance Operations/Processes Internal Supply Operations/Procedures Packaging/MIL-STD-129 Labeling for IUID Requisitioning by UII 3 4 In scope…secondary inventory governed by DoD 4140.1-R 5 5 5 5 5

  6. Workshop Outcomes and Deliverables • Outcomes • Enhanced business processes using IUID to serially manage items in the DoD logistics domain • Enhanced data exchanges for IUID information across the DoD logistics domain • Deliverables • DoD-level policy/procedural updates • Guidebook for IUID Enabled Serialized Item Management for Supply and Maintenance • Proposed/Approved DLMS changes (data exchanges/business rules) • Serialized Item Management Integrated Requirements Set • 1st Volume will be Supply and Maintenance (6 nodes) • 2nd Volume will be inclusive of all 10 supply chain nodes 6 6 6 6

  7. Definition of Serialized Item Management By UII SIM by UII: Management and tracking of a select population of items that have a unique item level traceability requirement Unique item level traceability is defined as the requirement to trace lifecycle management events related to acquisition, property accountability, storage, operation, maintenance, safety, physical security, retirement, and disposal by each individual item “Individual item” is defined as a single instance of a stock-numbered item or a single assembly/subassembly The need for unique item level traceability requirement is determined by the manager of the item (materiel manager for consumables and PICA for reparables) Existence of a manufacturer’s serial number does not constitute a requirement for SIM…must meet at least one of the following: DoD serially-managed sensitive, DoD serially-managed critical safety, and/or DoD serially-managed pilferable items All depot-level reparable items Any items that the materiel manager or program manager decides require unique item level traceability In scope…secondary inventory governed by DoD 4140.1-R 7 7

  8. Definition of a DoD-Serially Managed Item An item of supply that has a unique item level traceability requirement, i.e. requires the capture and use of a unique item identifier during any lifecycle event related to acquisition, property accountability, storage, operation, maintenance, safety, physical security, retirement, and disposal by each individual item “Individual item” is defined as a single instance of a stock-numbered item or a single assembly/subassembly The need for unique item level traceability requirement is determined by the manager of the item (materiel manager for consumables and PICA for reparables) In scope…secondary inventory governed by DoD 4140.1-R 8 8

  9. Uses of IUID in Supply Processes • Receipt: Capture of UII(s) upon receipt enables traceability to physical location of goods as they travel through supply chain nodes. Receivers will collect the UII(s) from exterior packaging, validate them against the shipment status/notice, and store information in the appropriate business system. • Acceptance: Acceptance by UII(s) enables visibility and traceability to custodial changes. Upon acceptance, any discrepancies will be recorded by UII(s). • Store: Storage by UII is not required unless necessary to trace high intensity items in a facility. • Issue: Issuing materiel by UII(s) enables traceability to the physical location of the UII(s) as goods travel to a downstream supply chain nodes. Wholesale and below wholesale activities will respond to requests by NSN/Quantity (MRO, LRO, RDO) and provide the UII(s) upon issuing materiel. This enables notification • Inventory: Inventory by UII(s) enables synchronization and validation of owner and storage/managing activity records. The storage and/or managing activity will verify records by UII(s), and can provide history of balance affecting records by UII(s) to owners. Traceability throughout the supply chain Note: Procedures for assigning IUID Designator FLIS Codes are not finalized

  10. 4 7 8 1 5 2 6 RECEIPT USING IUID: DLA Distribution Center receives new procurement items by UII from the commercial vendor* Distribution Depots UID Registry Manufacturers/Suppliers WAWF sends UIIs to the UID Registry System will prompt user to collect AIT off the exterior of the package WAWF Supplier enters item UII into WAWF, along with other shipment info 3 WAWF sends advanced shipment notice to customer system, incl. the UII(s) (DLMS 856) DSS WAWF notifies supplier of acceptance via email Customer performs acceptance, sending a transaction back to WAWF (WAWF 861) Owner/ Manager DAAS All business events impacting high-intensity managed items will be communicated to the Owner/Manager(DLMS 527R & WAWF 861) *This depicts FOB Destination

  11. INVENTORY USING IUID: Wholesale and below-wholesale activities perform inventory Owner/Manager must verify reported UII against their record. Owner/Manager may request transaction history (DLMS 846P)for analyzing inventory discrepancies (WMS responds with the historical balance affecting transactions with all UII(s) included). UII mismatches require new reconciliation procedures between owner record and WMS accountable record. Owner/ Manager Inventories are initiated by the Owner/Manager sending inventory requests (DLMS 846P) to WMS (depot or local system accountable record), or by the WMS based on schedule or other requirement e.g., denial. Inventory line item will be defined as stock number + supply condition code + UII. 3 1 DAAS • When performing inventories, the WMS must verify, by physical location, all UII(s) against the accountable record and report differences to the owner/manager (DLMS947I) • Details for reporting UII differences to the owner/manager must be determined (e.g., when only UII has mismatches - no quantity or condition change)Mismatches on UII-- Causative research is required on any discrepancies found as a result of the inventory. 2 WMS or local system Wholesale or below-wholesale activity

  12. 2 6 5 4 7 1 Supply system ISSUE USING IUID: DLA Distribution Depots issue items to customers based on receipt of a Materiel Release Order (MRO) DLA Distribution Depot Maintenance Facility DSS will issue items by NSN and ensure that UII(s) are included on the exterior package label 3 “527R MRA” Maint. system DSS “856S” DLA will send a shipment status, incl. UII(s) to the customer (DLMS 856S) DLA will send a MRC or Issue (DLMS 945A/867I)with UII(s) to the owner/manager DAAS Recipient performs a receipt, sending a transaction back to the owner/manager via DAAS, incl. the UII(s) (DLMS 527R MRA); generate an SDR if discrepant All business events impacting high-intensity managed items will be communicated to the owner/manager (945A, 867I and 527R MRA) Owner/ Manager Service customer will send a requisition (DLMS 511R) for a quantity of an NSN (not by UII) to the owner/manager Owner/manager will send a MRO (DLMS 940R) to the DLA Distribution Depot

  13. Levels ofSupply Management Intensity Standard-intensity serialized management by UII Items that have a lifecycle traceability requirement, but do not require management by eaches on a daily basis Managed by UII in accountable records (storage activity) DoD serially managed items that are sensitive or pilferable or DoD serially managed critical safety items or depot level reparables High-intensity serialized management by UII Items with a lifecycle traceability requirement, that are “micro-managed” today Managed by UII in accountable records (storage activity) and owner records (ICP) Nuclear Weapons-Related Materiel (NWRM) FLIS code under development will enable standard and high intensity 13 13 13

  14. Standard-Intensity Serialized Management • Worldwide Inventory for owned materiel by NSN X and Qty • NSN X - Qty 2 Location: Supply Base • NSN X - Qty 1 Location: Maintenance Report Worldwide inventory by NSN as “Qty of 3” (527R) Owner/Manager Supply Base: Receipt, Store, Inventory and Issue for NSN X by UII Report UIIs shipped (856S) Accountable Records By UII Supply Activity Base 1 Report UIIs shipped (856S) Storage Activity Maintenance Base: Store UII at receipt, capture UII during repair action • Inventory by Qty (By UII is Optional) • Receipt, Store and Issue by UII Report UIIs shipped upon Materiel Return (856R) Maintenance Activity Base 2 Validate correct UII received, Resolve UII mismatches, discrepancies Mismatches are researched by UII 14 14 14 14 14 14

  15. High-Intensity Serialized Management Owner/Manager Records By UII • Worldwide inventory for owned materiel by NSN X and UII: • UII #1 Location: Supply Base • UII #2 & #3 Location: Maintenance Base Owner/Manager • Receive NSN X with Qty 3 • UII – #1 • UII – #2 • UII – #3 Daily reconciliation by UII on balance affecting transactions; resolve UII mismatches/discrepancies Report Worldwide Inventory by UII • Supply Base: Receipt, Store, Inventory and Issue for NSN X by UII: • UII-#1 Report UII shipped Supply Activity Base 1 Accountable Records By UII UID Materiel Report 2 UIIs shipped Storage Activity • Maintenance Base: Receipt, Store, Inventory and Issue for NSN X by UII: • UII #2 • UII #3 Receipt, Store, Inventory and Issue by UII Report UIIs shipped upon Materiel Return (856R) Mismatches are researched by UII Maintenance Activity Base 2 Validate correct UII received; Resolve UII mismatches, discrepancies ALL SUPPLY CHAIN NODES MANAGE AN ITEM BY UII 15 15 15 15 15 15

  16. Identifying IUID Items-Proposed IUID Indicator Code Assigned to each stock number (NSN) requiring SIM using the UII, as determined by the manager of the item (Materiel Manager, with recommendation from the Engineering Support Activity, for consumables and the Primary Inventory Control Activity (PICA) for reparables) Indicates the level of management intensity required for the individual items within each IUID-eligible NSN Standard-intensity serialized management by UII – managed by UII in accountable records High-intensity serialized management by UII – managed by UII in accountable records and owner/manager records Provides for an optional interim IUID Code … Applies to NSNs that require serial management by IUID but on which legacy assets on the NSN have not yet been IUID-marked Enables the supply activity to manage the item by the NSN with the legacy serial number in the interim until all legacy assets on the NSN have been marked with a UII Once the legacy assets on the NSN have been marked with a UII, the code values will be updated to full serialized item management using the UII 16 16 16 16 16

  17. Implementation of JLB Task Force Recommendations - Policy

  18. JLB IUID Task Force Conclusions BOTTOM LINE: Military & General Equipment: Current Policy Remains Secondary Inventory: Revise current IUID policy to focus on items with a unique item level traceability requirement

  19. IUID Memo for Secondary Items - Dec 2010IUID Policy Revision Clarification • Scope – DoD serially-managed secondary inventory: • Spare and repair parts that are serially managed by DoD • AA&E that are serially managed, but not managed only by lot • Small Arms • Depot Level Reparables (DLRs) • Other sensitive or pilferable or critical safety items that are serially managed by DoD • Other secondary items that require unique item level traceability • Unit acquisition price requirement: • $5000 threshold no longer applies for legacy secondary inventory • $5,000 threshold still applies to new secondary inventory (DFARS being updated to synchronize new and legacy item IUID policy)

  20. Draft DoDM 4140.01-M Policy MANAGEMENT OF CONTROLLED INVENTORY SPECIAL REQUIREMENTS MATERIEL PROGRAMS MATERIEL DATA MANAGEMENT AND EXCHANGE SUPPORTING TECHNOLOGIES MATERIEL RETURNS, RETENTION, AND DISPOSITION DELIVERY OF MATERIEL MAKE AND MAINTAIN MATERIEL SOURCING DEMAND AND SUPPLY PLANNING OPERATIONAL REQUIREMENTS • Draft DoDM 4140.01-M: • Provides guidance on supply chain materiel management • Reorganized from a single regulation to a multi-volume manual • Includes specific guidance on serialized management using the UII

  21. Draft DoDM 4140.01-M Policy Table of Contents

  22. Draft DoDM 4140.01-M Policy Content Changes • NWRM • Vol 1 & 11 • Physical Inventory • Vol 2, 3, 5, 11 • Comprehensive Inv Mgt Improv. Plan (CIMIP) • Vol 3, 6, 10 • Anti-Counterfeiting • Vol 1, 3, 6 • IUID • Vol 1, 5, 9, 11 • Disposal • Vol 1 & 6 • Metrics • Vol 10 • RFID • Vol 5, 7 • Destination acceptance • Vol 5 • Packaging • Vol 9 • GFP • Vol 5, 10 • Organic Support • Vol 3, 4 • Green procurement • Vol 2, 3, 4, 5

  23. Draft DoDM 4140.01-M Policy Volume 9 2. ITEM UNIQUE IDENTIFICATION (IUID) a. Required Procedures (1) In accordance with DoDD 8320.03 (Reference (h)), a unique item identifier (UII) shall be used for population of items that have a unique item level traceability requirement. (2) The primary purpose of UIIs is to enable more accurate engineering analysis and maintenance planning. Other functional areas may also benefit, including security, property accountability, safety, operational readiness, and warranty management. Instructions for constructing the UII are found in the “DoD Guide to Uniquely Identifying Items” (Reference (i)). (3) The DoD is transitioning from uniquely identifying items within an approved unique item tracking (UIT) program or serial number tracking (SNT) program to use of IUID for items identified in Volume 11 of this Manual as well as all items in approved serialized item management (SIM) programs. Previously approved UIT programs, such as the DoD Small Arms and Light Weapons Serialization and Navy Depot Level Reparable programs, shall continue under the purview of the Unique Item Tracking Committee, but should be transitioned to IUID management as soon as practicable. Use of local stock numbers in previously approved UIT programs will be discontinued. No additional UIT or SNT programs shall be approved.

  24. Draft DoDM 4140.01-M Policy (Vol. 9 continued) b. Implementing Procedures   (1) The DoD Components shall:  (a) Begin to transition from serially managing selected items using the manufacturer’s serial number to serially managing selected items using the globally unique and machine-readable UII (Construct #1 or #2 or acceptable equivalents) as defined in Reference (i). For unmarked existing items in inventory, installed, in use, or undergoing maintenance repair or overhaul, mark existing IUID required items as follows: 1. prioritize marking by most critical assets first: NWRM, critical safety items, sensitive, and pilferable. 2. mark items in inventory as criticality warrants it. 3. mark unserviceables only when inducted into repair. 4. mark items installed and in use only when removed and inducted into repair.   (b) Develop the capability to exchange IUID data using Defense Logistics Management System (DLMS) transactions or Wide Area Workflow Property System Notices.   (c) Place machine readable UII marks on the item itself or encode the UII on other permanent media (e.g., Data Matrix ECC 200, item identification labels) in accordance with MIL-STD-130 N (Reference (j)) as required.   (d) Develop the capability to capture, retain, and provide current and historical data regarding uniquely identified tangible items by UII.   (e) Develop the capability to use UII as a common key in functional databases to enable information sharing and information access to achieve collaboration between and among already existing, or emerging, item management systems.

  25. Draft DoDM 4140.01-M Policy (Vol. 9 continued) (2) All IUID implementations shall include provisions for data introduction and tracking using AIT. Business processes that include IUID capabilities shall use AIT devices that shall be capable of reading an ECC 200-compliant data matrix symbol from product markings, portable document format 417 barcode from unit or exterior packaging markings, or accompanying documentation. Information recorded in AIT devices shall be used to update automated information systems per serialized item management programs required by DoDI 4151.19 (Reference (k)). (3) The DoD Components shall ensure training is provided to personnel who perform functions affecting IUID and training courses are updated to teach current DoD policies and procedures. (4) The Director of the Defense Logistics Management Standards Office shall: (a) Require that DLMS be updated to provide full inter-DoD Component UII tracking capability and that applicable DLMS transactions require use of the UII. (b) Coordinate recommended changes to the DLMS to support IUID through the appropriate process review committee.

  26. Draft DoDM 4140.01-M Policy (Vol 11) (3) Unique item level traceability is required for all DoD serially managed items that are also sensitive or pilferable, all DoD serially managed critical safety items and all NWRM using a Unique Item Identifier (UII) assigned to each individual item, i.e. a single instance of a stock-numbered item or a single assembly or subassembly. Unique item level traceability is also required for depot level reparables as well as any item that the materiel manager decides requires unique item level traceability. This requirement does not apply to items managed only by lot. Components shall begin to transition from serially managing these critical items using the manufacturer’s serial number to serially managing the items using the globally unique and machine-readable UII (Construct #1 or #2 or acceptable equivalents) as defined in the “DoD Guide to Uniquely Identifying Items” at the IUID website.

  27. Draft DoDM 4140.01-M Policy (Vol 11 continued) While most items are accounted for by NSN, Components shall account for all DoD serially managed items that are also sensitive or pilferable, or DoD serially managed critical safety items or NWRM by UII within NSN or by serial number during the transition state until system changes implementing IUID are complete. These items shall be assigned a UII in accordance with DoD Instruction 8320.04 and a level of management intensity commensurate with the risk (high and standard). The Military Departments and DLA shall develop the capability to intensively manage these items as follows: (a) For high management intensity items (NWRM): 1. Receipt, issue, and inventory processes or balance affecting actions to both the storage site asset balance record and the materiel manager asset balance record, will be conducted by UII within NSN.2. Issuing activities will provide shipment notification or shipment accompanying documentation to the recipient identifying the NSN and UII provided. 3. When wholesale stocks are issued, whether from stock or direct delivery, the recipient, in addition to updating asset records by UII within NSN, will acknowledge receipt back to the wholesale materiel manager by UII.

  28. Draft DoDM 4140.01-M Policy (Vol 11 continued) (b) For standard management intensity items (DoD serially managed items that are also sensitive or pilferable or DoD serially managed critical safety and depot level reparables):1. Receipt, issue or balance-affecting actions to the storage site asset balance record will be conducted by UII within NSN at the storage site. Physical inventory at the storage site can be performed by NSN or by UII within NSN. The materiel manager asset balance record will continue to be updated and maintained by NSN.2. Issuing activities will provide shipment notification or shipment accompanying documentation to the recipient identifying the NSN and UII provided. 3. When wholesale stocks are issued, whether from stock or direct delivery, the recipient will update asset records by UII within NSN, but will acknowledge receipt back to the wholesale materiel manager by NSN only.

  29. IUID Game Plan 1. Update Policy/Guidance 9. GO LIVE! 2. Cost Effective Item Identification 6. Obtain Proposed DLMS changes, and Approval of FLIS Codes & “SIM Guidebook” 7. Finalize Implementation Planning 8. Finalize System Development 3. Develop/Refine Business Rules Across Logistics Enterprise 4. Develop/Refine Standard Data Exchanges and Mechanisms 5. Rationalize Cost of Management Intensity Level with Item Population 29

  30. IUID Game Plan (continued) Update DoDI 8320.04 Update DoDI 4151.19 Update DoDM 4140.01-M Update GFP/CAP Policy & Procedures Update DFARS Clauses 211.7003 & 211.7007 Develop/issue guidance on items that require tech. data Develop tools that reduce the cost of tech. data updates • Conduct workshops and draft “SIM Guidebook” • Revise IUID in Maintenance CONOPs • Provide processing costs estimates for evaluation of the levels of management intensity • Publish “SIM Guidebook” • Publish FLIS Code and update catalog procedures • Propose DLMS changes 3. Develop/Refine Business Rules Across Logistics Enterprise 4. Develop/Refine Standard Data Exchanges and Mechanisms 1. Update Policy/Guidance 5. Rationalize Cost of Management Intensity Level with Item Population 2. Cost Effective Item Identification 6. Obtain Proposed DLMS changes and Approval Of FLIS Codes & “SIM Guidebook” 30 30 30

  31. Fund transition to management by UII and sustainment thereof Perform engineering analysis for marking Attrit unmarked legacy items Facilitated by storing unmarked legacy items in a separate location Ensure new/modified contracts require: Item mark (MIL-STD-130) Exterior package identification labeling (MIL-STD-129) Engineering analysis to determine marking location WAWF Clause Purchase and install 2D data matrix and PDF 417 scanning/reading/marking equipment for appropriate sites Establish training requirements IUID Game Plan – Component Implementation Planning Activity 7. Finalize Implementation Planning 31 31 31 31

  32. Modify FLIS to: Provide IUID flag via master data and ultimately as part of FLIS Accept new IUID flag values through standard cataloging interface with legacy systems/ERPs Must accommodate business processes from provisioning to disposal IUID Game Plan – Component System Development Activity • Modify legacy systems/ERPs to incorporate business rules, processes and standard data exchanges as defined in the “SIM Guidebook”: • Use IUID constructs • Integrate FLIS code for IUID as part of standard cataloging interface • Populate NSNs within FLIS with proper IUID code • Implement systems changes to support new business processes • DLMS transactions including UII capability • Program discrepancy/deficiency processing for missing, mismatched and non compliant UII conditions • Program reconciliation processing to resolve mismatched UIIs 8. Finalize System Development 32 32 32 32

  33. Immediate Next Steps Arms, Ammunition & Explosives Workshop – May 5th Reconciliation and Other Forms of Mismatches Workshop – Date TBD IUID Registry Workshop – Date TBD Stable participation key to success 33 33 33

  34. Back Up 34 34 34 34

  35. IUID Timeline = Today Product Lifecycle Management, Property Accountability & Intensive Item Management via IUID-enabled SIM Components develop, fund, and field capabilities to manage items in compliance with “Guidance” and Policies* Components complete comprehensive implementation planning based on “Guidance” Dec2015 Leverage IUID TF to develop and issue IUID “Guidance” Dec2012 Complete policy and DFARS revisions IUID TF conducted value proposition analysis Mar2012 Complete Implementation Planning Jun2011 Deliver “IUID Guidebook” Completed Tasks Dec2010 • DPAP Issued IUID Policy Clarification Feb2010 • JLB approved IUID Task Force recommendations Jun2009 • JLB directed the formation of an IUID Task Force Jun2008 • 8320.04 established IUID standards for Tangible Personal Property 35 Dec2006 • 4151.19 established SIM for Materiel Maintenance

  36. Definitions for IUID Items High Intensity Worldwide visibility and management of NSNs by UII where both owner and storage activities have visibility and traceability to the exact location of a serialized item in real time. Records between owner and storage activity are synchronized at least daily and differences reconciled by UII. Mismatches identified by receiving activities must be reported under Discrepancy Report business rules, and corrective action taken where appropriate. Standard Intensity Visibility and management of NSNs by UII where only the local storage activity has visibility and traceability to the exact location of a serialized item in real time. The owner can query the local storage activity to locate the serialized item if required. Mismatches identified by receiving activities must be reported under Discrepancy Report business rules, and corrective action taken where appropriate. 36

  37. Proposed IUID Required Code - Details CODEEXPLANATION 1A High-intensity serialized management by UII. Worldwide visibility and management of NSNs by UII where both materiel manager and storage activities have visibility and traceability to the exact location of a serialized item in real time. Records between materiel manager and storage activitiesare synchronized at least daily and differences reconciled by UII. Mismatches identified by receiving activities must be reported under Discrepancy Report business rules, and corrective action taken where appropriate. 1B Proposed High-intensity serialized management by UII (INTERIM). Applies to NSNs that require serial management by IUID but on which legacy assets on the NSN have not yet been IUID-marked in critical mass to allow system logic for supply chain management using the UII. This code will enable the storage activity to manage the item by the NSN in the interim until legacy assets on the NSN have been marked with a UII and contracts have been updated to include the IUID clause. Once the legacy assets on the NSN have been marked with a UII, the code value will be updated to full serialized item management by UII using the “1A” code value above. 2A Standard-intensity serialized management by UII. Visibility and management of NSNs by UII where only the local storage activity has visibility and traceability to the exact location of a serialized item in real time. The materiel manager can query the local storage activityto locate the serialized item if required. Mismatches identified by receiving activities must be reported under Discrepancy Report business rules, and corrective action taken where appropriate. 2B Proposed Standard-intensity serialized management by UII (INTERIM). Applies to NSNs that require serial management by IUID but on which legacy assets on the NSN have not yet been IUID-marked in critical mass to allow system logic for supply chain management using the UII. This code will enable the storage activity to manage the item by the NSN in the interim until legacy assets on the NSN have been marked with a UII and contracts have been updated to include the IUID clause. Once the legacy assets on the NSN have been marked with a UII, the code value will be updated to full serialized item management by UII using the “2A” code value above. 37 37 37

  38. Definition of Principal & Secondary Inventory Items from 4140.1-R Principal Item An end item or a replacement assembly of such importance to operational readiness that management techniques require centralized individual item management throughout the supply system to include items stocked at depot level, base level, and using unit level Secondary Item An item that is not defined as a principal item and includes reparable components, subsystems, and assemblies, consumable repair parts, bulk items and material, subsistence, and expendable end items, including clothing and other personal gear 38 38

More Related