Platform
Two products, one engine, and no place for the truth to drift.
Bought separately they are two good tools. Bought together they answer a question nobody else can even form: what the delay is costing, and which fact is causing it.
What is true, and what it costs
Vantomic OCC
Facts, not status.
The whole outage, every discipline — maintenance, electrical, I&C, mechanical, RP, operations, NDT and third-party suppliers. Release state recomputed live from evidence, every blocker named and priced against your own replacement-power cost, with the recovery move already worked out.
Explore Vantomic OCCWhen RP is the reason
Vantomic RP
The only RP system that learns from its own estimates.
A complete radiation-protection operation — surveys, RWPs, dose of record, scheduling, NRC reporting and PI-historian trending in one system. Plus a feedback loop that compares estimated to actual job dose and calibrates the next pre-job brief from what actually happened.
Explore Vantomic RPThe engine
Evidence, computation, consequence.
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.
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.
Four agents running continuously
- Schedule reconciliation
- Dollar-ranked blockers
- Closure-evidence screening
- Resequencing with the hours already computed
Coverage
Every discipline. Every crew. One live picture.
The engine is discipline-agnostic. It tracks the work, the crew and the system of record — whoever owns the activity — and treats your own staff and your suppliers the same way.
Where the gap is
The exact missing fact, the owning role, the system of record.
What to do about it
Defer this crew onto the critical path, or run that sign-off in parallel.
What it saves
The hours pulled in, priced against your replacement-power cost.
“Defer the RP survey to put that crew on the valve lineup — up to 6.5 hours of pull-in.” The suggestion is real, and the hours are already computed.
The built-in assistant
Ask it in plain language. Every answer is grounded and checked.
- “What's the predicted dose for RWP 24-0417, and how accurate were our last estimates on jobs like it?”
- “How much dose has badge 4471 taken this year, and what percent of the annual limit is that?”
- “What's driving the collective dose on the RCP survey route this outage?”
- “Can we justify reducing survey frequency at this point? Show me the 30-year PI trend.”
- “What does 10 CFR 20.1201 say about the annual dose limit?”
How it is enforced
- Every question routes to a closed, fixed catalogue of engine-backed answers.
- Every number is computed by a deterministic tool — the model never does arithmetic.
- Anything outside the catalogue is refused with fixed text, not model narration.
- The AI runs on its own database role, with INSERT revoked on every authoritative table.
- A post-answer check re-verifies every figure against the source; a mismatch fails the response.
In the demo: ask it something outside its scope, on purpose. Watch it refuse.
The full assurance architectureBuilt around your plant
The big vendors sell what they have. We adapt to how you work.
No two nuclear plants run the same way. We know it, and the product is built for it.
The large agentic suppliers
- — Sell a fixed product, as-is
- — You change your process to fit their tool
- — Your request goes on a roadmap
- — Changes arrive on a quarterly release cycle — if at all
Vantomic
- Our own codebase, deployed in your tenant
- We change the tool to fit your workflow
- A new RWP field, a report your NRC coordinator needs, a plant-specific rule
- Small changes often within 24 hours — days at most