IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGIN IA 22060-6221 

August 17, 2012 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

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

Revised Procedures for Inclusion of Contract Data in Transactions Associated with 

Government Furnished Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) Requisitions (Supply and 

Contract Administration) (Staffed as PDC 473) 

The attached change to DLM 4000.25, Defense Logistics Management System (DLMS) and 

DLM 4000.25-1, Military Standard Requisition and Issue Procedures (MILSTRIP) is approved for 

phased/staggered implementation. Supply PRC members are required to actively monitor for 

implementation of this ADC and provide implementation dates when they become available. The 

updated DLMS Supplements will be posted to the DLA Logistics Management Standards Web at 

www.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp within 10 days from the above date. 

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

767-0676 or DSN 427-0676, email: Ellen.Hilert@dla.mil, or Ms. Heidi Daverede, DOD 

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

must contact their Component designated representative. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

ODASD DPAP (PDI) 

DONALD C. PIPP 

Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program G Printed on Recycled Paper 
Attachment, ADC 1014 

Page 1

ADC 1014

Revised Procedures for Inclusion of Contract Data in Transactions 

Associated with GFP and MCA Validation of CFM Requisitions

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Requestor: Office of the Deputy Assistant Secretary of Defense (ODASD) Supply 

Chain Integration (SCI) and ODASD Defense Procurement and Acquisition Policy (DPAP)

Program Development and Implementation (PDI)

b. Sponsored by: DLA Logistics Management Standards Office, Ms. Ellen Hilert, Supply 

PRC Co-Chair, 703-767-0676; DSN 427-0676; or, e-mail: Ellen.Hilert@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/Contract Administration

b. Primary/Secondary Functional Process: GFP Accountability

3. REFERENCES: Significant changes subsequent to staffing of the proposed change are 

highlighted in green.

a. Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics 

(OUSD(AT&L)) Memo of January 11, 2010, Subject: Government Furnished Property (GFP). 

Describes the requirements for strengthening the accountability and management of personal 

property owned by DOD when the property is used on contracts. 

b. DODI 8320.04, Item Unique Identification (IUID) Standards for Tangible Personal 

Property, dated June 16, 2008. Established the DOD IUID Registry as the master data source for 

GFP and requires DOD Components to identify and track GFP using Unique Item Identifiers 

(UII) in transaction-derived data from electronic business transactions.

c. DODI 4161.02, Accountability and Management of Government Contract Property, 

dated April 27, 2012. Assigns responsibilities and provides procedures for Government contract 

property in the custody of defense contractors. This document was identified as a draft during 

initial staffing. Since then, the DODI has been published.

d. DOD 4140.1-R, DOD Supply Chain Materiel Management Regulation, to be replaced 

by DOD 4140.01, DOD Supply Chain Materiel Management Procedures (Draft).

e. DLM 4000.25-1, MILSTRIP; DLM 4000.25-2, MILSTRAP; and equivalent procedures 

under DLM 4000.25 Volume 2, DLMS Manual. Manuals are available at: 

http://www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp

f. Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7007. Updated 

clause defines expanded reporting requirements for Government-furnished property to include 

items uniquely and non-uniquely identified, and clarifies policy for contractor access to 
Attachment, ADC 1014 

Page 2

Government supply sources. 

g. DFARS Procedures, Guidance and Information PGI 245.1 – General, revised November 

18, 2011. Provides amplifying information to define government property, furnishing 

government property to contractors and transferring government property accountability. 

h. Approved Defense Logistics Management System (DLMS) Change (ADC) 344, Revised 

DLMS Shipment Status (856S) in Support of Navy Enterprise Resource Program (ERP) and 

Commercial Asset Visibility II (CAV II) Systems and Carrier Name Field Length in Materiel

Release Advice (945A). 

i. ADC 353A, Revised Procedures for Pre-positioned Materiel Receipt (PMR) and 

Shipment Status for Retrograde and Directed Discrepant/Deficient Materiel Returns Including 

Corrected Time Standard for Security Assistance/Foreign Military Sales (SA/FMS).

j. ADC 390, dated January 28, 2011, Revised DLMS Supplement (DS) 527R Materiel 

Receipt Acknowledgement (MRA) and Receipt Functions to Require the DOD Contract Number 

for Transactions Associated with GFM and CFM. Business rules and scope of ADC 390 

include:

• Requirement for inclusion of contract number (and call/order number, when 

applicable) on DLMS 527R transaction associated with GFM and CFM,

• Applicability to the MRA (comparable to MILSTRAP Document Identifier Code 

(DIC) DRA) and to the accountable receipt (comparable to MILSTRAP DIC 

D6_), when appropriate for intra-Service use (e.g., Navy CAV),

• Applicability to both pushed and pulled GFM,

• Applicability to the Management Control Activity (MCA) preparing the MRA on 

behalf of contractors, and

• Requirement that contracting officers ensure the ADC 390 requirements are 

implemented in contracts authorizing GFM/CFM. 

k. ADC 417, Shipment Status of Local Delivery Manifested, Outbound MILS Shipments 

on Behalf of On-Base Customers, Re-Warehousing Actions between Distribution Depots, and 

non-MILS Shipments to Off-Base Customers, with Passive Radio Frequency Identification 

(RFID). 

4. OVERVIEW/BACKGROUND:

a. Overview. This change updates DLMS procedures and multiple DLMS transactions to 

enhance the visibility of GFP through associated logistics transactions. It perpetuates the 

DFARS contract number through the requisitioning and MCA validation processing and 

establishes a mandatory requirement for inclusion of the applicable GFP contract number in 
Attachment, ADC 1014 

Page 3

relevant requisitions, redistribution/materiel release orders, and shipment status, thereby 

providing capability to monitor GFP through enterprise visibility/accountability programs. 

b. Terminology. The following terminology applies to the processes discussed in the 

proposal:

(1) Government-Furnished Materiel (GFM). Materiel owned by the Government and 

furnished to a contractor to use for specific contract purposes. Title to all materiel furnished by 

the Government remains with the Government. GFM is property that may be incorporated into 

or attached to a deliverable end item or that may be consumed or expended in performing a 

contract. GFM does not include materiel sold by the Government to a contractor, equipment, 

