DEFENSE LO< !STICS AGENCY 

HEAD0 74RTERS 

8725 JOHN J INGMAN ROAD 

FORT BELVOIR. \; ?GINIA 22060-6221 

January 12,2005 

MEMORANDUM FOR SUPPLY PROCESS R1:VIEW COMMITTEE MEMBERS 

SUBJECT: Approved DLMS Change (ADC) 148, Inclusion of Data Supporting Unique 

Identification (UID) of Items in DLMS 527D Due-in, Advance Receipt, Due 

Verification and DLMS 527R Receipt, Inquiry, Response and MRA (Supply) 

(Staffed as PDC 1 14) 

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.mi1/~j-6/dlmso/ICs/Default.htm) within 30 days from 

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

:evisims te the g~verning Federa! !mp!ementation Cmventim to the DO9 E!ectrmic Data 

Interchange Standards Management Committee. and the Federal Electronic Data Interchange 

Standards Management Coordinating Committee, and applicable working groups. 

Addressees may direct questions to the DLMSO point of contact, Ms. Mary Jane Johnson, 

703-767-0677, DSN 427-0677; email Mary.Jane.Johnson@dla.mil. Others must contact their 

Component designated Supply Process Review Committee representative. 

/ hirector / / i/ Defense t&gdics Management 

Standards Office 

Attachment 

cc: 

ADUSD(L)SCI 

ADUSD AT&L UID Program Office 

DOD LOGISTICS AIT OFFICE 

UNIQUE ITEM TRACKING COMMITTEE 

JOINT SMALL ARMS COORDINATING GROUP 

JOINT PHYSICAL INVENTORY WORKING GROUP 
1 of 15

ADC 148

Attachment

ATTACHMENT TO ADC 148

Inclusion of Data Supporting Unique Identification (UID) of Items in DLMS 527D Due-in, Advance 

Receipt, Due Verification and DLMS 527R Receipt, Inquiry, Response and MRA 

1. ORIGINATOR:

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

b. Sponsors:

(1) Unique Item Tracking Committee (UITC) Chair/MILSTRAP Administrator: Ms. 

Mary Jane Johnson, DLA DLMSO/J-6251, DLMSO, 703-767-0677 (DSN 427). 

(2) Supply Process Review Committee, Chair: Ms. Ellen Hilert, DLA DLMSO/J-6251, Defense 

Logistics Management Standards Office (DLMSO), 703-767-0676 (DSN 427).

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. UID policy and associated documentation is available at: http://www.acq.osd.mil/dpap/UID/.

3. FUNCTIONAL AREA: Primary: Supply

4. REQUESTED CHANGE:

a. Title: Inclusion of Data Supporting Unique Identification (UID) of Items in DLMS 527D Duein, Advance Receipt, Due Verification and DLMS 527R Receipt, Inquiry, Response and MRA.

b. Description of Change: This change updates DLMS supplements 527D and 527R 

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

Component system changes which are required to support the integration of the 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. 

Initial inclusion of the data in DLMS is intended to facilitate UIT by UII for DOD UIT programs, but it 

also positions DLMS transactions for wider use of UID if requirements are identified as UID logistics 
2 of 15

ADC 148

Att

and financial implementation policies evolve. 

c. Procedures: Modify DOD 4000.25-M, Defense Logistics Management System Manual as 

follows:

(1) This approved change modifies the Terms and Definition for Issuing Agency Code (IAC) 

previously approved by Approved DLMS Change (ADC) 127 as follows:

Issuing Agency Code (IAC). The IAC represents the registration authority that issued the enterprise 

identifier. The value for the IAC is assigned by the Registration Authority for ISO/IEC 15459-2, 

Registration Procedures. The current Registration Authority of ISO/IEC 15459-2 is NEN – Nederlands 

Normalisatie-instituut. The IAC can be derived from the data qualifier for the enterprise identifier 

and does not need to be marked on the item or carried in the DLMS transaction. 

Rationale for change: (1) The deleted sentence is procedural and should not be part of the IAC 

