The BEMS GuyBuilding automation & energy savings
for smarter buildings

Anonymised BMS case study

BMS alarm rationalisation example

A site can have hundreds of alarms that no longer help the operator. The review separates real plant risk from repeated nuisance, stale points, bad priorities and missing descriptions.

Request a similar reviewBack to case studies

Checks carried out

Evidence before recommendations.

  • Export alarm history and identify repeated, stale and high-frequency points.
  • Separate safety, comfort, energy and maintenance alarms into clearer groups.
  • Check whether alarm text, priority and routing match the actual site risk.
  • Agree changes with the site team before suppressing or changing anything.

Output

What the client should receive.

A practical alarm action list: keep, rename, reprioritise, investigate, trend, suppress only if agreed, or pass to the BMS maintainer for software change.

This style of case study is deliberately anonymised. The aim is to show the engineering process without naming sites, exposing live systems or making unsupported savings promises.