special tooling, special test equipment, or real property. (DODI 4161.02, Reference 3.c. GFM is 

a form of Government-Furnished Property (GFP). Under MILSTRIP, all requisitions that 

identify the Government as the bill-to (or where the requisition indicates that the materiel is 

provided with no billing/free issue) will be processed under GFM requisitioning procedures.

(2) Contractor-Furnished Materiel (CFM). Materiel that the contractor is 

contractually required to provide. The source of supply for CFM may be the commercial market 

or the federal supply system when authorized by contract. Under MILSTRIP, CFM is identified 

by identification of a contractor activity as the bill-to DoDAAC and the requirement for MCA 

validation varies by authorizing Service.

(3) Contractor-Acquired Property (CAP). Any property acquired, fabricated, or 

otherwise provided by the contractor for performing a contract, and to which the Government 

has title. CAP that is subsequently delivered and accepted by the Government for use on the 

same or another contract is considered GFP. (DODI 5000.64) Under MILSTRIP, all 

requisitions that identify the contractor as the bill-to will be processed under CFM requisitioning 

procedures. 

(4) Government-Furnished Property (GFP). Property in the possession of, or directly 

acquired by, the Government and subsequently furnished to the contractor for performance of a 

contract. Government furnished property includes, but is not limited to, spares and property 

furnished for repairs, maintenance, overhaul, or modification. Government furnished property 

also includes CAP if the CAP is a deliverable under a cost contract when accepted by the 

Government for continued use under the contract.

(5) Manufacturing Directive Number (MDN). Identifies the contract or MCA in 

GFM-related transactions and documents. MILSTRIP currently authorizes the use of the MDN, 

instead of the authorizing GFM contract number, for requisitioning and subsequent MCA 

validation. The MDN is constructed using the MILSTRIP Distribution Code to facilitate 

transaction routing by DLA Transaction Services. For clarification: DLA Directive 5452.242-

9002, “Manufacturing Directive Number (MDN) for Use In Identifying Government-furnished 

Property (GFP) Transactions,” requires an MDN be assigned to any contract resulting from the 

solicitation/contract for use in identifying GFP transactions. This number is entered on 

receiving, shipping, and disposition documents prepared under the contract terms to identify each 

receipt of components into the assembler’s plant and each shipment leaving the assembler 
Attachment, ADC 1014 

Page 4

Contractor’s plant, whether assembled rations or components, including shipments to other 

Contractors, shipments to consignees, materiel shipped at the end of the contract, and materiel 

reported destroyed. GFP transaction identification is required on a single copy of the receiving 

document for components entering the Contractor’s plant and the shipping document for items 

leaving the assembly Contractor’s plant. Staffing Note: The MILSTRIP Administrator is aware 

of limited use of the MDN by DLA1 for contractor requisitioning, and requested feedback from 

other Services/Agencies to determine whether this practice is applied outside DLA. No Military 

Services have identified a requirement for use of the MDN. 

c. Reference 3.a. directed the use of electronic transactions to strengthen internal controls 

and oversight practices in the “DOD GFP Business Environment.” Reference 3.a. established 

five specific goals intended to reinforce internal controls over the accountability for DOD

personal property provided to a contractor by a DOD Component, or requisitioned from DOD

Component supply sources as GFP:

(1) Electronic transactions shall be used to transfer government property to a contractor 

and/or return property to DOD. Contractors and the DOD Components shall confirm receipt by 

contract number for property received electronically. 

(2) All transactions used to transfer property to contractor custody or return property to 

DOD custody shall cite a contract number under which the property is or was accountable.

(3) For contractor requisitions of GFP, DOD Components shall capture or link to the 

contract number under which requisition authority to contractors is granted, and shall reject any 

contractor requisitions that are not authorized. 

(4) Consistent with Federal Acquisition Regulation (FAR) 45.201, GFP requirements 

shall be fully described and listed in an attachment in any solicitation and contract to notify the 

contractor of those items of GFP that are due-in from the DOD or that are authorized for 

requisitioning from a DOD Component supply source.

(5) GFP transfer transactions and receipts for non-UII’d property shall be routed to a 

GFP Module in the IUID Registry (formerly GFP Hub)2

. 

d. The impact of the new GFP Module in the IUID Registry was discussed during a

Supply PRC meeting (June 21-22, 2011) and GFP Working Group meetings (February 3, 2011

and July 14, 2011). Successful performance of the GFP module requires modification of the 

DLMS transactions. The DLA Logistics Management Standards Office was directed to draft a 

Proposed DLMS Change (PDC) to support GFP functionality required by DPAP (PDI) to 

identify the applicable contract number in DLMS transactions supporting GFP shipments. The 

 1 MDNs are currently being used by DLA by exception. For example, MDN F00 applies to the Energy Supply 

Chain as an interim procedure to obtain fuel additives managed by DLA Aviation until DLA Energy transitions into 

ECC/EBS. The fuels part of Energy Convergence will be part of the R2 (DLA-EBS) currently scheduled for 

October 2013. MDN H00 is employed to support the DLA Navy Base Realignment and Closure (BRAC) contract 

support. No other MDNs are known to be in use for requisitioning purposes by DLA or other Service/Agencies. 2 The GFP Module deployed in WAWF V5.0 on July 25, 2011.
Attachment, ADC 1014 

Page 5

required data elements to identify contract data are generally present as placeholders in most of 

the relevant DLMS transactions; however, GFP procedures need to be specifically identified in 

the respective areas of the DLMS Manual. 

e. Scenarios for which the transactions are used: Materiel may be requisitioned by a 

contractor as GFP under a contract that authorized the contractor to receive materiel from 

Government sources. Materiel may be directed for shipment to the contractor from DOD or 

GSA stock or for direct vendor delivery (DVD). GFP materiel may be ‘pushed’ to the contractor 

based on a contract schedule or issued in response to a requisition submitted by the contractor or 

Government representative, such as the MCA. DOD-owned reparable items may be inducted 

into commercial maintenance from DOD stock requiring preparation of Materiel Release Order 

and/or Shipment Status. As defined above, these reparable items are considered GFP. 

Additionally, contractors may requisition materiel under contracts authorizing CFM or CAP, 

where the contractor DoDAAC is identified as the bill-to activity.

f. Procedures, transactions, data elements, processing details in use today:

(1) MILSTRIP procedures (Reference 3.e) prescribe preparation and submission of GFM 

requisitions. Requisitions identifying a contractor as the ship-to location and either free issue or 

a Government activity as the bill-to party, are processed under GFM controls via the MCA. 

Under MILSTRIP procedures, all Army CFM requisitions are processed under MILSTRIP GFM 

controls via the MCA. Additional controls are enforced for contractor GFM/CFM ordering 

within DOD EMALL. Procedures require that GFM requisitions for or by contractors must 

identify appropriate contract data. All GFM requisitions must include GFM-related information 

as follows:

• MCA monitoring the contract.

• DoDAAC of the contractor requesting and/or receiving the materiel.

• Indication when issue is without reimbursement.

• Identification of the MDN or contract number.

3

• Identification of the call or order number, when required by the Component 

contract.

(2) With the exception of ADC 390 procedures described above (Reference 3.j.), the

existing DLMS manual procedures do not specify a requirement for the contract number beyond 

the initial requisition submission and the GFM validation (DLMS 517G/DIC AX_) transactions. 

(3) DLMS transactions currently perpetuate the legacy MILSTRIP 80-record position 

transaction GFP data requirements specific enhancements for inclusion of GFP contract data 

authorized by ADC 390 and ADC 344.

(4) The Army legacy process includes identification of the Contract Line/Subline Item 

number (CLIN/SLIN) for requisitioned GFM (rather than the contract number).

 3 The MILSTRIP 80-record position legacy format only supports inclusion of the last eight positions of the 

Procurement Instrument Identification Number (PIIN).
Attachment, ADC 1014 

Page 6

(5) The Navy uses a DLMS 867I (DIC D7M) transaction for retrograde of Not Ready for

Issue (NRFI) repairable items directly to a commercial repair vendor. Although the contract 

number is known at the time of the retrograde movement, it is not required in the legacy 

MILSTRAP transaction. 

g. Intent of this Change: Changes are required to DLMS transactions to enhance the 

visibility of GFP within logistics transactions. The changes will incorporate the authorizing

contract data in DLMS 511R, 511M, 517G, 856R, 856S, 867I, 869C, 869F, and 940R

transactions. DLMS transactions require modification to existing notes and data content updates, 

with some requiring more extensive revision where GFP was not previously identified. In 

addition to establishing mandatory inclusion of the applicable GFP contract number, this change 

supports inclusion of the call or order number and contract line/subline item number 

(CLIN/SLIN) when applicable and directed by the authorizing Service/Agency. The MDN may 

be retained as discretionary information. The requisition and MCA validation process data 

enhancements apply to Army-authorized CFM as well as GFM. The GFP contract number is 

perpetuated from the requisition and MCA validation to the materiel release order and shipment 

status, thereby providing enterprise-wide visibility. 

h. Description of Changes:

(1) DLMS changes to enhance visibility of GFP in selected logistics transactions are 

shown below. These procedures are extended to CFM only by direction of the authorizing 

Service/Agency (pending planned policy change under Reference 3.d.). 

• Require the DLMS-compliant applications to carry the full Defense Federal 

Acquisition Regulation Supplement (DFARS) contract number (13 positions) 

for requisitions associated with GFP. The applicable call/order number and 

CLIN, shall be included when applicable and when directed by the authorizing 

Service/Agency. This requirement is also applicable to Army-authorized 

CFM requisitions, and may be employed as directed by other authoring 

Services/Agencies. This would be in addition to (or instead of) the MDN 

currently used by DLA. The MDN is retained as an optional data element.

• Require the MCA to perpetuate the full DFARS contract number and 

call/order/CLIN, where applicable, to the source of supply (via DLMS 511R) 

and to the GFM Validation (DLMS 517G (DIC AX2). This requirement is 

applicable to DLA Transaction Services when acting as the MCA under 

MILSTRIP exception processing.

• For shipments from stock, require the source of supply to perpetuate the GFP

contract data to the Materiel Release Order (MRO) (DLMS 940R) transmitted

to the shipping activity.

• Require the shipping activity or source of supply, as applicable, to perpetuate 

the GFP contract number data to the shipment status (DLMS 856S) and to 
Attachment, ADC 1014 

Page 7

shipping documentation.

• Require contractors using DLMS transactions to for shipping GFP into DoD 

inventory to identify the GFP contract data on the shipment status transaction 

(DLMS 856S or 856R) and to shipping documentation.

(2) Specific requirements were identified during the July 14, 2011 GFP Meeting

• Establish procedures to include the GFP contract data on the DLMS 940R, 

Materiel Release Order, used to direct shipment of reparables for induction to 

commercial maintenance, and perpetuation of the contract data to the 

shipment status. The mapping of data elements will be the same as prescribed 

for requisitioned GFP, but the implementing procedures differ. 

• Establish procedures to require the contract number on the DLMS 856S, 

Shipment Status, when used for DD 1149 requirements and shipping to a 

contractor as GFP. This will require the originator of the shipment to make 

the GFP contract number available to the shipper. 

(3) Additional requirements were identified subsequent to staffing.

• For shipments from stock, require the shipping activity to identify the GFP 

contract number on the Issue transaction (DLMS 867I/DIC D7M) transmitted 

to the materiel owner.

• Require the inclusion of GFP contract data on DLMS transactions prepared by 

contractors shipping Government property to DOD activities under 

performance-based logistics (PBL) or contractor supported weapon system

(CSWS) contracts.

5. PROPOSED CHANGE

a. Requested change in detail:

(1) DLMS procedures and transaction exchanges shall be revised to ensure that the GFP 

contract data is provided and perpetuated, as applicable, to ensure that this information is 

available and included in the shipment status transaction.

(2) Services/Agencies authorizing contractors to receive GFP shall provide guidance for 

including applicable GFP contract data in requisitions prepared by the contractor or by a 

Government representative.

(3) Distribution Depots shipping GFP shall perpetuate the GFP contract data from the 

associated materiel release order to the shipment status transaction.
Attachment, ADC 1014 

Page 8

(4) Shipments of GFP shall include the GFP contract number (and call order number 

when provided) on the Issue Release/Receipt Document (IRRD) DD 1348-1A or DD Form 

1348-2. This includes shipments from DOD to contractors and shipment of GFP to DOD

activities from contractors. The contract number shall be prefaced by the word “GFP.”

(5) Services providing GFP to a collocated Distribution Depot for transshipment shall 

provide the GFP contract information on the DD 1149, Requisition and Invoice/Shipping 

Document, where applicable, for inclusion in the DLMS 856S, Shipment Status.

(6) DLA Transaction Services shall update data maps to support this change. With 

coordination by the Navy, this will include remapping of the GFP contract information provided 

by CAV applications for use in the DLMS 856S for Proof of Shipment (POS).

b. Alternatives:

(1) Variations in mapping were considered during the preparation of the proposed 

change. Although introduction of the Furnished Goods and Services (GF) Segment in the 

shipment status is slightly more complex than use of the Reference (REF or N9) Segment, it is 

proposed as the more appropriate mapping for the contract information. 

(2) Remapping of CFM contract information in requisition and validation-related 

transactions to remove it from the GF Segment was also considered. Remapping of CFM 

contract data was not proposed because of the significant disruption it would cause for a widely 

implemented process. Instead, to ensure proper interpretation of the information, a new data 

element is introduced to clarify the type of contract property involved. Consideration was given 

to requiring changes to the legacy MILSTRIP GFM requisition transaction and the MCA 

validation transactions. Although the requisition itself could be formatted to include both the 

MDN and the contract number, the MCA validation transactions cannot accommodate both 

within the existing legacy format. Because of the limited use of the MDN and the inability of the 

legacy formats for requisition validation to handle the added content, this change primarily 

targets DLMS implementation which can support the expanded data requirements. However, the 

MILSTRIP legacy procedures have been updated to require the inclusion of the last eight 

positions of the contract number (with the MDN retained as optional), thereby promoting the 

transition to the contract number during the MCA validation.

(3) Inclusion of GFM contract information in the DLMS 869A, Requisition 

Inquiry/Supply Assistance Request, was considered for consistency across requisition-related 

transactions, but was not proposed due to lack of an identified requirement. 

(4) Inclusion of GFM contract information in the DLMS 945A, Materiel Release Advice, 

was considered for consistency, but was not proposed because the extra data would already be 

available in the source of supply system.

c. Proposal Comment Resolution: Concurrence and comment resolution are provided at 

Enclosure 10. 
Attachment, ADC 1014 

Page 9

6. REASON FOR CHANGE:

a. In Reference 3.a., OUSD(AT&L) identified specific goals to reinforce internal controls 

over the accountability for DOD personal property requisitioned from Government sources by a 

contractor or provided to contractors by DOD Components. The key requirement is to cite a 

contract number under which requisition authority is granted to contractors or the contract 

number under which the contractor has authority to receive materiel pushed to the contractor by

DOD Components. This change will enable the GFP contract number to be perpetuated on 

relevant transactions through the logistics pipeline. While placeholders may have been identified 

in DLMS transaction for GFP contract data, the mapping is not consistent and the requisite 

business rules were not established with limited exceptions applicable to the MRA and CAV. 

This change also revises the DLA concept for use of the MDN to also comply with the DOD 

GFM requirements for inclusion of the contract number.

b. Reference 3.c. requires inclusion of the GFP contract number in DLMS transactions

associated with shipment/issue of materiel to contractors and shipment/return of GFP to 

Government activities.

c. ODASD (SCI) has identified a pending requirement for validation of CFM under 

MILSTRIP MCA procedures. This requirement is currently under coordination in draft DOD 

4140.01-M, DOD Supply Chain Materiel Management Procedures (see excerpt at Enclosure 1). 

A separate change will be issued to further modify the DLMS/MILSTRIP procedures upon 

formal publication of this policy change. 

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Adding the GFP contract data to the affected transactions and defining the 

use and business rules in the appropriate DLMS Manual chapters will enable the DOD 

Components to comply with the expanded GFP tracking requirements identified in the ADC 

reference section. 

b. Disadvantages: DOD Components require system modifications to accommodate and 

perpetuate the contract related data on the identified transactions. 

8. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: Revised policy for validation of CFM will further impact changes to 

MILSTRIP/DLMS processing and will be addressed separately. The concept used for this 

change is that the CFM contract data will only be perpetuated through the requisitioning and 

MCA validation process, but will not be carried forward to the subsequent transactions (e.g., 

shipment status (since there is no identified requirement for tracking/visibility of CFM based 

upon the contract number subsequent to requisition processing/MCA validation at this time). 

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Staggered/phased

implementation. Supply PRC members are required to actively monitor for implementation of 

this ADC and provide implementation dates when they become available. 
Attachment, ADC 1014 

Page 10

• Transition to mandatory inclusion of the full DFARs contract number on DLMS 

requisitions and MCA validation transactions originated in the DLMS format to be 

enforced by DLA Transaction Services edit beginning January 1, 2013.

• Staggered implementation of GFP contract data on the DLMS release order, issue, and 

shipment status beginning January 1, 2013, and to be completed by all DLMS-capable 

Components no later than December 31, 2013. 

Air Force and DLA Distribution: Include contract data for directed release of GFP by 

Distribution Depots when using the point-to-point user-defined file (UDF) interface via 

the Customer Information Control System (CICS) no later than December 31, 2013. 

Navy and DLA Transaction Services: Remap GFP data within the DLMS 856S 

supporting CAV no later than December 31, 2013. An Administrative ADC Addendum 

will be provided to remove the REF segment mapping when transition is complete.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Improved management, oversight, and visibility 

of GFP are expected to generate savings or cost avoidance. However, no specific data is 

available to quantify any expected savings or cost avoidance. 

11. IMPACT:

a. New/Revised DLMS Data Elements: 

(1) New. There are no new data elements identified. Note: If desired for proper 

processing/recognition, Services/Agencies may propose an additional requirement for a unique 

code in DLMS transactions to distinguish GFP from CFM, and/or distinguish among the 

different “flavors” of GFP, such as CAP and GFP shipped/returned by the contractor to DOD 

inventory.

(2) Revised. Use of the abbreviated contract number in requisition and MCA 

validation transactions shall be phased out with full implementation of the DLMS.

b. Service/Agency Implementing Guidance: Update for consistency with DLMS 

guidance. 

c. Service/Agency Automated Information Systems: 

 (1) Applications sending and receiving transactions revised by this change will need to 

ensure that transactions will not fail during a staggered implementation.

 (2) Update is required for use of the DFARS 13-position contract number and associated 

call/order number and CLIN as applicable. 

 (3) Update is required for perpetuation of GFP contract data through the release/issue

and shipment status. This requirement is applicable to shipment status prepared by the shipping 

activity or by the source of supply, including shipment status provided for direct vendor delivery. 
Attachment, ADC 1014 

Page 11

The source of supply will need to distinguish GFP contract data from CFM contract data 

provided in the requisition to accomplish this revision.

 (4) Army Logistics Modernization Program (LMP) internal mapping of contract data to 

properly identify the call order number and CLIN/SLIN from the DLMS format is required to 

discontinue use of a work-around that converts this information to a concatenated format. Army 

contractors will be required to provide the contract number in GFP transactions regardless of the 

fact that the specific contract number can be derived from the Army-assigned contractor 

DoDAAC.

 (5) In addition to Service/Agency standard logistics systems, this change impacts DOD 

EMALL and the Navy-supported CAV program.

d. DLA Transaction Services: Mapping updates are required. Additional changes are 

required for the Defense Automatic Addressing System (DAAS) MCA validation exception 

process.
Attachment, ADC 1014 

Page 12

e. Publications:

(1) Recommended update to DOD 4140.1-R, DOD Supply Chain Materiel Management 

Regulation, to be replaced by DOD 4140.01-M, DOD Supply Chain Materiel Management 

Procedures (Draft) (Enclosure 1).

(2) Update DLM 4000.25, DLMS, Chapter 4, Requisitioning (Enclosure 2).

(3) Update DLM 4000.25-1, MILSTRIP, Chapter 11, Contractor Access to Government 

Sources of Supply (Enclosure 3). 

(4) Update DLM 4000.25-1, MILSTRIP, Appendix 1.1, Forms/Message Formats 

(Introduction) (Enclosure 4).

(5) Update DLM 4000.25-1, MILSTRIP, Appendix 3.2, Requisition (Enclosure 5).

(6) Administrative update DLM 4000.25-1, MILSTRIP, Appendix 3.23, Passing Order 

(Enclosure 6).

(7) Administrative update DLM 4000.25-1, MILSTRIP, Appendix 3.24, Referral 

Order/Lateral Redistribution Order for Retail Assets (Enclosure7).

(8) Update DLM 4000.25-1, MILSTRIP, Appendix 3.48, Materiel Release Document 

DD Form 1348-1A or DD Form 1348-2 (Enclosure 8).

(9) Update the following DLMS Supplements for inclusion of relevant contract data: 

511R, 511M, 517G, 856R, 856S, 867I, 869C, 869F, and 940R (Enclosure 9). Note: 

Components may propose GFP contract data be perpetuated to additional transactions as needed.

(10) Update the DLMS 870S for removal of placeholders data fields for GFP contract 

information (the Service/Agencies did not identify a requirement for the source of supply to 

perpetuate GFP contract data to the supply status) (Enclosure 9).
Enclosure 1, ADC 1014 

Page 1

Enclosure 1, Draft Supply Chain Materiel Management Procedures Proposed Revision

The following is an extract from the DOD 4140.01-M, Volume 10, DOD Supply Chain Materiel 

Management Procedures: Operational Requirements, Enclosure 3, Procedures. This guidance is 

equivalent to that in the currently published guidance with the exception of the expanded 

requirement for CFM validation. The revisions identified in red bold italics will be submitted to 

ODASD(SCI) for consideration during reissuance.

“8. CONTRACTOR ACCESS TO GOVERNMENT SUPPLY SOURCES

a. Required Procedures

(1) Contractors shall supply all materiel required for the performance of U.S. 

Government contracts except when the contracting officer determines that contractor access to 

DoD supply sources for such materiel would:

(a) Be significantly more economical.

(b) Maintain necessary

standardization. 

(c) Expedite production.

(d) Otherwise be in the U.S. Government’s best 

interest. 

(2) In executing this requirement, the DoD Components 

shall:

(a) Determine if the materiel is contractor-furnished materiel (CFM) or

government furnished materiel (GFM).

(b) Include in the contract file the required authorization and in the contract a list 

of the authorized items and quantities.

(c) Provide the contractor with a DoD activity address code (DoDAAC) and advice 

on the use of priority designators to allow the contractor to requisition the authorized materiel in 

accordance with Volume 5 of this Manual.
Enclosure 1, ADC 1014 

Page 2

(d) Provide the contractor with the materiel directly, when appropriate, and ensure 

that the provided (pushed) materiel is controlled and utilized in a manner consistent with the 

requirements of the contract.

(e) GFM and CFM are subject to materiel receipt acknowledgement for materiel 

sourced from the DoD wholesale supply system, consistent with Volume 5 of this Manual and 

Reference (j). The materiel receipt acknowledgement must reference the applicable contract.

b. Implementing Procedures

(1) When a DoD Component authorizes contractor use of CFM, the DoD 

Component shall establish a process where:

(a) Contractors are not relieved of any agreed-to performance criteria imposed by

the contract.

(b) The DoD supply source shall have appropriate edit processes in place to 

comply with the access controls established under Federal Acquisition Regulation, Part 51 

(Reference (n)) and to ensure contractors obtaining CFM acquire only the materiel and quantities 

established in the scope of their contract.

(2) When a DoD Component authorizes contractor use of GFM or CFM, the DoD

Component shall establish one or more management control activities (MCAs) to maintain 

control over all requisitions submitted to the DoD wholesale supply system by contractors and 

by DoD Component activities when such DoD Component activity requisitions indicate

shipment to a contractor. The MCA shall carry out the procedures in DLM 4000.25-1 

(Reference (o)) and DLM 4000.25 (Reference (p)), and shall establish a system that:

(a) Validates and approves all contractor-initiated requisitions and DoD-initiated 

materiel requisitions that are coded for direct shipment to a contractor.

(b) Restricts contractor access to specific predetermined items and quantities of

those items by ensuring requisition validity, adequate authority, and consistency with the terms 

of an existing contract.

(c) Rejects contractor and DoD-initiated materiel requisitions that do not comply 

with the requirements of an existing contract.

(d) Passes approved requisitions containing relevant contract data to the

applicable DoD source for supply action.

(e) Ensures that the quantity requisitioned does not exceed the contract authorized 

quantity.

(f) Supports the supply source GFM or CFM validation process that ensures no 

shipment is made without MCA verification.
Enclosure 1, ADC 1014 

Page 3

(3) DoD supply sources shall refer requisitions for DoD materiel provided to 

contractors that have not passed through and been approved by an MCA back to the cognizant 

MCA for review and applicable action.

(4) The MCAs shall establish a management reporting system that:

(a) Maintains a contract, requisition, and shipment status history file that serves as

an auditable record of transactions involving DoD materiel provided to contractors.

(b) Provides the DoD contract administration offices a status report showing

all materiel requisitions that were rejected and all shipments of DoD materiel to contractors 

or to DoD activities for subsequent shipment to contractors.

(5) Each MCA shall prepare the DoD materiel status report required for the quarterly 

reporting periods ending March 31, June 30, September 30, and December 31, using DD

Form

2543, “Government Furnished Materiel (GFM) Status Report,” and provide the report to 

the cognizant DoD contract administration office.

(6) The ASD(L&MR) shall establish and maintain guidance for and monitor the

control of access to DoD inventories.

(7) The DoD Components shall carry out the procedures in this section and shall:

(a) Establish all required MCAs.

(b) Execute all procedures specified in Reference (p).

(c) Refer all requests for policy waivers from this section through the DoD 

Component Headquarters to the office of DASD(SCI).

(8) The Director, DLA Logistics Management Standards Office, shall maintain 

procedures supporting this section to control contractor access to DoD materiel inventories. 

Additionally, these procedures shall ensure visibility of GFP shipments through the pipeline 

by requiring the applicable contract data be included in all associated issue/ release orders 

and shipment status.”
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2, Page 1

Enclosure 2, DLMS Manual Procedures Revision

Update DLM 4000.25, Volume 2, as shown below. 

Note: Some of the changes reflected below are administrative changes to merge legacy 

MILSTRIP guidance with the DLMS procedures in preparation for future consolidation under a 

single manual. To distinguish these from the substantive changes associated with this approved 

change, the ADC 1014 substantive changes are highlighted in blue. All proposed revisions are 

identified in red bold italics. 

A. Procedures applicable to GFM/CFM controls:

C4.2.8. Government Furnished Materiel Requisitions

C4.2.8.1. General

C4.2.8.1.1. Purpose. This section prescribes policies and procedures for 

requisitioning GFM/contractor furnished materiel (CFM) by or for contractors from the DoD 

Supply System. These procedures establish guidelines for requisitioners, authorized contractors, 

and the DoD Components to obtain GFM from DoD inventories in support of contract 

requirements. These procedures also support the use of DLMS requisitioning by authorized 

contractors to obtain materiel from Government sources of supply to be used as contractor 

furnished materiel (CFM) under controls established by the authorizing Component and as 

specified in this chapter. In those instances where one Component is performing the 

procurement/contract writing for another Component that includes the authorization for a 

contractor to order or receive GFP (or Army CFM), the Component providing the 

procurement/contracting service and the Component requesting the contract shall coordinate 

efforts to ensure that the requesting Component’s management control activity (MCA) has 

access to the necessary contract and applicable contract modification information to perform its 

management control and accountability functions over Government supply system materiel 

access.

C4.2.8.1.2. DoDAAC Assignment Establishing an MCA. The DoD 

Components shall assign a unique RIC and distribution code to each MCA. Requisitioners, 

authorized contractors, and the DoD Components shall send all requisitions for GFM to the 

appropriate MCA for validation.

C4.2.8.1.3. Violations. Any attempt to circumvent GFM/CFM validation 

requirements is sufficient cause to refer the violation to the appropriate criminal investigating 

activity to determine possible fraud, waste, and abuse. The sponsoring Component or 

monitoring activity must refer all violations to the criminal investigators based on reports of 

rejected transactions or violations discovered during the post-validation process.

C4.2.8.1.4. Applicability. These procedures apply to all contractors and all 

DoD Components requisitioning GFM or CFM from DoD sources of supply. The production of 

ammunition is excluded from GFM control.
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2, Page 2

C4.2.8.2. Preparation of Requisitions and Related Transactions For Government 

Furnished Materiel to Contractors

C4.2.8.2.1. Initiation. Requisitions for GFM may be initiated by the 

responsible DoD Component or, subject to the terms of the contract, by contractors. 

Requisitions for GFM shall be prepared and initially submitted by GFM requisitioners, both 

contractors and DoD Components, using current DLMS media transmission techniques legacy 

MILSTRIP or DLMS transaction formats to the MCA designated for monitoring the contract. 

Transmission through DAAS shall be used to the extent practical.

C4.2.8.2.2. Source of Supply Processing. Sources of supply shall process 

requisitions and associated transactions containing the DoD Component Service/Agency codes 

designated for contractors under GFM controls and restrictions except when the issue will be for 

CFM with contractor reimbursement by other than an Army contractor. All Army contractor 

requisitions and associated transactions shall be processed under GFM/CFM controls.

C4.2.8.2.3. Required Information. All GFM requisitions, including referral 

and passing orders, must include GFM-related information as follows:

C4.2.8.2.3.1. MCA monitoring the contract shall be identified as the 

RIC-To.

C4.2.8.2.3.2. DoDAAC of the contractor requesting and/or receiving the 

materiel.

C4.2.8.2.3.3. Indication when issue is without reimbursement (including 

applicable signal code).

C4.2.8.2.3.4. Identification of the manufacturing directive number (MDN)

or contract number.

C4.2.8.2.3.5. Identification of the call or order number, when applicable.

C4.2.3.2.3.6. Identification of the contract line item number, when 

applicable.4

C4.2.8.2 4. Contract Information. All GFM requisitions for or by contractors 

must identify the contract number and other appropriate contract data, as required. 

Components authorizing GFM may direct the inclusion of the manufacturing directive 

number (MDN) as supplemental to the authorizing contract number.5

C4.2.8.3. Submissions of Government Furnished Materiel Requisitions

 4 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant 

contract number (rather than the abbreviated contract number authorized under legacy MILSTRIP 

procedures). 5 Refer to ADC 1014. Staggered implementation is authorized for the transition to the mandatory inclusion of the 

contract number (rather than MDN as an alternative to the contract number).
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2, Page 3

C4.2.8.3.1. Applicability. Requisitioners, control offices, and monitoring 

activities must submit all requisitions and associated transactions for GFM, regardless of origin 

(such as contractor or DoD Component-initiated), to the appropriate DoD Component MCA.

C4.2.8.3.2. Forwarding. After validating the GFM requisitions, the DoD 

Component MCA shall forward the validated requisitions to the source of supply. The DoD 

Component MCA may pass validated transactions internally where the MCA and source of 

supply are collocated. The DoD Component MCA shall send the validated transactions via 

DAAS when the MCA and source of supply are not collocated.

C4.2.8.3.3. Modifier Transactions. Modifier transactions are authorized for 

GFM requisitions to modify information such as the project code, priority designator (PD), 

advice code, and the required delivery date (RDD). Modifiers may not be used to change the 

ship-to/bill-to information. Modifiers are subject to GFM controls and validation procedures.

C4.2.8.4. Management Control Activity Processing of Government Furnished 

Materiel Requisitions and Related Transactions

C4.2.8.4.1. Management Control Activity Actions. The MCA shall receive and 

validate the data in the GFM requisitions, and related transactions referral orders, and passing 

orders, as well as subsequent modifiers and follow-ups, based on the criteria furnished by the 

procurement and/or contracting offices and as described in Table C4.T2. The MCA shall make 

changes, reject, or continue the processing action. The MCA shall:

C4.2.8.4.1.1. Item Verification. Verify the item requisitioned against a 

valid contract to determine authority for issue to the contractor. If blank, incorrect, or not 

authorized, reject with Status Code DN.

C4.2.8.4.1.2. Quantity Authorization. Determine if the item ordered is 

authorized by contract, and verify the quantity. If blank or invalid, reject with Status Code CD. 

If the requisitioned quantity exceeds the remaining authorized quantity, reject the quantity 

exceeding the authorized quantity with Status Code DJ. If authorized quantity has been 

exhausted by previous requisition(s), reject total requisitioned quantity with Status Code DQ.

C4.2.8.4.1.3. Unit of Issue Validation. Validate the unit of issue in 

conjunction with the quantity to ensure that the quantity requisitioned does not exceed the 

authorized quantity. (NOTE: If a change of unit pack has occurred, appropriate adjustment 

should be made for the quantity authorized.) If the resulting requisitioned quantity exceeds the 

remaining quantity authorized, reject the quantity that exceeds the authorized quantity with 

Status Code DJ. If the authorized quantity has been exhausted by previous requisition(s), reject 

the total quantity requisitioned with Status Code DQ.

C4.2.8.4.1.4. Contractor DoDAAC Validation. Determine if the 

contractor DoDAAC is valid, and if incorrect or not authorized, reject with Status Code DN.
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2, Page 4

C4.2.8.4.1.5. Contract Number Validation. Determine if the 

manufacturer’s directive number (MDN) or contract number is valid and if invalid, reject with

Status Code DB. 

C4.2.8.4.2. History Files. The MCA shall maintain a requisition history file to 

serve as an auditable record of each GFM transaction. In addition, the MCA shall generate

reports required by DoD 4140.1-R.

C4.2.8.4.3. Telephonic Requisitions. Under emergency conditions, such as a 

potential contract work stoppage, the MCA may receive telephonic requisitions, with PDs 01-08, 

for GFM. When this occurs, the MCA may telephone the requisitions to the appropriate source 

of supply and validate the requirements afterward. If the post validation process reveals the 

requisitioner is not authorized GFM, the MCA shall:

C4.2.8.4.3.1. Send cancellation requests to the appropriate source of 

supply, and

C4.2.8.4.3.2. Advise the appropriate criminal investigating agency for 

determination of fraud, waste, and abuse.

C4.2.8.4.4. Forwarding. Upon completion of the validation process, the MCA 

shall identify itself as the FROM organization in the transaction and forward the requisition

transactions, or internal transactions (optional only when the MCA and source of supply are 

collocated in the same distribution system), cancellations, follow-ups, modifiers, passing 

orders, or referral orders to the applicable source of supply via DAAS.

C4.2.8.4.4.1. Update the outgoing transaction to insert the RIC-To of 

the source of supply.

C4.2.8.4.4.2. Insert the distribution code of the MCA validating the 

transaction.

C4.2.8.4.4.3. Perpetuate all applicable contract data. Under DLMS, the 

MCA must include the DFARS contract number. Where required by the Component, the 

MCA may also perpetuate the MDN consisting of the MCA’s distribution code and two other 

alpha/numeric characters as assigned.6

C4.2.8.5. Management Control Activity Processing of Government Furnished 

Materiel Validation Requests. MCAs in receipt of a GFM validation request (DLMS 517G, 

GFM Validation Request) shall validate the data contained therein. This validation process 

must be completed and a DLMS 517G GFM Validation Response transaction created and 

 6 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant 

contract number (rather than the abbreviated contract number authorized under legacy MILSTRIP 

procedures) and for the transition to the mandatory inclusion of the contract number (rather than MDN as an 

alternative to the contract number).
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 5

forwarded to the applicable source of supply within 15 days of receipt of the GFM validation 

request transaction. by the response due date indicated in the validation request and forward A

GFM validation response (DLMS 517G) shall be transmitted to the applicable source of supply 

as follows:

C4.2.8.5.1. If the requisition has been previously validated, cite Advice Code 

2M.

C4.2.8.5.2. If the requisition has not been previously validated and the call 

order number/procurement instrument identification number (PIIN) (or MDN, if required by the 

Component in addition to the call order number/PIIN) is not present, cite Advice Code 2U.

C4.2.8.5.3. If the requisition has not been previously validated and the call 

order number/PIIN (or MDN) is present, validate data as indicated in Table C4.T2 including the 

stock number, unit of issue/quantity, and contractor, and generate the GFM Validation response 

as follows:

C4.2.8.5.3.1. If the validation process reveals that the contract is not 

valid, respond with Advice Code 2U.

C4.2.8.5.3.2. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, respond with Advice Code 2R and indicate the quantity 

approved for issue in the QTY segment.

C4.2.8.5.3.3. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, respond with Advice Code 2Q and indicate the total 

quantity is disapproved for issue in the QTY segment.

C4.2.8.5.3.4. If the validation process reveals that the requested item, or 

contractor is not authorized GFM under a valid contract, respond with Advice Code 2V.

C4.2.8.5.3.5. If the validation process reveals that the requested item is 

authorized, respond with Advice Code 2M.

C4.2.8.5.4. MCAs in receipt of supply status (DLMS 870S transactions) with 

Status Code BF shall review for establishment of a valid requisition. If the a valid requisition is 

valid exists, a DLMS 869F transaction shall be generated. If a valid requisition does not exist, a 

report shall generated for internal review. Subsequent receipt of a valid requisition shall be 

processed under the procedures/validation process indicated in Table C4.T2.

Table C4.T2. MCA Validation Process for GFM Transactions

CODE OR DATA 

ELEMENT

VALIDATION OF ENTRY

Transaction Type If DLMS 511R, Requisition, Referral, or Passing Order (DICs A01, 

A02, A04, A05, A0A, A0B, A0D, A0E, A3_, A4_,)
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 6

Table C4.T2. MCA Validation Process for GFM Transactions

CODE OR DATA 

ELEMENT

VALIDATION OF ENTRY

DLMS 511M, Requisition Modification (DIC AM_) (for 

modification to RDD, project code, PD, or advice code),

DLMS 869F, Requisition Follow-up (DIC AT_),

continue the GFM validation.

Stock Number Verify item requisitioned against a valid contract to determine 

authority for issue to the contractor. If blank, incorrect, or not 

authorized, reject with Status Code DN.

Unit of Issue Validate the unit of issue in conjunction with the quantity to ensure 

that the requisitioned quantity does not exceed the authorized 

quantity. If quantity is excessive, see validation of quantity field. 

(Note: If a change of unit pack has occurred, appropriate 

adjustment should be made for authorized quantity.)

Quantity If ordered item is authorized by contract, verify the quantity. If 

blank or invalid, reject with Status Code CD. If the requisitioned 

quantity exceeds the remaining authorized quantity, reject the 

quantity exceeding the authorized quantity with Status Code DJ. If 

authorized quantity has been exhausted by previous requisition(s), 

reject total requisitioned quantity with Status Code DQ.

Requisitioner If blank or incorrect, discard. If not authorized, reject with Status 

Code DN.

Document Number If blank or incorrect, reject with Status Code CD.

Supplementary Address If contractor DoDAAC, and affected by signal code, and incorrect 

or not authorized, reject with Status Code DN.

Signal and Fund If signal and fund codes indicate issues without contractor 

reimbursement, process as GFM; otherwise, consider as CFM. 

CFM requisitions, except for Army, are not subject to MCA review. 

All Army contractor requisitions and associated transactions shall 

be processed under GFM controls. DAAS shall respond to requests 

for MCA review for Army CFM under special processing rules 

authorized by the Army.

Manufacturer’s Directive 

Number

If the MDN option is required by the Component and the MDN 

equates to a valid contract number, validate; otherwise, reject with 

Status Code DB.
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 7

Table C4.T2. MCA Validation Process for GFM Transactions

CODE OR DATA 

ELEMENT

VALIDATION OF ENTRY

Contract Call Order Number If specified by S/A contract, and entry is blank or incorrect, reject 

with Status Code DB.

Procurement Instrument 

Identification Number

If blank, or contract is not on MCA file, or contract has expired, 

reject with Status Code DB. (If requisition originated in the legacy 

MILSTRIP format, then only the last eight positions of the PIIN

are mandatory.) 

C4.2.8.6. Source of Supply Processing of Government Furnished Materiel 

Requisitions and Related Transactions

C4.2.8.6.1. General. Sources of supply receiving GFM requisitions, modifiers, 

inquiries follow-ups, and cancellations, regardless of the method of transmission, shall process 

such transactions under these procedures. Sources of supply receiving GFM requisitions for 

items not managed by their activity shall reject the requisitions with Status Code CH. Sources of 

supply shall edit the GFM transactions for the prescribed data elements and codes and correct, 

continue the processing actions, or provide the appropriate reject status.

C4.2.8.6.2. Validation. Sources of supply shall validate all GFM transactions. 

Sources of supply in receipt of requisitions, passing orders, referral orders, modifiers, or followups being treated as requisitions, containing a contractor’s service/agency code shall perform the 

source of supply/MCA validation process except when the signal and fund codes indicate the 

issue will be with contractor reimbursement by other than an Army contractor. All Army 

contractor requisitions and associated transactions shall be processed under GFM/CFM controls. 

The source of supply/MCA validation process is not required when an internal requisition 

transaction is received from a collocated MCA in the same distribution system. However, 

sources of supply must have safeguards in place to ensure that only internal transactions 

generated by the collocated MCA are accepted/processed.

C4.2.8.6.3. Telephonic Requisitions. Under emergency conditions, sources of 

supply may receive telephonic (PD 01-08) requisitions from the MCA or requisitioner. The 

source of supply may process these requisitions for immediate supply action. Subsequent to 

taking immediate supply action, the GFM validation process shall be performed. If the GFM 

validation response is not received within 15 days of the request or the advice code indicates 

that the transaction validation process reveals the activity is not authorized GFM, refer the 

incident to the appropriate criminal investigating agency.

C4.2.8.7. Source of Supply Government Furnished Materiel Validation Process. For 

each GFM requisition or transaction that is treated as a requisition, the source of supply shall 

employ one of the following options:
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 8

C4.2.8.7.1. Create and forward a DLMS 517G GFM Validation Request to the 

MCA or distribution code identified in the requisitioner's transaction. If the MCA and 

distribution code are is invalid or missing, reject with Status Code CL.

C4.2.8.7.2. Create and forward a GFM validation request to DLA Transaction 

Services even if an MCA is contained in the requisitioner's transaction. DLA Transaction 

Services shall perform edits regarding the validity of the MCA data. 

C4.2.8.7.3. Use a combination of the above options: one for intra-Component

transactions and one for inter-Component transactions.

C4.2.8.7.4. Suspend further supply support action on the requisitioner's 

transaction pending receipt of the GFM validation response or until 15 days have elapsed from 

the date of the GFM the validation request, whichever occurs first.

C4.2.8.7.5. If the GFM validation response is not received and 15 days have 

elapsed from GFM the validation request, reject the requisitioner's transaction with Status Code 

DR.

C4.2.8.7.6. Upon receipt of the GFM validation response, the source of supply 

shall process the suspended transaction using instructions provided by the advice/status code.

C4.2.8.7.6.1. If Advice Code 2U, reject with Status Code DB.

C4.2.8.7.6.2. If Advice Code 2R, process for the approved quantity 

indicated in the GFM validation response. Reject the quantity difference between the suspended 

transaction and the GFM validation response with Status Code DJ.

C4.2.8.7.6.3. If Advice Code 2Q, reject with Status Code DQ.

C4.2.8.7.6.4. If Status Code CL, reject with Status Code CL.

C4.2.8.7.6.5. If Advice Code 2V, reject with Status Code DN.

C4.2.8.7.6.6. If Advice Code 2M, process under applicable source of 

supply procedures.

C4.2.8.7.6.7. If the advice/status code is invalid or an advice/status code 

is not indicated, reject with Status Code DR.

C4.2.8.7.7. If a GFM validation response is received and there is a record of the 

requisition, but a GFM validation request has not been submitted, discard the GFM validation 

response and generate a GFM validation request.

C4.2.8.7.8. If a GFM validation response is received and there is no record of 

the requisition, provide Status Code BF.

C4.2.8.8. DAAS Processing Of GFM Transactions. DAAS shall pass the following:
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 9

C4.2.8.8.1. All GFM transactions to the identified MCA. If the MCA is not a 

valid MCA, reject with Status Code CL.

C4.2.8.8.2. All GFM validation requests to the identified MCA. If the MCA is 

invalid, generate a GFM validation response with Status Code CL to the source of supply.

C4.2.8.8.3. All GFM validation responses to the identified source of supply.

C4.2.8.9. Exception Processing for Government Furnished Materiel for Packaged 

Fuel Additives Managed by DLA. DLA Transaction Services shall perform the DLMS 517G 

validation on behalf of the DLA Energy for selected requisitioning/bill-to activities and stock 

numbers in accordance with the following procedures:

C4.2.8.9.1. DLA Transaction Services shall maintain a DLA Energy GFM table 

that will identify DLA Energy-established U-series contractor DoDAACs authorized to 

requisition specified additive NSNs. The authorized DLA Energy POC shall provide to DLA 

Transaction Services the U-series DoDAAC/NSN combinations for the DLA Energy GFM table.

C4.2.8.9.2. DLA Energy sponsored orders for GFM shall specify DoDAAC 

SJ0630 (Americas East), SJ0606 (Americas West), SJ0629 (Middle East), SJ0601 (Europe), 

SJ0600 (Pacific), and SC0600 (DLA Energy for UC series DoDAAC contingency locations) as 

the requisitioner/bill-to activity. They will contain a U-series DoDAAC designated as the ship-to 

activity, and contain the applicable contract number and the DLA Energy assigned MDN.

C4.2.8.9.3. DLA Transaction Services shall route requisitions and requisition 

related transactions (DLMS 511R/511M/869F) to the source of supply for the NSN ordered, and 

the source of supply will generate the required DLMS 517G, GFM Validation Request to DLA 

Transaction Services.

C4.2.8.9.4. DLA Transaction Services shall capture any DLMS 517G 

transactions containing DoDAAC SJ0630, SJ0606, SJ0629, SJ0601, SJ0600, or SC0600 (for UC 

locations) as the requisitioner/bill-to and a U-series DoDAAC as the ship-to and match it against 

the DLA Energy GFM table. If a table match is made by U-series DoDAAC and the NSN, then 

DLA Transaction Services shall respond to the source of supply with a DLMS 517G MCA GFM 

Validation Response, with Advice Code 2M, indicating the order is authorized for processing. If 

no match, DLA Transaction Services shall respond with DLMS 517G with Advice Code 2V, 

indicating the order is not authorized for processing.

C4.2.8.9.5. The source of supply shall process the DLMS 517G Validation 

Response and either honor the order or reject the suspended transaction using Status Code DN, 

based on the advice code provided by DLA Transaction Services.

C4.2.8.10. DAAS Special Processing for Army7

. Pendingfull implementation of 

MCA procedures in Army systems, DLA Transaction Services shall assist the Army by 

 7 Procedures to control access to DoD material inventories by defense contractors last reported as not 

implemented by USA (Retail). Refer to AMCL 1A.
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 10

performing the GFM MCA transaction validation requirement for the Army wholesale MCAs 

and recording all transactions into a history file for eventual processing to the appropriate 

MCA using the following procedures:

C4.2.8.10.1. Process all DLMS 511R (DIC A0_) Army contractor identified 

requisitions with the below listed first two positions of the DoDAAC to the applicable Army 

MCA. Contractor requisitions with other than the DoDAAC entries indicated are considered 

Army retail and will be routed to the proper source of supply with the DAAS RIC “SGA” or 

“SHA” identified as the MCA.

C4.2.8.10.1.1. If the first two positions of the document number or 

supplemental address is CB, pass to RIC A81 (TACOM MCA)

C4.2.8.10.1.2. If the first two positions of the document number or 

supplemental address is is CL, pass to RIC A82 (AMCOM MCA).

C4.2.8.10.1.3. If the first two positions of the document number or 

supplemental address is is CG, pass to RIC A83 (CECOM MCA).

C4.2.8.10.1.4. If the first two positions of the document number or 

supplemental address is is CM, pass to RIC A84 (TACOM MCA)

C4.2.8.10.1.5. If the first two positions of the document number or 

supplemental address is is CK, pass to RIC A85 (TACOM MCA).

C4.2.8.10.1.6. If the first two positions of the document number or 

supplemental address is CH, pass to RIC A86 (AMCOM MCA)

C4.2.8.10.2. For requisition modifications (DLMS 511M/DIC AM_) and 

requisition follow-ups (DLMS 869F/DIC AT_) transactions, containing a valid MCA 

distribution code as identified below, the DAAS RIC “SGA” or “SHA” will be entered into 

MCA field and routed to the appropriate source of supply. If a valid MCA is not identified and 

the transaction contains the entries cited above for in the first two positions of the document 

number or supplemental address, the transaction will be passed to the appropriate MCA. If 

none of these conditions apply, the transaction will be considered retail and be routed to the 

appropriate source of supply with the DAAS RIC “SGA” or “SHA” entered into MCA RIC 

field. The following are valid MCA distribution codes:

C4.2.8.10.2.1. I (India) - TACOM MCA

C4.2.8.10.2. L (Lima) - AMCOM MCA

C4.2.8.10.2.3. P (Papa) - CECOM MCA

C4.2.8.10.2.4. S (Sierra) - TACOM MCA

C4.2.8.10.2.5. Y (Yankee) - TACOM MCA
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 11

C4.2.8.10.6. E (Echo) - AMCOM – MCA

C4.2.8.10.2.7. 8 (Eight) - USACEA MCA 

C4.2.8.10.3. Upon receipt of GFM validation transactions, a GFM validation 

response transaction shall be generated with Status Code 2M and returned to the RIC of the 

source of supply submitting the GFM validation request transaction.

C4.2.8.10. Contractor Requisitions for Contractor Furnished Materiel 

C4.2.8.10.1. Requisitions for materiel from Government sources of supply for 

shipment to contractors that identify the contractor as the bill-to activity are not subject to GFM 

MCA controls with the exception of Army contractor requisitions to which MCA controls are 

applicable. DAAS shall validate transactions for Army contractor requisitions of CFM for those 

items that contractors are authorized to requisition as CFM as specified in this chapter and for 

non-wholesale level supply as designed by the contractor-series DoDAAC. DoD Components 

shall establish appropriate procedures for oversight of CFM requisitions in accordance with the 

Federal Acquisition Regulation.

C4.2.8.10.2. DAAS Processing of CFM Transactions. The process described in 

this subparagraph provides mandatory CFM controls for CFM requisitions where the bill-toactivity, as identified in the requisition, is an Army contractor and the source of supply is DLA. 

This process is optional for other DoD Components and may be expanded to include other 

sources of supply, if needed. DAAS shall maintain a list of DoD Component-authorized 

contractor DoDAACs and the associated NSNs/DoD-managed part numbers for which these 

contractors may submit CFM requisitions on a CFM Authorized Materiel Table for use in 

validating requisitions regardless of method of payment. CFM contractor transactions that match 

the CFM Authorized Materiel Table by DoDAAC, but do not match by NSN or part number, 

shall be rejected with Status Code CL; requisitions that match on DoDAAC and NSN/part 

number shall be processed as valid. DAAS shall enter the DAAS RIC SGA or SHA as the 

validating MCA. DAAS shall perform DLMS 517G validation requirement for authorized CFM 

requisitions that match to the CFM Authorized Materiel Table. DAAS will furnish CFM reports 

upon request for use by the contracting officer in verifying that quantities ordered are within the 

contract allowance. Army contractor requisitions that do not match the CFM Authorized 

Materiel Table shall be processed by DAAS under the MCA waiver exception process or passed 

to the applicable MCA. CFM requisitions for other Service contractors shall be passed to the 

source of supply. NSNs listed in the table may be modified over the course of this agreement 

when appropriate Army contracting officer provides such authority. Updates to the authorized 

list shall be collected, consolidated into one Excel file by the designated DLA Lead Center POC 

with proof of Army Contracting Officer (CO) concurrence and provided to Headquarters DLA 

Army Performance Based Logistics (PBL) action officer. DLA shall coordinate updates to 

individual contractor lists with DLA DoD EMALL and DLA Transaction Services on a monthly 

basis. To optimize program changes, all additions to Army partnership lists shall be made during 

an agreed-to monthly timeframe between DLA and support entities.
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 12

C4.2.8.11. Preparation of DoD EMALL Requisitions by Contractors. Authorized 

contractors may establish DoD EMALL accounts to facilitate materiel requisition submissions. 

To register, go to https://dod-emall.dla.mil and click on New User Registration. Access to DoD 

EMALL is now fully Common Access Card (CAC)/Public Key Infrastructure (PKI) enforced. 

Details of the access requirements are listed on the registration pages of the EMALL site. Prior 

to establishing the account, the applicable contracting officer must ensure that the contractor is 

authorized access to Government supply sources and must agree to review monthly or quarterly 

reports prepared by the DoD EMALL monitoring contractor activity. The applicable contracting 

officer must also provide a list of approved NSN/part numbers associated with each 

account/contractor DoDAAC for Army authorized CFM. Army contractors will be processed 

under GFM/CFM controls as described.

C4.2.8.11.1. DoD EMALL shall validate that contractors are authorized to 

purchase materiel from DoD supply sources as a prerequisite for submission of EMALL orders. 

DoD EMALL requisitions for GFM will be subjected to prescribed rules for MCA controls 

within DoD EMALL or within the DAAS. DoD EMALL CFM requisitions indicating corporate 

credit card method of payment are subject to special processing controls as described below. 

Additionally, CFM requisitions for Army authorized contractors shall be validated to ensure that 

requisitioned NSNs or DoD managed part numbers are authorized regardless of the method of 

payment under CFM controls described above.

C4.2.8.11.2. The DoD EMALL program office shall identify to DLA 

Transaction Services all contractors authorized access to Government materiel for purchase as 

CFM using a corporate credit card as the method of payment. DAAS shall maintain these 

DoDAACs as an authorized contractor edit table (referenced hereafter as the DoD EMALL CFM 

Table) to be employed during initial processing and for DLMS 517G processing.

C4.2.8.11.3. DoD EMALL requisitions for shipment to contractors using 

corporate credit card payment are assigned Signal Code B, Fund Code XP, and the supplemental

address of the DoD EMALL DoDAAC (SP5200). This configuration identifies a Government 

DoDAAC as the bill-to activity, thereby triggering DAAS and the DoD Component source of 

supply processing systems to misinterpret such transactions as GFM requisitions. DAAS shall 

validate these transactions against existing GFM edits and the DoD EMALL CFM Table to 

determine appropriate action. If the contractor requisition does not contain a valid MCA 

identification code and the DoDAAC is not listed in the DoD EMALL CFM Table, DAAS shall 

reject with Status Code CL. If an MCA is identified by either a distribution code or a RIC, 

DAAS shall forward the requisition to the source of supply. The source of supply shall submit a 

DLMS 517G to DAAS for validation following GFM MCA procedures (including Army CFM). 

DAAS will recognize the EMALL supplemental address and again employ existing GFM edits 

and the DoD EMALL CFM Table to take appropriate action. If the validation using the DoD 

EMALL CFM Table identifies the contractor DoDAAC as authorized by the contracting officer 

for ordering CFM using corporate credit cards, then DLA Transaction Services shall validate the 

requisition and respond to the source of supply with a DLMS 517G Validation Response using 

Advice Code 2M indicating the requisition is valid. The source of supply shall continue 

processing. If the contractor DoDAAC is not contained on the DoD EMALL CFM Table, but 

the requisition contains a valid MCA code, then DLA Transaction Services shall forward the 
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 13

DLMS 517G Validation Request to the MCA for validation. If the contractor DoDAAC is not 

contained on the DoD EMALL CFM Table, or does not match the CFM Authorized Materiel 

Table, when applicable, and the requisition does not contain a valid MCA code, then DAAS shall 

provide a DLMS 517G Validation Response with Status Code CL indicating the transaction is 

invalid. The source of supply shall reject the requisition.

C4.2.8.11.4. To support DoD requirements for oversight of materiel sold to 

contractors, the DoD EMALL program office shall provide reports to monitor contractor activity. 

For contracts having a maximum total dollars ceiling, a DoD EMALL report shall be provided to 

the contracting officer when the cumulative value of CFM ordered reaches 80% of the ceiling.

C4.2.8.12 Inventory Control Point/Integrated Materiel Management-Directed 

Shipment of Non-Requisitioned Government Furnished Materiel Based on a Bill of Materiel. 

ICP/IMM-directed shipments of GFM may be managed through the use of a Bill of Materiel 

(BOM) as identified under the terms of the DoD contract. In this context, the BOM identifies the 

raw materiels/component parts needed to assemble/manufacture/repair the end item or final 

product. Based on the unit of allowance, the number/amount of GFM component materiel 

needed to accommodate the total number of end items to be manufactured/assembled/repaired on 

a specific contract/purchase order, may be calculated and provided. This procedure eliminates 

the need for separate GFM requisitions for the component materiel and subsequent MILSTRIP 

MCA validation. Instead, this process allows the ICP/IMM to push the materiel to the contractor 

as required by schedule and/or usage.

C4.2.8.12.1. Upon contract award for production of an end item or final 

product, the BOM becomes the basis for determining the quantity of GFM required by the 

contractor. These deliveries shall only include stocked raw materiel/component parts that the 

Government provides at no separate charge to the contractor for assembly/manufacture of the 

end item/final product. Under this process, the ICP/IMM shall use internal control procedures to 

monitor consumption of raw materiel/component parts against the receipt of items awarded by 

contract.

C4.2.8.12.2. The ICP/IMM shall prepare materiel release orders for stock 

shipment using document numbers based upon a DLA established DoDAAC. The ship-to 

location cited in the release order shall identify the contractor DoDAAC authorized to receive 

GFM. If no DoDAAC is assigned, the contractor facility may be identified by CAGE or as an 

exception ship-to address. The MRO shall include the authorizing contract number, and the 

call/order and CLIN, when applicable. The storage activity shall provide shipment 

confirmation to the ICP/IMM for monitoring GFM shipments and shall prepare shipment status

perpetuating applicable contract data. For contractors without capability to accept legacy 80 

record position/DLMS transactions, status of the GFM component delivery shall be provided 

upon request by the contractor. The assembled/manufactured end items may be shipped directly 

to customers or shipped to a storage location for future use.

C4.2.8.12.3. Use of the above business process does not relieve the ICP/IMM 

from a management reporting requirements required by DoD 4140.1-R, DoD Supply Chain 
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 14

Materiel Management Regulation.i Materiel Receipt Acknowledgement is required for GFM, 

including pushed shipments, under MILSTRAP procedures.

C4.2.8.12.4. This process is discretionary and may not be applicable to all 

commodities and contracts requiring GFM. This process may only be used to support GFM 

requirements satisfied by the DoD Component issuing the contract (that is, by design, it does not 

support inter-Component materiel support).

Enclosure 2, Continued

B. Procedures applicable to the DLMS Materiel Release Order (MRO):

C4.7.12. Preparing MROs

C4.7.12.1. Originator. MROs, DLMS 940R, Materiel Release, are prepared by the 

source of supply as a result of processing requisitions against inventory records and determining 

that materiel is available. MROs are used as a directive for release and shipment of materiel 

from stock.

C4.7.12.1.1 MROs directing shipment of requisitioned GFM shall perpetuate 

contract data to include the contract number authorizing GFP, and the call/order and CLIN 

when available. Contract data shall be provided by the source of supply for pushed GFM not 

initiated by a requisition.

C4.7.12.1.2. MROs directing shipment of reparables for induction for

commercial maintenance shall include the contract number authorizing GFP, and the 

call/order and CLIN when available. 

C4.7.12.1.3. MROs directing shipment of GFP in contractor custody shall 

include the contract number authorizing GFP, and the call/order and CLIN when available. 

------------------------------------------------

C. Procedures applicable to the DLMS Shipment Status:

C5.1.3.1.7. Under DLMS, the shipment status shall perpetuate data content as 

applicable: project code, the special requirements code (legacy MILSTRIP required delivery 

date (RDD) coded entries, e.g. 999), and priority designator. Shipment status applicable to

shipment of GFP, including requisitioned GFM and shipment of reparables to/from

commercial maintenance, shall perpetuate contract data from the MRO, to include the 

contract number authorizing GFP, and the call/order and CLIN when provided.

----------------------
DLMS Manual Vol 2, Chapter 4

ADC 1014, Enclosure 2

Page 15

C5.1.3.3.3. For outbound non-MILS shipments documented on a DD 1149, a 

DLMS 856S shall be created. Table C5.T1 lists the minimum data elements that should be 

included in the shipment status message; sources of the data are the DD1149 and pRFID tag 

information. Shipment status applicable to shipment of GFP shall perpetuate all GFP 

contract data from the shipping documentation, to include the contract number authorizing 

GFP, and the call/order and CLIN when provided.
MILSTRIP Manual, Chapter 11

ADC 1014, Enclosure 3, Page 1

Enclosure 3, MILSTRIP Chapter 11 Revision

Update DLM 4000.25-1, MILSTRIP Manual as shown below. 

C11. CHAPTER 11

CONTRACTOR ACCESS TO GOVERNMENT 

SOURCES OF SUPPLY

C11.1. GENERAL

C11.1.1. This chapter prescribes policies and procedures for requisitioning GFM by or for 

contractors from the DoD Supply System. These procedures establish guidelines to 

requisitioners and authorized contractors and Services/Agencies (S/As) to obtain government 

furnished materiel (GFM) from DoD inventories to fulfill contract requirements.8 These 

procedures also support the use of MILSTRIP requisitioning by authorized contractors to obtain 

materiel from Government supply sources to be used as contractor-furnished materiel (CFM) 

under controls established by the authorizing Component and as specified in this chapter.

C11.1.2. The S/As shall assign a unique Routing Identifier Code (RIC) and distribution 

code to each management control activity (MCA) validating GFM requisitions.

C11.1.3. Any attempt to circumvent GFM/CFM validation requirements is sufficient cause 

to refer violation to the appropriate criminal investigating activity to determine possible fraud, 

waste, and abuse. The sponsoring Service shall make violation referrals to criminal investigating 

activities or monitoring MCA based upon reports of rejected transactions or violations 

discovered during the post validation process.

C11.2. APPLICABILITY

C11.2.1. These procedures apply to all contractors and all S/A activities requisitioning 

GFM or CFM from DoD sources of supply. 

C11.2.1. Ammunition production is excluded from GFM control.

C11.3. PREPARATION OF REQUISITIONS AND RELATED TRANSACTIONS FOR 

GOVERNMENT MATERIEL FURNISHED TO CONTRACTORS

C11.3.1. Requisitions for GFM may be initiated by the responsible S/A or, subject to the 

terms of the contract, by contractors. Requisitions for GFM shall be prepared and initially 

submitted by GFM requisitioners, both contractors and S/As, using current MILSTRIP media 

transmission techniques transaction formats to the S/A MCA designated for monitoring the 

contract. Transmission through the Defense Automatic Addressing System (DAAS) shall be 

utilized to the extent practical.

 8 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to Approved MILSTRIP Change Letter (AMCL) 1A.
MILSTRIP Manual, Chapter 11

ADC 1014, Enclosure 3, Page 2

C11.3.2. Requisitions and associated transactions containing an S/A code designated for 

contractors, as specified in Appendix AP2.2 (rp 30-35 or rp 45-50 if ship-to address), shall be 

processed under GFM/CFM controls and restrictions except when the signal and fund codes 

indicate that the issue will be for CFM with contractor reimbursement by other than an Army 

contractor. All Army contractor requisitions and associated transactions must be processed 

under GFM controls.

C11.3.3. In addition to normal requisition data, GFM requisitions shall contain the 

following:

C11.3.3.1. Document Identifier Codes (DlCs) A01, A02, A04, A05, A0A, A0B, 

A0D, A0E, A3_, and A4_ shall be in rp 1-3.

C11.3.3.2. RlC in rp 4-6 identifying the appropriate S/A MCA monitoring the 

contract.

C11.3.3.3. Contractor generated requisitions shall contain the appropriate contractor 

DoD activity address code (DoDAAC) in rp 30-35.

C11.3.3.4. S/A generated requisitions for GFM shall contain the appropriate 

contractor DoDAAC in rp 45-50.

C11.3.3.5. When applicable, a signal code in rp 51 to indicate issue without 

reimbursement.

C11.3.3.6. When applicable, a fund code in rp 52-53 to indicate issue without 

reimbursement.

C11.3.3.7. At the option of the S/A, a three-character manufacturing directive 

number (MDN) in rp 54-56 may be used in lieu of the procurement instrument identification 

number (PIIN) in rp 73-80.

C11.3.3.8. When applicable, the call order number in rp 69-72.

C11.3.3.9. At the option of the S/A, The last eight positions of the PIIN in rp 73-80 

in lieu of the MDN in rp 54-56. This entry is mandatory if the MDN is not entered in rp 54-56.

C11.3.3.10. GFM non-national stock number (NSN) requisitions shall be identified 

with an E in rp 68; the call order number, if appropriate, in rp 69-72; and at the option of the S/A, 

the last eight positions of the PIIN in rp 73-80 in lieu of the MDN in rp 54-56 (this entry is 

mandatory if the MDN is not entered in rp 54-56 optional).
MILSTRIP Manual, Chapter 11

ADC 1014, Enclosure 3, Page 3

C11.4. SUBMISSION OF GOVERNMENT-FURNISHED MATERIEL REQUISITIONS AND 

RELATED TRANSACTIONS

C11.4.1. Frequency of submitting GFM requisitions is the prerogative of the requisitioner. 

GFM requisitions shall be submitted, when necessary, to meet contract requirements.

C11.4.2. GFM requisitions (DIC A0_) and associated GFM transactions shall be initially 

submitted to an MCA.

C11.4.3. It is mandatory that GFM requisitions be forwarded regardless of origin, such as 

contractor or S/A initiated, to the appropriate S/A MCA for validation. After validation by the 

S/A MCA, the MCA shall forward validated requisitions to the inventory control point (ICP). 

Where the MCA and ICP are collocated, internal passing of transactions is authorized. When the 

MCA and ICP are not collocated, the transmission should be via DAAS, where practical. In 

those instances where a Component is performing the procurement/contract writing for another 

Component that includes the authorization for a contractor to order or receive GFP, the 

Component providing the procurement/contracting service and the Component requesting the 

contract shall coordinate efforts to ensure that the requesting Component’s MCA has access to 

the necessary contract and applicable contract modification information to perform its 

management control and accountability functions over Government supply system materiel 

access.

C11.4.4. Modifier transactions are authorized for GFM requisitions only to modify the 

project code, priority designator (PD), advice code, and the required delivery date (RDD). 

Modifiers may not be used to change the Supplementary Address (SUPADD) to a contractor’s 

SUPADD. Modifiers are subject to GFM controls and validation procedures.

C11.5. MANAGEMENT CONTROL ACTIVITY PROCESSING OF GOVERNMENTFURNISHED MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

C11.5.1. The MCA shall receive GFM requisitions (DICs A01, A02, A04, A05, A0A, 

A0B, A0D, and A0E), passing orders (DIC A3_), referral orders (DIC A4_), follow-ups (DIC 

AT_), and modifiers (DIC AM_ only for RDDs, project codes, PDS, and advice codes). The 

MCA may receive supply status (DIC AE_), shipment status (DIC AS_), and MOV transactions 

(DICs AN_ and AP_), follow-ups (DICs AF_ and AK_), and cancellations (DIC AC_). All other 

DICs received by the MCA shall be rejected with Status Code CR.

C11.5.2. Based upon criteria furnished by procurement/contracting offices, the MCA shall 

validate the data elements and codes in GFM transactions other than DICs AE_, AS_, AF_, 

AK_, AC_, AN_, and AP_, as indicated in Table C11.T1. The MCA shall make changes, reject, 

or continue processing action on the GFM transactions.

C11.5.3. The MCA shall maintain requisition history files to serve as an auditable record 

of GFM transactions. In addition, the MCA shall generate reports as required by DoD 4140.1-R, 

“DoD Supply Chain Materiel Management Regulation”, May 23, 2003.

C11.5.4. Under emergency conditions, such as a potential contract work stoppage, the 

MCA may receive telephonic requisitions (PDs 01-08) for GFM. When this occurs, the MCA 
MILSTRIP Manual, Chapter 11

ADC 1014, Enclosure 3, Page 4

may telephone the requisitions to the appropriate source of supply and validate the requirements 

afterward. If the post validation process reveals that the requisitioner is not authorized GFM, the 

following actions shall be taken:

C11.5.4.1. Submit cancellation requests to the appropriate source of supply.

C11.5.4.2. Advise the appropriate criminal-investigating agency for determination of 

fraud waste, and abuse.

C11.5.5. Upon completion of the validation process, the MCA shall make the following 

changes and forward the requisitions, or internal requisition transactions (optional only when the 

MCA and source of supply are collocated in the same distribution system), cancellations, followups, modifiers, passing orders, or referral orders to the applicable source of supply through 

DAAS, if practical:

C11.5.5.1. Insert the RIC of the source of supply in rp 4-6.

C11.5.5.2. Insert the distribution code of the MCA validating the transaction in rp 54 

or the MDN consisting of the MCAs distribution code in rp 54 and two other alpha/numeric 

characters in rp 55-56.

C11.5.5.3. Delete the data in rp 69-80.

C11.5.5.4. If required by the S/A, insert the RIC of the validating MCA in rp 74-76 

of the requisition. The MCA RIC shall be in rp 74-76 of the passing order or referral order.

C11.5.6. MCAs in receipt of DIC AX1 transactions (Appendix AP3.52) shall validate the 

data contained therein. This validation process must be completed and a DIC AX2 transaction 

created and forwarded to the applicable source of supply within 15 days of receipt of the DIC 

AX1 transaction. The format for the DIC AX2 transaction is contained in Appendix AP3.53. 

The DIC AX1 shall be validated as follows:

C11.5.6.1. If the requisition has been previously validated, the DIC AX2 transaction 

shall contain Advice Code 2M.

C11.5.6.2. If the requisition has not been previously validated and the call order 

number/PIIN (or MDN, if required by the Component in addition to the call order 

number/PIIN)) is not present, the DIC AX2 transaction shall contain Advice Code 2U.

C11.5.6.3. If the requisition has not been previously validated and the call order 

number/PIIN (or MDN) is present, validate the data elements as indicated in Table C11.T1, and 

generate the DIC AX2 transaction as follows:

C11.5.6.3.1. If the validation process reveals that the contract is not valid, the 

DIC AX2 shall contain Advice Code 2U.
MILSTRIP Manual, Chapter 11

ADC 1014, Enclosure 3, Page 5

C11.5.6.3.2. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, the DIC AX2 shall contain Advice Code 2R and the 

quantity that can be supplied shall be entered in rp 25-29.

C11.5.6.3.3. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, DIC AX2 shall contain Advice Code 2Q.

C11.5.6.3.4. If the validation process reveals that the requested item, or 

requisitioner, or DoDAAC in rp 45-50, is not authorized GFM under a valid contract, the DIC 

AX2 shall contain Advice Code 2V.

C11.5.6.3.5. If the validation process reveals that the requested item is 

authorized, the DIC AX2 shall contain Advice Code 2M.

C11.5.7. MCAs in receipt of DIC AE_ transactions with Status Code BF shall review for 

establishment of a valid requisition. If a valid requisition exists, a DIC AT_ transaction shall be 

generated. If a valid requisition does not exist, a report shall be generated for internal review. 

Subsequent receipt of a valid requisition shall be processed under the procedures/validation 

process indicated in Table C11.T1.

Table C11.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

Document Identifier Code If DIC is A01, A02, A04, A05, A0A, A0B, A0D, A0E, AT_, A3_, A4_, or 

AM_ (for RDD, project code PD, or advice code), continue the GFM 

validation.

Stock Number Verify item requisitioned against a valid contract to determine authority for 

issue to the contractor. If blank, incorrect, or not authorized, reject with 

Status Code DN.

Unit of Issue Validate the unit of issue in conjunction with the quantity to ensure that the 

requisitioned quantity does not exceed the authorized quantity. If quantity is 

excessive, see validation of quantity field. (Note: If a change of unit pack 

has occurred, appropriate adjustment should be made for authorized 

quantity.)

Quantity If ordered item is authorized by contract, verify the quantity. If blank or 

invalid, reject with Status Code CD. If the requisitioned quantity exceeds 

the remaining authorized quantity, reject the quantity exceeding the 

authorized quantity with Status Code DJ. If authorized quantity has been 

exhausted by previous requisition(s), reject total requisitioned quantity with 

Status Code DQ.

Requisitioner If blank or incorrect, discard. If not authorized, reject with Status Code DN.

Document Number If blank or incorrect, reject with Status Code CD.

Supplementary Address If contractor DoDAAC, and affected by signal code, and incorrect or not 

authorized, reject with Status Code DN.

Signal and Fund If signal and fund codes indicate issues without contractor reimbursement, 

process as GFM; otherwise, consider as CFM. CFM requisitions, except for 

Army, are not subject to MCA review. All Army contractor requisitions and 

associated transactions shall be processed under GFM controls. DAAS shall 
MILSTRIP Manual, Chapter 11

ADC 1014, Enclosure 3, Page 6

Table C11.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

respond to requests for MCA review for Army CFM under special 

processing rules authorized by the Army.

Manufacturer’s Directive 

Number

The MDN may be used in rp 54-56 in lieu of the PIIN in rp 73-80. If the 

MDN option is used required by the Component and the MDN equates to a 

valid contract number, validate; otherwise, reject with Status Code DB.

Contract Call Order Number If specified by S/A contract, and entry is blank or incorrect, reject with 

Status Code DB.

Last eight positions of the 

Procurement Instrument 

Identification Number

If blank, or contract is not on MCA file, or contract has expired, reject with 

Status Code DB. (If not using the MDN option, rp 54-56, then The last eight 

positions of the PIIN are mandatory.)

-------------------------------

C11.10.2. The ICP/IMM shall prepare materiel release orders for stock shipment using 

document numbers based upon a DLA-established DoDAAC. The ship-to location cited in the 

release order shall identify the contractor DoDAAC authorized to receive GFM. If no DoDAAC 

is assigned, the contractor facility may be identified by contractor and Government entity 

(CAGE) code or as an exception ship-to address. The storage activity shall provide shipment 

confirmation to the ICP/IMM for monitoring GFM shipments and shall prepare shipment status. 

For contractors without capability to accept legacy 80 record position/DLMS transactions, status 

of the GFM component delivery shall be provided upon request by the contractor. The 

assembled/manufactured end items may be shipped directly to customers or shipped to a storage 

location for future use.
MILSTRIP Manual Appendix 1.1

ADC 1014, Enclosure 4, Page 1

Enclosure 4, MILSTRIP Manual Appendix 1.1 Revision

AP1.1.6.6.2. The Issue Release/Receipt Document data elements, configuration and 

locations are as follows:

DATA ELEMENT NAME LENGTH RECORD POSITION(S)

Document Identification Code 3 1-3

Routing Identifier Code (From) 3 4-6

Media and Status 1 7

Unit of Issue 2 23-24

Quantity 5 25-29

Service 1 45

Supplementary Address 5 46-50

Signal 1 51

Fund 2 52-53

Distribution 3 54-56

Project 3 57-59

Priority 2 60-61

Required Delivery Date 3 62-64

Advice 2 65-66

Routing Identifier 3 67-69

Ownership/Purpose 1 70

Condition 1 71

Management 1 72

1 73

Unit Price9 7 74-80

BLOCK ELEMENT NAME

BLOCK SIZE/

NO. OF CHARACTERS

BLOCK 

NUMBER

 9

Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size shall reflect the 

unit price as 9 digits for dollars and 2 digits for cents. Refer to ADC 221. 
MILSTRIP Manual Appendix 1.1

ADC 1014, Enclosure 4, Page 2

BLOCK ELEMENT NAME

BLOCK SIZE/

NO. OF CHARACTERS

BLOCK 

NUMBER

Total Price 1210 1

Ship-From 10 2

Ship-To 9 3

Mark-For 19 4

Doc Date 5 5

NMFC 9 6

Freight Rate 8 7

Type Cargo 10 8

Physical Security 4 9

Quantity 7 10

Unit Pack 3 11

Unit Weight 10 12

Unit Cube 7 13

UFC 6 14

Shelf Life 3 15

Freight Classification Nomenclature 36 16

Item Nomenclature 36 17

Type Container 5 18

No. of Containers 8 19

Total Weight 13 20

Total Cube 10 21

Received By 26 22

Date Received 10 23

Document Number and Suffix (30-

44) 44 24

National Stock Number and 

Additional (8-22) 44 25

RIC (4-6) UI (23-24) QTY (25-29) 

COND Code (71) Dist (55-56) UP 

80

 10Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size shall reflect 

the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on 

the printed form, the generating application may leave blank. Refer to ADC 221. 
MILSTRIP Manual Appendix 1.1

ADC 1014, Enclosure 4, Page 3

BLOCK ELEMENT NAME

BLOCK SIZE/

NO. OF CHARACTERS

BLOCK 

NUMBER

(74-80)11 26

Additional Data Variable 27

For shipments of GFP, include the 

GFP contract number (and call 

order number when provided). This 

includes shipments from DOD to 

contractors and contractor shipment 

of GFP to DOD activities. The 

contract number shall be prefaced 

by “GFP” to clarify the usage.

For IUID to support UIT/ serialized 

item management, include the 

following:12

Unique Item Identifier and/or Serial 

Number

The following additional data 

elements may be included in support 

of IUID:

Manufacturer’s CAGE, Current Part 

Number, Batch/Lot

Clear text labeling of IUID 

information must be provided using 

the following acronyms: CAGE, P/N, 

BT/LT, S/N, and UII.

Field size and characteristics of item unique 

identification data content and specific policy guidance 

is available at: 

http://www.acq.osd.mil/dpap/pdi/uid/index.html

 11 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size shall reflect 

the unit price as 9 digits for dollars and 2 digits for cents. Refer to ADC 221. 12 Capability to support IUID data content within the 2D symbol has been approved for staggered and phased 

implementation under ADC 44B. Components have not reported implementation at this time.
MILSTRIP Manual Appendix 3.2

ADC 1014, Enclosure 5, Page 1

Enclosure 5, MILSTRIP Manual Appendix 3.2

AP3.2. APPENDIX 3.2

REQUISITION

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Send to Block A13 Not Applicable Enter the appropriate in-the-clear 

name and address corresponding to 

the RIC, if applicable.

Requisition Is From Block B Not Applicable Enter the appropriate in-the-clear 

name and address of the requisitioner, 

if applicable.

Document Identifier 

Code

Block 1 1-3 Enter DIC A0_ or AM_.

Routing Identifier 

Code

Block 2 4-6 Enter RIC indicating the source of 

supply to which the document is being 

submitted.

Media and Status Block 3 7 Enter the M&S code.

Stock Number14 Blocks 4, 5, 6 8-22 Enter the stock or part number of the 

item being requisitioned. For 

subsistence items, enter the type of 

pack in rp 21.

Unit of Issue Block 7 23-24 Enter the unit of issue.

 13 See the AP2 series of appendices for an explanation of the data fields.

14 Requisitions to DLA Disposition Services (RIC S9D) cannot reflect an entry in rp 21-22..
MILSTRIP Manual Appendix 3.2

ADC 1014, Enclosure 5, Page 2

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Quantity Block 8 25-29 Enter the quantity requisitioned. For 

ammunition and ammunition related 

requisitions only (items in Federal 

supply group (FSG) 13 and for 

Federal supply classification (FSC) 

1410, 1420, 1427, 1440, 5330, 5865, 

6810 or 8140), enter an M in rp 29 to 

express in thousands any quantity 

exceeding 99,999. Example: A 

quantity of 1,950,000 will be 

expressed as 1950M (1950 in rp 25-28 

and an M in rp 29).

Document Number Blocks 9-12 30-43 Enter document number as assigned 

by the preparing activity.

Demand15 Block 13 44 Enter the demand code; otherwise, 

leave blank.

Supplementary 

Address

Blocks 14-15 45-50 When applicable, enter the coded 

SUPADD of the ship-to or bill-to 

activity; otherwise, leave blank. 

When coded data is not significant to 

the source of supply (other than an 

activity address code (AAC)), enter an 

alphabetic Y in rp 45.

Signal Block 16 51 Enter the signal code.

Fund Block 17 52-53 Enter the fund code as directed by the 

Component.

Distribution Block 18 54 When applicable, enter the 

distribution code of the activity to 

receive status information in addition 

to the requisitioner or the SUPADD.

55-56 Enter the code as directed by the 

Components.

Project Block 19 57-59 When applicable, enter the 

appropriate project code under 

Component instructions.

 15 On an Intra-Army basis a suffix code entry is authorized for identification of post-post partial issues of materiel by 

Army Single Stock Fund Activities. These requisitions will contain Army Edit Action Code IV in rp 74-75.
MILSTRIP Manual Appendix 3.2

ADC 1014, Enclosure 5, Page 3

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Priority Block 20 60-61 Enter priority designator.

Required Delivery 

Date/Required 

Delivery Period16

Block 21 62-64 Enter data requirements from AP2.14, 

as applicable; otherwise, leave blank.

Advice Block 22 65-66 Enter advice code to convey 

instructions to the source of supply; 

otherwise, leave blank.

Date of Receipt of 

Requisition17,18,19

Block 23 67-69 Leave blank.

Blank Block 23 70-80 Leave blank on inter-Component 

requisitions forwarded to the DLA 

and Government Services 

Administration (GSA) sources of 

supply.

a. This field is optional for intraComponent use.20, 21, 22, 23, 24, 25,26

b. This field may be used for internal 

purposes on retained copies of 

requisitions.

 16 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL 148.

17 Processing Points passing DIC AM_ transactions to another source of supply for continued processing will enter 

their RIC in rp 67-69. 18 The DLA Distribution Mapping System (DDMS) will enter the DDMS RIC SD7 in A0_ transactions returned to 

Mapping Enterprise Business System (MEBS)(HM8) for processing. This will indicate to MEBS that this is not 

the initial processing of the requisition (requisition was previously reviewed and forwarded to DDMS, which 

was unable to fulfill).

19 On Intra-Army basis a RIC entry is authorized for identification of the storage site related to post-post issues of 

materiel by Army Single Stock Fund Activities. These post-post requisitions will contain Army Edit Action 

Code IV in rp 74-75. 20 On Intra-Army requisitions rp 70 will contain the ownership/purpose code and rp 71 will contain the supply 

condition code of the materiel post-post issued by Army Single Stock Fund Activities. These post-post requisitions 

will contain Army Edit Action Code IV in rp 74-75. 21 On Intra-Army basis both post-post and image Single Stock Fund Activity requisitions may contain a 

management code in rp 72 to facilitate processing.

22 On Intra-Army basis requisitions may contain an Army Edit Action Code in rp 74-75 to indicate the actions 

required by the receiving system in order to process transactions and direct authorized follow-on actions. This 

code is meaningful to the Army only and is used on both post-post and image requisitions. 23 On Intra-Army basis requisitions may contain the date generated in rp 77-80. This date is required to accurately 

process transactions relative to image, post-post and working requisitions submitted by Army Single Stock Fund 

activities.
MILSTRIP Manual Appendix 3.2

ADC 1014, Enclosure 5, Page 4

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES.

27

Manufacturer’s 

Directive Number

54-56 If required by the Component 

contracts, enter the MDN.

Contract Call Order 

Number

69-72 If required by the Component 

contracts, enter the appropriate 

contract call order number.

Contract Identification 73-80 At the option of the Component, Enter 

the last eight positions of the 

procurement instrument identification 

number (PIIN) in rp 73-80 in lieu of 

the MDN in rp 54-56. This entry is 

mandatory28 if the MDN is not 

entered in rp 54-56.

MANAGEMENT CONTROL ACTIVITY ENTRIES. Entries Required for Requisitions for 

Government-Furnished Materiel.29

Routing Identifier 

Code

4-6 Enter the RIC of the source of supply.

Distribution 54-56 Enter the distribution code of the 

Management Control Activity (MCA) 

validating the transaction or the MDN 

consisting of the MCA’s distribution 

code in rp 54 and two other 

alpha/numeric characters in rp 55-56.

Routing Identifier 

Code

74-76 If required by the Component, enter 

the RIC of the validating MCA in rp 

74-76.

 24 For intra-Air Force lateral requisitions, the source of supply identified in rp 4-6 is another Air Force base, the RIC 

of the requisitioner is identified in rp 73-75, and the RIC of the DoD source of supply is identified in rp 78-80. 

Refer to ADC 266. 25 For intra-Air Force requisition modification, the unit price may be identified in rp 71-80. Refer to ADC 263. 26 For intra-Navy organic maintenance requisitions (citing Project Code Z5X), used to identify the storage activity 

from which the requisitioned item is requested in rp 74-76. 27 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.

28 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014. 29 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.
MILSTRIP Manual Appendix 3.2

ADC 1014, Enclosure 5, Page 5

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

DLA DISPOSITION SERVICES ENTRIES. Entries Required When Requisitioning a Specific Item 

From Disposal.30

Disposal Turn-in 

Document Number 

67-80 This entry is optional on DIC 

A01/A0A/A05/A0E requisitions and 

is mandatory on DIC A04/A0D 

requisitions. If applicable, the DTID 

suffix will be entered in rp 21.

DLA DISPOSITION SERVICES ENTRIES. Entries Required on Requisitions to Disposal When a 

Specific Item is Not Required.31

Blank 70 Leave blank.

Condition Code 71 Enter lowest acceptable supply 

condition code under Component 

criteria furnished to DLA Disposition 

Services. See Chapter C2, Paragraph 

C2.21., for requirement.

Blank 72-80 Leave blank.

 30 Procedures, formats, and codes for requisitioning materiel from disposal last reported as not implemented by 

DLA. Refer to AMCL 139A.

31 Ibid.
MILSTRIP Manual Appendix 3.23

ADC 1014, Enclosure 6, Page 1

Enclosure 6, MILSTRIP Manual Appendix 3.23

AP3.23. APPENDIX 3.23

PASSING ORDER1

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier Code 1-3 Enter DIC A3_.

Routing Identifier Code 4-6 Enter the RIC of the activity to which the 

document is being passed.

All Fields 7-66 Enter data as shown in the requisition.

Date of Receipt of Demand 67-69 Leave blank on submission. Processing points 

shall enter date of receipt when received from 

another distribution system.

Blank 70-71 Leave blank.

Cooperative Logistics Program 

Support Code

72 Enter data as shown in the requisition, if 

applicable.

Blank 73 Leave blank.

Routing Identifier Code 74-76 Enter the RIC of the activity from which the 

document is being passed.

Blank 77-80 Leave blank.

GOVERNMENT-FURNISHED MATERIEL PASSING ORDER ENTRIES.

2

Manufacturer’s 

Directive Number

54-56 If required by the Component contracts, enter 

the MDN.

Contract Call Order 

Number

69-72 If required by the Component contracts, enter 

the appropriate contract call order number.

Contract Identification 73-80 Enter the last eight positions of the 

procurement instrument identification 

number (PIIN). This entry is mandatory.3

 1 Entries from the remarks field shall be made only when it is necessary to report that data when it is 

entered on the requisition. In all such instances, rp 3 of the DIC shall identify the document as containing 

exception data and the passing order shall not be transceived.

2 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.

3 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.
MILSTRIP Manual Appendix 3.23

ADC 1014, Enclosure 6, Page 2

MANAGEMENT CONTROL ACTIVITY ENTRIES. Entries Required for passing orders for 

Government-Furnished Materiel.4

Routing Identifier 

Code

4-6 Enter the RIC of the source of supply.

Distribution 54-56 Enter the distribution code of the 

Management Control Activity (MCA) 

validating the transaction or the MDN 

consisting of the MCA’s distribution code in 

rp 54 and two other alpha/numeric 

characters in rp 55-56.

Routing Identifier 

Code

74-76 If required by the Component, enter the RIC 

of the validating MCA in rp 74-76.

 4 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.
MILSTRIP Manual Appendix 3.24

ADC 1014, Enclosure 7, Page 1

Enclosure 7, MILSTRIP Manual Appendix 3.24

AP3.24. APPENDIX 3.24

REFERRAL ORDER/LATERAL REDISTRIBUTION 

ORDER FOR RETAIL ASSETS

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier Code 1-3 Enter DIC A4_.

Routing Identifier Code 4-6 Enter the RIC of the source of supply to which 

the transaction is being sent.

Media and Status 7 Enter the M&S code as shown in the original 

requisition.

Stock or Part Number 8-22 a. When no change or substitution is made, 

enter the stock or part number shown in the 

requisition.

b. When a change or substitution is made, enter 

the corrected stock or substituted stock or part 

number.

Unit of Issue 23-24 Enter U/I.

Quantity 25-29 a. Enter the quantity.

b. For ammunition and ammunition related 

items only (items in Federal supply group 

(FSG) 13 and for Federal supply classification 

(FSC) 1410, 1420, 1427, 1440, 5330, 5865, 

6810 or 8140), enter an M in rp 29 to express in 

thousands any quantity exceeding 99,999. 

Example: Express a quantity of 1,950,000 as 

1950M (1950 in rp 25-28 and an M in rp 29).

Document Number 30-43 Enter document number as shown in the 

requisition.

Suffix 44 a. Enter the suffix code applicable to quantity 

in rp 25-29 when the requisitioned quantity is 

divided into separate actions.

b. When the requisitioned quantity is not 

divided, leave this field blank.

Supplementary Address 45-50 Enter data from the original requisition.
MILSTRIP Manual Appendix 3.24

ADC 1014, Enclosure 7, Page 2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Signal 51 Enter data from the original requisition.

Fund 52-53 Enter data from the original requisition.

Distribution 54-56 When used to effect lateral redistribution of 

retail assets, enter 2 for consumables and 3 for 

reparables in rp 54; otherwise, enter data from 

the original requisition.

Project 57-59 Enter data from the original requisition.

Priority 60-61 Enter data from the original requisition.

Required Delivery Date/Required 

Delivery Period1

62-64 Enter data from the original requisition.

Advice 65-66 Enter data from the original requisition.

Date of Receipt of Demand 67-69 Enter the date of receipt of the demand 

document as recorded in that document by the 

initial recipient in the supply distribution 

system. Note: Referral orders generated as a 

result of backorder releases and submitted to 

the (Single Manager for Conventional 

Ammunition) SMCA shall contain code 888 in 

rp 67-69.

Management Data 70-71 Enter management data, as authorized. 

Demand Code/ 2

Management Data3

72 Enter demand code from rp 44 of original 

requisition or management data, as authorized. 

Note: Intra-Air Force Foreign Military Service 

(FMS) DIC A4_ transactions may use a 

Cooperative Logistics Program Support Code

(CLPSC) (program/non-program) code in rp 

72.

Management Data 73 Enter Management data, as authorized.

Routing Identifier Code 74-76 Enter RIC applicable to the activity generating 

the transaction.

Management Data 77-80 Enter management data, as authorized.

 1 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL 148. 2 Deferred implementation authorized. The revised format of the referral order to include the demand code of the 

original requisition may be deferred for DLMS/logistics systems modernization. 3 On an Intra-Navy basis, a management code may be used to identify the reason a requisition is referred to the Navy 

Inventory Control Point (ICP) when the requisition cannot be filled by the referring system. Refer to ADC 363.
MILSTRIP Manual Appendix 3.24

ADC 1014, Enclosure 7, Page 3

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

LATERAL REDISTRIBUTION ORDER ENTRIES: Entries applicable when rp 54 equals 2 or 3:

Purpose code 70 Enter the purpose code of the materiel being 

issued if required based on Component 

agreement (derived from DIC DZF, Asset 

Status Reporting Transaction); otherwise leave 

blank.

Condition Code 71 Enter the applicable condition code.

Blank 72-73 Leave Blank.

GOVERNMENT-FURNISHED MATERIEL REFERRAL ORDER ENTRIES.

4

Manufacturer’s 

Directive Number

54-56 If required by the Component contracts, enter 

the MDN.

Contract Call Order 

Number

69-72 If required by the Component contracts, enter 

the appropriate contract call order number.

Contract Identification 73-80 Enter the last eight positions of the 

procurement instrument identification 

number (PIIN). This entry is mandatory.5

MANAGEMENT CONTROL ACTIVITY ENTRIES. Entries Required for referral orders for 

Government-Furnished Materiel.6

Routing Identifier 

Code

4-6 Enter the RIC of the source of supply.

Distribution 54-56 Enter the distribution code of the Management 

Control Activity (MCA) validating the 

transaction or the MDN consisting of the 

MCA’s distribution code in rp 54 and two 

other alpha/numeric characters in rp 55-56.

Routing Identifier 

Code

74-76 If required by the Component, enter the RIC of 

the validating MCA in rp 74-76.

 4 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.

5 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.

6 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.
MILSTRIP Manual Appendix 3.48

ADC 1014, Enclosure 8, Page 1

Enclosure 8, MILSTRIP Manual Appendix 3.48

AP3.48. APPENDIX 3.48

MATERIEL RELEASE DOCUMENT

DD FORM 1348-1A OR DD FORM 1348-2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier Code 1-342 Perpetuate from requisition or source 

document unless otherwise indicated.

Routing Identifier Code

(From)

4-643 Enter the RIC of the shipping activity.

Media and Status 7 Enter the M&S code assigned to the 

requisition or source document.

Stock or Part Number 8-22 Indicate the NSN or part number being 

released. See Block 25.

Unit of Issue 23-24 Indicate the U/I of the NSN or part number 

being released.

Quantity 25-29 Indicate the quantity being released. See 

Block 26.

Document Number 30-43 Enter the document number of requisition. 

See Block 24.

Suffix Code 44 Leave blank if the document represents 

release of the total quantity requisitioned. 

Indicate the appropriate suffix code assigned 

to indicate a partial quantity release. See 

Block 24.

Supplementary Address 45-5044 Perpetuate from the original requisition or 

source document. See Block 26.

Signal 5145 Perpetuate from the original requisition or 

source document.

 42 Procedures, formats, and codes for requisitioning material from disposal last reported as not implemented by 

DLA. Refer to AMCL 139A.

43 Ibid. 44 Ibid. 45 Ibid.
MILSTRIP Manual Appendix 3.48

ADC 1014, Enclosure 8, Page 2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Fund 52-5346 Perpetuate from the original requisition or 

source document.

Distribution 54-5647 Perpetuate from the original requisition or 

source document.

Project 57-5948 Perpetuate from the original requisition or 

source document.

Priority 60-6149 Perpetuate from the original requisition or 

source document.

Required 62-6450 Perpetuate from the original requisition or 

source document.

Advice 65-6651 Perpetuate from the original requisition or 

source document.

Routing Identifier Code 67-6952 Perpetuate from the original requisition or 

source document.

Management 70-73 Perpetuate from the original requisition or 

source document.

Unit Price53 74-80 Indicate the unit price of item being released. 

See Block 26.

 46 Ibid. 47 Ibid. 48 Ibid. 49 Ibid. 50 Ibid. 51 Ibid. 52 Ibid. 53 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect 

the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on 

the printed form, the generating application may leave blank. Refer to ADC 221.
MILSTRIP Manual Appendix 3.48

ADC 1014, Enclosure 8, Page 3

BLOCK(S) ENTRIES

1 Total price (10 digits dollars and 2 digits cents).54

2 Department of Defense Activity Address Code (DoDAAC) of shipping activity/DLA 

Disposition Services Field Office. If reduced print in used, in-the-clear address may 

be entered in addition to the DoDAAC.

3 DoDAAC of the activity to receive the shipment, if applicable. If reduced print is 

used, in-the-clear address may be entered in addition to the DoDAAC.

4 DoDAAC of the MARK FOR recipient, if applicable. If reduced print is used, in-theclear address may be entered in addition to the DoDAAC.

5 Document preparation date (enter numerical day of year).

6 National motor freight classification commodity code.

7 Freight rate for the shipment.

8 Type of cargo code (See DTR 4500.9-R “Defense Transportation Regulation)

9 Enter applicable controlled inventory item code (CIIC) that describes the classified 

and/or sensitive or pilferage classification of the shipment from DoD 4100.39-M 

(FLIS Procedures Manual), Volume 10, Chapter 4, Table 61. (Mandatory Entry)55

10 Actual quantity received.

11 Unit pack of item shipped.

12 Unit weight of item shipped.

13 Unit cube of item shipped.

14 Uniform freight classification (UFC) commodity code.

15 Shelf life of item shipped. Enter SL (for shelf life) followed by applicable shelf-life 

code from DoD 4100.39-M (FLIS Procedures Manual) Volume 10, Chapter 4, Table 

50. (Mandatory Entry)56

16 Freight classification nomenclature.

17 Item nomenclature.

18 Type of container used for the shipment.

19 Number of containers that make up the shipment.

20 Total weight of all containers that make up the shipment.

21 Total cube of all containers that make up the shipment.

 54 Ibid.

55 Mandatory requirement to enter the controlled inventory item code (CIIC) and shelf-life code on the DD Form 

1348-1A for issues from stock last reported as not implemented by USN. Refer to AMCL 32. 56 Ibid.
MILSTRIP Manual Appendix 3.48

ADC 1014, Enclosure 8, Page 4

BLOCK(S) ENTRIES

22 Received by, signature of receiver, or call sign/code of individual authorized access to 

the automated file.

23 Date received, date shipment was received.

24 Document Number - The document number assigned to the requisition.57

Suffix Code - Blank if the document represents release of the total quantity 

requisitioned. If partial shipment, the appropriate suffix code assigned to indicate 

partial quantity released.

25 National Stock Number - Enter the stock or part number being released.

Add - For subsistence items, enter the type of pack code in position 21.

FOR OTHER THAN FMS SHIPMENTS

26 Routing Identifier Code - The RIC code of the shipping activity.

Unit of Issue - The unit of issue of the stock or part number being released.

Quantity - The quantity being released.

Condition Code - The supply condition code of materiel being released.

Distribution - Perpetuate from record positions 55 and 56.

Unit Price58 - The unit price for the NSN/part number being released.

27 This block may contain additional data including bar coding for internal use. This 

block may contain a 2D symbol that contains information for serially tracked items 

and repeats bar coded data content. Data entered in this block is as required by 

shipping activity by commodity. When data is entered in this block, it will be clearly 

identified. 

For shipments of GFP, include the GFP contract number (and call order number 

when provided). This includes shipments from DOD to contractors and contractor 

shipment of GFP to DOD activities. The contract number shall be prefaced by 

“GFP” to clarify the usage.

See Appendix 1.35 for Code 39 linear bar code and PDF417 2D symbol format 

information. See Appendix 1.36 for the Block 27 continuation page requirements.

DTID - On issues from DLA Disposition Services Field Office, enter Disposal TurnIn Document (DTID).59

 57 Prepare data from blocks 24-26 in two configurations: (1) three-of-nine bar code and (2) in-the-clear. When 

prepared manually, do not include bar code. 58 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect 

the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on 

the printed form, the generating application may leave blank. Refer to ADC 221.. 59 Procedures, formats, and codes for requisitioning material from disposal last reported as not implemented by 

DLA. Refer to AMCL 139A.
MILSTRIP Manual Appendix 3.48

ADC 1014, Enclosure 8, Page 5

BLOCK(S) ENTRIES

27 

(Continued)

For Issues of DLA Disposition Services-owned property :

Warehouse/Shipping Instructions:

Exception Shipping Address: If the ship to address is an exception address, 

print the exception address (up to five lines).

Special Shipping Instructions: Print any special shipping instructions. Some 

examples of shipping instructions can include:

Do not ship. Customer will arrange for transportation.

Do not ship property. Contact customer for transportation instructions.

Contact customer to obtain transportation fund cite and TAC.

Fax this 1348 and shipping document to [insert point of contact].

Fund Citation: Print line of accounting in a single text field.

Foreign Military Sales Proceeds Information: For FMS shipments, print “FMS 

PROCEEDS”.

Type of Property Being Shipped: Indicate if the property is either “Hazardous 

Property” or a “Small Arms Issue”.

Other Instructions:

Instructions for Return of Unneeded Property: Print applicable instructions if 

customer is required to return material to DLA Disposition Services, when 

they no longer require the property and/or it requires demilitarization.

USML Items - This block will contain clear-text information to identify shipments of 

USML items which may require filing of export licenses and shipper export 

declarations (SED) per 22CFR126.4 and 22CFR123.22 as follows: “USML item—

may need SED.”

For IUID to support UIT/serialized item management60:

Unique Item Identifier (UII) and/or Serial Number

The following additional data elements may be included in support of IUID:

Manufacturer’s contractor and Government entity (CAGE)

Current Part Number (PN)

Batch/Lot (BT/LT) 

Clear text labeling of IUID information must be provided using the 

following acronyms: CAGE, P/N, BT/LT, S/N, and UII.

 60 Capability to support IUID data content within the 2D symbol has been approved for staggered and phased 

implementation under ADC 44B. Components have not reported implementation at this time.
MILSTRIP Manual Appendix 3.48

ADC 1014, Enclosure 8, Page 6

BLOCK(S) ENTRIES

FOR FMS SHIPMENTS61

26 Unit of Issue - two positions - the unit of issue of the stock or part number being 

released.

Quantity - five positions - the quantity being released.

Condition - one position - the supply condition code of materiel being released.

Unit Price62 - the unit price for the NSN/part number being released.

Supplementary Address - the first position and last three positions of the 

supplementary address.

27 This block may contain additional data including bar coding for internal use. This 

block may contain a 2D symbol which contains information for serially tracked items 

and repeats bar coded data content. Data entered in this block is as required by 

shipping activity by commodity. When data is entered in this block, it will be clearly 

identified. See Appendix 1.35 for Code 39 linear bar code and PDF417 2D symbol 

format information. See Appendix 1.36 for the Block 27 continuation page 

requirements.

USML Items – This block will contain clear-text information to identify shipments of 

United States Munitions List (USML) items which may require filing of export 

licenses and Shipper Export Declarations (SED) per 22CFR126.4 and 22CFR123.22 

as follows: “USML item—may need SED.

For IUID to support UIT/serialized item management63:

Unique Item Identifier (UII) and/or Serial Number (S/N)

The following additional data elements may be included in support of IUID:

Manufacturer’s CAGE

Current Part Number

Batch/Lot

Clear text labeling of IUID information must be provided using the following 

acronyms: CAGE, P/N, BT/LT, S/N, and UII.

 61 Requirement to add bar-coded Foreign Military Sales data to the Issue Release/Receipt Document last reported as 

not implemented by United States Marine Corp (USMC). Refer to AMCL 8.

62 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect 

the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on 

the printed form, the generating application may leave blank. Refer to ADC 221.

63 Ibid.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 1

Enclosure 9, DLMS Supplement Revisions

a. Revise DLMS 511R as follows:

Item # Location 511R, Requisition 

Revision

Reason

1. DLMS

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract Data in 

Transactions Associated with Government Furnished Property 

(GFP) and Management Control Activity (MCA) Validation of 

Contractor Furnished Materiel (CFM) Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/GF/070 Revise Segment Level DLMS note:

DLMS Notes: Use either the Manufacturing Directive Number 

(MDN) or contract number (but not both) to identify the 

procurement source from which the commercial contractor is 

authorized to requisition materiel from DOD inventories. 

1. Must use to provide contract information applicable to the 

procurement source under which the contractor is authorized to 

receive GFP. 

2. May be used to provide contract information applicable to the 

procurement source under which the contractor is authorized to 

purchase from a Government source when directed by the 

authorizing Service/Agency under CFM procedures.

Clarifies usage as applicable 

to both GFP and CFM in 

requisitions, passing orders, 

and referral orders. This is 

consistent with current usage 

for Army CFM requisitions, 

but was not identified 

previously in the DLMS 

notes. 

Removes the MDN as an 

alternate to the contract 

number.

3. 2GF01/70 Revise DLMS Note to C7 and Add DLMS Note to W3: 

C7 Contract Line Item Number

DLMS Note:

1. Use to associate a Contract Line Item Number with the 

Contract Number.

2. Use with GF03 in CAV transactions to associate a Contract Line 

Item Number with the Contract Number or as directed by the 

authorizing Service/Agency.

W3 Manufacturing Directive Number

DLMS Note:

1. Use to identify the MDN, in addition to the contract number. 

2. Use as directed by the authorizing Service/Agency. Refer to 

ADC 1014.

Clarifies that the CLIN may 

be directed for use by the 

Service/Agency authorizing 

GFP.

Requirement for MDN was 

revised to be more specific.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 2

Item # Location 511R, Requisition 

Revision

Reason

4. 2/GF03/70 Add DLMS note:

Contract Number

DLMS Note: 

1. Must use to identify the contract number for GFP.

2. Use as directed by the authorizing Service/Agency to identify 

the contract number authorizing the contractor to purchase 

materiel from a Government source. 

3. Fully compliant DLMS applications must support 

identification of the DFARS contract number, rather than the 

abridged contract number authorized for legacy MILSTRIP. 

Refer to ADC 1014.

Clarification.

Specifically identifies the 

discontinued use of the 

abbreviated form of the 

contract number

5. 2/GF07/70 Add DLMS Note:

Release Number

Federal Note: Use to identify the call or order number, or the call 

or order number including the respective call or order 

modification, as applicable, when using GF03.

DLMS Note: Use as directed by the authorizing Service/Agency. 

Clarification.

b. Revise DS 511M as follows:

Item # Location 511M, Requisition Modification 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract Data 

in Transactions Associated with Government Furnished Property 

(GFP) and Management Control Activity (MCA) Validation of 

Contractor Furnished Materiel (CFM) Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/GF/070 Revise Segment Level DLMS note:

DLMS Notes: Use either the Manufacturing Directive Number 

(MDN) or contract number (but not both) to identify the 

procurement source from which the commercial contractor is 

authorized to requisition materiel from DOD inventories.

1. Must use to provide contract information applicable to the 

procurement source under which the contractor is authorized to 

receive GFP. 

2. May be used provide contract information applicable to the 

procurement source under which the contractor is authorized to 

purchase from a Government source when directed by the 

authorizing Service/Agency under CFM procedures.

Clarifies usage as applicable 

to both GFP and CFM. This 

is consistent with current 

usage for Army CFM 

requisitions, but was not 

identified previously in the 

DLMS notes. 

Removes the MDN as an 

alternate to the contract 

number.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 3

Item # Location 511M, Requisition Modification 

Revision

Reason

3. 2/GF01/70 Revise DLMS Note to C7 and Add DLMS Note to W3: 

C7 Contract Line Item Number

DLMS Note:

1. Use to associate a Contract Line Item Number with the 

Contract Number.

2. Use with GF03 in CAV transactions to associate a Contract

Line Item Number with the Contract Number or as directed by the 

authorizing Service/Agency.

W3 Manufacturing Directive Number

DLMS Note:

1. Use to identify the MDN, in addition to the contract number. 

2. Use as directed by the authorizing Service/Agency. Refer to 

ADC 1014.

Clarifies that the CLIN may 

be directed for use by the 

Service/Agency authorizing 

GFP.

Requirement for MDN was 

revised to be more specific

4. 2/GF03/70 Add DLMS note:

Contract Number

DLMS Note: 

1. Must use to identify the contract number for GFP.

2. Use as directed by the authorizing Service/Agency to identify 

the contract number authorizing the contractor to purchase 

materiel from a Government source. 

3. Fully compliant DLMS applications must support 

identification of the DFARS contract number, rather than the 

abridged contract number authorized for legacy MILSTRIP. 

Refer to ADC 1014.

Clarification.

5. 2/GF07/70

Release Number

Federal Note: Use to identify the call or order number, or the call 

or order number including the respective call or order 

modification, as applicable, when using GF03.

DLMS Note: Use as directed by the authorizing Service/Agency. 

Clarification.

c. Revise DLMS 517G as follows:

Item # Location 517G, Government Furnished Materiel (GFM) Validation 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract Data 

in Transactions Associated with Government Furnished Property 

(GFP) and Management Control Activity (MCA) Validation of 

Contractor Furnished Materiel (CFM) Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 4

Item # Location 517G, Government Furnished Materiel (GFM) Validation 

Revision

Reason

2. 2/GF/060 Revise Segment Level DLMS note:

DLMS Notes: Use either the Manufacturing Directive Number 

(MDN) or contract number (but not both) to identify the 

procurement source from which the commercial contractor is 

authorized to requisition materiel from DOD inventories.

DLMS Note:

1. Must use to provide contract information applicable to the 

procurement source under which the contractor is authorized to 

receive GFP. 

2. May be used to provide contract information applicable to 

the procurement source under which the contractor is 

authorized to purchase from a Government source when 

directed by the authorizing Service/Agency under CFM 

procedures.

Clarifies usage as applicable 

to both GFP and CFM. This 

is consistent with current 

usage for Army CFM 

requisitions, but was not 

identified previously in the 

DLMS notes. 

Removes the MDN as an 

alternate to the contract 

number.

3. 2/GF01/60 Add Code C7 with DLMS Note and Add DLMS Note to W3: 

C7 Contract Line Item Number

DLMS Note:

1. Use to associate a Contract Line Item Number with the 

Contract Number.

2. Use with GF03 in CAV transactions to associate a Contract 

Line Item Number with the Contract Number or as directed by 

the authorizing Service/Agency.

W3 Manufacturing Directive Number

DLMS Note:

1. Use to identify the MDN, in addition to the contract number. 

2. Use as directed by the authorizing Service/Agency. Refer to 

ADC 1014.

Clarifies that the CLIN may 

be directed for use by the 

Service/Agency authorizing 

GFP.

Requirement for MDN was 

revised to be more specific

4. 2/GF03/60 Add DLMS note:

Contract Number

DLMS Note: 

1. Must use to identify the contract number for GFP.

2. Use as directed by the authorizing Service to identify the 

contract number authorizing the contractor to purchase 

materiel from a Government source of supply. 

3. Fully compliant DLMS applications must support 

identification of the DFARS contract number, rather than the 

abridged contract number authorized for legacy MILSTRIP. 

Refer to ADC 1014.

Clarification of required input 

under this DLMS Change.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 5

Item # Location 517G, Government Furnished Materiel (GFM) Validation 

Revision

Reason

5. 2/GF07/60 Add DLMS note:

Release Number

Federal Note: Use to identify the call or order number, or the call 

or order number including the respective call or order 

modification, as applicable, when using GF03.

DLMS Note: Use as directed by the authorizing 

Service/Agency. 

Clarification.

d. Revise DLMS 856S as follows:

Item # Location 856S, Shipment Status 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract 

Data in Transactions Associated with Government Furnished 

Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) 

Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/REF04-01/ 

1500

Revise Data Element DLMS notes:

2. Use one of codes CT (Contract Number) or W3

(Manufacturing Directive Number) to identify the procurement 

document which authorized the commercial contractor to 

receive/obtain/requisition property from DoD inventories. Use 

with document number (REF01

Code TN). 

3. For CAV shipment status, must use to identify the 

procurement document which authorized the commercial 

contractor to repair and ship Government Furnished Materiel

GFP into to DoD inventories. Use with contractor-assigned 

shipment number (REF01 Code SI).

3. Under ADC 1014, GFP contract data is transitioned 

from the REF segment to the GF Segment. Delayed 

implementation is authorized. 

The contract number for GFP 

shipments to the contractor is remapped to the GF Segment. 

The originally planned mapping 

at REF04-01 following the 

document number in REF01 

would not support split 

shipments requiring the 

identification of the Suffix Code 

in REF04-01.

Mapping for CAV is already 

implemented and must be 

transitioned to the GF Segment.

Staffing Note to the Navy: If 

acceptable, the CAV mapping to 

the REF Segment will be 

removed concurrent with 

documentation of the ADC. 

DLA Transaction Services 

would then map this information 

to the GF Segment without 

altering the CAV user defined 

file format.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 6

Item # Location 856S, Shipment Status 

Revision

Reason

3. 2/REF04-01/ 

1500

Revise DLMS notes associated with Qualifier CT. Delete 

Qualifier W3 and associated notes.

CT – Contract Number

1. Use on shipments of GFM GFP to the contractor.

2. Must use for CAV shipment status, to identify the contract 

number authorizing repair/return of GFP.

2. Under ADC 1014, GFP contract information is 

transitioned from the REF segment to the GF Segment. 

Delayed implementation is authorized. 

3. Authorized DLMS enhancement; see introductory DLMS 

2a.

W3 Manufacturing Directive Number

DLMS Note:

1. Use on shipments of GFM to the contractor.

2. DLMS enhancement; see introductory DLMS 2a.

Establishes transition plan for 

mapping for the GFP contract 

information to the GF Segment.

4. 2/REF04-03/ 

1500

Revise DLMS Notes:

OQ Order Number

DLMS Note:

1. Must use for CAV shipment status Use with contract 

number (REF04-01 Code CT) to identify the call or order 

number, or the call or order number including the respective 

call or order modification associated with the applicable 

contract.

2. Must use for CAV shipment status. Under ADC 1014, GFP 

contract information is transitioned from the REF segment to 

the GF Segment. Delayed implementation is authorized. 

3. Authorized DLMS enhancement; see introductory DLMS 2a.

Clarification.

5. 2/REF04-05/ 

1500

Revise DLMS Notes:

C7 Contract Line Item Number

DLMS Note:

1. Must use for CAV shipment status Use with contract 

number (REF04-01 code CT) to identify the application 

CLIN/SubCLIN.

2. Must use for CAV shipment status. Under ADC 1014, GFP 

contract information is transitioned from the REF segment to 

the GF Segment. Delayed implementation is authorized. 

3. Authorized DLMS enhancement.

Clarification.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 7

Item # Location 856S, Shipment Status 

Revision

Reason

6. 2/GF/3300 Mark GF as used and add segment Level DLMS notes:

DLMS Note:

1. Must use in GFP-related transactions. 

2. Use to provide contract information for shipments of GFP 

to the contractor.

3. Use for contractor shipment of GFP into DoD inventory. 

4. Authorized DLMS enhancement. Refer to ADC 1014.

Inclusion of the contract number 

on the DLMS shipment status 

will require perpetuation from 

the materiel release order when 

shipment status is prepared by 

the distribution depot for 

shipments of requisitioned GFP, 

pushed GFP without a 

requisition, and shipments of 

reparables to a commercial 

maintenance activity. 

Applicable to ICP-prepared 

shipment status for direct vendor 

delivery shipments of GFP.

Applicable to shipment status 

prepared from a DD 1149.

Applicable for CAV shipments 

of reparables into DoD 

inventory.

7. 2GF01/3300 Mark GF01 as used and add Qualifier C7 and DLMS note: 

C7 Contract Line Item Number

DLMS Note:

1. Use as directed to associate a Contract Line Item Number 

with the Contract Number.

Staffing Note: If a requirement 

is identified to perpetuate the 

MDN, it would be mapped to 

the GF01-02. At this time, no 

requirement has been identified.

8. 2GF02/3300 Mark GF02 as used Opens GF02 for the CLIN 

value.

9. 2/GF03/3300 Mark GF03 as used and add a DLMS note:

Contract Number 

DLMS Note: Must use to identify the applicable contract 

number. 

The GF Segment is optional. 

When the GF Segment is used, 

then the GF03 contact number 

must be used for X12 syntax .

10. 2/GF07/3300 Mark GF07 as used and add a DLMS note:

Release Number

DLMS Note: 

Use to identify the call or order number, or the call or order 

number including the respective call or order modification, as 

applicable. 

DPAP identified a requirement 

for use of call or order number 

in addition to the contract 

number which authorized GFM.

e. Revise DLMS 856R as follows:

Item # Location 856R, Shipment Status Materiel Returns

Revision

Reason
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 8

Item # Location 856R, Shipment Status Materiel Returns

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract 

Data in Transactions Associated with Government Furnished 

Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) 

Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/GF/3300 Mark GF as used and add DLMS notes:

