DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

May 23, 2018

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 

1284, Issue Release/Receipt Document (IRRD) PDF417 Two-Dimensional (2D) 

Bar Code Part Number Field Length (MILSTRIP/DLMS)

We are forwarding the attached change to DLM 4000.25, Defense Logistics Management 

Standards, and DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), for implementation. This change is effective upon publication.

Addressees may direct questions to Mr. Eric Flanagan or Ms. Tonja Daniels, email:

DLMS_MILSTRIP@dla.mil. All others must contact their Component designated Supply PRC 

representative available at www.dla.mil/HQ/InformationOperations/DLMS/allpoc.

 HEIDI M. DAVEREDE

 Director

 Enterprise Business Standards Office

Attachment

As stated

cc: 

ODASD (SCI)
Attachment, ADC 1284

Page 1

Attachment to ADC 1284

Issue Release/Receipt Document (IRRD) PDF417 

Two-Dimensional (2D) Bar Code Part Number Field Length

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Ellen Hilert, DOD 

MILSTRIP Administrator, Enterprise Business Standards Office (EBSO), email:

DLMS_MILSTRIP@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Distribution

3. REFERENCES:

a. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP)

Appendix 1.35 Issue Release/Receipt Document (IRRD) (DD Form 1348-1A) with Code 39 

(Three-Of-Nine) Bar Codes and PDF417 Two-Dimensional 2D Bar Code

b. Federal Logistics Information System (FLIS) Technical Procedures Data Element 

Dictionary, July 2017

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change is the first of multiple changes required to 

update the IRRD to correlate data content to the DLMS. This change expands the field length in 

the 2D bar code for the discrete part number entry to allow a 32-character part number 

comparable to FLIS catalog data. This change includes additional updates to clarify published 

guidance for the 2D bar code.

b. Background:

(1) DLMS transactions contain a standard 32-character part number field length. 

However, the table for creation of the IRRD PDF417 2D bar code indicates that the field length 

is 16 characters.

(2) The FLIS data element dictionary (Reference 3.b.) specifies a field length of 

32 characters for part numbers as follows:

“3570 REF-NBR-LOG REF_NBR_3570 F CHAR 32

REFERENCE NUMBER, LOGISTICS

A NUMBER, OTHER THAN AN ACTIVITY STOCK NUMBER, USED TO IDENTIFY AN ITEM OF 

PRODUCTION OR, EITHER BY ITSELF OR IN CONJUNCTION WITH OTHER REFERENCE NUMBERS, 

TO IDENTIFY AN ITEM OF SUPPLY (WHEN USED IN CONJUNCTION WITH THE CAGE CODE). 

INCLUDES MANUFACTURERS PART, DRAWING, MODEL, TYPE, SOURCE-CONTROLLING 

NUMBERS, SPECIFICATION-CONTROLLING NUMBERS, THE MANUFACTURERS TRADE NAME 
Attachment, ADC 1284

Page 2

WHEN THE MANUFACTURER IDENTIFIES THE ITEM BY TRADE NAME ONLY, NATO STOCK 

NUMBERS, SPECIFICATION OR STANDARD PART, DRAWING, OR TYPE NUMBERS. SEE VOLUME 

10, TABLE 21 AND QUICK INFO ON-LINE.” 

“3571 CONV-REF-NBR CONV_REF_NBR_3571 F CHAR 32

CONVERTED REFERENCE NUMBER

THE VALUE OF REFERENCE NUMBER, LOGISTICS AFTER IT HAS BEEN SUBJECTED TO THE 

REFERENCE NUMBER FORMAT CONVERSION CRITERIA. THIS VALUE IS USED IN ALL 

REFERENCE NUMBER SCREENING, INCLUDING NEW ITEMS, MAINTENANCE. THE CONVERTED 

REFERENCE NUMBER VALUE MAY OR MAY NOT BE EQUAL "" REFERENCE NUMBER, LOGISTICS 

VALUE.”

c. Approved Change in Detail: Update MILSTRIP 2D bar guidance to increase the 

discrete part number data field from 16 to 32 characters. Revise data format table instructions to 

clarify the intended content and replace the obsolete/inappropriate routing identifier code (RIC) 

S9I. This change specifically authorizes including the Commercial and Government Entity 

(CAGE) code and part number when materiel is identified by other types of numbers, (e.g., 

national stock number or local stock number).

d. Revisions to DLM 4000.25 Manuals: Revise DLM 4000.25-1 MILSTRIP Appendix 

