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.
- Product Development
- Support
- Test and Evaluation
- Management Services
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.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 13.4 |
| FY2026 | Enacted | 15.6 |
| FY2027 | Request | 25.1 |
| FY2028 | Outyear | 31.9 |
| FY2029 | Outyear | 32.0 |
| FY2030 | Outyear | 31.4 |
| FY2031 | Outyear | 32.0 |
1 accomplishment / planned program
The R-2A exhibit — the only level of the budget that describes work that has not happened yet. Activities carry the prior, current and budget year only, no five-year plan. Each describes FY2027 work in enough detail to have its own page; the rest are shown here in full. Coverage is partial across the corpus, so count activities, never total them.
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 →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.