What the FY2027 request buys
Verbatim from the R-2A exhibit for project UN4 of PE 0603884BP. 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 feature development of CSC2 capabilities, including integration of S&T capabilities for sensor data analytics, non-CBRN sensor data, decision support tools, and data broker capabilities for internal and external data exchanges. Features will be delivered through quarterly software capability releases. This continues the ability to securely exchange, integrate, and manage data across multiple systems, platforms, and domains. Enable CSC2 capability delivery to be tailored to service-specific needs while ensuring data security, interoperability, and operational relevance. Incorporate additional Commercial Off-the-Shelf (COTS) and developmental sensor capabilities to the baseline for the Sensor Controller Manager to reduce disparate capabilities in the field. Provide program/financial management, costing, contracting, scheduling and acquisition oversight and product support for software development and experimentation with operational forces.
Increase due to minor program adjustments and inflation.
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.
Continued feature development of CSC2 capabilities, including baseline capabilities for Warning Reporting and Advanced Hazard Prediction for a Minimum Viable Capability Release (MVCR) in 3Q FY 2026. Initiated development of internal and external data broker capabilities to facilitate the secure exchange, integration, and management of data across multiple systems, platforms, and domains. Delivered features through quarterly software capability releases. Initiated aligning contracts to an agile workforce for the development of capabilities and integration into deployable CSC2 configurations. This ensured the features and capabilities had access to necessary data while ensuring security, interoperability, and operational relevance. Incorporated force protection sensor capabilities into the baseline for the Sensor Controller Manager to reduce disparate capabilities in the field. Provided program/financial management, costing, contracting, scheduling and acquisition oversight, and product support for software development and experimentation with operational forces.
MVCR for CSC2 was completed and continued development of MVP prototype for CBRN Warning and Reporting decision support tools. Demonstrated integration and interoperability with CCMDs and service networks, enhancing battlespace awareness and accelerating decision-making. Conducted multiple service feedback events to refine capability development and support agile testing, evaluation, and engineering for future releases. Maintained quarterly deliveries of CSC2 capabilities.
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 | 25.5 |
| FY2026 | Enacted | 26.5 |
| FY2027 | Request | 28.9 |
This activity is 56% of project UN4's FY2027 request and 7.4% of PE 0603884BP'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.
11 activities in project UN4
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.