Vantomic OCC · Outage control
Facts, not status.
There is no status field in the database. Release state is computed on every read, from timestamped evidence. It cannot drift out of sync with reality, because there is nothing to drift.
How it works
Evidence → computation → consequence
1
Evidence
A fact is asserted once — by a worker, a Maximo closure, an Asset Suite attestation — with a timestamp, an author, and a decision record behind it.
2
Computation
Release is an OR over AND-groups of required facts, recomputed on read. Alternate paths need explicit human arming. Never inferred, never cached.
3
Consequence
Every blocker names the missing fact, the predecessor, the owning role, the system of record — and the critical-path hours and dollars at stake.
Continuous agents
Four agents, running while the outage runs.
They do not narrate. Each produces a computed result you can act on, with the arithmetic done by the engine rather than the model.
- Schedule reconciliation
- Dollar-ranked blockers
- Closure-evidence screening
- Resequencing with the hours already computed
What a blocker looks like
- Missing fact
- Post-maintenance test signature
- Predecessor
- WO 41-88213 closure evidence
- Owning role
- RP supervisor
- System of record
- Asset Suite
- Critical path
- 6.5 h
- Cost of wait
- $270,835
Illustrative. Every figure in the product is computed from your data and your replacement-power cost.
Coverage
Every discipline, your staff and your suppliers alike.
“Defer the RP survey to put that crew on the valve lineup — up to 6.5 hours of pull-in.”
Next
Pair it with Vantomic RP and the sentence completes itself.
OCC prices the hour. RP knows the hold is an RP hold, and names the missing signature.