Severity One is a code blue for network managers. If you don’t know what a code blue is, here is the Wikipedia definition - "Code Blue" is generally used to indicate a patient requiring resuscitation or otherwise in need of immediate medical attention. To be blunt, code blue means someone is dying. Fast.
So when I compare severity one to a code blue, you now get the picture? Great! We’re all on the same page. Steve Mahoney, one of the first four SevOne employees responded with this when I asked him about the significance of a “severity one.” His wording was a little off, but you understand what he's trying to say. Mahoney didn't know this conversation was going to be screenshotted for the blog.
You might have deduced that the name SevOne came from the phrase severity one. I’m confirming that statement. SevOne IT performance management - preventing severity one outages since 2005.
And then, a link to this report happened to fall in my inbox a couple of days ago– Median Number of Hours to resolve Severity One Outages which Occurred within the Month. The last paragraph of the dictionary definition is this, “OIM tracks the number of Severity One outages that are received during the month and the median number of hours it took for OIM to resolve the issue. OIM strives to reduce the number of hours it takes to resolve Severity One outages and return services to our customers.”
But when looking at the graph, you see that in July there were 86 severity one outages. 86! And the median time to fix it was 2.1 hours, being that it's the median it could be significantly more or significantly less than 2.1 hours. Let's for instance assume that all 86 outages took one hour to fix. Do you know how many days that is? 2.77, which would mean for about 8% of the month of July the network was in a severity one state. And by Mahoney’s definition (which means it’s the rest of the world’s definition too) if not reacted to ‘quickly,’ severity ones could cost an organization significant resources and money. But we’re not judging the government. Not one bit. All we’re asking is why the network has to get to the point of a severity one in the first place? Because, let’s be serious – we all know, with network baselining and alerting, severity ones can be avoided. IT performance management and reporting, prevents severity ones. Troubleshooting problems in seconds instead of hours prevents hours and sometimes days of outages.
Editors Note - A number of governmental agencies are now meeting their growing IT challenges and exceeding their required service levels by optimizing their networks through SevOne's performance management solution. Learn more on our website.