Alarm management
December 12, 2024
Now, you can follow up on events requiring attention directly from Blockbax. With our newly released alarm management functionality you can keep track and resolve alarms according to a structured, industry-standard workflow (following best practices from ISA-18.2 and IEC 62682).
We’ve built Alarms in Blockbax to be able to handle alarms from existing systems like SCADA and BMS, as well as alarms from Blockbax’s condition-based event triggers – providing a uniform approach to handling alarms. When alarms are scattered across different systems, it makes it difficult to improve operations. Because we aim to do just this – unlock the full potential of data-driven operations - we believe a uniform approach is key, allowing you to leverage our flexible rules to minimize false alarms and prevent alarm fatigue.
With Alarms you can:
- Move alarms through workflow stages (unacked, acked and closed)
- Temporarily put alarms on hold and get notified after specified time
- Easily get the right information and context about the related asset
- View which changes are made on the alarm by different users
- Filter and sort alarms by status, priority and asset
- Use quick actions to automatically resolve an alarm once inactive or suppress it
Alarm management is only available to users on our Advanced and Enterprise plan - contact us if you are interested in trying it out. For a full overview of the alarm management functionality visit the docs.
Improvements
- Add external ID of parent to the information available to an action
- Add option for existing account to switch to SAML for logging in
- Skip email verification for project invite initiated registration
- Allow password resets with no verified email
Fixes
- Fully allow a subject PUT based on the GET result
- Fix form submit on enter
- Fix project or role deletes failing when a role is used as default role in SSO settings
- Speed up page loads for roles, status and event statistics
- Fix bug when changing aggregation function in heatmap
- Fix last known location not visible when no measurements