1. "Planned" Unplanned Downtime
Might be easier to remember this if it was called a scheduled unplanned outage. In these scenarios, there is a system degradation type incident occurring. Essentially, the service is so slow it is having a negative effect on production. Or, there is a bug in an application which has been detected and an emergency change needs to be deployed immediately to fix it. In either scenarios, multiple tickets get logged with the Service Desk. A resolution plan is determined by IT which requires a planned unplanned outage to occur.
Downtime is another way of saying a system is not available to the users. It is also referred to as an outage.
The greatest invention in the last 200 years isn't a product, but rather the scientific method, the process which has been used to create millions of products. Today, when change is exponential, a focus on process over products is even more important.
Signs & Symptoms
Downtime is the number one cause of financial harm yet most IT leaders don't understand the signs and symptoms of an environment that experiences too much unplanned downtime.
Sure it's easy to surmise that the systems are offline more than they should be especially when management is enraged but there are legitimate signs and symptoms which will allow you to reduce the frequency and impact of unplanned outages.
Calculate Your Downtime Today!
3. Implement Measurements & Indicators