1 of 9 

ADC 170 

Attachment 

APPROVED DLMS CHANGE (ADC) 170 

Inclusion of Data Supporting UID of Items in DLMS Supplements 180M, Material Returns 

Reporting and 870M, Materiel Returns Supply Status (Supply) 

1. ORIGINATOR: 

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

b. Sponsors:

(1) Supply Process Review Committee Chair: Ellen Hilert, DLMSO/J-6251, 703-767-0676 

(DSN 427), e-mail: Ellen.Hilert@dla.mil.

(2) Unique Item Tracking Committee Chair: Mary Jane Johnson, DLMSO/J-6251, 

703-767-0677 (DSN 427), e-mail: Mary.Jane.Johnson@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/Unique Item Tracking (UIT)

4. REQUESTED CHANGE: 

a. Title: ADC 170, Inclusion of Data Supporting UID of Items in DLMS Supplements 180M, 

Material Returns Reporting and 870M, Material Returns Supply Status 

b. Description of Change: This change updates DLMS supplements 180M and 870M to 

carry unique item identifier (UII) data for unique identification (UID) of assets. Component 

system changes which are required to support the integration of 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 Management Regulation, provide for unique item tracking (formerly called serial 

number tracking) for specific DOD UIT programs. The inclusion of UII data in the DLMS 
 

facilitates UIT for those items that fall under the UID policy criteria of ‘serial managed’ assets. 

Inclusion of the data in DLMS is intended to facilitate UIT by UII for DOD UIT programs. 

c. Procedures: 

