What the FY2027 request buys
Verbatim from the R-2A exhibit for project 3241 of PE 0604636N. 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.
Navy Shore C-UxS systems need to continue to evolve due to the rapidly evolving UAS capability, to reduce operator burden, and to increase interoperability of fixed facility Navy sites with joint C-UxS systems and with C-UxS systems on Navy ships.
The program reflects a increase from FY26 to FY27 due to the support for testing of material solutions and the integration of networking capabilities essential for system evaluation and performance validation.
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.
Continues to provide funding for refinement of material solutions, threat assessments, identification and development of advanced target discrimination, defeat (kinetic and non-kinetic) capabilities, and integration into the C-sUAS FoS. Provide management and technical support for the C-sUAS System Under Test (SUT). Initiate system assessment. In partnership with the Joint C-sUAS Office (JCO), identify or develop additional detect and deter capabilities to integrate into the C-sUAS FoS. As the JCO designated CORIAN Acquisition Lead, continue development, implementation and integration of additional sensor modalities to improve system detect/ID/track/defeat capabilities. Continue efforts to improve interoperability between ashore and afloat C-sUAS systems. Funding provides for continued development of data fusion architecture for external sensor integration into a C-sUAS common Command and Control (C2). Provide systems engineering support for the technology development and acquisition strategy for fielding material solutions.
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 | 1.6 |
| FY2026 | Enacted | 4.7 |
| FY2027 | Request | 13.6 |
This activity is 100% of project 3241's FY2027 request and 65% of PE 0604636N'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.
1 activity in project 3241
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.