IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 2206Q-6221 

May 16,2013 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 1065, 

Modification to the Required Delivery Date (RDD) Edit for Ammunition and 

Ammunition-Related Requisitions and Requisition Alerts under Navy Base 

Realignment and Closure (BRAC) Retail Supply Storage and Distribution 

(SS&D)/Inventory Management and Stock Positioning (IMSP) (Supply/MILSTRIP) 

The attached change to Defense Logistics Manual (DLM) 4000.25, Defense Logistics 

Management System (DLMS) and DLM 4000.25-1, Military Standard Requisitioning and Issue 

Procedures (MILSTRIP), is approved for immediate implementation by DLA Transaction 

Services. The requisition alert exclusion must be implemented late May-early June. The expanded 

criteria for ammunition and ammunition-related materiel exclusion may be implemented 

separately. DLA Transaction Services must provide actual implementation dates to the DLA 

Logistics Management Standards Office. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 703-

767-0676 or DSN 427-0676, e-mail: ellen.hilert@dla.mil, or Ms. Heidi Daverede, DOD 

MILSTRIP Alternate, 703-767-5111; DSN 427-5111 , e-mail: heidi.daverede@dla.mil. Others 

may contact their Component designated Supply PRC representative available at: 

www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

..C, #~~ DONALD C. PIPP 

Director 

Defense Logistics Management 

Standards Office 

Federal Recycling Program 0 Printed on Recycled Paper 
ADC 1065, Attachment

Page 1

Attachment to ADC 1065,

Modification to the Required Delivery Date (RDD) Edit for Ammunition and AmmunitionRelated Requisitions and Requisition Alerts under Navy Base Realignment and Closure 

(BRAC) Retail Supply Storage and Distribution (SS&D)/Inventory Management and Stock 

Positioning (IMSP)

1. ORIGINATOR: Defense Logistics Agency (DLA) J331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Supply/ Logistics (Requisitioning)

3. REFERENCES: 

a. Functional Requirements for DLA’s implementation of the BRAC SS&D/IMSP

b. Approved DLMS Change (ADC) 57, Enhanced Edits for the Required Delivery Date 

(RDD) Data Field in Requisitions, dated May 23, 2002

c. ADC 57B, Revisions to Required Delivery Date (RDD) Edit, dated April 15, 2004

d. DLM 4000.25, Defense Logistics Management System (DLMS), Volume 2, Supply, 

Chapter 4, Requisitioning

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

Refer to Chapter 3, Requisition Processing and Related Action for requisition edit procedures, 

and Appendix 3, Formats Introduction, for guidance on recognizing ammunition and ammunition 

related materiel.

4. REQUESTED CHANGE:

a. Overview:

(1) This change provides a revision to the business rules relating to the use of the

RDD on requisition alerts, requisition alert modifications, and requisition alert follow-ups to 

support long lead time requirements supported by DLA under approved Navy BRAC

SS&D/IMSP procedures. Under this change, the Navy Fleet Readiness Center (FRC) will be 

allowed to submit requisition alert transactions using an RDD that exceeds the current restriction 

that requires a standard RDD to fall within 100 days of the document number date. 

(2) This change includes an administrative update to clarify procedures associated 

with the ammunition requisition 100-day edit and expand the applicability to additional federal 

supply classes (FSCs) for ammunition and ammunition-related materiel.

Staffing Note: This update for ammunition and ammunition-related materiel is the result of 

staffing comments and was not identified in the original proposal.
ADC 1065, Attachment

Page 2

b. Background: 

(1) ADC 57 (Reference 3.b.) provided tighter RDD and Priority Designator edits at 

DLA Transaction Services (planned for later implementation by Inventory Control Points (ICPs) 

under modernization) in response to DOD Inspector General Audit Report, Required Delivery 

Dates in Requisitions for Secondary Items of Supply Inventory, Report No D-2000-113, April 

19, 2000. Under this change, RDDs must fall within a 100-day timeframe subsequent to the

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

unreasonable RDDs. 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 (DLMS Special Requirements Code).

(2) ADC 57B authorized a Navy requisition exception to the standard RDD edit 

based upon the 100-day timeframe. This edit exception was applicable to the Naval

Ammunitions Logistics Center (NALC) and was based upon the Navy cognizance (COG) 

