DoD taps Viasat to field operations ‘center’ for Golden Dome satellite data relay network

Viasat has been selected to build a Missions Operation Center, or MOC, for the Space Data Network Backbone. The center will integrate satellite constellations, coordinate missions, and manage data traffic. This matters because the network is intended to connect military and eventually commercial spacecraft with decision-makers and weapons platforms.

Space Systems Command awarded Viasat an indefinite delivery/indefinite quantity contract with a ceiling of $450 million. Under this type of arrangement, the government can issue orders for needed work rather than committing the entire ceiling immediately. Viasat will design, field, and scale the center.

The company will serve as the network and mission system integration partner. The MOC is being developed in partnership with the Pentagon’s Golden Dome office and will support the Space Data Network’s open-architecture ecosystem. Its near-term focus is supporting the Golden Dome missile defense initiative.

A Missions Operation Center is a software-run hub that brings together mission integration, network operations, and data transport management. It will coordinate a growing architecture made from multiple satellite providers. That role matters because the Space Data Network must make different space systems work together as one communications network.

The article compares the MOC with an old-fashioned telephone exchange. Human operators once connected calls by patching cables between users and helped resolve problems when connections failed. The MOC performs a similar coordinating function digitally, directing data across satellites, ground stations, and users.

Unlike the manual exchanges of the past, the MOC is intended to support real-time priority routing and autonomous data movement. It will help create high-speed, low-latency, and cyber-resilient paths across air, land, sea, and space. The center therefore becomes the network’s operational control layer.

The MOC effort could become substantial because Viasat’s contract has a ceiling of $450 million. That figure covers an indefinite delivery/indefinite quantity arrangement for designing, fielding, and scaling the center. The contract structure allows work to expand through orders as requirements develop.

The center is meant to connect multiple satellite constellations and providers. The article identifies the Space Data Network Backbone as a low-Earth-orbit constellation being built by SpaceX. It also describes a broader architecture containing military and eventually commercial sensor and communications satellites.

The article does not state an exact number of satellite systems. Instead, it emphasizes a growing multi-vendor architecture and the integration of disparate systems. The MOC’s purpose is to bring these systems together, allowing the network to use different constellations, orbits, and ground stations as one coordinated capability.

The MOC is designed to keep information moving when a normal connection becomes unreliable. It orchestrates data across multiple satellite constellations in different orbits and across the ground stations that support them. This matters because military data may need to travel quickly even when bandwidth is limited or an adversary is interfering.

For example, if one constellation’s transmission slows because of congestion, the network can shift the data to another constellation. The information can then continue through a different satellite or ground-station path. The article describes this as data “hopping” from one constellation to another.

The mechanism is network orchestration. It enables autonomous shifting and real-time routing based on mission priorities. By combining multiple providers and paths, the MOC is intended to provide more resilient connectivity. The article specifically links this design to cyber-resilient data paths and the ability to respond to adversary jamming.

The Space Data Network is intended to connect space-based sensors and communications systems with decision-makers and weapons platforms. Its near-term focus is the Trump administration’s Golden Dome missile defense initiative. Faster movement of useful data could help those users receive information through a more integrated network.

A sensor satellite might collect information that must travel through several space and ground systems before reaching a decision-maker or weapons platform. The MOC would coordinate that movement, choose paths based on mission priorities, and redirect traffic when another route is congested or jammed.

The article does not describe specific weapons or claim a measured improvement in military performance. It does identify high-speed, low-latency, and cyber-resilient connectivity across air, land, sea, and space. Those capabilities could strengthen the movement and coordination of sensor and communications data supporting missile defense and other connected missions.

The Pentagon is pursuing an open architecture because the Space Data Network must connect disparate military and eventually commercial satellite systems. A network built around multiple providers can combine different sensors, communications satellites, orbits, and ground stations. That gives the system more ways to move data toward users.

If one satellite constellation experiences congestion, the MOC can route traffic through another constellation. If an adversary jams one path, data can “hop” through a different space or ground route. The article presents this orchestration as a way to support high-speed, low-latency, and cyber-resilient connectivity.

The article does not say that one system is being discarded or identify a specific single-system alternative. It does show why integration matters: the MOC will bring multiple vendors together and provide real-time priority routing. That approach supports a broader, more adaptable network as related space systems develop.

Low-Earth-orbit satellites can relay digital data by receiving a signal, processing or forwarding it, and transmitting it to another satellite or a ground station. In the Space Data Network, those links can connect different satellite constellations with users on Earth. The article describes the backbone as a low-Earth-orbit constellation designed for high-speed, low-latency communications.

For example, data could move from a sensor satellite to another satellite, then down through a ground station. Network orchestration can select or change that route. If one path is congested or jammed, the data may “hop” through another constellation or station.

The shorter-distance explanation comes from established communications principles beyond the article’s detail. A signal traveling a shorter path generally takes less time to arrive, reducing propagation delay. Real networks also add processing and routing delays, so low orbit usually supports lower latency rather than eliminating delay entirely.