Attachment, ADC 1062

Page 1

Attachment to ADC 1062

Non-Inventory Control Point/Integrated Materiel Manager (ICP/IMM)-

Directed Inter-Service Lateral Support via Retail Level Passing Order

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Global Combat 

Support System-Army (GCSS-Army): U.S. Army Combined Arms Support Command 

(CASCOM), Logistics Enterprise System Support Branch, GCSS-Army Supply Team Lead 

(804-279-8086), and CASCOM Chief Enterprise System Division, (804-734-1212).

2. FUNCTIONAL AREA: Supply Logistics/Requisitioning

3. REFERENCES:

a. DLM 4000.25, DLMS, Volume 2, Supply

b. DLM 4000.25, DLMS, Volume 4, Finance

c. DLM 4000.25, DLMS Volume 6, Logistics Systems Interoperability Support 

Services, Chapter 4, Pipeline Measurement

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

4. APPROVED CHANGE(S):

a. Brief Overview of Change:

(1) Under DOD’S current MILSTRIP procedures, requisitions from Military Services 

to the national-level Sources of Supply (SoS) are normally transmitted to Defense Logistics 

Agency (DLA) Transactions Services and then routed to the appropriate SoS as populated on the 

Federal Logistics Information System (FLIS) catalog record for the materiel. This change

authorizes Military Service requiring activities to bypass standard ordering from the cataloged 

FLIS SoS and, instead, use requisition passing order transactions directed to the Global Combat 

Support System-Army (GCSS-Army) Supply Support Activities (SSA) to satisfy high priority,

mission readiness requirements, thereby reducing lead-time for both deployed and non-deployed 

forces. This process was designed to accommodate a pre-approved other Military Service

customer submitting a requisition to a GCSS-Army SSA for non-Army managed materiel 

(referred to by the Army as Non-Army Managed Item (NAMI)) or Army Managed Item (AMI) 

materiel from the Army SSA in close proximity.

(2) This process is not designed to replace MILSTRIP procedures for Inventory 

Control Point-directed DOD Lateral Redistribution or DLA stock optimization capabilities. 

Instead, the goal is to proactively assist the Army in meeting the Commander’s readiness 

requirements when mission critical materiel are available in SSAs in the same geographical area 

as determined by asset visibility provided by GCSS-Army. 
Attachment, ADC 1062

Page 2

(3) The requirements in this solution require DLA Transaction Services to pass the 

requisition passing order transaction to the appropriate GCSS-Army SSA identified by the 

Routing Identifying Code (RIC)-To that will be populated on the DLMS 511R/Document 

Identifier Code (DIC) A3_ transaction initiated by the requesting Military Service. The 

requisition passing order transaction will be submitted by pre-approved other Service customers

who have been given roles and permissions in GCSS-Army to perform an asset visibility check 

for the predetermined GCSS-Army SSA in close proximity to their location. If materiel is 

available, the other Service has the option of submitting a requisition passing order transaction 

through DLA Transaction Services with the appropriate GCSS-Army SSA RIC-To identified as 

the predetermined SoS for this lateral Service to Service high-priority requirement.

(4) An update to the DLMS/MILSTRIP manual guidance for ICP/IMM-directed lateral 

redistribution of retail assets is provided for consistency with DOD policy and identification of 

an exception for this process.

b. Background: 

(1) The requirement identified in this change was initially instituted in the Army retail 

level legacy environment at the request of combatant commanders for Operation Iraqi Freedom

(OIF) II. In 2004, a System Interface Agreement was established between United States Army 

and United States Marine Corps. Its intent was to support logistics objectives in the Area of 

Responsibility (AOR) in theater across other Services for tactical readiness purposes. GCSSArmy is developing processes and interfaces that will allow GCSS-Army to provide high-priority 

requisition support to other Military Services from one of its SSAs. 

(2) Prior to staffing the original proposed change, it was reviewed from a policy 

perspective by the Office of the Deputy Assistant Secretary of Defense for Supply Chain 

Integration (ODASD (SCI)) and authorization to proceed with formal staffing was provided. 

ODASD(SCI) expressed concern that the demand filled by the retail level supply source should 

also be communicated to the wholesale ICP/IMM (refer to Paragraph 9) . 

(3) These processes will allow transactions to be sent to or from GCSS-Army through 

intermediate systems such as Army Enterprise System Integration Program (AESIP) and DLA

Transaction Services to include:

(a) Requisition: Materiel requests (DLMS 511R/DIC A3_) will be sent by 

other Services (on an exception basis) to DLA Transactions Services and passed to AESIP with 

final destination to GCSS-Army. The other Services would place the RIC of the desired GCSSArmy SSA on the requisition passing order transaction (DLMS 511R/A3_) allowing DLA 

Transaction Services to pass the transaction to the intended GCSS-Army SSA. Use of the 

passing order allows the requisition to bypass DLA Transaction Services’ SoS routing logic and,

consequently, get passed directly to GCSS-Army SSA.

(b) Status: Supply status (DLMS 870S/DIC AE8_) will be sent by GCSS-Army 

via DLA Transaction Services to other Services in response to receiving and processing their 

high priority requisition. For Wave 1 the order will only be available for customer pick-up. The 

fill or kill supply support relationship with other Services solution introduced in GCSS-Army’s 
Attachment, ADC 1062

Page 3

Wave 1 design will facilitate the appropriate GCSS-Army status to the other Service when a 

partial or full quantity is available and filled by the GCSS-Army SSA. GCSS-Army will send 

the appropriate status for all unfilled quantities including any requisitions rejected for quantity,

priority, DoDAAC, etc. Shipment Status (DLMS 856S/DIC AS_) will be produced and provided 

to the requisitioning other Service for tracking and reporting purposes. 

c. Approved Change in Detail:

