Oil Rig Satellite Internet: Platform Design and Acceptance

Oil rig satellite internet is a complete platform communications system, not an antenna and an airtime plan. The design must match the asset's motion, operating area, hazardous-area boundaries, process and business applications, available power, environmental exposure, network-security architecture, support access, and required failure response.

This guide focuses on a single drilling rig or production platform. For fleet- and portfolio-level decisions, use oil and gas satellite communications. For telemetry and control transactions, use SCADA using satellite communication. For an independent protection path, see satellite backup for offshore operations.

Quick Design Rule

A rig link is qualified only when these inputs agree:

accepted rig connectivity = asset and operating-area dossier
                          + application and degraded-mode requirements
                          + authorized service and compatible terminal
                          + approved physical, power, and Ex boundaries
                          + segmented and monitored platform network
                          + support, failure, and lifecycle plan
                          + witnessed end-to-end acceptance tests

Do not start by asking which provider or orbit is “best.” First establish whether the asset is fixed, relocatable, station-keeping, towed, or operating as a vessel; whether the terminal must function during motion; and where transmission is legally and physically permitted.

Classify the Asset Before Selecting the Terminal

“Oil rig” can refer to different assets with different terminal requirements:

Record the asset type, coordinates or operating area, motion envelope, headings, draft or loading states, deck changes, cranes, derricks, flare and exhaust zones, neighboring structures, radios and radars, and planned relocation. A service approved at one fixed coordinate should not be assumed to cover transit or a new jurisdiction.

Build the Application and Traffic Dossier

Separate operational and human traffic rather than purchasing one undifferentiated speed tier:

For each application, record source and destination, direction of initiation, protocol, security mechanism, packet or transaction size, normal and burst rate, concurrent users, latency and loss tolerance, maximum outage, safe degraded mode, and support owner.

Headline download speed cannot replace this matrix. A service may pass a bulk speed test while alarm transactions, VPN reconnection, voice, or a vendor maintenance workflow fails.

Map the End-to-End Rig Architecture

platform OT / operations / IT / welfare zones
                    |
       firewall, routing, QoS, identity
                    |
          terminal and RF system
                    |
        satellite or constellation path
                    |
       gateway and provider network core
                    |
    enterprise edge, cloud, or public internet

Name the owner, monitoring point, acceptance boundary, and recovery procedure for every segment. The service seller, satellite-network operator, terminal supplier, installer, platform IT/OT teams, enterprise-security team, and application vendor may all own different parts.

Document the service demarcation carefully. A contractual uptime value may exclude platform power, local networking, blockage, weather, customer configuration, the public internet, cloud services, or the enterprise security overlay.

Survey Antenna Placement and Blockage

Create a three-dimensional obstruction and operations study rather than choosing the highest available deck point. Include:

• derrick, mast, cranes and their working envelopes, flare boom, exhaust, containers, temporary equipment, helideck restrictions, and future modifications;
• satellite look directions or sky-view requirements across platform motion, heading, trim, list, loading, and operating state;
• structural load path, vibration, fatigue, fasteners, penetrations, radome or antenna mount, inspection access, and dropped-object controls;
• separation from radar and other transmitters, RF exposure, electromagnetic compatibility, cable loss and routing, earthing or bonding, and lightning protection;
• heat, salt spray, corrosion, water, wind, icing where applicable, drainage, condensation, cleaning, and maintenance safety;
• hazardous-area boundary, escape routes, lifting paths, work permits, and simultaneous operations.

A model certificate does not prove that its location, mount, cable system, power feed, enclosure, or maintenance method is accepted on the asset.

Resolve the Hazardous-Area Boundary

Obtain the approved area-classification drawings before freezing the equipment list. Record every outdoor and indoor component, connector, gland, enclosure, cable route, isolator, power interface, and maintenance activity that enters or crosses a classified boundary.

