<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE dita
  PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<dita xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/"
      domains="(topic task)                            (topic concept)                            (topic concept glossentry)                            (topic concept glossgroup)                            (topic reference)                            (topic troubleshooting++task) (topic task)                            (topic abbrev-d)                            a(props deliveryTarget)                            (topic equation-d)                            (topic hazard-d)                            (topic hi-d)                            (topic indexing-d)                            (topic markup-d)                            (topic mathml-d)                            (topic pr-d)                            (topic relmgmt-d)                            (topic sw-d)                            (topic svg-d)                            (topic ui-d)                            (topic ut-d)                            (topic markup-d xml-d)                            (topic task strictTaskbody-c)   "
      ditaarch:DITAArchVersion="1.3">
   <concept id="DFARS_PGI_225.373"
            outputclass="3"
            ditaarch:DITAArchVersion="1.3"
            class="- topic/topic concept/concept ">
      <title class="- topic/title ">
         <ph props="autonumber" class="- topic/ph ">PGI 225.373</ph> Contract administration in support of contingency operations.</title>
      <conbody class="- topic/body  concept/conbody ">
         <p outputclass="List2" class="- topic/p ">(1) In accordance with Joint Publication 1, Doctrine for the Armed Forces of the United States, at http://www.apexnet.org/docs/Joint_Publication_1.pdf, the geographic combatant commander or subordinate joint force commander, through his command authority to exercise operational control, has the authority to exercise control over the assignment of contract administration during contingency operations, consistent with the combat support agency’s established mission functions, responsibilities, and core competencies, for contracts requiring delivery of items or performance within the area of operations.</p>
         <p outputclass="List2" class="- topic/p ">(2) In certain contingency operations, the combatant commander or joint force commander may promulgate theater or joint operations area guidance for contracting that may include establishing—</p>
         <p outputclass="List3" class="- topic/p ">(i) A contracting command and control structure;</p>
         <p outputclass="List3" class="- topic/p ">(ii) Head of contracting activity responsibilities, specific orders, and policies, including local clauses;</p>
         <p outputclass="List3" class="- topic/p ">(iii) Roles and responsibilities of DoD components and supporting agencies in contract formation and execution; and</p>
         <p outputclass="List3" class="- topic/p ">(iv) Procedures and requirements for contract clearance and contract administration of contracts requiring delivery of items and performance within the area of operations.</p>
         <p outputclass="List2" class="- topic/p ">(3) When a combat support agency is tasked by the combatant commander to provide contingency contract administration services in support of contingency operations and such support will be required for a long duration, the combat support agency shall initiate a memorandum of agreement with the combatant commander or joint force commander. This agreement shall clearly delineate the purpose of the support, respective responsibilities of the combat support agency and the joint, lead service, or service contracting activity requesting the support, combat support agency support parameters, and a resolution process for resolving support issues.</p>
         <p outputclass="List3" class="- topic/p ">(i) The memorandum of agreement should focus on maximizing the combat support agency’s core competencies to address the more critical, complex, high-risk, and specialized oversight requirements.</p>
         <p outputclass="List3" class="- topic/p ">(ii) The memorandum of agreement should take into consideration the combat support agency’s core competencies, workload priorities, and contract administration services support parameters for accepting requests for contract administration services support.</p>
         <p outputclass="List3" class="- topic/p ">(iii) A combat support agency shall not be assigned to perform tasks outside its mission functions, responsibilities, or core competencies.</p>
         <p outputclass="List3" class="- topic/p ">(iv) Contracting officers contemplating requesting contract administration support in a contingency area from a combat support agency should first ascertain whether such a memorandum of agreement exists by contacting their combat support agency point of contact and/or checking the combatant commander operational contract support website (referenced in DFARS PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_225.370"
                  href="PGI_225.370.dita#DFARS_PGI_225.370"
                  xtrc="225.370">225.370</xref>
            ).</p>
         <p outputclass="List3" class="- topic/p ">(v) The following is a notional format for a memorandum of agreement for contract administration services support;</p>
         <p outputclass="List4" class="- topic/p ">(A) Purpose: Outline formal procedures for requesting contract administration services support, describe objectives associated with combat support agency providing such support.</p>
         <p outputclass="List4" class="- topic/p ">(B) Reference: Key documents or reference(s) associated with the execution of the contract administration services support.</p>
         <p outputclass="List4" class="- topic/p ">(C) Clearing-house functions performed by the designated joint or lead component contracting activity in the operational area–</p>
         <p outputclass="List6" class="- topic/p ">(1) Contract clearance parameters – when required;</p>
         <p outputclass="List6" class="- topic/p ">(2) Contract delegation parameters – when required.</p>
         <p outputclass="List4" class="- topic/p ">(D) Contract administration services support parameters—</p>
         <p outputclass="List6" class="- topic/p ">(1) Acceptable for delegation - contract types that will be accepted by the combat support agency based on risk, dollar threshold, geographic dispersion of performance, service type, criticality of acceptance, or other criteria;</p>
         <p outputclass="List6" class="- topic/p ">(2) Generally not be delegated – below-threshold contract types;</p>
         <p outputclass="List6" class="- topic/p ">(3) Will not be delegated – no agency expertise to oversee.</p>
         <p outputclass="List4" class="- topic/p ">(E) Delegation process – process for accepting and assigning contract administration services tasks within the combat support agency.</p>
         <p outputclass="List4" class="- topic/p ">(F) Joint resolution process – procedures in the event of disagreement on actions to be supported by the combat support agency.</p>
         <p outputclass="List4" class="- topic/p ">(G) Term of the Agreement and Modification - length of time the agreement will be in effect and procedures for the parties to modify or terminate it.</p>
         <p outputclass="List2" class="- topic/p ">(4) Disputes regarding requested support should be resolved at the lowest management level possible, through a predetermined resolution process. When support issues arise that affect the ability of a combat support agency to provide contract administration support that cannot be resolved at lower management levels, follow procedures set forth in DoDI 3000.06, Combat Support Agencies, paragraphs 5.6.8 and 5.6.9, (http://www.dtic.mil/whs/directives/corres/pdf/300006p.pdf).</p>
         <p outputclass="List2" class="- topic/p ">(5) Responsibilities of the head of the contracting activity for contingency contract closeout are addressed at DFARS <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-204.804"
                  href="204.804.dita#DFARS_204.804"
                  xtrc="204.804">204.804</xref>(2). See also planning considerations at PGI 
               <xref outputclass="fm:ParaNumOnly"
                  class="- topic/xref "
                  base="DFARS-PGI_PGI_207.105"
                  href="PGI_207.105.dita#DFARS_PGI_207.105"
                  xtrc="207.105">207.105</xref>
            (b)(20)(C)(8).</p>
      </conbody>
   </concept>
</dita>
