UNIQUE ITEM IDENTIFICATION (UID) NPMA Eastern Region NES Fort Wayne, Indiana. October 15, 2004 Pat Jacklets, CPPM CF Manager, Property Management NGIS

Transcription

1 UNIQUE ITEM IDENTIFICATION (UID) NPMA Eastern Region NES Fort Wayne, Indiana October 15, 2004 Pat Jacklets, CPPM CF Manager, Property Management NGIS

2 Data Sources The information that is being shared on the subject of UID and RFID today have been obtained from AIA Meetings and AIA/DoD Meetings and the following Websites or NOW: 11/04/2003

3

4

5 UID

6

7 AGENDA Why? DoD's Vision Policy Overview What Items Require UID? How? How is it Constructed What Items Require UID Valuation Data Requirements Who are the Stakeholders? 11/04/2003

8 AGENDA GFP Implementation Legacy Policy Migration Strategy Business Rules Property Management Opportunities and Issues Next Steps RFID Summary Background Info Important Links 11/04/2003

9 Why we need UID... and RFID

10 Why Do It? DoD Vision Acquisition Increase business intelligence Enable paperless Government Furnished Property Management Leverage commercial technologies and practices Increase supply chain visibility Create a common language of business Logistics Increase systems/equipment operational availability Lower costs of managing assets Improve end to end asset visibility Reliability and maintainability info on each item through life Improve supply chain efficiency Accounting and Finance Enable clean audit opinion Reduce late interest penalties Joint Forces Increase in-transit visibility Decrease frustrated freight Enable coalition support Improve data quality and interoperability