DLMS Note:

1. Must use in GFP-related transactions. 

2. Use as directed by the authorizing Service/Agency to 

provide contract information for shipments of GFP directed 

returns/retrograde. 

3. Authorized DLMS enhancement. Refer to ADC 1014.

Supplements procedures 

associated with ADC 353A 

(Reference 3.J.)

3. 2GF01/3300 Mark GF01 as used and add Qualifier C7 and DLMS note: 

C7 Contract Line Item Number

DLMS Note:

1. Use as directed to associate a Contract Line Item Number 

with the Contract Number.

4. 2GF02/3300 Mark GF02 as used Opens GF02 for the CLIN value.

5. 2/GF03/3300 Mark GF03 as used and add a DLMS note: 

Contract Number 

DLMS Note: Must use to identify the applicable contract 

number. 

The GF Segment is optional. 

When the GF Segment is used, 

then the GF03 contact number 

must be used.

6. 2/GF07/3300 Mark GF07 as used and add a DLMS note:

Release Number

DLMS Note: 

Use to identify the call or order number, or the call or order 

number including the respective call or order modification, 

as applicable. 
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 9

f. Revise DLMS 867I as follows:

Item # Location DLMS 867I Issue

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract 

Data in Transactions Associated with Government Furnished 

Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) 

Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/REF01/30 Modify DLMS Note 1 for Qualifier CT – Contract Number 

