Showing posts with label Outlook. Show all posts
Showing posts with label Outlook. Show all posts

Tuesday, November 17, 2026

Communicating an Alarm Could be a Challenge - Cause Serious Injuries

I guess you remember the problems Microsoft had last week with their cloud services ... Outlook, ...

A friend of mine stated the other day (in the context of attackin cooling systems): "There is no need to allow any kind of active remote control; allow only view mode."

That may help to some degree ... BUT check how even monitoring could cause severe problems ... and bring many people into a dangerous situation ... really:

"allow only viewing mode" could be implemented as "polling" or "pushing" ... in many cases a combination of both makes sense.

On October 13, 2026 (the day when Microsoft still had some problems with Outlook) the following happened in Germany (see excerpt of the report):
----------------
Phantasialand: Microsoft outage hid pool chlorine fault, 15 guests hurt Excess chlorine in a hotel pool at Brühl's Phantasialand injured 15 guests on Friday, 13 November. Warning emails from the pool's dosing system never arrived because of a Microsoft Outlook outage.
https://pollar.news/en/event/phantasialand-pool-15-guests-hurt
----------------

Just pushing a warning via email is dangerous because it could get lost ... in addition to the event-driven report (e.g., via Outlook), polling to view the status periodically or sending the status periodically by an unsolicited report would help to figure out a disconnect.

Anyway, I do not understand that there was obviously no red flashing light in (or near) the pool indicating a serious problem ... warning the guests ...

The reporting service in IEC 61850-7-2 supports sending a report when (1) an event occurred and (2) periodically. In addition, a client can poll actively at any time.

IEC 61850 has a set of very useful and efficient services for monitoring processes by sending unsolicited reports and storing events in a log.