11 UID Policy Overview The contractor shall deliver all items under a contract line, subline, or exhibit line item and determine the data qualifier strategy they will use Specific Requirements Item is defined as a single hardware article or unit formed by a grouping of subassemblies, components or constituent parts The requiring activity determines the necessity for UID for items with a unit acquisition cost less than $5,000 The requiring activity determines whether to require a UID for subassemblies, components, and parts embedded within an item regardless of dollar value Subassemblies, components and parts embedded within an item will be identified in a CDRL or other exhibit (see the Data Item Description for Use in Preparing the DD1423 (CDRL) at Requirements for UID and acquisition cost determination will be passed on from prime to subcontractors 11/04/2003 NORTHROP GRUMMAN PRIVATE/PROPRIETARY LEVEL 1 0R LEVEL 2

12 UID Policy Latest Update September 3, 2004 Update of UID Policy (M. Wynne, OUSD) Approves : Use of Electronic Serial Number (ESN) Use of Issuing Agency Codes (IAC): Commercial and Government Entity (CAGE) Department of Defense Activity Address Code (DoDAAC) Provides Schedule of Events Identifies New Data Elements 11/04/2003 NORTHROP GRUMMAN PRIVATE/PROPRIETARY LEVEL 1 0R LEVEL 2

13 What Items Require UID?. 11/04/2003 NORTHROP GRUMMAN PRIVATE/PROPRIETARY LEVEL 1 0R LEVEL 2

14 How is UID Constructed? An UID number cannot be more than 78 characters as follows: Issuing Agency Code: 3 Enterprise Identifier: 5-13 Part Number: 1-32 Serial Number: 1-30 Total (Max all Elements) 78 11/04/2003 NORTHROP GRUMMAN PRIVATE/PROPRIETARY LEVEL 1 0R LEVEL 2

15 UID: How is it Constructed? 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 From the Data Matrix: Enterprise Identifier Original Part Number = 1234 Serial Number = 0CVA5 (CAGE Code) = 674A36458 The UID can be derived using the IAC for CAGE, which is D : UID Construct 1 If the Serial Number is Unique within the Enterprise Identifier D0CVA5674A36458 UID Construct 2 If the Serial Number is Not Unique within the Enterprise Identifier but is Unique within the Part Number D0CVA A /04/2003 NORTHROP GRUMMAN PRIVATE/PROPRIETARY LEVEL 1 0R LEVEL 2

16 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. 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. UID Construct #1 1 UID Construct #2 1 12V S V P S /04/2003 EID Serial No. EID Original Serial No. Part No. 1 This example uses MH Data Identifiers.

17 UID Number Does NOT Change if the Part Number Changes In the database, once the UID is created from the separate data elements: It shall exist as a discrete data element It shall not be parsed to determine the original elements It shall be the primary pointer/key for the database 17V P S Record ID UID (Constructed with a Business Rule) EID Original Part No Serial No Current Part No Other Data Incremental Never Changes (mandatory for audit) Optional Can Change

18 UID for an End Item Manufacturer s EI = IAC = UN Serialized within Original Part Number PN EI PN SN Data Elements Placed on Item Delivery to Govt UN Concatenated UID End Item Product Spec EI = Enterprise Identifier; IAC = Issuing Agency Code, UN = IAC for Dun & Bradstreet; PN = Original Part Number; SN = Serial Number Serialized within Enterprise Identifier EI SN 674A36458 Data Elements Placed on Item Delivery to Govt UN A36458 Concatenated UID

19 UID Process SAMPLE Step 1: Define the UID (Enterprise) 1 2-D Data Matrix (Required) 17V S V Step 2: Mark the asset with the UID (Enterprise) Step 3: Read and concatenate the UID upon acceptance (DoD) Step 4: Transfer the UID to the AIS (DoD) 18S May Also have 1-D Linear Bar Code 1 This example uses UID Construct #1 with MH Data Identifiers and assumes the asset has been determined to require a UID.

20 VALUATION 1. Contracts Requirements UID Policy The following chart provides further guidance on UID/Valuation. Deliverable CLIN/SLIN Items requiring UID or UID Equivalent UID or UID Equivalent Required Yes All items valued over $5K/unit value. Use DoD decision tree to determine requirements under $5K/unit value Unit Acquisition Cost (or price) Required Yes Valuation Method (Contract type) Fixed Price- use CLIN/SLIN values Cost Type-use target prices. Gov t will address delta $ from final total price Sub items contained within CLIN/SLIN delivered end items. (LRU/Spares/ROR) Yes No dollar threshold for applicability; IAW maintenance plan (e.g. consumables and repairables). * No N/A Other commercially marked items. CLINs/SLINs No The Government shall accept commercial markings as the UID equivalent Yes All delivered items must be valued/unit. Use CLIN/SLIN value or target price if cost type Example: JSF : Contractor provides one UID corresponding with tail number and a value (CLIN Price). Also provides list of UIDs (IAW CDRL) internal to JSF (without values) *UID CDRL Requirement

21 UID in the Supply Chain 1 (Government determines which items it wants with UIDs IAW Contract Clause which may be based on the Maintenance Plan) Pull Information Rather Than Push Valuation at This Level Only Product Data Enterprise Prime PNO 200H0028 End Item Specs Supply Chain Item Markings 1 CAG PRO 200H0028 SEQ Item Markings 1 Unique Items UID (Note) H0028 List of Hardware Delivery to Govt UIDs End Item (Optional) Tier 1 PNO 210H0611 Subassembly Specs CAG PNO 210H0611 SEQ Item Markings 1 Delivery to Govt Spares H0611 List of Hardware UIDs (Optional) Tier 2 PNO 216H1439 CAG PNO 216H1439 SEQ H1439 Tier 3 Component Specs PNO 218H2861 Item Markings 1 CAG PNO 218H2861 SEQ Delivery to Govt Spares List of Hardware UIDs (Optional) H2861 Part Specs 1 This example uses UID Construct #2 with Text Element Identifiers. Delivery to Govt Spares

22 Valuation To satisfy valuation the Government does not need to have visibility into the value of the components of the delivered item, unless they are purchased separately as spares CLIN for vehicle # abc, contains a motor value provided for vehicle but not the motor CLIN for motor purchased as a separate spare value provided for the motor

23 When is data required? When a contractor ships items, UID data must be included in the shipment notification as the contract specifies and as the program manager requests. Development of the Wide Area Work Flow (WAWF) system to process the UID data is currently under way fixed price contracts - complete. A number of interim solutions have been developed to accept UID data for items until WAWF is ready to accept the UID data. Visit: For the most current guidance, please reference the UID website at and Click on the UID Data Tab.

24 How do I submit UID data? The Government Issued Tasking Memo 0147 on March 3, 2004 Submit invoices and receiving reports electronically into WAWF using existing Electronic Commerce methods. Choices that are now available include Web interactive forms and straight push from Vendor automated systems (FTP and EDI). Vendors can access the WAWF system via the web interface and follow the link called "Self Register to use WAWF (New Users)", whereby they will be walked through the process of having access to the WAWF system,

25 UID data Submitted via WAWF or Direct The following decision tree identifies when to use WAWF and when to use a direct method. It will be updated as WAWF functionality is increased to handle additional contract and item types.

26 UID: Database Data Transmission The contractor is required to transmit, upon shipment notification, UID database data in addition to the data in the Data Matrix symbol and in addition to any data previously required during shipment notification Database data required for UID includes: End Item Database Data (15) UID (Concatenated) Descriptive Data UID Data Elements (3) Issuing Agency Code UID Type 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 (3) Issuing Agency Code UID Type Item Description Unit of measure Parent UID as of delivery date GFP flag

27 UID Data Elements Unique Item Identifier Type (UID Type): UID1 - Unique Identification Construct 1, Serialization within the Enterprise UID2 - Unique Identification Construct 2, Serialization within the Original Part Number VIN - Vehicle Identification Number GRAI - EAN.UCC Global Returnable Asset Identifier GIAI - EAN.UCC Global Individual Asset Identifier OTHER - For UIDs without an assigned UID Type

28 New UID Data Elements Identified in Attachment B to Sept 3, 2004 Policy Update Action code (e.g. Add, update) Currency Code (default US$) Current Part Number with Effective Date Government Furnished Property (GFP (End Items and Embedded Items) - GFP Flag (Y/N) -GFP Effective Date Current Marking - This will cover the use of a "Virtual UID" Type (None, 2D, Contact Memory button, RFID, etc) Type Effective Date It was also noted that "Future policy updates will address ownership, location, and additional descriptive information as the Department's approach to uniquely identifying other entities, such as real property and organizations, continues to mature.

29 Users Assessments Retrieved Total Governm ent Contractor Total Government Contractor 14-A ug O ct N ov ,1 60 1, Dec ,6 31 1, D ec ,7 21 1, Jan ,9 00 2, Feb ,6 24 3, Mar-01 1, ,9 28 6, M ar-01 1, ,8 27 8,78 7 1, May-01 1, , ,32 8 1, Jun-01 2, , , ,64 8 1, Jul-01 2, , , ,86 4 1, Aug-01 2,757 1,056 1, , ,53 6 1, A ug-01 3,136 1,083 2, , ,18 2 2, O ct-01 3,595 1,150 2, , ,35 7 2, N ov-01 3,985 1,214 2, , ,79 1 2, Dec-01 4,481 1,265 3, , ,24 5 3, Jan-02 4,695 1,237 3, , ,84 0 3, Feb-02 5,109 1,212 3, , ,23 2 3, Mar-02 5,515 1,216 4, , ,62 6 3, Apr-02 6,132 1,325 4, , ,39 2 4,2 60 Users Assessments Retrieved Total Governm ent Contractor Total Government Contractor 14-A ug O ct N ov ,1 60 1, Dec ,6 31 1, D ec ,7 21 1, Jan ,9 00 2, Feb ,6 24 3, Mar-01 1, ,9 28 6, M ar-01 1, ,8 27 8,78 7 1, May-01 1, , ,32 8 1, Jun-01 2, , , ,64 8 1, Jul-01 2, , , ,86 4 1, Aug-01 2,757 1,056 1, , ,53 6 1, A ug-01 3,136 1,083 2, , ,18 2 2, O ct-01 3,595 1,150 2, , ,35 7 2, N ov-01 3,985 1,214 2, , ,79 1 2, Dec-01 4,481 1,265 3, , ,24 5 3, Jan-02 4,695 1,237 3, , ,84 0 3, Feb-02 5,109 1,212 3, , ,23 2 3, Mar-02 5,515 1,216 4, , ,62 6 3, Apr-02 6,132 1,325 4, , ,39 2 4,2 60 Enterprise UID Digital Data Flow Potential DoD Budget Submission Need Line Item Appropriations Requirement Requisition X-6X G 25POLI P68EY78945J145 POLI X-6X G 25POLI P68EY78945J123 POLI Lines of Accounting Shipping Notice Contract Transportation Commitment Obligation WAWF Delivered Item Inspection Receiving Expenditure Financial Management Acceptance Acquisition Property Log Property, Logistics, and Transportation

30 Leveraging UID Data Capture/Use User Requirements Acquisition Systems Design, Development and Manufacture Inspection/ Acceptance/ Receipt Transportation/ Transfer of Ownership Disposal/ Sale Level 1 Processes M,R&O Requirements Mgmt Supplier Mgmt Procurement Inventory Mgmt Contracts Mgmt 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 Level 2 Processes Identify UID items Level 3 UID Transactions Solicitations Contracts Trace-ability Mark Scan Populate Ship Notice Populate DID/CDRL Populate CM system 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

31 UID Vendor Perspective 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 Issue: Existing marking processes must be able to accommodate UID requirements. Impact: Existing investments in marking infrastructure are leveraged.

32 Who are the Stakeholders? Stakeholder Contracts Engineering/ CDM Role Understand the UID requirements in solicitations/ contracts. Contract structure for deliverables Evaluate UID data elements in equipment specifications and engineering drawings. Impact Understand business rules that are being developed Ensure solicitations are properly estimated when UID is introduced. Drawing Revisions Track and Provide As Built UID Information for DD250 Finance Cost Collection/Accounting Billings New Data Base for Managing Serial Numbers Added Task to provide data through Wide Area Work Flow (WAWF) (WAWF changes: April 04 for FP and July 04 for Cost type)

33 Who are the Stakeholders? Stakeholder Role Impact Material/ Procurement/ Government Material Control Operations Marking/Supply Chain Management Requirement flow down to subcontractors Information flow up to prime contractor Managing Government Furnished Material with Unique Identifications Marking manufactured items requiring UID New Equipment for Marking New T&C s for PO s System change to accommodate up to a 78 character UID number (by January 2005) New Equipment for Marking Changes to Processes

34 Who are the Stakeholders? Stakeholder Role Impact Integrated Logistics Support Quality Property Management Maintenance Plan Importance Of Control of ROR Spares Requirements Enforce rule both in house and at Suppliers for proper DD250 Information Understand the UID requirements in solicitations/ contracts Understand business rules that are being developed Ensure solicitations are properly estimated when UID is introduced. Data base change to accommodate UID Additional tasks during inspection and acceptance Business Rules not developed yet! Data Base Change to Accommodate UID for Government Property ST, STE, APP, IPE and OPE Managing Serial Numbers by January 2005

35 GFP Implementation Meetings have been held to Brainstorm approach to GFP implementation Legacy Property In Custody of Contractors GFM Repair of Repairables Visit the UID website and click on the GFP tab Minutes and Action Items are Posted

36 UID Plan for Government Furnished Property Guidance to Government Policy then DFARS All solicitations issued after Jan 06 must use UID business rules All GFP sent after January 2006 must have UID unless DCMA verifies in GFP registry that the contractor has an approved UID corporate or facility implementation plan AT&L issuance of GFP Policy October 04

37 UID Plan for Government Furnished Property Guidance to Contractors - DFARS 2005 No 1662 report required for Sept 05 if all existing property in GFP registry by July 05 using virtual UIDs Jan 06 All GFP property recorded in GFP registry* DCMA updates existing contractor T&Cs using block changes Jan 07 CAC/PKI target date for GFP functionality Add Real Property capability *Password enabled

38 Legacy Policy Migration Strategy Use of Virtual UIDs Critical Data Mass Deployed/Stored Serially Managed Items 2005 Assign Virtual UIDs End Items Embedded Items Spares GFP Newly Manuf. Depot Few Data Matrix New Labels; Data Plates Near Term Mid Term Long Term Parts Physically Marked New Serialized & Non- Serially Managed Items Data Matrix UID Direct Mark New Labels Data Plates UID Central Data Registry Notional Registration Rate Modify On-Going Contracts Delivery Orders Options 2007 Rebuilt/Repaired Serially & Non-Serially Managed Items Data Matrix UID Data Plates New Labels Direct Mark Depot Manufacturing & Maintenance 2010

39 Property Management Opportunities and Working Groups Objectives Define GFP scenarios, trigger events, thresholds (lot vs. item), GFP pedigree data Map one complex scenario to use as test case (e.g., outsourcing depots, BRAC) Enhance current business rules Identify logical, staged implementation approach for UID/GFP Bring existing FAR terms into alignment with UID and industry, reduce the classifications of property Identify policy modifications including data considerations (i.e., WAWF)

40 Property Management Issues Additional Data Elements are Being Identified - Based Upon the Vision and Purpose of the Registry Intention is to minimize the burden on contractors. But projected functionality includes additional fields Status: Original, installed, retired, sold, scrapped.. Mark Type: Recognition of Virtual UID, Linear Barcode, Contact Memory Buttons, PDF417. Parent UID NHA UID for embedded and GFM 1 level GFP Indicator I m already in the UID Registry Catalog information Company, Version and Date??

41 Property Management Issues Additional Data Elements are Being Identified The source of data for each data element on each form has not been identified Business rules for each form has not been developed DoD and Industry team are developing transaction scenarios using UID as a basis to determine business rules The balance between benefits with complexity, functionality, application and Government and Industry cost has not been determined

42 Property Management Issues Current state of in-plant asset tags: Most use preprinted barcode labels CAGE code is not included Future State: Expect most sites to acquire capability to create labels on an as needed basis. This capability may be required regardless, because of label deterioration Expect some sites to order preprinted labels of construct one

43 What are Business Rules? A Business Rule is a statement that defines or constrains some aspect of the business. It is intended to assert business structure or to control or influence the behavior of the business. Typical Business Rules include definitions of terms, facts relating terms to each other, constraints, and derivations.* * DoD Guide For Uniquely Identifying Tangible Property; Appendix C - Business Rules (Version 3.5a)

44 Business Rules - Categories Contracts and Administration Accounting and Finance UID Construction and Physical Marking for: Items considered part of a new solicitation after January 1, 2004 (i.e., New Items) Items existing under contract or in inventory is TBD (i.e., Legacy Items) Items considered tangible personal property owned by the government in possession of a contractor after January 1, 2005 (i.e., Property Management Items) Expect to move to the right 2006? Automated Information System (AIS) Technical Interface

45 Current Business Rules: 36. A UID is not required to be physically marked on tangible personal property items owned by the Government in the possession of a contractor unless the item is moved or delivered to a different location with a different enterprise identifier. Having a virtual UID provides the benefits without the high cost of an additional physical UID label. There is no intent to require UID on all items for sites that have more than one CAGE code or with moving an item to an alternate site or subcontractor.

46 What Does Delivery Really Mean? Definition: Must include Change in Enterprise, Accountability and Physical Location Must be required under a specific contract line item rather than a clause. (CLIN/SLIN) Is not expected to be delivered in place. Would be part of the DD-250 Process, including Quality inspection Expect most STE and ST will not be delivered Must provide data elements as required by the UID rules

47 Final UID DFARS Rule with Proposed Changes Requirement Clarifications Items under $5K: Equipment and reparable items when they are serially managed, mission essential, or controlled inventory Material and consumable items when the requiring activity determines that permanent identification is required General requirement for commonly accepted commercial marks if UID not required - deleted Definitions added for Issuing Agency and Lot or Batch number Embedded items; Any serially managed subassembly component, or part Exceptions Added Contingency operations Items acquired from a small business or under FAR Part 12 for commercial items, when More cost effective for the Government to assign, mark, and register the UID after delivery, and HCA approves D&F (CAE for ACAT I)

48 RFID RFID Policy Policy for Implementation Draft July 30, 2004 Policy Update February 20, 2004 Policy October 2, 2003 Attachment (1) Attachment (2)

49 DFARS Clause: Two Major Requirements for Suppliers Passive Tagging at the case, pallet, UID item packaging level in accordance with the Implementation Plan Advanced Shipment Notification (ASN) Definitions of levels of tagging are included (in accordance with MIL-STD 129 Definitions) Case Shipping Container and/or Exterior Container Pallet Palletized Unit Load UID Item Packaging UID Item Pack Tag Data Standards Tag Placement DoD will publish a Supplier Guide that contains information that details requirements for compliance

50 RFID for DoD VISION: Implement knowledge-enabled logistics through fully automated visibility and management of assets in support of the warfighter GOAL: Employ mature and emerging supply chain technologies to optimize the supply chain OBJECTIVE: Utilize RFID to facilitate accurate, handsfree data capture in support of business processes in an integrated DoD supply chain enterprise as an integral part of a comprehensive suite of AIT technology.

51 What does the Draft Policy Cover? Active RFID Freight containers and consolidated air pallets Passive RFID Cases, pallets and packaging on UID items

52 Implementation Level of Tagging January 1, Palletized Unit Load Tag YES Pallet tag Exterior Container YES Shipping Container YES UID Item Unit Pack* NO *If the UID Packaging is also an External Container or a Shipping Container, it will have an RFID tag.

53 Implementation Level of Tagging January 1, 2007 Palletized Unit Load Tag YES Pallet tag Exterior Container YES Shipping Container YES UID Item Unit Pack YES

54 Summary UID and RFID are Here Government Self Admits to Chaos This Year! First Solicitation with a UID requirement will Probably be a Spares Order Compliance Entails 2 D Data Matrix Mark Which Provides the UID Component Data Elements Enterprise No. + Part Number + Serial Number or Enterprise No. + Serial Number Controlling Serial Numbers to Ensure Uniqueness Negotiate to Have the Government Mark Items Upon Receipt

55 BACKGROUND MATERIAL

56 Background 11/04/2003 Chief Financial Officers Act of 1990 (affects Property Valuation and Marking) DoD Memorandum USD (AT&L and USD (Comp) Aug 16, 2002; Universal Identifier Code DoD Memorandum DUSD (AT&L) Sept 6, 2002; Universal Identifier Code, Interim Policy DoD Memorandum DUSD (AT&L) Dec 19, 2002; Forecast of Policy for Unique Identification of Tangible Assets DoD Memorandum DUSD (AT&L) Apr 4, 2003; Forecast for Unique Identification of Tangible Items Memorandum Policy for UID, issued Jul 29, 2003, Michael Wynne, Acting Under Secretary of Defense

57 11/04/2003 Background (cont d) DFARS Draft Interim Rule on Property Valuation/Marking forwarded to DAR Council August 6, 2003 Memorandum Policy for RFID, issued Oct 2, 2003, Michael Wynne, Acting Under Secretary of Defense DFARS Interim Rule Published Oct 10, 2003 in the Federal Register (30 day Comment Period) DFARS MIL-STD-130L Which Includes UID Marking Published Oct 16, 2003 Public Hearing Held on Nov 6, 2003 Memorandum Policy Update, issued Dec 22, 2003, Michael Wynne, Acting Under Secretary of Defense (OK for CAGE Code!) DFARS 2 nd Interim Rule Published Dec 30, 2003 in the Federal Register (60 day Comment Period)

58 Recent UID Events & Policy Update On November 26, a policy clarification memo was released providing further information on such areas as DoD accepted UID equivalents. Another clarification regarding the Issuing Agency Code (IAC) for CAGE and DoDAAC was issued Dec 22. Memorandum Policy for UID, issued Sept. 3, 2004, Michael Wynne, Acting Under Secretary of Defense

59 Current Business Rules: 33. Tangible personal property items owned by the Government in the possession of a contractor will use the enterprise identifier of the enterprise maintaining the serial number of the item. In this case the manufacture s identifier will not be used as in the case of other delivered products the accountable contractor s enterprise identifier will be used. This approach assures uniqueness.

60 Current Business Rules: 34. A UID should be created for tangible personal property items owned by the Government in the possession of a contractor by using UID Construct #1. (EID and Serial Number) The CAGE code is a unique number for suppliers, and the internal serial number is unique within the supplier s plant the combination is unique world wide.

61 Current Business Rules: 37. Tangible personal property initially furnished to the contractor by the Government will use the UID provided by the Government. If none is provided, establish a UID using the criteria in Rules This will require internal business rules of how to retain or use the UID for internal management purposes. Most companies are expected not to use the UID for internal control because of the size of its footprint. 38. Tangible personal property will also require markings or labels indicating Government ownership. (Not a data element)

62 LINKS Reference UID Guide to Marking Items v1.3 (Posted ) UID General Information Paper 6.3 UID Contracting Information Paper v8 (Posted ) Business Rules Version 3.5 (Posted ) UID Data Submission (Posted ) Data Submission Information Paper UID Elements Structure Data Submission Information File (Compressed File)

63 LINKS References Section of the Website UID Guide to Marking Items v1.3.1 (Posted ) Data Item Description (Posted ) Information needed to prepare a DD Form 1423 Contract Data Requirements List (CDRL) for embedded UIDs by tailoring the data item description for Bar Code Identification Report (DI-MGMT-80177A) UID General Information Paper 6.3 UID Contracting Information Paper v9 (Posted ) Business Rules Version 3.5 (Posted )

64 LINKS UID Data Submission (Revised ) Data Submission Information Paper UID Elements Structure v1.1 (Posted ) Data Submission Information File v1.1 (Posted )

65 LINKS Military Standard 130L (MILSTD 130L) UID DFARS Interim Rule (Posted )