Roll-up of 2 projects. Projects are the summable leaves — the PE total is their sum, never added to it.
For fiscal year 2027, the U.S. Navy is requesting $82.6M for Mission Planning under RDT&E program element 0605215N, down 31% from FY2026.
Funding profile, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 113.2 |
| FY2026 | Enacted | 120.3 |
| FY2027 | Request | 82.6 |
| FY2028 | Outyear | 74.7 |
| FY2029 | Outyear | 67.3 |
| FY2030 | Outyear | 66.5 |
| FY2031 | Outyear | 60.7 |
Acquisition lifecycle
This program is funded in RDT&E Budget Activity 5 — System Development & Demonstration.
2 projects roll up into PE 0605215N
Projects are the summable leaves — the PE total is their sum, never added to it. Program elements and projects carry the full five-year plan; activities stop at the budget year. This PE moves -31% overall, which can hide much larger swings below.
Stores Planning and Weaponeering Module
Congressional marks
Committee marks on the FY2027 request. Adds and cuts are reconciled in conference before they become law.
Where the FY2027 request goes
Performers named in the R-3 exhibit, resolved into industry, government-lab, and unspecified shares. Budget-justification contract funding, not obligations.
| Where FY2027 funding flows | Share | $M |
|---|---|---|
| Industry primes | 98% | 81.2 |
| Government labs & warfare centers | 1.7% | 1.4 |
| FY2027 request | 100% | 82.6 |
Mission & acquisition strategy
The Mission Planning PE is used to develop automated mission planning systems to support Naval Aviation. (Proj 2213) The Joint Mission Planning System (JMPS) is the designated automated mission planning system for Naval Aviation, supporting over 40 Type/Model/Series (T/M/S) of U.S. Navy and Marine Corps aircraft, expeditionary forces as well as Joint and Coalition forces.
The initial Joint Mission Planning System (JMPS) development effort was a phased evolutionary approach. JMPS is a post Milestone III program and Initial Operational Capability (IOC) occurred in December 2005. Cost Plus Award Fee (CPAF) and Cost Plus Incentive Fee (CPIF) contracts were awarded during initial development. During the down-select process, one contractor was selected to develop the JMPS architecture framework and Version 1.0 basic flight planning components. Additional phases focused on strike planning requirements (i.e., support Precision Guided Missions and other tactical data intensive missions) in order to migrate platforms from legacy mission planning systems to JMPS.
- Product Development
- Support
- Test and Evaluation
- Management Services
Ask this program element
Answers are generated from the figures on this page — the FY2027 justification exhibits and the marks tracked above — and nothing else is consulted. Confirm any figure against the cited exhibit before you use it externally.
This page carries the budget justification and the NDAA marks — nothing else. For what DCS has actually been obligated, the ledger is at hitchintel.com/vendors; for live solicitations, hitchintel.com/opportunities. Both are member surfaces.
Cite this page
/programs/0605215N.md · MCP mcp.hitchintel.com → budget_get_program_element, budget_get_cong_marksMission Planning — one RDT&E project inside PE 0605215N. Congressional marks are recorded on the program element, not on a project.
Project 2213 — Mission Planning — requests $71.0M in FY2027, 86% of the $82.6M requested for program element 0605215N. Year over year it falls 34% against FY2026.
Project 2213 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 101.2 |
| FY2026 | Enacted | 108.3 |
| FY2027 | Request | 71.0 |
| FY2028 | Outyear | 62.5 |
| FY2029 | Outyear | 54.8 |
| FY2030 | Outyear | 54.0 |
| FY2031 | Outyear | 47.8 |
3 accomplishments / planned programs
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
- 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…
Read the FY2027 plan →- Continue development and integration of OEM Munitions Application Program (MAP) software products for Navy and Marine Corps munitions. - Continue non-recurring engineering activities to address software discrepancies discovered during Middle Tier Acquisition, Section 804. - Continue hardware/software integration activities required for…
Read the FY2027 plan →- Complete transition of the JMPS-E software to the CMPC architecture. - Complete development of infrastructure to interface with meteorological, bathymetric, and intelligence databases. - Conduct end-to-end system integration and system test.
Named performers on project 2213
Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.
What project 2213 buys
The Joint Mission Planning System (JMPS) is the designated automated mission planning system for Naval Aviation, supporting over 40 Type/Model/Series (T/M/S) of U.S. Navy and Marine Corps aircraft, expeditionary forces as well as Joint and Coalition forces. The Joint Mission Planning System - Maritime (JMPS-M) enables weapon system employment by providing the information, automated tools, and decision aids needed to rapidly plan aircraft, weapon, or sensor missions, load mission data into aircraft and weapons, conduct mission rehearsal, execute missions, and conduct post-mission analysis. The Joint Mission Planning System -Expeditionary (JMPS-E) is a scalable, tailorable, and collaborative web-based mission planning and execution monitoring tool for Amphibious Squadron staffs embarked with each Amphibious Ready Group and Expeditionary Strike Group. Electronic Kneeboard (EKB) is a mobile computing device configured with various software applications and features to support aircrew during pre-flight planning, in-flight re-planning and mission execution, and post-mission debriefing and analysis. Preflight mission planning, data loading, rehearsals, mission execution and post mission analyses are conducted at all appropriate security classification levels. The Collaborative Mission Planning Continuum (CMPC) formerly called Next Generation Naval Mission Planning System (NGNMPS), will address critical capability gaps and deficiencies in the legacy JMPS that are required for modern 21st century integrated mission-centric and collaborative multi-domain mission planning, execution and analysis. The CMPC will begin replacing Naval Aviation's legacy JMPS no later than FY 2027 while also affordably leveraging prior investments across the systems of systems to deliver integrated and collaborative capability. The CMPC will address technological obsolescence while delivering enhanced capabilities to support the current Air Wing and the Air Wing of the future. The CMPC capability provides advanced multiple aircraft planning capabilities focused on emerging, high-threat mission areas. Current mission planning capabilities support individual aircraft and weapon initialization requirements.
- Product Development
- Support
- Test and Evaluation
- Management Services
Stores Planning and Weaponeering Module — one RDT&E project inside PE 0605215N. Congressional marks are recorded on the program element, not on a project.
Project 2311 — Stores Planning and Weaponeering Module — requests $11.6M in FY2027, 14% of the $82.6M requested for program element 0605215N. Year over year it falls 3.2% against FY2026.
Project 2311 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 12.0 |
| FY2026 | Enacted | 12.0 |
| FY2027 | Request | 11.6 |
| FY2028 | Outyear | 12.2 |
| FY2029 | Outyear | 12.5 |
| FY2030 | Outyear | 12.6 |
| FY2031 | Outyear | 12.8 |
4 accomplishments / planned programs
The R-2A exhibit. Activities carry the prior, current and budget year only — no five-year plan — and they are descriptive: coverage is partial and they do not always add back to the project, so count them, never total them. Opening lines only here — the full year-by-year narrative is on the project page.
- Continue quarterly WASP 5.2.X software database updates, software patches, and defect corrections. - Continue non-recurring engineering, software development, and system test for migration of WASP capabilities to the CMPC framework.
- Continue test and evaluation of WASP 5.2.X database updates prior to fleet deployment. - Continue developing and publishing test plans and test reports related to the WASP product line. - Conduct test and evaluation of the WASP/CMPC product. - Continue providing testing and test support to ensure all components (to include internally…
- Continue Systems Engineering support to the WASP for future software releases to the fleet. - Develop integration plans with micro-services architecture for integration into CMPC. - Provide continued support for database updates, software patches and defect corrections.
- Continue project management support to the WASP for future software releases to the fleet. - Develop integration plans with services architecture and CMPC. - Provide continued support for multiple database releases.
Named performers on project 2311
Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.
What project 2311 buys
The Weaponeering and Stores Planning (WASP) software is approved by NAVAIR Airworthiness and Cybersafe Office (A0P0000) as a flight clearance implementation system for the F/A-18C, C+, D, D (RC), E, F, EA-18G. The WASP software includes potential support for other platforms to include F-35, P-8, AH-1, and other fixed wing and rotary wing platforms. The WASP software components will alert pilots if their planned weapon release conditions meet flight clearance limits, will result in bomb-to-bomb collisions, bomb-to-aircraft collisions, aircraft over stress, or excessive risk of aircraft loss/damage in the event of fuze early bursts. Weapon employment planning is fundamental to the Joint Capability Area of Force Application and joint mission areas of Strike and Amphibious Warfare. The WASP software provides the Navy and Marine Corps with weaponeering capabilities that are critical requirements for Interdiction, Armed Reconnaissance and Close Air Support mission planning. Therefore, WASP product availability is critical to successful employment of the Joint Mission Planning System (JMPS) for the F/A-18C-F and EA-18G. The WASP product encompasses a multitude of Government Furnished Information software components and tools including aircraft target maneuver simulations and weapon flyout models. The WASP software products will require updates as emergent requirements for new aircraft T/M/S, stores and weapons are approved, new flight clearances/restrictions are issued by Naval Air Systems Command and cyber security mandates are released. FY 2025 and out includes funding for the research and development in order to develop WASP for other Navy and Marine Corps platforms, and support WASP development and integration with the Collaborative Mission Planning Continuum (CMPC).
- Product Development
- Support
- Test and Evaluation
- Management Services