Outage Pathology edit
Root cause analysis of downtime is the process of identifying what failed, why it failed, and who is responsible for the failure. A particular outage can be divided into segments of downtime duration which have either different impacts, different
External Attributable Downtime edit
Customer Attributable Downtime edit
Product Attributable Downtime edit
scheduled downtime edit
In a system scheduled downtime is planned downtime that is included in the design of the system. Usually, for an activity such as software upgrade, equipment growth, reconfiguration, and preventive maintenance (such as diagnostics). In particular a planned event for the purpose of corrective action is not scheduled downtime but instead should be attributed to the cause of the corrective action.[1] The following are examples of planned downtime that should not be counted as scheduled downtime:
- Deferred maintenance, e.g., a deferred hardware repair or a deferred restart to clean-up a garbled memory
- Diagnostics to isolate a detected fault
- Hardware fault repair
- Fixing an error or omission in a configuration database or omission in a recent configuration database change
- ^ TL9000 Measurements Handbook 4.0