Attachment, ADC 455

Page 1

ADC 455A

Revisions to Procedures and Supply Status (DLMS 870S/DIC AE_)

from DLA Disposition Services under RBI

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: DLA Logistics Information Service, 269.961.5723

b. Functional POC: DLA Disposition Services, 269.961.5906

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/ Logistics

b. Primary/Secondary Functional Process: Requisitioning

3. BACKGROUND: The DLA Disposition Services (formerly Defense Reutilization and 

Marketing Service) is a worldwide presence within the Department of Defense, with disposal 

specialists in 14 foreign countries, two U.S territories, and 39 states. DLA Disposition Services’

mission is the execution of disposition solutions for excess military property. The Reutilization 

Business Integration (RBI) project will replace the DLA Disposition Services Automated Information 

System (DAISY) by integrating DLA Disposition Services’ business processes within the DLA 

enterprise suite of applications, including the DLA Distribution Standard System (DSS) and the 

Enterprise Business System (EBS). Note: Blue highlighting identifies significant revisions 

subsequent to staffing of original proposal. Yellow highlight is applicable to the ADC 455A. ADC 

455A is provided to remove an incorrect mapping in the DLMS transaction; there are no process 

changes. ADC 455A replaces ADC 455 in its entirety. 

a. Intent of the transaction: Military Service supply system-prepared requisitions may be 

submitted to DLA Disposition Services using either the MILSTRIP legacy 80-record position (rp) 

format or the DLMS 511R, Requisition. The Services have the capability to order property by 

National Stock Number (NSN) without regard to specific Disposal Turn-In Document (DTID) 

numbers contained within DLA Disposition Services inventory. A Service legacy or ERP system may 

process a MILSTRIP requisition to DLA Disposition Services (Routing Identifier Code (RIC) S9D) 

which DLA Transaction Services will route to the DLA Disposition Services’ Reutilization/Transfer/

Donation (RTD) Web application (www.dispositionservices.dla.mil/rtd03/index.shtml) for processing. 

Once the RTD Web receives this requisition, the DLA Disposition Services’ inventory will be 

searched, regardless of property location if a DTID is not identified by the customer. If there is a 

match of property to the requested stock number, a requisition document with updated information will 

be generated by the RTD Web for transmission to EBS. In some instances, the property will be 

physically located in multiple locations or will require multiple DTID numbers to satisfy the 

requisition quantity. When this occurs, a partial action, identified by the original document number 

sent by the customer will be filled with the DTID quantity on hand for the order. For the remaining 

requisition open quantity, RTD Web will be required to generate separate requisitions to DLA 

Disposition Services including the customer document number and sequentially assigned suffix codes 

as needed to fill the requested quantity. As requisition transactions with suffix codes are being 

generated, RTD Web will provide Supply Status (DLMS 870S/DIC AE_) with notification of the 
Attachment, ADC 455

Page 2

document number/suffix code combination. Additionally, the RTD Web will send supply status 

updates (as requisitions are processed and their status is changed/updated) to each of its non-RTD Web 

customers (i.e., requisitions received by RTD Web via DLMS 511R, including those originating as 

MILSTRIP legacy transactions or from GSA Web). The RTD Web does not provide Supply Status 

transactions for requisitions originated within the RTD Web.

Staffing Note. Use of the suffix code as described above to provide separate transactions for each 

DTID is not consistent with MILSTRIP suffixing to identify split shipments. However, the DLA 

Disposition Services requires accountability down to the DTID level and only supports a single 

occurrence of the DTID for each document number. The originally proposed RTD procedure to 

generate unique document numbers for each DTID Number was not considered acceptable since 

these document numbers would not be recognized by the Component’s supply system creating a 

disconnect between the original requirement/due-in and the DLA Disposition Services 

response/shipment. The use of suffix codes in the manner described above will leverage existing 

Component legacy system processing to recognize and retain suffix codes provided via supply status 

and will simultaneously create the one-to-one relationship necessary. More extensive redesign is 

not feasible. Suffixing by document number to uniquely identify each associated DTID is, 

