What the FY2027 request buys
Verbatim from the R-2A exhibit for project 640141 of PE 0604003F. 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.
CBC2: -Continue supporting activities focused on a scalable and extensible data-cloud architecture at multiple classification levels and different REL environments in partnership with ABMS Digital Infrastructure, and other DAF enterprise solutions that leverages AI/ML applications and produces a common operating picture. - Continue to ingest, fuse, and analyze data from military, government, and commercial sources to multi-classification cloud environments. -Continue efforts to design and build infrastructure to support CBC2 in partnership with ABMS DI to include but not limited to: platform, cloud, cloud outposts, data transport, tactical data bus, identity management, zero trust network, cyber defense and data storage solutions. -Continue quarterly minimum viable capability releases (MVCRs), iteratively building upon the Cloud-Based C2 application/software baseline and addressing product backlogs associated with N&NC deliveries. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture. Common BMC2 Interface: -Continue development based on core CBC2 tactical C2 software suite to extend microservices functionality to support distributed BMC2 operational concepts and CBC2+ requirements and associated capability needs. -Continue to develop automated and operator-selectable tasking of assets, voice, data and C2. -Continue developing shared visualization consistent with CBC2 with automated and fused representation of multiple domains. -Continue integrating new and existing development teams with ABMS Software Integrator to create a microservices system that is fully government owned. -Continue quarterly MVCR, iteratively building out extensibility to additional distributed battle management operational concepts (e.g. Tactical Operations Center-Lite, Air Base Air Defense Systems). -Iteratively build and integrate human machine teaming, AI/ML capabilities aligned with the Common Battle Management Engine (CBME) and Transformational Model -Decision Advantage concepts -Facilitate data sharing and collaboration with foreign coalition partners in delivering battle management capabilities. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture
Funding will increase significantly in FY 2027 due to continuous integration and continuous delivery (CI/CD) software development for CBC2+ activities for multiple Combatant Commands simultaneously, CBC2 development cost begins to stabilize in FY 2027. Software teams will scale up contributions to CBC2+ activities with additional CBC2+ software development teams to continue to support emerging capability requirements and follow-on integration activities for distributed battle management operational concepts and ACC's CBC2+ with the Tactical Operations Center-Lite and Air Base Air Defense Systems.
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.
CBC2: -Continue design/development activities focused on developing a scalable and extensible data-cloud architecture at multiple classification levels and different REL environments in partnership with ABMS Digital Infrastructure, and other DAF enterprise solutions that leverages AI/ML applications and produces a common operating picture. -Continue developing shared visualization of multiple sources, automated and fused representation of air domain. -Ingest, fuse, and analyze data from military, government, and commercial sources to multi-classification cloud environments. -Continue to develop automated and operator-selectable tasking of assets, voice, data and C2. -Continue integrating new and existing development teams with ABMS Software Integrator to create a micro-services CBC2 system that is fully government owned. -Continue building micro-services-based software applications that will enable distributed battle management. -Continue efforts to design and build infrastructure to support CBC2 in partnership with ABMS DI to include but not limited to: platform, cloud, cloud outposts, data transport, tactical data bus, identity management, zero trust network, cyber defense and data storage solutions. -Continue quarterly minimum viable capability (MVCR) releases, iteratively building out the Cloud-Based C2 application/software baseline and addressing product backlogs associated with N&NC deliveries. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture. Common BMC2 Interface: -Continue development based on core CBC2 tactical C2 software suite to extend microservices functionality to support distributed BMC2 operational concepts and CBC2+ requirements and associated capability needs. -Continue to build microservices consistent with CBC2 development approach and in response to capability needs associated with joint tactical integrated fire control, long range kill chains, and other BMC2 functions. -Continue developing shared visualization consistent with CBC2 with automated and fused representation of multiple domains. -Continue integrating new and existing development teams with ABMS Software Integrator to create a microservices system that is fully government owned. -Continue quarterly MVCR, iteratively building out extensibility to additional distributed battle management operational concepts (e.g. Tactical Operations Center-Lite, Air Base Air Defense Systems) with the goal to gain operational acceptance of CBC2 tactical C2 software suite by Q4 FY 2026. -Continue facilitation of transition of advanced targeting tools (e.g. developed under the Hawkeye program) by ensuring compatibility with ABMS digital infrastructure and battle management software. -Facilitate data sharing and collaboration with foreign coalition partners in delivering battle management capabilities. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture
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 | 136.0 |
| FY2026 | Enacted | 149.9 |
| FY2027 | Request | 198.3 |
This activity is 19% of project 640141's FY2027 request and 19% of PE 0604003F'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.
7 activities in project 640141
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.