What the FY2027 request buys
Verbatim from the R-2A exhibit for project 675368 of PE 0101318F. 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.
- Continued integration of Data and Analytics in support of NC3 next-gen - Continued expansion of D-DIL/EMCON environment support - Continued test and evaluation all GDI segments in support of data governance, provenance and discovery
The $49.4M increase is attributed to expanded program levels of effort.
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.
- Continued integration of Data and Analytics in support of NC3 next-gen - Continued expansion of D-DIL/EMCON environment support - Continued test and evaluation all GDI segments in support of data governance, provenance and discovery
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 | 6.4 |
| FY2026 | Enacted | 6.3 |
| FY2027 | Request | 55.7 |
This activity is 99% of project 675368's FY2027 request and 99% of PE 0101318F'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 675368
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.