Platform
The barrels that left on a truck still count.
A tank that got hauled produces a negative volume change. Software that ignores the haul reports negative barrels, somebody fixes it by hand at month end, and the real numbers move into a spreadsheet. This is the part that stops that happening.
Derived volumes are reported at the tank and battery level.
Hauled loads, at whatever detail you want
Production since the last gauge is the volume change plus what went out on a truck. The pumper records the load that left, and it is carried into the next calculation.
- Volume alone is enough. A crew that needs to move fast enters one number.
- Full run ticket or disposal manifest — ticket number, carrier, destination — where you need the paper trail.
- Both produce the same corrected production figure. One simply carries more history with it.
- A haul that would drive production negative is flagged, not quietly absorbed.
Innage or outage, both first class
Different crews and different tanks are gauged differently. Forcing one convention is how you get bad data, so the platform accepts either and records which was used.
- Innage measured up from the bottom, outage measured down from the top.
- Feet-inches-eighths or decimal inches — the units your crew already works in.
- The raw observation is kept exactly as recorded, alongside the normalized value.
The strapping table does the arithmetic
The tank strapping table converts a gauge height into a volume in software. The pumper never carries a paper table and never does the sum.
- The calculation happens once, correctly, instead of thirty times a day on a clipboard.
- Values between table entries are interpolated, and the result is marked as interpolated.
- A reading outside the table bounds is rejected with an explanation, never extrapolated.
- Tables are versioned. Re-strapping a tank creates a new version rather than editing the old one.
Oil and condensate, corrected properly
The strapped gauge yields gross observed volume at observed temperature. Temperature and gravity give a volume correction factor to 60 °F, and BS&W is deducted to reach net standard volume.
- GOV × VCF = GSV, then GSV less BS&W = NSV.
- Every intermediate value is retained, not collapsed into a final number.
- Water gets no thermal or gravity correction — it is volume change plus hauled volume, and the platform does not pretend otherwise.
One rule for every measurement input
BS&W, API gravity and observed temperature can each arrive from three places. The platform takes all three and applies one stated precedence, most specific first.
- A value recorded with this gauge — shakeout, hydrometer, thermometer.
- A current lab result on file for that tank.
- The configured default for that tank.
- Every computed volume records which source each input actually came from. An NSV resting on a tank default looks different from one resting on a shakeout taken that morning.
- If no source supplies a required input, the volume is reported as unavailable with the missing input named — never computed from an assumed value.
Corrections that do not rewrite history
A pumper can amend an earlier gauge, haul or input from the field. Nothing is overwritten and nothing is deleted.
- The original reading is retained; the correction records who made it and when.
- Downstream volumes recompute, including intervals that were already closed.
- Anything that changed is flagged as restated rather than silently replaced. A production figure someone already acted on does not get rewritten behind their back.
Gauge the tank. Drive back. It syncs.
Tank batteries are where coverage is worst. Every pumper reading this has stood somewhere with no bars, holding a phone.
Gauges, hauls and corrections are captured and queued on the device whether or not there is service. The queue survives the app closing and the phone restarting. The pumper can see what is queued and what has synced, because a field app that silently loses a day of gauges is worse than a paper sheet, and crews know it.
Observation time is captured on the device when the reading is taken. The time it reached the server is recorded separately. Offline entry makes those two diverge by hours, and treating them as the same number corrupts every interval calculation downstream.
Gauged tanks and instrumented tanks are the same kind of fact
A manually gauged tank and an instrumented tank are the same kind of measurement to everything downstream. They carry different provenance, and the platform records which is which — but they land in the same production surfaces, the same trends and the same reconciliation.
That is what gives an operator real coverage across a whole field, rather than across the twenty wells that happen to have a transmitter on them.
Built for the actual conditions
Usable on a phone, with gloves on, in sunlight, with intermittent or absent cell service. It installs to the home screen and opens full screen, so there is no app store to wait on and nothing for IT to approve before a contractor pumper can start work.
A note on measurement standards
The platform uses the industry vocabulary — GOV, VCF, GSV, BS&W, NSV — because that is what the work is called and the people doing it know these terms. It does not claim conformance to a named measurement standard. «TODO: confirm» which correction-factor table family the implementation uses, and whether those tables are carried in the product or supplied by the operator, before any standard is named on this page.
Common questions
What if a tank has no strapping table yet?
The tank shows as unmeasurable rather than disappearing, and gauges can still be recorded against it. Volumes compute as soon as a table is loaded. Operators supply their own tables, because a strapping table comes from a physical survey of one specific vessel.
Does a gauge give us production per well?
No, and the platform does not claim it does. A gauge measures a tank, a tank sits on a battery, and a battery commonly serves several wells. Derived volumes are reported at the tank and battery level, which is the level a gauge can honestly support.
What happens if a tank has a level transmitter as well?
The transmitter reading and the manual gauge are cross-checked. A drifting transmitter shows up as a growing disagreement between the two rather than as silently wrong data.
Can a pumper gauge a tank with no cell service?
Yes. Entry is captured and queued on the device with no connectivity and syncs when signal returns. The queue survives the browser closing and the phone restarting, and the pumper can see what is still waiting to send.
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.