OFFSETOFFSET

MFP-2 versus MFP-11: Who Actually Buys It

12 min read

MFP-2 versus MFP-11: Who Actually Buys It

Every capability sold into special operations runs into one question before it runs into any other: is this thing special operations-peculiar, or is it service-common? The answer decides which organization programs the money, which budget it competes inside, how many years it takes, and who has to say yes. Vendors who lose this fight usually lose it without knowing it was happening, because it is settled during programming, two or more years before anything reaches a contract.

The short version

MFP-2 (and MFP-3)MFP-11
CategoryGeneral Purpose ForcesSpecial Operations Forces
Who programs the moneyThe military departmentUSSOCOM
Who validates the requirementService requirements processSOCOM, under 10 U.S.C. § 167(e)
Whose topline it competes inThe service’s, roughly $250B for the Army in FY2027SOCOM’s, roughly $15.6B in FY2027
Buying customerService program officeSOCOM, via SOF_AT_L
Legal basis§ 165(b) service support obligation§ 167(e)(4) and § 167(g)
Typical cycle to moneyService POM, slower, competes service-wideSOCOM POM, smaller and closer to the user

The two definitions

These are the load-bearing texts. Both derive from DoD Directive 5100.03.

Special operations-peculiar, quoted from USSOCOM Directive 700-2, which sources it to DoDD 5100.3:

Equipment, materiel, supplies and services required for SO activities for which there is no service-common requirement. These are limited to items and services initially designed for, or used by, SOF until adopted for service-common use by other DoD Forces; modifications approved by the Commander […] for application to standard items and services used by other DoD forces.

Service-common, as reproduced by GAO-15-571:

Equipment, materiel, programs, and services adopted by a military service for use by its own forces and activities. These include standard materiel items, base operating support, and the supplies and services provided by a military service to support and sustain its own forces, including those assigned to the combatant commands.

Read those two together and the boundary is defined by negation: SOF-peculiar is what is left after service-common is subtracted. There is no affirmative list. Worse, DoDD 5100.03 acknowledges the definition varies by military department, so the same item can be service-common in one service and SOF-peculiar relative to another. The M4 carbine is service-common to the Army, where it is the standard infantry weapon. To a service that does not issue it as standard, the identical rifle is arguably peculiar.

This is not a drafting failure that someone will eventually fix. It is a permanent seam, and it generates recurring disputes by design.

Why SOCOM can buy at all

Ordinary combatant commands do not buy things. They receive forces from the services and employ them. USSOCOM is the exception, and the exception is statutory.

10 U.S.C. § 167(e)(4), verbatim:

(A) The commander of the special operations command shall be responsible for, and shall have the authority to conduct, the following: (i) Development and acquisition of special operations-peculiar equipment. (ii) Acquisition of special operations-peculiar material, supplies, and services.

Subparagraph (B) lets the commander exercise the functions of head of an agency under chapter 137, the procurement chapter. Subparagraph (C) puts a command acquisition executive on his staff. That officer negotiates memoranda of agreement with the military departments and represents the command in acquisition discussions with them. In practice that is SOF_AT_L.

§ 167(g), verbatim:

In addition to the activities of a combatant command for which funding may be requested under section 166(b) of this title, the budget proposal of the special operations command shall include requests for funding for— (1) development and acquisition of special operations-peculiar equipment; and (2) acquisition of other material, supplies, or services that are peculiar to special operations activities.

That subsection is what makes SOCOM a budget-submitting entity rather than a customer of one. Note that both provisions are bounded by the same adjective. SOCOM’s purchasing authority extends exactly as far as the word “peculiar” extends and no further. The definitional fight is therefore a fight about the scope of a statutory power.

State the MFP relationship precisely, because it is commonly cited loosely: MFP-11 is not a Title 10 term. It is a budget construct created by the statutory note to § 167 from the Nunn-Cohen Amendment. When you need statutory authority, cite § 167(g) and § 167(e)(4), and describe MFP-11 as the FYDP structure through which those requirements are executed. See Title_10_Structure.

Creation was not control

A detail most summaries skip, and it matters for understanding how slowly these things actually move.

Congress ordered the MFP-11 category in November 1986. It did not become SOCOM-controlled money then. Per RAND RR-360, before November 1989 all SOF funding, MFP-11 included, still sat inside the military department budgets. Program Budget Decision 731C, promulgated in December 1989, is what actually moved control of baseline MFP-11 funding from the departments to USSOCOM. Service-common and base operating support funding were explicitly excluded from that transfer, which is the moment the modern boundary hardened.

