cc: 

ADUSD(L)SCI 

UID PROGRAM OFFICE 

UNIQUE ITEM TRACKING COMMITTEE (UITC) 

JOINT SMALL ARMS COORDINATING GROUP (JSACG) 

JOINT PHYSICAL INVENTORY WORKING GROUP (JPIWG) 

 
 

1 of 8

ADC 172 

Attachment 

ATTACHMENT TO ADC 172, 

New Unique Item Tracking (UIT) Designator Code and Inclusion of UID and RFID 

Indicators in DS 527D Advance Receipt Information (Supply/UID/RFID/SDR) 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO) 

b. Originator: Ms. Mary Jane Johnson, MILSTRAP Administrator and UITC Chair, 

DLMSO (J-6251), DSN 427-0677, commercial (703) 767-0677, e-mail: 

Mary.Jane.Johnson@dla.mil and Ellen Hilert, Supply Process Review Committee Chair, 

DLMSO (J-6251), 703-767-0676 (DSN 427), e-mail: ellen.hilert@dla.mil 

2. FUNCTIONAL AREA: Supply (UID/RFID/SDR)

3. REQUESTED CHANGE: 

a. Title: New Unique Item Tracking (UIT) Designator Code and Inclusion of UID 

and RFID Indicators in DLMS Supplement (DS) 527D Advance Receipt Information 

(Supply/UID/RFID/SDR) 

b. Description of Change: 

(1) ADC 172 establishes two indicators for use in the DS 527D, Advance 

Receipt Information (ARI) transaction (formerly Prepositioned Materiel Receipt (PMR) 

transactions in MILSTRAP), in support of UID and RFID policy. The intent is to 

provide an automated mechanism for the ICP to notify the receiving activity in advance 

that there is a contractual requirement for UID or passive RFID. Under the DLMS, the 

ARI is mandatory. The 2 new 527D indicators are as follows:

(a) A new “UID Requirement Indicator” to specify that the contract 

requires unique identification (UID) of items IAW UID policy.

(b) A new “Passive RFID Requirement Indicator” to specify that the 

contract requires use of passive radio frequency identification (RFID) for shipment IAW 

RFID policy.

(2) In addition, this change assigns a new value for the cataloging (Federal 

Logistics Information Services (FLIS)) UITDC to identify catalogued items requiring 

UID under DOD policy or by direction of the program manager, but which are not 

subject to a DOD UIT program.

 c. Request for Implementation Date. By DLMSO memorandum, August 18, 2005, 

subject: Request for Implementation Date (RFID) for Approved DLMS Change (ADC) 

172, New Unique Item Tracking (UIT) Designator Code, and Inclusion of UID and RFID 

Indicators in DLMS Supplement (DS) 527D Advance Receipt Information (Supply/UID/ 
 

2 of 8

ADC 172 

Attachment 

RFID), Components were asked to provide their earliest implementation dates for the DS 

527D ARI transaction UID and passive RFID indicators. The following responses were 

received: 

Organization Response to the Request for Implementation Date 

DLA 

Distribution Standard 

System (DSS) 

Mr. George Gray 

DLA J-3731 

The DSS estimated implementation date for ADC 172 - to have the new 

RFID indicator and the UID indicator on the DLMS transaction, and 

recognize these indicators on the DLMS due-in is January 2007. 

DLA 

Business System 

Modernization (BSM) 

Mr. Hellion Flowers 

DLA J-3321 

BSM does not have an implementation date. This ADC is going to 

require a Cross Process Systems Change Request that will have to be 

evaluated in Pos R2.2 which won’t start until January 2006 and not be 

released until end of December 2006. At best if the SCR gets accepted 

by all process areas (it crosses TQ and PR along with OF) and has to be 

accepted by all Process Owners. It looks like at best, 2007 if all goes 

well. I am submitting the requirement today and will have a better answer 

when the DLA Partners group (Deputy Commanders and DLA) meets to 

discuss all the BSM SCRs for Release 2.2X. I will let you know as soon 

as I get more information. 

BSM implementation date response still due to DLMSO. 

Army No response to date. 

Army response still due to DLMSO. 

Navy 

Mr. Edward Poling 

NAVICP M0581 

N-ERP is the solution to incorporate this change. UICP/U2 as legacy 

systems are in brown out and will not be making changes at this point in 

time. 

N-ERP implementation date response still due to DLMSO. 

