What the FY2027 request buys
Verbatim from the R-2A exhibit for project 68A035 of PE 1208248SF. 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 to fund government software centers, laboratories, contractors for supporting the update, maintenance and modification, integration, configuration management and cybersecurity requirements of infrastructure, current system software, associated hardware, operationally accepted software applications, capabilities, and workflows associated with Space Domain Awareness (SDA) Planning and Tasking programs. Expand fielding of Platform, Infrastructure, and Data as a Service to operations sites. This includes associated connectivity, enhancements, on-site manpower, and training required to enable simultaneous operations across all nodes. Enhance reliability and scale and expand to other classification levels. Maintain foundational Development, Security, and Operations (DevSecOps) enablers such as, but not limited to, Data as a Service (DaaS), Platform Support, Continuous Improvement/Continuous Deployment (CI/CD) toolchain, and infrastructure and inherent sustainment efforts that are an integral part of the agile software development process.
FY 2027 increased by 46.815M due to combining the Distributive Space Command and Control (DSC2) sustainment funding into a unified operational mission baseline and a single acquisition baseline for the enterprise SDA mission area.
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.
Fund government software centers, laboratories, contractors for supporting the update, maintenance and modification, integration, configuration management and cybersecurity requirements of infrastructure, legacy software, associated hardware, operationally accepted software applications, capabilities, and workflows associated with SDA/Planning/Tasking program. Expand fielding of Platform, Infrastructure, and Data as a Service to operations sites. This includes associated connectivity, enhancements, on-site manpower, and training required to enable simultaneous operations across all nodes. Transition infrastructure to a hardware as a service model, enhance reliability and scale and expand to other classification levels. Maintain foundational Development, Security, and Operations (DevSecOps) enablers such as, but not limited to, Data as a Service, Platform Support, continuous Improvement/Continuous Deployment (CI/CD) toolchain, and infrastructure and inherent sustainment efforts that are an integral part of the agile software development process.
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 | 74.0 |
| FY2026 | Enacted | 97.6 |
| FY2027 | Request | 144.4 |
This activity is 40% of project 68A035's FY2027 request and 23% of PE 1208248SF'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 68A035
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.