What the FY2027 request buys
Verbatim from the R-2A exhibit for project 085 of PE 0604122D8Z. 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 field additional tactical edge data mesh nodes to build out capability supporting Department priorities. Additionally, CDAO will continue working with Echelon 1 and Echelon 2 components to prioritize API level data integrations for the nodes. CDAO continues to improve blue data objects and enterprise cross-domain solution capabilities for more robust operational-to-tactical C2. Continue work with Joint organizations to provide tactical C2 for counter drone threats.
FY 2027 increase due to Edge Data Mesh usage and related contract support. The increase allows accelerated deployment of nodes and deployments to keep pace with the expansion of the overall Joint C2 commercial architecture and support strategic priorities.
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.
In FY 2026 CDAO fields additional tactical edge data mesh nodes and data integrations to support tactical-to-strategic data linkages in high priority locations. CDAO continues to support API-enabled data integrations and hardware deployments in order to support Joint C2, counter-drone missions, and other priorities.
CDAO awarded a production Other Transaction Authority (OTA) agreement after successfully completing prototyping as part of the Joint Operating System (JOS). This award resourced the deployment of Edge Data Mesh (EDM) nodes and additional data integrations with edge sensors and effectors to support CCMD needs. Key EDM deployments in FY25 supported JTF-Southern Border and INDOPACOM, including SOCPAC, PACFLT, USARPAC, and MARFORPAC. This funding also enabled Data Integration Services (DIS) that improved blue data objects, data specificity, and a methodology for enabling enterprise cross-domain solutions to move data across the data mesh at multiple classification levels.
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 | 163.3 |
| FY2026 | Enacted | 26.3 |
| FY2027 | Request | 52.8 |
This activity is 100% of project 085's FY2027 request and 2.5% of PE 0604122D8Z'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.
1 activity in project 085
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.