R-2A Activity · President's Budget PB2027

Mission Planning Environment (MPE)

FY2027 Request
$10.2M
▼ 22% vs FY2026
HitchAI read

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

FY2027 Request
$10.2M
▼ 22% vs FY2026
FY2026 Enacted
$13.1M
▲ 30% vs FY2025
FY2025 Actual
$10.0M
Prior year
Planned work

What the FY2027 request buys

Verbatim from the R-2A exhibit for project 2558 of PE 0604840N. 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.

FY2027 planned work

Complete development support for F-35 Mission Planning capability enhancements identified in approved requirements documents for Block 4 and modernization efforts within the mission planning support hardware and software. Improve the common, tailorable MPSE software suite that supports all developmental and fielded OFP/ SDL releases, as well as introducing a virtualized environment that reduces development build times and administrative burdens for squadrons. Further enhance F-35 Next Generation Mission Planning program, focusing on development and certification of Ground Data Receptacle replacement, meeting latest cybersecurity directives. Continue fielding agile increments of cloud-developed NextGen Open Mission Systems (NOMS) mission planning software, leveraging DevSecOps development pipeline; complete development of classified components on IL6+ JPO Cloud environment. Continue efforts to improve data transfer layer for improved operational data movement. Continue to build upon MPSE efforts to partner with government organizations for software development and contract directly with equipment suppliers, and continue to reduce overhead costs and management burdens.

FY2026 to FY2027 change

When considering the FY2027 mandatory funding in addition to discretionary funding, the increase from FY2026 to FY2027 reflects funds needed for Block 4 capabilities included in Next-Generation Mission Planning Environment development and Air System Alignment, which is required to ensure mission readiness.

Before the request year

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.

FY2026 plans — current year

Continue development support for F-35 Mission Planning capability enhancements identified in approved requirements documents for Block 4 and modernization efforts within the mission planning support hardware and software. Improve the common, tailorable MPSE software suite that supports all developmental and fielded OFP/ SDL releases, as well as introducing a virtualized environment that reduces development build times and administrative burdens for squadrons. Further enhance F-35 Next Generation Mission Planning program, focusing on development and certification of Ground Data Receptacle replacement, meeting latest cybersecurity directives. Field first iteration of cloud developed NextGen Open Mission Systems (NOMS) mission planning software, leveraging DevSecOps development pipeline; begin development of classified components on IL6+ JPO Cloud environment; improve interoperability capabilities to support COCOM requirements. Continue efforts to improve data transfer layer for improved operational data movement. Build upon MPSE efforts to partner with government organizations for software development and contract directly with equipment suppliers, continuing to reduce overhead costs and management burdens.

Money

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.

010.0FY25ACTUAL13.1FY26ENACTED10.2FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual10.0
FY2026Enacted13.1
FY2027Request10.2

This activity is 51% of project 2558's FY2027 request and 2.4% of PE 0604840N'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.

Where this sits

2 activities in project 2558

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.

Mission Planning Environment (MPE) — this activity$10.2M ▼ 22%
Joint Reprogramming Environment (JRE)$9.9M ▼ 3%
Source
FY2027 Department of the Navy RDT&E Budget Justification · Exhibit R-2A · PE 0604840N, project 2558 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0604840N/2558/a1.md · MCP mcp.hitchintel.combudget_get_activity