February 10, 2005 

MEMORAKDI'M FOR SL'I'PLY PROCESS 1: LVILU COMMITTEE MEMBERS 

SL~EMEC~P: .4ppro\.ed Dei'csnse Imgistics Management System (DLMS) Change (ADC) 153. 

Inclusion of Data Supporting Uniqi~c Identification (UID) of Items in DLMS 

Supplement 8671. Product Transfer L~nd Resale Report (Issue). and Administrative 

C']la!lp~s L. (Supp!~.) (Staffed by PI?(' ] 57) 

-7 I I nc aiiaciied ciiangc to DGD 4660.25-hI. iiiMS. is approved for irripierrie~iiatiori. The 

updated DLMS Supplement n-ill be posted to tlic Defense Logistics Management Standards Office 

(IlI.MS0) b'eb site (http: '~\-1\-~~-.dla.miI~,j-6~'dl11~soiICs!I)efault.htm) within 30 days from the above 

date for implementation planning. DLMSO nil i submit concurrently any necessary revisions to the 

go\.erning Federal Implementation Convention to tlic DOD Electronic Data Interchange Standards 

Management Committee. and the Federal Electl-onic Data Interchange Standards Management 

('oordinating Committee. and applicable \\.orliillg groups. 

Addressees ma! direct questions to the Dclkiist. Logistics Management Standards Office 

point of' contact. Ms. Mar! .lane Solinson. 703-707-0677. DSN 427-0677. or e-mail: 

\lar! ..Tane..lohnson tr dla.mil. Others must cont,ict their Component designated Supply Process 

p \c., ic.,; C'<;iiiiiiit:cc rq;-c5ci;:a:i., ,, 

i~ ector 

St,~ndards Office 

Attachment 

cc : 

ADI 'SD SC'I 

I1nique Item I racking Committee 

.io~nt Smaii ,Arms i oordinating i~rollp 

Jo~nt Phj sical In\ entor: b orking Group 
 

1 of 11 

ADC 153 

Attachment 

ATTACHMENT TO APPROVED DLMS CHANGE (ADC) 153 

Inclusion of Data Supporting UID of Items in DLMS Supplement 867I, Product Transfer and 

Resale Report (Issue) (Supply) 

1. ORIGINATOR: 

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

b. Sponsors:

(1) Unique Item Tracking Committee Chair: Mary Jane Johnson, DLMSO, 703-767-0677 

(DSN 427), E-mail: Mary.Jane.Johnson@dla.mil

(2) Supply Process Review Committee Chair: Ellen Hilert, DLMSO, 703-767-0676 (DSN 

427), E-mail: Ellen.Hilert@dla.mil

2. REFERENCES: 

 a. All DLMS Supplements (DS) listed in this memorandum are posted to the DLMSO Web site 

at http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/x12.asp. Federal Implementation 

Conventions (IC) are available at http://fedebiz.disa.mil/cgi/advsearch.cgi. 

 b. Unique identification (UID) policy and associated documentation is available at:

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

 c. Unique item tracking (UIT) policy is published in DoD 4140.1-R, DOD Supply Chain 

Materiel Management Regulation, Chapter 5, section C5.7.3. DOD 4140.1-R is available at: 

http://www.dtic.mil/whs/directives/corres/html/41401r.htm. 

3. FUNCTIONAL AREA: Primary: Supply

4. REQUESTED CHANGE: 

a. Title: ADC 153, Inclusion of Data Supporting Unique Identification (UID) of Items in 

DLMS Supplement 867I, Product Transfer and Resale Report (Issue) and Other Administrative 

Changes (Supply)

b. Description of Change: This change updates DLMS supplement 867I to carry the unique 

item identifier (UII) for unique identification (UID) of assets. Component system changes which 

are required to support the integration of UID UII data are not identified in this change and must 

be addressed by the Components. The DLMS and DOD 4140.1-R, DOD Supply Chain Materiel 
 

2 of 11 

ADC 153 

Att 

Management Regulation, provide for unique item tracking (formerly called serial number tracking) for 

specific DOD UIT programs. The inclusion of UID UII data in the DLMS facilitates UIT for those 

items that fall under the UID policy criteria of ‘serial managed’ assets. Initial inclusion of UID data 

in DLMS is intended to facilitate tracking by UII for DOD UIT programs, but it also positions DLMS 

transactions for wider use of UID if requirements are identified as UID logistics and financial 

implementation policies evolve. 

c. Procedures: Modify DOD 4000.25-M, DLMS Manual as follows: 

(1) ADC 127 updated DLMS manual front matter to include unique item identification related 

definitions and acronyms as provided below for ease of review: 

Terms and Definitions

Unique Identification (UID) of Items. The application of a set of data elements that is globally 

unique and unambiguous, ensures data integrity and data quality throughout life, and supports 

multifaceted business applications and users.

Unique Item Identifier (UII). An identifier used in unique item tracking programs to uniquely 

identify an individual asset used within DOD. The UII may be derived from a DOD-approved 

commercially-accepted identification methodology [e.g., Vehicle Identification Number (VIN)] or a 

composite structure defined by the DOD [refer to UID Construct 1 and UID Construct 2]. 

Formation of the UII relies upon two primary methods of serialization: (1) Serialization within the 

enterprise and (2) Serialization within the original part number of the enterprise. Regardless of which 

numbering system is used, the UII must include the Enterprise Identifier. Refer to OSD 

policy and supporting documentation for specific guidance at http://www.acq.osd.mil/dpap/UID/. Refer 

to MIL-STD-130L for specific guidance marking of U.S. Military property. 

Acronyms and Abbreviations:

UII Unique Item Identifier 

UID Unique Identification 

 (2) This ADC complements and supports PDC 147, November 4, 2004, DLMS Unique Item 

Tracking (UIT) Procedures – New Chapter 19 (Supply/UIT). PDC 147 is currently being revised for 

staffing as PDC 147A, based on discussion at the December 9, 2004, Unique Item Tracking 

Committee meeting. 

 (3) Modify DLMS Supplement (DS) 867I. Mapping and associated notes for ANSI ASC X12 

formats are identified in the table at paragraph 7 below. All changes are at the ANSI ASC X12 Version 

4010. Changes will be carried over to DLMS XML equivalent transactions. DS 867I intends to 

support the following data configuration. 

[1] The UIT loop (2/LX/280 loop) provides specific UID information and provides flexibility 

to accommodate tracking by UII or serial number. Providing for UIT by serial number is a transitional 

requirement until the Components fully implement the UID concept, and tracking by UII, across DOD. 

[2] The UIT loop is repeated for each item to be uniquely identified. 
3 of 11 

ADC 153 

Att 

5. REASON FOR CHANGE: 

a. OSD policy for UID states that the Unique Item Identifier (UII) shall be the primary or 

alternate pointer or key data element for the automated information systems (AIS). In support of 

this requirement, logistics transactions must identify the UII. This change incorporates the UII as 

defined under UID policy, within DLMS logistics exchange transactions. 

b. A goal of unique identification of items is to help achieve clean audit opinions on DOD 

financial statements. As the financial policy and requirements for UID evolve, they may influence 

future UID logistics policy, and implementation in logistics transactions and systems. 

c. The UII terminology that had been carried in DS 867I prior to this change was 

comparable to the serial number, but did not equate to a UII under the new DOD UID definition 

since a serial number lacks “uniqueness” when used alone. This change introduces the revised 

understanding of the term UII to DS 867I. 

d. This change also includes administrative updates to DS 867I for consistency with other DS. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Although specific logistics policy and requirements for implementing UID 

have not been defined, this ADC supports the UID concept by incorporating UID functionality in 

DS 867I.

b. Disadvantages: None specifically identified; however UID implementation policy is 

evolving and additional changes may be required to modify or enhance the transactional exchange 

as outlined in this change. 

7. COMMNTS DISPOSITION FOR PDC 157 COMMENTS: 

 COMPONENT COMMENT DISPOSITION 

1 ARMY 

Mr. Ken Deans 

Army SPRC rep

Headquarters, U.S. 

Army Materiel 

Command Asset Management & 

Distribution Branch 

On page 1 of PDC 157 it states 

in the description of Change 

that "Component system 

changes which are required to 

support the integration of UID 

UII data are not identified in 

this change and must be 

addressed by the Components." 

Have the reporting systems 

been notified of this 

requirement to support UID UII 

data? 

The object of this comment is not under 

DLMSO’s purview. Army must address this 

comment internally, and address their system 

implementation of the approved change. 
 

4 of 11 

ADC 153 

Att 

 COMPONENT COMMENT DISPOSITION 

2 ARMY 

Mr. Ken Deans 

Army SPRC rep

Headquarters, U.S. 

Army Materiel 

Command Asset Management & 

Distribution Branch 

Item 22, 2/REF01/290 

combines Batch Number and 

Lot Number under code BT and 

in the DLMS note it is 

explained that BT is used to 

identify both the batch number 

and lot number. Would it not 

be prudent to change qualifier 

‘BT Batch Number' to read "BT 

Batch Number/Lot Number'? 

This would allow the user to 

see at a glance that this is 

a multi-use field without having 

to read the DLMS note to 

ascertain the full extent of the 

field usage. 

Nonconcur. 

The suggested change would require a change at 

the American National Standards Institute 

(ANSI) Accredited Standards Committee (ASC) 

X12 level. However, since ANSI ASC X12 has 

separate qualifiers for Batch (BT) and for Lot 

(LT), it is unlikely they would change BT- Batch 

to represent batch/lot. 

DLMSO made this change for DLMS 

transactions to eliminate a disparity between the 

AIT identification of batch/lot data and the 

DLMS transaction identification of the data since 

AIT is the preferred method for introducing 

batch/lot data for system and transaction use. 

Batch/lot is one data field in DOD AIT 

standards. Prior to this change, batch and lot had 

been portrayed as two separate data fields in 

DLMS, thereby creating a disconnect between 

the AIT and DLMS portrayal of the data.

8. IMPACT: 

a. Automated Information Systems. Component system changes required to support the 

integration of UID UII data are not identified in this change and must be addressed by the 

Components. 

b. Publication(s): DOD 4000.25-M, DLMS, Federal IC 867I and corresponding DLMS 

Supplement. If needed, revisions to Federal ICs will be submitted to the EDISMC/Logistics 

Functional Work Group for coordination/approval. Revise Federal IC and DS for 867I as follows 

(administrative changes from PDC 157 are identified by highlighted text): 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes

Revise DLMS note 1:

1. Storage organizations use this transaction set to report 

material issues to Inventory Control Points (ICPs) or 

Integrated Material Managers (IMMs). This transaction 

encompasses functionality of MILSTRAP DI Code D7_. 

Administrative update No revision 

required 
5 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

2. DLMS Introductory 

Notes 

Added new DLMS note 6 to read: 

6. This transaction may be used to provide Unique 

Item Identifier (UII) information. Refer to the Unique 

Identification (UID) web at URL: 

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

and business rules. 

To identify that UID 

data can be conveyed 

by this transaction, 

and the UID web URL 

No revision 

required 

3. DLMS 

Introductory 

Notes 

Added DLMS note 7 and ADCs to list DLMS Change 

This revision to the DLMS Supplement incorporates 

Proposed DLMS Change (PDCs) and Approved 

DLMS Changes (ADCs) listed. PDCs/ADCs are 

available from the DLMSO Web site 

http://www.dla.mil/j-6/dlmso/Changes. 

- ADC 77, Air Force Unique Management 

Coding for Materiel Management 

Aggregation Code (MMAC) 

- ADC 153, Inclusion of Data Supporting Unique 

Identification (UID) of Items in DLMS Supplement 

867I, Product Transfer and Resale Report (Issue), 

and Administrative Changes (Supply) 

Identifies DLMS 

Changes included in 

the DLMS 

Supplement 

No revision 

required 

4. 1/N101/080 Revised Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS.

Revision 

required 

5. 2/PTD01/010 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

6. 2/PTD01/010 Add DLMS note:

For DLMS use, only the following codes are 

authorized:

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

No impact 

7. 2/DTM01/020 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 
 

6 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

8. 2/DTM/020 Add DLMS note:

For DLMS use, only the following codes are 

authorized: 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

No impact 

9. 2/REF01/030 Revised Federal Note to read:

Use any code. 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS.

Revision 

required 

10. 2/REF01/030 Code ZZ-Mutually defined, revised DLSM notes to 

read:

1. Use to identify nonstandard material when all other 

authorized codes do not apply or cannot be determined 

(includes management control numbers and locally 

assigned control numbers). May be used for DLSS-toDLMS conversion when the translator cannot determine 

a more appropriate code. 

2. DLMS enhancement; see introductory DLMS note 

5a.

Administrative update No impact 

11. 2/REF04/030 Add Federal Note: 

Use any code. 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS.

Revision 

required 

12. 2/REF04/030 Add DLMS note:

For DLMS use, only the following codes are 

authorized:

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

No impact 

13. 2/N101/050 Revised Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS.

Revision 

required 
7 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

14. 2/N103/050 Add UR - Uniform Resource Locator with DLMS 

notes:

UR Uniform Resource Locator (URL) 

DLMS Note: 

1. Use when appropriate to identify the Component 

UIT registry. 

2. DLMS enhancement; see introductory DLMS note 5a. 

For consistency with 

DLMS UIT capability 

added to DS 140B 

Revision 

required 

15. 2/QTY01/110 Add Federal note:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

Revision 

required 

16. 2/QTY01/110 Add DLMS note:

For DLMS use, only the following codes are 

authorized:

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

No impact 

17. 2/LQ01/270 Revised Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS.

Revision 

required 

18. 2/LQ01/270 Revise DLMS notes:

1. Use either code 99 or A1 (but not both), except for 

ammunition where both codes may be used. (Use of both 

codes for ammunition is a DLMS enhancement (see 

introductory DLMS note 5a.). 

2. For DLMS use, only the following codes are authorized: 

(Use of both codes for ammunition is a DLMS enhancement 

(see introductory DLMS note 5a. )

Administrative. 

Corrects existing 

DLMS notes 1 and 2. 

No impact 
 

8 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

19. 2/LQ01/270 Add qualifier GQ, Group Qualifier Code, as 

follows: 

GQ Group Qualifier Code 

DLMS Note: Use to identify the MMAC for 

NSNs to be managed by a specific manager (i.e., 

system, program, aggregation, selected FSC, 

technology group). This is an Air Force-unique 

data element, meaningful to the Air Force only. 

Non-Air Force Components perpetuate without 

action. 

A data maintenance action was approved in 

version 5010. The approved code/name is 

“MAC-Materiel Management Aggregation code”. 

The code source is identified as the Air Force 

Manual (AFMAN) 23-110, Volumes 1 and 2. 

Administrative 

update to 

incorporate 

ADC 77

No impact 

20. 2/LX/280 Add new Federal note 1.

1. Use the 2/LX /280 loop to provide Unique Identification 

(UID) information for the purpose of Unique Item Tracking 

(UIT). 

2. Use the LX segment as a counter to identify the number of 

2/LX/280 loop iterations in the transaction set.

Identifies the purpose 

2/LX/290 loop 

Revision 

required 

21. 2/LX/280 Revise and add LX segment DLMS notes:

1. Must use the 2/LX/280 loop when the item identified 

in the 2/N1/310 segment is subject to a UIT program to 

identify the unique item identifier (UII) or serial 

number. 

2. The 2/LX/280 loop is repeated for each item to be 

uniquely identified and provides flexibility to 

accommodate tracking by UII or serial number. 

3. May use the 2/LX/280 loop to provide batch/lot 

number information 

4. The entire 2/LX//280 loop is a DLMS enhancement. 

See introductory DLMS note 5a. 

Identifies the purpose 

2/LX/290 loop 

No impact 
9 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

22. 2/REF/290 Revised REF Segment notes to read:

Federal Note:

Use the 2/REF/290 segment to provide Unique 

Identification (UID) information. 

DLMS Notes:

1. Must use the 2/REF/290 loop in Product Transfer and 

Resale Report (Issue) transactions when the item 

identified is subject to UIT requirements. 

2. This transaction will support item identification based 

upon the UII or the serial number. 

3. This transaction also provides for use of a batch/lot 

number, when applicable. 

4. Use multiple iterations of 2/REF/290 segment within 

the 2/LX/280 loop, to provide identifying information for 

an item as needed. 

Identifies the purpose 

2/REF/290 segment. 

Revision 

required 

23. 2/REF01/290 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

Revision 

required 

24. 2/REF01/290 Add DLMS note:

For DLMS use, only the following codes are 

authorized: 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

No impact 

25. 2/REF01/290 Deleted qualifier “LT” and revised DLMS Note for 

qualifier “BT”:

LT Lot Number 

BT Batch Number 

DLMS note:

1. Use to identify the manufacturer's batch/lot 

number or other number identifying the production 

run. 

2. DLMS enhancement. See introductory DLMS 

note 5a.

 “BT” and “LT” 

Qualifiers have been 

combined. Batch/lot 

is one field in DOD 

AIT standards. This 

change eliminates a 

disconnect between 

AIT use of batch/lot as 

one field, and DLMS 

portrayal of the data 

as two separate data 

fields. 

No revision 

required 
 

10 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

26. 2/REF01/290 Revised DLMS note for qualifier “SE” to read:

SE Serial Number 

1. Use to identify the serial number. Place serial 

number value in REF02. 

2. DLMS enhancement. See introductory DLMS 

note 5a. 

Established data 

element for serial 

number distinct from 

UII data element. 

No revision 

required 

27. 2/REF01/290 Add qualifier “U3” w/ the following DLMS notes: 

U3 Unique Supplier Identification Number 

1. Use to identify the UII. Place UII value in REF03. 

An ANSI data maintenance request has been 

prepared to request a new code qualifier for Unique 

Item Identifier for future use. 

2. DLMS enhancement. See introductory DLMS 

note 5a. 

Identifies the Unique 

Item Identifier (UII) 

value. 

Revision 

required 

28. 2/REF02/290 Modified Data Element from “Must Use” to “Used”

and added the following DLMS note:

DLMS Note: 

Use to indicate serial number when REF01=SE. 

Identifies the location 

of the serial number 

value when used. 

Revision 

required 

29. 2/REF03/290 Opened REF03 and added the following DLMS 

note:

DLMS Note: 

Use to indicate UII value when REF01=U3.

Identifies the location 

of the UII value when 

used. 

Per DOD policy, the 

DOD UID can be up to 

78 characters. To 

allow for the longer 

length, the UII value is 

mapped to the REF03 

ANSI text field (vice 

the shorter REF02 

reference number 

field). 

Revision 

required 

30. 2/DTM01/300 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

Revision 

required 
11 of 11 

ADC 153 

Att 

Item 

# 

Location DS 867I Revision Reason

Federal 

IC 

Impact

31. 2/DTM01/300 Add DLMS note:

For DLMS use, only the following codes are 

authorized: 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

No impact 

32. 2/DTM01/300 Codes ‘094’ and ‘512’: Delete Federal note and add as 

DLMS note 1:

094 Manufacture 

DLMS note: 

1. Use to identify the date of manufacture for the 

material identified. 

2. DLMS enhancement. See introductory DLMS note 

5.a. 

512 Warranty Expiration 

DLMS note: 

1. Use to identify the warranty expiration date 

associated with the materiel reported.

2. DLMS enhancement. See introductory DLMS note 

5.a. 

Administrative. 

Makes current Federal 

note a DLMS note 

since codes ‘094’ and 

‘512’ are no longer 

specified at Federal 

level. 

Revision 

required 

33. 2/N101/310 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

Revision 

required 

34. 2/N101/310 Add DLMS note:

For DLMS use, only the following codes are 

authorized: 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

No impact 

35. 2/N103/310 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

Revision 

required 

36. 2/N103/310 Add DLMS note:

For DLMS use, only the following codes are 

authorized: 

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers, consistent 

with other DS. 

No impact