Approved DLMS Change 57

Enhanced Edits for the Required Delivery Date (RDD) Data Field in Requisitions

1. ORIGINATOR:

a. Service/Agency: DLMS Supply Process Review Committee

b. Originator: Ellen Hilert, DLMSO, ellen_hilert@hq.dla.mil, 703-767-0676, DSN: 

427

2. FUNCTIONAL AREA: Primary. Supply

3. REFERENCES:

a. DoD Inspector General Audit Report, Required Delivery Dates in Requisitions for 

Secondary Items of Supply Inventory, Report No. D-2000-113, April 19, 2000.

b. DLMSO memorandum, December 12, 2000, subject: DLMS Supply PRC Meeting 00-

3, November 14-15, 2000.

c. DLMSO memorandum, July 6, 2001, subject: DLMS Supply PRC Meeting 01-2, June 

12-14, 2001.

4. REQUESTED CHANGE:

a. Title: Enhanced Edits for the Required Delivery Date (RDD) Field in Requisitions

b. Description of Change: This change provides clarification and revision of business 

rules relating to the use of the RDD field and its compatibility with the priority designator (PD). 

It includes provisions for Defense Automatic Addressing System (DAAS) edit of the requisition 

RDD and PD fields to ensure incorrect entries are identified and appropriately modified prior to 

forwarding the requisition to the ICP. DAAS will provide supply status notification of requisition 

modificationwhenever a customer PD/RDD entry is blanked out or modified based upon 

prescribed rules (with exception that no notification is provided when inserting the default routine 

priority under specified conditions). Enhanced ICP edits are included for staggered 

implementation during logistics modernization where an earlier implementation is not possible. 

The ICP will also provide supply status notification of requisition modification using a staggered 

implementation. The identification of short RDDs associated with NMCS/ANMCS and work 

stoppage conditions is discontinued. Demand sequencing is revised to eliminate providing 

precedence to requisitions with an RDD/RAD earlier than the computed SDD or containing an 

expedited transportation* signal. Figure C3-2, UMMIPS Supply Source Processing Standards is 

deleted and a cross-reference to equivalent information published in the DoD 4140.1-R, DoD 

Material Management Regulation, is provided. Note: MILSTRIP footnotes associated with the 

deleted figure have been incorporated in the text where appropriate. Revisions to MILSTRIP 

are identified by bold-italicized text. Revisions supporting SPRC 02-2 agreements and postmeeting recommendations are identified by highlighting. [*Corrected copy]
3

c. Background: 

 (1) This change proposal is provided in response to the OIG Report D-2000-113 

(reference 3.a.), which recommended streamlining rules for using RDDs and enhanced editing of 

the RDD at DAASC. The report stated: “Because DAASC did not edit RDDs, several types of 

errors went undetected. For instance, ..., an edit that examined the compatibility of requisition 

elements such as the requisition date, RDD, and PD would identify inaccurate and invalid 

entries. We believe DAASC would enhance the accuracy and utility of RDDs, especially after the 

rules for using RDDs are streamlined and simplified, if it had a system of automated edit of 

RDDs.” While the lack of DAAS edit is accurate, ICP edits for the RDD field would have 

appropriately identified most (if not all) of the errors referred to in the OIG report. This change 

will provide standard validation at an earlier point in the process and provides flexibility to 

improve validation pending Component system modernization. Note: This change contains 

exceptions for intra-Component requisitions to preclude disruption of legacy system practices that 

have evolved to include Component unique application of the RDD. All such Component 

uniques must be identified and incorporated under the DLMS.

 (2) By agreement with the auditors during a mediation session conducted on April 

19, 2000, this change does not attempt the full-scale re-engineering of the RDD as suggested in 

the report. Process re-engineering will occur under DLMS in conjunction with the separation of 

the date field from special coding requirements. Limited restructuring of the RDD rules has been 

incorporated in this proposal as well as clarification of supply source processing associated with 

the RDD and coded entries. 

(3) This change facilitates and clarifies RDD processing within the current 

MILSTRIP context. Process re-engineering requirements to support the time definite delivery 

concept or Component modernization efforts must be addressed independently of this proposal. 

Components are encouraged to submit related requirements early in the design phase to minimize 

delays and ensure interoperability is not compromised. 

(4) Publication of UMMIPS time standards within MILSTRIP is terminated as 

