Univ. of Illinois Goes War-of-the-Worlds On Students
theodp writes "'Strange beings who landed in New Jersey tonight are the vanguard of an invading army from Mars.' (Orson Welles, 1938). 'Active shooter at BUILDING NAME/INTERSECTION. Escape area if safe to do so or shield/secure your location.' (Univ. of Illinois, 2011). An alert message sent out Thursday to 87,000 emails and cell phones warning recipients to escape from an 'active shooter' at the University of Illinois was an error, the Office of the Chief of Police confirmed. 'The alert sent today was caused by a person making a mistake,' explained an email. 'Rather than pushing the SAVE button to update the pre-scripted message, the person pushed the SUBMIT button. We are working with the provider of the Illini-Alert service to implement additional security features in the program to prevent this type of error.'"
To turn keys that initiate the Minute Man launch sequence...
"Flyin' in just a sweet place,
Never been known to fail..."
It meant to say "Reactive HOOTERS at State & Main."
It's part of a new network detection system for big, non-artificial breasts detected by a camera system. The roll out is initially for Los Angeles and Beverly Hills, the AI is being perfected by the NCSA guys.
But Schroyer said some students were shaken by the initial alert and criticized the university for taking about 12 minutes to send an email confirming it was false.
"That was unacceptable in my opinion," he said.
Really? 12 minutes is too slow? The thing sent out 87,000 e-mails (which takes a while no matter how big and distributed your mail system is), and the person who made the error probably didn't notice until either they got the e-mail or somebody who did told them.
I think 12 minute response time for something like this is pretty impressive.
Do you want to cancel the alarm?
[Cancel] [Cancel]
Bert
... if there was a real shooter, and it still said BUILDING NAME/INTERSECTION. Thanks for the heads up, morons!
How about prompting for a CONFIRMATION before spamming thousands of text messages/emails out?
Sounds like UI needs a better UI on their emergency notification system.
It sounds like they have no way to test the message other than it sending it out to every address in the alert list.
Let's say in this case after updating the message templates, the person hit 'save' rather than 'submit'. On the bright side, then no message would have been sent. On the not-so-bright side, no message would have been sent!
Don't you want to know before there's an actual emergency that your emergency message is working? Not that this incident was an intentional test, but shouldn't they have a test after updating the message template?
The really scary part is that we live in a society where the police have to pre-prepare texts and emails to warn students that someone is shooting up their school.
Linux O Muerte!
at least all these students know that there's a system in place, and that it works!
I just hope it doesn't turn into an inordinate amount of "Are you SURE?" prompts.
"Are you sure you want to send this alert?" YES / NO
"Are you SURE? You're saying there's a shooter on the loose.." YES / NO
"OK, so you're certain.. *BLAM*
I kid...I'm sure they'll implement a better system then that.. but really.. is it broken? How long have they had this system? How many false alarms have there been before?
I was passing BUILDING NAME/INTERSECTION just when I got the text and really panicked.
All the poor souls who are looking down and reading a text while the shooter stalks... How about a "heads up" policy being instituted at the school? Or a directional gunfire analysis certificate mandatory for all students? Or a "Typing Under Pressure" exam followed by a "How to Use the Illi-Alert System" for all shooting alert writers?
Poor GUI bite another person in the ass.
The Kruger Dunning explains most post on
Ultimately this seems like a very over-elaborate system anyway. Why do they need to have a bunch of prepared single line warnings anyway. In the time it takes to select one of probably several warnings from the system, a user could have typed the message in themselves.
The whole thing could probably be handled with an updated email distribution list and _maybe_ a shortcut on the desktop to quickly start a new message to said list.
"We are working with the provider of the Illini-Alert service to implement additional security features in the program to prevent this type of error."
After implementing the "additional security" we will hear how they were unable to send an alert for an actual event because the Chief of Police was dealing with the problem and couldn't come in to put his code in.
And this is why "[SAVE MESSAGE TEMPLATE FOR LATER USE] [SEND MESSAGE IMMEDIATELY]"
is better than "[OK] [CANCEL] [ABORT] [ERROR] [RETRY]"
- For the complete works of Shakespeare: cat
I am picturing a glowing screen with a a blinking popup dialog box reading "Are you SURE you want to send this message? [OK] [CANCEL]" with blood dripping down the screen.
- For the complete works of Shakespeare: cat
>a user could have typed the message in themselves
They set up a template so that, in the stress of the moment, the person sending the message wouldn't forget to include some important detail (e.g., location of the emergency, what to do, etc.)
The solution is a lot more simple then everyone is making it. "Update" should be a button you click with a mouse. Actually sending the message shouldn't be a button, rather it should be a multi-key sequence/shortcut that either sends the message or better yet, produces the actual send button. The shortcut can be listed on the dialog box where it currently exists, and a properly composed paragraph can encourage reading of the short warning about sending, since the operator is reading for the shortcut already. The lack of being presented right away with a simple button *should* (there are ALWAYS exceptions to the rule) prevent accidental occurrences like this one. The extra work involved should break the pattern/trance we tend to fall into when doing repetitive tasks.
I suspect this meant more for a student who has a class in BUILDING NAME/INTERSECTION 10 minutes from now. I would hope that you wouldn't have to tell people to hit the deck when they hear gunfire.
In regards to the question of whether we're in more danger than we were in years past, I would agree that we are not, but point out that if UT had had such a system in 1966, it might have saved some people then, too.
Clippy:
It must have been something you assimilated. . . .
The real question is what happened after the everyone starting hitting Reply to All?
I'm an alumni of the U of I, and I work here as well. I get these notifications. I thought I'd bring up 2 points:
Overall, I'm satisfied with the system and I was impressed by the very explicit letter from the chief both explaining the error and accepting the blame for the mistake. She also detailed the upcoming efforts to address the error. I'd like to see the same level of accountability from my ISP or phone company.
The Internet has no garbage collection
No, the real version will say "shooter at BUILDING NAME/INTERSECTION, looking for INSERT NAME HERE".
Give a man a fish and you have fed him for today. Teach a man to fish, and he'll say "WHERE'S MY FISH, YOU IDIOT?"
This has nothing to do with War-of-the-Worlds, except that there was false panic. The Orson Welles broadcast was done as a fictional story, this incident was an accidental broadcast of an alert.
Next up, a headline saying "Oncologist Pretends to be Orson Welles with Wrong Diagnosis!"
"Active shooter" is police jargon for a Columbine-type situation.
The opposite isn't "passive shooter", but the term signifies (at least in some jurisdictions) a situation in which immediate action needs to be taken, rather than, say, waiting to call out the SWAT team.
Give a man a fish and you have fed him for today. Teach a man to fish, and he'll say "WHERE'S MY FISH, YOU IDIOT?"
I work at a university too, and you're right about all ten!
Never let a lack of data get in the way of a good rant.
That or have your templates entered through an entirely different executable/interface. Heck, don't even let the templates be edited on the system that sends the real messages. While you may need to send a real message quickly, you will never need to save a template in the heat of the moment, and if you are editing the templates frequently enough that walking over to a completely separate machine is going to have any real effect on productivity, then your problem isn't with the computer.
Wrong. Submit is a perfectly find button name. It is simple, it is direct, and it is understood by the population. It is not always appropriate, but the label of "Submit" is not why this happened. It happened because of a mistake earlier in the workflow of the application. The screen that you use to make templates should never have been the same screen that is used for sending messages.
If Submit is an unacceptable label, then so is Save, File, Edit, Help, Save As, etc...
By having the same form used to generate templates as used for sending real messages, the developers had already made a mistake in their application's workflow.
Dramatically more lives could have been saved by banning football. My point being that you are talking about an number that is statistically irrelavent. Besides, you are just as likely to simply move the venue as you are to actually stop it.
The message we got actually said "BUILDING / INTERSECTION NAME" as the location of the alleged incident. To anyone with half a brain it was more than obvious that it was sent in error. I just waited and waited for the explanation. I never actually expected a corrected version with an actual location.
The bigger issue is the use of this system at all. It has been used twice so far (not including yesterdays bout of criminal stupidity). The first was for an "impending tornado" that never touched down. We already have a warning system for that. There are big loud sirens that everyone should be listening for when a nasty storm is rolling through and a watch/warning has already been issued by a non-university organization. The second was just earlier this week for a fire in a non-campus building to warn university employees based in nearby buildings. Who were already evacuated.
The university has now cried wolf three times. Time to file the alerts directly to spam.
...it was an INSIDE job?
Word has it, there is this professor at UI who drinks only rain water and whiskey. He thinks fluoridation is a part of a mind control conspiracy. Could it be that he triggered the alarm?
This is how to design the perfect interface:
Offices should have sensors that detect gun shots and trigger an email alert.
This would be double plus good:
What makes people angry are false reports. Not with this system.
We are working with the provider of the Illini-Alert service to implement additional security features in the program to prevent this type of error.
most likely means: The same contractors who messed up basic usability in the original implementation will now get paid again to "fix" it. BTW what is with people using wrong words? Additional "security" features, my ass, this is HMI 101, nothing to do with security.
A successful API design takes a mixture of software design and pedagogy.
Silencers aren't really that 'silent'. It's not like in the movies, you still hear a gunshot if you're anywhere near, just not as loud.
"Think about how stupid the average person is. Now, realise that half of them are dumber than that." - George Carlin
Good point. And thank you for improving the system...
Say there's a really bad chemical spill in an area where students typically walk through... are you implying that the administrators should shoot the spill to trigger the alarm?
Of course not. To warn the campus of chemical spills, administrators should have a bottle of muratic acid on the shelf. If they want to trigger the chemical alert system, just spill it on the office floor, and this activates the chemical alert warning.
Absolutly no way of confusing the trigger events, and as I said: never ever a false warning.