AFFARS APPENDIX CCContingency Operational Contracting Support

Previous PageTable Of ContentsAFFARSNext Page



APPENDIX CC
Contingency Operational Contracting Support

[Revised October 27, 2010]

PART CC-1 — GENERAL


CC-101 Scope

This appendix establishes policies, assigns responsibilities, and prescribes implementing procedures for the organizing, training, and equipping of Air Force contingency contracting forces. It also offers guidance on accomplishing tasks normally encountered by contingency contracting officers while supporting contingency operations. The intent of this appendix is to establish and maintain responsive contracting support for military contingencies and local incident response.

CC-102 Definitions

Advance Echelon (ADVON): an initial deployment element of personnel and equipment within a specific unit type code (UTC). The ADVON portion of a UTC normally consists of the equipment and personnel required to establish an austere operational capability for a period of up to seven days.

Air Force Contract Augmentation Program (AFCAP): a worldwide contingency contract tool available to support the Air Force and joint force along with any U.S. Government agency in need of urgent logistic assistance in support of contingency operations. AFCAP is designed to rapidly leverage private industry capabilities as a force multiplier in supplying highly responsive solutions to meet global mission objectives across the full range of military operations. Unlike the other Service CAPs, AFCAP can be utilized to procure and expeditiously ship just-in-time commodities. Depending on urgency, degree of requirements definition, or task stability, AFCAP can be tailored into firm-fixed price, cost-plus-fixed-fee, or cost-plus-award-fee task orders as necessary to best match the government’s needs. Air Force Civil Engineering Support Agency (AFCESA) provides PM functions and Air Education and Training Command (AETC) provides contracting support for AFCAP requiring activities. HQ AFCESA is located at Tyndall AFB, FL, with PM deployed forward as required. The AFCAP PCO normally delegates all appropriate contract administration and audit services functions to the Defense Contract Management (DCMA) IAW the specific needs of that task order.

Air Expeditionary Forces (AEF): the pre-determined set of forces (aircraft, equipment, and personnel) from which tailored force packages will be deployed in support of theater commanders. Each AEF will operate a cross section of Air Force weapon systems (150 plus aircraft) and will include 10,000-15,000 personnel.

Area Of Responsibility (AOR): a defined area of land and/or sea in which responsibility is specifically assigned to the commander of the area for the development and maintenance of installations, control of movement, and the conduct of tactical operations involving troops under the commander’s control along with parallel authority to exercise these functions.

Comprehensive Emergency Management Plan (CEMP) 10-2: a document that provides comprehensive guidance for emergency response to physical threats resulting from major accidents, natural disasters, conventional attacks, terrorist attack, and CBRN (chemical, biological, radiological, and nuclear) attacks. (for more information see AFI 10-2501)

Concept of Operations (CONOPS): a verbal or graphic statement, in broad outline, of a commander's assumptions or intent in regard to an operation or series of operations. The concept is designed to give an overall picture of the operation and provide clarity of purpose.

Contingency: an emergency, involving military forces, caused by natural disasters, terrorists, subversives, or required military operations. Due to the uncertainty of the situation, contingencies require plans, rapid response, and special procedures to ensure the safety and readiness of personnel, installations, and equipment.

Contingency Contracting Officer (CCO): a person with delegated contracting authority to enter into, administer, and terminate contracts on behalf of the Government in support of a local contingency, steady-state deployments, or other contingency operations. The CCO also acts as the primary business advisor to the deployed/incident commander or the Emergency Operations Center (EOC) director.

DAS(C): Deputy Assistant Secretary for Contracting. The authority granted to DAS(C) may also be exercised by the Associate Deputy Assistant Secretary (Contracting).

Designed Operational Capability (DOC) Statement: a document prepared by the parent MAJCOM for each measured unit that outlines the DOC of the unit and contains unit identification, mission tasking narrative, mission specifics, and resources to be measured.

Joint Expeditionary Tasking (JET): the Air Force’s overarching method that provides alternative force sourcing when the preferred force solution is not an option. Examples include using Air Force contracting forces when Army contracting forces are not available. For more information see AFI 10-401, paragraph 1.10.4.2.1.

