AFCAP Volume I: Vehicle Brief

The Air Force Contract Augmentation Program (AFCAP) is run out of Tyndall AFB, Florida, by the 772d Enterprise Sourcing Squadron. It is a multiple-award IDIQ, meaning the Air Force ran one big competition years ago, awarded the same basic contract to several companies at once, and now everybody works off task orders against those parent contracts. The hard work of selecting vendors, vetting their capacity, and pricing the framework is done. What's left when a requirement comes in is the task order layer.

That structure is where AFCAP earns its reputation. A normal acquisition starts with market research, builds a solicitation, runs an evaluation, and finally awards. That whole sequence can take years. With AFCAP, the parent contracts are already in place, the holders are already qualified, and the program team at Tyndall is already running source selections every week. So the timeline collapses to: the customer brings the requirement, the program team competes the task order across the holders, and the award goes out in a matter of months instead of years.

The current contract is AFCAP V. It was awarded in April 2020 with a $15 billion ceiling and an 8-year ordering window (a base year plus seven option years). Most basic contracts also include a six-month extension of services, and services already underway can continue for up to three years after the ordering window closes.

What kinds of work does it cover? Mostly services, but also commodities and construction support. Base operating support, life support, infrastructure, engineering services, recovery and reconstitution work, and any mission-support package that fits the parent-contract scope. The contract types available on a task order include firm-fixed-price (FFP), fixed-price incentive fee (FPIF), cost-plus incentive fee (CPIF), cost-plus fixed fee (CPFF), and straight cost reimbursement. The right type depends on how well-defined the requirement is and how much risk the Government is asking the contractor to absorb.

AFCAP was built for situations where the schedule won't tolerate a normal acquisition. Some of those are obvious. A hurricane just wiped out a base, a contingency just kicked off, the requirement is real and the clock is short. Some are less obvious. The program is structured broadly enough to support a range of mission categories.

The mistake most COs make with AFCAP is reaching for it when something else fits better. The vehicle is familiar, the program team is responsive, the awards move quickly, and once you've used it once it becomes the default. Resist the default. There are several common situations where AFCAP isn't the right answer.

The pattern across all of these is the same: AFCAP is a specialized tool. Reach for it when the specialization fits. When it doesn't, you'll have a better outcome and the program team will have more capacity for the requirements that genuinely need them.

AFCAP V is held by six companies. Most CCOs and operational COs will encounter one or two of these names regularly and the others rarely. Recognition is the goal. If a mission partner says any of these names in a contingency-support conversation, AFCAP should be one of the pathways that comes to mind.

You'll also see legacy names in older files: DynCorp, PAE, URS/AECOM, CH2M Hill, Bechtel National, Washington Group International. These companies held AFCAP I–IV. If an old Performance Acceptance Report (PAR) or task-order document references them, it isn't a different universe. It's an earlier generation of the same program.

Once a requirement reaches the AFCAP team and the fit is good, there are two paths the task order can take. The default is competitive. The exception is urgent and compelling. Both paths drive the same six holders. The file work is very different.

Most of the friction on AFCAP comes from the responsibility split between the customer and the contract team, not from the FAR. Customers often arrive expecting AFCAP to handle pieces that AFCAP cannot handle for them. AFCAP, in turn, can move quickly only when the customer-side inputs are real. Knowing the split is the difference between a smooth task order and a stalled one.

AFCAP is geographically distributed. The program office, the source selection work, the funding management, and the closeout team all sit at Tyndall AFB, Florida, with reachback support at Joint Base San Antonio, Texas. That's where the PCO, the AFCAP Team Lead, the Flight Chief, and the buyers live.

The forward side of the program is in theater. AFCEC Program Managers and AFCENT Administrative Contracting Officers handle the on-the-ground work: writing PWSs and SOWs in coordination with the customer, building Government estimates, facilitating pre-bid contractor site visits, evaluating proposals, generating technical evaluation inputs, administering contracts, processing adjustments, and accepting products and services as they get delivered. Forward locations have included Al Udeid, Al Dhafra, Al Jaber/Ali Al Salem, Muwaffaq Salti, Prince Sultan, Israel, and Thumrait, among others.

If you're routing something to AFCAP for the first time, a few of the foundational pieces will make or break the speed of the eventual award. None of these are unique to AFCAP. They show up faster on a fast vehicle.

Volume I is recognition and routing: what AFCAP is, when to use it, what the customer brings, and what the team brings. If you're going to actually administer an AFCAP task order, the rest of the curriculum lives elsewhere on the site.