AFFARS APPENDIX CCAir Force Contingency Contracting Readiness Program

Previous PageTable Of ContentsAFFARSNext Page



APPENDIX CC
Air Force Contingency Contracting Readiness Program

[Revised November 7, 2012]

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 to meet global mission objectives across the full range of military operations, utilizing firm-fixed price, cost-plus-fixed-fee, or cost-plus-award-fee task orders as necessary to best meet the government’s needs. Air Force Civil Engineering Support Agency (AFCESA) is located at Tyndall AFB, FL, with the AFCAP Program Manager deployed forward as required.

Air and Space Expeditionary Forces (AEF): The AEF is the force generation construct used to manage the battle rhythm of the forces in order to meet global Combatant Commander (CCDR) requirements while maintaining the highest possible level of overall readiness.

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 Operation: See FAR 2.101

Contingency Contracting Officer (CCO): See AFFARS 5318.001

DAS(C): See AFFARS 5302.101

Designed Operational Capability (DOC) Statement: a summary of a unit’s mission and resources for which it has been organized, designed, and equipped.

Humanitarian or Peacekeeping Operation: See FAR 2.101 and DFARS 218.270

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: See FAR 2.101

Micro-purchase Threshold: See FAR 2.101

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): See AFFARS 5302.101

Simplified Acquisition Procedures (SAP): See FAR 2.101

Simplified Acquisition Threshold (SAT): See FAR 2.101

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 must:

(b) Each MAJCOM SCO must:

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

PART CC-2 —CONTRACTING ORGANIZATIONAL RELATIONSHIPS

CC-201 RESERVED

CC-202 RESERVED

CC-203 RESERVED

CC-204 RESERVED

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 must 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 must also be inspected prior to and upon return from all deployments. Kit inspection results must 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 must 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 must 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 covered 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 and tailored to the contingency requirement. (NOTE: Recommend using the AFLMA’s Contingency Contracting Customer guide during this training.)

PART CC-5 — CONTRACTING SUPPORT FOR CONTINGENCY OPERATIONS

CC-501 RESERVED

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