A drilling rig is one of the more hostile environments a computer system can run in: vibration, salt air, temperature swings, ATEX-rated hazardous zones, and a satellite link the weather degrades. Operations run around the clock, and decisions made by software carry the same consequences as decisions made by the crew.
Most industrial IT infrastructure was designed for offices and data centers, where connectivity is reliable and a 500ms delay costs nothing. On a rig, what that delay is in determines what it means.
The connectivity problem
GEO satellite, which most offshore rigs ran until recently, delivers latency of 600ms or more per round-trip, before processing time, and before the 10–15% of hours spent in outage or degraded service. Starlink Maritime has changed the bandwidth economics but not the physics: even at 20–50ms latency, a real-time control loop at the asset cannot tolerate a cloud round-trip on each decision.
A decision that needs to happen in 150ms cannot be made 500km away.
What this means for Red Zone Manager
Helin Red Zone Manager monitors drill floors with computer vision. When a person enters a restricted zone, the system activates warning lights and sends a real-time alert. That response happens in under 150ms. The decision executes at the rig.
At BP's operations: 1,176 drilling events, 14,162 trips, 1,179 zone intrusions detected. The outcome BP cited: human lives saved.
Noble Corporation runs the system across 40+ rigs. The hardware sits on the asset. The application runs locally. The uplink carries compliance logs, video clips flagged for review, and management dashboards. When the satellite link drops, the system keeps working.
Data sovereignty on a rig
Drilling data is commercially sensitive. Operators contract with clients who have specific requirements about where data can be stored and who can access it. Raw operational data is processed at the asset and stays there unless the operator decides to send it elsewhere. What travels to the cloud is structured output: alerts, logs, dashboards.
For BP, Shell, and similar operators with strict data handling requirements, that is a contract condition, not a preference.
NIS2 in offshore operations
Offshore drilling operators that qualify as essential entities under NIS2 face the same 24-hour early warning and 72-hour incident reporting obligations as any other energy sector operator. An OT environment fragmented across rig-specific systems, vendor VPNs, and manual logs cannot produce a compliant incident report within the deadline.
Certificate-based device identity, zero-trust access, and automated incident logging at the edge produce the audit trail as a by-product of normal operations, rather than requiring a preparation exercise before each review.
The governance question
For operators evaluating architecture decisions on rigs, the question is not whether to run software locally. It is which local software to run, and who is responsible when it does not.
Back to the main guide: Industrial edge computing, what it is and how it works
By Helin