Central alarm management

Every alarm, prioritized, resolved.

Alarms from every critical asset, unified in one queue, prioritized by what actually matters right now, and automated through to a closed work order.

Book a demo Read the docs
Battery storage/Alarms
Filter alarms…
Open 20 On hold 2 Closed 11 All 33
Filter by creation date…

47 alarms in 90 seconds clustered to one probable root: breaker trip at Substation 14.
The other 46 are downstream.

Alarms

SCADA · BMS · Blockbax triggers, one workflow

3 selected
Prio Alarm Status Created
  • Critical Substation 14 · breaker trip Unacked 2m ago
  • Critical Riverside Hub · ATO exceedance imminent Acked 6m ago
  • High Delta Cold Store · compressor 3 vibration high Unacked 14m ago
  • High Charging bay 4 · charger offline On hold 22m ago
  • Medium PV string 7 · below expected yield Acked 38m ago
  • Low Harbour pump B · filter pressure (maintenance) Suppressed 1h ago

ALM-4821

Substation 14 · breaker trip

Critical
Unacked Acked On hold Closed

Linked resources

Ultimo job #48231 · In progress
ServiceNow INC-88214 · Assigned

Automated action

Work order created and technician notified. Auto-closes when the condition clears.

Activity log

  • 14:02 Alarm created from SCADA event
  • 14:03 Acknowledged by e.jansen
  • 14:05 Action → Ultimo job #48231 created
  • 14:06 Priority raised to Critical · site impact
  • 14:20 Auto-close check scheduled
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
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
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
Noël Steentjes Technical Director
Firan Eteck Heijmans Elix Nett Eneco Bredenoord TBI Van der Ende Group Gemeente Rotterdam Volta Energy Aquon Gigastorage Inwarmte Electroproject Caeli Additive Restrain

A structured workflow that ends in resolution

What deserves attention right now, given everything else happening.

One uniform lifecycle across every alarm source, with the prioritization and noise control a busy operation needs.

One queue, whatever raised it

Alarms from SCADA, BMS and Blockbax triggers land in the same queue and follow the same process. Scattered alarm inboxes make improvement impossible.

  • Critical Substation 14 · breaker trip SCADA
  • High Riverside Hub · ATO exceedance Blockbax
  • Medium Cold store · compressor vibration BMS
  • Suppressed Harbour pump B · maintenance Rule
Defined lifecycle

Unacknowledged through to closed, with on-hold timers and auto-unacknowledge up to a year. Built on ISA-18.2 and IEC 62682, the industry standards for alarm management.

Unacked 4
Acked 17
On hold 3
Closed 128
  • 14:02 Raised · flow deviation Unacked
  • 14:06 M. Visser acknowledged Acked
  • 16:48 Valve replaced · cleared Closed

Every stage change is timestamped and attributed, so the handling history is defensible.

Bulk handling

After an outage, act on fifty alarms at once instead of one by one. Filter by status, priority, asset or ID first.

12 selected
  • Substation 14 · breaker trip AL-4821
  • Cold store · compressor vibration AL-4822
  • Harbour pump B · flow deviation AL-4826

+ 9 more

Noise control

Suppress expected alarms during planned work, scoped by asset, trigger and period, so alarm fatigue never sets in.

06:00 18:00
Maintenance window

No alarms, no notifications, no webhooks during planned work.

Every findings stays on the alarm

Who did what, and why, in one place instead of scattered over chat and email

Comments sit in the alarm's activity next to every status change, so whoever picks it up next, or handles the next similar alarm, starts with the full story.

Comments in the activity timeline

Report findings and share progress right on the alarm. Comments appear between the status changes, so the timeline shows what happened, who did what and why.

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

    Checked the dashboard: temperature has been rising steadily since 06:00. The compressor power consumption dropped at the same time, so it looks like the compressor stopped.

  • Mark Jansen changed status from Ack'ed to On hold · 3 days ago
  • Mark Jansen changed status from On hold to Closed · 7 minutes ago
  • MJ
    Mark Jansen 7 minutes ago

    Breaker reset after planned maintenance, all downstream readings restored.

Explain every status change

Add a reason when you close an alarm or put it on hold, also when you change many alarms at once.

  • 33 High Transformer 2 Oil temperature Unack'ed
  • 31 Medium Battery System Oulu State of health Ack'ed
  • 30 High Transformer 6 Transformer alarm Unack'ed
  • 28 Low Battery System Helsinki Cell voltage Unack'ed

Close 12 alarms

Resolution (optional)
Breaker reset after planned maintenance, all downstream readings restored.

Messaging & on-call Roadmap

Tell the people the moment an alarm changes or a finding is shared, not at the next shift handover.

Microsoft Teams
Microsoft Teams

Post alarm updates and comments to the Teams channel your operators already watch, with priority, asset and status in the message.

Slack
Slack

Share comments and status changes in the right Slack channel, so stakeholders stay informed without logging in to another tool.

PagerDuty
Pagerduty

Page the on-call engineer when a critical alarm comes in, so it reaches someone who can act out of hours instead of waiting until morning.

Resolution happens in other systems, so connect it

An alarm without a work order is just a notification.

Link tickets and jobs to alarms, and automate their creation with parameters resolved from your asset model.

Linked to your systems

Ultimo, SAP and ServiceNow records attached to the alarm, with job status rendered live inside Blockbax.

  • Ultimo job #48231 In progress
  • ServiceNow INC-88214 Assigned
  • TOPdesk · Pump flow checks Attached

Job status polls back, so the alarm always shows the current state of the work.

Actions and webhooks

GET, POST, PUT and PATCH calls fired on an event, with parameters taken straight from the asset model.

POST /api/now/table/incident

{ "asset": <asset.name>,

  "priority": <alarm.severity> }

// fired on event, audit-logged

On alarm raised On acknowledge On close
Complete activity log

Who did what and when, on every alarm. The record a 24/7 operation needs when someone asks afterwards.

  • 14:02 Created from SCADA event
  • 14:03 Acknowledged by e.jansen
  • 14:05 Ultimo job #48231 created
  • 14:20 Auto-close check scheduled
Ultimo
ServiceNow
TOPdesk
Microsoft Dynamics 365

When fifty alarms fire at once, where do you start?

AI triage answers that question in seconds.

Cluster alarm floods, surface the probable root alarm, and get the follow-up drafted for you.

  • Alarm-flood clustering collapse cascades to the probable root
  • Suggested prioritization from historical patterns
  • Drafted handovers shift and stakeholder updates, ready to send
Explore the AI Agent
AI agent 47 alarms → 1 root
Alarm flood 47 alarms in 90 seconds · Substation 14

Heads up, 47 alarms just fired at Substation 14 in 90 seconds. I clustered them into one probable root. A breaker trip at 14:02 cascaded to 46 downstream sensors, so those are follow-on noise, not separate faults.

Suggested actions

Stop firefighting the
same failure twice

Trace the cause, learn from history, and turn the diagnosis
into a fix in one place.

Book a demo Contact us