What the FY2027 request buys
Verbatim from the R-2A exhibit for project 3085 of PE 0603599N. 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.
Continue systems engineering and platform integration efforts for C4I, Combat, and Aviation systems. Begin System Qualification Testing (SQT) of the Combat Management System (CMS) and initiate Combat System Integration (CSI) Testing to verify system functionality, interoperability, and readiness for integration into the total ship combat system architecture. Coordinate with PAE RAS to enable integration pathways of the FF(X) with MUSV and other unmanned systems to support "plug and play" accommodations for future unmanned systems. Initiate Flight Upgrade planning activities to support a comprehensive capability increase for the FF(X) class including evaluation, planning, and management of future transition from Atalanta Weapon System (ATwS) to the Integrated Combat System (ICS) and increased integration with unmanned capabilities. This effort will establish the technical, operational, and integration foundations required to define, assess, and implement a new Flight configuration. Continue planning to support Support Combat System (CS) development to ensure platform combat capability, including integration of the SPS 77 radar and Rolling Airframe Missile (RAM) system into the Combat System. Continue SPS 77 radar integration activities to meet Frigate requirements. Mature the integrated Warfare System baseline to support integration and test events that assess platform performance across all mission areas. Implement additional cybersecurity and information assurance measures across the Warfare System and C4I suite to address current and emerging threats.
Funding increase in FY27 related to increased CS Baseline Development and integration/Testing efforts and System Qualification Testing necessary for a 2028 launch and 2030 delivery of Ship 1.
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.
Initiated systems engineering and platform integration efforts for C4I, Combat, and Aviation systems. Supported Combat System (CS) development to ensure platform combat capability, including integration of the SPS 77 radar and Rolling Airframe Missile (RAM) system into the Combat System. Funding supports SPS 77 radar integration activities to meet Frigate requirements. Advanced the Integrated Warfare System baseline to enable integration and test events that evaluated platform performance across all mission areas. Implemented additional cybersecurity and information assurance measures across the Warfare System and C4I suite to address current and emerging threats.
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 | 0.0 |
| FY2026 | Enacted | 68.9 |
| FY2027 | Request | 176.0 |
This activity is 83% of project 3085's FY2027 request and 83% of PE 0603599N'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.
2 activities in project 3085
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.