cross-posted from: https://feddit.online/c/[email protected]/p/2115831/microsoft-365-outage-leads-to-chlorine-gas-poisoning-of-15-hotel-guests
cross-posted from: https://feddit.online/c/[email protected]/p/2115831/microsoft-365-outage-leads-to-chlorine-gas-poisoning-of-15-hotel-guests
I think that automation is fine, but when you start talking about life-critical systems, the bar on failure modes and reliability becomes a lot higher. Like, if you have a sensor for excessive chlorine levels, the default probably should be not to keep pumping more of the chemical in, but to have some “hard” upper level where no more chlorine goes in (and if the two systems aren’t directly-integrated, to at least let the maintenance safety system power off the chlorine system), and for a secondary alarm to be triggered (like, start playing a loud audible alarm) if maintenance doesn’t respond to the email notification and indicate that they’ve dismissed the alert within a given amount of time. That’s disruptive and undesirable compared to just emailing maintenance, but as long as there aren’t any failures, you shouldn’t ever see it. But if you do have it come up, you don’t want the failure mode to be chemical-keep-being-dumped-into-the-system-and-people-being-unaware-of-it.
You want fail-safe behavior.
It’s like those supermarket fridges.
When these things go off a literal alarm needs to be screaming that there’s an issue.
Yes, you can set up additional email alerts and logging. But the primary mechanism needs to be an in your face loud uncomfortable alarm, and safety cutoffs like you said.