# Collaborative Mission Planning Continuum (CMPC) Development

**R-2A activity** of project 2213 — Mission Planning  
**Program element:** 0605215N — Mission Planning  
**Component:** U.S. Navy · **Budget Activity:** 5  
**Vintage:** President's Budget PB2027  
**Canonical URL:** https://hitchintel.com/programs/0605215N/2213/a0  
**Parent:** https://hitchintel.com/programs/0605215N/2213

## Summary

This activity requests $58.4M in FY2027, 82% of project 2213, down 23% on FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

## What the FY2027 request buys

**FY2027 planned work.** - The CMPC continues to deliver advanced collaborative and single platform mission planning capabilities for the Carrier Air Wing, anti-submarine warfare, and amphibious assault mission areas. Development continues at all appropriate security classification levels. - Continue transition from the legacy JMPS-M program to CMPC. - Engineering and design of post-mission capabilities and tools. - Continue engineering design and software development activities to implement CMPC functionality on mobile computing devices. Engineering design will ensure data transfer compatibility with EKB and MAGTAB devices. - Continue effective multi-platform and single platform, multi-domain data strategy implementation. - Continue implementation of a multi-domain architecture supporting air wing of the future and delivery of capabilities to the warfighter. - Continue development and deliveries of software and hardware products supporting operations in both land-based and shipboard environments. This work includes any continued non-recurring engineering design required to support CMPC deployments aboard various classes of ships including CVN, LHA/LHD, and DDG class ships. Additionally, the effort includes the software development, optimization, and network integration/compatibility necessary for deployments in stand- alone, networked, and cloud-based environments at all classification levels. - Delivery of capabilities associated with integration of external systems and continued non-recurring engineering design activities to integrate with additional external systems.

**FY2026 to FY2027 change.** FY 2026 to FY 2027 decrease due to a reduced level of software development, deferring the implementation of DevSecOps processes and the onboarding of additional development teams from other platforms.

## Before the request year

**FY2026 plans — current year.** -The CMPC continues to deliver advanced mission planning capabilities for the Carrier Air Wing, anti-submarine warfare, and amphibious assault mission areas. Development continues at all appropriate security classification levels. -Continue transition from the legacy JMPS-M program to CMPC. -Continue engineering design and software development activities to implement CMPC functionality on mobile computing devices. Engineering design will ensure data transfer compatibility with EKB and MAGTAB devices. -Continue effective multi-platform, multi-domain data strategy implementation. -Continue engineering design and implementation of a multi-domain architecture supporting air wing of the future. -Continue development and deliveries software and hardware products supporting operations in both land-based and shipboard environments. This work includes any continued non-recurring engineering design required to support CMPC deployments aboard various classes of ships including CVN, LHA/LHD, and DDG class ships. Additionally, the effort includes the software development, optimization, and network integration/compatibility necessary for deployments in stand- alone, networked, and cloud-based environments at all classification levels. -Continue non-recurring engineering design activities to integrate with external systems -Continue implementation of software DevSecOps and processes to achieve continuous integration & continuous deployment. The effort includes on-boarding additional development teams from other platforms (e.g., P8, E-2, V-22, CH-53K, H-1, C-130), weapons (JDAM, SDB, LRASM), and common mission planning components.

## Funding

| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 83.2 |
| FY2026 | Enacted | 75.8 |
| FY2027 | Request | 58.4 |

> Prior, current and budget year only — an R-2A activity carries no five-year plan. It sums exactly into its project in the request year and not necessarily in any other.

## Other activities in project 2213

- [Standardized Tester of Reprogrammable Munitions (STORM) / Common Munitions BIT Reprogramming Equipment Cyber Enhanced (CMBRE CE)](https://hitchintel.com/programs/0605215N/2213/a1) — FY2027 10.4
- Joint Mission Planning System Expeditionary (JMPS-E) — FY2027 2.2

## Source & machine access

- **Source:** FY2027 Department of the Navy RDT&E Budget Justification, Exhibit R-2A, PE 0605215N project 2213 (PB PB2027). Narrative is the government's own text.
- **No marks, no contractors at this grain** — congressional marks land on the program element and R-3 performers on the project.
- **MCP:** `mcp.hitchintel.com` — `budget_get_activity`.

*HitchAI is an independent intelligence service, not affiliated with the U.S. Department of Defense. Budget figures are requests/estimates, not obligations.*