Skip to main content
HonestMOS
InvestigationsCongress made VA disability claims free to file. An entire industry charges veterans anyway — and nobody can stop them.
← Follow the Money

Spending Intelligence · Defense Acquisition System

The $300B/Year Procurement System
That Keeps Breaking

Your unit has equipment designed in 2003 while China fields a weapon system in 7 years that DoD would still be writing requirements for. The defense acquisition system — the JCIDS/PPBE/DAS triad — is why. It takes 7 to 20 years to field a major system, costs have grown by $628 billion across active programs, and reform attempts have been ongoing since the Reagan administration. Every number on this page is sourced to a public government record.

Sources: GAO-23-105594 · DoD Selected Acquisition Reports (SARs) · PPBE Reform Commission Final Report (2023) · CBO defense analyses · RAND acquisition research · DoD Comptroller · POGO database

Annual Procurement & R&D Budget

~$300B

FY2024 DoD budget request; procurement + RDT&E accounts combined

Avg Timeline — Major System

7–20 yrs

GAO analysis of major defense acquisition programs; varies by complexity

Active Major Defense Acquisition Programs

300+

MDAPs tracked in DoD annual Selected Acquisition Reports (SARs)

Total Cost Growth Across MDAPs

$628B

Cumulative cost growth above original baselines; GAO-23-105594 (2023)

Section 01

How DoD Acquisition Is Supposed to Work

The system is not random. It has a logic. Understanding the logic explains why it produces the outcomes it produces.

JCIDSRequirements

Joint Capabilities Integration and Development System

JCIDS answers the question: "What do we need?" A capability gap gets identified — say, infantry lacks sufficient anti-armor capability against a specific emerging threat. That gap triggers an Initial Capabilities Document (ICD), which must be validated by the Joint Requirements Oversight Council (JROC), a four-star-level body chaired by the Vice Chairman of the Joint Chiefs. If the ICD is approved, the requirements community develops a Capability Development Document (CDD), which defines what the system must do in measurable, testable terms. After development and testing, a Capability Production Document (CPD) locks in production requirements. Every document requires JROC approval. The JROC meets infrequently, prioritizes joint programs, and often returns documents for revision. A single round-trip from JROC can take 6–12 months. Programs rarely go through only one round.

PPBEMoney

Planning Programming Budgeting Execution

PPBE answers the question: "Who gets the money?" Once requirements are established, the program must compete for funding inside the DoD budget cycle. Each service submits a Program Objective Memorandum (POM) to OSD every two years. OSD reviews, adjusts, and forwards to OMB, which assembles the President's Budget. Congress then appropriates — or modifies, cuts, or adds to — the budget through the National Defense Authorization Act (NDAA) and accompanying appropriations bills. The entire cycle from POM submission to enacted appropriation takes 18–24 months. Critically, the budget is built in two-year cycles while programs span decades. This mismatch means programs are routinely underfunded in early years, generating cost growth as work slips to later years with higher inflation.

DASExecution

Defense Acquisition System

DAS answers the question: "How do we build it?" Governed by DoD Instruction 5000.02, the DAS defines the lifecycle phases and milestone decisions that every major program must pass through. Milestone A authorizes entry into the Technology Maturation and Risk Reduction (TMRR) phase — the government is exploring materiel solutions. Milestone B authorizes entry into Engineering and Manufacturing Development (EMD) — the government has selected a contractor and is developing the actual system. Milestone C authorizes entry into production and deployment. Each milestone requires an Acquisition Decision Memorandum (ADM) signed by the Milestone Decision Authority (MDA) — typically the USD(A&S) for major programs. Between milestones, programs undergo Defense Acquisition Board (DAB) reviews, independent cost estimates, and test evaluations. Each touchpoint adds months.

The Math

From capability gap to first unit equipped: a minimum viable timeline

ICD development and JROC approval12–24 months
CDD development and JROC approval12–24 months
PPBE cycle: POM to appropriation18–24 months
Milestone A: materiel solution analysis12–18 months
Milestone B: source selection and EMD contract award12–24 months
Engineering and Manufacturing Development (EMD)24–60 months
Initial Operational Test and Evaluation (IOT&E)12–24 months
Milestone C: production decision and ramp12–18 months

Minimum: ~7 years if every step proceeds without delay, revision, or program restructure. No major program proceeds without delay, revision, or program restructure.

