Major Force Programs: The Twelve Buckets of the FYDP
There are two ways to describe a defense dollar and they do not line up. Congress appropriates by account: an amount of Army procurement money, available for three years. The Department programs by mission: everything it takes to field and sustain special operations forces, regardless of which account the money came from or which service holds it. The Major Force Program is the second structure. Learning to read it is how you find money that an appropriation table will not show you.
| Field | Value |
|---|---|
| What it is | The mission-oriented aggregation layer of the FYDP |
| Count | Twelve, numbered MFP-01 through MFP-12 |
| Statutory hook | 10 U.S.C. § 222(b) |
| Structure authority | FYDP Structure Handbook (Feb. 2014), managed by OSD CAPE. Supersedes DoD 7045.7-H (Apr. 2004) |
| Where it appears | The FYDP and DoD internal program review. Never in an appropriations act |
What an MFP actually is
An MFP is an aggregation of program elements that reflects a force or support mission of the Department and contains the resources necessary to achieve an objective or plan. That definition comes from the Defense Acquisition University glossary by way of CRS R45252, and the original handbook language is nearly identical.
The reason the construct exists is stated cleanly in the 2004 structure handbook: the FYDP “crosswalks the Department’s internal review structure (which is primarily output oriented) with the congressional review structure (which specifies inputs to the Department).” Congress buys inputs. The Department manages outputs. The MFP is the translation layer between them.
The appropriations side is where legal authority lives. As the DoD Financial Management Regulation Volume 2A puts it, “Appropriation accounts form the structure for the President’s budget request and are the basis for congressional action.” MFPs appear nowhere in an appropriations act. A committee cannot fence an MFP. It can only fence the accounts and lines that happen to carry that MFP’s program elements, which is precisely why the boundary between MFPs becomes contested during programming rather than during appropriation.
The twelve
Six are combat force programs, marked below with a dagger. Six are support programs. The current list is from CRS In Focus IF10831, “Defense Primer: Future Years Defense Program”; scope descriptions are from DoD 7045.7-H, which remains the best publicly available text even though it has been formally superseded.
| MFP | Title | What rides in it |
|---|---|---|
| 01 † | Strategic Forces | Organizations and weapon systems with intercontinental or transoceanic inter-theater missions. Strategic offensive and defensive forces plus their operational headquarters and organic support. |
| 02 † | General Purpose Forces | Forces whose mission responsibilities are limited to one theater at a time. Force-oriented PEs, associated commands, organic logistics, deployable support, JCS-directed exercises, war reserve materiel and ammunition. The largest MFP, slightly over a third of DoD funding. |
| 03 † | Command, Control, Communications, Intelligence, and Space | Intelligence, security and communications functions, plus mapping and geodesy, weather, oceanography, nuclear weapons operations, satellite control. Carve-out: intelligence and communications specifically identifiable to a mission in another program go to that other program instead. |
| 04 † | Mobility Forces | Airlift, sealift, traffic management, water terminal activities, direct-funded and through the working capital fund. |
| 05 † | Guard and Reserve Forces | Reserve component training units supporting the other programs. PE positions 3 and 4 identify which active program the reserve unit relates to. |
| 06 | Research and Development | The development pipeline. Nearly all RDT&E program elements in budget activities 1 through 6 sit here. See the coding rule below, because this is where most misreadings happen. |
| 07 | Central Supply and Maintenance | Centrally managed supply, maintenance and service activities. Depot maintenance, supply management, industrial preparedness, commissaries. |
| 08 | Training, Medical, and Other General Personnel Activities | Training and education, personnel procurement, health care, PCS travel, family housing. Excludes training organic to a program elsewhere. |
| 09 | Administration and Associated Activities | Departmental and major headquarters administration, construction planning and design, public affairs, claims, criminal investigations. |
| 10 | Support of Other Nations | Military assistance, foreign military sales, NATO infrastructure, humanitarian assistance. |
| 11 † | Special Operations Forces | Force-oriented special operations forces, active and reserve, including command organizations and directly related support units. Office of primary responsibility is LIC. See MFP_2_vs_MFP_11. |
| 12 | National Security Space | The unified aggregation of national security space programs, created to give Congress visibility into space spending otherwise scattered across services and agencies. Includes some classified programs. Generally excludes NGA and NRO. |
† Combat force program.
Two corrections worth carrying
It is twelve, not eleven. A great deal of secondary writing still says eleven, because that was the count for decades and it is what the 2004 handbook says. MFP-12 was added in 2015.
MFP-12 is National Security Space, not “Environmental Programs.” This error circulates widely. “Environmental Programs” is a special-analysis exhibit category in the O&M budget justification, not a Major Force Program. No authoritative source has ever identified an MFP by that name.
Where the two newest MFPs came from
Only two categories have been added since the construct was created in the McNamara era, and both were acts of Congress forcing visibility onto the Department.
MFP-11, Special Operations Forces (1986). Created by the Nunn-Cohen Amendment, § 1311(c) of the FY1987 National Defense Authorization Act, Pub. L. 99-661, Nov. 14, 1986, 100 Stat. 3985, which directed the Secretary of Defense to “create for the special operations forces a major force program category” in the Five-Year Defense Plan. Note carefully where that language lives: it is a statutory note to 10 U.S.C. § 167, not text in the body of the section. Congress had to repeat the instruction in the FY1988-89 NDAA before it took. See MFP_2_vs_MFP_11 and Title_10_Structure.
MFP-12, National Security Space (2015). Created by statute at 10 U.S.C. § 239(a), added by § 1601(a)(1) of the FY2016 NDAA, Pub. L. 114-92, Nov. 25, 2015, 129 Stat. 1095, directing the Secretary to “establish a unified major force program for national security space programs.” Before it existed, space was tracked as a “virtual program” defined inside the existing PE structure, which is exactly why historical space funding is so hard to trace.
The pattern is worth noticing. In both cases Congress could not see a mission it cared about, because the money was distributed across services and accounts. Creating an MFP was the remedy. An MFP is fundamentally an oversight instrument.
The statutory hook
The organizing requirement sits in 10 U.S.C. § 222(b), “Future-years mission budget”:
The future-years mission budget shall be consistent with the future-years defense program required under section 221 of this title. In the future-years mission budget, the military programs of the Department of Defense shall be organized on the basis of major force programs.
10 U.S.C. § 221 is the neighboring provision requiring the FYDP itself be submitted to Congress within five days of the President’s budget. It does not define or enumerate MFPs. When you need a citation for the MFP construct generally, § 222(b) is the one.
How to read an MFP off a program element number
This is the practical skill, and it is mechanical. Positions 1 and 2 of a program element code are the Major Force Program.
0 6 0 5 3 3 0 A
│ │ │ │ └─┴─┴── serial and component (A = Army)
│ │ └─┴──────── positions 3-4: in MFP-6, the RDT&E budget activity (05 = BA-5)
└─┴──────────── positions 1-2: MAJOR FORCE PROGRAM (06 = Research and Development)
So 0605331A (NGC2 C2 Applications) is MFP-6. 0310704A (WIN-T) is MFP-3. 0203728A (JADOCS) is MFP-2. 1160480BB (SOF Tactical Vehicles) is MFP-11.
The rule that trips people up. Per FMR Volume 2B, Chapter 5, RDT&E program elements in budget activities 1 through 6 carry 06 in the first two positions, because development is its own Major Force Program. But budget activity 7 program elements, Operational Systems Development, instead carry the MFP of the fielded system. That is why a single appropriation, in a single budget activity, contains program elements sitting in several different MFPs at once.
The consequence is that a conventional program changes MFP over its life. It is MFP-6 while in development, then takes on MFP-2 or MFP-3 when it fields and moves to BA-7. See The asymmetry that actually matters for why special operations programs do not work this way.
The three axes
CRS describes the FYDP as examined in three dimensions, and holding all three in mind at once is the whole discipline:
graph TD F["FYDP<br/>every programmed dollar"] F --> C["COMPONENT<br/>Army, Navy, SOCOM, agencies<br/><i>who programs it</i>"] F --> M["MAJOR FORCE PROGRAM<br/>MFP-01 … MFP-12<br/><i>what mission it serves</i>"] F --> A["APPROPRIATION TITLE<br/>RDT&E, Procurement, O&M, MILPERS<br/><i>what Congress voted on</i>"] style F fill:#1a365d,color:#fff style C fill:#2c5282,color:#fff style M fill:#b7791f,color:#fff style A fill:#2b6cb0,color:#fff
A single MFP draws from many appropriation titles. A single appropriation title feeds many MFPs. The cleanest illustration is RDT&E, which is the one case where the same words name both an appropriation title and an MFP, and even there they are not the same thing: MFP-6 contains program elements funded by more than just the RDT&E appropriation, and RDT&E dollars appear in other MFPs.
MFP versus the vertical chain
DoD_Budget_Hierarchy teaches the vertical chain: appropriation, then budget activity, then program element, then project. That chain is correct and it is how money is executed. The MFP is a different axis entirely, and the distinction is worth stating precisely.
| Appropriation title | Budget activity | Program element | Major Force Program | |
|---|---|---|---|---|
| Set by | Congress | Congress and Comptroller | OSD CAPE | OSD CAPE via the FYDP |
| Crosses appropriations? | n/a | Never | Rarely | Always can |
| Crosses services? | No | No | No | Yes |
| Carries legal budget authority | Yes | Within the account | Within the account | No |
| Appears in an appropriations act | Yes | Yes | Often | Never |
| Orientation | Input | Input | Both | Output and mission |
A budget activity is a subdivision within one appropriation account and can never leave it. An MFP is an aggregation across accounts and services. They are encoded in different positions of the same program element number, which is about as direct a proof of orthogonality as the Department offers.
Why this matters commercially
It tells you who your customer actually is. The MFP on a program element tells you which organization programmed the money and therefore who must be convinced years before a contract exists. See MFP_2_vs_MFP_11 for the case where this is sharpest.
It tells you when a fight is winnable. MFP tags shape programming and budgeting. RAND’s observation in RR-360 is that the funding actually available in organizational budgets “has lost these MFP-related tags by the time funds are appropriated.” The consequence for anyone selling: the argument over which pot pays for your capability is won or lost in the requirements and POM phases, not at award.
It is how consolidation gets detected. When program elements are collapsed into new lines, the MFP prefix of the new line tells you whether money moved across mission categories, not merely across program names. NGC2 is the current worked example: donor lines from MFP-2 and MFP-3 were folded into new MFP-6 lines.
See also
- MFP_2_vs_MFP_11 for the SOF-peculiar versus service-common boundary, the sharpest MFP question in practice
- PPBE_Process for the cycle that produces the FYDP
- DoD_Budget_Hierarchy for the vertical appropriation chain
- Title_10_Structure for the statutory architecture, including § 167
- NGC2 for a live consolidation crossing MFP boundaries
- Congressional_Budget_Process | Unfunded_Requirements | Program Elements
Sources
- CRS In Focus IF10831, “Defense Primer: Future Years Defense Program (FYDP)”
- CRS R45252, “United States Special Operations Command Acquisition Authorities”
- DoD 7045.7-H, “Future Years Defense Program (FYDP) Structure,” April 2004 (superseded by DoDD 7045.14, Jan. 25, 2013; scope language retained here as the best public text)
- DoD 7000.14-R Financial Management Regulation, Volumes 2A and 2B
- 10 U.S.C. § 221, § 222, § 239