unnecessary and inefficient now that the appropriate UMMIPS information is carried in the DoD 

4140.1-R. 

d. Procedures: 

(1) DAASC will perform the specified edits on requisitions for accuracy and 

reasonableness of the entry in the RDD field and compatibility with the PD. ICPs will 

incorporate comparable edits on a staggered schedule to accommodate logistics system 

modernization.

(2) Under DLMS for long-term implementation, appropriate supply status codes 

will be assigned for more specific identification of the reason for modification (replacing generic 

use of the BK status).

e. Alternatives: None identified.
4

5. REASON FOR CHANGE: 

a. This change provides clarification and simplification of the RDD business rules and 

implements a system of automated edits in accordance with reference 3.a and subsequent 

mediation agreements. 

b. Under this proposal, RDDs must fall within a 100-day timeframe subsequent to the 

requisition date. This validation is imposed to create a frame of reference for determining 

unreasonable RDDs. RDDs should never precede the date in the document number. 

Identification of an RDD that exceeds the UMMIPS time standard does provide meaningful 

information impacting supply source processing. The selection of the 100-day cut-off point is 

arbitrary; however, all UMMIPS time standards fall well within this timeframe. Communication 

of meaningful information related to the RDDs, such as restrictions on shipment not before or not 

after a particular date, is indicated by extended RDD coding.

c. An exception to the 100-day timeframe is authorized for Navy conventional 

ammunition to support Naval Ammunition Logistics Center (NALC) legacy system processes 

which permit extended RDDs using numeric calendar days. DAAS will exclude requisitions 

bearing COG symbols: 0T, 2D, 2E, 2T, 4T, 6T, 8E, 8T, and 8U from that portion of the edit 

(C2.28.7.7) which blanks the RDD field for entries greater than 100 days after the requisition 

date.

d. Under this proposal, short RDDs associated with NMCS/ANMCS requisitions are 

eliminated. This is intended to simplify the logic associated with the identification of 

NMCS/ANMCS. Under current practice, shipment is accomplished using the UMMIPS time 

standard for NMCS/ANMCS with no adjustment based upon the presence of a short RDD. The 

identification of a short RDD is currently optional, but it is not associated with supply source 

processing rules. The presence of the NMCS/ANMCS indicator alone in rp 62 establishes the 

appropriate level of demand sequencing. Because this feature has frequently been subject to 

misinterpretation and provides no significant benefit, use of the short RDD with NMCS/ANMCS 

is terminated under this proposal. 

e. Under this proposal extended RDDs (Codes X and S) must be associated with PD 09-

15 only. It is incongruent to have PD 01-08 requisitions associated with an extended RDD 

request.

f. Under this proposal work stoppage indicators must be associated with PD 01-08 only. 

It is incongruent to have a PD 09-15 when indicating a work stoppage condition is dependant 

upon requisitioned material. In addition, use of the short RDD with a work stoppage condition is 

terminated as adding unnecessary complexity to processing rules.

g. Demand sequencing is revised to eliminate providing precedence to requisitions with 

an RDD/RAD earlier than the computed SDD. Such precedence is inconsistent with policy 

requiring use of the PD and non-calendar day RDD (vice calendar day RDD) for determination of 

priority/timeframes for shipment. This is a highly complex edit requiring determination of the 

SDD based upon geographic area. Its elimination simplifies processing rules with little or no 
5

impact. Neither DLA nor Army currently consider RDDs shorter than SDDs when sequencing 

requisitions. 

h. Demand sequencing rules are further simplified by the elimination of the Expedite 

Transportation Signal 777 from the list of criteria. It was agreed by the SPRC members that 

customer requests for expedited transportation do not justify according any precedence to the 

requisition. Such requests are not adequately controlled by documented DoD procedures and are 

not comparable to other factors employed in sequencing release of material.

i. The withdrawal of ADC 40 was recommended and approved during the SPRC 02-2 

meeting. All the necessary clarification of the usage of coded RDD data field entries is integrated 

into this proposal. This change specifically authorizes Not Mission Capable Supply (NMCS) 

(Code N) and Anticipated Not Mission Capable Supply (ANMCS) (Code E), Expedited Handling 

Signal 555 and Expedited Transportation Signal 777 for Foreign Military Sales (FMS) 

requisitions. The application of any of the aforementioned codes for FMS use is NOT restricted 

to CLSSA requisitions (as it was in AMC 40). The use of Expedited Handling Signal 999 

