Technology · Sustainability · smart FM operations · live
One week. 1,157 alarms. A handful deserved a human.
Every BMS operator knows the wall of amber: alarms configured with good intentions, chattering sensors nobody re-tuned, and cascade storms where one chiller trip detonates forty downstream complaints. So operators learn to ignore the wall, and then one night the ignored wall contains a fire pump that failed to start. The referee runs three deterministic passes over the raw log: collapse the chatter, walk the equipment graph to name each storm's root cause, and surface the quiet criticals the flood was hiding. Synthetic estate and log; the behaviour is planted, the findings are computed. Runs entirely in your browser.
Synthetic BMS log · dependency graph shown · every suppression accountable
A storm is not many problems; it is one problem with many voices. For each flood period the referee finds the alarmed equipment whose downstream children explain the most other alarms, names it the root-cause candidate, and files everything downstream as consequence. The operator gets one incident, with the tree attached; the suppressed alarms stay on the record, grouped, never deleted.
Rationalisation is not software alone; it is a maintenance programme wearing software. The ten worst points below produced most of the week, and each gets a concrete fix: a deadband, a delay-on timer, or a work order for the sensor that cried wolf six hundred times.
Runs fully in your browser. Synthetic log from a seeded generator; chattering, storms and root causes re-derived on every load; nothing labelled in the data. · willytai.com