therefore, employed here as a less intrusive business model for RBI.

b. Scenario for which the transaction is used: The process starts when a MILSTRIP legacy or 

DLMS-formatted requisition request is processed by RTD. As the status of requisitions are 

changed/updated, customers will be notified of these changes via the DLMS 870S (DIC AE_), Supply 

Status.

4. PROPOSED CHANGE(S):

a. Requested change in detail: As MILSTRIP requisition status changes occur, RTD Web will 

send updates via DLMS 870S (DIC AE_), Supply Status. As requisitions are generated and as supply 

status changes, customers will be notified via MILSTRIP status codes. Revisions to specific status 

codes are shown at Enclosure 1. 

b. Proposed Procedures:

1) MILSTRIP requisitions for DLA Disposition Services NSN property may be prepared 

and submitted external to the DLA Disposition Services’ RTD Web (via the customer’s own supply 

system). These requisitions will be forwarded by DLA Transaction Services to the RTD Web for 

processing. When a DTID Number is not cited on the requisition transaction, the RTD Web will 

determine the applicable DTID Number(s) necessary to fill the requisition. This is required because 

DLA Disposition Services property is managed by NSN/DTID Number. Each NSN/DTID Number 

combination must be associated with a different requisition transaction; therefore, the RTD Web will 

need to generate suffix codes for the customer’s document number as needed to fill the requsted 

quantity. RTD Web will transmit the DLMS 511R Requisition to DLA (EBS) citing the document 

number, suffix code, and applicable DTID Number.

2) The RTD Web will provide processing status via MILSTRIP supply status transaction 

citing the applicable status code under MILSTRIP business rules. As the status of these requisitions is 

updated, the RTD Web will provide supply status updates ensuring customers have the most up to date 
Attachment, ADC 455

Page 3

information on their requisition requests.

c. Alternatives: None identified.

5. REASON FOR CHANGE: As a result of the RBI project, the requisition process needs to be 

updated to account for a newly re-designed DLA Disposition Services process.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages (tangible/intangible): Customers will receive status updates for 

DLMS/MILSTRIP requisitions submitted to DLA Disposition Services transactionally, and minimize 

the need to directly contact DLA Disposition Services for status updates. 

b. Disadvantages: There are no identified disadvantages.

7. NOTE ANY REGULATIONS OR GUIDANCE: Changes will be needed for manuals DOD

4160.21-M and DRMS-I 4160.14.

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: None identified at this time.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: March 2012.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not Applicable

11. IMPACT:

a. New DLMS Data Elements: There are no new DLMS data elements associated with this 

change. 

b. Changes to DLMS Data Elements: Revisions to existing requisition-related status codes 

are shown at Enclosure 1.

 c. Publications:

 (1) MILSTRIP Appendix, AP2.16, Status Codes is updated as shown at Enclosure 1.

 (2) DLMS Supplement revisions are identified at Enclosure 2

 (3) DLMS Manual procedures are shown at Enclosure 3.

d. Component Automated Information Systems: Under RBI, the DLMS 870S Supply Status 

transaction provided for requisitions from DLA Disposition Services shall include the applicable DTID

Number. Individual supply status transactions will be provided to accommodate suffixing by the RTD 

Web. Components may choose to retain this additional information on due-in records to facilitate 

receipt processing or for perpetuation to cancellation transactions. 
Enclosure 1, ADC 455

Page 1

Enclosure 1, MILSTRIP Supply Status Codes Revisions

SUPPLY STATUS CODES

CODE EXPLANATION

B1 

C5

Assets not currently available. Requisition will be retained by DLA Disposition 

Services DRMS for 60 days from date of receipt awaiting possible arrival of assets. 

(DLA Disposition Services DRMS use only.) 

Rejected. Requisitioner, upon inspection of materiel located in the DLA Disposition 

Services Field Office DRMO activity, rejected acceptance due to condition of 

materiel/unacceptable substitute and/or materiel incorrectly identified. This status 

code is generated by the DRMO and furnished to the appropriate status recipients.

