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
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 — the only level of the budget that describes work that has not happened yet. Activities carry the prior, current and budget year only, no five-year plan. Coverage is partial across the corpus, so count activities, never total them.
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.
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.
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).
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.
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.