Three years elapsed between the statutory command and the transfer of control, and Congress had to repeat itself in the interim.

What the services still pay for

10 U.S.C. § 165(b) keeps the services on the hook:

the Secretary of a military department is responsible for the administration and support of forces assigned by him to a combatant command.

SOF personnel remain members of their parent service and count in its end strength. GAO groups the residual service obligation into three categories:

  1. Pay and benefits. Basic pay, bonuses, special pays and retired pay accrual for SOF personnel, out of the services’ military personnel appropriations.
  2. Service-common equipment and goods. Major platforms and commodities: the C-130, the CV-22, the MQ-9, ammunition for service-common weapons.
  3. Support programs and services. Base operating support, facilities, logistics, civilian personnel management, intratheater lift.

The magnitude is the surprising part. GAO found SOCOM estimated service funding supporting SOF at roughly $8 billion annually, which at the time exceeded SOCOM’s own base budget. Service-common money supporting SOF is comparable in size to all of MFP-11. Anyone modeling the SOF market off SOCOM’s budget alone is looking at about half the picture.

The services are also obligated to supply service-common items to SOF at parity: under the SOCOM-department memoranda of agreement, such items are “to be made available to SOF at a rate not less than provided to conventional units.”

The seam that vendors should actually target

Here is the most useful single fact on this page.

MFP-11 money can lawfully modify a service-common platform without SOCOM buying the platform. GAO records SOCOM using special operations-specific funding “to modify service-common systems to meet special operations-peculiar requirements for which there is no broad conventional force need,” citing SOF modifications to the C-130. The service bears the platform cost. SOCOM buys the mission kit.

The commercial reading is direct. If your capability is a modification, an integration, a payload or a software layer riding on something the service already owns, you are on the peculiar side of the line and SOCOM can buy it on its own authority and timeline. If your capability is the platform, you are asking a service to program it, and you are competing against every other service priority.

USSOCOM enforces the same boundary inside its own property system. The USSOCOM Table of Equipment Distribution and Allowance, established in 1992, authorizes MFP-11 funded SO-peculiar equipment and explicitly “will not be used to authorize non-MFP-11 purchased/funded equipment or MFP-11 funded items that are purely administrative in nature such as office furniture.” Even office furniture has to pick a side.

Military construction follows the identical logic, and SOCOM states it plainly in its FY2027 justification: “USSOCOM budgets only for those facilities, specifically for SOF use.” Common support facilities belong to the departments.

What the disputes actually look like

RAND found that funding disputes between USSOCOM and the departments “primarily concern fundamental differences of interpretation about what constitutes Service-common and BOS on one hand and SOF-peculiar on the other.” The documented examples are almost comically mundane, which is the point:

  • A boat dock. Nothing about it was SOF-peculiar, but a geographic combatant command argued it was an MFP-11 expense because Naval Special Warfare boat units would use it.
  • Indigenously procured vehicles. Treated as SOF-peculiar by others simply because the request looked unusual. SOCOM considered them service-common.
  • Dining facilities and billeting on installations with no general purpose forces, argued to be SOF-peculiar despite being universal needs.
  • The M4 carbine, service-common to the Army and arguably peculiar elsewhere.

The pattern: when SOF is the only user present, others reach for MFP-11 regardless of whether the item has any special operations character. SOCOM resists, because its topline is roughly a twentieth of a service’s.

Escalation. When action officers deadlock, the matter goes to the Under Secretary of Defense (Comptroller), who decides and directs the manner of funding. DoDD 5100.03 formally requires disputes be elevated through the Chairman to the Secretary of Defense, but establishes no working-level mechanism. RAND recommended the memoranda of agreement be amended to define service-common per department and to create a dispute process below the level of the SOCOM Commander, noting that the Air Force agreement defines service-common only generically and never defines base operating support at all.

The asymmetry that actually matters

This is the structural point, and it is sharper than the usual framing.

SOF program elements carry MFP-11 across their entire lifecycle. Conventional program elements do not.

Per FMR Volume 2B, RDT&E program elements in budget activities 1 through 6 normally carry 06 in positions 1 and 2, because research and development is its own MFP. Budget activity 7 lines instead carry the MFP of the fielded system.

