What the FY2027 request buys
Verbatim from the R-2A exhibit for project 672569 of PE 0401130F. 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.
Continuation of engineering and manufacturing development to include but not limited to software development, data, cyber security, testing, integration laboratory updates, and other program support activities.
Funding increased due to additional engineering, software development and testing activities.
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.
Continue engineering and manufacturing development to include but not limited to software development, data, cyber security, testing, integration laboratory updates, and other program support activities.
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 | 5.2 |
| FY2026 | Enacted | 70.1 |
| FY2027 | Request | 105.5 |
This activity is 59% of project 672569's FY2027 request and 59% of PE 0401130F'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.
5 activities in project 672569
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.