The engine behind the service
OperTiva Intelligence
Not a product you log into. This is how InnoTech delivers the service securely, consistently and at a cost that works across your plants — and it is where thirty years of engineering judgement now lives.
A tool tells you something changed. The service knows what it means, what it threatens and what to do about it — because it has seen it before.
The five pillars
What makes the service deliverable.
Each one exists because an operator told us, in an interview, why the last thing they were sold did not work.
Three agents work every signal in sequence, none deciding alone: a Risk Chassis scores against production consequence across five dimensions (ISO 31000 / IEC 61511); a Solution Agent proposes break-fix, managed change, or defer-and-monitor with cost and effort; a Residual Risk Agent predicts what remains and re-scores once the work is done.
We do not touch your control systems. Nothing is installed on your OT network. Integration happens at the process level — offline data ingestion, one reconciled OT Asset Ledger, forwarded infrastructure alerts, EoL/EoS analysis.
Your data is anonymised and segregated. Patterns learned across the fleet never carry one operator's specifics into another's analysis.
No pre-cleaning, no data project, no set-up cost. Setpoint and Continuum scope against your reconciled plant model — source packs, asset inventory and mapping — as it already exists.
Completed work and schedules flow back to the maintenance system you already run. We add a governed loop; we do not replace your CMMS.
A five-year capital and maintenance budget
Budget-constrained, not wish-listed.
The same live workbook, seen as a plan: a ten-year OPEX and CAPEX model built from your lifecycle catalogue and current risk evidence, with the residual exposure that remains. Every formula live — argue with it.
How the service runs
The machine prepares. A person decides.
Every signal is scored, every option is costed and every residual is predicted before it reaches a human — so the engineer spends judgement where it counts, not on triage.