AFFARS APPENDIX CC Air Force Contingency Contracting Readiness Program

Previous PageTable Of ContentsAFFARSNext Page



APPENDIX CC
Air Force Contingency Contracting Readiness Program

[2013 Edition]

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 5318.001

DAS(C): See 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 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 (described above), 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 1100.22, Policy and Procedures for Determining Workforce Mix. In addition to DoDI 1100.22, Policy and Procedures for Determining Workforce Mix, plans for military contingency operations should cover requirements found in DoDI 3020.41, Operational Contract Support, 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 paragraph 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 paragraph 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.

Paragraph 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 “Defense Contingency Contracting Handbook”. In addition to contingency-specific training, paragraph 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.

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:

Mandatory Procedure

MPCC-301(c) — Contracting Support of an Installation

The following areas will be addressed in a local Comprehensive Emergency Management Plan (CEMP) or checklists associated with a CEMP, as defined in Air Force Instruction 10-2501. This is not an all-inclusive list. Items may be added as required to meet unit specific needs.

MPCC-301(c)(1) — Contracting Incident Response Kits (CIRK)

A. In addition to DOC Statement requirements, units will assemble and maintain at least two CIRKs for use during local incident responses. The CIRKs will be pre-assembled and positioned for rapid retrieval and transportation. Unit commanders should consider positioning at least one kit outside the squadron’s main facility or at an off-base site. CIRKs are intended to be hand-carried. The list below is not all inclusive. Items may be added as required to meet unit specific needs. As a minimum, CIRKs must contain the following items:

MPCC-302(a) — Deployment/Mobility Kits

(i) Each operational contracting organization shall maintain sufficient supplies and equipment to provide quick reaction contracting support for deployment taskings and/or local contingencies. In addition to personal gear and unit-issued mobility bags, the subparagraphs below describe two primary Contingency Contracting Kits and equipment packages corresponding to Unit Type Codes XFFK4 and XFFKT. Operational contracting organizations will maintain the required number of kits as assigned. Unless otherwise indicated, consumable items such as supplies and forms should be in sufficient quantity to operate for a 30-day period.

Home station items to include in kit or add to kit prior to deployment

Equipment and/or operational capability

Publications, forms, and formats

(* in addition to electronic media versions, must have at least ten (10) hardcopies on-hand)

Office Supplies

Home station items to include in kit or add to kit prior to deployment

Equipment and/or operational capability

Publications, forms, and formats

(*in addition to electronic media versions, must have at least ten (10) hardcopies on-hand)

Office Supplies

MPCC-401(a)(i) — Contingency Contracting Officer Training

A. General. The training addressed within this procedure is intended to provide the contracting unit commander with a comprehensive outline for conducting unit level contingency contracting training. It lists the minimum required training and is in no way intended to be all inclusive or limit individual unit’s creativity. Units are encouraged to supplement this training with additional training as frequently as unit leadership deems appropriate or required. The mandatory training will typically consist of at least a 1-hour block of time. A training session should normally follow the basic schedule outlined below. Units are encouraged to adapt this schedule to suit the specific needs of their CCOs.

B. Notional Training Session Agenda

C. Training Documentation

D. Initial Contingency Contracting Training

E. Recurring Contingency Contracting Training

F. Recurring General Contracting Training

Informational Guidance

IGCC-301(b)(1) — OPLAN Review

The following are areas should be addressed in OPLANs tasking contracting assets. It is not an all-inclusive list. This list may be tailored, as required, to meet unit-specific needs.

IGCC-301(b)(2)A — Contracting Site Surveys

The following topics should be addressed in the contracting portion of site surveys. It is not an all inclusive list. Items may be added as required to meet unit specific needs.

(a) Update information concerning potential contracting sources in the deployment area, including information from the U.S. Embassy, Consulate, Air Attaches, and/or other Government agencies operating in the same area. Typically, these agencies can assist with:

(b) Include a master listing of contractors and identify those willing to provide emergency response after normal business hours.

(c) Assess vendor acceptance of the Government-wide Purchase Card;

(d) Identify sources for potential and pre-identified requirements. If no source is available to provide a pre-identified requirement, the survey should establish procedures for ensuring the user is notified that contracting support may not be available for the requirement at a particular deployment site;

(e) Survey local customs, laws, taxes, and shortages within the local economy, local bureaucratic impediments, language difficulties, currency exchange rate fluctuations, and security concerns. If local sales tax exemption procedures or numbers are available, obtain them through embassy personnel;

(d) Examine local transportation and communication resources availability;

(e) Determine the applicability of the Host Nation Mutual Support Agreements, Status of Forces Agreements, Acquisition Cross-Servicing Agreements, or other diplomatic agreements, if any, and evaluate the impact of these agreements upon contingency contracting within the deployment area;

(f) Survey facilities, equipment, and other support needed for the deployed contracting office. Coordinate contracting facility requirements with the Civil Engineer, Communications Specialist, and Logistics functional commanders as necessary;

(g) Consider problems that should be anticipated in supporting contract requirements for an extended exercise or contingency operation. Particular attention should be given to those items or services that are available in limited quantities; and

(h) Determine what contract formats may be needed in the local area considering Host Nation Support Agreements, expected taskings, and local business customs.

IGCC-502(a)(1) —Initial Deployment Phase Actions

A. Contingency contracting activities during initial deployment.

IGCC-502(a)(2) — Build-up/Reception, Staging, Onward Movement, And Integration (RSOI) Phase Actions

A. Contingency contracting activities during the build-up/RSOI phase.

IGCC-502(a)(3) — Sustainment Phase Actions

A. Contingency contracting activities during the sustainment phase.

IGCC-502(a)(4) —Termination/Redeployment Phase Actions

A. Contingency contracting activities during the termination/redeployment phase.

Previous PageTop Of PageTable Of ContentsAFFARSNext Page