Platform
The field number and the booked number, side by side.
The platform reads approved fields from your production accounting system over a least-privilege, SELECT-only connection, and puts what the field measured next to what the books say. The difference is a tracked number, not a month-end discovery.
Read-only to your system of record. The platform never writes to it.
| 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.
Reconciliation as an object, not an exercise
Measured and booked volumes sit in the same view, with the variance between them carried as its own figure you can open and attribute.
- Variance is tracked per stream, per day, at the level both sides can honestly support.
- A difference has a place to live, so it stops being resolved from memory at month end.
Actuals with their context attached
Daily oil, gas and water volumes with operating hours, plus the runtime and operating-day metrics derived from them.
- Units labelled on every figure — BBL, MCF, PSIG — and never silently converted.
- Production-day boundaries stated rather than assumed.
- Derived values are marked as derived, never presented as source data.
Zero is not the same as missing
A null renders as missing. A zero renders as zero. Stale renders as stale, with its age. Truncated results say they were truncated.
- The difference matters when someone is deciding whether a well is shut in or a poll failed.
- Out-of-range values are retained and flagged rather than clamped into something plausible.
Inventory, trends, maps and exports
Well and facility inventory, bounded multi-well trends, coordinate maps, and reports you can export without a separate reporting tool.
- Deep links that survive a refresh, so a number you found can be sent to someone else.
- CSV export from the surfaces where the numbers are, not from a separate module.
Why reconciliation belongs in the SCADA layer
Reconciliation usually happens after the fact, in a spreadsheet, by a person who has to reconstruct the month from several systems that were never designed to agree. That work is slow because the evidence is scattered, and it is fragile because the reasoning lives in someone’s head.
Putting reconciliation next to the measurement changes what it costs. The platform already holds the measured side with full provenance — which device, which gauge, which lab result, what time, what quality state. Reading the booked side and comparing them is then a daily operation rather than a monthly excavation.
What the platform reads, and what it never touches
It reads approved fields from your production accounting system of record over a least-privilege connection restricted to SELECT. It does not write to that system, does not update it, and does not need credentials that could.
That distinction is worth stating precisely, because the platform does accept input — gauges, hauls, corrections — which it stores in its own database. The correct claim is read-only to your system of record, not that the software accepts no input at all.
Freshness is part of the number
Every figure carries when it was read and how current it is. A value that is four hours old says so. A source that has not answered says so. Nothing is presented as fresh because a page happened to load.
Common questions
Does the platform write anything back to our accounting system?
No. The connection to your system of record is read-only — a least-privilege, SELECT-only connection to approved fields. Field input you record in the platform, such as gauges and hauls, is stored in the platform own database and is never pushed into your books.
What if the connection to our accounting system fails?
The affected surfaces report the failure and say what could not be read. Nothing is filled in with estimated or cached-as-current values to keep the page looking complete.
At what level does reconciliation happen?
At whatever level both sides can honestly support. Telemetry and gauge capture resolve to a tank and a battery; your books resolve to whatever entity you book against. The platform reconciles where those meet rather than manufacturing a split it cannot defend.
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.