RDT&E Program Element · President's Budget PB2027

LCS Mission Modules

PE 0603596N·U.S. Navy·Approp. 1319 — RDT&E·BA4 — Advanced Component Development & Prototypes
FY2027 Request
$46.2M
⚑ Contested — House cuts 65%
HitchAI read

U.S. Navy funding ramps 18% to a $46.2M request in FY2027 — the program's peak, sustained across the five-year plan. In the FY2027 defense authorization, the House cut 65% (to $16.2M); the Senate funded it in full; House appropriators funded it in full. AAC leads the industry work, though an unusually large share flows to government labs and warfare centers.

FY2027 Request
$46.2M
▲ 18% vs FY2026
House mark
$16.2M
▼ $30.0M vs request
FY2026 Enacted
$39.3M
In law

Roll-up of 2 projects. Projects are the summable leaves — the PE total is their sum, never added to it.

For fiscal year 2027, the U.S. Navy is requesting $46.2M for LCS Mission Modules under RDT&E program element 0603596N, up 18% over FY2026. In the FY2027 defense authorization, House moved to cut it to $16.2M.

Funding trajectory

Funding profile, FY2025–FY2031

Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure.

25028.5FY25ACTUAL39.3FY26ENACTED46.2FY27REQUEST39.3FY2841.8FY2941.3FY3042.1FY31HOUSE
Actual Enacted Request Outyear (FYDP) House mark
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual28.5
FY2026Enacted39.3
FY2027Request46.2
FY2028Outyear39.3
FY2029Outyear41.8
FY2030Outyear41.3
FY2031Outyear42.1
Where it sits

Acquisition lifecycle

This program is funded in RDT&E Budget Activity 4 — Advanced Component Development & Prototypes.

Complete
Research
BA 1–2
Complete
Advanced Technology
BA 3
Current
Prototyping
BA 4
Later
Development & Fielding
BA 5–7
Inside the program element

2 projects roll up into PE 0603596N

Projects are the summable leaves — the PE total is their sum, never added to it. Program elements and projects carry the full five-year plan; activities stop at the budget year. This PE moves 18% overall, which can hide much larger swings below.

Congressional action

The request is contested

Committee marks on the FY2027 request. Adds and cuts are reconciled in conference before they become law.

RequestPresident's Budget
$46.2M
House NDAA (HASC)HASC
$16.2M −$30.0M · −65%
Senate NDAA (SASC)SASC
$46.2M full · +$0
House Approps (HAC-D)HAC_D
$46.2M full · +$0
▲ $30.0M chamber gap — unresolved as of 2026-07-27. These are FY2027 authorization marks (NDAA); appropriations and the conference agreement may differ.
Who's building it

Where the FY2027 request goes

Performers named in the R-3 exhibit, resolved into industry, government-lab, and unspecified shares. Budget-justification contract funding, not obligations.

AAC
$8.4M · 18%
4.0 Command, Control, Communication, Computers, Collaboration and Intelligence (C5I) · CPFF
NIWC PAC
$1.0M · 2.1%
4.0 Command, Control, Communication, Computers, Collaboration and Intelligence (C5I)
Where FY2027 funding flowsShare$M
Industry primes23%10.6
Government labs & warfare centers64%29.7
Other / unspecified13%6.0
FY2027 request100%46.2
See AAC's full federal contract ledger members
Program detail

Mission & acquisition strategy

The Littoral Combat Ship (LCS) Mission Modules (MM) Program Element (PE) provides funds for detailed design, development, issue resolution, certification, integration, and testing of the LCS MM. LCS is a fast, agile, and networked surface combatant with capabilities optimized to defeat asymmetric threats and ensure naval and joint force access into contested littoral regions. It uses open-systems architecture design, modular weapons, sensor systems, and a variety of manned and unmanned vehicles to expand the battle space and project offensive power into the littorals.

The LCS Mission Module Acquisition Strategy is employing an incremental procurement approach to allow for the rapid introduction of additional capabilities as system technology matures. This phased plan provides incremental fielding of capability through the introduction of mature programs of record into the respective Mission Packages until the full baseline capability defined in the Capability Development Document (CDD) is reached.