D1 Canceled. Requisition was retained for 60 days. Requested asset did not become 

available. Quantity field indicates quantity not filled. (DLA Disposition Services

DRMS use only.)
Enclosure 2, ADC 455

Page 1

Enclosure 2, DLMS Supplement (DS) Revisions

# Location DS 870S Supply Status Reason

1. DLMS 

Introductory 

Notes

Add ADC 455 to DLMS Introductory Note 5:

- ADC 455A, Revisions to Procedures and DLMS 870S, Supply Status,

from DLA Disposition Services under Reutilization Business Integration 

(RBI)

Identifies DLMS 

Changes included 

in the DS.

2. 2/REF04-01/87 Add Qualifier W1 and associated notes:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the controlling document number for the 

transaction cited in REF01 Code TN. 

2. Use for DLA Disposition Services requisition supply status to identify 

the specific DTID number shipped under the controlling document 

number/suffix code. Authorized DLMS enhancement. Refer to ADC 455.

Supports RBI 

requirements.
Enclosure 3, ADC 455

Page 1

Enclosure 3, DLMS Manual Revisions

Revise DOD 4000.25-M, Volume 2, Chapter 16, as follows. Paragraph numbering is approximate 

pending full re-write of this chapter for RBI-related changes.

C16.1.4.9. Providing Status to Customers

C16.1.4.9.1. For Service/Agency supply system generated requisitions and GSA Web 

submitted requisitions, RTD Web will provide processing status via the 870S Supply Status transaction, citing the applicable MILSTRIP status code (DOD 4000.25-1-M, Appendix 2.16). As supply 

status on these requisitions is updated, RTD Web will provide supply status updates to ensure customers have the most current information available on their requisitions.

C16.1.4.9.1.1. For unfilled requisition quantity retained by DLA Disposition 

Services for 60 days from date of requisition receipt awaiting possible arrival of assets, the RTD 

Web will provide Supply Status B1. The customer’s document number and the next available suffix 

will be shown on a B1 status subsequent to a partial supply action.

C16.1.4.9.1.2. If unfilled requisition quantity does not become available within 60 days from the date of the requisition receipt, the requirement shall be cancelled and the RTD 

Web shall provide Supply Status D1. The customer’s document number and the next available suffix will be shown on a D1 status subsequent to a partial supply action.

C16.1.4.9.2. For requisitions originated within RTD Web customers will have the 

ability to view current status of all their submitted requisitions on their account at the RTD Website. 

No DLMS 870S Supply Status transaction shall be generated for these requisitions. 

C16.1.4.9.3. Regardless of method of submission, when shipment occurs against a 

requisition, the DLA Disposition Services Field Office shall generate a DLMS 856S Shipment Status 

to the customer.
Enclosure 4, ADC 455

Page 1

Enclosure 4, Comment Resolution for PDC 496 and ADC 455

Originator Response/Comment Disposition

1. Navy Concur Noted.

2. Army Concur Noted.

3. Air Force The AF non-concurs with comments: 

The 591 SCMG commented on this PDC in reference to 

the following from paragraph 3.a: "For the remaining 

requisition open quantity, the RTD Web will select the 

next available DTID, spin up a new document number 

using the DoDAAC/Julian Date of the original requisition,

and populate the serial number portion of the document 

number with Y001. This serial number will sequentially 

increase with this same format YXXX until the entire 

quantity of the requisition is filled." Our two concerns are:

- The Stock Control System (SCS) subsystem

Reutilization/Disposition System (RDS, D035G) generates 

disposal release orders (doc id A5J) with document number 

serial numbers that begin with "Y". If the above scenario 

occurs for a requisition from the AF, it's possible the RTD 

Web-generated document numbers will duplicate 

document numbers generated from RDS. 

- If requisitions processed with document numbers 

not initiated by an AF supply system, receipt transactions 

for those requisitions will fail in the supply systems.

Therefore, IAW DoD 4000.25.25-M, Military Standard 

Requisitioning and Issue Procedures (MILSTRIP), we 