Micro-purchase: an acquisition of supplies or services, the aggregate amount of which does not exceed the micro-purchase threshold.

Micro-purchase Threshold: $3,000, except it means—

Operation Plan (OPLAN): a plan for a single or series of connected operations to be carried out simultaneously or in succession. It is usually based upon stated assumptions and is the form of a directive employed by higher authority to permit subordinate commanders to prepare supporting plans and orders. The designation “plan” is usually used instead of “order” in preparing for operations well in advance. An operation plan may be put into effect at a prescribed time, or on signal, and then becomes the operation order.

Senior Contracting Official (SCO): the MAJCOM/DRU or AFISRA headquarters staff official with overall functional responsibility for contracting. The deputy to an SCO may exercise any SCO authority unless specifically limited by the SCO. The SCO may include the A7K, MSK, or MAJCOM Chief/Director of Contracting.

Simplified Acquisition Procedures (SAP): authorized streamlined purchasing methods prescribed in FAR Part13 used to expedite purchasing support to the warfighter. SAPs are authorized for construction up to the SAT and commercial commodities and services up to $12 million (See FAR 13.500(a)).

Simplified Acquisition Threshold (SAT): $150,000, except that for acquisitions of supplies or services that, as determined by the head of the agency, are to be used to support a contingency operation or to facilitate defense against or recovery from nuclear, biological, chemical, or radiological attack (Pub. L. 108-136, Title XIV, Sec 1443), the term means--

Status of Resources and Training System (SORTS): a Joint Chief of Staff (JCS) controlled automated data system primarily created to provide the National Command Authority and JCS with authoritative identification, location, and resource information. It is used throughout the chain of command to measure the daily resource status of operating forces.

Time-Phased Force Deployment Database (TPFDD): a database that identifies types and/or actual units required supporting operational plans and indicating origin and ports of debarkation or ocean area.

Unit Type Code (UTC): a five-character, alphanumeric code used in automated planning systems that uniquely identifies a specific unit capability. The UTC is linked with specific personnel and/or logistical detail for the purpose of deployment manning, transportation planning, personnel accounting, and replacement planning. The Mission Capability Statement (MISCAP) linked with each UTC specifies the capabilities the UTC represents, as well as the limitations of usage of the UTC.

CC-103 Responsibilities

Effectively supporting contingency operations requires thorough planning and support by organizations at all levels of authority. The following list delineates the key responsibilities and duties at each level to ensure well planned and executed contracting support. This list is not all-inclusive; each level is expected to identify and implement additional responsibilities as they are identified.

(a) SAF/AQC shall:

(b) Each MAJCOM SCO shall:

(c) The commander or chief of each operational contracting organization shall:

PART CC-2 — CONTRACTING AUTHORITY AND ORGANIZATION

CC-201 Contracting Authority

DAS(C) is the Head of Contracting Activity (HCA) for Air Force component commands tasked to support a “supported commander” during JCS declared contingency operations or exercises in accordance with AFFARS 5301.601. See AFFARS 5301.601 for the specific delegations.

CC-202 Establishment of Need for Contingency Contracting Officers (CCO)

The contingency contracting officer (CCO) is the key individual providing contracting support to contingency operations. Contracting activities shall review contingency taskings and designate a sufficient number of qualified individuals to perform those contingency contracting taskings. If the contracting office requires more manpower to support OPLANs than can be reasonably provided without degrading home station functions, then the chief of the contracting office shall notify the cognizant MAJCOM SCO of the shortfall.

CC-203 Selection of Contingency Contracting Officers

(a) Individuals appointed as contingency contracting officers become members of the Air Force’s Contingency Contracting Force, as defined in 10 U.S.C Section 1724 (f) and

(b) Contingency contracting officers (CCOs) shall be otherwise qualified for appointment as contracting officers, as described in FAR 1.603, as supplemented. At a minimum, warrants issued to CCOs will specify contracting authority up to the simplified acquisition threshold on their face.

(c) CCOs shall meet the following additional requirements:


CC-204 Appointment of Contingency Contracting Officers

