Product · Balance

Custody variance. Explained and owned.

Each day's custody and imbalance variance split into measurement, movement or unexplained, valued, with a named owner. From daily exports, beside the measurement suite you already run.

In designDesigned from existing building blocks. Not built.

Variance split: measurement, movement, unexplained

Meter drift named within days (target; first proof pending)

Each difference valued; an owner named

Needs

Daily ticket, movement and gauge exports
Tariff and balancing-agreement rules
An owner of the LAUF (gas) or loss/gain (liquids) number
A blind, scored first month

Is not

Not a custody-transfer calculation
Not a settlement system
No OT connection

Where it stops

Sits beside the measurement suite. Never recomputes custody quantities for settlement. Every UNEXPLAINED carries its provenance, so it never reads as an accusation.

Built from

What exists, what does not

The reconciliation engine (telecom harness, separate codebase): register against inventory against ERP against billing, each difference valued, who fixes it named. The request model: done-when lines, evidence, a party, a clock, independent acceptance. Wavepin's observation fabric (units, quality flags, freeze and dropout detection) and its UNEXPLAINED discipline. The read-only adapter framework with recordings replay. Shares the Register engine. Not built: custody loaders, the reconciliation statistics, balancing-agreement and tariff rules.

First proof

The experiment

A synthetic gathering system (ten meters, two tanks, truck loadings) with injected faults: a 0.1 %-per-month drift on one meter, one omitted manual movement, one stuck transmitter. Run the reconciliation on the daily data, publish the variance split and the owner list as receipts, show the drift named within days rather than at the quarterly review. Then one month of anonymised tickets from a pilot partner, replayed read-only and scored blind.