(1) Previously Approved DLMS Change (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 available from the 

DLMSO Web site at: http://www.dla.mil/j-6/dlmso/eLibrary/changes/proposed.asp. 

 (3) Modify DLMS Supplements (DS) 180M and 870M. Mapping and associated notes for 

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

Version 4010. Changes will be carried over to XML equivalent transactions. DS 180M and 870M 

are intended to support the following data configuration. 

[1] The UIT 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 which may be required 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. 

5. REASON FOR CHANGE: 
3 of 9 

ADC 170 

Att 

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 

Property, Plant and Equipment and Operating Materials and Supplies portions of DOD financial 

statements. As the Financial policy and requirements for UID evolve, they may influence or drive 

future UID implementation in logistics transactions and systems. 

c. The UII terminology that had been carried in DS 180M and 870M 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 180M and 870M. 

d. This change supports an AIT enabled Automatic Return Item (ARI) program and promotes 

visibility of material in the pipeline. 

e. This change also includes administrative updates to DS 180M and 870M 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 180M and 870M.

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 proposal. This change establishes the transaction format, but does not provide 

procedural guidance for the use of the additional UID data content. DLA comments associated with 

previous PDC for requisition/release order processing is applicable to this change as well: The 

allocation of data elements in EDI transactions is innocuous. However, if the implementation of 

this concept comes with the expectation of standing up a new process to perpetuate UID data, we 

have some concerns. The middleware (known as See Beyond software or the eGATE) must be 

programmed how to handle any and all data passed through it. If new data is introduced to an 

interface as fundamental as the inbound orders and outbound MROs, we would require a significant 

period of time to sufficiently design, build, and test the changes. We have not even identified 

where to store such data due to the lack of any formal process documentation. Without a clearly 

stated process for the flow of data and expectations by all interface partners, there are obvious 

concerns on the BSM side for how this will work. 

7. IMPACT: 

a. AIS. 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. 

b. Publication(s): DOD 4000.25-M, DLMS, Federal IC 180M and 870M and 
 

corresponding DLMS Supplements. 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 180M and 870M as follows: 
5 of 9 

ADC 170 

Att 

Item

# 

Location DS 180M Revision Reason Federal IC 

Impact

1. DLMS 

Introductory 

Notes

Added new DLMS note 3 to read: 

3. 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 

2. DLMS 

Introductory 

Notes 

Changed former DLMS note 3 to DLMS note 4 and 

added ADC 170 and ADC 77 titles to list of DLMS 

Changes 

4. This revision to the DLMS Supplement 

incorporates Proposed DLMS Change (PDC) and 

Approved DLMS Change (ADC) 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 170, Inclusion of Data Supporting Unique 

Identification (UID) of Items in DLMS Supplements 

180M, Material Returns Reporting and 870M, Material 

Returns Supply Status 

Deleted former note 4.

Identifies DLMS 

Changes included in 

the DLMS 

Supplement 

No revision 

required 

3. 2/LQ01/58 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

4. 2/LQ01/58 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 
 

Item

# 

Location DS 180M Revision Reason Federal IC 

Impact

5. 2/N101/60 Add Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

6. 2/N9/180 Revised N9 Segment notes to read:

Federal Note:

Use the 2/N9/180 loop to provide Unique Identification 

(UID) information for the purpose of Unique Item 

Tracking (UIT). 

DLMS Notes:

1. Must use the 2/N9/180 loop in Material Returns 

Reporting (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. 

4. The entire 2/N9/180 loop is a DLMS enhancement. 

See introductory DLMS note 2a. 

Identifies the purpose 

2/N9/180 loop and 

explains use of 

batch/lot number. 

Revision 

required 

7. 2/N901/180 Deleted qualifier “LT” and revised DLMS Note for 

qualifier “BT”:

LT Lot Number 

BT Batch Number 

DLMS notes:

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

number identifying the production run. 

2. Use ‘BT’ in 2/N901/180 when UII or serial number does 

not apply for the item. 

Explains use of 

batch/lot number in 

2/N9/180 loop. 

“BT” and “LT” 

Qualifiers have been 

combined. Batch/lot 

are 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 

8. 2/N901/180 Revised DLMS note for qualifier “SE” to read:

SE Serial Number 

1. Use to identify the serial number (when code U3 is 

not used). Use this qualifier for unique item tracking 

based upon the serial number. 

2. DLMS enhancement. See introductory DLMS 

note 2a. 

Established data 

element for serial 

number distinct from 

UII data element. 

No revision 

required 
7 of 9 

ADC 170 

Att 

Item

# 

Location DS 180M Revision Reason Federal IC 

Impact

9. 2/N901/180 Added qualifier “U3” w/the following DLMS notes: 

U3 Unique Supplier Identification Number (USIN) 

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

Use this qualifier for unique item tracking based 

upon the UII. 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 2a. 

Identifies the Unique 

Item Identifier (UII) 

value. 

Revision 

required 

10. 2/N902/180 Modified Data Element from “Must Use” to “Used”

and added the following DLMS note:

DLMS Note: 

Use to indicate serial number when N901=SE.

Identifies the location 

of the serial number 

value when used. 

Revision 

required 

11. 2/N903/180 Opened N903 and added the following DLMS 

note:

DLMS Note: 

Use to indicate UII value when N901=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 
 

Item 

# 

Location DS 870M Revision Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Notes

Added new DLMS note 5 to read: 

5 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 

2. DLMS 

Introductory 

Notes

Changed former DLMS note 5 to DLMS note 6 and 

added ADC 170 title to list of DLMS Changes 

6. This revision to the DLMS Supplement (DS) 

incorporates Proposed DLMS Change (PDC) and 

Approved DLMS Change (ADC) listed. PDCs/ADCs 

are available from the DLMSO web site 

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

- ADC 170, Inclusion of Data Supporting Unique 

Identification (UID) of Items in DLMS Supplements 

180M, Material Returns Reporting and 870M, 

Material Returns Supply Status 

Identifies DLMS 

Changes included in 

the DLMS 

Supplement 

No revision 

required 

3. 1/N101/50 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

4. 2/REF01/87 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

5. 2/N101/90 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

6. 2/LQ01/145 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 
9 of 9 

ADC 170 

Att 

Item 

# 

Location DS 870M Revision Reason Federal IC 

Impact 

7. 2/REF01/300 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

8. 2/LQ01/330 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

qualifiers consistent 

with other DS. 

Revision 

required 

9. 2/LQ01/330 Updated DLMS note for qualifier “GQ”

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 

10. 2/REF/350 Revised REF Segment notes to read:

Federal Note:

Use the 2/REF/350 loop to provide Unique Identification 

(UID) information for the purpose of Unique Item 

Tracking (UIT). 

DLMS Notes:

1. Must use 2/REF/350 loop in Material Returns Supply 

Status 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. 

4. The entire 2/REF/350 loop is a DLMS enhancement. 

See introductory DLMS note 4a. 

Identifies the purpose 

2/REF/350 loop and 

explains use of 

batch/lot number. 

Revision 

required 

11. 2/RE01/350 Added Federal Note to read:

Use any code.

Administrative. 

DLMS Supplement 

authorizes specific 

Revision 

required 
 

Item 

# 

Location DS 870M Revision Reason Federal IC 

Impact 

qualifiers consistent 

with other DS. 

12. 2REF01/350 Deleted qualifier “LT” and revised DLMS Note for 

qualifier “BT”:

LT Lot Number 

BT Batch Number 

DLMS notes:

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

other number identifying the production run. 

2. Use ‘BT’ in 2/REF01/15350 when UII or serial number 

does not apply for the item. If both UII and serial number 

and batch/lot number is required, use REF01 for UII or 

serial number, and use REF04 for batch/lot number.

Explains use of 

batch/lot number in 

2/N9/180 loop. 

“BT” and “LT” 

Qualifiers have been 

combined. Batch/lot 

are 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 

13. 2/REF01/350 Revised DLMS note for qualifier “SE” to read:

SE Serial Number 

1. Use to identify the serial number (when code U3 

is not used). Use this qualifier for unique item 

tracking based upon the serial number. 

2. DLMS enhancement. See introductory DLMS 

note 4a. 

Established data 

element for serial 

number distinct from 

UII data element. 

No revision 

required 

14. 2/REF01/350 Added qualifier “U3” w/ the following DLMS notes: 

U3 Unique Supplier Identification Number (USIN) 

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

Use this qualifier for unique item tracking based 

upon the UII. 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 4a. 

Identifies the Unique 

Item Identifier (UII) 

value. 

Revision 

required 

15. 2/REF02/350 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 

16. 2/REF03/350 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 

Revision 

required 
11 of 9 

ADC 170 

Att 

Item 

# 

Location DS 870M Revision Reason Federal IC 

Impact 

REF02 reference 

number field). 

17. 2/REF04/350 Open 2/REF04/350 for use as follows: 

Add Federal note: 

Use any code. 

Add DLMS notes: 

1. Use REF04 to associate a batch/lot number 

with the UII or serial number identified in REF01. 

2. For DLMS use, only the following codes are 

authorized: 

BT Batch Number 

DLMS notes:

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

number or other number identifying the production 

run. 

2. Use ‘BT’ in REF04 when the associated UII or 

serial number is cited in REF01.

Provides for use of a 

batch/lot number in 

addition to associated 

UII or serial number, 

when applicable. 

Revision 

required.