Subject: Update to Policy for Unique Identification of Tangible Items

Defense AT&L, Jan-Feb, 2005 by Michael W. Wynne

THE UNDER SECRETARY OF DEFENSE

3010 DEFENSE PENTAGON

WASHINGTON, D.C. 20301-3010

SEP 3 2004

MEMORANDUM FOR: SEE DISTRIBUTION

SUBJECT: Update to Policy for Unique Identification (UID) of Tangible Items

[ILLUSTRATION OMITTED]

Applying UID to existing items in inventory and operational use is based on the value proposition that UID provides a joint data capability that enables achievement of focused logistics and performance-based logistics strategies, strategic acquisition, and asset visibility to support combat operations. This policy update approves the use of the Electronic Serial Number (ESN) as a UID-equivalent, announces the approved Issuing Agency Codes to be used for the Commercial and Government Entity (CAGE) code and the Department of Defense Activity Address Code (DoDAAC), and addresses other specific UID implementation issues detailed in Attachment A. This policy update also forecasts the requirement to apply UID to existing items in inventory and operational use in Attachment B.

I understand there are physical and time/resource issues relating to the implementation of the UID policy to some tangible items. Therefore, I am encouraging an evolutionary approach that will allow resolution of these issues. To begin this evolutionary implementation, I request that the Component Acquisition Executives (CAEs) direct preparation of model program plans on a number of mission-critical warfighting and combat support systems for submission to the DoD UID Program Manager by November 2004. Development of these plans should take an evolutionary approach and assume use of trigger events to mark items in quantity. I also request that the CAEs direct all program and item managers to begin planning for the application of the UID to the Department's existing legacy items in inventory or in operational use.

All plans should target FY2007 as the point by which: (a) all existing serialized assets should be entered in the UID registry, and (b) UID marking capabilities have been established for all existing items and embedded assets such that marking can commence as applicable equipment is returned for maintenance. Program offices that have already initiated UID planning include the AH-64 Apache, UH-60 Blackhawk, CH-47 Chinook, C-17 Globemaster Ill, B-1B Lancer, V-22 Osprey, and the Program Executive Officer, Ammunition. I request that all program and item managers plan and establish a goal to complete UID marking of items and all embedded assets within existing items by December 31, 2010, using the planning guidelines included in Attachment B. It is recognized that programs will have different levels of completion by 2010 because fielded items will not be removed from service for the sole purpose of UID marking.

To support this objective, I also request that the Army, Navy, Air Force and Defense Logistics Agency CAEs develop and present to me by January 2005, plans to develop infrastructure, modify Automated Information Systems (AIS) and propose exempted systems that will be phased out of inventory prior to UID implementation. My expected outcomes for FY 2005 are as follows:

* Plans for programs will be developed and required resources identified.

* OSD UID budget guidance issued by April 2005.

* AIS and depot roadmaps for key data systems developed and necessary infrastructure identified, in coordination with the Joint Forces Command and the Transportation Command, as required. The Deputy Under Secretary of Defense (Logistics and Materiel Readiness) and the Director, Defense Procurement and Acquisition Policy will provide staff assistance to the CAEs in this effort.

* Army, Navy, Air Force and Defense Logistics Agency UID Acquisition Manager appointed.

I have requested that the Director, Defense Contract Management Agency (DCMA) lead the development of facility-wide or corporate Single Process initiative strategies with DoD's top 30 suppliers of supplies and equipment, and collectively with aircraft engines and avionics sector suppliers. DCMA will use block changes to expedite UID implementation working with the Components. As part of this process, the DCMA Director will have the authority to grant near-term extensions on UID implementation if such extensions are consistent with the implementation schedules of the negotiated corporate/facility strategies. I have asked the Director, DCMA to lay out the specifics of this approach for discussion with the CAEs by November 2004. I have also asked DCMA to take the lead in developing a UID Quality Assurance Plan for implementation across DoD.

The DoD UID Program Management Office will accomplish the following:

* Develop guidance for trigger events (i.e., a change in an item's ownership, status, location, identity or program alignment).

* Develop guidance for the use of "virtual" UIDs for items in operational use and inventory (e.g., establishing UIDs in DoD information systems but deferring the physical item marking until a "trigger event" such as maintenance or overhaul occurs.

* Develop a refinement to the Department's unique identification registry concept of operations working with the Office of the Under Secretary for Personnel and Readiness, Office of the Assistant Secretary of Defense (Networks and Information Integration), Office of the Joint Chiefs of Staff (J-4 Logistics), and Office of the Joint Chiefs of Staff (J-8 Force Structure, Resources and Assessment).