1.35 Issue Release/Receipt Document (IRRD) (DD Form 1348-1a) with Code 39 (Three-OfNine) Bar Codes and PDF417 Two-Dimensional 2D Bar Code as shown in extracted rows 

below.

Category/Description

ANSI MH10.8.2

Format 06

Data Identifier (DI)

or

Format 07

Data Element Identifier (DEI)

Data Field

(DoD Usage)

Data Format 

(Type/Length)

Sample Data

(Compliance, 

Header, Identifier

and 

Data)

Total Characters

N

Category 14, Industry Assigned Codes: 

National/NATO Stock Number (NSN)

National Stock Number (NSN) or Stock Identification 

Elements

May reflect NSN, CAGE Code/part number, FSC, etc., as 

applicable. May also include associated coding, e.g., Type of 

Pack, USN Special Material Identification Code (SMIC) or 

USAF Materiel Management Aggregation Code (MMAC)

This data content is analogous to the legacy MILSTRIP stock 

number field. When using this data field to identify an item by 

CAGE Code/part number, also use separate identifiers below

for CAGE Code and part number. For unique item tracking or 

in support of DoD policy for the application of IUID in supply 

processes, use this identifier for the NSN and use separate 

identifiers listed below to uniquely identify a specific individual 

item. 

AN/15 N5340013145957 17

V

Category 22, Party to the Transaction: 

Supplier Code assigned by Customer

Routing Identifier Code – Shipping Activity

Identifies the RIC of the source of supply shipping activity

(MILSTRIP legacy transaction rp 4-6).

AN/3 VS9ISRR 5

1P

Category 16, Item Information: Item 

Identification Code assigned by Customer

Part Number

The part number currently used to identify this item. Use to 

supplement item identification when the item is otherwise 

identified (e.g., by NSN or local stock number) and when the 

combined CAGE code/part number is cited.

AN/1632 1P9988771212SP 1935
Attachment, ADC 1284

Page 3

e. Transaction Flow: Not applicable.

f. Alternatives: None identified.

5. REASON FOR CHANGE: Updates MILSTRIP guidance for current, accurate information. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Provides updated guidance for users. This change will expand 2D bar 

code part number field to 32-characters without requiring a major revision to re-map the stock 

number fields in the linear and 2D bar codes. This provides additional flexibility while

continuing to support legacy constraints.

b. Disadvantages: Separate, future DLMS Changes are necessary to fully transition the 

IRRD data content for DLMS functionality.

7. ADDITIONAL COMMENTS TO CONSIDER:

a. A future change is required to adjust mapping for the 2D bar code data field for 

“National Stock Number (NSN) or Stock Identification Elements.” This data field is structured 

to mirror the legacy MILSTRIP stock number field, which is a multi-purpose data field. At a 

future date, the MILSTRIP Administrator will transition this field to discrete identifiers 

comparable to DLMS transactions.

Staffing Note: Components did not provide feedback on feasibility of eliminating the multipurpose legacy equivalent stock number field in the 2D bar code and transitioning to discrete 

identifiers for data content currently carried in legacy record positions 8-22, inclusive of 

Component unique content.

b. This change does not modify field length for part numbers identified in the linear bar 

code in Block 25 of the IRRD. As with the 2D stock identification field, this data field is 

structured to mirror the legacy MILSTRIP stock number field and is a multi-purpose data field

with a restricted field length. At a future date, the MILSTRIP Administrator will transition this 

field to support the standard part number field length when applicable.

c. A future change will update the field length for bar coded quantities for compatibility 

with the DLMS.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This change is effective

upon publication. Components must ensure compatibility with system design no later than 

December 2018.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

10. IMPACT:

a. New DLMS Data Elements: None.
Attachment, ADC 1284

Page 4

b. Changes to DLMS Data Elements: None.

c. Automated Information Systems (AIS): AIT systems may require update to support 

the 32-character part number.

d. Defense Automatic Addressing System (DAAS): None identified.

e. Non-DLM 4000.25 Series Publications: Comparable update required to expand the 

part number field length from 16 to 32 characters in MIL-STD-129, Department of Defense 

Standard Practice Military Marking for Shipment and Storage. The MIL-STD change is 

currently under coordination.

11. PROPOSED DLMS CHANGE (PDC) 1279 STAFFING RESPONSE/COMMENT 

RESOLUTION:

Originator Response/Comment Disposition

1. Army Concur Noted

2. Navy Concur Noted.

3. Air Force Concur Noted.

4. Marine Corps Concur Noted.

5. USTRANSCOM Abstain Noted.

6. DLA Concur Noted.