CT Contract Number

DLMS Note:

1. Use for government furnished materiel (GFM) issues to 

identify the contract number from which the contractor is 

authorized to requisition materiel from DoD inventories. Do 

not use if a manufacturing directive number is provided.

2. DLMS enhancement; see introductory DLMS note 5a.

1. Must use in GFP-related transactions. 

2. Use to provide contract information for shipments of 

GFP to the contractor.

3. Use for issue of contractor shipments of GFP into DoD 

inventory. 

4. Authorized DLMS enhancement. Refer to ADC 1014.

The REF segment is used 

because the GF Segment is not 

available in this transaction.

3. 2/REF01/30 Delete Qualifier W3 and associated DLMS note.

W3 Manufacturing Directive Number

DLMS Note: Use on shipments of GFM to the contractor.

Removes MDN. 

4. 2/REF04-01/ 

30

Revise DLMS notes:

OQ Order Number

DLMS Note:

1. Use as directed by the authorizing Service/Agency in 

GFP-related transactions with REF01 Code CT to identify 

the call or order number including the respective call or 

order modification associated with the applicable contract.

2. Authorized DLMS enhancement. Refer to ADC 1014.

Supports enhanced visibility of 

contract data. 

5. 2/ REF04-03/ 

30

Add DLMS Qualifier C7 and DLMS Note:

