R-2A Activity · President's Budget PB2027

Networks & Resiliency C4I

FY2027 Request
$22.6M
◆ Restart — nothing in FY2026
HitchAI read

This activity requests $22.6M in FY2027, 14% of project 3067 — a restart, funded in FY2025 and zeroed in FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

Restart

This activity was funded in FY2025 ($20.1M), zeroed in FY2026, and requests $22.6M again in FY2027. A restart has an incumbent and a new start does not; with a zero current year there is no percentage to quote, which is why it appears in no growth ranking.

FY2027 Request
$22.6M
No FY2026 funding
FY2026 Enacted
$0.0M
▼ 100% vs FY2025
FY2025 Actual
$20.1M
Prior year
Planned work

What the FY2027 request buys

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

FY2027 efforts will focus on continued maturation of the Medium Unmanned Surface Vehicle (MUSV) prototype build, leveraging commercial solutions. In parallel, the initial MUSV Program of Record (PoR) EDM delivery is scheduled for late Q2 FY2027, followed by EDM installation, integration, and testing in Q4 FY2027. These activities will include implementation of all required cybersecurity and cryptographic capabilities. Additionally, FY2027 efforts will support the continued maturation of the ORIENT-like solution developed under DIU initiatives, with the next iteration planned for delivery in Q4 FY2027. This solution will provide resilient C4I capabilities designed to support mass deployment of RAS platforms and ensure secure communications in denied, degraded, intermittent, and low-bandwidth (DDIL) environments.

FY2026 to FY2027 change

FY27: +$22.6M to support expansion of MUSV and sUSV production and amplified requirements under PAE RAS

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

Although Project 3067 was zeroed in PB26, the accomplishments below reflect work executed under PB25 funding, with some activities continuing into early FY26.

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.

020.1FY25ACTUAL0.0FY26ENACTED22.6FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual20.1
FY2026Enacted0.0
FY2027Request22.6

This activity is 14% of project 3067's FY2027 request and 8.9% of PE 0605513N'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

7 activities in project 3067

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 0605513N, project 3067 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0605513N/3067/a0.md · MCP mcp.hitchintel.combudget_get_activity