definition and (2) the enterprise identification will be in some, but not all, DLMS transactions. 

(2) 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

Enterprise Identifier (EID). An activity identifier code assigned to the entity that is responsible for 

assigning the unique item identification to an item. EID codes are uniquely assigned by a registration (or 

controlling) authority (e.g., Dun & Bradstreet’s Data Universal Numbering System (D-U-N-S), European 

Article Number (EAN).Uniform Code Council (UCC) System, and Allied Committee 135).

Issuing Agency Code (IAC). Replace ADC 127 IAC definition as noted in paragraph 4.c(1) above.

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

ADC 148

Att

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:

EID Enterprise Identifier

IAC Issuing Agency Code

UII Unique Item Identifier

UID Unique Identification

 (3) This PDC 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. 

 (4) Modify DLMS Supplements (DS) for 527D and 527R. 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 XML equivalent transactions. DS 527D and 

527R are intended to support the following data configuration. 

[1] At the transaction level, existing material identification is retained, e.g. NSN or part 

number/CAGE.

[2] The UIT loop (2/REF/250 loop) provides specific UID information allowing flexibility to 

identify the item by either the UII or the serial number. The transaction structure will accommodate 

DLMS unique item tracking by serial number. This is a transitional requirement which may be employed

until the Components fully implement tracking by UII across DOD.

[3] Additional data may be related to the primary number but are not mandatory. The 

following related data elements are permitted: Original Part Number; New Part Number; Serial Number 

(to be used, if needed, when the UII is the primary identification number); Batch/Lot; Enterprise ID and/or 

Manufacturer ID; and UII Type. In addition, if the Issuing Agency Code is needed for the AIS system, it 

may be derived from the ANSI X12 qualifier which identifies the type of EID used when EID is carried in 
4 of 15

ADC 148

Att

the transaction (e.g., the ANSI X12 qualifier for DUNS number is “1” from which the corresponding ISO 

standard IAC value of “UN” may be derived). 

[4] The UIT loop is repeated for each item to be identified.
5 of 15

ADC 148

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 and provides maximum flexibility. 

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 

implementation in logistics transactions and systems. 

c. The UII terminology that had been carried in DS 527D and DS 527R 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 527D and 527R.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) Although specific logistics requirements for implementing UID have not been defined, 

this PDC supports the UID concept by incorporating UID functionality in DS 527D and DS 527R. This 

change is intended to provide maximum flexibility in transmitting related UID/UIT data requirements. 

(2) Provides capability for UIT by UII in DS 527D and DS 527R.

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. 
6 of 15

ADC 148

Att

7. IMPACT: Publication(s):

a. Automated Information Systems. 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. Publications. DOD 4000.25-M, DLMS, Federal IC for 527D and 527R and corresponding 

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

Functional Work Group for coordination/approval.

(1) Revise Federal IC and DS for 527D as follows (highlighted text shows administrative 

changes not identified in PDC 114). No comments were received to PDC 114.

Item

#

Location DS 527D 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

Added ADC 149 title to list of DLMS Changes to DLMS 

note 6.

-ADC 149, Inclusion of Data Supporting UID of Items 

in DLMS 527D Due-in, Advance Receipt, Due 

Verification and DLMS 527R Receipt, Inquiry, 

Response and MRA (Supply)

Identifies DLMS 

Changes included in 

the DLMS Supplement

No revision 

required

3 2/RCD/040 Revise DLMS segment level note 3 as follows:

3. For due-in transactions, use the 2/QTY/310 loop to 

stratify the RCD due-in quantity by receiving location, 

when desired. When the entire RCD quantity is due in 

to one location, specify the receiving location in the 

2/N1/210 loop. NOTE: UIT/UID information cannot be 

provided for quantities stratified by the 2/QTY/310 

loop.

Clarifies that UID/UIT 

data cannot be

provided for due-in 

transaction quantities 

which are stratified by 

different receiving 

locations in the 

2/QTY/310 loop.

No revision 

required

4 2/N907/090 Add Federal and DLMS notes as follows:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following 

