Outages

An outage is a temporary loss of service of a Configuration Item. It can be the result of planned maintenance or operational failure.

Outage classes

Outages fall into different classifications:

  • Planned (and approved) outages
  • Degraded service
    • Partial loss of service
    • Slow response time
    • Intermittent interruptions
  • Total loss of service

Availability criteria should specify what the maximum outage threshold is on a monthly basis. For example, you can choose a metric based on the required percentage of up time, or the maximum time allowed for an outage, when you define an availability Service Level Target.

Planned outages

A planned outage is usually the result of a routine maintenance schedule, upgrade action, or faulty equipment replacement. Incidents, change requests, and change tasks can generate outage records. The change request and task records show scheduled downtime. Incident, change request, and change task records have a checkbox to specify if the Configuration Item is out of service.

Note Some planned outages may fall within pre-defined service windows when the outage does not count against availability metrics.

Calculating outage costs

When an outage occurs and the associated CI has an SLT, the outage costs to the business are calculated and stored in the outagedetail records. You can configure the default Outage Cost per Hour in the Configuration Management Environment record. The default Outage Cost per Hour is only applied if you do not specify Outage Cost per Hour in the CI form.

Related topics

Service Level Management
Working with service agreements
Operational Level Agreements
Service Level Agreement components
Service agreement selection process
Automatic outage posting
Outage spreading
Outage posting in other applications
Service Level Agreement performance and reporting

Related topics

Enable automatic outage posting
Disable automatic outage posting
Enable outage spreading
Disable outage spreading
Change outage start and end times