continues to be reserved for use solely by U.S. Forces.

6. ADVANTAGES and DISADVANTAGES:

a. Advantages: Satisfies recommendations of OIG report and subsequent mediation. 

Clarifies and simplifies the use of the RDD and associated PD while limiting impact on supply 

sources. 

b. Disadvantages: None known.

7. IMPACT: This change is designed to have minimal impact on Component systems. Under 

full DLMS implementation RDD dates will be subject to validation in accordance with the ANSI 

standard thereby eliminating many potential problems. Special requirements are identified 

through the Special Requirements Code. Components are required to identify any internal 

requirements not addressed under the DLMS.

a. DAAS requisition processing must be modified to comply with above procedures. 

Component shall incorporate changes under long term logistics system modernization if an earlier 

implementation can not be achieved..

b. The Air Force identified their internal use of the RDD field which will continue under 

the provisions of this proposal. Specifically, DAAS will blank only two numeric characters 

intended as short RDDs, but will not blank out coding used for Air Force intra-Service 

communication of a NMCS/MICAP condition. However, Component-unique coding in the RDD 

field will not be perpetuated under logistics system modernization. Under the DLMS, Air Force 

requirements must be defined and appropriately transmitted. 

c. Publication(s): DoD 4000.25-1-M, MILSTRIP; DoD 4000.25-M, DLMS; DoD 

4140.1-R, DoD Materiel Management Regulation.
DoD 4000.25.1-M

6 Enclosure 1

Approved DLMS Change 57 Attachment

Enhanced Edits for the Required Delivery Date (RDD) Data Field in Requisitions

MILSTRIP Chapter Extract

(1) Revise Figures (front matter) to delete reference to figure C3-2.

(2) Revise Chapter 2, Preparation and Submission of Requisitions, Modifiers, Cancellations, and 

Followups, paragraph C2.3.2 as shown.

 “C2.3.2 Expedited Handling Signal 999

C2.3.2.1 PDs 01-03, requisitions for items causing mission-essential systems and 

equipment to be NMCS, will be prepared to contain code 999 in rp 62-64 in lieu of the RDD. 

Code 999 will provide identification of documents related to critical items and requiring expedited 

handling. When entered into requisitions, code 999 will be perpetuated on MROs and DD Form 

1348-1A (or DD Form 1348-2.) This procedure applies only to materiel being shipped to U.S. 

Forces OCONUS and to CONUS Forces alerted for OCONUS deployment within 30 days of the 

date of the requisition for materiel involved.

C2.3.4.2 Enter N in rp 62 of requisitions applicable to NMCS conditions originating at 

activities where forces in CONUS are not alerted for deployment. FMS requisitions applicable to 

NMCS conditions will contain an N in rp 62 which will identify transactions related to critical 

items and requiring expedited handling.

 

C2.3.4.3 Entries in rp 63-64 may indicate short RDDs expressed in number of days from 

the requisition dates are considered nonsignificant on inter-Component requisitions.

 

C2.3.5.2 Enter E in rp 62 of requisitions applicable to ANMCS conditions. FMS 

requisitions applicable to ANMCS conditions will contain an E in rp 62 which will identify 

transactions related to critical items and requiring expedited handling.

 

C2.3.5.3 Entries in rp 63-64 may indicate short RDDs expressed in number of days from the 

requisition dates are considered nonsignificant on inter-Component requisitions.”

(3) Revise Chapter 2, paragraph C2.28 as shown.
7

C2.28 DEFENSE AUTOMATIC ADDRESSING SYSTEM EDIT OF INCOMING 

REQUISITIONS

C.2.28.1 The DAAS will edit all incoming requisitions and other MILSTRIP transactions 

for data errors and validity under procedures in DoD 4000.25-10-M (DAAS).

C2.28.2 As a result of these edits, DAAS will correct data entries or reject transactions. In 

the case of supply source errors, the correct supply source will be entered in the RI field and the 

transaction rerouted, as appropriate. 

C2.28.3 The DAAS will reject all requisitions/EMALL orders containing GY/GZ series AACs. 

The DAAS will furnish DI AE9 transactions with status code CX to advise all concerned of the rejection of 

the requisition.

C2.28.4 The DAAS will use AP2.13 to validate requisitions for invalid/expired 

OSD/CJCS Category D project codes. The DAAS will blank out the inappropriate project code 