codes are authorized.

Administrative. 

DLMS Supplements 

authorize specific 

qualifiers.

Revision 

required adding 

Federal note.
7 of 15

ADC 148

Att

Item

#

Location DS 527D Revision Reason

Federal

IC

Impact

5 2/LQ01/130 Revise DLMS notes 1 and 2 as follows:

DLMS Note: 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 4a).

2. For DLMS use, only the following codes are 

authorized. (Use of both codes for ammunition is a 

DLMS enhancement (see introductory DLMS note 4a).

Administrative change 

to fix existing DLMS 

notes

No revision 

required

6 2N106/210 Add Federal and DLMS notes as follows:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following 

codes are authorized.

Administrative. 

DLMS Supplements 

authorize specific 

qualifiers.

Revision 

required adding 

Federal note.

7 2/REF/250 Revised REF Segment notes to read:

Federal Note:

Use the 2/REF/250 loop to provide Unique 

Identification (UID) information for the purpose of 

Unique Item Tracking (UIT).

DLMS Notes:

1. Must use the 2/REF/250 loop in due-in and advance 

receipt information transactions when the item 

identified in LIN03 of the 2/LIN/010 segment is subject 

to UIT requirements. 

2. This transaction will support item identification 

based upon the UII or the serial number. Data 

elements associated with the UII may be identified 

separately. Use the appropriate data elements to 

satisfy the desired functionality. 

3. When both UII or serial number and batch/lot 

number are required for the item, enter the UII or serial 

number in 2/REF/250 and enter the batch/lot number 

in 2/N9/270. When the batch/lot number is required, 

but the UII/serial number does not apply, enter the 

batch/lot number in 2/REF/250.

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

See introductory DLMS note 4a.

Identifies the purpose 

of providing the Unique 

Identification (UID) 

information and 

explains use of 

batch/lot number in the 

2/REF/250 loop.

Revision 

required
8 of 15

ADC 148

Att

Item

#

Location DS 527D Revision Reason

Federal

IC

Impact

8 2/REF01/250 Revised DLMS note for qualifier “BT” and delete 

qualifier “LT”:

BT Batch Number

1. Use to identify the batch, lot, or production run. 

2. Use ‘BT’ in 2/REF/250 when UII or serial number 

does not apply for the item. When UII or serial number 

 is required in addition to batch/lot number, enter the UII

or serial number in 2/REF/250 and enter the batch/lot 

number in 2/N9/270.

Deleted the following qualifier:

LT Lot Number

1. Explains use of 

batch/lot number in 

2/REF/250 loop.

2. “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

9 2/REF/01/250 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.

Identifies the purpose 

of serial number during 

Unique Item Tracking 

(UIT) 

No revision 

required

10 2/REF01/250 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 

4a.

Identifies the Unique 

Item Identifier (UII) 

value.

No Revision 

required

11 2/REF02/250 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
9 of 15

ADC 148

Att

Item

#

Location DS 527D Revision Reason

Federal

IC

Impact

12 2/REF03/250 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

13 2/G62/260 Revised Federal Segment note to read:

Federal Note:

Use to identify dates related to data represented in 

2/REF/250.

Administrative Revision 

required 

14 2/N9/270 Add DLMS segment level note:

DLMS enhancement. See introductory note 4.a.

Administrative to 

identify segment is an 

enhancement.

No revision 

required 

15 2/N901/270 Revised Data Element DLMS note 1 and added the 

following qualifiers w/ DLMS notes: 

DLMS Note:

1. The following codes are used to identify the 

characteristics related to the item designated in the 

2/REF/250 segment.

PM Part Number

DLMS Note:

Use to identify the part number of the item identified 

by UII or serial number. Use to identify the original 

part number when associated with a UII. When this 

differs from the current part number use N901 to 

identify the new part number. An ANSI data 

maintenance request has been prepared to request 

a new code qualifier for Original Part Number for 

future use.

T0 Dealer Type Identification 

DLMS Note:

Use to identify the UII type per UID guidance e.g., 

VIN, UID1, UID2, etc.

QW New Part Number

DLMS Note:

Use to indicate the current part number when 

different from the original part number 

Provides capability for 

conveying additional 

UID information.

No Revision 

required
10 of 15

ADC 148

Att

Item

#

Location DS 527D Revision Reason

Federal

IC

Impact

16 2/N901/270 Revised DLMS notes for qualifiers “BT” and “SE” 

BT Batch Number

DLMS Note:

Use to identify the batch, lot, or production run when 

UII or serial number is identified in 2/REF/250.

SE Serial Number

DLMS Note:

Use to identify the serial number (when code U3 is 

used in REF01).

Batch and lot numbers 

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

17 2/N901/270 Deleted the following qualifier:

LT Number

Batch and Lot Number 

have been combined. 

See ‘BT’ above.

No Revision 

required

18 2/N901/270 Deleted the following qualifier and DLMS notes: 

W5 Inspector Identification Number

DLMS notes: 

1. Use to identify the code assigned by each 

inspection agency to an inspector.

2. DLMS enhancement; see introductory DLMS 

note 5a.

No business case has 

been identified to 

DLMSO for use of 

“W5” Inspector 

Identification. 

No Revision 

required

19 2/N1/280 Revise Federal segment level note to read:

Use to identify UIT information as needed.

Add DLMS segment level note:

DLMS enhancement. See introductory DLMS note 

4.a. 

Administrative Revision 

required to 

Federal note.

20 2/N101/280 Revised DLMS note for qualifier “MF” and added 

qualifier “IAT” w/ DLMS note:

MF Manufacture of Goods

DLMS Note:

Use to identify the manufacturer of the identified 

item.

IAT Party Executing and Verifying

DLMS Note:

Use to indicate the Enterprise Identifier (EID) 

responsible for the UII. An ANSI data maintenance 

request has been prepared to request a new code 

qualifier for Enterprise identifier for future use.

Clarifies use of ‘MF’ 

as manufacturer of 

identified item, and 

adds the Enterprise 

Identifier for the item. 

Both are provided here 

for flexibility. There 

may be exception 

conditions where these 

will not be identical.

No revision 

required
11 of 15

ADC 148

Att

Item

#

Location DS 527D Revision Reason

Federal

IC

Impact

21 2/N103/280 Added Data Element notes:

Federal Note:

Use any code.

DLMS Note:

1. For DLMS use, the following codes are authorized.

2. The value of the UID Issuing Agency Code (IAC)

may be derived from the qualifier used for the

Enterprise Identifier.

Provides information 

that the IAC can be 

derived from the 

enterprise identifier 

ANSI qualifier.

Revision 

required

22 2/N103/280 Added qualifiers “8” and “41” w/ DLMS notes, and

added DLMS note to qualifiers ‘1’, ‘9’, ‘10’, and ‘33’

1 D-U-N-S Number, Dun & Bradstreet

DLMS Note:

Corresponds to IAC 'UN'.

8 UCC/EAN Global Product Identification Prefix

DLMS Note:

Corresponds to IAC '0-9'.

9 D-U-N-S+4, D-U-N-S Number with Four 

Character Suffix

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

Corresponds to IAC 'LD'.

33 Commercial and Government Entity (CAGE)

DLMS Note:

Corresponds to IAC 'D'.

41 Telecommunications Carrier Identification Code

DLMS Note:

Corresponds to IAC 'LB' (ANSI T1.220, Commercial

Telecommunications Standards).

Adds 2 new qualifiers. 

Adds DLMS notes to 

all qualifiers to address 

how the ANSI 

qualifiers, when used 

for the enterprise 

identifiers, correspond 

to the IAC.

Revision 

required 

23 2/QTY/310 Add DLMS segment level note 3.

3. UIT/UID information cannot be provided for 

quantities stratified by the 2/QTY/310 loop.

To document that UIT/UID 

information cannot be 

provided for stratified 

quantities under the 

2/QTY/310 loop.

No revision 

required-
12 of 15

ADC 148

Att

(2) Revise Federal IC and DS for 527R as follows (highlighted text shows administrative 

changes not identified in PDC 114). No comments were received to PDC 114.

Item

# Location DS 527R Revision Reason

Federal

IC

Impact

1 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 to 

identify UID web URL

No revision 

required

2 DLMS 

Introductory 

Notes

Added ADC 149 title to list of DLMS Changes to DLMS 

note 7.

- ADC 149, Inclusion of Data Supporting UID of Items 

in DLMS 527D Due-in, Advance Receipt, Due 

Verification and DLMS 527R Receipt, Inquiry, 

Response and MRA (Supply)

Identifies DLMS 

Changes included in 

the DLMS Supplement

No revision 

required

3 2/N106/210 Add Federal and DLMS notes as follows:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following 

codes are authorized.

Administrative. 

DLMS Supplements 

authorize specific 

qualifiers.

Revision 

required adding 

Federal note

4 2/REF/250 Revised REF Segment notes to read:

Federal Note:

Use the 2/REF/250 loop to provide Unique 

Identification (UID) information for the purpose of 

Unique Item Tracking ( UIT).

DLMS Notes:

1. Must use the 2/REF/250 loop in receipt and material 

receipt acknowledgement transactions when the item 

identified in LIN03 of the 2/LIN/010 segment is subject 

to UIT requirements. 

2. This transaction will support item identification 

based upon the UII or the serial number. Data 

elements associated with the UII may be identified 

separately. Use the appropriate data elements to 

satisfy the desired functionality. 

3. When both UII or serial number and a batch/lot number 

are required for the item, enter UII or serial number in 

2/REF/250 and enter the batch/lot number in 2/N9/270. When 

batch/lot number is required, but UII/serial number does not 

apply, enter the batch/lot number in 2/REF/250.

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

See introductory DLMS note 5a.

Identifies the purpose 

of providing the Unique 

Identification (UID) 

information and

explains use of 

batch/lot number in the 

2/REF/250 loop. 

Revision 

required
13 of 15

ADC 148

Att

Item

# Location DS 527R Revision Reason

Federal

IC

Impact

5 2/REF01/250 Revised DLMS note for qualifier “BT” and delete 

qualifier “LT”:

BT Batch Number

1. Use to identify the batch, lot, or production run. 

2. Use ‘BT’ in 2/REF/250 when UII or serial number 

does not apply for the item. When UII or serial number 

 is required in addition to batch/lot number, enter the 

UII or serial number in 2/REF/250 and enter the

 batch/lot number in 2/N9/270.

Deleted qualifier “LT”:

LT Lot Number

1. Explains use of 

batch/lot number in 

2/REF/250 loop.

2. “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

6 2/REF/01/250 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.

Identifies the purpose 

of serial number during 

Unique Item Tracking 

(UIT) 

No revision 

required

7 2/REF01/250 Add qualifier “U3” w/ the following DLMS note:

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 

4a.

Identifies the Unique 

Item Identifier (UII) and 

cites placement for UII 

value.

No revision 

required

8 2/REF02/250 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 

when used.

Revision 

required
14 of 15

ADC 148

Att

Item

# Location DS 527R Revision Reason

Federal

IC

Impact

9 2/REF03/250 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

10 2/G62/260 Revised Federal Segment note to read:

Federal Note:

Use to identify dates related to data represented in 

2/REF/250.

Administrative Revision 

required 

11 2/G6201/260 Add Federal and DLMS notes as follows:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following 

codes are authorized.

Administrative. 

DLMS Supplements 

authorize specific 

qualifiers.

Revision 

required adding 

Federal note.
15 of 15

ADC 148

Att

Item

# Location DS 527R Revision Reason

Federal

IC

Impact

12 2/N901/270 Revised Data Element DLMS note 1 and added the 

following qualifiers w/ DLMS notes: 

DLMS Note:

1. The following codes are used to identify the 

characteristics not defined in the 2/REF/250 segment.

PM Part Number

DLMS Note:

Use to identify the part number of the item identified 

by UII or serial number. Use to identify the original 

part number when associated with a UII. When this 

differs from the current part number use N901 to 

identify the new part number. AN ANSI data 

maintenance request has been prepared to request 

a new code qualifier for Original Part Number for 

future use.

T0 Dealer Type Identification 

DLMS Note:

Use to identify the UII type per UID guidance e.g., 

VIN, UID1, UID2, etc.

QW New Part Number

DLMS Note:

Use to indicate the current part number when 

different from the original part number identified in 

REF04.

Provides capability for 

conveying additional 

UID information.

No revision 

required

13 2/N901/270 Revised DLMS notes for qualifiers “BT” and “SE” 

BT Batch Number

DLMS Note:

Use to identify the batch, lot, or production run when 

UII or serial number is identified in 2/REF/250.

SE Serial Number

DLMS Note:

Use to identify the serial number (when code U3 is 

used in REF01).

Batch and lot numbers 

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

14 2/N901/270 Deleted the following qualifier:

LT Number

Batch and Lot Number 

have been combined. 

See ‘BT’ above.

No Revision 

required
16 of 15

ADC 148

Att

Item

# Location DS 527R Revision Reason

Federal

IC

Impact

15 2/N901/270 Deleted the following qualifier and DLMS notes: 

W5 Inspector Identification Number

DLMS notes: 

1. Use to identify the code assigned by each 

inspection agency to an inspector.

2. DLMS enhancement; see introductory DLMS 

note 5a.

No business case has 

been identified to 

DLMSO for use of “W5” 

Inspector Identification. 

No revision 

required

16 2/N1/280 Revise Federal segment level note to read:

Use to identify UIT information as needed.

Add DLMS segment level note:

DLMS enhancement. See introductory DLMS note 

5.a. 

Administrative Revision 

required to 

Federal note

17 2/N101/280 Added DLMS note for qualifier “MF” and added 

qualifier “IAT” w/DLMS note:

MF Manufacture of Goods

DLMS Note:

Use to identify the manufacturer of the identified 

item.

IAT Party Executing and Verifying

DLMS Note:

Use to indicate the Enterprise Identifier (EID) 

responsible for the UII. An ANSI data maintenance 

request has been prepared to request a new code 

qualifier for Enterprise identifier for future use.

Clarifies use of ‘MF’ 

as manufacturer of 

identified item, and 

adds the Enterprise 

Identifier for the item. 

Both are provided here 

for flexibility. There 

may be exception 

conditions where these 

will not be identical.

No revision 

required

18 2/N103/280 Added Data Element notes:

Federal Note:

Use any code.

DLMS Note:

1. For DLMS use, the following codes are authorized.

2. The value of the UID Issuing Agency Code (IAC)

may be derived from the qualifier used for the

Enterprise Identifier.

Provides information 

that the IAC can be 

derived from the 

enterprise identifier 

ANSI qualifier.

Revision 

required
17 of 15

ADC 148

Att

Item

# Location DS 527R Revision Reason

Federal

IC

Impact

19 2/N103/280 Added the qualifiers ‘1’, ‘8’, ‘9’, ‘10’, and ‘41’ with 

DLMS notes, and added DLMS note to qualifier “33”

1 D-U-N-S Number, Dun & Bradstreet

DLMS Note:

Corresponds to IAC 'UN'.

8 UCC/EAN Global Product Identification Prefix

DLMS Note:

Corresponds to IAC '0-9'.

9 D-U-N-S+4, D-U-N-S Number with Four 

Character Suffix

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

Corresponds to IAC 'LD'.

33 Commercial and Government Entity (CAGE)

DLMS Note:

Corresponds to IAC 'D'.

41 Telecommunications Carrier Identification Code

DLMS Note:

Corresponds to IAC 'LB' (ANSI T1.220, Commercial 

Telecommunications Standards).

Adds new qualifiers 

that can be used, and 

adds DLMS notes to 

all qualifiers to address 

how the ANSI 

qualifiers, when used 

for the enterprise 

identifier, correspond 

to the IAC.

No revision 

required