IN Brief:
- Viasat has received a US Space Force IDIQ contract with a $450m ceiling and an initial $115m task order.
- The company will develop and operate mission-control functions supporting the Space Data Network Backbone’s multi-vendor connectivity.
- Future tasks remain subject to orders, while the operations centre is intended to support network visibility, priority management, and sustainment.
Viasat has received a US Space Force contract to support the design, fielding, operation, and sustainment of the Space Data Network Backbone (SDN-B) mission operations centre. The indefinite-delivery, indefinite-quantity agreement has a maximum ceiling of $450 million and includes an initial $115 million task order to develop and scale the centre and its associated network operations capability.
Space Systems Command awarded the contract for work undertaken under government direction. The network is intended to support US Space Force missions, the Golden Dome for America programme, and wider joint operations, using a multi-vendor data transport design. Viasat’s assigned role concerns the control, integration, and sustainment functions that allow participating communications services to be monitored and managed; the contract does not establish that Viasat will manufacture or own every satellite or ground station in the architecture.
The $450 million amount is the ceiling for orders that may be issued over the contract’s life, rather than a sum confirmed as immediately funded. The first $115 million task order is a distinct award for specified work on the mission operations centre and associated network operations capability. Viasat did not disclose the complete schedule for later task orders or the final total that might be ordered under the framework.
SDN-B is intended to provide high-capacity, low-latency data transport through a multi-vendor architecture. Bringing several space and ground services into one managed environment requires reliable information about connectivity, link status, service capacity, and the ability of participating systems to exchange operational data. The procurement announcement defines these objectives, but does not disclose a final network topology, supplier list, or throughput and latency guarantees.
A network assembled from multiple suppliers presents an integration problem different from operating a single proprietary communications system. Links may rely on different orbits, frequencies, ground networks, management tools, and service rules. A common mission-control layer needs to receive information from the participating systems and translate it into a usable view of performance without assuming that each provider exposes identical controls or telemetry.
Viasat will provide systems engineering and integration for the space-to-ground interface and multi-orbit connectivity services. That remit covers the management and integration layer rather than an identified order for new Viasat satellites. Interfaces between providers must represent network condition in a form usable by the mission operations centre, although the company has not published the protocols, system boundaries, or hardware architecture selected for SDN-B.
The mission operations centre will also support a common operational picture of network health, status, and performance. Such a view can help controllers identify degraded links, changing demand, and the consequences of outages for communications service. Its value depends on how accurately and promptly the underlying systems report their condition, and whether operators can use that information to make decisions in accordance with the Space Force’s priorities.
Enterprise network operations are another contracted work area. The team will establish infrastructure that supports data transport management in accordance with government-directed mission priorities. A common management capability must account for which participating links are available and how they report their condition; the announcement does not say that every service can already be switched automatically, or that the final operating software has completed acceptance testing.
Life-cycle support is included in the scope alongside availability, resilience, and cybersecurity requirements. When one communications path becomes unavailable, alternative services can be useful only if they meet the relevant traffic, access, and security needs. Viasat has not identified the network’s redundancy targets or the operational tests that will establish resilience across different provider systems.
Viasat’s existing government satellite communications activities provide relevant experience in multi-layer connectivity. Its publicly described Hybrid Adaptive Network approach combines different communication services and management functions across multiple orbit types. The SDN-B contract, however, has its own government-directed architecture and deliverables, and it would be inaccurate to assume that all components of Viasat’s commercial or existing defence systems will be used in the new programme.
The contract aligns with Space Systems Command’s broader interest in open, interoperable architectures that can incorporate commercial technology without tying the entire network to a single supplier. That model creates continuing demands for interface compatibility, service assurance, testing, and configuration management as additional providers join the system.
The first funded work identified publicly is the $115 million task order covering development and expansion of the mission operations centre. Viasat has not announced a full deployment date, specified later task orders, or disclosed which third-party networks will be integrated first. The remaining headroom under the $450 million ceiling is subject to subsequent procurement decisions.
