WellOPS · Field Data Capture · Offline and mobile capture

Offline field data capture: the route in the truck, no signal required.

Most wellsites have no cell coverage, so an oilfield data capture app has to carry a working copy of the day rather than a connection to a server. This page explains exactly how that works in Field Data Capture: what is cached before the truck leaves the yard, what is recorded and checked at the site with no connection, what the device queues, and what happens when it comes back into range.
See Your Wells RankedView a Sample 6 AM Plan 

For field superintendents, pumpers, inspectors and HSE managers

In plain terms

What is offline field data capture in the oilfield?

Offline field data capture in oil and gas is the recording of wellsite readings and forms on a phone or tablet that has no cellular connection, with the records held on the device and sent to the office systems later. It works by loading each site on the day’s route, its forms and its prior readings onto the device while it still has service, recording tank gauges, well tests, runtime, downtime and inspection entries at the location with a time and location stamp, queueing those records on the device, and syncing them to production accounting, the historian and the maintenance system when a connection returns. The approach exists because most wellsites have no cellular service, so an app that needs a live connection to a server cannot be used where the readings are taken.

Why offline is the deciding requirement

A capture app that needs a signal cannot be used where the readings are taken.

Oil and gas field data capture is a harder problem than generic form apps admit. Most wellsites have no cell coverage. Crews work in gloves, in wind, next to running equipment. A tank gauge only matters if it reconciles against SCADA and lands in production accounting before month-end close. A form app built for a warehouse or a clinic assumes the device can reach a server when the form is submitted, and on a lease road that assumption fails at the second stop.

So the offline step is what separates oilfield capture from a generic mobile forms app. The device has to carry the day: which sites are on the route, which forms each one calls for, and what each well read last time, so a reading entered at the back forty of a lease with zero bars is checked and kept exactly as it would be with full coverage. The Field Data Capture module page sets that as one of four things an oilfield capture system is judged on, alongside speed of capture, validation at the moment of capture, and how deep the integration into the back office goes. This page is the first of the four, in detail.

The mechanism

How offline capture works, in four moves

The module page states this in one paragraph. Here is each move with what the device is actually holding at that point in the day.
  1. 01 · Before the yard

    Load the route while there is still service

    The day’s sites, the forms each one calls for and each well’s prior readings are cached on the phone or tablet before the truck leaves the yard. From that point the rest of the route does not depend on a live connection: the app carries a working copy of the day rather than a link to a server.
  2. 02 · At the site

    Record at the wellsite, with no connection

    Tank gauges, well tests, runtime and downtime notes, inspections and JSAs are entered on the device at the location: one-tap entries, voice-to-text for notes, photos for what a number cannot carry, signature capture where sign-off is required, and a GPS and time stamp on every entry.
  3. 03 · On the device

    Validate at the moment of entry, then queue

    Range checks against that well’s own history, required fields that cannot be skipped and unit guards all run on the device, offline. A suspect reading is questioned while the person who took it is still standing at the tank. Each accepted entry joins the queue the device carries back.
  4. 04 · Back in range

    Sync and reconcile when coverage returns

    The queued records sync through DataHub into production accounting, the historian and the maintenance system. Gauges reconcile against SCADA where sensors exist, and a discrepancy surfaces the same shift as a work item rather than at month-end close as an allocation argument.

Caching, queueing, syncing

What the device holds at each point in the day

Caching is the part that happens before the yard: the route, the forms and the prior readings go onto the device while it still has service. Queueing is the part that happens at the site: each validated entry is held on the device in the order it was taken. Syncing is the part that happens on the way back in: the queue drains to the systems of record when a connection returns, and the gauges are reconciled against SCADA as they land.

None of the three steps asks the field team member to do anything. The pumper opens the app, taps complete, adds a voice note or a photo, and moves to the next stop. The device does the rest, which is what it means for the shift-end re-keying session in the truck to be gone by design.

On the device
WhenWhat it holds
Before the yard
Every site on the day’s route, the forms each site calls for, and each well’s prior readings.Cached onto the device while it still has service.
At the site
Tank gauges, well tests, runtime, downtime notes, inspections and JSAs, with photos, voice notes and signatures where they belong, each carrying a GPS and time stamp.Validated on the device as each entry is made, then held in the device’s queue.
Back in range
The queued records, in the order they were taken.Synced through DataHub to production accounting, the historian and the maintenance system; gauges reconciled against SCADA where sensors exist.

What happens on conflict

When the manual gauge and the sensor disagree

The failure mode of paper and spreadsheet capture is not that data goes missing. It is that bad data goes unquestioned for weeks. A transposed tank level or a gauge read against the wrong well flows into production accounting, gets trusted, and surfaces as an allocation fight at close.

Offline capture handles the first half of that on the device: a reading outside the range of that well's own history is questioned while the person who took it is still at the tank, which is the only cheap moment to fix it. The second half happens on sync. Where a sensor exists, the manual gauge reconciles against SCADA automatically, and when the two disagree the discrepancy surfaces the same shift as a work item, flagged for review, instead of at month-end as a mystery.

What does not happen is the discrepancy passing silently into production accounting. A disagreement is information: the sensor may have drifted, the tank may have been hauled, the gauge may have been read on the wrong tank. The point of surfacing it the same day is that the person who can tell which is still on the route.

Every entry, four checks
Check
Range check against the well’s own historyOn the device, offline
Required fields that cannot be skippedOn the device, offline
Unit guardsOn the device, offline
Reconciliation against SCADA where sensors existSame shift, on sync

What the crew sees

The day arrives assembled, before the truck leaves the yard.

