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 focus on delivering the minimum viable product (MVP) of the full edge-to-shore software and cloud infrastructure required to enable continuous development, integration, and delivery of RAS capabilities by the end of Q4FY27. The FY27 MVP will include the implementation of DevSecOps pipelines to support automated software development, testing, accreditation, and deployment across RAS platforms. This infrastructure will enable rapid iteration and delivery of autonomy, perception, and command-and-control software updates to operational systems. FY27 efforts will also deliver an enterprise-level data management and analytics capability to support efficient ingestion, storage, and processing of RAS data. This capability will enable accelerated improvement of autonomous capabilities. Additionally, FY27 will deliver integrated edge-to-shore testing infrastructure, including hardware-in-the-loop (HIL) and software-in-the-loop (SIL) environments, to support development, integration, and validation of software for Medium USV array of small USV platforms. The infrastructure delivered in FY27 will also support the deployment of C2 software capabilities into operational environments to meet requirements across Fourth Fleet, Fifth Fleet, Sixth Fleet, and Seventh Fleet operations. Lastly, FY27 MVP efforts will deliver the required Modeling and Simulation (M&S) capabilities necessary to support software development, testing, and validation, ensuring that autonomy and mission software can be evaluated in representative operational scenarios before deployment to the Fleet.
FY27: +$13.823M 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 | 20.4 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 13.8 |
This activity is 8.8% of project 3067's FY2027 request and 5.4% 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.