Acquisition

In defense, acquisition means the process a government uses to define, buy, and field military capability. Not corporate M&A. When a program manager at the Pentagon says acquisition, they mean the machinery that turns a requirement into a fielded system: requirements definition, budgeting, competition, contract award, development, test, production, and sustainment. The F-35 program, the largest acquisition in DoD history, is expected to cost around $1.7 trillion across its full lifecycle, and most of that is sustainment rather than the aircraft themselves.

How the US system works

The Department of Defense runs acquisition on three connected processes. JCIDS defines what the force needs. PPBE allocates the money. The Defense Acquisition System, governed by DoD Directive 5000.01, manages the actual programs. A major program passes through milestone reviews labeled A, B, and C. Milestone B is the big one. It marks formal program start, locks in a cost and schedule baseline, and commits real production money.

Cost growth against that baseline has teeth. A program that overruns its baseline by 25 percent triggers a Nunn-McCurdy breach, which forces the Pentagon to notify Congress and justify why the program should survive at all. Some do not.

The rulebook

Two documents govern nearly every purchase. The Federal Acquisition Regulation (FAR) applies across the US government, and the Defense Federal Acquisition Regulation Supplement (DFARS) layers defense-specific rules on top, covering everything from cybersecurity requirements to specialty metals sourcing. Contractors feel DFARS most directly through clauses like 252.204-7012, which mandates NIST SP 800-171 compliance for handling controlled unclassified information.

Since 2015 Congress has pushed alternatives to the traditional route because the milestone process is slow. Other Transaction Authority (OTA) agreements let the DoD prototype with companies that never work under the FAR, and Middle Tier of Acquisition lets programs skip JCIDS entirely if they can field within five years. Anduril and other newer entrants built much of their early defense business on OTAs.

Why programs overrun

Three causes come up in nearly every GAO report on the subject. Requirements creep, where the customer keeps adding capability after the baseline is set. Concurrency, where production starts before testing finishes, so early units need expensive retrofits. And optimistic cost estimating at Milestone B, since a program priced honestly might never get approved. The pattern is old. It shows up in the A-12 cancellation of 1991 and again in the F-35's early production lots.

How is defense acquisition different from ordinary government purchasing?

Scale, secrecy, and the absence of a commercial market. Nobody else buys aircraft carriers. When there is only one buyer and two or three possible sellers, normal price competition breaks down, so the government substitutes regulation, audit rights, and certified cost data for market pressure. That substitution is where most of the paperwork burden on defense suppliers comes from.

What does acquisition mean for a supplier trying to enter the market?

Registration in SAM.gov, a CAGE code, and compliance with the DFARS clauses in your contract come first. Beyond the basics, the practical question is which acquisition pathway your customer is using. A program office buying through an OTA behaves differently from one working a traditional milestone program, in timeline, in data rights expectations, and in how much past performance history it demands.