Section 02

Why the System Is Structured to Fail

These are not bugs. They are features of a system designed to serve multiple stakeholders simultaneously — and those stakeholders do not all want the same things.

Systemic

Requirements Creep

The requirements process has a structural incentive toward expansion. Each service, each combatant command, and each functional community that reviews a requirements document has an opportunity to add capabilities. Adding a requirement is costless to the person adding it. The cost is borne by the program office that has to engineer, test, and produce it. The F-35 began as a joint, affordable, multirole strike fighter to replace several legacy aircraft at dramatically lower unit cost. Over two decades of requirements refinement, it accumulated stealth, supersonic performance, STOVL capability, carrier compatibility, nuclear weapon integration, advanced sensor fusion, and electronic warfare capability simultaneously across three variants. Each addition was individually justifiable. Collectively, they produced the most expensive weapon system in human history.

Systemic

Spiral Development and Lock-In

Programs are frequently approved at lower cost and capability than ultimately delivered, using a concept called "spiral development" — the system is fielded in increments, with each increment adding capability. The theory is sound. The practice is that Spiral 1 establishes an industrial base, a contractor team, a government program office, and a congressional constituency. By the time Spirals 2 and 3 arrive with expanded requirements and higher costs, canceling the program would eliminate jobs in multiple congressional districts, strand significant sunk-cost investment, and leave a capability gap. The political economy of large defense programs makes them nearly impossible to cancel once the industrial base is established — even when the program is failing.

Systemic

Congressional Pork and Constituency Politics

Defense programs are not just weapons. They are employment programs, and every member of Congress whose district hosts a prime contractor, a subcontractor, or a supplier has a direct financial incentive to keep the program funded. The C-17 Globemaster III cargo aircraft is the clearest example: the Air Force declared it did not need additional C-17s in 2009 and requested program closure. Congress continued funding production for two additional years, adding aircraft the Air Force said it did not want. The Boeing plant in Long Beach, California, employed thousands; the political calculus was straightforward. This is not an aberration. It is the norm. The DoD "unfunded priorities list" — the list of things the military actually wants — regularly differs from what Congress actually funds.

Contributing

"Too Big to Fail" Prime Contractors

Lockheed Martin, Boeing, Raytheon Technologies (now RTX), Northrop Grumman, and General Dynamics are the five prime contractors that dominate the DoD industrial base. Their workforce, specialized facilities, technical expertise, and cleared personnel are genuinely irreplaceable on a short timeline. DoD knows this. The primes know this. When a major program encounters cost growth, schedule slippage, or technical failure, the honest market response — termination and competition — is rarely available. Walking away from a failing Lockheed or Boeing program risks destroying cleared manufacturing capacity that took decades to build and could take a decade to reconstitute. This structural dependency gives prime contractors negotiating leverage that no competitive market would tolerate.

Contributing

The Valley of Death

Small, innovative companies — often the source of genuinely disruptive technology — face a structural trap in DoD acquisition. A DARPA or Army Futures Command program manager discovers a promising technology at a startup. The startup wins a $2–5M Other Transaction Authority (OTA) prototype contract. They deliver a working prototype. Then the program must transition to a Program of Record — a formal acquisition program with a budget line, a prime contractor team, ITAR compliance infrastructure, cleared facilities, and the ability to respond to the full weight of Defense Federal Acquisition Regulations (DFAR). Most small companies cannot survive the 5–7 year gap between prototype success and production contract award. The technology either dies, gets acquired by a prime (who may or may not develop it), or gets copied by the prime who then wins the production contract. The Valley of Death is why COTS technology routinely outperforms DoD-developed alternatives at a fraction of the cost.

Section 03

Major Acquisition Disasters: The Actual Numbers

These are not the only programs that overran cost and schedule. They are representative examples where the public record is clear.

F-35 Lightning II

USAF / USN / USMCMajor Overrun

Original Estimate

$233B (2001)

Current / Final Cost

$398.6B acquisition / $1.7T lifecycle

Schedule

10+ years late to full operational capability

The most expensive defense program in US history. Mission capable rates have never hit the program target. The F-35B STOVL variant weight crisis in 2004 triggered the first of multiple program restructures. Unit cost grew from ~$81M to ~$162M (flyaway cost of ~$82M). See the full F-35 breakdown at /spending/f35.

