Well Intelligence Platform
Measured volumes sit beside booked volumes, and the variance between them is a tracked number rather than a month-end surprise. Every figure names the source it came from.
Works with the RTUs, PLCs and flow computers you already run. Read-only to your system of record.
| Stream | Measured | Booked | Variance | State |
|---|---|---|---|---|
| OILBBL | 1,284.6 | 1,290.0 | −5.4−0.42% | in tolerance |
| GASMCF | 14,203 | 14,203 | 0.00.00% | match |
| WATERBBL | 3,910.2 | 3,884.0 | +26.2+0.67% | review |
| CONDBBL | no data | 61.4 | — | no gauge |
None of this is exotic. It is what the last day of the month looks like at most operators.
The field screen says one thing, the report says another, and the real numbers have quietly been living in a spreadsheet for two years.
Shut in, or the poll failed? Software that renders both as 0 teaches the whole team to stop believing the screen.
Days reconstructing three weeks ago from memory, paper tickets and a tank that got trucked but never got recorded.
When everything alarms, nothing does. The one that mattered scrolled past at two in the morning.
Instrumented wells send telemetry. Tanks with no instrumentation get gauged by a pumper on a phone. Both arrive as the same kind of measurement, each carrying its own provenance, and both land in the same reconciliation against your books. That convergence is the product.
Instrumented
RTUs, PLCs, flow computers
Modbus · DNP3 · OPC UA · MQTT / Sparkplug B
Not instrumented
A pumper with a phone
gauge · haul · correction
both arrive as one measurement
One measurement pipeline
Normalized, quality-flagged, attributed
Every value keeps its source, units, observation time and quality state.
Reconciled
Measured against booked
reads your accounting system — SELECT only
Answered
Engineers, accountants, operations
trends · reports · exports
Five capabilities, one pipeline. Every one of them records where its numbers came from.
Modbus, DNP3 and OPC UA to the equipment you already run, plus MQTT with Sparkplug B for constrained cellular. Tags from different vendors normalize into one model.
Severity tiers, attributed acknowledgment, and escalation to whoever is actually on call. Rationalization shows which alarms are noise, because flooding is why crews stop trusting a system.
High-high level
JR14.TK03.LEVEL
07:41 · unacknowledged
Pressure above limit
JR14.SEP.TUBINGP
06:12 · J. Reyes
Rate below expected
JR14.MTR.GASRATE
until 08-09 · with reason
Setpoints, start and stop, remote shutdown. Authority is granted per device group rather than globally, and every command lands in an audit log that cannot be edited.
Entries are append-only. Nothing here can be edited or removed after the fact.
Pumpers gauge tanks from a phone, in innage or outage, in the units the crew works in. The strapping table does the conversion in software — nobody runs the arithmetic on a clipboard thirty times a day. Oil and condensate carry temperature and gravity correction; water is volume change plus what left on a truck. A hauled load is entered once and carried into the next calculation, so a tank that got trucked never reads as negative barrels.
Actuals, runtime, trends, maps and exports — with measurement reconciled against booked volumes, so the difference is a number you can open rather than a surprise you discover. Units, dates and freshness are labelled on everything.
| Day | Oil BBL | Gas MCF | Water BBL | Hours | State |
|---|---|---|---|---|---|
| 2026-08-06 | 128.4 | 1,420 | 391.0 | 24.0 | complete |
| 2026-08-05 | 131.9 | 1,388 | 402.6 | 24.0 | complete |
| 2026-08-04 | 96.2 | 1,011 | 288.4 | 17.5 | partial |
| 2026-08-03 | no data | no data | no data | no data | not received |
A day that did not arrive reads as no data, not as zero. The difference matters when someone is deciding whether a well is down.
Any vendor can draw a trend line. These are the design decisions underneath it.
Every stored value keeps its source device, its units, its acquisition time and its quality flag. A reading that arrived late, arrived interpolated or failed a check stays distinguishable from one that did not. When a number gets questioned, the platform can answer where it came from.
If a connection, schema, permission or query fails, the platform returns an error and says so. It never substitutes sample, estimated or stale-as-fresh data to keep a dashboard looking full. An empty chart with a stated reason is worth more than a complete one built from a guess.
Seeing a well and commanding it are separate grants. Every command captures who sent it, from where, the prior value, the commanded value and the device acknowledgment. Operators can hand out control without handing over a blank cheque.
Which wells and facilities anyone can see or command is bounded by their company grants. Identity lives in a separate database from operational data, and no query joins across the two. Revoking an account takes effect on the next request.
Tank batteries are where cell coverage is worst, and every pumper reading this has stood somewhere with no bars holding a phone. Gauges, hauls and corrections are captured and queued on the device with no signal at all, and sync when signal returns. The queue survives the browser closing and the phone restarting, and the pumper can see what is still waiting.
01 At the tank
TANK 3 · OIL
No paper table to carry. The strapping table turns the gauge into barrels.
02 Driving out
Held on this phone. Times stay as observed, not as sent.
03 Back in range
Every entry accounted for. A day of gauges is never silently dropped.
Well-level telemetry, artificial-lift monitoring, tank levels, runtime and downtime attribution, and production actuals you can hand to an accountant.
Facility and system telemetry, throughput and volume accounting across a gathering system, compressor and station monitoring, and measurement point rollups.
Levels, manual gauges and hauled volumes on the same footing, whether or not a tank has a transmitter on it.
Water handling, plants and stations, measured with the same provenance rules as everything else.
No. The platform talks to the RTUs, PLCs and flow computers you already have, over the protocols they already speak. There is no hardware replacement programme and no rip-and-replace step. If your field equipment works today, it keeps working.
Modbus RTU and Modbus TCP, DNP3, and OPC UA for direct device communication, plus MQTT with Sparkplug B through an edge gateway for publish-subscribe telemetry over constrained or metered cellular links. The protocol reference in the docs describes how each one is configured.
Yes. Cloud is the default and needs no infrastructure from you. Customer-hosted deployment is available where your security posture requires operational data to stay inside your own network. Both run the same platform; the deployment choice does not change the feature set.
Only accounts granted control authority on that specific device group. Visibility and control are separate grants, so a user who can see a well cannot necessarily command it. Every command requires an explicit confirmation and is written to an audit log recording who, what, when, from where, the prior value, the commanded value and the device acknowledgment.
That is what gauge sheets are for, and most wells are not fully instrumented. A pumper records the tank gauge on a phone, the strapping table converts it to a volume, and that volume flows into the same reconciliation as telemetry. Derived volumes are reported at the tank and battery level, which is the level a gauge can honestly support.
The pumper enters the load that left, and that volume is carried into the next production calculation — production since the last gauge is the volume change plus what went out on a truck. Volume alone is enough if a crew wants to move fast. If you need the paper trail, capture the full run ticket or disposal manifest with ticket number, carrier and destination. Both produce the same corrected figure; one just carries more history. Systems that ignore hauls make a tank that got trucked look like it produced negative barrels, and somebody fixes that by hand at month end, every month, forever.
No. The platform runs in the mobile browser and installs to the phone home screen, where it opens full screen and behaves like an app. There is no app store listing to wait on and nothing for IT to approve, and updates land the moment they ship rather than whenever a crew gets around to updating.
The platform reads approved fields from it over a least-privilege, SELECT-only connection and never writes to it. Field input you record here — gauges, hauls, corrections — is stored in the platform own database, not pushed back into your books. The point is to put measured and booked volumes side by side so the variance is visible, not to take over your accounting.
A demo runs against synthetic data first, then against a read-only connection to your system of record if you want to see real numbers. Or start a trial and look around on your own.