Air Force No response to date. 

Air Force response still due to DLMSO.

Marine Corps No response to date. 

Marine Corps response still due to DLMSO.

d. Procedures: 

(1) Unique Item Tracking Designator Code (UITDC):

 (a) As an interim step, the UITDC had initially been made available in 

CD-ROM format and web-FLIS. However the ultimate UIT Committee goal was to 

have the UITDC available from the standard FEDLOG catalog system. To that end, 

and in response to an August 11, 2005, conversation between Mr. Dave Osburn, 

Defense Logistics Information Services (DLIS), and Ms. Mary Jane Johnson, UIT 

Committee Chair, DLMSO sent the DLIS Director a memorandum (see enclosure) on 

behalf of the DOD UIT Committee, asking that the UITDC be incorporated in the 

standard FEDLOG cataloging record, to initiate the process. DLMSO first 

coordinated the memorandum with the UIT Committee by e-mail. 

 

 (b) Upon release of ADC 172, the UIT Committee Chair will submit a 

revision to DLIS to add the new UITDC ‘UID’ for use with National Item 
 

3 of 8

ADC 172 

Attachment 

Identification Numbers (NIIN) which fall under UID policy criteria (i.e. they require 

UID marking), but which are not part of established DOD unique item tracking (UIT) 

programs. By definition all assets tracked in DOD UIT programs are subject to UID, 

however, all items subject to UID are not part of DOD UIT programs. The UIT 

Committee chair will request a UITDC revision to add a code for UID as shown 

below (changes are identified by bold italicized text): 

FLIS CODE NAME: UIT Designator 

FORMAT: 3 position alphanumeric code 

PURPOSE: Used to indicate that an item requires DOD level unique item tracking (UIT) and 

to identify a DOD UIT program associated with the UIT requirement. Also used to identify 

items which fall under the DOD Unique Identification (UID) criteria but which are not 

subject to a DOD UIT program. All UID items subject to a DOD UIT program will be 

identified by a UITDC other than ‘UID’. 

AAA DOD Small Arms Serialization Program (DODSASP) 

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Testing and Tracking System (RATTS) Program 

AAD Navy Depot Level Reparables (NDLR) Program 

AAE The Army Maintenance Management System (TAMMS) 

Equipment Data Base (TEDB) 

AAF Aviation Component Tracking Program 

 AAG Tritium Unique Item Tracking Program 

AAH Controlled Cryptographic Items (CCI) 

UID Assets which meet DOD UID criteria for UID marking, but which are 

not subject to DOD UIT program/tracking requirements.1

 

1 See http://www.acq.osd.mil/dpap/UID/ for UID policy and criteria for assigning UID to materiel. 
 

4 of 8

ADC 172 

Attachment 

(2) DS 527D UID and Passive RFID Indicators. Add an indicator to DS 

527D, Due-in/Advance Receipt/Due Verification to provide the storage activity with 

advance receipt information (ARI) identifying whether the contract requires that the item 

due in is subject to UID and/or RFID requirements as follows: 

Item 

# 

Location DS 527D Revision Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Change PDC 149 to ADC 172 in DLMS 

Introductory note 6:

-- ADC 172, New Unique Item Tracking (UIT) 

Designator Code and Inclusion of UID and 

RFID Indicators in DLMS Supplement (DS) 

527D Advance Receipt Information 

(Supply/UID/RFID/SDR) 

To identify DLMS 

changes included in 

the DS.

No impact. 

2. 2/CS17/140 Open CS17, data element 1073, Yes/No 

Condition or Response Code

DLMS Note: Enter ‘Y’ to indicate that the 

contract requires use of passive radio frequency 

identification (RFID) for shipment IAW RFID 

policy. Enter ‘N’ if contract does not require 

passive RFID for the item. See 

http://www.acq.osd.mil/log/rfid/index.htm for 

RFID policy. 

To indicate whether 

shipment is subject to 

passive RFID 

requirements under 

the contract. 

Revision 

required. 

3. 2/CS18/140 Open CS18, data element 1073, Yes/No 

Condition or Response Code

DLMS Note: Enter ‘Y’ to indicate that the 

contract requires unique identification (UID) 

for the item identified in 2/LIN/010 IAW UID 

policy. Enter ‘N’ if contract does not require 

UID for the item. See 

http://www.acq.osd.mil/dpap/UID/ for UID 

