Well Intelligence Platform
Everything the field measured, carried through to what the books say.
Most systems in this category end at the telemetry. The platform carries the measurement all the way through to production actuals, and shows its work at every step.
Works with the RTUs, PLCs and flow computers you already run. Read-only to your system of record.
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
Field telemetry and connectivity
Connects to the field equipment you already have, over the protocols it already speaks, and normalizes what comes back into one asset model.
- Modbus RTU and TCP, DNP3, and OPC UA for direct device communication.
- MQTT with Sparkplug B through an edge gateway, for metered cellular links where polling every register is impractical.
- Tags from different vendors normalize into one well and facility model.
Historian
Time-series storage of field measurements at full resolution, queryable across arbitrary ranges.
- Every value keeps its source device, units, acquisition time and quality flag.
- Late, interpolated and quality-failed readings stay distinguishable from clean ones.
Alarms and call-out
Conditions on any measured or derived tag, routed to the person actually on call.
- Severity tiers with active, acknowledged, cleared and shelved states.
- Acknowledgment carries attribution — who cleared it, and when.
- Rationalization tooling shows which alarms fire most and which are never acknowledged.
Supervisory control
Setpoint writes, equipment start and stop, and remote shutdown against authorized field devices.
- Authority is granted per device group, not per user globally.
- Every command takes an explicit confirmation.
- Each one is written to an audit log that cannot be edited afterwards.
Field data capture
Gauge sheets, strapping tables and hauled loads, recorded on a phone at the tank and folded into the same pipeline as telemetry.
- Innage or outage, in the units the crew actually gauges in.
- Temperature and gravity correction for oil and condensate; water is volume change plus hauls.
- Works with no signal, and syncs when signal returns.
Production intelligence
Well inventory, daily actuals, derived runtime and operating-day metrics, trends, maps and exportable reports — reconciled against booked volumes.
- Units, dates and freshness labelled on every number.
- Zero, missing, stale and partially truncated stay visually distinct.
- A Data Quality surface reports which checks ran and which did not.
The shape of the problem
Two things are true at most operators at the same time. The field produces measurements continuously, and the business runs on a different set of numbers that get assembled monthly. Between them sits a gap that nobody owns.
The gap is not usually a technology problem. It is that the two sides were never designed to be compared. Field systems record what an instrument said. Accounting systems record what got booked. When they disagree — and they always disagree a little — there is no shared object that represents the disagreement, so it gets resolved by whoever has the most patience with a spreadsheet.
What this platform does differently
It treats the measurement and the booked volume as two views of the same thing, and makes the difference between them a first-class number: visible, tracked, and attributable to a specific tank, battery, day and input.
That only works if the measurement side is honest about where it came from. So every value in the system carries four things it never loses:
- the source that produced it — a specific device, a lab result, a pumper at a tank, or a configured default
- its units, retained and never silently converted
- its observation time, kept separate from the time it reached the server
- its quality state, so a reading that failed a check is never mistaken for one that passed
Both kinds of measurement, one pipeline
Most wells are not fully instrumented, and will not be next year either. A platform that only understands telemetry can only tell you about the wells that happen to have a transmitter on them.
Gauge capture closes that. A pumper records a tank gauge on a phone, the strapping table converts it to a volume in software, hauled loads are carried into the next calculation, and the result lands in the same reconciliation as telemetry — carrying different provenance, but treated as the same kind of fact.
Derived volumes from gauge capture are reported at the tank and battery level. A gauge measures a tank, and a battery commonly serves several wells; the platform does not manufacture a per-well split it cannot defend.
Deployment
Cloud is the default. Sign in and go; there is nothing to run. Customer-hosted deployment is available for operators whose security posture requires operational data to remain inside their own network.
Common questions
Do we have to replace any field hardware?
No. The platform speaks the protocols your existing RTUs, PLCs and flow computers already use. There is no hardware replacement programme.
Is this cloud or on-premises?
Cloud is the default and requires no infrastructure from you. Customer-hosted deployment is available where operational data has to stay inside your own network. Both run the same platform, and the choice does not change the feature set.
What happens when a data source fails?
The platform returns an error and says what failed. It never substitutes sample, estimated or stale-as-fresh data to keep a screen looking populated.
See it against your own wells.
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.