C7 Contract Line Item Number

DLMS Note:

1. Use as directed by the authorizing Service/Agency in 

GFP-related transactions to associate a Contract Line Item 

Number with the Contract Number.

2. Authorized DLMS enhancement; Refer to ADC 1014

Supports enhanced visibility of 

contract data. 
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 10

g. Revise DLMS 869C as follows:

Item # Location 869C Requisition Cancellation

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract 

Data in Transactions Associated with Government Furnished 

Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) 

Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/GF/100 Revise DLMS note 2: 

DLMS Note

Use either the Manufacturing Directive Number (MDN) or 

contract number (but not both) to identify the procurement 

source from which the commercial contractor is authorized to 

requisition materiel from DoD inventories. 

1. Must use to provide contract information applicable to the 

procurement source under which the contractor is 

authorized to receive GFP. 

2. May be used to provide contract information applicable 

to the procurement source under which the contractor is 

authorized to purchase from a Government source when 

directed by the authorizing Service/Agency under CFM 

procedures.

Clarifies the use of the contract 

number for GFP and MDN,

removing the option to use 

either one or the other. Updates 

for consistency with the 511R.

3. 2/GF01/100 Add DLMS note:

W3 Manufacturing Directive Number

DLMS Note: 

1. Use to identify the MDN, in addition to the contract 

