Production data
The connection to your production accounting system, what the platform reads, how units and dates are handled, and how freshness is reported.
The connection
The platform reads approved fields from your production accounting system of record over a least-privilege, SELECT-only connection.
It does not write to that system. The credential it uses does not need — and should not have — rights that would let it.
Word this precisely
The platform does accept input: gauges, hauls and corrections, recorded by people in the field and stored in the platform’s own database.
The accurate claim is read-only to your system of record. The stronger version — that the software has no write path at all — is not true and is not made anywhere in this documentation or on the site.
What is read
Well and property inventory, and daily production actuals:
| Field | Units |
|---|---|
| Oil | BBL |
| Gas | MCF |
| Water | BBL |
| Operating hours | hours in the production day, normally 0–24 |
Only approved fields are read. The set is explicit, not “whatever the schema offers”.
Production days
Production accounting systems use a production-day label that may not correspond to midnight-to-midnight local time. The platform uses the source system’s production-day boundary and states it rather than assuming a calendar day.
Where a contract day runs on a different boundary, that boundary is displayed alongside the data, so nobody has to remember which convention a given number follows.
Derived values are marked as derived
The platform calculates some values from what it reads. These are always identified as platform calculations and never presented as source data:
| Derived value | From |
|---|---|
| Daily operating-day fraction | operating hours ÷ 24 |
| Daily runtime percentage | operating hours ÷ 24 × 100 |
| Period operating days | sum of operating hours ÷ 24 |
Zero, missing, stale and truncated
These are four different things and they look different:
- Zero is a real measured zero and renders as
0. - Missing renders as missing. A null is never rendered as a zero.
- Stale carries its age. A four-hour-old value says so; it is never relabelled as current.
- Truncated says the result was truncated, so a partial answer is never mistaken for a complete one.
Source zeroes are preserved as zero and source nulls as missing. Values outside their expected range — operating hours above 24, for example — are retained and flagged rather than clamped, because clamping destroys the evidence that something is wrong upstream.
Freshness
Every figure carries when it was read and how current it is. Nothing is presented as fresh merely because a page happened to load.
When the connection fails
The affected surfaces report the failure and say what could not be read.
No sample data is substituted, no cached value is relabelled as current, and no gap is interpolated to keep a chart continuous. See data quality for why.
Reconciliation
Measured volumes from telemetry and gauge capture are compared against booked volumes, and the variance is carried as its own tracked figure.
Reconciliation happens at the 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.