1 of 5

ADC 135

 Att

 

ATTACHMENT TO ADC 135

Revise DS 527D Advance Receipt Information (ARI) Transaction and MILSTRAP DWK

Pre-Positioned Materiel Receipt (PMR) to Carry Status Code “BD” When Assets are Not 

Available to Replenish a National Inventory Management Strategy (NIMS) Site 

(Implementation DoD Component Optional) (Staffed as PDC 140/140A)

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Agency (DLA)

b. Originator: Mr. Bob Vitko, J332/PCCI

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Title: Revise DS 527D Advance Receipt Information (ARI) Transaction and 

MILSTRAP DWK Pre-Positioned Materiel Receipt (PMR) to Carry Status Code “BD” When 

Assets are Not Available to Replenish a National Inventory Management Strategy (NIMS) 

Site (Implementation DoD Component Optional) (Supply/DLMS/MILSTRIP/MILSTRAP)

b. Description of Change: 

(1) Under the NIMS concept of operation, DLA will own materiel for DLA managed 

NSNs down to the retail level; e.g., SARSS 1 sites for Army. This will only happen based 

on agreements between DLA and the Service. Replenishment of DLA owned assets will 

be accomplished under a push scenario (redistribution of DLA owned assets from a 

distribution depot to a NIMS site when assets at NIMS site fall below Reorder Point) vice the 

traditional pull scenario (submission of a requisition when assets fall below retail reorder 

point). Redistribution from depot inventory will be accomplished using the MILSTRIP 

Document Identifier (DI) Code A2_ Redistribution Order (DLMS 940R) transaction. When 

assets are available to push, the current MILSTRAP DI Code DWK, Pre-Positioned Materiel 

Receipt (PMR) (DLMS 527D, Advance Receipt Information (ARI) transaction), will be sent 

to the NIMS site. [NOTE: The DLMS equivalent to the MILSTRAP PMR is DS 527D with 

1/BR02/020 Transaction Type Code DE (ARI). The DLMS equivalent to the specific 

PMR DI Code DWK is 527D with 1/BR02/020 Transaction Type Code DE and 

2/LIN01/010 code N.]

 (2) The intent of this approved change is to also send a DWK PMR (527D ARI) to 

the NIMS site when reorder point is breached and assets are not available to be pushed. It 

should be noted that this would be an optional capability. That is, if the Service 

desires this capability, then DLA will provide it, however, if the Service is not 

interested in receiving notification when assets are not available to push, then none 

will be provided. Accordingly, this change only applies to Services entering into 

NIMS support agreements with DLA and then only if they desire this notification 

capability. In this regard, when negotiating business rules and system interfaces required 

for the NIMS process some Services expressed a need for this type information since they 

will no longer have a backordered requisition at the ICP with status notifying them of the 
2 of 5

ADC 135

 Att

 

estimated shipping date (ESD) when materiel is not available. These negotiations further 

revealed the least system impact would be for a DWK transaction modified to contain BD 

delay notification, and an ESD indicating when the materiel would be available to fill the 

NIMS site requirement. The business rules and system interfaces for DLA/Army NIMS 

pilots with SARSS initially established this requirement. A pilot between DLA and Navy RSupply is scheduled for January 2005 and preliminary meetings indicate Navy R-Supply is 

also interested in this functionality. DLA already programmed the capability to generate DI 

Code DWK with BD delay notification into legacy SAMMS and the replacement BSM 

Automated Information System (AIS).

