1 

ADC 258 

DLMS Enhancement – 

Addition of Project Code Field to DRO 

1. ORIGINATOR: 

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

b. Sponsor: Supply PRC, Chair, Ellen Hilert, DLA DLMSO/J-6251, Defense Logistics 

Management Standards Office (DLMSO), 703-767-0676 (DSN 427), ellen.hilert@dla.mil 

2. FUNCTIONAL AREA: Supply, Disposal Release Order 

3. REFERENCE: DLMSO Memorandum dated September 11, 2006, subject: Approved 

DLMS Change (ADC) 205A, Assignment of MILSTRIP Document Number Serial Number 

Record Position (RP) 40/DLMS Utilization Code M for Base Realignment and Closure (BRAC) 

(Staffed by PDC 218) 

4. REQUESTED CHANGE:

 a. Description of Change: This change is provided to document procedures for the use of a 

proposed DLMS enhancement to include the Project Code data element in the format for the 

Disposal Release Order. 

 b. Background: Under the current MILSTRIP the DRO (DI Code A5J) format does not have 

adequate space to include the project code field within the 80 record position format. The 

project code is carried in the Material Release Order (DI Code A5_); however, the comparable 

record positions with the DRO are unavailable due to the necessary inclusion of the retention 

quantity. The Components’ attention was drawn to the lack of a project code in this format at the 

time the Utilization Code M was proposed for BRAC-associated disposal actions. The Supply 

PRC recommended that the DLMS documentation be updated to specifically permit future use of 

the project code on the DRO.

 c. Procedures: Modify the DLMS Supplement 940R, Material Release, to reflect optional 

use of the project code in the LQ segment at position 1300 as follows:

Qualifier 78, Project Code 

DLMS Note: 1. Use in redistribution orders, material release orders, disposal release orders

and historical material release orders, but only to identify special programs, exercises, projects, 

operations, and other purposes. Use in material release order modifications to identify the 

revised project code. 

2. Use of a project code in a disposal release order is an authorized DLMS enhancement. See introductory 

DLMS note 4b. 

 
2 

5. REASON FOR CHANGE: A DLMS change is necessary to formally adopt expanded data 

content within the DLMS. The project code field is available within the DLMS 940R, Material 

Release, and should be available for use in all release order formats. 

6. ADVANTAGES and DISADVANTAGES: 

 a. Advantages: 

(1) By formally identifying the Project Code as applicable to the DRO, Components 

implementing the DLMS may adopt this enhancement during migration. Allowing the inclusion 

of the Project Code will support association of the DRO with assigned project codes. 

(2) Near-term adoption of the Project Code in the DRO by Distribution Standard System 

(DSS), DLA Electronic Business System (EBS), Army Logistics Modernization Program (LMP), 

and other DLMS capable implementation, will support tracking of DROs under the current and, 

more likely, future BRAC operations. 

 b. Disadvantages: Components who transmit a DLMS DRO with a project code must have 

prior knowledge that the receiving system can accept the project code, or should have no 

expectation that the project code will be understood systemically. 

7. IMPACT:

 a. DLMS Users. Components which have already implemented the 940R for the DRO will 

be required to amend the format if the project code was not specifically included. 

 b. DAAS Conversion. No direct conversion of the project code from DLMS to MILS can be 

supported since the data field is not available in the MILS format. However, by Component 

request, DAASC may populate the project code field on DLMS DROs resulting from conversion 

of MILSTRIP DROs (Document Identifier AJ5) with document number serial numbers 

beginning with “M” (see 3. Reference, above). This would be appropriate subsequent to DSS 

implementation of this change. Components employing procedures under ADC 205A should 

contact DAASC to establish this conversion rule for inclusion of BRAC Project Code 3BC. 

This project code is defined as used to track cost, performance data, and distribution/ 

redistribution of assets to and from Base Realignment and Closure (BRAC) 2005 affected 

activities, effective July 25, 2005, to July 25, 2011. 

 c. Mixed DLMS/MILS Environment. There will be an interim period during mixed 

DLMS/MILS communication during which a project code may be designated as applicable by 

the creator of the DRO, but will not be captured by the receiving system. However, since project 

codes on DROs are for tracking costs, and not a factor in priority or precedence of material 

release orders, this is understood to be an acceptable phase toward full DLMS functionality. 

 d. Shipping Documentation. Project codes on DROs will be perpetuated to shipment 

documentation and two-dimensional (2D) symbol as an alternate means of communication.