symbol in the transaction (legacy record position 55-56 equal to 0T, 2D, 2E, 2T, 4T, 6T, 8E, 8T,

or 8U and document number Service Code N, P, Q, R, or V). Under ADC 57B (Reference 3.c.), 

the edit was expanded to all Services based upon FSC 1300 (conventional ammunition). The 

MILSTRIP manual was updated upon publication of ADC 57B to drop the reference to the 

NALC in the footnote used to identify the authorized exception; instead the FSC 1300 was used 

to indicate the wider applicability of the exception. In response to the staffing of PDC 1065, the 

Navy commented that the original version of the edit based upon the COG symbol had a much 

broader applicability to different NSNs within the Navy, and so the sole reference to the FSC 

1300 was misleading. After further research, the MILSTRIP Administrator concluded that the 

Defense Automatic Addressing System (DAAS) edit is no longer consistent with the 

DLMS/MILSTRIP procedures to identify ammunition and ammunition-related materiel based 

upon additional FSCs. 

(3) In conjunction with the finalization of this ADC, the MILSTRIP Administrator 

contacted the Air Force to determine if the intra-Air Force exception authorized under ADC 57B 

(Reference 3.c.), could be withdrawn. This exception authorized use of Air Force unique codes 

within the legacy RDD field on an intra-Air Force basis. The Air Force determined that there are 

still pockets of legacy transactions requiring continued processing under this exception.

(4) As a result of the 2005 BRAC decision, retail supply, storage and distribution 

functions and associated infrastructure supporting the Navy industrial/maintenance sites will 

transfer to DLA. DLA will become the materiel provider to the FRC sites. Navy industrial 

activities (IAs) use requisition alert transactions to provide advance notification to the source of 

supply allowing stock positioning or procurement action in response to the forecasted future 

funded requirement. The requisition alert itself is an unfunded requirement. DLA requires 

visibility of an RDD ranging from 100 to 365 days to accomplish planning and procurement of 

long lead time items in support of the maintenance mission at the BRAC SS&D FRC sites. The 

operational requirement identified in the proposal is specific to the FRC and does not impact 

Naval Shipyard (NSY) procedures.
ADC 1065, Attachment

Page 3

c. Detailed Procedures: 

(1) Navy Requisition Alert. The following exception criteria and procedures are 

applicable to Navy requisition alerts.

(a) DLA Transaction Services will modify the edit currently applied to 

requisitions RDDs allowing the RDD to exceed the 100 day restriction for requisition alerts

(511R), requisition alert modifications (DLMS 511M), and requisition alert follow-ups (DLMS 

869F). Requisition alert transactions are identified by the Action Code 83, interpreted as 

Requisition Alert (DLMS 511R/511M at 1/BR06/20 and the DLMS 869F at 1/BSI09/20 

Qualifier 83 (Future)).

(b) FRC sites will request materiel in advance of the start of an availability 

using a requisition alert. This will serve as a notice to DLA that an item is required in advance 

of a scheduled maintenance project. 

(c) The FRC sites will identify the RDD, which may fall between 100-365 

days in advance of the document number date, on requisition alerts. Any RDD that exceeds 1 

year from the document number date will use extended RDD coding (DLMS Special 

Requirements Code S or X). Valid transactions will be passed to DLA for planning and 

procurement of materiel in advance of the RDD. 

(d) DLA’s Enterprise Business System (EBS) will post the RDD to the 

associated sales order created from the processing Requisition Alert. Inventory will be 

positioned at the applicable site in advance of a scheduled maintenance project. Accurate RDDs 

support DLA in accomplishing the task of planning and procurement to place that materiel at the 

industrial site and react with one of the following actions:

• Protect materiel when readily available under DLA ownership at the 

IA site.

• Request materiel be moved from co-located Distribution Depot to the 

IA site and protect materiel under DLA ownership in support of maintenance mission.

• Generate a redistribution order to move materiel within the DLA 

network to the IA site and upon receipt protect under DLA ownership in support of maintenance 

mission, or

• generate a new procurement or request to other source of supply, 

protecting materiel under DLA ownership upon receipt in support of the maintenance mission.

(e) When a requisition modifier for a requisition alert is received and 

processed in EBS, the modified fields will be updated and the applicable Supply Status will be 

