Capability

Root-cause analysis & diagnostics

From symptom to root cause in minutes.

Correlate measurements, events, alarms and maintenance history to understand why something failed, then close the loop with a work order, without leaving the platform.

Book a demo Read the docs

Activity

Sanne de Vries changed status from Unack'ed to Ack'ed · 6 days ago

High

Substation 14 Flow loss · V-206 stuck closed

UNACK'ED Close

Root cause

Valve V-206 failed to open after this morning's maintenance

Valve unchanged despite 13:15 open command
Pump vibration rise is consequence, not cause
Similar pattern seen in March incident (ref. WO-2241)

Create work order

Data sources

SCADA · flow & vibration sensors
DCS · valve command log
CMMS · maintenance record 09:30

customers

Trusted by teams running critical operations

Enterprises across energy, heat, water and infrastructure rely on Blockbax to keep critical assets running.

"By automating tasks and improving productivity, we're prepared to support Eneco's asset growth strategy across our full portfolio."

Michel Klaasse Head of Asset Control & Steering

"Blockbax is key to operating our heat networks at the highest standard, with full control over asset performance across all sources."

Harold Maasen Manager of Realisation, Operations & Asset Management

"With Blockbax, our maintenance and operations teams have real-time insight into our full fleet of energy solutions."

Noël Steentjes Technical Director

Event correlation

See everything that
happened before the alarm

Root cause hides in the relationships between signals. Reconstruct the full sequence of events, measurements and maintenance actions on one timeline.

Substation 14

PRE-ALARM SEQUENCE

14:02 Alarm raised · flow deviation ALARM

13:58 Pump vibration exceeded band EVENT

13:41 Supply temp trending down METRIC

13:15 Valve V-206 commanded open · no state change EVENT

09:12 Maintenance completed on V-206 ULTIMO

CORRELATED Valve V-206 never reopened after this morning’s maintenance.

Historical analysis

Is this new, or has it happened before?

Recurring failures reveal themselves against history.

Overlay current behaviour on past periods and group events to expose the patterns behind repeat failures.

Compare against any period

Overlay this week on last week, or this month on the same month last year. Both curves stay on one axis, so the deviation is visible rather than remembered.

Same spike, second week

Recurring failures

Group events per asset and compare frequency over time, so a pattern shows up before it becomes a habit.

7X T-03 pitch fault Trend ↑
2X T-11 same fault Stable
1X T-07 same fault Stable

AI Agent

A diagnosis partner with
perfect recall

Everything your operation has ever seen, at hand.

AI explains anomalies with the data behind them, recalls how similar incidents were resolved, and suggests the next step.

Anomaly explanation with the measurements and events behind it
Similar-incident recall how comparable cases were resolved
Suggested next step when the cause isn't obvious yet

Explore the AI Agent

AI agent 47 alarms → 1 root

T-03 keeps tripping on pitch fault. What’s the cause?

7 trips in 7 days, all after wind gusts > 18 m/s. Identical signature to incident #2041 (Jan), resolved by recalibrating the pitch sensor.

Suggested actions