(a) Air Force issued contracting officer warrants will be honored by Air Force Expeditionary contracting units. If specific limitations on the warrant hinder the CCO’s ability to support contingency operations, warrants may be adjusted by the warrant’s signatory or another warrant may be issued by the gaining command.

Note: Home station warrants may not be accepted when deploying into a joint organization or a unit where the Air Force is not the lead service for contracting support. In these cases, make every effort to coordinate with gaining deployed unit to have warrant in-hand prior to departure from home station. This does not relieve the home station unit from the requirement at CC-204 (b) below.

(b) All contingency contracting officers will deploy with a warrant. Unless the deploying CCO has a valid warrant in hand from the gaining command, the CCO’s home station unit shall issue a warrant to an individual before deploying. Units can issue warrants for CCOs ahead of time if the CCO(s) are designated to support no-notice deployment(s) or incidents. Specific contracting authority on a contingency warrant should be limited to a level commensurate with the individual’s APDP-level certification, demonstrated business acumen, and experience (e.g. micro-purchase, simplified acquisition, unlimited or other designated dollar amount as appropriate).

CC-205 Contracting Organizational Relationships

(a) When deployed, CCOs may fall under one of three organizational structures as described in Joint Publication 4-10, Operational Contracting Support. CCOs should be familiar with each.

(b) When CCOs deploy supporting contingency operations following the Service Component Support to Own Forces construct, CC-205 (a)(3), they are under the operational, administrative, and tactical control of the supported Air Force Component Commander. Oversight of contracting operations is normally accomplished by the Air Force Component Commander’s A7K staff and associated Air Force MAJCOM Senior Contracting Official (SCO).

PART CC-3 — PLANNING FOR CONTINGENCY CONTRACTING SUPPORT


CC-301 Planning Actions

(a) Each operational contracting office monitors current plans and coordinates on all plans tasking the contracting organization for support according to AFI 10-401, Air Force Operations Planning and Execution. All plans should address appropriate actions to be taken by each tasked functional unit to ensure continued performance of essential contractor services pursuant to DODI 3020.37, Continuation of Essential DOD Contractor Services During Crisis. In addition to DODI 3020.37, plans for military contingency operations should cover requirements found in DODI 3020.41, Contractor Personnel Authorized to Accompany the U. S. Armed Forces and Joint Publication 4-10, Operational Contract Support. Plans should also exploit the capabilities CCOs can deliver as part of an advance echelon (ADVON) teams. ADVONs should be manned with an experienced CCO who can locate sources and become familiar with local conditions before arrival of the main body of forces. Plans should provide for adequate security arrangements and disbursing officer support during advanced deployments.

(b) Review of OPLANs. The contracting squadron commander or chief of the contracting office is responsible for reviewing all OPLANs tasking contracting support. When a MAJCOM SCO tasks a contracting office with specific deployment support responsibilities, the MAJCOM will ensure the office includes such tasking in its local plans.

(c) Review of the Installation Comprehensive Emergency Management Plan (CEMP).
In accordance with AFI 10-2501, Air Force Emergency Management (EM) Program Planning and Operations, the CEMP provides comprehensive guidance for emergency response to physical threats resulting from major accidents, natural disasters, conventional attacks, terrorist attack, and CBRN (chemical, biological, radiological, and nuclear) attacks. In developing and maintaining the contracting supplements, checklists, or portions of a CEMP, the chief of the contracting activity will ensure the areas listed in MPCC-301(c) are addressed.

(d) Other Pre-Deployment Requirements for Contingency Contracting Officers


CC-302 Deployment/Mobility Kits

As tasked within their Designated Operational Capability (DOC) Statements, contracting activities will develop local support plans and kits with contracting supplies, forms, instructions, and office equipment to respond to contingency situations. Refer to MPCC-302(a) for specific contents for contingency contracting kits.

