# Next Generation Naval Mission Planning System (NGNMPS)

**R-2A activity** of project 1662 — F/A-18 Improvement  
**Program element:** 0204136N — F/A-18 Squadrons  
**Component:** U.S. Navy · **Budget Activity:** 7  
**Vintage:** President's Budget PB2027  
**Canonical URL:** https://hitchintel.com/programs/0204136N/1662/a9  
**Parent:** https://hitchintel.com/programs/0204136N/1662

## Summary

This activity requests $11.8M in FY2027, 4.6% of project 1662, down 44% 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.** 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 change.** FY2026 to FY2027 decrease of $9.359M due to realignment of CMPC requirements

## Before the request year

**FY2026 plans — current year.** 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.

## Funding

| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 18.0 |
| FY2026 | Enacted | 21.2 |
| FY2027 | Request | 11.8 |

> 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 1662

- [Advanced Electronic Warfare (ADVEW)](https://hitchintel.com/programs/0204136N/1662/a0) — FY2027 63.3
- [Multi-System Integration (MSI)](https://hitchintel.com/programs/0204136N/1662/a7) — FY2027 59.2
- [Automatic Ground Collision Avoidance System (AGCAS) E/F/G](https://hitchintel.com/programs/0204136N/1662/a1) — FY2027 36.1
- [F/A-18 Beyond Line Of Sight (BLOS) Comms](https://hitchintel.com/programs/0204136N/1662/a2) — FY2027 33.4
- [Digital Video Map Computer-Upgrade (DVMC-U)](https://hitchintel.com/programs/0204136N/1662/a4) — FY2027 14.7
- Brizo Beacon — FY2027 10.2
- F/A-18 Obsolescence Redesign — FY2027 9.5
- Flight Plan Engineering / System Configuration Set Development and Integration — FY2027 9.1
- USMC Capability Upgrades — FY2027 6.1
- F/A-18 E/F/G Network Cyber Defense — FY2027 5.0
- Live Virtual Constructive (LVC) Aircraft Integration — FY2027 0.0

## Source & machine access

- **Source:** FY2027 Department of the Navy RDT&E Budget Justification, Exhibit R-2A, PE 0204136N project 1662 (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.*