Littoral Combat Ship (LCS)

USNMajor Overrun

Original Estimate

$220M per ship (2002 promise)

Current / Final Cost

$700M+ per ship (actual average)

Schedule

Multiple delivery delays; survivability failures

The LCS was conceived as a fast, affordable, networked surface combatant to replace three legacy ship classes. It would cost less than $220M per hull. When actual costs emerged, the program split into two competing designs (Freedom-class and Independence-class), which increased overhead without achieving competition savings. The Navy's own testing found the ship could not survive in a "moderate threat environment." Ships are being decommissioned well short of their planned service lives.

Boeing KC-46 Pegasus Tanker

USAFSignificant Overrun

Original Estimate

Fixed-price contract 2011

Current / Final Cost

$7B+ in Boeing overruns absorbed by Boeing (fixed-price)

Schedule

6+ years behind delivery schedule

The KC-46 was supposed to demonstrate that fixed-price development contracts could discipline prime contractor cost growth. Boeing bid low and won. When technical problems multiplied — most critically, a remote vision system (RVS) that couldn't reliably see the receiver aircraft — Boeing absorbed $7B+ in losses rather than let the government escape. The Air Force received aircraft with known Category 1 deficiencies because they needed tankers. The RVS 2.0 fix was promised for years. As of 2024, the aircraft still has unresolved deficiencies.

Army DCGS-A (Distributed Common Ground System)

USASignificant Overrun

Original Estimate

~$2.3B (early program)

Current / Final Cost

$6B+ through 2016

Schedule

Fielded late; replaced by COTS solution

DCGS-A was the Army's intelligence fusion system — designed to aggregate signals intelligence, imagery, human intelligence, and other sources into a single analytical platform for brigade and division staff. Soldiers who used it described an unintuitive, crash-prone system that required extensive training to produce results that an analyst with commercial tools could produce faster. Units deployed with unofficial workarounds. After spending over $6B, the Army ultimately moved toward commercial platforms. The system exists in Army unit T/O&E today but is widely regarded as acquisition malpractice.

JSTARS Recapitalization

USAFSignificant Overrun

Original Estimate

~$1B in requirements/concept work

Current / Final Cost

$1B+ spent before cancellation

Schedule

Cancelled 2019 before Milestone B

The Air Force spent roughly a decade and over $1B studying how to replace the aging E-8 JSTARS ground surveillance aircraft. Multiple industry teams competed. Then the program was cancelled — not because the mission went away, but because the analysis concluded that distributed UAS and long-range radar systems could perform the ground moving target indicator (GMTI) mission better, cheaper, and more survivably. The money spent on requirements and concept development bought information, but that information could have been purchased faster. The JSTARS replacement gap remains partially unfilled.

Army IVAS (Integrated Visual Augmentation System)

USASignificant Overrun

Original Estimate

$21.9B contract (2021, with Microsoft)

Current / Final Cost

Restructured; reduced quantities

Schedule

IOC delayed; capability increment 1.2 replaced 1.0

IVAS promised soldiers an augmented reality headset providing digital maps, blue force tracking, thermal sensor display, and squad communication overlay on a single wearable device. The technology is real and the capability is genuinely valuable. What happened instead: soldiers in operational testing reported dizziness, nausea, balance problems, and visual interference in ambient light. For two years, soldier feedback was documented and ignored as the program pressed toward fielding. In 2023, after sustained congressional scrutiny, the Army restructured the program. The $21.9B ceiling contract remains, but the path to that number is now uncertain.

Section 04

The Other Transaction Authority Reform Attempt

OTA was supposed to open DoD contracting to the Silicon Valley ecosystem. The results are more complicated than the reformers hoped.

What OTA Is Supposed to Do

Other Transaction Authority (10 U.S.C. § 4022) allows DoD to enter prototype agreements with contractors without following the Federal Acquisition Regulations (FAR). This matters because FAR compliance is extraordinarily expensive for small companies — accounting requirements, certified cost and pricing data, property clauses, and audit rights create overhead that a 50-person startup simply cannot absorb. OTA was designed to let DoD work with the commercial technology ecosystem — Silicon Valley, defense-tech startups, dual-use innovators — without forcing them through a compliance gauntlet that was designed for Lockheed Martin.