policy. 

To indicate whether 

item is subject to UID 

requirements under 

the contract. 

Revision 

Required. 
 

5 of 8

ADC 172 

Attachment 

(3) DLMS Manual Revision. The following procedures provide guidance 

for use of the new 527D ARI UID and RFID indicators approved by this change. Revise 

DOD 4000.25-M (DLMS), Volume 2 (Supply), Chapter 12, Due-In and Advance Receipt 

Information, section C12.3, as follows (change identified by bold italicized red text): 

“C12.3. PROVIDING THE STORAGE ACTIVITY WITH ADVANCED RECEIPT 

INFORMATION (ARI)

C12.3.1. Due-In Information Requirements. IMMs shall provide storage activities 

with due-in information for scheduled material receipts by providing them with DS 527D

ARI transactions. For dues-in from procurement instrument sources, IMMs shall include 

applicable contract information and packaging data, allowed by the convention, to 

facilitate the receiving process and reduce need for hard copy contracts at the receiving 

activity. As part of the contract information, the IMM shall include indicators 

identifying whether the contract requires use of UID or passive RFID. 

 C12.3.2. Storage Activity Requirements. Storage activities receiving DS 527D 

shall keep them in an ARI file pending receipt of the material or the receipt of updates to 

the ARI from the IMM. Storage activities may use the ARI contract information and 

packaging data to facilitate the receiving process. 

 C12.3.2.1 Passive RFID. ARI notice that a shipment contractually 

requires passive RFID will allow preplanning so that the incoming shipment may be 

directed for offloading at the RFID reader location and provides a basis for submission 

of a Supply Discrepancy Report (SDR) in accordance with SDR procedures should the 

vendor fail to employ the required RFID. 

 C12.3.2.2 UID. ARI notice that a shipment contractually requires UID 

provides a basis for submission of SDR in accordance with SDR procedures, should 

the vendor fail to employ the required UID. 

4. REASON FOR CHANGE: 

a. The July 29, 2003, OUSD AT&L memorandum, subject: Policy for 

Unique Identification of Tangible Items - New Equipment, Major Modifications, and 

Reprocurements of Equipment and Spares, established the following criteria for items 

requiring unique identification: “(1) the acquisition cost is $5,000 or more, (2) it is 

either a serially managed, mission essential or controlled inventory piece of equipment or 

a repairable item, or a consumable item or material where permanent identification is 

required, (3) it is a component of a delivered item, if the program manager has 

determined that unique identification is required, or (4) a UID, or DOD-recognized UID 

equivalent is available”. 

b. This change proposes a means to identify National Item Identification 

Numbers (NIINs) subject to UID criteria by exploiting an existing FLIS code, the 

UITDC, which identifies NIINs subject to UIT requirements. 
 

6 of 8

ADC 172 

Attachment 

c. This change provides a transactional method to provide the receiving 

wholesale storage activity with information that an item due-in has a contractual 

requirement for RFID to facilitate the receiving process. Advance notice that the 

shipment requires RFID will allow preplanning so that the incoming shipment may be 

directed for offloading at the RFID reader location. Knowledge of the RFID requirement 

derived from the ARI provides a basis for submission of a Supply Discrepancy Report 

(SDR) should the vendor fail to employ the required RFID. 

d. This change also provides a transactional method to provide the receiving 

wholesale storage activity with information that an item due-in has a contractual 

requirement for UID to facilitate the receiving process. DLMS, Volume 2 (Supply), 

Chapter 17, Supply Discrepancy Reporting (and corresponding DLAI 4140.55/AR 735-

11-2/SECNAVINST 4355.18A/AFJMAN 23-215, Reporting of Supply Discrepancies) as 

updated by ADC 128, requires reporting of discrepancies involving unique item 

identification under UIT program requirements or as contractually required under UID 

program policy. Knowledge of this requirement derived from the ARI provides a basis 

for submission of a SDR should the vendor fail to provide the required UID. 

5. UNIQUE ITEM TRACKING DESIGNATOR CODE (UITDC) BACKGROUND: 

a. DOD 4140.1-R establishes the policy for DOD UIT and charters the UIT 

Committee (UITC) with responsibility for recommending improvements in UIT program 

concepts and technology. One such UITC recommendation was the establishment of a 

FLIS UIT designator code (UITDC) to provide a standard DOD means to systematically 

