Three stages. You control the promotions.
Every stage has an exit criterion, and no stage begins until the previous one has met it. There is no scheduled date on which OmniPath starts writing to your process — there is a standard you set, and we meet it or we don't advance.
The stages
Each rung states what is installed, what is connected, and the measured standard that has to be met before the next one starts.
Advisory (read-only)
Edge node installed, historian read path established, no write path exists. The policy runs in shadow alongside your operators and incumbent APC, and we report weekly on what it would have done versus what happened.
Exit criterion: shadow performance tracks or beats the incumbent on fuel per unit throughput and recycle valve open-time, across a representative ambient range, with zero recommended actions that would have approached the operating envelope.
Supervisory (narrow band)
Write path enabled to the regulatory layer, clamped to an operator-set band, slew-limited, shielded, with watchdog fallback tested and demonstrated before go-live.
Exit criterion: measured fuel or recycle improvement sustained over a full seasonal swing, no envelope excursions, no unplanned fallbacks attributable to the optimizer, and operator sign-off.
Widened band
The operator widens the authority band as confidence accrues. The band is always theirs. Scope may extend to additional units, additional stations, or start-stop sequencing.
Exit criterion: set by you.
Pilot options and pricing are provided when you request a pilot.
Failure modes, MOC scope and data requirements — the controls-engineer FAQ →