1 Proposed Revision to ADC 338A 

 Attachment 

Proposed Revision to ADC 338A 

Surge Requirements of MSM under Navy BRAC SS&D IMSP 

1. ORIGINATOR: 

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

b. Originator: DLA J-331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/ Logistics.

3. REFERENCES: 

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

b. DLA Logistics Management Standards Office (formerly DLMSO) memorandum dated 

September 28, 2009, subject: ADC 338, New Advice Code for Surge Requirements of Mission 

Support Material (MSM) under Navy Base Realignment and Closure (BRAC) Inventory Management 

and Stock Positioning (IMSP) 

4. REQUESTED CHANGE: 

a. Description of Change: This change republishes ADC 338 to replace the assigned advice 

code with a new management code for use on DLMS transactions associated with requisitioning to 

identify surge requirements for Mission Support Material (MSM) under DLA-Navy BRAC IMSP. 

Use of a management code (in lieu of an advice code) to identify surge requirements will allow for 

continued independent use of applicable advice codes on the requisition. The management code will 

be used to trigger special processing rules in DLA’s Enterprise Business System (EBS). 

b. Background: As a result of the 2005 BRAC decision, retail supply, storage and distribution 

(SS&D) functions and associated infrastructure supporting Service industrial/maintenance sites will 

transfer to DLA. In Spiral 2, there will be two Naval Shipyards (NSY) and three Fleet Readiness 

Centers (FRCs) transferring to DLA. Naval Shipyards have multiple shop service centers supporting 

the maintenance mission with items stocked based on established levels. The items in these service 

centers are referred to as Mission Support Material (MSM). During a job availability there will be 

times when surge requirements must be met for items identified as MSM stock. DLA will process the 

request for surge quantities applying unique logic developed to allow the request to process to 

appropriate source for fulfillment and not deplete local industrial site on-hand quantities. Also DLA 

will continue to replenish to any appropriate level, excluding due-ins identified as surge request. 

Unique logic will be limited to FRC and Shipyard requests. All other requisitions will bypass this logic 

within EBS. 

c. Clarification of Navy Users for New Management Code: The UICs/DoDAACs the shipyard 

and the FRCs will use in requisitions containing the new management code are the same ones that are 

currently being used today for both CAV-ORM and any Navy funded requisitions. However, the new 

management code would not be in any of the CAV-ORM requisitions as they are created and sent out 
Proposed Revision to ADC 338A 

Attachment 

2

via a different path directly into CAV-ORM via DAASC (to be verified during testing). 

d. Clarification for use of Management Code in lieu of Advice Code. During the NSY critical 

design review (CDR) it was brought to everyone’s attention the proposed design for identifying surge 

requests using one advice code did not meet the NSY current functionality. There are instances where 

a ‘screen out’ code is used with different advice codes for surge requirements. Research of NSY usage 

indicates additional logic would be needed to accommodate multiple advices codes submitted with a 

‘screen out’ code. However, since the Navy systems involved already recognize and react to the 

current advice codes, DLA is requesting a management code be assigned for the ‘screen out’ code , 

which will allows the NSY sites to continue with their current use of the advice codes. The Navy 

MAT application will be modified to map the new management code when the ‘screen out’ code is 

applicable. DLA EBS will be modified to apply the current logic developed for the Advice Code 3C 

to the new management code. There are no modifications required for the Distribution Standard 

System. 

e. Detailed Procedures: 

1) Delete ADC 338 Advice Code 3C from the DLMS Dictionary and MILSTRIP Appendix 

AP2.15, Advice Codes. 

Code Explanation

3C Identifies surge requirements for mission support material (MSM) that are to be 

processed as one-time requests and not sourced against on-hand assets. Applicable 

to DLMS requisition alerts, requisitions, and follow-on transactions for DLAsourced materiel under Navy BRAC IMSP.

3C through 3J Deleted. 

2) Establish Management Code S in the DLMS Dictionary and MILSTRAP Appendix 2.6, 

Management Codes. Refer to Enclosure 1. Management Code S is authorized for use in funded 

