Solutions
A gathering system is an accounting problem wearing a pipeline costume.
Throughput has to add up across measurement points, and when it does not, somebody has to find out where. The platform keeps every measurement point attributable and reconciles the rollup against what was booked.
| Stream | Measured | Booked | Variance | State |
|---|---|---|---|---|
| OILBBL | 1,284.6 | 1,290.0 | −5.4−0.42% | in tolerance |
| GASMCF | 14,203 | 14,203 | 0.00.00% | match |
| WATERBBL | 3,910.2 | 3,884.0 | +26.2+0.67% | review |
| CONDBBL | no data | 61.4 | — | no gauge |
Facility and system telemetry
Station, compressor and facility data from the equipment already installed, over standard protocols.
- Compressor and station monitoring alongside the measurement points they serve.
- Suction and discharge conditions kept with their units and their quality state.
- Devices that stop answering are reported as such rather than showing a last-known value.
Measurement point rollups
Volumes aggregate from measurement points up through the system, and every level of the rollup keeps its inputs.
- An aggregate can be opened to the points that produced it.
- A point that did not report is visible in the rollup as missing rather than contributing zero.
- Imbalance is a number you can track rather than a residual someone notices later.
Throughput against the books
System throughput is reconciled against booked volumes on the same daily basis as everything else.
- Variance is carried per stream and per point, with its own state.
- The comparison happens daily, so a drift is caught while it is still small.
Partner and shipper visibility
Counterparties see what they are granted and nothing else.
- Company-scoped grants bound visibility to specific assets.
- Control authority is a separate grant from visibility.
- Exports carry the same scoping as the interface.
Why missing and zero have to look different here
On a gathering system, a measurement point that reports zero and a measurement point that failed to report produce very different conclusions and identical arithmetic if the software treats them the same way.
Rolled up across a system, a handful of silently-zeroed points turn into an imbalance that looks like a physical problem. People go looking for a leak, or for theft, or for a mismeasurement that is not there.
The platform keeps those two states distinct all the way up the rollup. An aggregate that includes a point which did not report says so, which usually resolves the question before anyone drives anywhere.
Common questions
Can shippers or partners have their own access?
Yes. Access is bounded by explicit company grants, so a counterparty sees only the assets you have granted them. Visibility and control are separate grants, so granting visibility never implies command rights.
How is system imbalance handled?
As a tracked figure rather than a residual. Because each measurement point retains its own provenance and quality state, an imbalance can be attributed to the points that contributed to it, including the ones that did not report.
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.