What the FY2027 request buys
Verbatim from the R-2A exhibit for project 676020 of PE 0207134F. 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 and expand software integration efforts with R-EGI prototypes in the system integration lab; maintain F-15 development baseline with R-EGI updates; expand testing and F-15-specific non-recurring engineering activities.
Increase in funds for continuation of non-recurring engineering and software integration efforts.
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 and expand software integration efforts with R-EGI prototypes in the system integration lab; maintain F-15 development baseline with R-EGI updates; expand testing and F-15-specific non-recurring engineering 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 | 0.0 |
| FY2026 | Enacted | 23.8 |
| FY2027 | Request | 37.3 |
This activity is 12% of project 676020's FY2027 request and 12% of PE 0207134F'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 676020
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.