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.
In FY27, efforts will continue the maturation and expand operational deployment of the Navy's Command and Control (C2) ecosystem, initially awarded under a production Other Transaction Authority (OTA) in FY26. Activities will focus on delivering critical C2 capabilities in support of Fourth Fleet's Iron Sentinel operations, while expanding those capabilities to support U.S. Fifth Fleet and U.S. Sixth Fleet counter-UAS missions. FY27 efforts will also lay the groundwork for the C2 capabilities required to operationalize Medium USVs. Development activities will focus on ensuring the C2 architecture can support scalable mission control across distributed operational environments. Additional C2 capabilities will be developed in FY27 to enable mass deployment of RAS across multiple theaters and mission sets. This includes the initial deployment of the C2 system in operational environments, with infrastructure supporting both afloat platforms and shore-based control nodes, enabling persistent command, monitoring, and tasking of distributed unmanned assets. FY27 will also build upon sensor integration activities initiated in FY26, including integration with Minotaur and Maven Smart Systems, as well as alignment with other high-priority Department of War initiatives. This includes integration with the Defense Innovation Unit (DIU) C2 Orchestrator capability, which is planned to transition to PAE RAS in FY27 to further support enterprise-level unmanned system command and control. These efforts will continue to advance a scalable, interoperable C2 architecture capable of supporting distributed unmanned operations across multiple operational theaters.
FY27: +$23.4M to support expansion of MUSV and sUSV production and amplified requirements under PAE RAS
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.
Although Project 3067 was zeroed in PB26, the accomplishments below reflect work executed under PB25 funding, with some activities continuing into early FY26.
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.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 6.1 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 23.4 |
This activity is 15% of project 3067's FY2027 request and 9.2% 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.
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.