*DLM 4000.25, Volume 2, August 03, 2023*

*Change 16*

**C26. CHAPTER 26**

**CONTRACTOR ACCESS TO GOVERNMENT SOURCES OF SUPPLY**

C26.1.  GENERAL

	C26.1.1.  Purpose.  This chapter prescribes policies and procedures for requisitioning government furnished materiel (GFM) by or for contractors from the DoD Supply System.  These procedures establish guidelines for requisitioners, authorized contractors, and Services/Agencies (S/As) to obtain GFM from DoD inventories to fulfill contract requirements.[footnoteRef:1]  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.  Basic MILSTRIP requisitioning procedures are documented in DLM 4000.25, Volume 2, Chapter 4; those procedures are augmented by this chapter to identify additional requirements associated with GFM and CFM. [1:  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.] 

	C26.1.2.  Transactions.  This chapter addresses the procedures and applicable transactions relevant to requisitioning GFM and CFM.  See the Defense Enterprise Data Standards Office Website for available formats on the DLMS IC page.  The corresponding MILSTRIP legacy 80 record position transaction functionality is also provided for ease of interpretation by DLMS users and to support those working in a legacy environment.  In addition to the listed MILSTRIP legacy transactions, the DLMS formats may incorporate functionality to support Component-unique transactions as noted in the implementation convention.

		C26.1.2.1.  The Requisition Transaction is identified by the DLMS 511R by beginning segment (1/BR02/020 Code A0).  This transaction provides the functionality of MILSTRIP legacy Document Identifier Codes (DIC) A01, A02, A04, A05, A0A, A0B, A0D, and A0E.

		C26.1.2.2.  The Passing Order Transaction is identified by the DLMS 511R by beginning segment (1/BR02/020 Code BM).  This transaction provides the functionality of MILSTRIP legacy DIC A31, A32, A34, A35, A3A, A3B, A3D, and A3E.

		C26.1.2.3.  The Referral Order Transaction is identified by the DLMS 511R by beginning segment (1/BR02/020 Code BN).  This transaction provides the functionality of MILSTRIP legacy DIC A41, A42, A44, A45, A4A, A4B, A4D, and A4E.

		C26.1.2.4.  The Requisition Modification Transaction is identified by the DLMS 511M by beginning segment (1/BR02/020 Code AM).  This transaction provides the functionality of MILSTRIP legacy DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and AME.

		C26.1.2.5.  The Requisition Follow-Up Transaction is identified by the DLMS 869F by beginning segment (1/BSI08/020 Code IN).  This transaction provides the functionality of MILSTRIP legacy DIC AT1, AT2, AT4, AT5, ATA, ATB, ATD, and ATE.

		C26.1.2.6.  The Requisition Inquiry is identified by the DLMS 869A by beginning segment (1/BSI08/020 Code AF).  This transaction provides the functionality of MILSTRIP legacy DIC AF1, AF2, AF3, AF4, AF5, AFC, AFY).

		C26.1.2.7.  The Requisition Supply Assistance Request is identified by the DLMS 869A by beginning segment (1/BSI08/020 Code AR).  There is no equivalent MILSTRIP legacy DIC.

		C26.1.2.8.  The MCA Validation Request is identified by the DLMS 517G by beginning segment (1/BR02/20 Code GI).  This transaction provides the functionality of MILSTRIP legacy DIC AX1.

		C26.1.2.9.  The MCA Validation Response is identified by the DLMS 517G by beginning segment (1/BR02/20 Code GA).  This transaction provides the functionality of MILSTRIP legacy DIC AX2.

		C26.1.2.10.  The Supply Status Transaction is identified by the DLMS 870S by beginning segment (1/BSR01/020 Code 4).  This transaction provides the functionality of MILSTRIP legacy DIC AE1, AE2, AE3, AE8, AE9, AEA, AEB, AED, and AEE.  

		C26.1.2.11.  The Requisition Cancellation Transactions is identified by the DLMS 869C by beginning segment (1/BSI08/020 Code AC).  This transaction provides the functionality of MILSTRIP legacy DIC AC1, AC2, AC3, AC4, AC5.

		C26.1.2.12.  The Follow-Up on Requisition Cancellation Request Transactions is identified by the DLMS 869C by beginning segment (1/BSI08/020 Code AC).  This transaction provides the functionality of MILSTRIP legacy DIC AK1, AK2, AK3, AK4, AK5.

		C26.1.2.13.  The Shipment Status Transaction is identified by the DLMS 856S by beginning segment (1/BSN06/0200 Code AS).  This transaction provides the functionality of MILSTRIP legacy DIC AS1, AS2, AS3, AS8, AU1, AU2, AU3, and AU8.

		C26.1.2.14.  The Materiel Obligation Validation Request Transaction is identified by the DLMS 517M by beginning segment (1/BR02/20 Code AN).  This transaction provides the functionality of MILSTRIP legacy DIC AN1, AN2, AN3, AN4, AN5, AN9, and ANZ.

		C26.1.2.15.  The Materiel Obligation Validation Response Transaction is identified by the DLMS 517M by beginning segment (1/BR02/20 Code AP).  This transaction provides the functionality of MILSTRIP legacy DIC AP1, AP2, AP3, AP4, AP5, AP8, AP9, APR, and APX.

		C26.1.2.16.  The Post-Post Requisition/Referral Order Transaction identified by the DLMS 511R by beginning segment (1/BR02/020 Code A0 or BM) with Action Code J.  This transaction provides the functionality of legacy DIC C0A, C01, CQA, CQ1, or comparable Component-unique DIC.

		C26.1.2.17.  The Requisition/Referral Order Image Transaction identified by the DLMS 511R by beginning segment (1/BR02/020 Code A0 or BM) with Action Code FI.  This transaction provides the functionality of legacy DIC CHA, CH1, or comparable Component-unique DIC.

	C26.1.3.  Establishing a Management Control Activity.  The S/As must assign a unique routing identifier code (RIC) and distribution code to each management control activity (MCA) validating GFM and CFM requisitions.

	C26.1.4.  Violations.  Any attempt to circumvent MCA validation requirements is sufficient cause to refer the violation to the appropriate criminal investigating activity to determine possible fraud, waste, and abuse.  The sponsoring Service/Agency must refer all violations to criminal investigators and the monitoring MCA based on reports of rejected transactions or violations discovered during the post validation process.

