DoD Budget Hierarchy

The Comptroller (OUSD(C)) structures defense spending through a strict hierarchy. Every dollar traces from an Appropriation Title down to a Project line item. Understanding this chain is how you follow the money.

The Chain

graph TD
    A["Appropriation Title<br/>(Budget Book)"] --> B["Budget Activity<br/>(BA 1-7)"]
    B --> C["Program Element<br/>(PE#)"]
    C --> D["Project<br/>(R-2/R-3/R-4 Exhibits)"]
    D --> E["Accomplishments<br/>(Line Items)"]

    style A fill:#1a365d,color:#fff
    style B fill:#2a4365,color:#fff
    style C fill:#2c5282,color:#fff
    style D fill:#2b6cb0,color:#fff
    style E fill:#3182ce,color:#fff

Appropriation Titles (Budget Books)

The top-level buckets Congress votes on:

Book	Code	What It Funds
Appropriation_RDT_E_Army	2040	Army research, development, test & eval
Appropriation_RDT_E_Navy	1319	Navy/Marine Corps RDTE
Appropriation_RDT_E_Air_Force	3600	Air Force RDTE
Appropriation_RDT_E_Defense_Wide	0400	SOCOM, DARPA, CDAO, OSD, MDA, etc.
Appropriation_Procurement_Army	2035	Army procurement
Appropriation_Procurement_Navy	1506/1507	Navy/Marine procurement
Appropriation_Procurement_Air_Force	3010/3020	Air Force procurement
Appropriation_Procurement_Defense_Wide	0300	SOF, defense agencies procurement
Appropriation_OM	varies	Operations & Maintenance
Appropriation_MILPERS	varies	Military Personnel
Appropriation_MILCON	varies	Military Construction

Budget Activities (BA) — RDTE Only

Within each RDTE book, money is categorized by maturity:

BA	Name	What It Means	Typical Actors
BA_6_1	Basic Research	Fundamental science	Labs, universities
BA_6_2	Applied Research	Proof of concept	Labs, DARPA, industry
BA_6_3	Advanced Technology Dev	Prototyping	PEOs, DARPA, industry
BA_6_4	Adv Component Dev & Prototypes	System-level prototypes	PEOs, primes
BA_6_5	System Dev & Demonstration	EMD phase	PEOs, primes
BA_6_6	RDT&E Management Support	T&E infrastructure	Test ranges, labs
BA_6_7	Operational System Dev	Post-fielding upgrades	PEOs, sustainment

Why this matters: BA tells you where a program sits in its lifecycle. A BA 6.3 program is still prototyping. A BA 6.5 is in EMD heading toward production. A BA 6.7 is already fielded and getting upgrades. This determines who the buyer is and how to sell.

Program Element (PE#)

The atomic budget unit. Every PE has:

• A unique number (e.g., 1160402BB)
• A parent Appropriation Title
• A parent Budget Activity
• An owning Service Agency
• One or more Projects
• A managing PEO

See: Program Elements

Project

Sub-elements within a PE. Documented in R-exhibits:

• R-2 — Program Element funding summary
• R-3 — Project-level cost detail
• R-4 — Schedule and milestones
• R-4A — Schedule detail

See: Projects

Accomplishments

The most granular level — specific line items within a project, often by fiscal year.

---

The Two Parallel Chains

graph LR
    subgraph "MONEY FLOW (Comptroller)"
        A1[Congress] --> A2[Appropriation]
        A2 --> A3[Budget Activity]
        A3 --> A4[Program Element]
        A4 --> A5[Project]
    end

    subgraph "REQUIREMENTS FLOW (Warfighter)"
        B1[Operational Unit] --> B2[Component Command]
        B2 --> B3[COCOM]
        B3 --> B4[Joint Staff / OSD]
        B4 --> B5[PPBE Process]
    end

    subgraph "ACQUISITION (Bridge)"
        C1[PEO] --> C2[Program Manager]
        C2 --> C3[Program of Record]
        C3 --> C4[Contract / OT]
    end

    B5 -.->|"requirements drive"| A4
    A5 -.->|"funds flow to"| C3
    C4 -.->|"delivers to"| B1

Money flows down from Congress. Requirements flow up from warfighters. The acquisition system bridges them — PEOs manage the programs that turn budget into capability.

See: Acquisition_to_Operational_Mapping

---

The other axis: Major Force Programs

Everything above is the vertical chain, and it is how money is executed. There is a second, orthogonal structure: the Major Force Program.

An appropriation title is what Congress voted on. A budget activity is a subdivision within one appropriation and can never leave it. An MFP is a mission aggregation that cuts across appropriations and across services, used for DoD internal program review in the FYDP. MFPs appear nowhere in an appropriations act.

The two are encoded in different positions of the same PE number, which is the cleanest proof they are independent:

0 6 0 5 3 3 1 A
│ │ └─┴──────── budget activity (05 = BA-5), when MFP is 06
└─┴──────────── Major Force Program (06 = Research and Development)

There are twelve MFPs. The two that decide who buys a capability for special operations are MFP-2 (General Purpose Forces) and MFP-11 (Special Operations Forces). See Major_Force_Programs and MFP_2_vs_MFP_11.