Solutions
Most of your wells are not instrumented. They still have to count.
An upstream field is a mix: a handful of wells with good instrumentation, a long tail with a tank and a pumper, and a production report that has to cover all of them. The platform measures both the same way.
| 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.
The instrumented wells
Well-level telemetry from the controllers already on location, over the protocols they already speak.
- Plunger, rod pump and other artificial-lift monitoring from the controller data you already generate.
- Tubing, casing and line pressure alongside production, on one production-day basis.
- Tank levels where a transmitter exists — cross-checked against the manual gauge where both do.
The long tail
The wells with no instrumentation are usually the majority, and they are where allocation arguments start.
- Pumpers gauge tanks on a phone; the strapping table converts the reading to a volume.
- Hauled loads are recorded and carried into the next calculation.
- Volumes are reported at the tank and battery level, which is what a gauge can honestly support.
Runtime and downtime you can attribute
Operating hours and the runtime and operating-day metrics derived from them, with the arithmetic stated rather than assumed.
- Derived values are marked as derived and never presented as source data.
- Hours outside the expected range are retained and flagged rather than clamped.
- A day that did not arrive reads as missing, not as a zero-production day.
Non-operated and per-entity scoping
What a given user or partner can see is bounded by explicit company grants.
- Non-operated interests can be scoped separately from operated assets.
- Scoping applies to exports and the mobile experience, not only to the main interface.
The gap that shows up every month
The instrumented wells are not the problem. They report continuously, the data looks credible, and everyone believes it.
The problem is that the production report covers every well, and for most of them the evidence is a gauge sheet, a text message and a haul that may or may not have been written down. Those two classes of well get combined into one report, and the combination is where the confidence quietly drains out.
Treating the manual side with the same rigour as the telemetry side — the same provenance, the same units discipline, the same reconciliation — is what closes that gap. It is not a smaller feature for lesser wells. It is the same pipeline.
Common questions
Can we start with just the wells that have instrumentation?
Yes, and most operators do. Gauge capture can be added to the uninstrumented tail afterwards without changing how the instrumented wells are handled, because both feed the same pipeline.
Does the platform allocate tank volumes to individual wells?
No. A battery commonly serves several wells, and any split between them is an allocation decision with real consequences for how defensible the number is. The platform reports at the tank and battery level rather than manufacturing a per-well figure.
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.