and furnish DI AE9/BK status to the customer.

C2.28.5 The DAAS will validate F/AD I usage through the requisitioning 

process. Requisitions containing an unauthorized priority designator according to AP2.14 will 

be downgraded. The DAAS will furnish DI AE9/BK status to the customer.

C2.28.6 The DAAS will perform validation of requisitions (DI Codes A0_, AM_, 

AT_, A3_, A4_, and APR) for accuracy and reasonableness of the entry in the RDD field and its 

compatibility with the PD. The DAAS will furnish DI AE9 transaction with status code BK to 

advise the requisitioner of resulting modification. For Security Assistance requisitions 

forwarded to the applicable ILCO, DAAS will not blank out customer input. DAASC will 

perform PD and RDD edits according to Figure C3.1.2 supply source guidance. 

[subparagraphs removed]

(4) Revise Chapter 3, Requisition Processing and Related Actions, to delete paragraph C3.1.2.8 

and renumber remaining paragraphs as follows.

 “C3.1.2. When supply sources and storage activities utilize the sequential (or batch) method of 

processing and do not possess real time processing capability, such processing is to be performed 

as frequently as necessary in order to meet UMMIPS time standards, or specific RDD for 

subsistence requisitions, as applicable. In every such cycle, cancellation requests DI AC_, 

including automatic cancellation initiated by the supply source) and MOV reconciliation requests 

(DI AP_) will be processed prior to backorder releases and new requisitions (DI A0_). Demands

will be sequenced as follows:

C3.1.2.1. PD in rp 60-61.

C3.1.2.2. OSD/JCS project codes, when entered in rp 57-59.

C3.1.2.3. Expedited Handling Signal (999 in rp 62-64) with PD 01, 02, or 03 in rp 60-61.
8

C3.1.2.4. N (NMCS) in rp 62 and PD 01-08 in rp 60-61.C3.1.2.5. E (ANMCS) in rp 62 

and PD 01-08 in rp 60-61.

C3.1.2.6. Expedited Handling Signal (555 in rp 62-64) and PD 01-08 in rp 60-61.

C3.1.2.7. Expedited Transportation Signal (777 in rp 62-64) and PD 01-08 in rp 60-61.

C3.1.2.8. RDD/RAD in rp 62-64, if earlier than the computed SDD.

C3.1.2.7. Requisition document number date in rp 36-39.

C3.1.2.8. RDP in rp 62-64, if later than the computed SDD - conventional ammunition 

only.

(5) Revise Chapter 3, paragraph C3.3.1 as follows:

“C3.3.1. Each requisition will contain a PD assigned by the requisitioning activity, which 

will not be changed by processing points except as noted in this chapter. The assigned PD 

dictates the precedence of internal supply processing actions (such as, from the receipt of a 

transaction until release to transportation) and determines the SDD. The Mandatory time 

