Hybrid Networks in Oil & Gas: Where LEO Satellite Fits

Oil & Gas operators have never relied on a single network, and that is not changing. What is changing is the mix. As operations become more connected, remote monitoring, SCADA and telemetry, video, automation, connected worker applications and edge systems all place different demands on a network, and those demands shift again from a well pad to a pipeline, compressor station, terminal or processing facility.

The result is an increasingly hybrid connectivity environment, with different LAN and WAN technologies working together and different networks serving as primary, secondary or contingency paths depending on the site. Low-Earth-orbit (LEO) satellite is adding a new option to that mix, and it is worth thinking through deliberately rather than treating it as a plug-and-play add-on.

LEO changes the conversation, not the fundamentals

Satellite connectivity is not new to Oil & Gas. What has changed is the performance and accessibility of LEO services, which make satellite practical for a broader range of remote and distributed sites than earlier satellite options allowed.

That does not mean LEO is set to replace microwave, cellular, fiber or fixed wireless. The more useful question is where LEO belongs in the connectivity architecture, and when it should complement rather than replace the networks already in place.

At one site, microwave might remain the primary transport while LEO provides a contingency path. At another, cellular could be primary with satellite as secondary. At a particularly remote location, satellite might reasonably serve as the primary connection. The right answer depends on what the site and its applications actually require, not on which technology is newest.

A second connection doesn't automatically create resilience

LEO is a good illustration of why hybrid-network design needs to go beyond simply adding another path. Imagine a remote Oil & Gas site running on a private microwave link or cellular service with a private APN. Adding LEO satellite can provide valuable path diversity if that primary connection goes down.

But when traffic fails over, what else changes? The alternate path may have different characteristics for capacity, latency, routing, management and security. Maintaining connectivity does not necessarily mean every application keeps operating with the same characteristics it had on the primary network.

That raises an important design principle: a contingency network is not truly a contingency architecture unless you understand what changes when you fail over.

Security is a good example. Enterprises can use Starlink with VPN and SD-WAN appliances, and Starlink now also offers Private Networking options designed to keep enterprise traffic off the public internet. The point for operators is not that LEO is inherently secure or insecure. It is that the security architecture needs to be designed for the specific service being used and the applications it supports, especially when traffic moves between different primary, secondary and contingency transports.

Start with the requirement, not the network

This is why the hybrid-network discussion should not start with satellite versus microwave, or cellular versus fixed wireless. It should start with the operation itself.

• What applications need connectivity, and how critical are they?
• What happens if the primary connection fails?
• How much capacity do they need, and what latency can they tolerate?
• What security controls must remain in place?
• How quickly must traffic move to another path?

Only after answering those questions can an operator determine which combination of fiber, microwave, fixed wireless, cellular and satellite makes sense, and what role each should play. In some cases that analysis will validate the architecture already in place. In others it will point toward adding a transport for resilience or capacity. Where requirements have shifted significantly, it may justify redesigning portions of the network. The objective is not to use more networks. It is to use the right networks, in the right roles, for the operational requirement.

Three questions worth asking about your hybrid network

As LEO becomes a practical option alongside established transports, Oil & Gas operators should be asking:

• When should LEO complement microwave, cellular or fiber rather than replace them?
• What needs to remain consistent when operations fail over from one transport to another?
• How should we decide which network is primary, secondary or contingency for a particular site or application?

Those questions are ultimately bigger than satellite. They are about designing connectivity for Oil & Gas environments that are becoming more distributed, more connected and more operationally dependent on the network staying up. Future Technologies works through these questions with operators site by site, validating architecture choices before they reach the field.

A contingency network isn't truly a contingency architecture unless you understand what changes when you fail over.

Future Technologies will be discussing these questions at the ENTELEC Fall Seminar during a panel on hybrid networks on Thursday, October 8th at 1:15 PM. Visit the Future Technologies Lab on Wheels at the event to continue the conversation about where LEO and other connectivity options fit within your operational network.