I just spent some time thinking about 1 to many notification.
I agree with what you wrote here:
> The solution is a better coordination of the many flares to
> a single flare that summarizes the entire domino-effect of failures.
But I found myself wondering if you had mis-stated the situation here:
> _Well, the problem isn't that we don't need flares, the problem is we
> have too many flares._
Literally true? I don't think so.
I think why this matters is that it's experienced as "too many flares".
I'd reformulate this way: everything is reported with the same priority (null) and routing (broadcast), so actually there aren't any flares at all!
FWIW at my DEWLine site I had 3 levels of audio alert. 1st was a loud bell ringing /dong … dong … dong/ … one strike every 2 or 3 seconds. Quite a while later (minute and a half?) a buzzer would sound. Still later the phone would ring. That was Cheyenne Mountain … a shift officer (All of them called themselves "Snoopy"; such a good nick cuz that's what they were doing: snooping huh huh) and that was not a good thing. He was checking to see if I'd dropped the ball.
But see I don't know for a fact that I have the scenario right at the level of operations.
Do different failure modes trigger signals that are qualitively different?
Addendum: There was no real response to this. There was a reply … which is better than stony silence, of course. But not anything like a response that would in some even small way acknowledge what I had written.
Google+: View post on Google+
Post imported by Google+Blog. Created By Daniel Treadwell.