C26.2.  APPLICABILITY

	C26.2.1.  These procedures apply to all contractors and all S/A activities requisitioning GFM or CFM from DoD sources of supply. 

	C26.2.2.  Ammunition production is excluded from GFM control.

C26.3.  PREPARATION OF REQUISITIONS AND RELATED TRANSACTIONS FOR GOVERNMENT MATERIEL FURNISHED TO CONTRACTORS

	C26.3.1.  Requisition Initiation.  Requisitions for GFM may be initiated by the responsible S/A or, subject to the terms of the contract, by contractors.  Requisitions for GFM will be prepared and initially submitted by GFM requisitioners, both contractors and S/As, using MILSTRIP transaction formats to the S/A MCA designated for monitoring the contract.  Transmission through the Defense Automatic Addressing System (DAAS) will be utilized to the extent practical.

	C26.3.2.  Identifying Requisitions for GFM Controls.  Requisitions and associated transactions containing an S/A code designated for contractors, as specified in Appendix AP7.2 (Department of Defense activity address code (DoDAAC) in the document number or ship-to DoDAAC), will be processed under GFM 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.

	C26.3.3.  Required Information.  In addition to normal requisition data, GFM requisitions, including Referral and Passing Orders will contain the following:

		C26.3.3.1.  RlC of the MCA monitoring the contract, (2/N101/***180*** Code Z5) (MILSTRIP legacy rp 4-6).

		C26.3.3.2.  For contractor generated requisitions, contractor DoDAAC in first six positions of document number. Document number DoDAAC perpetuated to the ordered by activity (1/N101/70 Code OB) (MILSTRIP legacy rp 30-35).

		C26.3.3.3.  For S/A generated requisitions for GFM, contractor ship-to DoDAAC (2/N101/***180*** Code ST) which may also be perpetuated to the supplementary address (2/LQ01/140 Code A9) based upon signal code usage (MILSTRIP legacy rp 45-50).

		C26.3.3.4.  When applicable, a signal code to indicate issue without reimbursement, (2/LQ01/140 Code DE) (MILSTRIP legacy rp 51).

		C26.3.3.5.  When applicable, a fund code to indicate issue without reimbursement, (2/FA201/286 Code B5) (MILSTRIP legacy rp 52-53).

		C26.3.3.6.  Contract Information.  All GFM requisitions for or by contractors must identify the procurement instrument identifier (PIID)[footnoteRef:2] 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 PIID.[footnoteRef:3] [2:  Use the legacy PIIN pending transition to the PIID.  Refer to ADC 1161A.]  [3:  Refer to ADC 1014.  Staggered implementation is authorized for the transition to the mandatory inclusion of the PIID (rather than MDN as an alternative to the PIID).] 

			C26.3.3.6.1.  Identification of the PIID in 2/GF03/70.  When GFM is authorized under a PIID call/order number (F in 9th position), provide the value in the PIID field.  In MILSTRIP legacy, the last eight positions of the PIID are mandatory in rp 73-80.[footnoteRef:4] [4:  Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant PIID (rather than the abbreviated contract number authorized under legacy MILSTRIP procedures).] 

			C26.3.3.6.2.  When applicable, provide the legacy call/order number associated with the PIIN in 2/GF07/70, (MILSTRIP legacy rp 69-72).  Leave blank when the call/order number is the PIID with ‘F’ in the 9th position.

			C26.3.3.6.3.  Identification of the contract line item number, (2/GF01/70 Code C7).  There is no MILSTRIP legacy equivalent for the contract line item number. 

			C26.3.3.6.4.  At the option of the S/A, a manufacturing directive number (MDN), (2/GF01/70 Code W3) (MILSTRIP legacy rp 54-56).

		C26.3.3.7.  GFM non-national stock number (NSN) requisitions are identified by the applicable code qualifier at 2/LIN02/100.  In MILSTRIP legacy, they must be identified with an E in rp 68; the legacy call/order number, if appropriate, in rp 69-72; and the last eight positions of the PIID in rp 73-80 (the MDN is optional).

C26.4.  SUBMISSION OF GOVERNMENT FURNISHED MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

	C26.4.1.  Frequency of submitting GFM requisitions is the prerogative of the requisitioner.  GFM requisitions will be submitted, when necessary, to meet contract requirements.

	C26.4.2.  Initiating activities must submit all GFM requisitions (DLMS 511R/MILSTRIP legacy DIC A0_) and associated GFM transactions, regardless of origin (such as contractor or S/A initiated) to the appropriate S/A MCA for validation.

	C26.4.3.  After validating the GFM requisitions, the MCA forwards validated requisitions to the inventory control point (ICP).  The MCA may pass transactions internally when the MCA and ICP are collocated.  The MCA will send the transactions via DAAS when the MCA and ICP are not collocated.  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 GFM (or Army  CFM), the Component providing the procurement/contracting service and the Component requesting the contract will coordinate efforts to ensure 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.

	C26.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 ship-to/bill-to information.  Modifiers are subject to GFM controls and validation procedures.

C26.5.  MANAGEMENT CONTROL ACTIVITY PROCESSING OF GOVERNMENT-FURNISHED MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

	C26.5.1.  The MCA must receive and validate GFM Requisitions, Passing Orders, Referral Orders, Requisition Follow-Ups (DIC AT_), and Requisition Modifiers, based on the criteria furnished by procurement/contracting offices and as indicated in Table C26.T1. The MCA will make changes, reject, or continue the processing action on the GFM transactions.  The MCA may also receive Supply Status, Shipment Status, Materiel Obligation Validation transactions, Requisition Inquiry/Supply Assistance Requests (DICs AF_, Requisition Cancellations, and Follow-Ups on Requisition Cancellation Requests.  All other DLMS transactions and legacy DICs received by the MCA must be rejected with Status Code CR.

	C26.5.2.  The MCA will maintain requisition history files to serve as an auditable record of GFM transactions.  In addition, the MCA will generate reports as required by DoDM 4140.01, “DoD Supply Chain Materiel Management Procedures”, February 10, 2014.

	C26.5.3.  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 (SoS) and validate the requirements afterward.  Additionally, if the requisition is processed as a post-post action and, therefore, bypassed MCA validation prior to order fulfillment, the SoS retains responsibility for ensuring MCA validation is accomplished.  If the post validation process reveals that the requisitioner is not authorized GFM, the following actions must be taken:

		C26.5.3.1.  Submit cancellation requests to the appropriate SoS for any unshipped materiel.

		C26.5.3.2.  Advise the appropriate criminal-investigating agency for determination of fraud waste, and abuse.

	C26.5.4.  Upon completion of the validation process, the MCA will identify itself as the RIC-From organization in the transaction, make the following changes and forward the requisitions, or internal requisition transactions (optional only when the MCA and SoS are collocated in the same system), cancellations, follow-ups, requisition modifiers, passing orders, or referral orders to the applicable SoS through DAAS:

		C26.5.4.1.  Insert the RIC-To of the SoS.

		C26.5.4.2.  Insert the distribution code of the MCA validating the transaction. 

		C26.5.4.3.  Perpetuate all applicable contract data.  Under DLMS, the MCA must include the PIID.  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.[footnoteRef:5] [5:  Refer to ADC 1014.  Staggered implementation is authorized for the transition to the full DFARS compliant PIID (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 PIID] 

		C26.5.4.4.  For MILSTRIP legacy transactions, delete the data in rp 69-80.

	C26.5.5.  MCAs in receipt of MCA Validation Request transactions will validate the data contained therein.  This validation process must be completed and an MCA Validation Response transaction created and forwarded to the applicable SoS within 15 days of receipt of the MCA Validation Request transaction.  The results of the validation will be documented in the MCA Validation Response as follows:

		C26.5.5.1.  If the requisition has been previously validated, cite Advice Code 2M.

		C26.5.5.2.  If the requisition has not been previously validated and the legacy call/order number/PIID (or MDN and/or CLIN, if required by the Component in addition to the legacy call/order number) is not present, cite Advice Code 2U.

		C26.5.5.3.  If the requisition has not been previously validated and the call/order number/PIID is present, validate the data elements as indicated in Table C26.T1, and generate the MCA Validation Response as follows:

			C26.5.5.3.1.  If the validation process reveals that the contract is not valid, respond with Advice Code 2U.

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

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

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

			C26.5.5.3.5.  If the validation process reveals that the requested item is authorized, respond with Advice Code 2M.

	C26.5.6.  MCAs in receipt of Supply Status with Status Code BF from the SoS will review for establishment of a valid requisition.  If a valid requisition exists, a Requisition Follow-Up (MILSTRIP legacy DIC AT_) transaction will be generated.  If a valid requisition does not exist, a report will be generated for internal review.  Subsequent receipt of a valid requisition will be processed under the procedures/validation process indicated in Table C26.T1.

C26.6.  SOURCE OF SUPPLY PROCESSING OF GOVERNMENT-FURNISHED MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

	C26.6.1.  An SoS receiving GFM requisitions, requisition modifiers, passing orders, referral orders, requisition follow-ups, and requisition cancellations, regardless of the method of transmission, will process such transactions under GFM procedures.  A SoS in receipt of GFM requisitions for items not managed by their activities will reject the requisitions with Status Code CH.  The SoS will edit the GFM transactions for the prescribed data elements and codes and correct, continue processing actions, or provide the appropriate reject status.

	C26.6.2.  The SoS will validate all GFM transactions.  The SoS in receipt of requisitions, passing orders, referral orders, requisition modifiers, or requisition follow-ups being treated as requisitions, containing a contractor’s Service/Agency code under Appendix AP7.2, will perform the SoS/MCA validation process.  (The SoS/MCA validation process is not required when an internal requisition transaction is received from a collocated MCA in the same system.  However, the SoS must have safeguards in place to ensure that only internal transactions generated by the collocated MCA are accepted/processed.)

	C26.6.3.  Under emergency conditions, the SoS may receive telephonic requisitions (PD 01-08) from the MCA or requisitioner.  The SoS may process these requisitions for immediate supply action.  Subsequent to taking immediate supply action, the MCA validation process will be performed.  If the MCA Validation Response is not received within 15 days of the MCA Validation Request or the advice code indicates that the transaction is not authorized, refer the incident to the appropriate criminal investigating agency.

	C26.6.4.  The SoS/MCA validation process is as follows:

		C26.6.4.1.  For each GFM requisition or transaction that is treated as a requisition, the SoS will employ one of the following options:

			C26.6.4.1.1.  Create and forward an MCA Validation Request to the MCA identified by RIC or distribution code in the requisitioners transaction.  If the MCA RIC and distribution code are not provided or invalid, reject with Status Code CL.

				C26.6.4.1.1.1.  If the requisitioners transaction contains a distribution code but no MCA RIC, DLMS compliant sources of supply will use a DLMS enhancement to address the MCA Validation Request to DAAS.  DAAS (RIC SGA) will be identified as the RIC-To.

				C26.6.4.1.1.2.  DAAS will convert the Distribution Code to the appropriate RIC (or DoDAAC) for transmission to the MCA.

			C26.6.4.1.2.  Create and forward an MCA Validation Request to DAAS regardless of an MCA RIC or distribution code contained in the requisitioners transaction.  DAAS will perform edits regarding validity of the data. 

			C26.6.4.1.3.  Use a combination of the above options:  one for intra-Component transactions and one for inter-Component transactions.

		C26.6.4.2.  Suspend further supply support action on the requisitioners transaction pending receipt of the MCA Validation Response or until 15 days have elapsed from the date of the MCA Validation Request, whichever occurs first.

		C26.6.4.3.  If the MCA Validation Response is not received and 15 days have elapsed, reject the requisitioners transaction with Status Code DR.

		C26.6.4.4.  Upon receipt of the MCA Validation Response, the SoS will process the suspended transaction using instructions provided by the advice or status code.

			C26.6.4.4.1.  If the Advice Code is 2U, reject with Status Code DB.

			C26.6.4.4.2.  If the Advice Code is 2R, process for the approved quantity indicated in the MCA Validation Response.  Reject the quantity difference between the suspended transaction and the MCA Validation Response with Status Code DJ.

 			C26.6.4.4.3.  If the Advice Code is 2Q, reject with Status Code DQ.

			C26.6.4.4.4.  If the Status Code is CL, reject with Status Code CL.

			C26.6.4.4.5.  If the Advice Code is 2V, reject with Status Code DN.

			C26.6.4.4.6.  If the Advice Code is 2M, process under applicable SoS procedures.

			C26.6.4.4.7.  If neither advice nor status code is provided or is invalid, reject with Status Code DR.

		C26.6.4.5.  If an MCA Validation Response is received and there is a record of the requisition, but an MCA Validation Request has not been submitted, discard the MCA Validation Response and generate an MCA Validation Request to initiate the validation process.

		C26.6.4.6.  If an MCA Validation Response is received and there is no record of the requisition, generate a Supply Status with Status Code BF.

	C26.6.5.  Follow-ups will be processed to determine the current status of previously submitted requisitions or cancellation requests.  Time standards for dispatching status in reply to follow-ups are as indicated in Chapter 4, Paragraph C4.7.20.1.

	C26.6.6.  Requisition/referral order image transactions provided to DAAS for visibility/record history must contain GFM/CFM contract data as applicable.

C26.7.  DEFENSE AUTOMATIC ADDRESSING SYSTEM PROCESSING OF GOVERNMENT-FURNISHED MATERIEL TRANSACTIONS

	C26.7.1.  DAAS will pass all GFM requisitions and related transactions to the identified MCA using the MCA RIC or distribution code provided in the transaction.  If the RIC and the distribution code do not identify an established MCA reject with Status Code CL.

	C26.7.2.  DAAS will pass all MCA Validation Requests to the identified MCA using the MCA RIC or distribution code provided in the transaction.  If the MCA is invalid, generate an MCA Validation Response with Status Code CL to the SoS.  If the MCA Validation Request does not include the MCA RIC, DAAS will populate the MCA RIC (or DoDAAC) based upon the distribution code and forward the transaction accordingly. 

	C26.7.3.  DAAS will pass all MCA Validation Responses to the SoS.

	C26.7.4.  DAAS Special Processing for Army.[footnoteRef:7] [footnoteRef:8] Pending implementation of MCA procedures in Army systems, DAAS will assist the Army by performing the MCA Validation Request/Response 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: [7:  Procedures to control access to DoD material inventories by defense contractors last reported as not implemented by USA (Retail).  Refer to AMCL 1A.]  [8:  DAAS special processing for Army to be terminated upon full implementation of MCA validation. Refer to ADC 1123.] 

		C26.7.4.1.  Process all Army contractor identified requisitions (MILSTRIP legacy DIC A0_) with the below listed first two positions of the DoDAAC in the document number or ship-to 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 SoS with the DAAS RIC SGA or SHA identified as the MCA.

			C26.7.4.1.1.  If the first two positions of the document number or ship-to DoDAAC are CB, pass to RIC A81 (TACOM MCA)

			C26.7.4.1.2.  If the first two positions of the document number or ship-to DoDAAC are CL, pass to RIC A82 (AMCOM MCA).

			C26.7.4.1.3.  If the first two positions of the document number or ship-to DoDAAC are CG, pass to RIC A83 (CECOM MCA).

			C26.7.4.1.4.  If the first two positions of the document number or ship-to DoDAAC are CM, pass to RIC A84 (TACOM MCA)

			C26.7.4.1.5.  If the first two positions of the document number or ship-to DoDAAC area CK, pass to RIC A85 (TACOM MCA).

			C26.7.4.1.6.  If the first two positions of the document number or ship-to DoDAAC are CH, pass to RIC A86 (AMCOM MCA)

		C26.7.4.2.  For Requisition Modification and Requisition Follow-Up transactions containing a valid MCA distribution code as identified below, the DAAS RIC SGA or SHA will be entered into the MCA field and routed to the appropriate SoS.  If a valid MCA is not identified and the transaction contains the entries cited above in the first two positions of the document number or ship-to DoDAAC, 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 SoS with the DAAS RIC SGA or SHA entered into the MCA field.  The following are valid MCA distribution codes:

			C26.7.4.2.1.  I (India) - TACOM MCA

			C26.7.4.2.2.  L (Lima) - AMCOM MCA

			C26.7.4.2.3.  P (Papa) - CECOM MCA

			C26.7.4.2.4.  S (Sierra) - TACOM MCA

			C26.7.4.2.5.  Y (Yankee) - TACOM MCA

			C26.7.4.2.6.  E (Echo) - AMCOM MCA

			C26.7.4.2.7.  8 (Eight) - USACEA MCA 

		C26.7.4.3.  Upon receipt of an MCA Validation Request transaction, an MCA Validation Response transaction will be generated with Status Code 2M and returned to the RIC of the SoS submitting the MCA Validation Request transaction.

C26.8.  CONTRACTOR REQUISITIONS FOR CONTRACTOR-FURNISHED MATERIEL

	C26.8.1.  Requisitions for materiel from a Government SoS for shipment to contractors that identify the contractor as the bill-to activity are subject to MCA controls.  Pending full implementation by Services/Agencies, this requirement must be applied to Army contractor requisitions and may be applied to other Services/Agencies as this functionality is adopted within SoS systems.[footnoteRef:9]  DAAS will 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 designated by the contractor-series DoDAAC.  Pending full implementation of MCA validation for CFM, DoD Components will establish appropriate procedures for oversight of CFM requisitions in accordance with the Federal Acquisition Regulation.  To support staggered implementation of full CFM validation, DoD Components authorizing CFM will advise contractors to construct requisitions using required data content comparable to GFM requisitions.[footnoteRef:10] [9:  Staggered implementation authorized; refer to ADC 1123.]  [10:  CFM requisitions are required to have data content comparable to GFM requisitions by January 1, 2017. Refer to ADC 1123.] 

	C26.8.2.  DAAS Processing of CFM Transactions.  The process described in this paragraph provides mandatory CFM controls for CFM requisitions where the bill-to activity, as identified in the requisition, is an Army contractor and the SoS is DLA.  Upon full implementation of MCA validation for CFM, the following special DAAS processing procedures will be terminated; CFM will be validated in the same manner as GFM.[footnoteRef:11] [11:  Refer to ADC 1123.] 

		C26.8.2.1.  DAAS will maintain a list of Service/Agency 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.  

		C26.8.2.2.  CFM contractor transactions that match the CFM Authorized Materiel Table by DoDAAC, but do not match by NSN or part number will be rejected with Status Code CL; requisitions that match on DoDAAC and NSN/part number will be processed as valid.  

		C26.8.2.3.  DAAS will enter the DAAS RIC SGA or SHA as the validating MCA.  

		C26.8.2.4.  DAAS will perform the MCA Validation Request/Response validation requirement for authorized CFM requisitions that match the CFM Authorized Materiel Table.  

		C26.8.2.5.  DAAS will furnish CFM reports upon request for use by the contracting officer in verifying that quantities ordered are within the contract allowance.

		C26.8.2.6.  Army contractor requisitions that do not match the CFM Authorized Materiel Table will be processed by DAAS under the MCA waiver exception process or passed to the applicable MCA as described in C26.7.4.

		C26.8.2.7.  For DLA CFM, DAAS processing will be as identified in C26.8.3.

		C26.8.2.8.  CFM requisitions for other Service contractors will be passed to the appropriate SoS.[footnoteRef:12]   [12:  Staggered implementation is authorized for Service generation of outgoing requests for MCA validation for CFM. In order to support staggered implementation, Services must be able to respond to incoming requests for MCA validation beginning January 1, 2017. Refer to ADC 1123.] 

		C26.8.2.9.  NSNs listed in the CFM Authorized Materiel Table may be modified over the course of this agreement when the appropriate Army contracting officer provides such authority.  Updates to the authorized list will be collected, consolidated into one Microsoft Excel file by the designated DLA Lead Center point of contact with proof of Army Contracting Officer concurrence and provided to Headquarters DLA Army Performance Based Logistics (PBL) action officer.  DLA will coordinate updates to individual contractor lists with DLA DoD EMall and DAAS on a monthly basis.  To optimize program changes, all additions to Army partnership lists will be made during an agreed-to monthly timeframe between DLA and support entities.

	C26.8.3.  DAAS Processing of DLA CFM Transactions

		C26.8.3.1.  DAAS is required to edit all incoming requisition, requisition modification, and requisition follow-up transactions containing a U-series contractor DoDAAC as the bill-to activity, to ensure the transaction contains a valid DLA MCA. If the transaction does not contain a valid DLA MCA, DAAS will reject the transaction using status code CL.

		C26.8.3.2.  If the transaction contains a valid DLA MCA, DAAS will route/pass the transaction based upon established DAAS rules to the appropriate SoS for further processing. 

C26.9.  PREPARATION OF DOD EMALL REQUISITIONS BY CONTRACTORS.[footnoteRef:13] [13:  Special processing unique to validation of contractor requisitions submitted via DoD EMALL will be terminated upon full implementation of MCA validation.  Staggered implementation authorized.  Refer to ADC 1123.] 

	C26.9.1.  Account Setup.  Authorized contractors may establish DoD EMALL accounts to facilitate materiel requisition submissions.  To register, go to the EMALL site and click on “New User Registration”.  Access to DoD EMALL is 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.  Pending full implementation of MCA validation for CFM, Army Contractors requisitioning from DoD supply sources will be processed under MCA validation controls.

	C26.9.2.  Contractor GFM/CFM Validations.  DoD EMALL will validate that contractors are authorized to purchase materiel from DoD supply sources as a prerequisite for submission of EMALL orders.  

		C26.9.2.1.  DoD EMALL requisitions for GFM will be subjected to prescribed rules for MCA controls within DoD EMALL or within DAAS.  

		C26.9.2.2.  DoD EMALL CFM requisitions indicating corporate credit card method of payment are subject to special processing controls as described in C26.9.3.

		C26.9.2.3.  Additionally, CFM requisitions for Army authorized contractors will be validated to ensure that requisitioned NSNs or DoD managed part numbers are authorized regardless of the method of payment under CFM controls.

	C26.9.3.  Corporate Credit Card Usage.  

		C26.9.3.1.  The DoD EMALL program office will identify to DAAS all contractors authorized access to Government materiel for purchase as CFM using a corporate credit card as the method of payment.  

		C26.9.3.2.  DAAS will 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 MCA Validation Request processing.

	C26.9.4.  Corporate Credit Card CFM Purchases and DAAS Processing.  DoD EMALL requisitions for shipment to contractors using corporate credit card payment are assigned Signal Code B, Fund Code XP, and the ship-to DoDAAC perpetuated to the supplementary address of the DoD EMALL DoDAAC (SC4210).  This configuration identifies a Government DoDAAC as the bill-to activity, thereby triggering DAAS and the DoD Component SoS processing systems to misinterpret such transactions as GFM requisitions.  

		C26.9.4.1.  DAAS will validate these transactions against existing GFM edits and the DoD EMALL CFM Table to determine appropriate action.  

		C26.9.4.2.  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 will reject with Status Code CL.  

		C26.9.4.3.  If an MCA is identified by either a distribution code or a RIC, DAAS will forward the requisition to the SoS.  

			C26.9.4.3.1.  The SoS will submit an MCA Validation Request to DAAS for validation following GFM MCA procedures (including Army CFM).  

			C26.9.4.3.2.  DAAS will recognize the EMALL supplementary address and again employ existing GFM edits and the DoD EMALL CFM Table to take appropriate action.  

			C26.9.4.3.3.  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 DAAS will validate the requisition and respond to the SoS with an MCA Validation Response using Advice Code 2M indicating that the requisition is valid.  The SoS will continue processing.  

			C26.9.4.3.4.  If the contractor DoDAAC is not contained on the DoD EMALL CFM Table, but the requisition contains a valid MCA code, then DAAS will forward the MCA Validation Request to the MCA for validation.  

			C26.9.4.3.5.  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 will provide an MCA Validation Response with Status Code CL indicating that the transaction is invalid.  The SoS will reject the requisition.  

		C26.9.4.4.  For DLA contractor credit card purchases (identified by a DLA-assigned U-series DoDAAC in the document number), DAAS processing rules will be as described in this paragraph, except that the requisition will be validated against the DLA ICP MCA Table.

	C26.9.5.  DoD EMALL Reports.  To support DoD requirements for oversight of materiel sold to contractors, the DoD EMALL program office will provide reports to monitor contractor activity.  For contracts having a maximum total dollar ceiling, a DoD EMALL report will be provided to the contracting officer when the cumulative value of CFM ordered reaches 80 percent of the ceiling.

C26.10.  INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGER-DIRECTED SHIPMENT OF NON-REQUISITIONED GOVERNMENT FURNISHED MATERIEL BASED ON A BILL OF MATERIEL.  

	C26.10.1.  ICP/integrated materiel manager (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 materials/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.

	C26.10.2.  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 will only include stocked raw material/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 will use internal control procedures to monitor consumption of raw material/component parts against the receipt of items awarded by contract.

	C26.10.3.  The ICP/IMM will 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 will identify the contractor DoDAAC authorized to receive GFM.  Under DLMS processing, the Materiel Release Order will include the authorizing PIID[footnoteRef:14], and CLIN, when applicable; this is not applicable to MILSTRIP legacy processing.  When a PIID call/order number (F in 9th position) is used, provide the value in the PIID field.  The storage activity will provide shipment confirmation to the ICP/IMM for monitoring GFM shipments and will prepare shipment status; under DLMS processing, the shipment status will perpetuate applicable contract data.  For contractors without capability to accept legacy 80 record position/DLMS transactions, status of the GFM component delivery will 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. [14:  Use the legacy PIIN pending transition to the PIID.  When using the PIIN, may include the four-position call/order number.  Refer to ADC 1161A.] 

	C26.10.4.  Use of the above business process does not relieve the ICP/IMM from management reporting requirements required by DoDM 4140.01, DoD Supply Chain Materiel Management Procedures.  Materiel Receipt Acknowledgement is required for GFM, including pushed shipments, under MILSTRAP procedures.

	C26.10.5.  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).

C26-17	CHAPTER 26