(1) Other Services will have asset visibility of stockage levels in GCSS-Army via 

Stock Requirements List (MD04 transaction). The asset visibility capability will be provided to 

approved customers through establishment of roles and permissions in the GCSS-Army portal. 

The asset visibility capability is a process intended to be used upfront in this ordering process 

before requesting a high-priority materiel. Asset visibility will be extended across all stocks for 

the GCSS-Army SSA within close proximity or geographic area. This access will be an interim 

solution until the Office of Secretary of Defense’s Strategic Network Optimization (SNO) 

initiative is in place. The SNO initiative is being led by DLA and is intended to provide asset 

visibility across all Service Enterprise Resource Planning (ERP) systems for the purpose of 

strategic optimization of resources and ICP-directed lateral support. 

(2) Requisition passing orders (DLMS 511R/DIC A3_ with Transaction Type Code 

BM) with applicable Action Code (BR06=RI) originating from the approved other Service 

requiring activity will be passed via DLA Transaction Services to GCSS-Army per the identified 

RIC-To under this process. These requisitions must be high priority (indicated by Priority 

Designator (PD) 01 - 03) and required for mission readiness (indicated by DLMS Special 

Requirements Code N (Not Mission Capable Supply (NMCS) (equivalent to the legacy coded 

Required Delivery Date) or Expedited Handling Signal 999. All other transactions will be 

rejected and result in supply status with appropriate status code being sent back to requesting

customer.

(3) Requisitions from the other Services will contain an Advice Code 2C or 2J, 

causing them to be “filled” or “killed” by GCSS-Army. GCSS-Army will not backorder an item 

under this process.

(4) Requisitions from other Services will be required to contain a valid fund code. 

This will be the responsibility of the requiring Service; no new edits are imposed by this 

requirement. If an invalid fund code were provided inadvertently, the submitter's default account 

will be billed under MILSBILLS procedures

(5) Instead of sending a requisition through DLA Transaction Services, the other 

Service can initiate a “walk-thru” sales order directly in the GCSS-Army portal. This will cause 

the subsequent transactions (supply status, requisition image, demand report, and post-post 

requisition, as described below) to be produced in the same manner as if the order were initiated 

by a passing order requisition transaction.

(6) GCSS-Army will apply the same stock availability rules to other Service

requisitions as it would to its own units, on a first-come, first-served basis based on priority and 

date of requisition.
Attachment, ADC 1062

Page 4

(7) An accepted requisition from the other Services will cause GCSS-Army to create 

a sales order in its system and send a Requisition Image (DLMS 511R/DIC A0A with Action 

Code=FI (at 2/BR06)) and Demand Report (Army unique DIC BAH) to Army wholesale, as is 

done now for a demand from an Army customer. GCSS-Army will also send a Supply Status 

(DLMS 870S/DIC AE8_) to other Services indicating the quantity available (Status Code BT or 

BH). If the item is only partially available, a Supply Status with Status Code CB will also be 

sent, indicating the quantity not available.

(8) An unaccepted requisition from the other Services will cause GCSS-Army to send 

a Supply Status to other Services with Status Code CA. Use of the Status Code CA requires a 

narrative explanation for the cancellation. Under DLMS, the explanation is provided as an 

enhancement to the supply status transaction (rather than sending a separate message to the 

requisitioner). 

(9) Invalid requisitions will be rejected and a Supply Status provided (e.g., Status 

Codes CD, CG, CX, etc.).

(10) The sales order in GCSS-Army will normally have the goods issue completed the 

same day. This will cause an additional Supply Status with Status Code BA to be sent to other 

Services, and a goods issue post-post issue DLMS 511R/DIC A0A with Action Code J (at 

2/BR06) to be sent to Army wholesale. The post-post transaction will contain Army Edit Action 

Code IV (DLMS LQ01 Qualifier DJ equates to legacy record position (RP) 74-75), which 

indicates the issue and triggers the billing at Logistics Modernization Program (LMP). 

(11) The GCSS-Army will provide a Shipment Status (DLMS 856S/DIC AS_) as a 

result of the issue of the materiel to the other Service. The DOD Transportation Mode/Method 

Code X (Bearer, Walk-Thru (Customer Pick-Up)) applies. If subsequent waves of this 

implementation result in deliveries to the customer, the appropriate DOD Transportation 

Mode/Method should be applied.

d. Revisions to DLM 4000.25 Manuals: 

(1) This change requires update to DLM 4000.25 DLMS Volume 2, Chapter 11. 

Comparable changes are required for DLM 4000.25-1, MILSTRIP, Chapter 9 (use the same 

wording as shown below, except the data element Special Requirements Code will be referred to 

as coded RDD). Update the introductory paragraph for ICP/IMM directed lateral redistribution 

guidance and insert new section for non-ICP/IMM directed inter-Service lateral redistribution as

shown in bold red italics. Renumber remaining paragraphs.
Attachment, ADC 1062

Page 5

“C11.17. INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGER 

LATERAL REDISTRIBUTION OF RETAIL ASSETS

C11.17.1. Purpose. This paragraph outlines procedures for filling back orders by 

generating lateral redistribution orders for retail materiel that has been identified through an 

inter- or intra-DoD Component retail asset visibility system. Additionally, ICPs/IMMs 

may use these procedures to direct lateral redistribution when the total cost of such 

action is lower or when the wholesale level does not have stock available to meet a 

requisition’s required response time. The DoD Components may elect to exclude 

government furnished materiel (GFM), security assistance, and contractor furnished 

materiel (CFM) backorders from these procedures under DoD 4140.1-R procedures.

(intervening text not shown)

C11.18 INTER-SERVICE LATERAL REDISTRIBUTION OF RETAIL ASSETS BY 

INTER-SERVICE AGREEMENT1

C11.18.1. Inter-Service redistribution will not occur before wholesale-level 

requisitioning, except within theater at Combatant Commander direction or as 

authorized by inter-Service agreement for lateral support of high priority mission 

readiness requirements where stock is available within the area of responsibility. 

C11.18.2. Prior to initiating MILSTRIP procedures for non-ICP/IMM-directed interService lateral redistribution, the requiring Service must establish a support agreement 

with the retail/tactical level supply source and employ agreed upon asset visibility tools to 

ensure that materiel is available. High priority mission readiness requirements (PD 01-

03 and Special Requirements Code N) may be submitted using a passing order 

requisition (DLMS 511R/DIC A3_ with Transaction Type code BM) identifying the retail 

source supply as the RIC-To. These transactions will bypass DAAS routing logic to the 

wholesale SoS. By alternative, the requiring Service may choose to skip the initiating 

requisition passing order transaction and request materiel in person as bearer walk-thru.

C11.18.3 Services supporting inter-Service lateral redistribution will ensure that only 

high priority mission readiness requisitions originated by pre-approved trading partners 

within the area of responsibility are honored. All such requisition passing orders will be 

processed on a fill or kill basis (Advice Code 2C or 2J). These requisitions are not 

subject to modification or follow-up; standard cancellation procedures apply. 

Transactional supply status will be provided regardless of initiating method (transaction 

or walk-thru). Upon receipt of BA status, the materiel will be available for pick-up by 

the requiring customer. Standard shipment status will be provided.

C11.18.3 The Service supply source has responsibility for preparation of Interfund 

billing and any required internal transactions associated with this method of lateral 

supply support.

----------------
Attachment, ADC 1062

Page 6

1 Refer to ADC 1062. Initial implementation applicable to Global Combat Supply System-Army 

(GCSS-Army) and authorized trading partners. Phased implementation for shipment status is 

authorized.”

(2) This change may result in Supply Discrepancy Reports (SDRs) (refer to paragraph 

9.d.) requiring update to routing rules due to lack of an automated interface between DOD 

WebSDR and Army systems. Update DLM 4000.25 DLMS Volume 2, Chapter 17, Supply 

Discrepancy Reporting, as follows:

“C17.3.10.2. SDR Distribution for Shipment (Item) Discrepancies

C17.3.10.2.1. DoD Originated Shipments. SDRs will normally be directed to 

the DoD shipping activity with exceptions and specific business rules as follows.

C17.3.10.2.1.1. Army Directed Shipments 

C17.3.10.2.1.1.1. Army Managed Item (AMI) and Non-Army Managed 

Item (NAMI)) Shipments. Initial action shall be directed to the source of supply (SoS). The 

only valid Army action activity/SoS RICs are AKZ, A12, A35, AJ2, B14, B16, B17, B46, B64, 

and B69. Army users are advised not to submit SDRs to single stock fund (SSF) site RICs or to 

Army shipping depot RICs via DoD WebSDR. There are currently no WebSDR interfaces to 

support SSF sites or Army shipping depots. The Army action activity can be determined from 

the shipping documentation (e.g., the RIC in record position 67-69 of the DD 1348-1A), or as 

part of a NIIN/NSN or Part Number search in WebFLIS (http://www.dlis.dla.mil/webflis/). 

Note that the FLIS SoS will not apply if the requisition was filled by AJ2, Non-Army Manager 

Item (NAMI) SoS. 

C17.3.10.2.1.1. 2. Army Ammunition Storage Activity Shipments. Services 

ammunition users are advised to send SDRs to B14 for ammunition commodity discrepancies. 

These SDRs will be further routed by the Army to Army ammunition storage depots that 

manage Army, Service common, and Service unique ammunition stock.

C17.3.10.2.1.1. 3. Global Combat Supply System-Army (GCSS-Army) InterService Lateral Redistribution of Retail Assets By Inter-Service Agreement. The Army 

requires that these SDRs to be processed by the AMI or NAMI ICP regardless of the FLISdesignated manager or the Army Supply Support Activity (SSA) providing lateral support. 

Any SDRs directed to the SSA will be transmitted to the default Army email account pending a 

system interface with DoD WebSDR or alternative guidance. The Army will ensure that these 

SDRs will be forwarded to the appropriate Army action activity and coordinated with the 

Logistics Modernization Program (LMP) for financial resolution when applicable.” 

(3) Revise DLM 4000.25 Volume 2, Appendix 3, Supply Discrepancy Report Relevant 

Data Elements, to support expanded use of Discrepancy Code Z5.

Z5 Immediate resolution/replacement of discrepant item under DLA industrial activity

inter-Service/Agency support agreement (restricted use per Service/Agency guidance) 
Attachment, ADC 1062

Page 7

e. Transaction Flow: 

(1) Normally, requisitions are processed through DLA Transaction Services where 

they are routed to the FLIS SoS. However, for high-priority mission readiness requirements, 

other Services would have the option of directing requisitions to a nearby GCSS-Army SSA after 

prior coordination and verification that assets are available. When GCSS-Army receives the 

request for issue, it will reply with the appropriate supply status (DLMS 870S/DIC AE8). DLA

Transaction Services will follow standard MILSTRIP distribution rules. This capability does not 

replace DOD Lateral Distribution or any DLA stock optimization capability that is existent 

today.

(2) Financially, as transactions are processed and orders are filled, GCSS-Army will 

employ the existing Interfund billing process to settle the financial obligations as a result of 

issues of materiel. Supported Services will continue to follow existing financial policies and 

procedures. When the SSA issues materiel, GCSS-Army will send a post-post requisition (postpost issue DLMS 511R/DIC A0A with Action Code J (at 2/BR06) containing Army Edit Action 

Code IV (at 2/LQ01 Qualifier DJ) to the wholesale system (LMP or Commodity Command 

Standard System (CCSS)) indicating that the other Service’s order has been filled, and triggering 

billing. The MILSBILLS transaction flow will occur between the Army LMP and the other 

Service’s financial systems based on fund codes/line of accounting provided by the other Service

to GCSS-Army in the passing order. 

f. Alternatives: The alternative to making the changes recommended in this change would 

be to create a direct interface between GCSS-Army and each of the supported Services.

g. Proposed DLMS Change (PDC) 1049 Staffing Response and Comment Resolution. 

Refer to the enclosure.

5. REASON FOR CHANGE: This change is required to accommodate an automated interface 

between the GCSS-Army and the other Services. This allows a GCSS-Army SSA to be 

populated on the transaction to accommodate the fill or kill support relationship design delivered 

in this interface solution as opposed to designated FLIS SoS.

6. ADVANTAGES AND DISADVANTAGES:

 a. Advantages: This change has the advantage of presenting an automated process that 

requires minimal changes to the existing requisitioning processes in each Service. It provides 

Combatant Commanders the capability and flexibility to utilize automated processes to satisfy 

their readiness requirements by utilizing other Service SSAs in close proximity of their Area of 

Operations (AO). It allows the utilization of a clear and concise variable in the process of 

determining the appropriate SoS for the requisition passing order. This automated process 

eliminates the need to put soldiers on Main Supply Routes (MSR) and in harm’s way without 

assurance that the materiel required is available for issue and released for pickup. Lastly, other

Services can leverage this change to establish similar supply support relationships with GCSSArmy SSAs. 
Attachment, ADC 1062

Page 8

 b. Disadvantages: This change requires the cooperation and timely processing of a number 

of other organizations rather than the existing direct interface employed today in our legacy 

Logistics Information System environment.

7. ASSUMPTIONS:

a. The requiring Service will exchange transactions via DLA Transaction Services.

 b. The interface to national-level systems will use DLMS XML formats with the exception

of the Army unique BAH Demand Report. The legacy format is used pending implementation of 

the DLMS 867D equivalent by GCSS-Army.

c. With the exception of a new code in the requisition to distinguish this process, there are 

no other changes required to the existing DLMS formats employed in this process.

d. DLA Transaction Services will receive and send DLMS XML transactions, except for 

BAH, to and from AESIP.

e. IDOC to DLMS or DLMS to IDOC mapping instructions for the new or changed 

interfaces will be provided to AESIP by the Army.

f. A predictor of future volume can be based upon past experience for the Army using a

direct interface with the Marine Corps and comparable business rules as follows: 

• SSA at Camp Bastion, Afghanistan, from June 2010 - January 2011, processed 

4,689 Marine Corps requisitions (filled 4,351, killed 212, and rejected 168 with 

Supply Status CA (with an additional 14 requisitions processed as bearer walkthru between June and November).

• SSA at Bagram AFB, Afghanistan, from June 2010 - Aug 2010 and November 

2010 - January 2011, processed 52 Marine Corps requisitions (filled 40, killed 

11, and rejected 2 with Supply Status CA (with an additional 42 processed as 

bearer walk-thru between July and September).

8. ADDITIONAL COMMENTS TO CONSIDER:

a. Phased Implementation. The provisions of this change are intended to address the 

GCSS-Army’s Wave I incremental requirement. That requirement is to be able to accommodate 

an automated “fill or kill” supply support relationship with other Services as mission and area 

support requirements permit. As GCSS-Army develops its future Wave 2 solution the scope of 

its supply support will be expanded to accommodate a fully supported capability that could 

potentially impact this change. GCSS-Army’s Wave 2 increment is currently scheduled for FY 

2017.
Attachment, ADC 1062

Page 9

b. Using Lateral Support for Reparable Items. Requiring activities are advised of the 

financial impact of using the lateral referral order procedures under this change where preestablished procedures are in place for exchange pricing based upon turn-in of the failed item.

9. ADDITIONAL FUNCTIONAL REQUIREMENTS:

 a. Demand Report Applicability. Under these procedures, GCSS-Army will report the 

other Service demand to the Army wholesale level to record the internal Army demand. When 

the materiel is managed by another Service/Agency, that Service/Agency will have no visibility 

of the demand.

 b. Materiel Receipt Acknowledgement (MRA) Applicability. Under current MILSTRAP 

procedures, requirements for submission of an MRA (DLMS 527R/DIC DRA) exclude lateral 

redistribution that is not ICP directed, so there is no current MRA requirement. If determined to 

be required in the future, GCSS-Army will be capable of receiving a MRA from the other 

Services.

 c. Pipeline Measurement Metrics. Currently, lateral support requirements are captured by 

the requiring Services in their internally calculated customer wait time metric. Support under 

these procedures will be measured/reported under customer wait time. Integration of this process 

under Logistics Metric Analysis Reporting System (LMARS) will not be pursued at this time 

because the focus of LMARS is wholesale level support.

 d. Supply Discrepancy Report (SDR) Applicability 

(1) Supply discrepancies, e.g. shortage, wrong item, or improper packaging, resulting 

from the non-ICP directed lateral support will be reported via SDR. At the discretion of the 

Army SSA, uninterrupted support with immediate resolution of the SDR (e.g. return of wrong 

item for exchange with the correct item) may be provided (Discrepancy Code Z5 applies). If the 

discrepancy resulted from a concealed discrepancy in a sealed vendor pack, the SSA will be 

responsible for reporting the discrepancy to the SSA’s original SoS.

(2) GCSS-Army has no capability to receive transactional SDRs. Any SDRs prepared 

via the other Service SDR application or input via DOD WebSDR will fail at DLA Transaction 

Services DOD WebSDR if addressed to the SSA. Additionally, the Army requires that SDRs be 

processed initially by the Army Managed Item (AMI) and Non-Army Managed Item (NAMI) 

ICP rather than the SSA. Therefore, pending a system interface or alternative solution, a new 

routing rule will be established for SDRs addressed to the SSA (or other non-routable Army 

activities. These SDRs will default to an Army email account and it will be Army responsibility 

to forward the SDRs to the appropriate action activity. 

 e. Requisition Follow-on Transactions: There is limited relevancy for requisition followon transactions in this process. The Requisition Modification, Requisition Inquiry, and 

Requisition Follow-up do not apply. Requisition Cancelation (DLMS 869C/DIC AC_) does 

apply. There are no changes to the requisition cancellation process or format.
Attachment, ADC 1062

Page 10

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The Army has identified 

a goal of achieving operational status approximately April 2014. The Marine Corps has not 

identified an implementation schedule. Initial implementation between GCSS-Army and GCSSMarine Corps is planned for Fort Bragg, North Carolina. 

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Unknown. 

12. IMPACT:

a. New DLMS Data Elements: No new data elements. 

b. Changes to DLMS Data Elements: The MILSTRIP Administrator recommends unique 

coding in the requisition passing order to specifically identify when this business process applies. 

This code is not perpetuated by GCSS-Army to subsequent transactions. Revise the DLMS 

511R Requisition and DLMS dictionary to reflect the passing order for non-ICP/IMM-directed 

inter-Service lateral redistribution use restriction.

Item 

#

Location DLMS 511R

Requisition Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1062 to DLMS Introductory Note 5:

- ADC 1062, Non-Inventory Control Point/Integrated Materiel 

Manager (ICP/IMM)-Directed Inter-Service Lateral Support via 

Retail Level Passing Order

Identifies DLMS

changes included in

the DLMS 

implementation 

conventions.

2. 1/BR06/20 Add new DLMS note 2. to existing Qualifier RI: 

RI Restricted

DLMS Note:

1. Use with requisition or referral order to designate for ownerdirected disposition of Service-owned stock, centrallymanaged/stored by DLA. Restricted use applicable only when a 

Service has entered into a memorandum of agreement (MOA) 

with DLA. Use with applicable Advice Code to indicate desired

action. Must include distribution depot storing material, 

ownership code, and supply condition code.

2. Use with requisition passing order (BR02 Code BM) to 

designate non-ICP/IMM directed inter-Service lateral 

redistribution is requested. Restricted use applicable only when 

a supporting Service has entered into an agreement with the 

requiring Service. Requisitioning activities must be preapproved 

for high priority mission readiness requirements using Advice 

Code 2C or 2J (fill or kill). Refer to ADC 1062. 

Distinguishes passing 

order requisitions 

applicable to this 

process. Use of this 

code does not interfere 

with traditional 

passing order data 

content. No 

equivalent code will be 

carried in the legacy 

MILSTRIP format due 

to a legacy system 

freeze. Initial 

implementation will 

employ DLMS 

compliant interfaces.

c. Automated Information Systems (AIS):
Attachment, ADC 1062

Page 11

 (1) GCSS-Marine Corps: Requires update to support dual paths for requisitioning to 

the national-level SoS and for inter-Service lateral support. Requires system modification to 

include a new code to distinguish requisition passing orders applicable to this business process.

Additional enhancements may be needed based upon staffing results.

 (2) GCSS-Army: Requires modification to the planned transaction exchange to 

incorporate format enhancements and shipment status. Additional enhancements may be needed 

based upon staffing results.

 (3) Other Services/Agencies: This guidance is applicable to all participating Services 

and Agencies and may be adopted over time.

d. DLA Transaction Services: 

 (1) No impact to Defense Automatic Addressing System (DAAS) processing based upon 

use of the requisition passing order (DIC A3_) vice requisition (DIC A0_) format.

 (2) Future impact to Web Visual Logistics Information Processing system (WebVLIPS). 

Under the described procedures there will be three DLMS 511R transactions associated with this 

requirement: the initiating passing order, the requisition image, and the post-post requisition. 

WebVLIPS does not currently display the DLMS transaction identification, but this information 

should be made available during a future upgrade for proper interpretation of the transactions.

 (3) Evaluate impact on current MRA report processing subsequent to implementation of 

the shipment status to ensure inter-Service lateral redistribution requirements are not identified as 

requiring an MRA at this time. There is a potential future impact for LMARS and MRA report 

procedures dependent upon policy decision. 

e. Integrated Data Environment (IDE)/Global Transportation Network (GTN) 

Convergence (IGC). This is a new business process with potential impact to IGC. 

f. Non-DLA Logistics Management Standards Publications: Requires update to DOD 

4140.1-R, DOD Supply Chain Material Management Regulation. Recommended update for the

draft reissuance as DOD Manual 4140.01, Volume 5, are shown in bold red italics:

“9. LATERAL REDISTRIBUTION OF ASSETS

a. The DoD Components may fill requests for materiel or requisitions through lateral 

redistribution of assets. Redistribution methodologies and procedures apply to all materiel 

assets, including fuel and medical, regardless of funding source. With the exception of 

ammunition, principal items and equipment are excluded. Redistribution (cross-leveling) 

procedures for ammunition are in Volume 11 of this manual.

 b. Redistribution within a Military Department may occur before wholesale level 

requisitioning, except for OCONUS activities when the theater FDP must be checked for 

item availability prior to redistribution from within a Military Department from another 

theater. Reimbursement for such intra-Service lateral redistribution is at Military Department 
Attachment, ADC 1062

Page 12

option; however, the associated materiel manager will manage and control inter-Service 

lateral redistribution, except as noted.

c. Inter-Service redistribution will not occur before wholesale-level requisitioning, except 

within theater at CCDR direction or as authorized by inter-Service agreement for lateral 

support of high priority mission readiness requirements where stock is available within the 

area of responsibility. When wholesale assets are not available to satisfy the requisition, the 

materiel manager will seek to satisfy the requisition through alternative means, including the 

DoD lateral redistribution process.

d. DoD Components will balance mission requirements with cost effectiveness when 

filling requests through lateral redistribution. Wholesale level activities will direct retail 

redistribution versus wholesale issue when the total cost of such action is lower or when the 

wholesale level does not have stock available to meet a requisition’s required response time 

and the retail level does and can meet the required response time. If no retail activity can 

meet the required response time, redistribution may still be used if a retail activity can deliver 

sooner than the wholesale level.”
Enclosure, ADC 1062

Page 1

Enclosure, Proposed DLMS Change (PDC) 1062 Staffing Response and Comment 

Resolution 

Staffing Note Resolution

Note 1: Shipment Status is currently a Wave 2 

requirement. It is recommended that this requirement 

be an incremental enhancement in Wave 1. It will 

come at a cost that is not currently in scope.

CASCOM Response: GCSS-Army has built to the 

specifications and has added the AS_/ASN 

functionality suggested in the note.

Marine Corps Response: Moving shipment status 

change from wave 2 to wave 1 is not recommended.

GCSS-MC changes require submission, 

prioritization, and funding.

MILSTRIP Administrator Response: The 

shipment status will use the normal format and 

should not cause any problems on the Marine Corps

side.

Note 2: The Status Code CA explanation is mapped 

using the REF Segment at position 300. Request 

confirmation that the GCSS-Army and GCSS-Marine 

Corps systems have programmed to support this 

DLMS enhancement.

CASCOM Response: GCSS-Army has 

programmed to this. CASCOM cannot speak for the 

GCSS-MC Program.

Marine Corps Response: GCSS-MC currently does 

not currently support mapping of CA status 

explanations to the reference segment at position 300. 

This function is desirable to support PDC 1062, and 

the current process. We do intend to get the 

explanation for CA Status visible within GCSS-MC 

however this is not yet in the change request queue 

for action.

Note 3: Should a demand report (DLMS 867D/DIC 

DHA) to the other Service/Agency wholesale 

materiel manager be required under this process? 

Feedback on this issue is requested for inclusion in 

the approved change documentation.

CASCOM Response: It is the service’s 

responsibility to update the Service/Agency 

wholesale materiel manager with demands. 

MILSTRIP Administrator Response:

If the GCSS-A were to send a demand transaction to 

the wholesale SoS, I am concerned that it might 

overstate demand since the Army would have to rerequisition the materiel from the SoS if providing 

non-excess stock to the Marine Corps.

DLA Response: I tend to agree with the MILSTRIP 

Administrator assessment that we'd be prone to 

double counting since we will almost certainly need 
Enclosure, ADC 1062

Page 2

Staffing Note Resolution

to replenish the Army stock anyway. The only thing 

that information would really do is let us know that a 

demand for that item came to the Marines, which I 

don't think is of terribly much value to us, especially 

if it only results in overstatement of demand levels. 

The only possible positive outcome may be the 

decision to forward stock inventory closer to the 

Marine point of consumption IF that customer were 

the primary user for the NIIN (unlikely if the Army 

had it in stock as well).

Marine Corps Response: Demand history reports 

from the GCSS-Army to Marine Corps material

manager are not required because GCSS-MC can 

track the demand history. 

Note 4: Should the MRA procedures be modified to 

remove the exclusion for this process? Feedback on 

this issue is requested for inclusion in the approved 

change documentation. 

CASCOM Response: No. Although the "fill" 

action that results from material availability will 

result in an AS_/ASN being sent to national, the 

other service will pick up material (no shipments). 

MRA will not be required.

DLA Response: Sounds like MRAs should not be 

excluded from these kinds of requisitions going 

forward. 

Marine Corps Response: Material Receipt 

Acknowledgement (MRA) procedures should be 

modified so MRAs processed in GCSS-MC will be 

reported to the service providing lateral

Support.

MILSTRIP Administrator Response: Under 

current MILSTRAP procedures, requirements for 

submission of an MRA (DLMS 527R/DIC DRA) 

exclude lateral redistribution that is not ICP directed, 

so there is no current MRA requirement. 

Services/Agencies may submit a separate proposal 

with justification and procedures for expanding 

the current MRA requirement. If determined to be 

required in the future, GCSS-Army will be capable of 

receiving a MRA from the other Services.
Enclosure, ADC 1062

Page 3

Staffing Note Resolution

Note 5: Should the proposed lateral supply support 

process be recognized in DOD metrics accumulation 

under Logistics Metric Analysis Reporting System 

(LMARS)? Feedback on this issue is requested for 

inclusion in the approved change documentation.

CASCOM Response: Yes, to determine the mission 

effectiveness and impact of the capability in the other 

services operational readiness efforts.

DLA Response: These should not be tracked in 

LMARS because they are so radically different from 

wholesale actions, which is what LMARS was 

designed to measure. Unless LMARS is expanded in 

scope, these should stay out in my opinion.

Marine Corps Response: The proposed lateral 

supply support process should be recognized in DoD 

metrics accumulation under LMARS.

MILSTRIP Administrator Response: Currently, 

lateral support requirements are captured by the 

requiring Service in their internally calculated 

customer wait time metric. Support under these 

procedures will be measures/reported under customer 

wait time. Integration of this process under LMARS

will not be pursued at this time because the focus of 

LMARS is wholesale level support. Services/

Agencies may submit a separate proposal with 

justification and procedures for expanding the 

current LMARS requirements. 

Note 6: Coordination of procedures between the 

Army and the requiring Service must address 

procedures for handling discrepancies. Reportable 

discrepancies must ultimately be submitted by the 

GCSS-Army to their SoS (when applicable to 

concealed discrepancies). Feedback on this issue is 

requested for inclusion in the approved change 

documentation. Upon clarification of procedures, 

DLMS Volume 2, Chapter 17, Supply Discrepancy 

Reporting, will be updated to reference this process. 

CASCOM Response: The current online Supply

Deficiency Report (SDR) capability is still in effect 

and the viable solution. GCSS-Army does not have 

that capability until Wave 2 projected in 2015.

Marine Corps Response: When lateral support is 

provided by a co-located unit, the procedures for 

handling discrepancies should be determined by the 

supporting unit. Normally, the supported unit would 

hand carry the discrepant part back to the

supporting unit and request corrective action or 

cancellation/reversal if correct part is not available.

Army SDR Committee Representative: The Army 

SDR community strongly requests leaving the 

specific verbiage pertaining to directing SDR's to the 

SSA out of the regulation. We believe that this 

would leave the door open for all customers to 

potentially submit SDR's to the SSA level regardless
Enclosure, ADC 1062

Page 4

Staffing Note Resolution

of how the requisition was fulfilled causing more 

routing problems. Leaving the verbiage out will 

retain current Army routing rules as well as not 

contradict the Army guidance posted on Web SDR. 

Furthermore, there is no systemic process to route the 

SDR to the retail level and any such system function 

is several years away. The Army will continue to 

assist in directing misdirected SDR's to the 

appropriate Army NICP when SDR's are submitted to 

the retail level.

SDR System Administrator Response: 

Discrepancy reporting responsibilities must be 

defined and cannot be left to the determination of the 

supporting unit. Swapping out the discrepant part 

may be acceptable if the correct item is available, but 

an audit trail and accurate inventory records must be 

maintained. MROs cannot be reversed; (Issue (D7) 

reversal is a possible alternative.) SDRs provide 

better history for metrics and accountability. SDR 

procedures do provide a discrepancy code that is used 

when an “exchange” is available (currently restricted 

to DLA IA Support under BRAC). Discrepancy Code 

Z5 will be updated to make it available for use if the 

Army authorizes immediate resolution. 

Pending an alternative solution to be provided by the 

Army, SDRs that cannot be routed to Army activities

such as those addressed to an Army SSA, will be 

systemically routed by DOD WebSDR via email to 

the Army SDR lead for forwarding to the 

AMI/NAMI ICP as applicable. 

Note 7: Under the described procedures there will be 

three DLMS 511R transactions associated with this 

requirement: the initiating passing order, the 

requisition image, and the post-post requisition. 

WebVLIPS does not currently display the DLMS 

transaction identification but this information should 

be made available for proper interpretation of the 

transactions during a future upgrade.

CASCOM Response: Currently the three separate 

images are output in GCSS-Army as three separate 

outbound processes with three separate RICEFWS 

that distinguish each one from the others. 

Marine Corps Response: GCSS-MC currently 

supports DLMS 5llR transactions; initiating passing 

order, requisition image, post-post requisition. We 

will submit a request for the code upgrade upon 

receipt of the ADC. 

MILSTRIP Administrator Response: Impact on 

WebVLIPS documented in the ADC.
Enclosure, ADC 1062

Page 5

Component Response/Concurrence

# Submitter Response Resolution

1. Army Concur. Noted.

Language has been further modified to 

state Army guidance, but it retains the 

documentation of Army responsibility 

for forwarding these SDRs to the 

desired Army action activity. The 

Service receiving lateral support from 

an SSA cannot be expected to 

understand Army requirements to direct 

the SDR to the NAMI or AMI ICP, 

particularly since the other Service has 

no visibility of that activity and the 

concept differs significantly from 

routine SDR procedures.

2. Navy Concur. Noted.

3. Marine Corps Concur. Noted.

4. Air Force AF concurs with PDC 1062 and agrees with 

the intent as stated in this PDC to support 

high priority mission readiness 

requirements. 

1. The PDC only mentions RDD = N(xx) 

but we use a RDD of '999' for OCONUS.

2. If this PDC remains an option (between 

Army and Marines) then no impact to ILSS. If the AF implements, then changes 

would need to be made (especially to 

eliminate manual preparation of 

transactions), but would need to discuss 

with all Services.

3. Do you know if the Financial Committee 

has reviewed this PDC for billing? Do they 

have any issues with the Army billing for a 

DLA managed item?

 

4. We can incorporate this into our DLMS 

Noted.

MILSTRIP Administrator Response: 

1. ADC has been updated to recognize 

use of Special Requirements Code 999

for expedited handling of high priority 

requirements.

2. Noted.

3. The Finance PRC chair has reviewed 

and has identified no problems with this 

procedure.

4. Noted.

5. Noted. Additional coordination may 

be required for better integration of Air 

Force as a participating Service in this 

process. The CAS modernization 
Enclosure, ADC 1062

Page 6

Component Response/Concurrence

# Submitter Response Resolution

transaction capabilities by adding the A3* 

(511M) to our DLMS template within ILSS. We could initially use manual processes 

to fill the gaps and eventually automate this 

process by modifying our application as 

needed.

5. AF in coordination with the Global 

Ammunition Control Point (GACP,

AFLCMC/EBH, Munitions Division) and 

the Combat Ammunition System (CAS) 

Program Management Office (PMO) offers 

the following comments:

a. There are no negative impacts to the 

Combat Ammunition System.

b. The Air Force has the ability to accept all 

A3 transactions from other Service’s 

systems. These are, however, all routed to 

the wholesale Item Manager and must then 

be forwarded to the retail level. The AF 

would expect all lateral support requests to

have been coordinated prior to receiving 

any A3 transactions.

- CAS does not have the capability to send 

out A3 transactions directly to

other Services is situations outlined within 

this PDC and we will continue

to work any inter-services lateral support 

requirements off line.

- The AF has initiated a CAS modernization 

effort which has identified requirements to 

create interfaces with other Service systems 

to enable greater online transaction receipt 

and processing. ECD for developing these 

interfaces in not yet known, but anticipated 

to be 2017 - 2018.

should accommodate DLMS 

transactions and could incorporate these 

procedures as an approved business 

process.

5. DLA Concur. Noted.

6. USTRANSCOM USTRANSCOM is changing to "approved 

with comment" on this PDC Ellen. This

PDC allows for the by-passing of DTS 

(which is IGC's source of requisition

MILSTRIP Administrator Response: 

The current process does bypass DLA 

Transaction Services; however, under 

the proposed process, the Marine Corp 
Enclosure, ADC 1062

Page 7

Component Response/Concurrence

# Submitter Response Resolution

transactions) by allowing requisitions to be 

submitted directly to the GCSS Army 

portal. Will this change cause a gap in 

visibility for USTRANSCOM for

requisitions? If yes, (in other words 

requisitions IGC currently receives

will no longer be visible to 

USTRANSCOM), then USTC-J3 may have 

concerns, particularly because this change 

applies to high priority requisitions, i.e.

ones that might need more, not less, 

visibility to AV customers and also to

TRANSCOM.

will send their referral order through 

DLA TS most of the time (GCSS-A is 

still allowing for walk-thru 

requisitioning, but the intent is for 

DLMS transactions via DAAS to be 

processed on both ends, thus providing 

visibility at an enterprise level - only the 

FLIS SoS will be bypassed in this 

process). 

7. FAA FAA has had some issues with the USAF 

using lateral support in the past so wanted to 

share the issues below.

The main issue is with repairable items 

where one site is ordering a replacement and 

a second base turning in a failed asset. No 

way to match up the order with the failed 

turn is causing due in's to not be cleared and 

credit to not be issued until the two 

transactions can be matched up. So order 

for a replacement sent to the PICA and the 

turn in from the second base needs to be 

linked if possible. Common document 

numbers would be great or a reference to 

the ordering document.

Noted. 

MILSTRIP Administrator Response: 

Under MILSTRIP business rules a 

requisition document number cannot be 

reused, therefore procedures for 

reparable exchange must be handled 

using other criteria than the document 

number. The ADC has been updated to 

alert users to the risk of using the lateral 

referral order where pre-established 

procedures are in place for exchange 

pricing based upon turn-in of the failed 

item.
Enclosure, ADC 1062

Page 8

Component Response/Concurrence

# Submitter Response Resolution

We also manage some items under a 

common NSN but with site unique 

software. So when the FAA receives an 

order from a base we load that bases site 

unique software prior to shipment. So a 

spare at one base may not function correctly 

at a different base. So probably need a 

means to identify these exceptions. 

Probably 90% of parts are common and no 

issue using lateral support but you will have 

exceptions.

CASCOM Response: As for the Fill or 

Kill relationship, GCSS-Army is only 

filling the NSN that is available and 

requested by the customer and will not 

substitute automatically.

MILSTRIP Administrator Response: 

FAA is saying that the NSN will be the 

same even though Service-specific 

software has been incorporated in the 

item. The Army should not provide 

support to the Marine Corps using an 

Army item if the item is FAA managed 

and includes FAA-updated software.

(follow-up sent for Army response)

8. DLA Transaction 

Services

1. In paragraph 4.c.(7) it says: "An 

accepted requisition from the other Services 

will cause GCSS-Army to create a sales 

order in its system and send a Requisition 

Image (DLMS 511R/DIC A0A with Action

Code=FI (at 2/BR06)).... to Army 

wholesale...." And then in paragraph 

4.c.(10) it says: "The sales order in GCSSArmy will normally have the goods issue 

completed the same day. This will cause 

....a goods issue post-post issue DLMS 

511R/DIC A0A with Action Code J (at 

2/BR06) to be sent to Army wholesale. The 

post-post transaction will contain Army Edit 

Action Code IV...." 

The question is for the Army to confirm this 

information (again, since I believe I have 

asked this question previously, but I may 

not have asked the question properly to 

receive the correct response). ARE THE 

TRANSACTIONS REFERRED TO IN 

PARAGRAPH (7) AND IN PARAGRAPH 

(10) ACTUALLY TWO SEPARATE 

TRANSMISSIONS OF THE DLMS 511R 

(same document number but transmitted at 

different steps in the process)?

CASCOM Response: GCSS-Army is 

responding to national with two 

separate DLMS 511R/DIC A0As:

(1) as a result of successful receipt of 

the Other Service request, and 

(2) as a result of an issue to another 

Service.

2. The PDC says: "(4) Requisitions from 

other Services will be required to contain a 

CASCOM Response: This PDC was 

NOT intended for DLA Transaction 
Enclosure, ADC 1062

Page 9

Component Response/Concurrence

# Submitter Response Resolution

valid fund code." Currently, the Fund Code 

is not edited at DLA Transaction Services 

(except for Signal Code C or L). If an 

invalid fund code where provided 

inadvertently, the submitter's default 

account would be billed under MILSBILLS 

procedures. Was there an expectation for 

this PDC process that DLA Transaction 

Services will implement an edit of the A3_ 

transactions against the Fund Code table 

prior to passing them to GCSS-A? 

Services to implement an edit of the 

A3_ transactions against the Fund Code 

table prior to passing the order to 

GCSS-Army. The use of the 

appropriate fund code is totally up to the 

Other Service and will be part of the 

Memorandum of Agreement (MOA) 

with the Other Service.

MILSTRIP Administrator Response: 

The ADC has been updated accordingly.