returned to customer. 

(f) When a follow-up action for a requisition alert is received and processed in 

EBS, a Supply Status will be returned to customer reflecting all applicable data elements from 

the requisition alert.
ADC 1065, Attachment

Page 4

(g) When the materiel is required for use, a funded requisition will be 

provided. The exception for long lead time RDDs will not apply to funded requisitions.

(2) Ammunition and Ammunition-Related Materiel. The 100-day RDD edit 

exception provided for conventional ammunition is currently implemented as applicable to Navy 

COG symbols (0T, 2D, 2E, 2T, 4T, 6T, 8E, 8T, and 8U) and federal supply group (FSG) 13. In 

association with the publication of this ADC, the ammunition exception will be expanded to 

include the following additional FSCs: 1410, 1420, 1427, 1440, 5330, 5865, 6810, and 8140. 

This exception applies to standard MILSTRIP requisitions, requisition modifications, and 

requisition follow-ups. 

(3) Intra-Air Force Requisitions. No changes; ADC 57B exception is retained.

d. Revisions to DLM 4000.25 Manuals: 

(1) Revise DLM 4000.25 DLMS Volume 2, Chapter 4, Table C4.T5, Requisition 

Processing and Related Actions, as shown:

CODE OR DATA ELEMENT ENTRY IS BLANK OR INCORRECT

Required Delivery Date (preceding text not shown)

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

indicate a calendar date that falls no more than 100 days subsequent 

to the requisition date,

29 furnish BK supply status, and process. By 

authorized exception30, the 100-day edit is not applicable to:

(1) ammunition and ammunition-related requisitions 

identified by any of the following: Navy Cognizance Symbol 0T, 

2D, 2E, 2T, 4T, 6T, 8E, 8T, or 8U; Federal Supply Group (FSG) 

13; or Federal Supply Class (FSC) 1410, 1420, 1427, 1440, 5330, 

5865, 6810, or 8140 ;

(2) requisition alert processing under Navy/DLA industrial 

activity support agreement.

29 Not applicable for intra-USAF requisitions. 30Refer to ADC 1065. The 100-day edit is not applicable to requisitions for FSC 1300 (conventional 

ammunition

(2) Revise DLM 4000.25-1, MILSTRIP Chapter 3, Table C3.T2, Requisition 

Processing and Related Actions, as above (footnote numbering must be adjusted).

(3) Numerous DLMS changes have been published in support of Navy BRAC 

SS&D)/IMSP. DLA J33 Supply PRC representatives are responsible for coordination with 

the appropriate DLA and Navy offices for development and submission of documentation 

for the DLMS procedures associated with BRAC for the DLMS manual.

e. Proposed Transaction Flow: No change.
ADC 1065, Attachment

Page 5

f. Alternatives: None identified.

5. REASON FOR CHANGE: DLA and Navy require the ability to pass appropriate RDDs

between systems for planning and procurement of long lead time items. Expansion of the criteria 

used for the ammunition-related requisition exception to include additional FSCs provides 

greater consistency across the DLMS. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: This change allows DLA access to known requirements to position

materiel at an IA site prior to the start of a maintenance initiative with sufficient lead time when 

new procurement is required. Additionally, it clarifies current requirements for ammunition and 

ammunition-related RDD edits and removes obsolete guidance.

b. Disadvantages: Not having the correct RDD passed from the NAVAIR Depot 

Maintenance System (NDMS) to EBS will prevent DLA from providing adequate support to the 

FRC mission. 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This change requires nearterm implementation due to operational impact and imminent deployment of FRC support 

processes within DLA. The target implementation for the requisition alert exclusion is the MayJune 2013 timeframe. DLA Transaction Services may implement this portion of the change 

immediately. The expanded criteria for ammunition and ammunition-related materiel exclusion 

may be implemented separately. DLA Transaction Services must provide actual implementation 

dates to the DLA Logistics Management Standards Office.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available.

9. IMPACT: 

a. New DLMS Data Elements: This change requires no new DLMS data elements.

b. Changes to DLMS Data Elements: This change requires no changes to existing 

DLMS data elements.

c. Automated Information Systems (AIS): 

(1) DLA must ensure internal EBS edits will accept the Navy requisition alert RDD 

as authorized in this change. 