number. 

2. Use as directed by the authorizing Service/Agency. Refer 

to ADC 1014.

Clarification.

4. 2/GF07/100 Revise Federal note:

Release Number

Federal Note: 

Use to identify the call or order number when using GF03, or 

the call or order number including the respective call or 

order modification, as applicable, when using GF03. 

DPAP identified a requirement 

for use of call or order number 

in addition to the contract 

number which authorized GFM.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 11

h. Revise DLMS 869F as follows:

Item # Location 869F Requisition Follow-up

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract 

Data in Transactions Associated with Government Furnished 

Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) 

Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/GF/100 Revise DLMS note: 

DLMS Note

Use either the Manufacturing Directive Number (MDN) or 

contract number (but not both) to identify the procurement 

source from which the commercial contractor is authorized to 

requisition materiel from DoD inventories. 

1. Must use to provide contract information applicable to the 

procurement source under which the contractor is 

authorized to receive GFP. 

2. May be used to provide contract information applicable 

to the procurement source under which the contractor is 

authorized to purchase from a Government source when 

directed by the authorizing Service/Agency under CFM 

procedures.

Clarifies the use of the contract 

number for GFP and MDN, 

removing the option to use 

either one or the other. Updates 

for consistency with the 511R 

(since the requisition follow-up 

may be used by the source of 

supply as new requisition).