standards for processing of transactions are as indicated in Figure C3-2 DoD 4140.1-R (DoD 

Material Management Regulation) Appendix AP8, UMMIPS Time Standards (published 

electronically at http://198.3.128.177/supreg/ ). All time standards are expressed in calendar 

days from the time of receipt of requisitions at the initial supply source. For subsistence 

requisitions, the assigned RDD is the primary processing criteria, while the assigned PD dictates 

the precedence of internal supply processing action for requisitions reflecting identical RDDs. 

Time standards, indicated in Figure C3-2 under UMMIPS, do not apply to subsistence 

requisitions. See AP2.14.”

(6) Revise Chapter 3, paragraph C3.3.5 as follows:

“C3.3.5 When system-wide inventory levels do not permit positive supply action on all 

requisitions within a given PD, supply procedures will provide for a release of demands containing 

the specifically designated OSD/JCS project codes and code 999 in the RDD field as the 

respective most urgent. PD 01-08 requisitions, including FMS requisitions, containing Expedited 

Handling Signal 555 or Expedited Transportation Signal 777 in the RDD field and other 

requisitions/material obligations will be processed for release under paragraph C3.1.2., this 

chapter.”

(7) Revise ICP edit processing as described in Chapter 3, Figure C3.1 (page C3-35), Requisition 

Processing and Related Actions:

CODE OR DATA 

ELEMENT

Priority1

ENTRY IS BLANK OR INCORRECT

1. If Expedited Handling Signal 999 is present in the RDD field, 

requisition is for U.S. forces, and the PD is not 01-03, enter PD 03 

and furnish BK supply status. 
9

Required Delivery Date1 2

2. If an OSD/JCS project code is present in rp 57-59 and the PD is not 

01-15, enter PD 03, and furnish BK status.

3. If NMCS/ANMCS indicator (N/E) is present in rp 62 and PD is not 

01-15, enter PD 08, and furnish BK status.

4. If special mass cancellation coding 555 is present in rp 62-64 and 

PD is not 01-15, enter PD 08, and furnish BK status.

5. If Expedited Transportation Signal 777 is in rp 62-64 and PD is not 

01-15, enter PD 08, and furnish BK status.

6. If required availability period (A in rp 62) is present, S, or X, and 

PD not 01-15, enter PD 15. 

7. If extended RDD (S or X in rp 62) is present and PD is other than 

9-15, enter 15, furnish BK status, and process.

8. If work stoppage indicator (F or R in rp 62) is present, and PD is 

not 01-08, enter 08, furnish BK status, and process.

9. For all other conditions, if PD is not 01-15, enter PD 15.

1. If NMCS/ANMCS indicator (N/E in rp 62) is present, and PD is

01-08, process. If there is an N or E in rp 62, but PD 09-15 in rp 60-

61, blank the entry in rp 62-64, furnish BK status, and process using 

the priority. If there is an N or E in rp 62 rp, blank any characters 

in rp 63-64 and furnish BK status. Exception: For Air Force 

requisitions, blank only numeric characters (01-99); do not blank 

special coding to fulfill an Air Force internal requirement for 

NMCS/MICAP justification. (Note: This eliminates short RDDs 

associated with NMCS/ANMCS and expressed as number of days 

from requisition date.)

2. If Expedited Handling Signal 999 is present in rp 62-64 and 

requisition is not intended for US forces, blank the expedited 

handling signal, furnish BK supply status, and process using the 

priority.1 If requisition is intended for US forces, process.

3. If special mass cancellation coding 555 is present in rp 62-64 

indicating continued processing during mass cancellation, process.

4. If Expedited Transportation Signal 777 is in rp 62-64 and PD 01-08 

is in rp 60-61, process. If the PD is 09-15, blank the entry in rp 62-64

Expedited Transportation Signal, furnish BK supply status, and 

process using the priority. 

5. If Co-Located Customer Handling Service Indicator 444 is 
10

present in rp 62-64, process.

6. If required availability date or extended RDD (rp 62 is A, S, or 

X), and rp 63-64 is not equal to 01-99, blank entry in rp 62-64, 

furnish BK supply status, and process.

7. If work stoppage indicator (F or R rp 62) is present and rp 63-64 

are not blank or equal to 01-99, blank any entry in rp 63-64, furnish 

BK supply status, and process. (Note: This eliminates short RDDs 

associated with work stoppage and expressed as number of days 

from requisition date.)

8. For subsistence, except for conditions 1, 2, 3, 4 above, all 

requisitions will contain a specific RDD in ordinal day of year format. 

If blank, compute an SDD.

9. For all other conditions, blank RDD field if entry does not indicate

a calendar date which falls no more than 100 days subsequent to the 

requisition date3, furnish BK supply status, and process. [Text 

deleted from proposal: No status is required when blanking a value 

of zero or when blanking a RDD prior to the requisition date.]

Required Delivery Period If rp 62 is B, C, D, G, H, J, K, L, M, P, T, U, V, or W, and rp 63-64 

contains 01-99, process.

1 Deferred implementation of PD/RDD compatibility edits and furnishing BK status under 

ADC 57 are authorized pending supply source system modernization. 

2

 Non-date entries in the RDD field i.e., Codes E, F, N, R, 444, 555, 777, and 999, are 

referenced as Special Requirement Codes under the DLMS.

3

 The 100-day edit is not applicable to requisitions directed to Naval Ammunitions Logistics 

Center (NALC).

(f) Delete Chapter 3, Figure C3-2 (page C3-36), UMMIPS Supply Source Processing Standards, 

in its entirety.

(8) Revise Chapter 6, as indicated.

“C6.17.1. Consolidation. The shipment planning process should recognize and assure 

compatibility of codes in requisitions and related documents when configuring shipment units. 

Requisitions with an N or E in rp 62, or 777 in rp 62-64, will not be held for consolidation, but 

the NOA requirements remain in effect. To assure compatibility of codes, rp 30-34, rp 45-50, 

and rp 57-61 must be considered for FMS non-assembly shipments; rp 55 and 56 must be 

considered in addition to rp 30-34, rp 45-50, and rp 57-61 for FMS assembly shipments; and rp 

30-33, rp 35, and rp 57-61 must be considered for Grant Aid.”

(9) Revise Chapter 9, as indicated.
11

“C9.19.3.3. Ensure materiel is shipped, using DD Form 1348-1A or DD Form 1348-2, to 

the activity identified in the LRO as the “ship-to” addressee. When the materiel is shipped, 

transmit a DI AS6 to the activity identified in rp 74-76 of the LRO. The DI AS6 will inc lude the 

DoDAAC (rp 45-50) and fund code (rp 52-53) of the activity to which the credit for the materiel 

and reimbursement for the PCH&T costs are to be provided, Signal Code B (rp 51), and 

Distribution Code 2 or 3 (rp 54). Retail activities will use UMMIPS time standards for 

processing LROs directed by the ICP/IMM. Refer to DoD 4140.1-R (DoD Material 

Management Regulation) Appendix AP8, UMMIPS Time Standards (published electronically at 

http://198.3.128.177/supreg/ )”
 

DoD 4000.25-1-M

Enclosure 2

12

Approved DLMS Change 57 Attachment

Enhanced Edits for the Required Delivery Date (RDD) Data Field in Requisitions

MILSTRIP Appendix AP2.14 Extract

Revise Appendix AP2.14, Priority Designators, Standard and Required Delivery Dates, as 

indicated.

AP2.14.10 Required Delivery Date (RDD) Data Field. Requisitioning activities, after 

determining the appropriate PD applicable to requisitions, will determine the appropriate entry 

for the RDD data field 1. The combination of the PD and the designation or non-designation of 

an RDD or other allowable entry for rp 62-64 as stated in this appendix, will determine the 

supply and transportation system response time requirements. Response times are located in 

DoD 4140.1-R, DoD Material Management Regulation, Appendix AP8, UMMIPS Time 

Standards (available at http://198.3.128.177/supreg/). 

AP2.14.10.1 An RDD which falls within 8 days of the requisition date will impact 

determination of the applicable UMMIPS time standard when the PD is 04-15. Otherwise, 

designation of a specific calendar day as the RDD will not influence response time; shipment 

will occur within the UMMIPS time standards for the assigned PD. When entered, the 

calendar day RDD may not precede the requisition date or exceed the requisition date by more 

than 100 days 2. [If the requisition is held in back-order status, the customer’s RDD will be 

taken into consideration for demand sequencing if earlier than the computed SDD.] 

Requisitions may also be coded using instructions below to indicate an extended RDD. [Deleted 

text] To preclude shipment later than the RDD, submit requisition with Advice Code 2T.

AP2.14.10.1.1 Extended RDD (Code X). When an extended RDD is assigned, it will be 

expressed in terms of months from the last day of the months expressed by the date of the 

requisition. The number of months, designating the extended RDDs, will be entered in rp 63-64 

and an alphabetic “X” will be entered in rp 62. In these instances, Use of the extended RDD is 

interpreted to indicate the latest acceptable delivery date and will not preclude earlier delivery if 

the materiel is available or later delivery should back-ordered material become available at a 

later date. Enter the appropriate PD, consistent with the F/AD and UND, in rp 60-61. Under 

these circumstances, the RDD will be the last day of the month depicted by the entry in rp 63-64. 

When supply status is provided, the ESD will be shown in rp 70-73. Supply source deferring

supply support to the requisitioner will enter Status Code BP in rp 65-66 of the supply status 

transaction.

___________________

1 Non-date entries in the RDD field, i.e., Codes E, F, N, R, 444, 555, 777, and 999, are 

referenced as Special Requirement Codes under the DLMS.

2

 The 100 day edit is not applicable to requisitions directed to Naval Ammunitions Logistics 

Center (NALC).
 

DoD 4000.25-1-M

Enclosure 2

13

AP2.14.10.1.2 Extended RDD (Code S). When a requisitioner desires that specific 

shipments not be released prior to 50 days before expiration of the extended RDD, an S will be 

entered in rp 62. No other entry will preclude earlier shipment if the material is available. The 

RDD will be interpreted as the last day of the month indicated in rp 63-64. The entry in rp 63-64 

will indicate the number of months from the requisition date that the materiel is required; such as, 

an “01" for the first month and “02" for the second. Shipping activities will ensure that this 

request is honored. Supply sources deferring supply support to the requisitioner will enter Status 

Code BP in rp 65-66 of the supply status transaction.

AP2.14.10.2 Expedited Transportation Signal. When expedited transportation is required, 

and the PD is 01-08, 777 may be entered in rp 62-64. 

AP2.14.10.3 Collocated Stock. If the customer is collocated with the supply depot issuing 

the materiel or has through local negotiations obtained collocated customer status and does not 

require the fastest possible service of the supply and transportation system, the customer should 

enter an RDD of 444. The customer entering a 444 RDD should expect the total time from order 

placement to delivery to be within the total order and ship time specified in chapter C3 UMMIPS 

time standards, figure C3-2, for the assigned PD.

AP2.14.10.4 Non-Mandatory RDD Data-Field Requirements. If the customer does not 

require an delivery date RDD or need to use one of the allowable entries for rp 62-64 as stated in 

this appendix, the RDD will may be left blank. The customer should expect the total time from 

order placement to delivery to be within the total order and ship time specified in chapter C3, 

figure C3-2, UMMIPS time standards for the assigned PD. When requisitions are received 

without entries in rp 62-64, these positions will be left blank on all transactions resulting from 

requisition processing. 

AP2.14.10.5 Mandatory RDD Data-Field Requirements. For subsistence, the RDD in rp 

62-64 is a mandatory entry on all requisitions, with the assigned PD prescribing the precedence of 

internal supply processing actions for requisitions reflecting identical RDDs. To ensure delivery 

on the RDD, the ICP/depot may bank the requisitions until the correct processing date, computed 

by subtracting the number of days needed for depot processing and transit time from the RDD. 

All requisitions will be submitted using schedules established by the ICP.

AP2.14.10.5.1 When RDDs extend beyond order/ship times established by the ICP (for 

MREs and other ration items), paragraph AP2.14.10.1.1, above, will apply.

AP2.14.10.5 .2 Provisions for work stoppage conditions identified below do not apply to 

subsistence.

AP2.14.10.5.3 During mass and universal cancellation situations, provisions of Chapters 

C3 and C8 take precedence over specific RDD requirements.

AP2.14.10.5 .4 Expedited Handling Signal 999 and other NMCS conditions covered in 

the succeeding paragraphs take precedence over the specific RDD requirements. 
 

DoD 4000.25-1-M

Enclosure 2

14

AP2.14.10.6 Not Mission Capable Supply/Anticipated Not Mission Capable Supply 

(NMCS/ANMCS). NMCS/ANMCS requisitions will be prepared with special coding in the 

RDD field when the following conditions exist/are anticipated to occur; equipment deadline for 

parts, aircraft out of commission for parts, engine out of commission for parts, and ships 

capability impaired for parts. The Commanding Officer of the requisitioning activity will either 

personally approve, or delegate in writing to specific personnel the authority to approve, all 

NMCS/ANMCS requisitions.

AP2.14.10.6.1 Expedited Handling Signal. Enter Expedited Handling Signal 999 in the 

RDD data field of PD 01-03 NMCS requisitions for materiel being shipped to U.S. Forces 

OCONUS and CONUS Forces alerted for OCONUS deployment within 30 days of the 

requisition date only when the conditions specified below are met:

AP2.14.10.6.2 The requisitioning unit must possess F/AD I, II, or III, and 

AP2.14.10.6.3 The items or equipment required are causing mission-essential systems or 

equipment to be incapable of performing any of their assigned missions, or 

AP2.14.10.6.4 The items or equipment required have been identified during maintenance 

or testing as necessary to prevent mission-essential systems or equipment from being unable to 

perform assigned operational missions or tasks within 5 days of the date of the requisition. 

AP2.14.10.6.5 Expedited Handling Signal 999 does not apply to Security Assistance 

requisitions.

AP2.14.10.6.6 Requisitions for NMCS conditions other than 999, and all ANMCS 

conditions, must contain PD 01-08, and rp 62 will contain with an N (NMCS) or E (ANMCS) in 

rp 62. Short RDDs expressed as days from the requisition date may be entered in rp 63-64. Rp 

63-64 are considered nonsignificant. Use UMMIPS time standards to ship material.

AP2.14.10.7 Required Availability Date (RAD). Security Assistance requisitions may 

contain a RAD in rp 62-64. The RAD will reflect the amount of time remaining from the date of 

the requisition until the materiel is required. Enter an A in rp 62 and use rp 63-64 to indicate

the number of months remaining from the date of the requisition to the required availability date 

entered in rp 63-64. (See Chapter C6.)

AP2.14.10.8 Processing Precedence during Mass Cancellation. Customers desiring to 

identify requisitions for continued supply document and/or shipment processing during mass 

cancellation situations, will submit a document requisition modifier (DI AM_) with 555 in the 

RDD data field (rp 62-64). Requisitions containing or modified to contain 555 in the RDD data 

field and containing PD 01-08 (rp 60-61), will receive processing precedence, under Chapter C3, 

paragraph A.2. Process requisitions containing 555 in the RDD data field and PD 09-15 under 

the priority.

AP2.14.10.9 Processing Precedence during Work Stoppage. For work stoppage conditions 

at industrial activities, the following procedures may apply at the option of the individual Service. 
 

DoD 4000.25-1-M

Enclosure 2

15

When utilized, these codes will only be significant on an intra-Service basis and will not be 

otherwise recognized.

AP2.14.10.9.1 Enter F in rp 62 of requisitions submitted by rework facilities for bits and 

pieces required for rework of mandatory turn-in reparable materiel. Rp 63-64 is left blank.

AP2.14.10.9.2 Enter R in rp 62 of requisitions submitted by repair activities, other than 

rework facilities, to indicate local work stoppage requirements. Rp 63-64 is left blank.

AP2.14.10.9.3 Entries in rp 63-64 may indicate short RDDs expressed in number of days 

from the requisition dates for those requisitions containing F or R in rp 62.

AP2.14.10.10 Required Delivery Period (RDP). For conventional ammunition requisitions 

only when materiel is required to be delivered within a specific time period; such as, materiel for 

an exercise which is not required before or after the exercise, an RDP may be established as 

outlined below and entered in rp 62-64:

AP2.14.10.10.1 Decide the latest acceptable delivery date, then calculate how many days 

this date is past the date of the requisition. Assign this number of days to the last two positions of 

the RDP (rp 63-64). (The RDP allows the last acceptable delivery date to reach up to but not 

exceed 99 days past the date of the requisition.)

AP2.14.10.10.2 Decide the earliest acceptable delivery date. Determine how many days 

this date is before the last acceptable delivery date. Match this number to the corresponding letter 

in the RDP table below. Assign this letter to the first position of the RDP (rp 62). (The RDP 

allows the earliest acceptable delivery date up to, but not greater than, 14 days before the last 

acceptable delivery date.)

B C D G H J K L M P T U V W

1 2 3 4 5 6 7 8 9 10 11 12 13 14

AP2.14.10.10.3 In the above manner, a requisitioner may specify an RDP without the use 

of exception data. As an example, assume a requisition has an ordinal date of 2125, and the last 

acceptable delivery date is 30 days after the date of the requisition (2155), while the earliest 

acceptable delivery date is 2 days before the latest acceptable delivery date (2153). In this case 

two positions of the RDP would be 30, and the first position would be C (2 days before 2155– the 

last acceptable delivery date). The RDP would appear on the requisition as C30.
 

DoD 4000.25-1-M

Enclosure 3

16

Approved DLMS Change 57 Attachment

Enhanced Edits for the Required Delivery Date (RDD) Data Field in Requisitions

MILSTRIP Appendix AP2.16 Extract

Revise AP2.16, Status Codes. Revise BK status as indicated.

 BK Modified. 

(1) Requisition data elements have been modified as requested. Examine data fields 

in this status document for current requisition data.

(2) Used by DAASC on DI AE9 to advise that the requisition contained a requisition 

priority for which the activity was not authorized. The requisition priority has been 

downgraded as shown and the requisition forwarded for processing. 

(3) Also uUsed by DAASC on DI AE9 to advise the customer that the requisition 

contained an invalid/expired OSD/CJCS Category D Project code. The project code 

has been blanked out and the requisition forwarded for processing. 

(4) Used by DAASC on DI AE9 or by supply source to advise the customer that 

the requisition priority designator and/or RDD data fields contained invalid or 

incompatible data. Customer entry has been modified or blanked out and the 

requisition forwarded for processing.