How it works

From the cabin to every screen.

Follow a single reading from the rig’s database to the people who need it, including what happens when the satellite link drops.

How data travels

  1. 01 / 05

    Read at the rigsite

    The Transmitter reads new rows from the rig’s database (Ancer), a WITS Level 0 feed or your own SQL query, from a saved cursor, so nothing is missed or sent twice.

  2. 02 / 05

    Sent in compressed batches

    Readings leave the cabin as gzipped batches over outbound HTTPS. There are no inbound ports to open and no VPN to keep alive.

  3. 03 / 05

    The link drops. Nothing is lost.

    When the satellite or 4G link goes down, rows wait in a local buffer, tagged with their well. The rig carries on as normal.

  4. 04 / 05

    Back online, oldest first

    As soon as the link returns, the buffer empties in order, so the chart in town fills in exactly as it happened on the rig.

  5. 05 / 05

    Every screen, at once

    The cloud stores each value, checks the alarm rules and pushes the reading live to everyone on the well: in the office, on a phone, or on a wall display.

CABIN 1tblTimecurrentNRG-Drill TransmitterSendingWell OML-58 7HSent 18,204Buffer 0 rowsLocal bufferlink downNRG-Drill cloudstore · alarms · livealarm rules ✓Office · LagosPhone · HoustonWall display · Port Harcourt

Architecture

Three parts, one stream.

Architecture

At the rigsite

  • NRG-Drill Transmitter on the cabin PC (Windows)
  • Reads Ancer, WITS Level 0 or custom SQL
  • Facility key, well chosen at the cabin
  • Local buffer for outages
  • Outbound HTTPS only, no inbound ports

In the cloud

  • Ingest checks the key and the facility’s allowed sources
  • Each value stored in your organisation’s own schema
  • Alarm rules checked as data is stored
  • Live push to every screen on the well
  • Retention, usage and audit jobs

On every screen

  • Web app in any modern browser
  • Live chart, dashboards and alarms
  • Wall displays in kiosk view
  • Phones and tablets, stacked layout
  • Sign-in tokens kept in memory, never local storage

For your IT team

What runs at the rigsite, exactly.

One Windows app per cabin. It reads the rig's data with read access, keeps its settings and buffer in the user's local application data, and makes outbound HTTPS requests to NRG-Drill. It opens no ports and changes nothing in the rig's own systems.

Direction
Outbound only
Protocol
HTTPS, gzipped JSON
Auth
Facility key (hashed server-side)
Buffer
Local SQLite file
Cursor
Persisted, no repeats
Time
Rig-local → UTC

Rollout

Live in an afternoon.

No servers to install, no VPN, no changes to the rig’s own systems.

Rollout steps

  1. 1

    Install the Transmitter

    A small Windows app on the cabin PC that can read the rig database or WITS feed. Outbound HTTPS only.

  2. 2

    Pair it with a facility key

    Create the cabin in Admin → Facilities and paste its key. The cabin picks the well it’s on.

  3. 3

    Pick a dashboard

    Start from the Rig display template, or build your own and share it with the organisation.

  4. 4

    Watch it live

    Invite engineers, pair the wall display, and set your alarm rules. The data starts flowing within seconds.

See your own rig, live, this week.

Book a 30-minute demo. We’ll show NRG-Drill on a live well and talk through connecting your first cabin.

Book a demo Request a trial