The Silicon Valley Problem OTA Was Meant to Solve

The most innovative software and hardware companies in the country have no interest in DoD contracting. Not because they are anti-military — many founders are veterans — but because the compliance burden, the security clearance requirements, the ITAR restrictions, the data rights disputes, and the 2–5 year procurement timelines make it economically irrational. A startup that raises a Series A can't wait four years to find out if it won a contract. By the time a DoD program "discovers" a commercial technology, the commercial market has already moved two generations beyond it. Google, Amazon, Palantir, Anduril, and SpaceX have been the notable exceptions, and each required either extraordinary patience (Palantir sued the Army), deep capital (Amazon), or a founder willing to absorb the friction (SpaceX).

How the Primes Captured OTA

Within years of expanded OTA use, prime contractors discovered that forming a consortium or a subsidiary company with a non-traditional contractor partner qualified the arrangement for OTA even though the prime was the economic beneficiary. RAND and GAO analysis found that a significant fraction of OTA dollars flowing to "non-traditional" contractors actually ended up with entities controlled by or closely affiliated with traditional defense primes. The spirit of OTA — accessing genuinely new entrants — was diluted. Congress has added requirements for independent review of large OTA awards, but the structural incentive remains: large primes have program offices dedicated to OTA capture.

What OTA Has Actually Delivered

Defense Innovation Unit (DIU) has used OTA to commercialize dual-use technology faster than traditional acquisition in areas like commercial satellite imagery, AI-enabled computer vision, and logistics optimization. Army Futures Command Cross-Functional Teams have used OTA to prototype several systems — some of which (LTAMDS, the next-generation Patriot radar) transitioned to programs of record. DARPA routinely uses OTA for early-stage research. The honest assessment: OTA works at prototype stage. The transition from OTA prototype to full program of record still hits the traditional acquisition wall. Fewer than 30% of OTA prototypes successfully transition to production programs.

OTA by the Numbers (DoD FY2023)

OTA Obligations FY2023

~$23B

DoD OTA report to Congress

Share of Total Procurement

<8%

OTA vs. traditional FAR contracts

OTA-to-Production Transition Rate

<30%

RAND analysis of prototype transitions

DIU Share of DoD Procurement

<1%

DIU annual report; total obligations

Section 05

What Service Members See at the Unit Level

Acquisition failures are not abstract. They show up as the gear in your arms room, the vehicles on your motor pool, and the software on your mission planning systems.

The Equipment Age Gap

Your unit is fielding equipment that was designed in the 1990s or early 2000s, entering production in the 2010s, and reaching your unit sometime in the past decade — right as commercial equivalents that are lighter, cheaper, more capable, and better-connected enter the market. This is not a coincidence. It is the predictable output of a system where the average major program takes 7–20 years from requirements validation to unit fielding. Technology generations turn every 3–5 years in commercial markets. The gap between what the acquisition system can deliver and what the commercial market offers grows wider every year.

Night Vision: Soldiers Buying Their Own Gear

Before the Army fielded ENVG-B (Enhanced Night Vision Goggle-Binocular) with its white phosphor tubes and fusion capability, many infantry and special operations units were purchasing commercial NVGs — PVS-31s, L3 DTNVG, Elbit systems — with personal money, unit MWR funds, or unofficial unit fund-raising. The commercial market had superior technology available for $2,000–$6,000 per unit. The Army's acquisition system took 12+ years to field a program-of-record solution. Soldiers died in that gap. The technical capability existed. The system for getting it to them did not.

MRAP: The Right Vehicle for the Last War

The MRAP (Mine-Resistant Ambush Protected) vehicle is the acquisition system working as intended — rapidly. After IED casualties mounted in Iraq and Afghanistan, DoD executed an emergency acquisition that fielded over 24,000 MRAPs between 2007 and 2012. That success story has a postscript. The MRAP is heavy (12–18 tons), high-profile, road-bound, and optimized entirely against a specific IED threat. Against a near-peer adversary with anti-armor weapons, MRAPs are targets. The Army has been working to field lighter, more mobile protected vehicles ever since. The AMPV (Armored Multi-Purpose Vehicle) is replacing the M113, which has been in service since Vietnam. The transition is happening — slowly, through a normal acquisition program that began in 2014.

Contractor Logistics Support Lock-In

