What the FY2027 request buys
Verbatim from the R-2A exhibit for project 673310 of PE 0207439F. 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.
- Scope, lead, and deploy STITCHES integrations and train DoW personnel. Lead continual development for STITCHES Platform and new certification processes. - Execution of testing, training, and integration efforts as directed by the MAJCOM requirements working group. - Improve STITCHES verification, validation, and testing capabilities through automation, Graphical User Interface development, and streamline the developmental process for STITCHES toolchain and projects. - Maintain and enhance a STITCHES toolchain and repository into web-based infrastructure for unclassified/classified information systems. Deploy secure cloud and non-cloud structures and NDAA 2021 Section 804 repositories within FENCES environment. Maintain CUI and classified cloud and stand-alone/edge structure ATOs. - Continue to create new integrations between previously incompatible weapon systems, sensors, and command and control networks. - Implement STITCHES development for efforts including an increase in automation and standardization between multiple mission data test networks. - Continue to develop interoperability between legacy systems and Universal Command & Control Interface (UCI). - Support the demand from joint partner organizations who need to resolve critical integration problems within their operational systems.
- We expect an increase in MAJCOM working group requirements which will increase the scope of testing, training, and integration efforts - Funding increased to implement STITCHES development for efforts including an increase in automation, standardization between multiple mission data test networks, and interoperability development between legacy systems and UCI. - Increased development funding is required to meet continued escalating demand from joint partners, who are seeking to bridge critical interoperability gaps across their command and control enterprise.
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.
- Scope, lead, and deploy STITCHES integrations and train DoW personnel. Lead continual development for STITCHES Platform and new certification processes at AFLCMC/HNJJ direction. - Improve STITCHES verification, validation, and testing capabilities through automation, Graphical User Interface development, and streamline the developmental process for STITCHES toolchain and projects. - Continue deploying STITCHES toolchain and repository into web-based infrastructure for unclassified/classified information systems. Deploy secure cloud and non-cloud structures and NDAA 2021 Section 804 repositories within FENCES environment. Maintain CUI and classified cloud and stand-alone/edge structure ATOs. - Develop EW/EMSO capabilities through creation novel kill chains and EA/ES/EP involving previously incompatible weapon systems, Mission Design Series, sensor, and command, control, and communication systems. The development of advanced EW capability projects through collaboration of all military services in cooperation with multiple MAJCOMs to support multiple AORs such as United States Indo-Pacific Command and European Command. STITCHES will focus on traditional EW/EMSO problem sets and new gaps in air, maritime, space, and cyberspace domains.
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 | 16.7 |
| FY2026 | Enacted | 13.6 |
| FY2027 | Request | 16.3 |
This activity is 100% of project 673310's FY2027 request and 22% of PE 0207439F'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 673310
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.