What the FY2027 request buys
Verbatim from the R-2A exhibit for project DJ9 of PE 0605054A. 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.
- Award the BM Suite contract - Begin the execution phase of the Software Pathway (SWP) acquisition program - Begin development progression to meet SWP milestone for Minimum Viable Capability Release (MVCR) to align with Early Operational Capability (Increment 1)
The FY 2027 funding increase is the result of no funding in the FY 2026 RDTE base budget.
FY2025: 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.
- Build out of the Special Access Program (SAP) Software Integration (SIL) Lab - Initial operation of the GDS digital environment - Completion of independent studies to inform and scope the effort to optimize the JIBM architecture - Development of Integrated Defense Planner
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 | 39.2 |
| FY2027 | Request | 65.2 |
This activity is 84% of project DJ9's FY2027 request and 44% of PE 0605054A'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.
3 activities in project DJ9
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 project page.