Vantomic OCC · Outage control
Facts, not status.
Vantomic OCC sits between outage planning and outage operations. During planning it reads the schedule and suggests a tighter sequence. During the outage it reads what actually happened in the field and recommends the exact move that recovers the critical path. It never writes back to your systems of record.
Two modes
Planning mode becomes operations mode.
Planning mode
Vantomic OCC joins the planning team 18 to 24 months before the outage starts. Refueling, maintenance, or forced outage; BWR or PWR — it reads the Primavera P6 schedule (or whichever planner you use) and suggests how to make the plan more efficient before a single day is committed.
It is one-way: OCC does not change the plan. Planners review the suggestion, update P6 if they agree, and the improved schedule flows back into OCC on the next read.
Operations mode
When the outage starts, OCC switches to operations mode. It ingests field attestations — work-order closures, clearance sign-offs, RCA documentation — and recomputes release state from what actually happened, not what was scheduled.
When a signature is missing, a work order stalls, or a crew is waiting, it names the missing fact, the downstream impact, and the exact dollars-and-hours move that recovers the schedule.
Advisory, not autonomous. Vantomic OCC never modifies your EAM, scheduler, or clearance system. It gives your outage managers and operations staff a live, priced recommendation; your people decide what to execute in the field.
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
Compares the live P6 plan against real field attestations and flags where actual progress has diverged from the schedule.
Dollar-ranked blockers
Identifies what is constraining the critical path and ranks each blocker by its replacement-power cost, so the most expensive wait is seen first.
Closure-evidence screening
Checks that every completed work order has the required evidence, sign-offs and documentation before downstream work is released.
Resequencing with the hours already computed
Suggests alternative orderings of pending work to recover slipped time, with the hour and dollar savings already calculated.
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.