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.
Enterprise Engineering Group (EEG): -Continue management of the ABMS Consortium activity comprised of industry partners, FFRDC, and USG stakeholders performing operational analysis, mission analysis, Systems Engineering, and integration of ABMS Digital Infrastructure. -Continue data architecture, data tagging, and data orchestration design solutions and prototypes that enable available data to be exposed, processed, and transferred within multi-level security ABMS cloud environments. -Continue maturing the extension of the ABMS DI to the tactical edge based on operator and ABMS CFT input. -Continue maturing CONUS and OCONUS clouds by adding more data types, data transfers across classification levels, establishing data and network management standards and tools (e.g., SD-WAN), and developing and hosting cloud-native applications (e.g., Cloud-Based C2, advanced targeting tools, air base air defense applications). -Expand locations and content in the collaborative, multi-security-level, enterprise systems engineering ecosystem for architecture and modeling development. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture. ABMS Digital Infrastructure (DI): -Continue to invest in technologies and solutions to expose, transport, and host data and mission/infrastructure software through widely used commercial best practices and techniques such as Application Program Interfaces (APIs) and standardized data fabric solutions. -Continue development and implementation of DI Network Major Releases 1 and 2, including SD-WAN, content delivery, network monitoring and security solutions, data link integration, scalable transport, cross domain solutions, and others. -Continue to develop and implement Deployable, Fixed, and Remote DI Processing Node solutions that provide a multi-level security compute and storage environment able to host mission data, data management software, and mission applications at multiple echelons of command, including tactical and operational C2 nodes. -Continue to support Cloud deployment, Platform as a Service, and Infrastructure as a Service offerings to the DAF BATTLE NETWORK. -Continue to fund efforts related to DI Network and DI Processing Nodes in collaboration with Major Commands, Combatant Commands, Component Major Commands, the ABMS CFT, and C3BM ASE. As operational and technical requirements are refined, ABMS DI will look to accelerate development of acquisition strategies and propel additional efforts into execution. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture. ABMS DI-Network Integration Lab (DI-NIL): -Continue experimentation efforts to accelerate requirements development. -Continue to integrate with and expand connections to Joint Partners. -Continue deployment of ABMS Digital Infrastructure to the DI-NIL. -Prepare to support experimentation for Distributed Battle Management Applications (DBMA) and CBC2+.
While funding decreases in FY 2027, C3BM DI will continue development, procurement, and implementation of Deployable, Fixed, and Remote DI Processing nodes to tactical and operational C2 echelons of command, cloud, platform, and infrastructure offerings, as well as the integration and deployment of the DI-Network.
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.
Enterprise Engineering Group (EEG): -Continue management of the ABMS Consortium activity comprised of industry partners, FFRDC, and USG stakeholders performing operational analysis, mission analysis, Systems Engineering, and integration of ABMS Digital Infrastructure. -Continue data architecture, data tagging, and data orchestration design solutions and prototypes that enable available data to be exposed, processed, and transferred within multi-level security ABMS cloud environments. -Continue maturing the extension of the ABMS DI to the tactical edge based on operator and ABMS CFT input. -Continue maturing CONUS and OCONUS clouds by adding more data types, data transfers across classification levels, establishing data and network management standards and tools (e.g., SD-WAN), and developing and hosting cloud-native applications (e.g., Cloud-Based C2, advanced targeting tools, air base air defense applications). -Expand locations and content in the collaborative, multi-security-level, enterprise systems engineering ecosystem for architecture and modeling development. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture. ABMS Digital Infrastructure (DI): -Continue to invest in technologies and solutions to expose, transport, and host data and mission/infrastructure software through widely used commercial best practices and techniques such as Application Program Interfaces (APIs) and standardized data fabric solutions. -Continue development and implementation of DI Network Major Releases 1 and 2, including SD-WAN, content delivery, network monitoring and security solutions, data link integration, scalable transport, cross domain solutions, and others. -Continue to develop and implement Deployable, Fixed, and Remote DI Processing Node solutions that provide a multi-level security compute and storage environment able to host mission data, data management software, and mission applications at multiple echelons of command, including tactical and operational C2 nodes. -Continue to support Cloud deployment, Platform as a Service, and Infrastructure as a Service offerings to the DAF BATTLE NETWORK. -Continue to fund efforts related to DI Network and DI Processing Nodes in collaboration with Major Commands, Combatant Commands, Component Major Commands, the ABMS CFT, and C3BM ASE. As operational and technical requirements are refined, ABMS DI will look to accelerate development of acquisition strategies and propel additional efforts into execution. -Test and Evaluation: Continue to analyze artifacts to test mission area architecture. ABMS DI Network Integration Lab (DI-NIL): -Continue experimentation efforts to accelerate requirements development. -Continue to integrate with and expand connections to Joint Partners. -Continue deployment of ABMS Digital Infrastructure to the DI-NIL. -Prepare to support experimentation for Distributed Battle Management Applications (DBMA) and CBC2+.
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 | 235.5 |
| FY2026 | Enacted | 283.8 |
| FY2027 | Request | 228.7 |
This activity is 22% of project 640141's FY2027 request and 22% 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.