What project 673945 buys
This is not a New Start. In FY 2027, funds for Integrated Operations Networking (ION) are transferred from PE 1203010SF, Project 646602 to PE 1203156SF, Project 673945. The USSF's Integrated Operations Networking (ION) effort is a critical component of the Space Force's mission to enable the Battle Management, Command, Control, and Communications (BMC3) warfighter missions. ION will integrate commercially available information technology (IT) capabilities to address urgent operational needs and close networking gaps tied to kill chain gaps identified by Space Forces - Space operating in support of USSPACECOM. ION aims to improve tactical and operational timelines within the kill-chain to enable USSF's ability to deliver credible combat power effects in support of the Joint Force. The program will focus on developing a secure, reliable, and multi-classification transport layer to support space missions, with an emphasis on direct connection between all elements of force packages, establishing a special access program (SAP)-level network with overlays, and developing high-speed connectivity and high resilience to Commercial Cloud Services (C2S). The ION program will also pursue opportunities to leverage existing efforts, such as meshONE-T, to support the development of ION. Funding in FY 2027 will enable the program to maintain a steady pace of execution throughout the year, ensuring that the Space Force can leverage the ION capability to enhance its mission effectiveness. The ION program will provide a critical capability to the Space Force, enabling the service to operate in a contested environment and to defend against adversary operations. The program will be executed in a manner that is consistent with the Space Force's priorities, including the development of a digital engineering ecosystem, the implementation of zero trust capabilities, and the modernization of cryptography and supply chain risk management.
- Support
- Management Services
Project 673945 funding, FY2025–FY2031
Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.
| Fiscal Year | Estimate Type | Amount ($M) |
|---|---|---|
| FY2025 | Actual | 0.0 |
| FY2026 | Enacted | 0.0 |
| FY2027 | Request | 34.8 |
| FY2028 | Outyear | 0.0 |
| FY2029 | Outyear | 0.0 |
| FY2030 | Outyear | 0.0 |
| FY2031 | Outyear | 0.0 |
1 accomplishment / planned program
The R-2A exhibit — the only level of the budget that describes work that has not happened yet. Activities carry the prior, current and budget year only, no five-year plan. Each describes FY2027 work in enough detail to have its own page; the rest are shown here in full. Coverage is partial across the corpus, so count activities, never total them.
FY 2027 efforts will focus on scaling and accelerating the expansion of classified cloud and networking infrastructure to support secure data transport in alignment with projected threat timelines. This includes building upon the existing pathfinder implementation to connect disparate classified space capabilities into integrated…
Read the FY2027 plan →