(2) Service ammunition systems may be impacted (if so desired) in order to apply

the expansion of the authorized RDD exception to additional FSCs.

d. DLA Transaction Services: 

(1) Revise the RDD edit process to remove the 100-day restriction for Navy 

requisition alert transactions (based upon the requisition alert indicator). Navy requisition alerts 

will be authorized to submit RDDs up to one year in advance of the document number date. 
ADC 1065, Attachment

Page 6

(2) Expand existing criteria for identification of ammunition and ammunition-related 

transactions using Navy COG Symbols 0T, 2D, 2E, 2T, 4T, 6T, 8E, 8T, 8U and FSG 13 to also

include FSCs 1410, 1420, 1427, 1440, 5330, 5865, 6810, and 8140.

(3) Retain RDD edit exception for intra-Air Force requisitions.

e. Non-DLA Logistics Management Standards Publications: DLA internal guidance

may require update to document this exception.
ADC 1065, Enclosure

Page 1

Enclosure, Comment Resolution

PDC 1065 Comments

Submitter Response Resolution

1. DLA Concur.

A systems change request is being worked by our IMSP 

build team. Synchronized implementation between EBS and 

DLA Transaction Services will not be required; DLA 

Transaction Services can implement as soon as available

Noted.

ADC has been updated.

2. Air Force Concur.

Regarding the intra-Air Force exception: Rota Air Station, 

Spain still uses the RDD exclusion. Thus, we need to keep

the exclusion in place for the time being.

Noted.

Intra-Air Force 

3. Marine Corps Concur. Noted.

4. Army Concur. Noted.

5. USTRANS

COM

Abstain. There is no impact to USTRANSCOM systems 

based on this change.

Noted.

6. Navy Concur.

Navy requests that a change be made to this PDC to more 

accurately exempt ammunition.

This PDC (PDC 1065) is making changes to previously 

approved DLMS Change 57. Change 57 had an exception 

that said:

"5 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."

This PDC, 1065, has the exception written as:

"The 100-day edit is not applicable to requisitions for FSC 

1300 (conventional ammunition)."

The issue we see is that there are many other FSC's in use for 

conventional ammunition other than ones that start with 

1300. Navy requests that we keep the existing edits for 

exempting the even COG items as was done under Change 

Noted.

Concur. The current 

footnote wording is 

inaccurate and misleading. 

The edit will continue to 

employ Navy COG symbol

and FSG 13. Additionally, 

the FSCs used for the edit 

are expanded to include the 

ammunition and 

ammunition-related FSCs 

validated under ADC

441/441A,

Clarification to Exception 

Rules to Accommodate 

Communication of 

Ammunition/Ammunition 

Related Quantities in 

Excess of Five Digits and 

reflected in MILSTRIP, 

Appendix 3.1, Formats 

Introduction (see paragraph 

AP3.1.3.1. for ammunition 

guidance). This update 

will provide consistency 

across the DLMS/
ADC 1065, Enclosure

Page 2

PDC 1065 Comments

57B.

If you change to the new edit of only exempting FSC 1300 

material, there is the chance that our ammo docs will be 

modified to have the RDD stripped if the RDD is in excess 

of 100 days. The FSC's currently in use other than the 1300 

series FSC's in our ammo systems are:

1040, 1055, 1075, 1095, 1260, 1285, 1290, 1410, 1420, 

1427, 1440, 1450, 1670, 2840, 3990, 4010, 4020, 4030, 

4220, 4440, 4710, 4730, 4921, 4923, 4925, 4935, 5120, 

5130, 5305, 5306, 5307, 5310, 5315, 5325, 5330, 5331, 

5340, 5342, 5355, 5360, 5365, 5821, 5826, 5845, 5865, 

5910, 5930, 5935, 5960, 5985, 5998, 6105, 6130, 6135, 

6140, 6150, 6160, 6625, 6640, 6645, 6655, 6810, 6830, 

6910, 6920, 7610, 8110, 8135, 8140, 8145, 8345, 9150,

9310, 9535

MILSTRIP/MILSTRAP

for procedures related to 

ammunition/ammunitionrelated materiel. (Note: 

This is not an exact match 

for the FSCs identified by 

the Navy.) The exclusion 

guidance is updated to 

identify cognizance 

symbols and applicable 

FSG/FSCs.