(a) Each contracting activity shall develop and maintain deployment kits for use during contingencies. Unit kits will be pre-assembled and positioned for rapid retrieval and transport. Kits will be inventoried on an annual basis Kits shall also be inspected prior to and upon return from all deployments. Kit inspection results shall be documented and maintained for a minimum of one year. Contents will be updated periodically to replace outdated material. Mission Capability (MISCAP) Statements for contracting UTCs are published in the War and Mobilization Plan, Volume 3, Part 3 and contain contracting cargo elements (LOGDET). Unit deployment kits may be tailored to the expected deployment location or expected emergency tasking, but they shall not exceed the size and weight limitations established in the LOGDET for the appropriate UTC. A complete assembled cargo package (UTC XFFK4) is an integral part of UTC XFFK1. Hand carried contracting kits (UTC XFFKT) are part of all other UTCs where specific taskings do not require complete cargo package. If required, the UTC XFFK4 shall be specifically tasked to accompany all UTCs other than UTC XFFK1.

PART CC-4 — TRAINING IN CONTINGENCY CONTRACTING

CC-401 Air Force CCO Training Policy

(a) Contracting Training provides initial and recurring proficiency skills needed by contracting professionals to perform duties in their primary Air Force Specialty Code or civilian job series. Training in contingency contracting skills not normally integrated into peacetime operations is particularly critical to contingency contracting officers and requires special leadership attention. Commanders and supervisors must give priority support to training.

MPCC-401 (a)(i) details a list of mandatory topics to be cover by unit-level training. This training will be used in conjunction with “Contingency Contracting: A Joint Handbook for the 21st Century,” published by the Air Force Logistics Management Agency. In addition to contingency-specific training, MPCC-401(a)(i) requires units to cover some general contracting topics. The general contracting topics may be incorporated into the squadron’s routine training program or accomplished as stand-alone courses.

CC-402 Training Provided to Non-Contracting Personnel

The contracting activity will train non-contracting personnel designated to support contingency plans on the proper use of ordering instruments, SF 44, Government Purchase Cards, and other decentralized procedures authorized for use. (NOTE: Recommend using the AFLMA’s Contingency Contracting Customer guide during this training.)

PART CC-5 — CONTRACTING SUPPORT FOR CONTINGENCY OPERATIONS

CC-501 Expedited Contracting Procedures in Contingency Operations

(a) For most critical steps in the contracting process, the acquisition tools in FAR, DFARS, and AFFARS provide flexibility to permit expedited contracting actions to satisfy urgent and compelling requirements. However, such circumstances do not provide blanket waivers of regulatory requirements, nor do they eliminate the need to maintain required controls and documentation. Examples of existing authorities to expedite contracting actions can be found in FAR Part 18 and DFARS Part 18. They include:

(b) When the nature of the contingency dictates, authorities at appropriate levels may relieve CCOs of specific regulatory requirements contained in the FAR, DFARS, or AFFARS. The authority to relax requirements is limited to those requirements contained in the FAR, DFARS, and AFFARS that are based on contracting policies established at the same level of authority. Department of Defense and Air Force contracting authorities maintain standby packages to initiate relief from regulatory requirements during contingencies. In a similar manner, MAJCOM contracting activities should identify in advance command-specific requirements that may be relaxed or waived during contingency operations. Operational contracting offices should also identify local requirements that would impede contingency contracting and coordinate procedures (within their authority) to relax those requirements.

(c) For Secretary of Defense declared contingency operations, it may also be possible for a CCO to request relief from FAR, DFARS, and AFFARS requirements established as a result of statutes, Executive Orders, or other Executive Agency regulations (e.g., Department of Labor, Small Business Administration, etc.). Relief from these requirements could take considerable time to obtain, so their identification prior to declaration of a contingency operation is essential. SAF/AQC will be responsible for drafting legislative packages for relief in periods of National Emergency from statutes, Executive Orders, and Executive Agency regulations. MAJCOM SCOs are encouraged to make recommendations for FAR, DFARS, and AFFARS requirements for which relief should be requested in support of contingency operations.

CC-502 Contracting Functions Under Deployed Conditions

(a) In providing contingency contracting support, CCOs will perform tasks required by established OPLANs, contingency support plans, and this appendix. Generally, contracting support of deployment operations takes place in four phases. Each of the phases is described below. The activities normally associated with a particular phase can be found in the accompanying Informational Guidance section:

Previous PageTop Of PageTable Of ContentsAFFARSNext Page