TL;DR. Major hardware programs move from a validated capability gap through five phases and three milestones to production and decades of sustainment. Most of the cost comes after fielding: the printer is cheap, the ink is not.
- New to this? The requirement describes the problem (JCIDS-era programs call it an ICD), an Analysis of Alternatives or competitive prototyping compares solutions, and each milestone is an approval gate.
- Government PM? Milestone B needs a validated requirement (a CDD on older programs), an acquisition strategy, an independent cost estimate and funding across the FYDP. No money, no Milestone B.
- Contractor? Sustainment and upgrades are where long-term revenue lives.
- Avoiding trouble? Watch for requirements creep, optimistic estimates, buying before testing and immature technology.
If you ask someone outside the defense world how long it takes to develop a new military aircraft, they'll guess maybe three to five years. The real answer, for a major acquisition program, is often more than a decade: GAO's July 2026 assessment found major programs take over 12 years, on average, to deliver a capability. The defense acquisition lifecycle isn't just slow, it's deliberate. Every phase exists for a reason, and knowing those reasons (and the decision gates between them) is what separates people who survive this system from people who get run over by it.
This guide focuses on the Major Capability Acquisition (MCA) pathway, governed by DoDI 5000.85, which is the dominant framework for large-scale hardware programs: ships, aircraft, ground vehicles, missiles. For the full context on how MCA fits within the six AAF pathways, see The Complete Guide to DoD Defense Acquisition.
Before the Lifecycle Starts: Requirements and the Capability Gap
The acquisition lifecycle doesn't begin in a program office. It begins when a warfighter identifies a capability gap. For about two decades, the Joint Capabilities Integration and Development System (JCIDS) was the process for documenting that gap and validating requirements. DoD disestablished JCIDS in August 2025. Today the sponsoring military service validates its own requirements, the Joint Requirements Oversight Council (JROC) ranks a short list of joint Key Operational Problems, and the Requirements and Resourcing Alignment Board (RRAB) lines those problems up with money.
On JCIDS-era programs, the document that kicked off acquisition was the Initial Capabilities Document (ICD), and you will still see ICDs on legacy programs. Whatever the paperwork is called, the idea is the same. The requirement doesn't prescribe a solution. It describes the operational problem. "We can't defeat this threat with current systems." "We have a logistics gap in this environment." The acquisition system takes that problem statement and begins figuring out how to solve it.
Why This Matters: Requirements instability is a classic cause of cost and schedule growth in defense programs. When requirements change mid-program (after design has begun), they cost far more to accommodate. Programs that start with a fuzzy, poorly validated requirement are setting themselves up for trouble at Milestone B and beyond.
Get the Acqlerate Acquisition Starter Kit (Free)
Key terms, ACAT levels, career roadmaps, and the 5 most common acquisition mistakes. Tailored to your role: USG, contractor, or career changer.
The MCA Lifecycle: Five Phases, Three Milestones
The MCA pathway has five sequential phases separated by three milestone decision gates. Here's how the full lifecycle flows:
| Phase | Name | Enters Via | Key Activity | Primary Document | Typical Duration |
|---|---|---|---|---|---|
| Pre-Acquisition | Materiel Solution Analysis (MSA) | Materiel Development Decision (MDD) | Analysis of Alternatives (AoA); technology assessment | Validated requirement (an ICD on JCIDS-era programs); AoA report or prototyping results; initial cost estimate | 1–3 years |
| Phase A | Technology Maturation & Risk Reduction (TMRR) | Milestone A | Competitive prototyping; requirements refinement; risk reduction | Draft requirement (a CDD on JCIDS-era programs); Acquisition Strategy | 2–5 years |
| Phase B | Engineering & Manufacturing Development (EMD) | Milestone B (Program Initiation) | Final design; system integration; CDR; LRIP quantity planning | Validated requirement (a CDD on older programs); Acquisition Strategy; T&E Master Plan (TEMP) | 3–8 years |
| Phase C | Production & Deployment (P&D) | Milestone C | LRIP; IOT&E; Full-Rate Production decision (FRP) | Production requirement (a CPD under JCIDS); LRIP determination | 3–10+ years |
| Phase D | Operations & Support (O&S) | Full-Rate Production decision | Operational sustainment; modifications; lifecycle management | Life Cycle Sustainment Plan (LCSP) | 20–50+ years |
Durations are rough ranges, not rules. The Phase 0/A/B/C/D labels are our shorthand, keyed to the milestone that opens each phase; DoD policy (DoDI 5000.85) just uses the phase names.
Phase 0: Materiel Solution Analysis (MSA)
The MSA phase begins with a Materiel Development Decision (MDD): the formal determination that a materiel solution is appropriate for the capability gap described in the ICD. Not every capability gap requires a new system; the MDD is the gate that separates cases where you need new development from cases where existing systems can close the gap.
What Happens in MSA
The program office's primary task during MSA is the Analysis of Alternatives (AoA). The AoA evaluates multiple approaches to solving the capability gap: existing systems, modified systems, new development, non-materiel solutions. The goal is to select the most promising technical approach before committing significant resources to development.
This step is changing. The November 2025 Warfighting Acquisition System memo tells DoD to replace analyses of alternatives with competitive prototyping and experimentation where it can, and 10 U.S.C. 4251 now lets a major program use early experimentation with a combatant commander in place of an AoA before Milestone A.
Simultaneously, the program office begins:
- Developing an initial life-cycle cost estimate
- Conducting a technology readiness assessment
- Drafting the Acquisition Strategy (older guidance called the Milestone A version a Technology Development Strategy)
- Working with the sponsoring service's requirements staff to refine the requirement (on JCIDS-era programs, turning the ICD into a draft CDD)
Exit: Milestone A
Milestone A is the decision to enter the TMRR phase. The MDA reviews whether the program has a viable solution identified, adequate cost estimates, an approved requirements document, and a sound plan for the next phase (10 U.S.C. 4251 lists the factors for major programs). The exit criteria are set by the MDA based on the program's ACAT level.
Phase A: Technology Maturation and Risk Reduction (TMRR)
After Milestone A, the program shifts from analysis to active risk reduction. The name says it all: the goal is to mature the technology and reduce the risk of committing to full development.
What Happens in TMRR
Competitive prototyping is the signature activity of this phase. Congress made competitive prototyping the default for major programs in the Weapon Systems Acquisition Reform Act of 2009, because multiple competing approaches reduce technical risk before a single vendor is selected. Program offices evaluate competing designs, conduct cost-performance trade analyses, and select the best approach to carry into EMD.
Other major TMRR activities include:
- Maturing the Capability Development Document (CDD): the detailed requirements document that will govern EMD. Since August 2025 the sponsoring service validates it; under JCIDS, the JROC validated CDDs for the biggest programs.
- Conducting a Preliminary Design Review (PDR), which the MDA must consider before Milestone B on major programs (10 U.S.C. 4252)
- Releasing draft Requests for Proposals (RFPs) for EMD contracts
- Developing the Test and Evaluation Master Plan (TEMP)
- Establishing the Acquisition Program Baseline (APB): the official cost, schedule, and performance commitments that will be tracked going forward
Exit: Milestone B (Program Initiation)
Milestone B is the most consequential decision gate in the entire lifecycle. It marks formal program initiation: the point at which a program officially enters the acquisition system (renamed the Warfighting Acquisition System in November 2025) and receives the resources needed for full development.
Requirements for Milestone B approval include:
- A validated requirement (the CDD on JCIDS-era programs; the sponsoring service is now the validation authority)
- Completed Acquisition Strategy
- Full FYDP funding (the program must be funded across the Future Years Defense Program; the law asks whether funding is expected to be available, per 10 U.S.C. 4252)
- An independent cost estimate (CAPE conducts or approves it for major programs, per 10 U.S.C. 3221)
- A TEMP with approved test approach
- Competition analysis and LRIP quantity determination
The Milestone B Reality Check: Programs that reach Milestone B without FYDP funding get turned away. Money is a common reason milestone decisions slip. The program is technically ready, but the funding hasn't come through in the POM. Program managers and their staffs spend enormous effort on PPBE advocacy in parallel with technical development precisely to avoid this problem.
Phase B: Engineering and Manufacturing Development (EMD)
EMD is where the hardware gets built. After Milestone B, a prime contractor is typically selected via competitive source selection, and the program transitions from prototyping to building the final production-representative design.
What Happens in EMD
It helps to think of EMD in two parts:
- Integrated System Design: System architecture finalized, preliminary designs reviewed, risk areas addressed.
- System Capability and Manufacturing Process Demonstration: Manufacturing processes proven, final design validated through a Critical Design Review (CDR), developmental testing conducted.
The Critical Design Review (CDR) is the major technical milestone within EMD. CDR confirms that the design is complete and stable enough to proceed to production. A failed CDR is a serious event. It typically means more development work and schedule delay before Milestone C.
Under JCIDS, the requirement then evolved from the CDD into a Capability Production Document (CPD), which spelled out what the production system would deliver and had to be approved before Milestone C. Today the sponsoring service validates the production requirement in whatever streamlined form it uses, and legacy programs may still carry a CPD.
Exit: Milestone C
Milestone C approves entry into Low-Rate Initial Production (LRIP), the first actual production units. Requirements for Milestone C include:
- Validated production requirement (a CPD on JCIDS-era programs)
- Successful developmental testing and a positive IOT&E plan
- LRIP determination (quantities approved)
- Updated independent cost estimate
- Demonstrated manufacturing capability
Phase C: Production and Deployment (P&D)
P&D is where the program transitions from development to delivering fielded units to operational units.
Low-Rate Initial Production (LRIP)
LRIP allows production of a limited quantity before the system is formally cleared for Full-Rate Production. If the LRIP quantity tops 10 percent of the total production quantity, the Secretary must explain why to Congress (10 U.S.C. 4231). LRIP units are used for Initial Operational Test and Evaluation (IOT&E), run by the service's independent operational test agency. For major programs, the Director of Operational Test and Evaluation (DOT&E) must approve the test plan in writing and reports the results to Congress, and contractor employees can't conduct the test (10 U.S.C. 4171).
IOT&E evaluates the system in realistic operational conditions with actual users. This is distinct from developmental testing (DT), which is conducted by the program office and focuses on whether the system meets specifications. IOT&E asks: does this system actually work for warfighters in the field?
Full-Rate Production Decision (FRP/LRIP)
The Full-Rate Production decision is the final major milestone: the MDA's approval to produce at the full planned rate. By law, a major program can't go beyond LRIP until IOT&E is complete, and FRP also depends on meeting all other statutory requirements. At this point, the program typically has firm production contracts in place and is delivering units to operational units regularly.
Phase D: Operations and Support (O&S)
O&S is the longest and most expensive phase of any major system's life. The F-15 has been in service since 1976. The B-52 has been flying since 1952. GAO puts O&S at about 70 percent of a system's total life-cycle cost, a fact that's often underappreciated during development when everyone's focused on getting to IOC.
Key O&S Activities
- Sustainment: Maintenance, spare parts, depot support, contractor logistics support (CLS)
- Modifications and upgrades: Capability improvements via Engineering Change Proposals (ECPs) and product improvements
- Life-cycle cost tracking: Against the Life Cycle Sustainment Plan (LCSP)
- Disposal planning: Demilitarization and disposal when the system is retired
The O&S Cost Trap: O&S costs are easy to underestimate during development, and GAO keeps finding O&S cost growth on fielded systems. For contractors, O&S is where long-term revenue lives: sustainment contracts, upgrades, and tech refreshes often exceed initial development contract value over a system's lifetime.
Common Failure Points in the Acquisition Lifecycle
DoD's own reports and program histories point to recurring reasons programs fail to deliver on time and on budget:
1. Requirements Creep
The most common culprit. Requirements that expand after Milestone B (without corresponding cost and schedule adjustments) almost always lead to overruns. The Warfighter always wants more capability; the PM's job is to manage that reality against an approved baseline.
2. Optimism Bias in Cost Estimates
Program offices have structural incentives to produce low cost estimates to win funding. CAPE exists precisely to counterbalance this. Programs that enter EMD with unrealistic baselines hit Nunn-McCurdy breach territory when reality catches up.
3. Concurrency: Buying Before Testing
Congressional pressure to show production progress sometimes pushes programs to buy LRIP units before testing is complete. When tests reveal problems, LRIP units must be retrofitted, at enormous cost. The F-35 is the textbook example. DoD approved its full-rate production decision on 12 March 2024, by which point more than 990 aircraft had already been delivered.
4. Technology Immaturity at Milestone B
Programs that enter EMD with immature technologies, below Technology Readiness Level (TRL) 6 as a rough benchmark, face significant technical risk. For major programs, the MDA has to weigh whether the technology has been demonstrated in a relevant environment (10 U.S.C. 4252), which is what TRL 6 means. The TMRR phase exists to address this, but programs sometimes rush through it.
5. Funding Instability
Programs that get restructured or had their PPBE funding cut mid-stream lose momentum, drive up unit costs (fewer units spread over fixed overhead), and delay fielding. This is a systemic problem that no individual program manager can fully control.
Get the Acquisition Lifecycle Reference Card
Milestone requirements, phase documents, and key decisions on one page. Free for subscribers.
Go Deeper on the Acquisition Lifecycle
Acqlerate's DoD Acquisitions Foundations module walks through each phase with case studies from real programs, including what went wrong and why.
Explore Module 1: DoD Acquisitions Foundations →Frequently Asked Questions
What is Milestone B in defense acquisition?
Milestone B is program initiation, the most important decision gate in the MCA pathway. It's where the Milestone Decision Authority officially authorizes a program to enter Engineering and Manufacturing Development (EMD), the full-scale development phase. At Milestone B, the program must have a validated requirement (a Capability Development Document, or CDD, on JCIDS-era programs), an Acquisition Strategy, full FYDP funding, and an independent cost estimate. Without FYDP funding, programs cannot receive Milestone B approval regardless of technical readiness.
What is the difference between IOT&E and developmental testing?
Developmental testing (DT) is conducted by the program office and tests whether the system meets its technical specifications. It's performed in controlled conditions, often by the contractor. Initial Operational Test and Evaluation (IOT&E) is conducted by the service's independent operational test agency, with DOT&E approving the plan for major programs, using actual military users in realistic operational conditions. IOT&E answers the operational question: can warfighters use this system effectively in the field? Full-Rate Production cannot be approved without a completed IOT&E.
How long does the MCA acquisition lifecycle typically take?
Longer than anyone would like. GAO's July 2026 assessment found major programs take more than 12 years, on average, to deliver a capability. The TMRR phase alone can take 2–5 years. EMD, depending on complexity, is typically 3–8 years. Congressional mandates and PPBE cycles can extend any phase significantly. Operations and Support then runs for another 20–50 years, and GAO estimates O&S alone is about 70 percent of total life-cycle cost.
What is the Analysis of Alternatives (AoA)?
The Analysis of Alternatives (AoA) is a formal evaluation conducted during the Materiel Solution Analysis phase that assesses multiple technical approaches to solving a capability gap. It analyzes the operational effectiveness, suitability, risk, and cost of each alternative, including the option of doing nothing (the baseline). For major programs, the MDA must consider an AoA done under study guidance from CAPE before Milestone A, or early experimentation with a combatant commander in its place (10 U.S.C. 4251). The November 2025 Warfighting Acquisition System memo goes further and tells DoD to replace AoAs with competitive prototyping where it can.
What happens if a program misses its Acquisition Program Baseline?
If a program's costs exceed APB thresholds, it triggers reporting requirements. For ACAT I programs, unit cost growth of 15% or more above the current APB (or 30% above the original) is a "significant" Nunn-McCurdy breach and requires notification to Congress. Growth of 25% or more above the current APB (or 50% above the original) is a "critical" breach, and DoD must either certify that the program is essential to national security or terminate it. Below ACAT I, APB breaches trigger internal DoD reporting and may require a program restructure, but there is no mandatory congressional notification.