What the FY2027 request buys
Verbatim from the R-2A exhibit for project 656060 of PE 0605056F. 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.
- Craft targeted prototype of open architecture implementation to inform maturation efforts and ease adoption - Complete 95 change requests in FY27 - Continue technical maturation of the OMS and UCI standards - Continue to update standards to account for emerging technologies and operational weapon system feature requests - Support feature requests from deployment of UCI in support of the DAF Battle Network - Conduct targeted training to new and existing adopters to ease implementation - Horizontally integrate and rationalize standards with other mission system architecture products - Develop and update open hardware technical standards for government reference architecture implementations - Define domain-specific data modeling usage for joint interoperability - Mature Model-Based Systems Engineering (MBSE) products within open architectures - Mature plans for adopting SOSA requirements
FY 2027 funding increased compared to FY 2026 by $2.06 million due to the continued adoption of open architecture adoption the United States Space Force, DAF Command, Control, Communications and Battle Management (C3BM) platforms. With the deliberate increase in depth of architecture knowledge across Air Force legacy platforms, there is a forecasted surge in change requests, training, and implementation guidance, to support the increase in adopting platforms. Furthermore, the Architectures and Standards will support implementing Open Architectures on new development Air Force Platforms [F-47, B-21, Collaborative Combat Aircraft (CCA)] as well as adopting SOSA requirements.
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.
- Increase adoptability with USSF/Command, Control, Communications and Battle Management (C3BM) systems to support DAF Battle Network - Rapidly respond to emerging technologies, operational weapons systems feature request and adopting platform requirements by completing 85-95 change requests annually - Align Open Mission System (OMS) with Agile Mission Suite Government Reference Architecture (AMS GRA), unlocking additional capabilities for future adopters - Continue technical maturation of the OMS and UCI standards - Conduct targeted training to new and existing adopters - Merge subsystem architectures with open architecture management - Develop and update open hardware technical standards for government reference architecture implementations - Define domain-specific data modeling usage for joint interoperability - Mature MBSE products within open architectures - Begin planning for adopting Sensor Open Systems Architecture (SOSA) requirements
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 | 40.1 |
| FY2026 | Enacted | 41.4 |
| FY2027 | Request | 43.5 |
This activity is 100% of project 656060's FY2027 request and 100% of PE 0605056F'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 656060
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.