# Project 2311 — Stores Planning and Weaponeering Module

**Program element:** 0605215N — Mission Planning  
**Project:** 2311  
**Component:** U.S. Navy  
**Appropriation:** 1319 — RDT&E, Navy  
**Budget Activity:** 5 — System Development & Demonstration  
**Vintage:** President's Budget PB2027  
**Canonical URL:** https://hitchintel.com/programs/0605215N/2311  
**Parent:** https://hitchintel.com/programs/0605215N

## Summary

Project 2311 — Stores Planning and Weaponeering Module requests $11.6M in FY2027, 14% of the $82.6M requested for program element 0605215N, down 3.2% on FY2026. 4 R-2A activities decompose the request. DCS is the largest named R-3 performer at $5.9M, 51% of the project's FY2027 R-3 total.

## Funding profile

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

> Estimate types are not summed. This project is one leaf of PE 0605215N; the PE total is the sum of its projects, never added to them.

## 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).

**R-3 lines of work:** Product Development; Support; Test and Evaluation; Management Services.

## Named R-3 performers

| Performer | $M | Share of this project's FY2027 R-3 total |
|---|---|---|
| DCS | 5.9 | 51% |
| NAWCAD | 2.7 | 24% |
| KBR | 2.6 | 23% |
| Precise | 0.1 | 0.9% |

> Budget-justification contract funding, not obligations. Shares need not reach 100% — unnamed and government work is in the denominator.

## Activities (R-2A) — 4

| Activity | FY2025 | FY2026 | FY2027 | Move | Page |
|---|---|---|---|---|---|
| Product Development | 5.5 | 5.4 | 5.2 | −5% | — |
| Systems Engineering Support | 3.3 | 3.3 | 3.2 | −2% | — |
| Test and Evaluation (T&E) | 3.0 | 3.0 | 2.9 | −2% | — |
| Program Management | 0.2 | 0.2 | 0.2 | +0% | — |

> Activities carry the prior, current and budget year only — no five-year plan. In the request year they partition this project exactly; in earlier years they can under-cover it.

### Product Development

**FY2027 planned work.** - 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.

**FY2026 to FY2027 change.** FY 2026 to FY 2027 decrease due to reduction of support for legacy WASP as the system transitions to CMPC WASP.

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

### Systems Engineering Support

**FY2027 planned work.** - 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.

**FY2026 to FY2027 change.** FY 2026 to FY 2027 decrease due to reduction of support for legacy WASP as the system transitions to CMPC WASP.

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

### Test and Evaluation (T&E)

**FY2027 planned work.** - 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 developed software, externally developed GFI) comply with Department of Navy (DON) and Department of War (DoW) software mandates and directives. These include Integrated Shipboard Network System IT-21, and Cyber Risk Management Framework (RMF).

**FY2026 to FY2027 change.** FY 2026 to FY 2027 decrease due to reduction of support for legacy WASP as the system transitions to CMPC WASP.

**FY2026 plans — current year.** - 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 developed software, externally developed GFI) comply with Department of Navy (DON) and Department of War (DoW) software mandates and directives. These include Integrated Shipboard Network System IT-21, and Cyber Risk Management Framework (RMF).

### Program Management

**FY2027 planned work.** - 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.

**FY2026 to FY2027 change.** No significant changes.

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

## What is NOT on this page

Congressional marks, the R-2 mission description and acquisition strategy, the industry vs government split of the whole request, and related program elements are recorded at **program-element** grain — an NDAA mark lands on a PE, never on a project. They are at https://hitchintel.com/programs/0605215N.

## Source & machine access

- **Source:** FY2027 Department of the Navy RDT&E Budget Justification, Exhibits R-2/R-2A/R-3, PE 0605215N project 2311 (PB PB2027).
- **MCP:** `mcp.hitchintel.com` — `budget_get_program_element(pe="0605215N")`.

*HitchAI is an independent intelligence service, not affiliated with the U.S. Department of Defense. Budget figures are requests/estimates, not obligations.*