The IECEx Certified Equipment Scheme assesses equipment for explosive atmospheres through approved bodies and laboratories. The IECEx service-facility scheme explicitly distinguishes facility competence from certification of a particular installation or area classification. In the European Union, Directive 2014/34/EU addresses equipment and protective systems intended for potentially explosive atmospheres.

Create a verification schedule with:

• exact model, revision, certificate, schedule, marking, group, protection concept, category or equipment protection level, temperature class, ambient range, and special conditions where applicable;
• installed location and classification, enclosure, interfaces, cable and gland selection, earthing or bonding, environmental limits, and inspection requirements;
• responsible designer, installer and inspector, certificate-status check, deviations, photographs, test results, and acceptance signature.

Do not state that a generic “marine-grade,” “IP-rated,” ATEX, or IECEx label approves the completed terminal installation.

Select the Satellite Service at Plan Level

Compare purchasable offers using the exact platform, operating area, terminal, and order date:

The ITU Radio Regulations, 2024 edition establish an international spectrum and radio-service framework; they do not replace national authorization for the actual station and operating area.

Orbit and Frequency Are Inputs

GEO, MEO, and LEO can all be candidates. The result depends on the application envelope, terminal, service plan, coverage geometry, gateway path, routing, congestion, transitions, support, and contract.

C-, Ku-, and Ka-band names likewise do not determine availability. Use actual uplink and downlink frequencies, elevation angle, antenna performance, interference, operator controls, and site propagation. ITU-R P.618-14 provides an in-force propagation prediction method for Earth-space systems. Use the applicable companion recommendations and site inputs; do not copy a generic offshore rain margin or terminal size.

Engineer Platform Power and Environmental Support

Measure the total communications load across startup, transmit, standby, degraded, recovery, heating or cooling, and battery-recharge states. Include terminals, RF equipment, routers, firewalls, switches, security appliances, local servers, monitoring, and conversion losses.

Define:

• normal and emergency feeds, protective devices, UPS or battery boundary, transfer behavior, maintenance bypass, and load shedding;
• whether the communications path is permitted or required on emergency power and for how long under the asset's approved design;
• environmental-control alarms, thermal margin, enclosure heat rejection, corrosion inspection, sealing, drainage, and spare storage;
• maintenance isolation, safe access, permit process, tools, test equipment, replacement procedure, and configuration restoration.

Avoid universal power or autonomy numbers. The approved load schedule, asset electrical philosophy, risk assessment, equipment limits, and recovery objective determine them.

Segment OT, IT, Welfare, and Management

Treat the satellite service as untrusted transport. Do not bridge crew or public internet directly into process networks.

NIST SP 800-82 Rev. 3 provides guidance for OT architectures and security controls. CISA's ICS recommended practices include defense-in-depth, remote-access, incident-response, procurement, and modem-security resources.

The platform design should define:

• security zones and conduits, permitted source/destination flows, inspection points, and default-deny boundaries;
• identity, privileged administration, certificates or keys, logging, time, vulnerability and patch processes, and configuration backup;
• vendor remote-access approval, jump path, named user, managed device, permitted action, time window, session evidence, and revocation;
• incident isolation, local operational continuity, forensic evidence, restoration, and reauthorization;
• welfare identity, rate policy, privacy, acceptable use, and separation from operational and management networks.

A public IP or VPN is not the security architecture. For addressing choices, use static IP for maritime satellite internet while applying the platform's OT-specific controls.

Design Resilience Around Platform Failure Domains

List the required failure cases before buying a second terminal:

Two terminals can still share the same view, mount, cable route, power distribution, router, gateway, security edge, DNS, account, or support team. Prove the failures that the second path removes.

The detailed protection-path method is in satellite backup for offshore operations.

Contract and Procurement Checklist

Attach these schedules to the request for proposal and final order:

1. Asset, operating-area, motion, obstruction, environment, power, hazardous-area, and application dossiers.
2. Exact service, terminal, mount, RF chain, software, plan, authorization, installation, and support scope.
3. Capacity, performance, availability, and measurement definitions with raw-data access.
4. Network, addressing, routing, VPN, DNS, security-zone, logging, data-handling, and remote-access responsibilities.
5. NOC, escalation, offshore dispatch, spares, restoration, software lifecycle, and configuration handover.
6. Change control for price, plan, hardware, network, gateway, satellite, software, coverage, policy, and upstream provider.
7. Installation acceptance, warranty, ownership, insurance, renewal, relocation, suspension, termination, removal, and restoration.

Compare total cost using the same platform and contract scenario. Include surveys, engineering, certificates, civil and electrical work, freight, lifting, permits, installation, commissioning, service, data, support, spares, inspection, offshore visits, changes, renewal, and removal. Generic monthly-price comparisons omit much of the actual rig cost.

Acceptance Test Plan

Agree safe conditions, witnesses, instruments, measurement points, thresholds, evidence ownership, and remedies before installation.

Documentation and Installation

• verify authorization, equipment identity, certification schedule, drawings, mount and fasteners, cable and penetration records, power and protection, environmental controls, labels, software, configuration, and inventory;
• accept structural, obstruction, RF, EMC, hazardous-area, electrical, network, cybersecurity, and work-completion records;
• demonstrate monitoring, alarms, support contacts, spares, manuals, training, backup, isolation, and recovery.

Network and Applications

• verify addressing, routes, DNS, time, VPN, identity, segmentation, firewall, QoS, logging, and management access;
• run real telemetry, alarm, approved command, historian, voice, video, enterprise, vendor-support, and welfare transactions as applicable;
• reproduce busy-period and degraded-capacity conditions and confirm critical traffic remains within its accepted envelope.

Failure and Recovery

• remove each approved dependency in turn without endangering the asset;
• measure detection, path decision, packet restoration, application recovery, alarm, escalation, repair, and failback separately;
• confirm local OT behavior, stale-data indication, buffering, security controls, and restricted traffic throughout.

Operating-Period Trial

Collect synchronized platform state, motion where applicable, heading, obstruction events, weather, power, terminal and RF metrics, path state, traffic, application outcomes, incidents, and support performance. Record untested locations and conditions as limitations.

FAQ

What is the best satellite internet for an oil rig?

There is no universal best service. Compare exact offers against the rig's fixed or moving status, operating area, authorization, application timing, hazardous-area design, power, environment, security, support, and failure requirements.

Can an oil rig use LEO satellite internet?

It can be a candidate when the selected terminal, plan, operating mode, authorization, sky view, service policy, application performance, security, and support pass the requirements. The orbit label alone is not acceptance evidence.

Does a rig need a public static IP?

Not automatically. Determine who initiates each session and whether the requirement is stable egress, inbound reachability, a private routed network, or a site-initiated overlay. Direct public exposure requires a justified and controlled security boundary.

How much bandwidth does an offshore platform need?

Calculate it from the application and traffic dossier, including simultaneous operations, alarms, remote support, voice/video, bulk data, encryption, retransmission, enterprise use, and welfare policy. Test the peak and degraded states.

Must the satellite terminal be IECEx or ATEX certified?

The approved area classification, jurisdiction, equipment location, and installation determine the requirements. Verify the exact equipment and certificate schedule, marking, conditions, interfaces, installation, inspection, and lifecycle obligations.

Is one satellite terminal enough?

Derive that decision from the platform's outage consequence and safe degraded mode. If a second path is required, prove that it removes the specified failure cases and can carry the required degraded applications.

Related Guides

• Oil and Gas Satellite Communications — portfolio planning across upstream, midstream, and downstream operations
• SCADA Using Satellite Communication — traffic, timing, protocol, outage, and application acceptance
• Satellite Backup for Offshore Operations — health checks, degraded policy, path independence, and recovery testing
• Offshore Satellite Connectivity — fixed platforms, remote islands, and cross-industry offshore infrastructure
• Satellite Terminal Architecture — antenna, RF chain, modem, and handoff boundaries
• Remote Site Network Monitoring — RF, terminal, network, and application telemetry