What the FY2027 request buys
Verbatim from the R-2A exhibit for project 2213 of PE 0605215N. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.
- 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.
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.
FY2026: the year under way
Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.
-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.
Three years, and no five-year plan
An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 83.2 |
| FY2026 | Enacted | 75.8 |
| FY2027 | Request | 58.4 |
This activity is 82% of project 2213's FY2027 request and 71% of PE 0605215N's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.
3 activities in project 2213
Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the project page.