Every line on this screen was loaded while the device still had service: the stops, why each one is on the plan, what each is worth per day, and the drive between them. None of it depends on a signal at the wellsite. That is the argument for caching the route rather than fetching it stop by stop: the plan the crew opens at the first site is the same plan at the last one, and the readings they take at each stop are recorded against a site the device already knows.

The site screen behind each stop carries why the visit is on the plan, what the well is doing against its own history, and the work waiting there. Readings and forms are recorded against that site while the field team member is still standing at it. The plan the sequence produces the next morning is on the sample 6 AM plan.

Rendered from the synthetic field fixture · synthetic demo data · no customer screen

WellOPS route screen, Crew ANext stop Alderridge F-7H, High Fluid Level, $5,627/d of deferred production. Then Thanegate Unit 1, Gildweir Unit 4H, Gildweir Unit 3, Fennbrook C-4H, Mardspur 1-4H, Mardspur Unit 4. Synthetic demo data.6:00SYNTHETIC DATACREW A · 06:00 PLANGood morning7 stops · 2h 39m drive · $10,331/dNEXT STOP14 min driveCRITICALRANK #1STOP 1Alderridge F-7HAlderridge 1 · Rod pump · ETA 06:44HIGH FLUID LEVEL$5,627/d deferred productionNavigateLeave stopALL STOPS0 of 7 done2Thanegate Unit 125 min · High Fluid Level$3,057/d3Gildweir Unit 4H13 min · High Tank Level$3,056/d4Gildweir Unit 31 min · High Fluid Level$2,123/d5Fennbrook C-4H27 min · Plunger Not Cycling$767/d6Mardspur 1-4H29 min · Plunger Not Cycling$675/d7Mardspur Unit 41 min · Separator Dump Stuck$641/dScoreRouteSitesMapMore
The route, cached before the yard. Synthetic demo data.

Where this is running

Offline by design, at deployment scale.

5,000+
Wells in live deployments, where the capture layer runs on the crew devices in the cab.
Measured across 5,000+ wells in live deployments
0
Re-keying at shift end. The reading is captured once at the wellhead and lands in the systems of record without anyone typing it again.
By design, capability statement
Offline
Capture with no cell coverage: cached before the yard, queued at the site, synced when a connection returns.
Capability, not a percentage

The module's other figures, including the deployment figure for redundant tank gauging, carry their own provenance on the module page. Nothing on this page is a new number.

Frequently asked

Offline and mobile data capture, in the words people search for

Does field data capture work with no cell signal?
Yes. Field Data Capture is offline-first by design. The day’s sites, their forms and each well’s prior readings are cached on the phone or tablet while it still has service, and readings, photos and voice notes taken at the wellsite are stored on the device and synced when it comes back in range. No data is lost and nothing is reconciled by hand afterwards. Most wellsites have no cellular service, so mobile data capture that only works with coverage is not field-ready.
How does mobile data capture work in the oilfield?
In four moves. First, the day’s sites, forms and prior readings are loaded onto the device before the truck leaves the yard, while there is still service. Second, the field team member records tank gauges, well tests, runtime and downtime notes, inspections and JSAs on the device at the wellsite with no connection, using one-tap entries, voice-to-text, photos and signature capture, with a GPS and time stamp on every entry. Third, each entry is validated on the device as it is recorded, against range checks built from that well’s own history, required fields and unit guards, and then queued. Fourth, when the device returns to coverage the queue syncs to production accounting, the historian and the maintenance system, and gauges reconcile against SCADA. The offline step is what separates oilfield capture from a generic mobile forms app.
Is the data GPS validated?
Every entry carries a GPS and time stamp, so each reading records where and when it was taken, and that context stays attached to the well downstream. The value itself is validated separately, on the device and offline: range checks against that well’s own history, required fields that cannot be skipped, and unit guards. On sync, gauges reconcile against SCADA where sensors exist. The stamp says where the reading was taken; the checks say whether it is plausible; the reconciliation says whether the sensor agrees.
What happens when a manual gauge disagrees with SCADA?
The discrepancy surfaces the same shift, as a work item, instead of at month-end as a mystery. Gauges reconcile against SCADA automatically when the device syncs, and a manual reading that does not agree with the sensor is flagged for review rather than passed silently into production accounting. Clean capture is what makes the rest of the platform work, so a disagreement is treated as something to resolve that day.
Which systems does the data sync to when the connection returns?
Through DataHub, by direct API integration, into the production accounting system of record (Enertia, Quorum, W Energy or Oildex), with reconciliation against SCADA (Ignition, AVEVA PI, Cygnet) where sensors exist. Fields map to the production accounting schema, so the reading is captured once, synced once, and feeds one data pipeline into accounting, engineering and the ranked work plan. Nothing is re-keyed at shift end.
Can forms be changed for crews who are usually offline?
Yes. Admins build and version inspection forms, daily logs, well tests and tank gauges in a drag-and-drop editor, without code. Changes are pushed to every crew on the next sync, so a crew that spends the day out of coverage picks up the new form the next time the device is in range. There is no app store rebuild cycle.
What should an oilfield mobile data capture app include?
Four things decide whether a field data capture system survives contact with a real route: offline-first operation, because most wellsites have no coverage; speed of capture, meaning one-tap entries, voice notes and gloves-on usability; validation at capture, meaning range checks, required fields and SCADA reconciliation; and direct integration into production accounting so the data lands without re-entry. Photo, GPS and signature capture cover the inspection and compliance side.

Are your best people working on your most valuable work today?

See your own gauge sheet in the app, with the signal off.

Bring your gauge sheet, your well test form and one inspection checklist. We build them in the editor with you and put them on a crew device in the first week, validated against each well's own history.

See Your Wells RankedView a Sample 6 AM Plan 

Continue the cluster