What the FY2027 request buys
Verbatim from the R-2A exhibit for project 250 of PE 0604250D8Z. 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.
These funds provide for SCO labor and travel to support the ~40 project teams that will be active in FY 2027.
Increase from FY 2026 to FY2027 for project support and inflation of SETA support contract costs associated with supporting 15 new project teams.
FY2025–FY2026: what came before
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.
These funds provide for SCO labor and travel to support the ~25 project teams that are active each fiscal year, and includes $15.272M for SBIR/STTR funding.
These funds provide for SCO labor and travel to support the ~25 project teams that are active each fiscal year.
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 | 47.6 |
| FY2026 | Enacted | 71.0 |
| FY2027 | Request | 146.6 |
This activity is 5.6% of project 250's FY2027 request and 5.6% of PE 0604250D8Z'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.
34 activities in project 250
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.