identify that an item is subject to UIT. The establishment of this code eliminated a void, 

and can facilitate DOD's ability to develop efficient UIT processes using automated 

processes.

b. The UITDC is assigned to NIINs which are UIT reportable, and identifies a 

DOD UIT program associated with the NIIN. The UITC, through the UITC chair, is the 

designated point of contact for submitting revisions to the UIT Designator Code list. The 

Integrated Materiel Manager (IMM) for a NIIN is responsible for assigning the code to a 

given NIIN based on direction from the Component UITC Central Point of Contact 

(POC) and IAW Component cataloging update procedures. Initially the UITDC was 

made available on CD-ROM and web-FLIS, with the ultimate UITC goal of becoming 

part of the standard FEDLOG cataloging record. 

6. ADVANTAGES AND ISSUES: 

a. Advantages: This proposed change exploits an existing cataloging code to 

provide a means to identify NIINs which fall within the DoD UID criteria. This change 

also provides a transactional means for the item manager to identify in the 527D Advance 

Receipt Information transactions, that an item due-in has a contractual requirement for 

UID and/or passive RFID. This information can be used by the receiving wholesale 

storage activity to facilitate the receiving process. 
 

7 of 8

ADC 172 

Attachment 

b. Issues: 

(1) The UIT Designator was not intended for materiel which has significant 

fluctuation as to its applicability. Accordingly, if NIINs identified as a UID item, are not 

consistently UID items across the entire NIIN, such as if a given NIIN is considered 

essential and requiring UID by one Program office, but not by another program office, 

meaning not all of the assets for the given NIIN are subject to UID, this may not be an 

appropriate means to identify UID items and other alternatives should be considered/ 

developed. By PDC 149, the Components were asked to evaluate the use of the 

UITDC for UID items in this context before approval of the new UITDC for UID. 

No negative comments were received. 

(2) Business rules for system/functional use of UITDC ‘UID’ have not been 

identified at this time. 

(3) Both the UID Requirement Indicator and the UITDC provide a means to 

identify UID assets. There is an element of redundancy in the establishment of both, and 

this requirement may be re-evaluated at a future date. Currently, in this early stage of 

implementation it is appropriate. Not all UID items will be identified by cataloguing 

action and not all items which fit the UID profile are shipped under contracts which 

require use of UID. The source for the UID Requirement indicator, which the 

owner/manager would include on the 527D ARI transaction would be procurement, not 

cataloging and would serve as an immediate tool for receiving. 

(4) Evolving UID Logistics Policy: As UID logistics policy requirements 

evolve, the concept for the UITDC ‘UID’ may shift. Initially, the concept is to provide a 

cataloging means to identify NIINs that meet the UID criteria, but which are NOT subject 

to a UIT program. UITDCs other than ‘UID’ represent UIT programs which have a 

tracking requirement established by either OSD (e.g., small arms) or the Services (e.g., 

Navy Depot Level Repairables). There is presently no logistics policy requirement for 

tracking UID items, not subject to UIT programs. 

7. IMPACT/INTERFACE: 

a. Data Content/Procedures/Automated Information Systems (AIS): 

(1) NEW UITDC:

(a) DOD Components may need to revise Component procedures/AIS 

to access and recognize the new FLIS UITDC code and provide for unique processing, as 

the presence of UITDC “UID” would mean the item is NOT subject to UIT requirements. 

(b) The existing Component mechanism for IMM assignment of 

FLIS codes to NIINs must address assignment of the new UITDC. A designated UIT 

point of contact is responsible for advising an IMM that a NIIN related to a UIT program 

requires assignment of a UITDC. Since items to be assigned the new UITDC ‘UID” are 

not, by definition, subject to a UIT program, the assignment of UITDC “UID” would 
 

8 of 8

ADC 172 

Attachment 

NOT fall under that same UIT umbrella of responsibility. Accordingly, Components 

must identify how the IMM is notified to assign UITDC ‘UID’ to a NIIN. Components 

must identify who is responsible for advising the IMM when the UITDC ‘UID’ is 

applicable to a NIIN. PDC 149 recommended Components coordinate this issue 

with both Component materiel management functional area and the Component 

UID POC. No negative comments were received, or concerns identified, during PDC 

149 staffing. 

(2) NEW 527D UID/RFID INDICATORS: 

(a) Storage activities which receive 527D Advance Receipt 