An increasing fraction of DoD weapon systems are fielded under Contractor Logistics Support (CLS) arrangements, where the manufacturer is responsible for maintenance rather than organic military personnel. The theory is sound — contractors maintain complex systems better at lower lifecycle cost. The practice creates dependency. Units cannot perform organizational-level maintenance on CLS systems without contractor presence. When contractors are not present (forward-deployed environments, communications-denied scenarios, surge operations), systems go down and stay down. The F-35, LCS, and IVAS are all CLS-dependent in significant ways. The acquisition system has traded short-term cost efficiency for long-term operational vulnerability.

The Spare Parts Trap

Parts availability is the invisible readiness tax of long acquisition timelines. A weapon system fielded in 2010 based on a 2003 design is already working with components that commercial suppliers stopped making in 2015. The program office has to either negotiate long-term supplier agreements (expensive), manufacture its own parts (very expensive), or cannibalizes other systems. The Air Force's aviation readiness reports consistently cite parts availability as a primary driver of not-mission-capable (NMC) aircraft. The cost of getting parts to a deployed location — airlifted on short notice, under military logistics — amplifies the underlying parts shortage. Every day an aircraft sits NMC waiting for a $400 part, the cost of that aircraft's program office, the flight hour target, and the unit's readiness report all get worse.

Case Study: IVAS

$21.9 Billion for a Headset That Made Soldiers Dizzy

In 2021, the Army awarded Microsoft a $21.9B contract ceiling for the Integrated Visual Augmentation System (IVAS) — an AR headset based on HoloLens technology that would display tactical maps, targeting data, thermal imagery, and squad communication overlays on a heads-up display worn by dismounted infantry.

The capability was real. The problems were also real. Soldiers participating in operational testing reported nausea, dizziness, eyestrain, and disorientation — particularly during vehicle movement and low-light operations. The device obscured natural vision in ways that were tactically dangerous. Soldiers preferred to not wear the device rather than operate impaired.

The Army had this feedback in 2021 and 2022. The program continued toward fielding. It took sustained congressional pressure — and a public GAO report — before the Army restructured the program in 2023, delaying Increment 1 fielding and committing to address the display problems in an Increment 1.2 variant.

Source: GAO-23-105765; Senate Armed Services Committee markup FY2023; Army press statements. The $21.9B ceiling contract does not mean $21.9B has been obligated — it is a contract vehicle ceiling. Actual obligations through 2023 are in the low billions.

Section 06

The Industrial Base Problem

The consolidation of the defense industry was intentional policy. Its long-term consequences were not fully anticipated.

The Consolidation Arc

51

Major Primes
1993

5

Major Primes
Today

Lockheed + Martin Marietta → Lockheed Martin. Boeing + McDonnell Douglas + Rockwell Defense → Boeing Defense. Northrop + Grumman + Newport News → Northrop Grumman. Raytheon + Hughes + TI Defense → Raytheon (now RTX). General Dynamics + Bath Iron Works → General Dynamics.

From 51 Primes to 5

In 1993, Secretary of Defense Les Aspin hosted a dinner with defense industry CEOs that became known as "The Last Supper." He told them the post-Cold War drawdown would make the current number of defense contractors unsustainable and that consolidation was coming. The industry took the message seriously. Between 1993 and 2000, 51 major prime contractors merged into 5. Lockheed merged with Martin Marietta. Boeing acquired McDonnell Douglas and Rockwell's defense units. Northrop acquired Grumman and Newport News. Raytheon acquired Hughes Electronics and Texas Instruments' defense unit. General Dynamics acquired Bath Iron Works and Gulfstream. The consolidation was deliberate policy. Its long-term consequences — reduced competition, single-source suppliers, concentrated political influence — were not fully anticipated.

Single-Source Critical Components

There is now one manufacturer of solid rocket motors for large strategic missiles in the United States (Northrop Grumman, after the 2018 acquisition of Orbital ATK). There are two nuclear submarine shipyards — General Dynamics' Electric Boat and Huntington Ingalls Industries — and the Virginia-class production program has pushed both to capacity. There is one manufacturer of the M1 Abrams tank hull (General Dynamics Land Systems in Lima, Ohio). There is one source for certain specialized missile seekers. When a single supplier has a quality problem, a workforce disruption, or a facility issue, the program has no alternative. This is not an abstract risk. Production pauses, quality escapes, and supplier disruptions have caused real schedule slippage in multiple programs in the past decade.