requisitions and requisitions alerts including the following DLMS transactions: 511R, 511M, 869F, 

869C. Staffing note: The Management Code S will not be perpetuated to the DLMS 940R, and 945A 

(as was stated for the original Advice Code 3C). This management code does not impact depot 

processing. 

Code Applicable DI Codes Explanation

S AO_, AM, AT_ (including 

Requisition Alert) 

Identifies surge requirements for mission support material 

(MSM) that are to be processed as one-time requests and not 

sourced against on-hand assets. Applicable to DLMS 

requisition alerts, requisitions, and follow-on transactions for 

DLA-sourced materiel under a DLA-Navy industrial activity 

support agreement.1

1/ Refer to ADC 338A. Note: The requisition alert transaction allows Navy industrial sites to notify DLA of 

their requirements in advance of the funded requisition, thereby allowing DLA to procure and position 

materiel appropriately to support prompt order fulfillment. Refer to ADC 352 for DLMS Requisition Alert 
Proposed Revision to ADC 338A 

Attachment 

3

procedures.

f. Alternatives: None identified. 

5. REASON FOR CHANGE: DLA requires ability to recognize a request for MSM items in 

support of Direct Material Inventory (DMI), for surge quantities on the submitted Requisition Alert to 

process as a one-time request and not source against available on-hand assets potentially exhausting all 

available inventories. For continued visibility, the new value will be perpetuated to any follow-on 

transaction allowing for the inclusion of the management code, to include the funded requisition.

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: 

1) EBS will recognize Requisition Alert in support of availability and treat as a request for 

DMI, ignoring on-hand assets, and process the request as one-time requirement. 

2) Use of a management code in lieu of an advice code preserves existing functionality for 

the Navy to use various MILSTRIP advice codes as applicable in conjunction with an MSM surge 

requirement.

 b. Disadvantages: N/A. 

7. IMPACT: 

 a. Requires revision to previously planned use of the advice code. 

b. Publications: MILSTRAP Appendix and DLMS Dictionary updates required. DLMS manual 

procedures to be provided separately. 

 c. Implementation Schedule. January 2010 
 1 Proposed Revision to ADC 338A 

 Enclosure 1 

Enclosure 1, MILSTRAP Extract 

AP2.6. APPENDIX 2.6

MANAGEMENT CODES

AP2.6.5. REQUSITION TRANSACTIONS. Management codes are assigned for use in requisitionrelated transactions: 

CODE APPLICABLE DI CODES EXPLANATION 

A thru L AO_, AT_1 Specific values as assigned by Army. Applicable 

on Intra-Army basis for post-post and image single 

stock fund activity requisitions. 

M thru N All DI codes Reserved for future DoD assignment. 

 

P AO_, AM, AT_ 

(including Requisition 

Alert)2

Re-requisitioned materiel to be alternatively 

sourced subsequent to receipt of deficient materiel 

(prior requisition document number must be 

identified for cross reference; PQDR required). 

Applicable only to DLMS requisition alerts, 

requisitions, and applicable follow-on transactions 

for materiel requisitioned from DLA under BRAC 

SS&D IMSP.1

Q thru R All DI codes Reserved for future DoD assignment. 

S AO_, AM, AT_ 

(including Requisition 

Alert)3

Identifies surge requirements for mission support 

material (MSM) that are to be processed as onetime requests and not sourced against on-hand 

assets. Applicable to DLMS requisition alerts, 

requisitions, and follow-on transactions for DLAsourced materiel under a DLA-Navy industrial 

activity support agreement. 

T thru Z All DI codes Reserved for future DoD assignment. 

0 thru 9 All DI codes Reserved for future DoD assignment. 

 

1

 Refer to ADC 243. 

2

 Refer to ADC 352, implementation date January 2011. 

3 Refer to ADC 338A, implementation date January 2011. Note: The requisition alert transaction allows Navy 

industrial sites to notify DLA of their requirements in advance of the funded requisition, thereby allowing DLA to 

procure and position materiel appropriately to support prompt order fulfillment. Refer to ADC 352 for DLMS 

Requisition Alert procedures.