3. 2/GF01/100 Add DLMS note:

W3 Manufacturing Directive Number

DLMS Note: 

1. Use to identify the MDN, in addition to the contract 

number. 

2. Use as directed by the authorizing Service/Agency. Refer 

to ADC 1014.

Clarification.

i. Revise DLMS 870S as follows:

Item # Location 870S Supply Status 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract Data in 

Transactions Associated with Government Furnished Property (GFP) 

and Management Control Activity (MCA) Validation of Contractor 

Furnished Materiel (CFM) Requisitions

Identifies DLMS 

Changes included in the 

DLMS Supplement
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 12

Item # Location 870S Supply Status 

Revision

Reason

2. 2/REF04-01/ 

87

Delete DLMS note: 

DLMS Note: Use one of codes CT or W3 to identify the procurement 

document from which authorizes the commercial contractor is to 

requisition materiel from DOD inventories. Use with REF01 code TN.

Removes planned 

DLMS enhancement to 

carry the GFP contract 

information in the 

Supply Status. 

In response to the 

original proposal, the 

Services/ Agencies did 

not identify a 

requirement for the

source of supply to 

perpetuate GFP contract 

data to the supply 

status.

3. 2/REF04-01/ 

87

Delete DLMS note for CT, Contract Number

CT Contract Number