Now look at SOCOM’s lines in the FY2027 R-1. 1160401BB SOF Technology Development sits in budget activity 2. 1160402BB SOF Advanced Technology Development sits in budget activity 3. Both carry 11, not 06. SOF research and development never leaves MFP-11.

An Army program’s life, by contrast, splits across mission categories:

graph LR
    subgraph CONV["Conventional program"]
        A["Development<br/>MFP-6<br/>PE 06xxxxx"] --> B["Fielded, BA-7<br/>MFP-2 or MFP-3<br/>PE 02xxxxx / 03xxxxx"]
    end
    subgraph SOF["SOF program"]
        C["Development<br/>MFP-11<br/>PE 11xxxxx"] --> D["Fielded<br/>MFP-11<br/>PE 11xxxxx"]
    end
    style A fill:#2b6cb0,color:#fff
    style B fill:#2c5282,color:#fff
    style C fill:#b7791f,color:#fff
    style D fill:#b7791f,color:#fff

The consequence is that SOF capability is traceable end to end as special operations money, by design, which is exactly the visibility Congress legislated in 1986. Conventional capability is not: it changes mission category when it fields, which makes a conventional program harder to follow across its life than a SOF one.

Where SOF networks sit

Directly relevant to any command and control question. SOCOM’s tactical network programs are MFP-11 by construction, because SOCOM may only develop and acquire SO-peculiar items with those funds. TACLAN appears as a USSOCOM-programmed IT investment funded across procurement, RDT&E and O&M inside SOCOM’s own portfolio, alongside SOCRATES and the SOF Information Environment. SOCOM describes the SIE as its own cyberspace weapons system and a critical enabler of its Title 10 responsibilities. PEO Tactical Information Systems owns tactical communications and networks for SOF.

An Army program like NGC2 is not MFP-11 and never will be. Its development lines are MFP-6 and its fielded predecessors were MFP-2 and MFP-3. When SOF formations operate on an Army-funded network, they are operating on infrastructure they did not program, cannot reprioritize, and do not control the roadmap for. Interoperability then becomes a SOCOM-funded integration problem, which loops back to the seam above: the network is the Army’s, the SOF interface to it is SOCOM’s.

SOCOM’s topline, FY2027

From the April 2026 justification books, dollars in thousands:

AppropriationFY2025 actualFY2026FY2027 request
O&M, Defense-Wide9,781,7839,670,54010,891,050
Procurement, Defense-Wide2,530,6092,504,9842,797,358
RDT&E, Defense-Wide1,420,1411,701,5571,620,730
MILCON, Defense-Wide306,000 (appropriation)
Total≈ $15.6B

For scale: the FY2027 national defense topline is roughly 252.8 billion. SOCOM’s request is on the order of 1 percent of the DoD topline and roughly 4 to 6 percent of a single military department. Breaking Defense totals the big three appropriations at about 1 billion in purchasing power to inflation.

The asymmetry is the whole strategic point. SOCOM controls a rounding error, but it controls it directly.

Nobody knows the real total

GAO’s structural finding, and a useful caution against over-precision: “DOD Has Little Visibility over Total Funding Devoted to SOF.” Funding data are tracked in a decentralized way and “neither DOD nor the military services have systematically collected, estimated, or reported total SOF funding needs.” Congress raised this in 2013 and directed SOCOM to provide OP-5 and OP-32 exhibits for each budget subactivity beginning in FY2015. SOCOM complied, but the service-provided half remains substantially unmeasured.

Any number quoted for “total SOF spending” is therefore SOCOM’s own appropriations plus an estimate. Say which you mean.

Practical checklist

Working out which side of the line a capability falls on:

  1. Is there a service-common requirement for this? If any service has adopted it for its own forces, it is service-common to that service, and SOCOM cannot buy it as peculiar.
  2. Was it initially designed for or used by SOF? If yes, it is peculiar until a service adopts it, at which point it converts.
  3. Is it a modification to a standard service item approved by the SOCOM Commander? If yes, it is peculiar even though the base item is not. This is the seam.
  4. Is it urgent and mission-critical per the Commander? There is a peculiar category for that.
  5. If none of the above, it is service-common. Your customer is the service, your timeline is the service POM, and you are competing against the service’s own priorities.

See also

Sources

Graph View

1

click focuses · double-click opens

Backlinks