Previous Topic

Book Contents

Book Index

Next Topic

Service Outage

Changes to IT infrastructure will inevitably cause performance downtimes. Expected downtime incurred by an infrastructure change is registered in the corresponding Change Details object.

This is captured in the corresponding Change Detail objects found in the 'Expected Changes' tab of the Change editor.

Help Image

Outages registered in changes linked to a particular service are considered Service Outages of that service, also referred to as expected service downtimes.

In the Service editor, a calendar of downtimes requested in connection with the service can be displayed in the 'Expected Changes' tab switched to the calendar mode.

Help Image

Calendar events are based on the Service Shop requests containing change details with downtime. Approved downtimes are rendered in different color than downtimes which are submitted but not approved yet.

Requesting a downtime

  1. Open the Service Request Shop and navigate to the IT-Changes area
  2. Select 'Emergency change'.
  3. After selecting the change, click the 'Change Details' button.

    Help Image

  4. In the Change Details editor, specify Downtime Start and End. Select the 'Services' check box in the middle part of the editor, then use the 'Search and Assign' action in the 'Services' tab to specify which service instances will be affected by the change.

    Help Image

  5. Add the change to cart and submit the request.

See Also

Related Information

User-Person-Supportgroup

Change Authorization

Risk Rating

Ticket and Calendar

Change Scheduling

Back-out Plan

Reporting

Process RFC Activities

Emergency Change

Integration With CMS

Problem - Change Association

Autoclose Functionality

Communication With the Stakeholders

Ticket Prioritization Guideline

Authorization Groups and Roles

RFC Links to Other Ticket Classes

Organizational Roles