c. Procedures. Revise procedures as follows (changes are identified by 

bold/italicized text unless otherwise noted:

 (1) Revise DoD 4000.25-1-M, AP2.16, Status Code “BD” explanation as follows:

Code Explanation

BD Multi-Use. Delay Status.

1. Requisition is delayed due to need to verify requirements relative to authorized 

application, item identification, or technical data. 

OR

2. Requisition for Government- furnished materiel (GFM) is delayed pending validation 

by either contracting management control activity (MCA) or between supply source 

and MCA. The activity performing the validation is identified. Upon completion of 

review, additional status will be provided to indicate action taken. 

OR

”3. For Optional use on the Advanced Receipt Information (formerly PrePositioned Materiel Receipt) transaction. When agreed to by participating 

National Inventory Management Strategy (NIMS) activities, indicates 

redistribution of material to support a NIMS site requirement is delayed. The 

wholesale-owned replenishment materiel required to be pushed to the retail 

NIMS site is not available for delivery. The ESD represents the projected date 

the material will be available for shipment.”

 (2) Revise DoD 4000.25-2-M (MILSTRAP), AP3.43, DWK, Pre-Positioned Materiel 

Receipt-Other than Procurement, to carry “BD” delayed notification, on an optional basis, 

when materiel to support a NIMS site requirement is delayed and to provide an Estimated 

Shipping Date for this condition as shown in Enclosure 1.
3 of 5

ADC 135

 Att

 

(3) Revise DoD 4000.25-2-M (MILSTRAP), Chapter 4, Receipt and Due-In, to add 

a new Paragraph C4.3.4 as follows: 

 “C4.3.4 Under the National Inventory Management Strategy (NIMS) concept of 

operation, the Integrated Materiel Manager (IMM) may own materiel for managed 

NSNs down to the retail level. Such arrangements will be based on agreements 

between participating Components. Replenishment of the IMM owned retail will be 

accomplished under a push scenario. Redistribution from depot inventory will be 

accomplished using the MILSTRIP A2_ Redistribution Order transaction. When 

assets are available to push, DI Code DWK PMR will be sent to the NIMS site using 

standard PMR procedures. Optionally, the Component agreements may authorize 

the use of DI Code DWK for the IMM to notify the NIMS site that materiel to support a 

NIMS site requirement is delayed. In this instance, the DI Code DWK will contain the 

quantity not available for push replenishment, the delay notification status code 

“BD” and an Estimated Shipping Date. If at the time push replenishment is required 

only a partial quantity is available, then two DWKs will be generated; one for the

quantity pushed and one for quantity delayed. These two DWKs will have different 

document numbers and the delayed one will have the “BD” notification. 

Subsequently, if only a partial amount of the quantity previously delayed becomes 

available to push, two DWKs will be generated. The one for the quantity pushed will 

maintain the document number of the original delayed notification with the “BD” 

indicator eliminated. The DWK for the quantity still delayed will be assigned a new 

document number and a ”BD” delayed indicator. If the total quantity is initially 

delayed and subsequently the total quantity is shipped, the DWK will have the same 

document number throughout the process. The IMM will update/replace the DWK 

delayed notification anytime either the replenishment quantity or the estimated 

shipping date changes. New delayed notification will maintain the same document 

number unless a partial push occurs. Replacement delayed notification under the 

same or new document number will not require the reversal of the previous DWK. 

Reversal logic for DWKs indicating that a push shipment has been initiated will 

follow the requirement in paragraph C4.3.3 above.

(4) Revise DLMS Supplement (DS) 527D as shown in Enclosure 2. 

 (5) Revise DoD 4000.25-M, DLMS, Volume 2 Supply, Chapter 12, Due-In and 

Advance Receipt Information, to add new paragraph C12.3.4 as follows:

“C12.3.4 Optional National Inventory Management Strategy (NIMS) Advanced Receipt 

Notification Under the NIMS concept of operation, the Integrated Materiel Manager 

(IMM) may own material for managed NSNs down to the retail level. Such 

arrangements will be based on agreements between participating DoD Components. 

Replenishment of the IMM owned retail will be accomplished under a push scenario. 

When assets are available to push, DS 527D ARI will be sent to the NIMS site using 

standard ARI procedures. Optionally, the DoD Component agreements may 

authorize the use of DS 527D ARI for the IMM to notify the NIMS site that material to 

support their replenishment requirement is delayed. In this instance, the 527D shall 

contain the quantity not available for push replenishment, the delay notification code 

“BD” and an estimated shipping date. If at the time push replenishment is required 
4 of 5

ADC 135

 Att

 

only a partial quantity is available, then two 527D ARI transactions shall be 

generated; one for the quantity pushed and one for quantity delayed. These 

transactions will have different document numbers and the delayed one will have the 

“BD” notification. Later, if only a partial amount of the quantity previously delayed 

becomes available to push, two 527D ARI transactions shall be generated. The one 

for the quantity pushed will maintain the document number of the original delayed 

notification with the “BD” indicator eliminated. The 527D for the quantity still 

delayed must be assigned a new document number and a ”BD” delayed indicator. If 

the total quantity is initially delayed and later the total quantity is shipped, the 527D 

ARI must have the same document number throughout the process. The IMM will 

update/replace the 527D delayed notification anytime either the replenishment 

quantity or the estimated shipping date changes. New delayed notification must 

maintain the same document number unless a partial push occurs. Replacement 

delayed notification under the same or new document number shall not require the 

reversal of the previous 527D. Reversal logic for 527D ARI transactions indicating 

that a push shipment has been initiated shall follow the requirement in paragraph

C12.3.3 above.”

d. Alternative: Consideration was given to using the DLSS/MILSTRIP DIC AE_ 

(DLMS/Supply 870S) to provide the delayed NIMS replenishment notification. This was 

abandoned in favor of the proposed process based on a review of the status alternative 

which revealed that solution was considerably more complicated to implement. In this 

regard, Service retail systems would not have a requisition resident within their system to 

process the status transaction against. Additionally, the redistribution transaction carries 

the IMM DoDAAC and document number which complicates the retail system accepting the 

requisition status transaction. Further review indicated that Service receipt systems were 

more receptive to external DoDAACs/document numbers. Using the PMR/ARI to 

communicate this data was considered a simpler approach on the IMM side also, as 

generating an maintaining requisition status without a requisition required a more complex 

system solution. Accordingly it was determined that using the PMR/ARI to communicated a 

delay in a NIMS replenishment shipment was both functionally proper and represented a 

less complex system solution.

4. REASON FOR CHANGE: 

Under the NIMS concept of operation, DLA will own materiel for DLA managed NSNs down 

to the retail level; e.g., SARSS 1 sites for Army. This will only happen based on 

agreements between DLA and the Services. These agreements will establish NIMS 

business rules (both materiel management and financial), outline support metrics and 

delineate NIMS site participants.

The DLA and the Service will jointly determine the range of items to be stocked at the NIMS 

site. The Requirements Objective (RO) and Re-Order Point (ROP) for stocked NSNs will 

be determined via a collaborative process.

Replenishment of the DLA owned retail will be accomplished under a push scenario. A 

daily transactional interface of all balance affecting transactions (issue, denial, receipt, and 

adjustment transactions) will be maintained between the NIMS site and the DLA ICP. When 

the ROP or its equivalent is breached materiel will be redistributed from wholesale depot 

inventory or directed from new procurement to bring inventory levels back to the RO. 
5 of 5

ADC 135

 Att

 

Redistribution from depot inventory will be accomplished using the MILSTRIP A2_ 

Redistribution Order transaction. When assets are available to push, the current MILSTRAP 

DWK will be sent to the NIMS site. 

The intent of this purposed change is to also send a DWK to the NIMS site when reorder 

point is breached and assets are not available to be pushed. It should be noted that this 

would be an optional capability. That is, if the Service desires this capability, then DLA will 

provide it, however, if the Service is not interested in receiving notification when assets are 

not available to push, then none will be provided. Accordingly, this change only applies to 

Services entering into NIMS support agreements with DLA and then only if they desire this 

notification capability. 

In this regard, when negotiating business rules and system interfaces required for the NIMS 

process some Services expressed a need for this type information since they will no longer 

have a backordered requisition at the ICP with status notifying them of the ESD when 

materiel is not available. These negotiations further revealed the least system impact would 

be for a DWK transaction modified to contain BD delay notification and an ESD indicating 

when the materiel would be available to fill the NIMS site requirement. The business rules 

and system interfaces for DLA/Army NIMS pilots with SARSS initially established this 

requirement. A pilot between DLA and Navy R-Supply is scheduled for January 2005 and 

preliminary meetings indicate Navy R-Supply is also interested in this functionality. DLA 

already programmed the capability to generate the DWK with BD delay notification into 

legacy SAMMS and the replacement BSM AIS.

5 ADVANTAGES AND DISADVANTAGES:

a. Advantages: This change facilitates the NIMS process which has the goal of 

reducing DoD Inventories. It facilitates the BSM release 2.1.1 NIMS implementation 

allowing BSM to interface with current and projected NIMS sites. Further it documents 

previously agreed to NIMS system interface rules between DLA and some Services and 

documents the use of a DI Code DWK intra-service use field.

b. Disadvantages: None Known.

6 IMPACT:

a. This is an optional change based on NIMS Service/Agency agreements. Accordingly, 

this change only applies to Services entering into NIMS support agreements with DLA and 

then only if they desire this notification capability. Service system changes are only 

required if they desire this capacity as part of the NIMS system interface.

b DLA already programmed the capability to generate DI Code DWK with BD delay 

notification into legacy SAMMS and the replacement BSM AIS.

c. Change revises MILSTRIP, MILSTRAP, DLMS, DS 527D and DAASC mapping of 

the DWK/527D. 

2 Enclosures
1 of 2

ADC 135

Enclosure 1

ENCLOSURE 1 to ADC 135

DoD 4000.24-2-M Prepositioned Materiel Receipt - Other Than Procurement Instrument

FIELD LEGEND

Record 

Position ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter appropriate DI code from the DW series.

Routing Identifier (FROM) 4-6 Enter RI code of the ICP to which the receipt will be reported.

Blank 7 Leave blank.

Stock or Part Number 8-22 Enter stock or part number of item to be received.

Unit of Issue 23-24 Enter UI of the item.

Quantity 25-29 Enter quantity to be received, preceding significant digits with zeros.1/2

Document Number 30-43 Enter controlling document number.

Suffix 44 Enter controlling suffix code; otherwise, leave blank.

Supplementary Address 45-50 Enter SUPADD; otherwise, leave blank.

Signal 51 Enter signal code; otherwise, leave blank.

Fund 52-53 Enter fund code; otherwise, leave blank.

Distribution 54-56 Enter distribution code; otherwise, leave blank.

Project 57-59 Enter project code; otherwise, leave blank.

Multiuse

(Optional intercomponent use for delay 

notification)

60-66

(65-66)

For intra-Component use, enter data prescribed by the Component. 

(For inter-Component use, enter shipment delay notification code 

“BD” in rp 65-66, if required based on Service/Agency NIMS 

agreement, and assets are not available to replenish the NIMS retail 

site requirement, otherwise leave blank.)3

Routing Identifier 67-69 Enter RI code of the storage activity which is to receive item.

Ownership/Purpose 70 Enter ownership/purpose code of item to be received.

Supply Condition 71 Enter supply condition code of item to be received.

Management 72 Enter management code; otherwise, leave blank.

Date Indicator (Estimated 

Delivery)

(Optional intercomponent use for 

Estimated Shipping 

Date)

73-75 If prescribed by the Component managing the item, enter last digit of the 

calendar year and two-digit month signifying estimated delivery date, 

e.g., 211 means 2002, month of November.4 (When delayed shipment 

notification “BD” is used in rps 65-66, then the date entry 

represents the Estimated Shipping Date vice the Estimated Delivery 

Date.)3

 

1

 See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.

2

 See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.

3

The DWK, Pre-Positioned Materiel Receipt-Other than Procurement, may carry “BD” delayed notification, on an 

optional basis, IAW Service/Agency agreement, when materiel to support a National Inventory Management Strategy 

(NIMS) site requirement is delayed. Under this circumstance, the transaction will also carry an Estimated Shipping 

Date (ESD). See Chapter 4. Paragraph C4.3.4 

4

 See Appendix AP3 - Formats Introduction, Paragraph AP3.3.4.
2 of 2

ADC 135

Encl 1

DI Code DWK

 

FIELD LEGEND

Record 

Position ENTRY AND INSTRUCTIONS

Blank 76-78 Leave blank.

Multiuse 79-80 For intra-Component use, enter data prescribed by Component. For 

inter-Component use, leave blank.
1 of 2

ADC 135

Enclosure 2 

DS 527D Changes

ENCLOSURE 2 to ADC 135

DS 527D Change Table

Item 

#

Location DS 527D Revision Reason Federal 

IC 

impact 

1. DLMS 

Introductory 

Notes

Revise Note 1 as follows:

1. Managers use this transaction set to provide advance receipt 

information transactions to storage activities. For material being 

logistically reassigned, Gaining Item Managers (GIMs) use this 

transaction set for delinquent due-in inquiries and due-in 

reconciliation inquiries to inquire to the Losing Item Manager 

(LIM) about the status of dues-in. LIMs use this transaction set 

for dues-in to transmit memorandum due-in information to the 

GIM and for delinquent due-in advice and due-in reconciliation 

advice to respond to GIM inquiries, and for delinquent due-in 

advice to provide revised Estimated Delivery Dates (EDDs) to 

the GIM as they occur. IMMs also use this transaction to 

provide a replenishment delay notification, IAW DoD 

Component agreement, when material to support a National 

Inventory Management Strategy (NIMS) site requirement is 

not available for shipment. In this instance the transaction 

will contain a delay notification code and an estimated 

shipping date (ESD).

Administrative

change to 

document 

additional 

functionality.

No 

impact.

2. DLMS 

Introductory 

Notes

Remove PDCs 140/140A and add ADC 135 to PDCs/ADCs in 

introductory DLMS note 5:

5. This revision to the DLMS Supplement incorporates

Proposed DLMS Changes (PDC) and Approved DLMS 

Changes (ADC) listed. PDCs/ADCs are available from the

DLMSO website http://www.dla.mil/j-6/dlmso/Changes.

-- ADC 135, Revise DLMS Supplement (DS) 527D 

Advance Receipt Information (ARI) Transaction and 

MILSTRAP DWK Pre-Positioned Materiel Receipt 

(PMR) to Carry Status Code “BD” When Assets are 

Not Available to Replenish a National Inventory 

Management Strategy (NIMS) Site (Implementation 

DoD Component Optional) (Staffed as PDC 140/140A)

Administrative 

to delete PDCs 

140/140A and 

replace with 

ADC 135, to 

accurately 

identify 

DLMS 

Changes 

included in the 

DLMS 

Supplement.

No 

Impact
2 of 2

ADC 135

Encl 2 

DS 527D changes

 

Item 

#

Location DS 527D Revision Reason Federal 

IC 

Impact 

3 1/BR06/020 Open BR06 for use and add BR06, data element 306, Action 

Code ‘RS’ Report Status with DLMS note. 

RS Report Status

DLMS note: IMMs use to provide a replenishment delay 

notification, IAW DoD Component agreement, when material 

to support a National Inventory Management Strategy (NIMS) 

site requirement is not available for shipment. In this instance 

the transaction will contain a delay notification code and an 

estimated shipping date (ESD). BR06 code ‘RS’ is only for 

use with ARI transactions (BR02 code ‘DE’) for relocations 

(2/LIN02/010 code ‘N’).

To provide 

for new 

functionality

Revision 

required.

4 2/RCD02/040 Revise DLMS note 1: 

Revise DLMS note 1: Use to indicate the total quantity due-in 

for the item identified in the 2/LIN/010 segment. For delinquent 

due-in inquiry and advice and due-in reconciliation inquiry and 

advice transactions, this is the open due-in quantity. For 

delayed NIMS replenishment shipments this is the NIMS site 

required quantity that is not available for shipment until the 

provided estimated shipping date.

To provide 

for new 

functionality.

No 

impact.

5 2/G6201/050 Add new date qualifier code TR, Transfer Date, with the DLMS 

note: 

TR Transfer Date 

DLMS note: 1. Used to identify the estimated shipping date 

for delayed replenishment shipments to NIMS sites for the 

required quantity not available for immediate shipment. Only 

for use with ARI transactions (1/BR02/020 code ‘DE), with 

BR06 code ‘RS’ and 2/LIN02/010 code ‘N’ (relocations). An 

ANSI data maintenance action has been taken to establish a 

more appropriate qualifier.

Note 2: DLMS enhancement. See introductory DLMS note 4.a.

To add ESD 

required for 

new 

functionality.

No 

impact.

6 2/LQ01/130 Add code list qualifier 81, status code, with DLMS note: 

81 Status Code

DLMS note: Use to provide code “BD” in LQ02 for delayed 

replenishment shipments to NIMS sites. Only for use with ARI 

transactions (1/BR02/020 code ‘DE), with BR06 code ‘RS’ 

and 2/LIN02/010 code ‘N’(relocations). Status Code is a 

candidate for streamlining after full DLMS implementation, 

as 1/BR06/020 provides same functionality. Use of Status 

Code ‘BD’ is required during a mixed DLSS/ DLMS 

environment. 

To add Status 

Code ‘BD’ 

required for 

new 

functionality 

for DLSS/ 

DLMS 

translation.

No 

impact.