IN REPLY 

REFER TO 

DLMSO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-622 1 

MEMORANDUM FOR: FINANCE PROCESS REVIEW COMMITTEE MEMBERS 

SUBJECT: Approved DLMS Change (ADC) 154, Inclusion of Data Elements Supporting 

Unique Identification (UID) of Items on Logistics Bills (DLMS Supplement 8 10L) 

(Staffed as PDC 154) (Finance) 

The attached change to DOD 4000.25-M, DLMS, is approved for implementation. The 

updated DLMS Supplement will be posted to the Defense Logistics Management Standards Office 

(DLMSO) Web site (http://www.dla.mil(j-6/dlmso/ICs/Default.htm) within 30 days from the above 

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

governing Federal Implementation Convention to the DOD Electronic Data Interchange Standards 

Management Committee, and the Federal Electronic Data Interchange Standards Management 

Coordinating Committee, and appiicabie working groups. 

Addressees may direct questions by email to DLMSO@dla.mil. Please include "ATTN: 

Finance PRC Chair" in the email subject line. Others must contact their Component's designated 

DLMS Finance Process Review Committee representative. 

Standards Office 

Attachment 
1 

ADC 154 

Attachment 

 ADC 154 

Inclusion of Data Elements Supporting Unique Identification (UID) of Items 

on Logistics Bills (DLMS Supplement 810L) (Finance) (Staffed by PDC 154) 

1. ORIGINATOR: 

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

DLMSO@dla.mil.

b. Sponsor: Chair, Finance Process Review Committee.

2. REFERENCES: 

 a. All Defense Logistics Management System (DLMS) Supplements (DS) listed in this 

memorandum are available at http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/x12.asp. 

Federal and DOD Implementation Conventions are available at 

http://fedebiz.disa.mil/cgi/advsearch.cgi. 

 b. UID policy and associated documentation is available at: http://www.acq.osd.mil/dpap/UID/.

3. FUNCTIONAL AREA: Primary: Finance 

4. REQUESTED CHANGE: 

a. Title: (ADC) 154, Inclusion of Data Elements Supporting Unique Identification (UID) of 

Items on Logistics Bills (DLMS Supplement 810L).

b. Description of Change: This change updates DLMS Supplement (DS) 810L Logistics 

Bill transactions to carry UII data. Component system changes which are required to support the 

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

the Components. 

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

(1) Update DLMS manual front matter as approved by Approved DLMS Change (ADC) 127: 

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 
 

 ADC 154 

Att 

2

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. 

Unique Item Identifier (UII) Type. A designator that identifies the specific structure and syntax 

of a type of UII. Specific examples of the UII Type are: Vehicle Identification Number (VIN), 

UID Construct I (UID1), UID Construct I (UID2). 

Unique Identification (UID) Construct I. This is a concatenated UII based upon serialization 

within the enterprise. The UII contains the IAC, EID, and serial number. 

Unique Identification (UID) Construct II. This is a concatenated UII based upon serialization 

within the part. The UII contains the IAC, EID, original part number, and serial number. For legacy 

material, a subset of UID Construct II (referred to as Construct IIA) contains a batch, lot number, or 

other production run number required for uniqueness of the serial number within the part. 

Acronyms and Abbreviations:

UII Unique Item Identifier 

UID Unique Identification 

 (2) Modify DLMS Supplements. Mapping and associated notes for DS 810L ANSI ASC X12 

format is identified in the table at paragraph 8. All changes are at the ANSI ASC X12 Version 

4010. Changes will be carried over to DLMS XML equivalent transactions.

5. REASON FOR CHANGE: DOD policy for the UID requires that the unique item identifier 

assigned to an asset be included on all transactions associated with the valuation of the asset. In 

support of this requirement, financial transactions within logistics must also identify the UII. This 

change incorporates the UII as currently defined within other DLMS transactions. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: The DOD has determined that to provide reliable and accurate data for 

accounting and property management, for tangible items, meeting specific criteria, will be 

uniquely identified and marked. Although specific requirements for use of the UII have not 

been defined, this ADC supports anticipated UID requirements by incorporating the UII in 

logistics bills (DS 810L). 

b. Disadvantages: Since not all related policy and requirements have been identified 

additional changes may be required. 
3 

ADC 154 

Att 

7. DLMSO DISPOSITION FOR PDC 154 COMMENTS: 

ORGANIZATION 

# COMMENT DLMSO DISPOSITION 

1 Both [SMAS and ABSS A&F] 

are legacy systems. We have a XML 

Waiver. 

OSD is not mandating the use of XML, but the 

elimination of MILS. DLMSO preference is the use of 

ASC X12. 

An XML waiver is not a DLMSO issue. 

2 IT1 Baseline Item Data (Invoice) 

includes the quantity but that loop is 

not mandatory. We believe the 

quantity is a mandatory field to 

match against the obligation details 

in our system. 

This quantity requirement is addressed within the 

transaction. 

The IT1 segment DLMS note 1 identifies that one 

iteration of IT1 must be used. Within the IT1 segment, 

which must be used, IT102 for quantity is marked ‘Must 

Use”, so the quantity must be cited when the IT1 

segment is used. 

DFAS 

Janice 

Herbel

Systems 

Manager for 

Standard 

Material 

Accounting 

System 

(SMAS) 

and 

Standard

Base Supply 

System 

Accounting 

and Finance 

(SBSS A&F)

3 The stock number and unit of issue

is also contained in that [IT1] loop 

and our systems use that data for 

matching. 

For Unit of Issue, this requirement is addressed within 

the transaction for unit of issue. 

The IT1 segment DLMS note 1 identifies that one 

iteration of IT1 must be used. Within the IT1 segment, 

IT103 for unit of measure is marked ‘Must Use”, so it 

must be cited. 

For stock number, 

IAW the note at 2/IT106/10, the data is to be perpetuated 

from the requisition order or issue document. Under 

DLMS, as a DLMS enhancement, the requisition and 

issue transactions provide for use of all of the qualifiers 

identified in the 810L at 2/IT1/06, with the exception of 

A3-Locally Assigned Control Number. Use of 

qualifiers other than ‘FS’ (NSN) are DLMS 

enhancements and are identified as such in the 

transaction. DLMS enhancements require 

coordination and business rules prior to use as noted 

in the associated DLMS note on page 1 of the 

transaction (DLMS note 6.a). The DS does state that 

the NSN (qualifier FS) must be used when known. 

(NOTE: 2/IT106/10 Qualifiers A1, A2, A4, FB, FT, 

MG, YP and ZZ already existed in DS 810L and were 

not added as part of PDC 154.) 

DLMSO will delete qualifier A3, and add the following 

DLMS note to 2/IT106/10 for consistency with other 

DLMS Supplements: 

“Use only one of codes A1, A2, A4, FB, FS, FT, MG, YP 

or ZZ to identify the material. Must use National Stock 

Number (NSN) (code FS) when known, except when 

appropriate brand name subsistence items are identified 

by the Subsistence Identification Number.” 
 

 ADC 154 

Att 

4

ORGANIZATION 

# COMMENT DLMSO DISPOSITION 

DLMSO will also revise the DLMS note for qualifier ZZ 

as follows for consistency with other DLMS 

supplements: 

ZZ Mutually Defined 

DLMS note: 

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

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

4 On N1 Name loop, there is a 

DODAAC. This is optional. Our 

systems will need this data to 

identify the buyer and process 

against the correct detail accounts.

The use of DUNS and DUNS+4 are DLMS 

enhancements and are identified as such by the 

associated DLMS note. Enhancements require 

coordination and business rules prior to use as noted in 

the DLMS note, accordingly they cannot be used unless 

coordinated/agreed to. However if such coordination is 

done between trading partners, they could be used in lieu 

of the DODAAC, therefore the DODAAC is not 

identified as ‘Must Use’ in DLMS transactions. 

5 FIABS is currently uses 80 column 

MILS Interfund compliant 

transactions which currently 

doesn't support additional positions 

for a UID. 

XML requirements were just sent to 

AFMC on the 23rd of December for 

analysis. 

UID is not intended to be supported by 80 column MILS 

transactions. 

The December 22, 2003 OSD memorandum, subject: 

Migration to DLMS and Elimination of MILS, requires 

action to eliminate the generation and transmission of 

transactions using the 80-character MILS formats. The 

memorandum notes that the constraints of the datalimited MILS formats prevent tracking an item 

throughout its life cycle across the entire supply chain 

using Unique Identifiers (UIDs). 

6 I don't know if FIABS, since it's 

owned by AFMC, also received a 

waiver or not. I'm checking. I have 

sent this requirement to AFMC for 

their comments as well. 

If the ‘AFMC’ referred to is the Air Force Material 

Command, Air Force has neither asked for, nor been 

granted, a waiver. 

DFAS requested a FIABS waiver which was granted 

through 1 October 2007. 

7 Of course funding issues will be high 

on the list. 

DFAS must address this issue. 

DFAS 

Mike 

Walker

DFASADWZ/DE 

8 Quick comments are since XML is 

replacing MILSBILLS and adding 

positions for the XML requirement 

add the UID requirement to the XML 

requirement or implement 

afterwards. 

DLMSO has not mandated the use of XML to replace 

MILSBILLS. 

The DLMS ASC X12 810L transaction is modified by 

this change to support UID, and these changes will be 

carried over to the equivalent DLMS XML 

transaction. 
5 

ADC 154 

Att 

ORGANIZATION 

# COMMENT DLMSO DISPOSITION 

9 Assignment and management of 

UIDs will also need to be addressed 

with the Logistics community. 

True. As noted in PDC 154, although specific 

requirements for use of the UII have not been defined, 

this change supports anticipated UID requirements by 

incorporating the UII in logistics bills. 

As also noted in the PDC, Component system changes 

required to support the integration of the UII data 

requirements are not identified in the change. 

DLMSO is revising approximately 25 DLMS logistics 

transactions to support transactional exchange of UID 

requirements. 

System changes required to support the integration of 

UID UII data must be addressed by the Components. 

DFAS 

Mike 

Walker

DFASADWZ/DE

1

0 

There are also other initiatives 

involved, such as CRISP, which 

appears to involve CAV II and 

AF Contractors and XML 

routing, DEAMS, and of course the 

other services will need to make the 

same changes. 

This change revises the DLMS 810L for 

transactional exchange supporting UID 

requirements. 

System changes required to support the integration 

of UID UII data must be addressed by the 

Components.

8. IMPACT:

Publication(s): DOD 4000.25-M, DLMS, DoD IC for 810L corresponding DLMS 

Supplement. If needed, revisions to DOD ICs will be submitted to the DOD Finance Functional 

Work Group for coordination/approval. Changes not identified in PDC 154 are highlighted in the 

table below. 

# 

Location DS 810L Revision Reason

1. DLMS 

Introductory 

Notes 

Added new DLMS note 7 to read: 

7. This transaction may be used to provide Unique Item Identifier 

(UII) information. Refer to the UID web at URL: 

http://www.acq.osd.mil/dpap/UID/ for DoD policy and business 

rules. 

To identify UID web URL 

2. DLMS 

Introductory 

Notes 

Added ADC 154 and ADC 77 titles to list of DLMS Changes to DLMS 

note 8.

- ADC 77, Air Force Unique Management Coding for Materiel 

Management Aggregation Code (MMAC) 

- ADC 154, Inclusion of Data Supporting UID of Items on Logistics 

Bills (DLMS Supplement 810L)

Identifies DLMS 

Changes included in 

the DLMS Supplement 
 

 ADC 154 

Att 

6

# 

Location DS 810L Revision Reason

3. 2/IT106/010 Delete qualifier A3

Add the following DLMS note at 2/IT106/10: 

“Use only one of codes A1, A2, A4, FB, FS, FT, MG, YP or ZZ to 

identify the material. Must use National Stock Number (NSN) 

(code FS) when known, except when appropriate brand name 

subsistence items are identified by the Subsistence Identification 

Number.” 

Delete code level DLMS note at qualifier ‘FS’. Use of NSN is 

identified in the DLMS note at 2/IT106/010 level as noted above

Revise the DLMS notes for qualifier ZZ: 

ZZ Mutually Defined 

DLMS note: 

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

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

Qualifier A3 deleted 

for consistency with, 

and to eliminate a 

disparity from, other 

DLMS Supplements 

(DS). 

DLMS notes updated 

for consistency with 

other DS. 

See “stock number’ 

discussion in the 

comments disposition 

at paragraph 7 (item # 

3) in this ADC. 

4. 2/REF/120 Revised REF Segment notes to read:

Federal Note:

Use the 2/REF/120 loop to provide Unique Identification (UID) 

information. 

DLMS Notes:

In general, use the 2/REF/120 loop to pass UID data in DLMS 

transactions. 

Identifies the purpose 

of providing the 

Unique Identification 

(UID) information 

5. 2/REF01/120 Add qualifier “U3” w/ the following DLMS note: 

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. 

Identifies the Unique 

Item Identifier (UII) 

value. 

6. 2/REF03/120 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. 
7 

ADC 154 

Att 

# 

Location DS 810L Revision Reason

7. 2/LQ01/310 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 highlight 

incorporation of 

Approved DLMS 

Change (ADC) 77, 

August 26, 2002. ADC 

77 is available at: 

http://www.dla.mil/j6/dlmso/eLibrary/change

s/approved.asp.