Information transactions may need to revise procedures and/or AIS to recognize and use 

the new 527D UID/RFID indicator. 

(b) Activities generating DS 527D Advance Receipt Information 

transactions should establish the necessary interface with contracting to enable inclusion 

of the new indicators indicating that the contract requires UID and/or passive RFID for 

the item. 

b. Interface:

(1) Component UID proponents and affected functional areas 

responsible for identifying materiel which falls under DOD UID policy requirements, and 

advising the IMM to assign the new UITDC for UID. 

(2) Wholesale and below wholesale logistics system modernization offices. 

(3) Materiel management functional area responsible for systematic 

creation of 527D Advance Receipt Information (ARI) transactions, to assure that the 

necessary contracting interface is in place to indicate that an item is subject to the 

contractual requirement for UID or RFID, and for inclusion of that information as a UID 

or RFID indicator in the 527D ARI transaction. 

(4) Interface with Component and DLIS cataloging function 

c. Publications: DOD 4000.25-M (DLMS); DOD 4000.39-M (FLIS), DOD 4140.1-R 

(which provides UID and UIT logistics policy); and applicable Service/Agency publications.

Enclosure
 

ADC 172 

Enclosure 

 

 September 7, 2005 

DLMSO 

MEMORANDUM FOR DIRECTORATE OF LOGISTICS INFORMATION MANAGEMENT 

 ATTN: DLIS-S (Ms. Linda Marvin) 

SUBJECT: Request to Add the Unique Item Tracking Designator Code (UITDC) to the 

 Federal Logistics Information System (FLIS) 

 

 The Unique Item Tracking (UIT) Designator is a code which was developed by the 

DoD Unique Item Tracking Committee in conjunction with the Defense Logistics Information 

Service (DLIS) to provide DoD Components a means to systematically identify that an item is 

subject to a DoD Unique Item Tracking program. Presently the UITDC is available to the 

Components on a compact disc-read only memory (CD-ROM) and on the web-based 

WEBFLIS. However the ultimate goal of the Unique Item Tracking Committee has been to 

have the UITDC available in the standard FLIS cataloging record for systematic access and for 

update by standard systematic transactional exchange. 

 Request DLIS initiate the necessary action to include the UITDC in the standard FLIS 

cataloging record. Inclusion of the UITDC in FLIS will support the policy requirement published in 

DoD 4140.1-R, DoD Supply Chain Materiel Management Regulation, May 2003, chapter 5, section 

C5.7.3.2.9.2.4 directing that DOD Components shall “Submit to the DLIS information necessary to 

record UIT program stock numbers and UIT designators for items in a UIT program.” Further, 

increased assignment and use of the UITDC is likely with the recent proposal for a new UITDC to 

identify National Stock Numbers which fall under the DOD criteria for unique identification (UID). 

 The Defense Logistics Management Standards Office submits this request on behalf of 

the DoD Unique Item Tracking Committee. The point of contact for this request is Ms. Mary 

Jane Johnson, Chair, Unique Item Tracking Committee, DSN 427-0677, commercial phone 

(703) 767-0677, email: Mary.Jane.Johnson@dla.mil. 

 

 //S// 

 EDUARDO VICENCIO 

 Lt Col, USAF 

 Acting Director 

 Defense Logistics Management 

 Standards Office 

Attachment 

 cc: 

ADUSD(L)SCI 

DOD Unique Item Tracking Committee 

DOD UID Program Office 

DLIS-D/DD (ATTN: Mr. Rick Maison) 

DLIS-X (ATTN: Ms. Deborah.Greger) 

DLMS Supply Process Review Committee 
 

ADC 172 

Encl 

 

FLIS CODE NAME: UIT Designator 

FORMAT: 3 position alphanumeric code 

PURPOSE: Used to indicate that an item requires DoD level unique item tracking (UIT) and to 

identify a DoD UIT program associated with the UIT requirement. 

AAA DoD Small Arms Serialization Program (DoDSASP) 

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Testing and Tracking System (RATTS) Program 

AAD Navy Depot Level Reparables (NDLR) Program 

AAE The Army Maintenance Management System (TAMMS) 

Equipment Data Base (TEDB) 

AAF Aviation Component Tracking Program 

 AAG Tritium Unique Item Tracking Program 

AAH Controlled Cryptographic Items (CCI) 

DoD UIT Committee to assign other codes as DoD UIT programs are identified.