The 155mm Shell Problem

The Ukraine war provided the clearest real-world test of the industrial base in a generation. In early 2022, Ukraine was consuming approximately 90,000 155mm artillery rounds per month. The United States was producing approximately 14,000 rounds per month — a production rate set by peacetime demand, not wartime requirement. The gap was not a funding problem. It was a production capacity problem. Powder lines, shell forging capacity, and fuze manufacturing had been allowed to atrophy to minimum-sustaining levels. The Army's "SURGE" industrial base expansion program, launched in 2022, is adding capacity — but building a shell manufacturing line takes 18–24 months. The lesson: the production industrial base is as much a strategic asset as the research base, and it cannot be reconstituted quickly.

ITAR and the Allied Market Problem

The International Traffic in Arms Regulations (ITAR) govern the export of US defense articles and services. Every sale of a US weapon system to an allied nation requires State Department export licensing. For major systems, the approval process takes 2–5 years. Allied nations facing urgent capability needs — particularly in the Indo-Pacific — increasingly look at European or Israeli suppliers who can deliver faster with fewer compliance requirements. The Eurofighter, Dassault Rafale, and Leonardo systems are winning competitions that F-16 upgrades or F-35 offers lose on delivery timeline alone. ITAR was designed to protect US technology from adversaries. It has also become a significant competitive disadvantage in allied markets and a friction point in coalition operations where partner nations need interoperable equipment.

The 155mm Shell Problem — By the Numbers

14,000

rounds/month

US Monthly Production (early 2022)

90,000

rounds/month

Ukraine Monthly Consumption

100,000

rounds/month

Target After SURGE (FY2025)

Sources: Army G-4; DoD press briefings; Congressional testimony FY2022–2023.

Section 07

Recent Reform Attempts

Acquisition reform has been declared a priority by every administration since the Reagan era. The results have been incremental.

PPBE Reform Commission (2023)

Partial Implementation

Established by the FY2022 NDAA, the Commission on Planning, Programming, Budgeting, and Execution Reform submitted its final report in March 2023. Key recommendations: separate the budget programming timeline from the acquisition execution timeline to reduce the 18–24 month funding lag; create a new "technology transition" budget account to fund the Valley of Death gap between prototype and program of record; reduce classified budget overclassification that prevents Congress from exercising effective oversight. As of 2024, implementation is partial. The biennial budget recommendation has not been adopted. The technology transition account concept has moved into discussion but not statute.

Section 804 / Middle Tier Acquisition

Underused

Section 804 of the FY2016 NDAA created "middle tier" acquisition authorities — rapid prototyping and rapid fielding pathways designed to deliver capability in 5 years or fewer. The rapid prototyping pathway was meant for programs that needed a working prototype within 5 years. The rapid fielding pathway was for mature technology that could be produced and fielded within 5 years using proven manufacturing processes. Both authorities exist and are technically available to every program manager. Both are chronically underused because program managers are evaluated on compliance with traditional acquisition milestones, not speed. The institutional incentives have not changed to match the statutory authorities.

Army Futures Command (AFC)

Mixed Results

Army Futures Command was established in Austin, Texas in 2018 — deliberately located away from Washington D.C. to reduce bureaucratic inertia. AFC's Cross-Functional Teams (CFTs) are purpose-built groups combining requirements officers, program managers, operational users, and industry representatives to accelerate development. Early results have been mixed but genuine. Long-Range Precision Fires (LRPF) has produced ATACMS follow-on capabilities faster than traditional timelines. Next-Generation Squad Weapon (NGSW) — the XM7 rifle and XM250 automatic rifle — moved from requirements to initial fielding in approximately 5 years, fast by historical standards. The IVAS headset remains a cautionary tale. AFC represents genuine institutional reform; it is not a complete solution.

Defense Innovation Unit (DIU)

Real but Small

DIU was established in 2015, elevated to reporting directly to the Secretary of Defense in 2022. It is the U.S. government's primary mechanism for accessing commercial technology at speed using OTA. DIU has fielded programs in commercial satellite imagery (with Planet Labs, Maxar), AI-enabled logistics, cybersecurity, and unmanned systems. Its contracting timelines are genuinely faster than traditional acquisition — months, not years, for prototype agreements. Its limitation: DIU represents less than 1% of DoD procurement spending. It can demonstrate that fast acquisition is possible. It cannot transform a $300B/year procurement system through demonstration alone.

