• Wildmimic@anarchist.nexus
    link
    fedilink
    English
    arrow-up
    58
    ·
    5 hours ago

    The technical standards for Email would allow for 3 days of delivery failure before finally giving up. That’s the amount of leeway email has (in theory - practically we assume that everything longer than 3 minutes means something has gone wrong). Sending alerts by email is fine for non-critical applications; if one of my docker containers crash, an email is fine because the amount of damage is nil.

    Why wasn’t there an actual fail-safe mechanism employed that measures the chlorine levels and shuts the whole thing down BEFORE it gets dangerous?

    This is not a Microsoft problem. This is a negligence problem on Phantasialands side, using inappropiate tools for a system that can hurt people on failure, and should be followed up by lawsuits.

  • absGeekNZ@lemmy.nz
    link
    fedilink
    English
    arrow-up
    14
    ·
    5 hours ago

    Industrial automaton engineer here, I’ve worked on a bunch of safety critical systems and audited systems after incidents.

    Best practice in situations were you are sending a remote start command, is for the stop command to be local to the pump controller.

    I audited a system where the main control system sheet a start command to the dosing shed (which stored the concentrated chemicals), unfortunately the stop command was over the same link that got interrupted. The start was received but the stop was never was. Radio is not a reliable link.

    For chemical dosing, I’d expect at least two types of command signals, such as concentration and Max allowed time; you could also measure the weight loss of the concentrate as a third check. Loss of communications to the main controller isn’t necessity an instant stop, but I would expect a prolonged loss to trigger a stop. As long as the local controller has stop control, dosing can usually continue.

      • Jason2357@lemmy.ca
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 hour ago

        We used to have these things called blinking lights and alarm sirens that required only a few cheap components and no internet at all.

          • Zron@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            60 minutes ago

            Imagine being so slop brained that you forget that physical alarms and local system alerts are a thing.

          • jj4211@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 hour ago

            A buzzer, a bell, a klaxon… Audio saying “caution: chlorine levels too high”

          • potustheplant@feddit.nl
            link
            fedilink
            English
            arrow-up
            20
            ·
            5 hours ago

            Notifications on the automation portal, a push notification if you have an app, an sms message, an email, a physical alarm or all of the above. Hell, you could even have a physical alarm at the actual pool to alert customers in case someone from maintenance missed the alarm. I don’t know how this is an actual question for you xd

        • 800XL@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          arrow-down
          4
          ·
          6 hours ago

          MS wants businesses to sign up for their cloud services, promises the world, and says don’t worry. Businesses rely on this nd when it goes down it’s not MS’s fault even tho MS is the service that went down? Come on.

          • Axolotl.cpp@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            2
            ·
            2 hours ago

            It’s not MS fault if you don’t also have a fallback system or any system that can work even offline/dipendently on your network. Regardless of microsoft being down or not, emails for such stuff is a VERY bad idea and should be changed with a better system that cannot be accidentally ignored.

          • Miaou@jlai.lu
            link
            fedilink
            English
            arrow-up
            2
            ·
            5 hours ago

            Gross negligence is a thing. What’s the point of moving away from MS if they can just point the finger at them and yell “daddy told me I could?”.

  • Beej Jorgensen@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    370
    arrow-down
    1
    ·
    18 hours ago

    No mails arrived due to the disruption […]. So no one noticed that the maintenance safety system of the sauna landscape has long since sounded the alarm by mail. Because the automatic dosing system had pumped too much chlorine into the pool.

    Kinda scary to rely solely on email for such alarms.

    • Remember_the_tooth@lemmy.world
      link
      fedilink
      English
      arrow-up
      198
      arrow-down
      9
      ·
      17 hours ago

      Yeah, I hate Microsoft as much as the next person, but this is 100% on Phantasialand for trying to cut corners with excessive automation.

      • Schemen110676@lemmy.ml
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        1
        ·
        6 hours ago

        No… with the wrong kind of automation.

        Safety relevant systems do not belong on public infrastructure

      • Miaou@jlai.lu
        link
        fedilink
        English
        arrow-up
        4
        ·
        5 hours ago

        “Excessive”?! You mean lack thereof? Do you understand emails are not automation?!

      • 2ndDegreeOWO@lemmy.world
        link
        fedilink
        English
        arrow-up
        91
        arrow-down
        1
        ·
        15 hours ago

        It’s not excessive automation – it’s a lack of redundancy for critical safety features.

        Anything safety-critical should never have a single point of failure if you can help it. And there was definitely an opportunity here to have some kind of secondary backup alarm system.

      • tal@lemmy.today
        link
        fedilink
        English
        arrow-up
        97
        ·
        edit-2
        17 hours ago

        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.

        Automation can increase safety by decreasing time until an issue is addressed, for example. Automation isn’t intrinsically incompatible with safety. Aircraft computers today use TCAS to automatically instruct pilots what to do if they are about to collide (and in fact, today the automated system is explicitly given higher priority than human air traffic controllers — if the two give pilots conflicting directives, the human is the one to be disregarded). But you gotta make your automated procedures have high reliability and handle failure the way you want when the consequences of a failure are high (and that goes for non-automated procedures too).

      • assaultpotato@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        55
        ·
        17 hours ago

        Excessive automation? That actually seems like a great thing to have automated… just not by email. Nothing stopping them from having a sub ghz radio that sets off a physical alarm somewhere. Improper automation I think would be more apt. A purely local automated alarm sounds great, but the internet shouldn’t be involved imo, at least not on the critical path to remediation.

        • db2@lemmy.world
          link
          fedilink
          English
          arrow-up
          9
          ·
          9 hours ago

          just not by email

          I disagree, email definitely had a place. Documenting the fault and time it happened.

          The way they did it was stupid.

      • helpImTrappedOnline@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        ·
        16 hours ago

        I wonder if they could have done something like [puts on big brain hat] have an actaul fucking alarm the pool staff and guests can hear.

    • Reannlegge@lemmy.ca
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      17 hours ago

      I for one think that IT team should be kicked to the curb, but they will probably get raises to figure out that they can use email, healthchecks.io, and ntfy all at the same time for redundancy or they will say we need money to switch providers and set up a gmail account to do the same thing and call that redundant cause you know getting two emails saying the same thing is not going to end up just being ignored.

      • shalafi@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        15 hours ago

        I used to have IT monitors that would email but also text me. Most folks don’t know they can send an email to (phone_number)@(provider).com and that shows up as a text.

        • halcyoncmdr@piefed.social
          link
          fedilink
          English
          arrow-up
          8
          ·
          12 hours ago

          Most of those email to sms portals no longer work, at least on the US carriers. Unless you are on a corporate account and your company pays for that additional service.

    • Norsca@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      16 hours ago

      That’s actually terrifying a lot of people don’t even care on checking their mails on a daily basis

  • magnue@lemmy.world
    link
    fedilink
    English
    arrow-up
    145
    arrow-down
    1
    ·
    17 hours ago

    Can’t put any blame on MS here. Using email for safety warnings with no redundancy is negligent.

    • rbb36@lemmy.world
      link
      fedilink
      English
      arrow-up
      31
      arrow-down
      2
      ·
      15 hours ago

      One can put some blame on them, legally speaking.

      • First, MS was outside their SLA. That’s right in their service agreement.
      • Second, they were so far outside their SLA that it gets into reasonable expectation.
      • Third, there will be litigants who assert negligence.

      Which of those claims will stick remains to be seen, but “no blame” is incorrect.

      • FenrirIII@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 hour ago

        Your answer is 100% incorrect. The hotel is solely responsible for the incident as it is their responsibility (liability) for maintaining the system. The hotel failed to properly maintain the system and provide adequate monitoring of said system. If the alerts were delivered by traditional mail and the letter was late, you wouldn’t blame (i.e. sue) the post office.

        If the hotel wants to sue Microsoft, they can try. They will get the damages from the missed SLAs, everything else will be laughed out of court.

        Your post reads like anti-Microsoft hate rather than actual legal argument. As much as MS sucks, there’s no jurisdiction here much less a burden of care or duty on MS’s behalf.

  • thatkomputerkat@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    16 hours ago

    Wow. Why wire up a blinking lite and speaker in the managers office to the system when you can just rely on fucking email. Pretty sure whoever made it possible to use email intended it to be a backup solution in case no one in charge was on site when the alarm went off.

  • ravenaspiring@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    17
    ·
    16 hours ago

    We were all exposed to this problem: on Friday there was an outage that crippled the US software company Microsoft, including the email program Outlook.

    Phantasialand was affected as well. Because of the disruption, no emails arrived, the company told WDR on Saturday. So nobody noticed that the maintenance safety system for the sauna area had long since raised the alarm by email. The automatic dosing system had pumped too much chlorine into the pool.

    • boonhet@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 hours ago

      we we all exposed to this problem

      Does seeing memes count? Otherwise, not really. I wouldn’t even have known it was down.