recommend using document number suffixes vice 

generating new document numbers. 

This PDC would cause changes to ECSS Release 1. ECSS 

is unable to provide an estimated implementation date due 

to the lack of execution progress on ECSS Pilot C as we 

continue to experience schedule setbacks.

Execution performance metrics, monitored and reviewed 

by Air Force senior leaders on a weekly basis, now reflect 

a four-to-six month delay to ECSS Pilot C completion and 

go-live. The Air Force is considering other options to the 

program for approval by the OSD Milestone Decision 

Authority. Until a final decision is made, an 

implementation date cannot be provided.

The concept of generation 

of new document numbers 

by RTD when multiple 

DTIDs are selected to fill 

the requisitioned quantity 

has been revised. Instead 

the RTD Web will assign 

suffix codes to the 

customer’s document 

number and provide 

supply status as 

notification of this action.
Enclosure 4, ADC 455

Page 2

Originator Response/Comment Disposition

We are using 'S' (For FES processing, RDS (D035G) will 

continue to use a 'S' in the first position of the document 

number serial number field on the A0A transaction sent to 

DLA Disposition Services). The problem RDS will have is 

with the fact DLA Disposition Services doesn't want to use 

suffix codes to indicate split actions for this requisition. 

RDS will have to be changed to tie a new document 

number with a 'Y' in the first position of the document 

number serial number field as a split action for their 

requisition with the 'S' in the first position of the document 

number serial number field. This logic will have to be 

used for supply and shipment status transactions sent by 

DLA Disposition Services and for receipt transactions 

posted in D035A or D035K. 

Bottom Line: If requisitions processed with document 

numbers not initiated by an AF supply system, receipt 

transactions for those requisitions will fail in the supply 

systems. Therefore, IAW DoD 4000.25.25-M, Military 

Standard Requisitioning and Issue Procedures 

(MILSTRIP), we recommend using document number 

suffixes

Note: Y was chosen for user-initiated disposals. Z is user 

for system generated disposals. And S is used for the 

requisitions for DRMO transactions. In order to meet PDC 

496's requirement a CSRD is required for D035G, 

therefore the AF will not be prepared to receive the 

change.

4. USTRANSCOM USTRANSCOM approves. Noted.

5. MILSTRIP 

Administrator

1. Please clarify procedures for use of Supply Status 

B1, Assets not currently available. Requisition will be 

retained by DLA Disposition Services for 60 days from 

date of receipt awaiting possible arrival of assets. If the 

quantity requested was partially filled on the customer’s 

original document number, will the document number for 

the B1 status be associated with a suffix code for the 

customer’s document number following the RTD rules or 

will the customer’s document number not be suffixed for 

this status transaction. (The original comment was based 

upon the Y-serial number and has been updated to reflect 

the use of suffix codes.)

2. Please clarify procedures for use of Supply Status 

D1, Canceled. Requisition was retained for 60 days. 

Requested asset did not become available. Quantity field 

indicates quantity not filled. If the quantity requested was 

1. The document number 

for the B1 status will be 

associated with a suffix

code for the customer's 

document number 

following the RTD rules.

2. If quantity requested is 

partially filled, D1 status 

will be associated

with a suffix code on the 

customer's document 

number following the 

RTD rules.
Enclosure 4, ADC 455

Page 3

Originator Response/Comment Disposition

partially filled on the customer’s original document 

number, will the document number for the D1 status be 

associated with a suffix code on the customer’s document 

number following the RTD rules or will the customer’s 

document number not be suffixed for this status 

transaction. (The original comment was based upon the Yserial number and has been updated to reflect the use of 

suffix codes.)

Comment Applicable to ADC 455A

6. DLA Transaction 

Services

Adding the DTID at both levels of the composite data 

element is unnecessary because the document number 

suffix code is not mapped to the reference segment 

composite data element in the supply status as it is in other 

transactions. The document number suffix is mapped to 

PO101 in the DLMS 870S.

Concur. Mapping for the 

DTID at 2/REF04-03/105 

has been removed from 

the ADC 455A document.