R-2A Activity · President's Budget PB2027

Fire Control Development

Activity a2·Project 3097 — W-93 / Mk 7·PE 0101221N·U.S. Navy
FY2027 Request
$20.4M
▲ 192% vs FY2026
HitchAI read

This activity requests $20.4M in FY2027, 2.4% of project 3097, up 192% on FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

FY2027 Request
$20.4M
▲ 192% vs FY2026
FY2026 Enacted
$7.0M
▲ 130% vs FY2025
FY2025 Actual
$3.0M
Prior year
Planned work

What the FY2027 request buys

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

- Integrate Mk7 capability into Fire Control system including software updates, system modifications, performance parameter integration, and interface requirements development. - Update Fire Control targeting algorithms, databases, and Mission Planning systems to accommodate Mk7 reentry body characteristics, trajectory planning, and operational constraints. - Execute Fire Control system testing, validation, and performance analysis to verify Mk7 integration impacts on targeting accuracy and overall weapon system effectiveness. - Support Fire Control system certification and acceptance testing including operator procedure updates, documentation, and demonstration of full Mk7 operational capability.

FY2026 to FY2027 change

The requested $13.417 million funding increase is required for software development and testing necessary for full Mk7 system integration. This FY 2027 funding will support comprehensive Fire Control system modifications, including updates to targeting algorithms and Mission Planning systems to accommodate the Mk7's characteristics. These efforts, which also include full system testing, validation, and certification activities, to support the development flight tests scheduled for FY 2028.

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 the development and refinement of the Fire Control software revision planned for future flight tests. - Implement new functionalities and address deficiencies in the existing software based on ongoing testing and analysis. - Conduct rigorous software testing, including unit testing, integration testing, and system-level testing, to ensure robustness and reliability.

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.

03.0FY25ACTUAL7.0FY26ENACTED20.4FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual3.0
FY2026Enacted7.0
FY2027Request20.4

This activity is 2.4% of project 3097's FY2027 request and 1.9% of PE 0101221N'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

5 activities in project 3097

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.

Source
FY2027 Department of the Navy RDT&E Budget Justification · Exhibit R-2A · PE 0101221N, project 3097 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0101221N/3097/a2.md · MCP mcp.hitchintel.combudget_get_activity