What the FY2027 request buys
Verbatim from the R-2A exhibit for project 1662 of PE 0204136N. 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.
Continued development efforts to remove the dependency on the JMPS Framework, while still running on a client Windows laptop with the ability to pull the UPCs out of the JMPS runtime, pull collaboration data (where available) from the web server, and reduce the friction in going to-and-from the brick. Specifically working the AEA UPC systems development, including software development, JMPS-Continuum two-way data transfer, library builds for GB1 and GB2, ALQ-218 planning, jammer planning, JME planning, MTRM, and the automation MVP. F/A-18 UPC systems development, including component communication methodology, code design for LRASM C-1 / C-3, Blue Angels, EWDS dependencies, Harpoon II+, and overall data migration and execution of Continuum data sources. Continuous/agile integration testing and evaluation will be conducted.
FY2026 to FY2027 decrease of $9.359M due to realignment of CMPC requirements
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.
Continued development efforts to remove the dependency on the JMPS Framework, while still running on a client Windows laptop with the ability to pull the UPCs out of the JMPS runtime, pull collaboration data (where available) from the web server, and reduce the friction in going to-and-from the brick. Specifically working the AEA UPC systems development, including software development, JMPS-Continuum data transfer, order of battle and map visuals, and the automation MVP. F/A-18 UPC systems development, including component communication methodology, code design for RNAV and weapons, and overall data migration and execution of Continuum data sources. Continuous/agile integration testing and evaluation will be conducted.
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 | 18.0 |
| FY2026 | Enacted | 21.2 |
| FY2027 | Request | 11.8 |
This activity is 4.6% of project 1662's FY2027 request and 4.4% of PE 0204136N'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.
12 activities in project 1662
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.