Project 3129, 2550 — LCS Mission Package Development
  • Product Development
  • Support
  • Test and Evaluation
  • Management Services
Ask Hitch

Ask this program element

Answers are generated from the figures on this page — the FY2027 justification exhibits and the marks tracked above — and nothing else is consulted. Confirm any figure against the cited exhibit before you use it externally.

H
Questions this page can answer
How does the FY2027 request compare with FY2026, and what does the five-year plan show?What did House do to this request, and what is still unresolved?Which project inside PE 0603596N is growing fastest, and which is shrinking?How is the FY2027 request split between industry and government performers?

This page carries the budget justification and the NDAA marks — nothing else. For what AAC has actually been obligated, the ledger is at hitchintel.com/vendors; for live solicitations, hitchintel.com/opportunities. Both are member surfaces.

Provenance

Cite this page

Sources
FY2027 Department of the Navy RDT&E Budget Justification · Exhibits R-2 / R-3 · PE 0603596N (President's Budget PB2027) — and FY2027 NDAA committee marks, as tracked 2026-07-27.
Suggested citation
HitchAI, "LCS Mission Modules (PE 0603596N)," federal budget intelligence, PB2027 vintage. hitchintel.com/programs/0603596N
Machine access
Markdown twin /programs/0603596N.md · MCP mcp.hitchintel.combudget_get_program_element, budget_get_cong_marks
FY2027 Request
$25.1M
▲ 61% vs FY2026
FY2026 Enacted
$15.6M
▲ 16% vs FY2025
FY2025 Actual
$13.4M
Prior year

LCS Mission Package Development — one RDT&E project inside PE 0603596N. Congressional marks are recorded on the program element, not on a project.

Project 3129 — LCS Mission Package Development — requests $25.1M in FY2027, 54% of the $46.2M requested for program element 0603596N. Year over year it grows 61% against FY2026.

Funding trajectory

Project 3129 funding, FY2025–FY2031

Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.

25013.4FY25ACTUAL15.6FY26ENACTED25.1FY27REQUEST31.9FY2832.0FY2931.4FY3032.0FY31
Actual Enacted Request Outyear (FYDP)
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual13.4
FY2026Enacted15.6
FY2027Request25.1
FY2028Outyear31.9
FY2029Outyear32.0
FY2030Outyear31.4
FY2031Outyear32.0
Inside the project

1 accomplishment / planned program

The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.

FY2025 actual$13.4M
FY2026 enacted$15.6M
FY2027 request$25.1M

Mission Package Computing Environment (MPCE) - AN/SYK-31/ Mission Module Online Boat Trainer (MMOBT): - Develop Technology Refresh of MPCE and certify version 2.X - Complete integration testing of MPCE v2.1 with Integrated Combat Management System (General Dynamics) and COMBATSS 21 (Lockheed) - Complete integration and testing of MPCE…

Read the FY2027 plan →
Project 3129 — every activity in full →
Who's building it

Named performers on project 3129

Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.

AAC
$8.4M · 34%
NIWC PAC
$1.0M · 3.9%
SEA 05
$0.6M · 2.5%
Booz Allen
$0.5M · 2.1%
Project detail

What project 3129 buys

The LCS Mission Modules Common Equipment consists of the development and integration of vital C5I products required by all Mission Packages to provide common hardware interfaces, computer operating environment, communications systems, aviation interface systems, UxV interfaces and portable development & integration test-sets. Common hardware interfaces include definition, installation, and control of mechanical, electrical, and cooling requirements common to all mission packages. The Mission Package Computing Environment (MPCE) provides common services and Operating Environment to support all Mission Package Application Software (MPAS) and Open Architecture Products. The Multi-Mission Software Architecture (MMSA) will provide a framework that enables hybrid mission packages such as combining Mine Countermeasures (MCM) with the Surface-to-Surface Missile Module (SSMM) to operate concurrently without mission package swaps, improving cyber survivability and providing common control for unmanned systems. The Multi-Vehicle Communications System (MVCS) enables the control and data exchange of simultaneous unmanned mission vehicles and the ship. Aviation interface systems include integration and management of data communications, data processing, and physical hardware interfaces such as common equipment and containers used by all mission packages. Development and integration test-sets provide a mobile operating environment installed in the Mission Package Portable Control Stations (MPPCSs) to serve as a surrogate ship during mission package development and integration test events at test ranges. MPCE 2.X baseline was split to support the evolution of different versions of the LCS, MPCE v2.0 for LCS Lethality and Survivability and MPCE v2.1 for non-Lethality and Survivability hulls.

R-3 lines of work
  • Product Development
  • Support
  • Test and Evaluation
  • Management Services
FY2027 Request
$21.2M
▼ 11% vs FY2026
FY2026 Enacted
$23.7M
▲ 57% vs FY2025
FY2025 Actual
$15.1M
Prior year

Mine Countermeasure (MCM) Mission Package — one RDT&E project inside PE 0603596N. Congressional marks are recorded on the program element, not on a project.

Project 2550 — Mine Countermeasure (MCM) Mission Package — requests $21.2M in FY2027, 46% of the $46.2M requested for program element 0603596N. Year over year it falls 11% against FY2026.

Funding trajectory

Project 2550 funding, FY2025–FY2031

Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.

015.1FY25ACTUAL23.7FY26ENACTED21.2FY27REQUEST7.4FY289.8FY299.9FY3010.1FY31
Actual Enacted Request Outyear (FYDP)
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual15.1
FY2026Enacted23.7
FY2027Request21.2
FY2028Outyear7.4
FY2029Outyear9.8
FY2030Outyear9.9
FY2031Outyear10.1
Inside the project

1 accomplishment / planned program

The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.

FY2025 actual$15.1M
FY2026 enacted$23.7M
FY2027 request$21.2M

- Integrate Near Surface Neutralization into MP - Develop Near Surface Neutralization support equipment and container - MCM MP MPAS Development - Integrate Multi-Mission System Architecture - Commence integration of alternative minehunting sonar to MP software and hardware baseline

Read the FY2027 plan →
Project 2550 — every activity in full →
Project detail

What project 2550 buys

The MCM Mission Package (MP) employs an incremental development approach to deliver capability which allows the continued insertion of mature capabilities throughout the life of the program without the need for modifications to the seaframes. Future MCM MP capabilities will be considered when joint warfighting objectives or changing threats create new operational capability requirements that cannot be met by current mission package designs, or when new technological opportunities allow significant progress toward delivering cost effective enhanced capabilities. Future mission module increments can be tested, constructed, and incorporated into existing mission packages, one of the most important benefits of LCS modular design. MCM MP successfully completed IOT&E in Q4FY22 and achieved Initial Operational Capability (IOC) on 31MAR 2023. MCM MPs were deployed to C5F in Q2FY5 The MCM MP will counter deep, shallow, and tethered mines in the littorals without putting sailors in the minefield. When the MCM MP is embarked, LCS is capable of conducting detect-to-engage operations (hunting, sweeping, and neutralization) against very shallow to deep-water sea mine threats. The MCM MP provides these capabilities through the use of sensors and weapons deployed from an MH-60S multi-mission helicopter, unmanned offboard vehicles, and support equipment/containers. MCM MP has a portable command and control station allowing operations from Vessel of Opportunity (VOO) or shore. The MCM MP consists of the following modules: - Unmanned Minesweeping (UMS) Module: Unmanned Influence Sweeping System (UISS) (USV + Minesweeping Payload Delivery System (PDS)) - Airborne Mine Neutralization (AMN) Module: Airborne Mine Neutralization System (AMNS) + MH-60S helicopter - Near Surface Detection (NSD) Module: Airborne Laser Mine Detection System (ALMDS) + MH-60S helicopter - Remote Minehunting (RMH) Module: Unmanned Surface Vehicle (USV) + Minehunting PDS + Minehunting Sonar - Near-surface Mine Neutralization (NSN) Module: Barracuda (Barracuda Neutralizer + USV + Mine Neutralization PDS) The program is also investigating implementation of deep mine neutralization and alternative mine hunting sonars in support of force generation.

R-3 lines of work
  • Product Development
  • Test and Evaluation
  • Management Services