Adaptive Acquisition Framework (AAF)

Framework Only

The 2020 Adaptive Acquisition Framework revised DoD Instruction 5000.02 to create six distinct acquisition pathways (Major Capability, Middle Tier, Software, Defense Business Systems, Acquisition of Services, and Urgent Capability Acquisition) rather than forcing all programs through one process. The framework is sensible. The problem is that most program managers still default to the Major Capability Acquisition pathway because it is the most documented, the most familiar, and the one for which career patterns and oversight structures have been built. Structural reform requires changing human incentives, not just creating new pathway options.

Section 08

What the Money Actually Buys — Or Doesn’t

The strategic implication of slow acquisition is real. In a peer-adversary competition where both sides are developing new capabilities, timeline matters as much as capability.

China can field a major weapon system in 5–7 years from first prototype to operational unit. The United States averages 15–20 years for comparable complexity. This is not because American engineers are inferior or American technology is behind — it is because the US acquisition system adds 5–10 years of requirements validation, budget competition, oversight review, and compliance documentation that Chinese acquisition does not require.

That accountability structure exists for reasons. It prevents corruption. It ensures taxpayer oversight. It reduces waste. These are real goods. The cost of those goods — in a peer-competition era where military technological advantage is being contested for the first time since the 1970s — is increasingly apparent. The system was designed for a world where the United States had uncontested technological dominance and could afford to take time. That world no longer exists.

The fundamental tension is not between good and bad. It is between accountability and speed — both of which are legitimate requirements, and which the current system does not adequately balance.

5th-Generation Fighter

United States

F-35: ~20 years from concept to IOC (2001 contract, 2015/2016 IOC)

Peer / Near-Peer

J-20: ~7 years from first flight (2011) to operational (2018 PLA announcement)

The comparison is imperfect — the J-20 is a single-service, single-mission aircraft while the F-35 is tri-service across three variants. But the order-of-magnitude timeline difference is real.

Hypersonic Missile

United States

ARRW (Air-Launched Rapid Response Weapon): cancelled after multiple test failures; HACM (Hypersonic Attack Cruise Missile) in development

Peer / Near-Peer

China fielded DF-17 hypersonic glide vehicle in 2019; Russia claimed Kinzhal operational in 2018

US hypersonic development has been hampered by technology risk decisions that delayed testing, combined with a requirements process that added capability simultaneously with development.

Long-Range Precision Strike

United States

PrSM (Precision Strike Missile): approximately 5–6 years from contract to initial fielding (faster than average)

Peer / Near-Peer

DF-26 IRBM: developed and fielded in approximately 5 years

PrSM is one of the acquisition reform success stories — used as evidence that Cross-Functional Teams and clearer requirements can accelerate timelines.

Unmanned Systems

United States

MQ-9 Reaper: fielded; successor programs (MQ-Next) still in requirements phase; Gray Eagle update cycles slow

Peer / Near-Peer

China's CH-4, Wing Loong II, and TB001 series are in production and export; MALE UAS market increasingly non-US

The unmanned aviation market is an area where US commercial leadership (DJI, before export controls) coexisted with slow military procurement.

The Honest Assessment

The United States military maintains genuine qualitative advantages in many domains — experienced NCO corps, joint force integration, logistics reach, global basing network, and decades of institutional combat experience. Those advantages are real. They do not negate the acquisition problem. A system that fields superior technology a decade late may still field superior technology — but with less time to train on it, integrate it, and discover its operational limitations before it is needed in a contested environment. Time is a resource. The acquisition system burns it.

FAQ

Common Questions

Why does it take 10 years to field a new rifle?

The JCIDS/PPBE/DAS process was designed for complex systems like aircraft, ships, and missiles — not squad-level weapons. But the same bureaucratic machinery gets applied. The Army's Next-Generation Squad Weapon (XM7/XM250) took approximately 5 years from requirements validation to initial fielding, which is considered fast. M4/M16 upgrades took longer. The process requires JROC approval of requirements documents, POM funding cycles, Milestone B contractor selection, Engineering and Manufacturing Development phases, Initial Operational Test and Evaluation, and a Milestone C production decision. Each step adds months. The system was not designed for speed; it was designed for accountability. Speed requires waiving or compressing steps, which requires deliberate decisions by senior officials.

