What the FY2027 request buys
Verbatim from the R-2A exhibit for project 655238 of PE 0605238F. 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 to mature the weapon system's software technology, ensuring robust cybersecurity, and developing comprehensive software sustainment strategies. Continue to refine requirements and modular architectures through rigorous testing and analysis, as well as maturing weapon system software, integration, and lifecycle management. Continue to expand data ingestion capabilities to accommodate flight test data and support model-based engineering approaches. Continue to increase government support to sustain the hardware and software technical baseline. Continue to develop and mature sustainment strategies for digital, software, and hardware components. Continue to assess software fielding requirements and timelines, in addition to software infrastructure needs for the transition from MM III to Sentinel. Continue to assess the feasibility of leveraging existing government software resources and partnerships to maintain control of the technical baseline.
Funding increased due to the risk reduction / parallel path efforts identified through the program restructure activities, TMRR efforts to achieve MS-B, and the EMD prime contract schedule incentive fee identified in the "Omni-Mod” contract framework.
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.
Mature the weapon system's software technology, ensuring robust cybersecurity, and developing comprehensive software sustainment strategies. Refine requirements and modular architectures through rigorous testing and analysis, as well as maturing weapon system software, integration, and lifecycle management. Expand data ingestion capabilities to accommodate flight test data and support model-based engineering approaches. Increase government support to sustain the hardware and software technical baseline. Develop and mature sustainment strategies for digital, software, and hardware components. Assess software fielding requirements and timelines, in addition to software infrastructure needs for the transition from MM III to Sentinel. Assess the feasibility of leveraging existing government software resources and partnerships to maintain control of the technical baseline.
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 | 143.5 |
| FY2026 | Enacted | 158.8 |
| FY2027 | Request | 292.7 |
This activity is 6.5% of project 655238's FY2027 request and 6.5% of PE 0605238F'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 655238
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 program-element page.