DLMS Note:

Use in GFM transactions

Same as above.

4. 2/REF04-01/ 

87

Delete qualifier and DLMS note

W3 Manufacturing Directive Number

DLMS Note:

Use in GFM transactions to identify the Manufacturing Directive 

Number (MDN) associated with the contract.

Same as above.

j. Revise DLMS 940R as follows:

Item # Location DLMS 940R Materiel Release

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1014 to DLMS Introductory notes:

- ADC 1014, Revised Procedures for Inclusion of Contract 

Data in Transactions Associated with Government Furnished 

Property (GFP) and Management Control Activity (MCA) 

Validation of Contractor Furnished Materiel (CFM) 

Requisitions

Identifies DLMS Changes 

included in the DLMS 

Supplement

2. 2/N901/0400 Delete Data Element level DLMS Note 1:

DLMS Note: 

1. In government furnished materiel (GFM) transactions, use 

one of codes CT or W3, but not both.

2. For DLMS use, only the following codes are authorized.

Removes note that is no longer 

valid.
DLMS Supplement Revisions

ADC 1014, Enclosure 9, Page 13

Item # Location DLMS 940R Materiel Release

Revision

Reason

3. 2/N901/0400 Modify DLMS Note 1 for Qualifier CT – Contract Number 

CT Contract Number

DLMS Note:

1. Use on shipments of Government Furnished Materiel

(GFM) to the contractor.

2. DLMS enhancement; see introductory DLMS note 4a.

1. Must use in GFP-related transactions. 

2. Use to provide contract information for shipments of 

GFP to the contractor.

3. Use for directed release of contractor shipments of GFP 

into DoD inventory. 

4. Authorized DLMS enhancement. Refer to ADC 1014.

Inclusion of the contract 

number on the DLMS materiel 

release order will require 

perpetuation from the 

requisition for requisitioned 

GFP. Also required for GFP 

pushed to contractors without a 

prior requisition.

The N9 segment is used 

because the GF Segment is not 

available in this transaction.

4. 2/N901/0400 Delete Qualifier W3 and associated DLMS note.

W3 Manufacturing Directive Number

DLMS Note: Use on shipments of GFM to the contractor.

Removes MDN. 

Staffing Note. This change 

requires confirmation that there 

is no requirement for the MDN 

on the MRO. To date no 

requirement has been identified.

5. 2/N907-01/ 

0400

Revise DLMS notes:

OQ Order Number

DLMS Note:

1. Use in GFM GFP-related transactions with N901 code CT 

to identify the call or order number including the respective 

call or order modification associated with the applicable 

contract.

2. Authorized DLMS enhancement; see introductory DLMS 

note 4a.

Revised for more consistent 

terminology. 

6. 2/N907-03/ 

0400

Add DLMS Qualifier C7 and DLMS Note:

C7 Contract Line Item Number

DLMS Note:

1. Use as directed by the authorizing Service/Agency to 

associate a Contract Line Item Number with the Contract 

Number.

2. Authorized DLMS enhancement; Refer to ADC 1014

Allows for perpetuation of the 

CLIN when provided.
Comment Resolution

ADC 1014, Enclosure 10, Page 1

Enclosure 10, Comment Resolution

Originator Response/Comment Disposition

1. DLA DLA concurs without comment, but reserve right to provide 

comment from DLA Distribution on using the point-to-point userdefined file (UDF) interface via the Customer Information Control 

System (CICS). 

Noted.

2. Army Army concurs with ADC 1014; however, the changes to the DLMS 

transactions (511R, 511M, 517G, 869C, 869F, 856R, 856S, and 

940R) specified in this PDC impact GCSS-Army design. The 

recommended changes in this PDC impact the Wave 2 design as it 

applies to GCSS-Army contracting functionality, we estimate the 

functionality will be included GCSS-Army Release Wave II 

4QFY14.

Noted.

3. Marine Corps Concurs with comment; current Marine Corps legacy systems do 

not have the capability to add the contracting number to the 

restricted 80 CC MILSTRIP format. Incorporation of this 

requirement will be levied in a future block of Global Combat 

Support System-Marine Corps (GCSS-MC).

Noted.

4. Navy The Navy has reviewed this PDC and submits the following 

comments.

1. Recommend that this PDC address a major business problem by 

requiring that DLA Distribution Standard Systems print the 

contract number and order, CLIN, sub-CLIN when available from 

the DLMS 940R on the DD1348-1A produced both from a desktop 

and a wireless RF picking solution. Currently, Navy resorts to 

using the exception form for MROs DIC A5E to provide contract 

number. This results in both inefficiencies on the DLA side and 

problems for Navy when that exception data is not actually printed 

out by DLA.

2. The Navy uses a DLMS 867I (D7M) transaction, which is not 

covered by this PDC, for retrograde of Not Ready For Issue 

repairable items directly to a commercial repair vendor. The Navy 

also uses some of its commercial repair vendors as stock point for

both NRFI, in advance of anticipated delivery orders for an existing 

long term vehicle and Ready For Issue. Therefore, there will be 

instances where only a contract number is known at the time of the 

retrograde.

3. Recommend that DLMS 527D is also included in this PDC.

4. Navy will assess the feasibility for remapping of GFP data within 

1.ADC updated to 

include printing 

requirement.

2. Mapping provided 

for the GFP contract 

information. 

3. The DLMS 527D, 

Prepositioned Materiel 

Receipt (PMR)

includes the contract 

number for new 

procurement items. 

There is no identified 

requirement for 

including the GFP 
Comment Resolution

ADC 1014, Enclosure 10, Page 2

Originator Response/Comment Disposition

the DLMS 856S supporting Commercial Asset Visibility (CAV), to 

meet the agreed upon implementation dates.

5. The Navy recognizes the importance of transiting to mandatory 

inclusion of the 13-postion contract number on DLMS requisitions 

and MCA validation transactions beginning JUN 2012, which will 

be enforced by DLA Transaction Services edit beginning JAN 1, 

2013. As well as, the staggered implementation of GFP contract 

data on the DLMS MRO and shipment status beginning JAN 1, 

2013, and completed by DEC 31, 2013. 

contract information in 

a PMR.

4. Noted.

5. Noted.

5. Air Force The Air Force concurs with comments. ECSS is unable to provide 

an estimated implementation date due to the lack of execution 

progress on ECSS Pilot C as we continue to experience schedule 

setbacks. Execution performance metrics, monitored and reviewed 

by Air

Force senior leaders on a weekly basis, now reflect a four-to-six 

month delay to ECSS Pilot C completion and go-live. The Air 

Force is considering other options to the program for approval by 

the OSD Milestone Decision

Authority. Until a final decision is made, an implementation date 

cannot be provided.

Noted

6. DPAP DFARS reference 5452.242-9002 is invalid. Anything in the 

procurement regulations that begins 54xx is actually a DLA 

Directive, not the DFARS.

Corrected.

7. USTRANSCOM Abstain. Noted.