Why can't DoD just buy commercial technology?

Three main barriers. First, ITAR and export control classification: commercial technology that incorporates controlled components or that would be used in classified contexts must navigate export licensing, facility clearance requirements, and data handling rules that most commercial vendors are not set up to handle. Second, military-specification requirements: DoD environmental standards (temperature extremes, shock, vibration, electromagnetic interference, water resistance) often exceed commercial specifications. A commercial tablet that works in a climate-controlled office may not survive a dismounted patrol in Kandahar. Third, data rights: DoD needs to maintain, upgrade, and support systems across 20-30 year lifecycles. Commercial vendors don't provide the technical data packages that enable this. The acquisition system has mechanisms to buy commercial items (FAR Part 12), and it uses them for many things — food, fuel, vehicles, software. For weapons and sensors, the barriers are real.

Who profits most from long acquisition timelines?

Prime contractors benefit disproportionately from extended timelines for two structural reasons. First, cost-plus contracts: during development, most major programs use cost-plus-fixed-fee or cost-plus-incentive-fee contracts that reimburse the contractor for actual costs plus a profit fee. Longer development means more billable cost, more fee revenue, and more overhead absorption. A prime contractor's program office has no financial incentive to accelerate. Second, congressional constituencies: members of Congress whose districts host contractor facilities benefit from sustained employment, tax revenue, and campaign contributions. The political economy of large defense programs creates a multi-party incentive for slower, more expensive execution. The losers — taxpayers and service members waiting for equipment — are diffuse and not organized.

Is the F-35 actually good?

The question conflates program management performance with aircraft operational capability. The F-35 program has been a management failure: costs grew from $233B to $399B acquisition, timelines slipped by a decade, and the aircraft has never achieved its readiness targets. These are facts. The aircraft itself — what it can actually do in the air — is more contested. Its sensor fusion (combining radar, EOTS, DAS, and datalinks into a single pilot display) is genuinely superior to any fourth-generation fighter. Its stealth in VHF frequencies is contested. Its range is shorter than the aircraft it replaces in some missions. Its engine is sole-sourced and expensive. For a peer-adversary air superiority mission, whether its capabilities justify its costs is a legitimate analytical debate. For an air-to-ground strike mission against a lower-threat adversary, it is extraordinary capability at an extraordinary price. The program is both a managerial catastrophe and a capable aircraft.

What is OTA and why doesn't it fix everything?

Other Transaction Authority (OTA) is a contracting mechanism that allows DoD to enter prototype agreements without following the Federal Acquisition Regulations (FAR). This matters because FAR compliance is expensive — it requires certified cost and pricing data, cost accounting standards, property management systems, and compliance infrastructure that small innovative companies typically lack. OTA lowers this barrier for prototype contracts. It does not fix the acquisition system because: prototype ≠ program. OTA prototypes still have to transition to programs of record to receive production funding, and that transition takes them back through PPBE budget cycles, congressional appropriations, and traditional contract structures. Additionally, large prime contractors have learned to use OTA through teaming arrangements and consortia, capturing much of the OTA spend without fundamentally changing who benefits.

Intel Brief

Weekly intel from the ranks. No spam. Unsubscribe anytime.

Related Spending Intelligence

Methodology & Sources

All statistics on this page are drawn from public government records: GAO reports, Congressional Budget Office analyses, DoD Selected Acquisition Reports (SARs), PPBE Reform Commission final report (March 2023), RAND Corporation acquisition research, and Congressional testimony. Timeline estimates are drawn from GAO annual assessments of major defense acquisition programs.

Where ranges are given (e.g., "7–20 years"), they reflect variation across program complexity, service, and acquisition pathway. Simple programs using middle-tier authorities have achieved fielding in 3–5 years. Complex joint programs with multi-variant requirements have taken 20+ years. The central estimate of "7+ year average" reflects the GAO median across all MDAPs tracked in the annual SAR data.

Cost growth figures reflect changes from original program baseline estimates to current estimates, as reported in program SARs. The $628B cumulative cost growth figure is from GAO-23-105594 (March 2023). Individual program costs are from their respective SARs and GAO program-specific reports, linked where available.