Data & Digital
The rig writes about forty thousand numbers a minute.
Most of them are noise. The job of our digital operation is to find the six that matter and put them in front of somebody who can act before the situation becomes expensive.
The pipeline
From the sensor to the decision
Acquisition
Surface parameters at 1 Hz, downhole on survey, mud gas continuously. Everything is timestamped at source against a single clock so that traces from different systems actually line up.
Transport
WITSML 2.0 over a redundant path — fibre or microwave onshore, VSAT with cellular failover offshore. Store-and-forward means a dropped link costs latency, not data.
Modelling
Torque and drag, hydraulics and hole cleaning models run live against the incoming trace rather than being rebuilt after the fact.
Alarming
Alarms fire on divergence from the model, not on absolute thresholds, because an absolute threshold in a 20,000 ft lateral is a guess.
Human review
A drilling engineer looks at every alarm. We do not send an automated message to a driller at three in the morning without a person having decided it is worth waking him for.
Client delivery
The same stream the operations centre sees is mirrored to the client workspace with no delay and no editing.
Predictive maintenance
Fix it on a Tuesday, not at 0300.
Every major rotating asset on the fleet — mud pumps, top drives, drawworks, generators — carries vibration and thermal monitoring feeding a condition model. When a signature drifts, the maintenance desk gets a work order and a part before the failure, not a phone call after it.
Since the programme went fleet-wide, unplanned mechanical downtime is down by roughly two thirds and we no longer lose whole days waiting on a top drive.
- Vibration and thermal signatures on all major rotating equipment
- Condition-based work orders raised automatically to the maintenance desk
- Spares held against predicted rather than historical demand
- Failure modes shared across the fleet, not kept on one rig
Client access
What an operator gets
| Feed | Format | Rate | Delivered to |
|---|---|---|---|
| Surface drilling parameters | WITSML 2.0 | 1 Hz | Client workspace + operator historian |
| Downhole MWD / LWD | WITSML 2.0 | On survey | Client workspace |
| Directional surveys | LAS / CSV | On station | Data room |
| Mud logging gas | WITSML 2.0 | 0.2 Hz | Client workspace |
| Daily drilling report | Signed PDF | Daily 06:00 | Data room |
| Mud and fluids report | Signed PDF | Daily 06:00 | Data room |
| Emissions telemetry | REST / JSON | 5 min | Client workspace |
| Marine and aircraft positions | AIS / ADS-B relay | 30 s | Client workspace |
| End of well report | Signed PDF | Within 10 days | Data room |
Security
How the data is held
Segregation
Operator data is segregated at the tenancy level. A client workspace can only ever resolve assets and documents attached to that programme.
Control systems
Rig control networks are physically separated from the business network. Data leaves the control system through a one-way path; nothing routes back in.
Access
Named accounts only, provisioned by Xtragate. No self-registration, no shared logins, and every session is logged against a session identifier.
Keys
Programmatic read-only keys are scoped to a single programme and rotate every ninety days.
Retention
Seven years minimum, written to immutable storage. Nothing on the record can be altered after issue — corrections are issued as a new revision.
Verification
Annual third-party penetration test of the client-facing platform, with findings tracked to closure.
How we take work.
Xtragate does not tender publicly and does not accept unsolicited enquiries. Programmes come to us through operators we already work for.