Availability Management

From IT Process Wiki

DE - ES - Availability Managementdiese Seite auf Deutschesta página en español
DE - ES - Availability Management


Objective: ITIL Availability Management aims to define, analyze, plan, measure and improve all aspects of the availability of IT services. It is is responsible for ensuring that all IT infrastructure, processes, tools, roles etc are appropriate for the agreed availability targets.

Part of: Service Design

Process Owner: Availability Manager

 

Process Description

Availability Management ITIL
ITIL Availability Management

There are no major differences between Availability Management in ITIL V3 (2007) and ITIL 2011.

Following the introduction of Design Coordination in ITIL 2011 the information flows have been adapted. The process overview of ITIL Availability Management (.JPG) shows the key information flows (see fig. 1).

ITIL 4 refers to 'Availability Management' as a service management practice.

 

Sub-Processes

These are the ITIL Availability Management sub-processes and their process objectives:

Design Services for Availability

  • Process Objective: To design the procedures and technical features required to fulfill the agreed availability levels.

Availability Testing

  • Process Objective: To make sure that all availability, resilience and recovery mechanisms are subject to regular testing.

Availability Monitoring and Reporting

  • Process Objective: To provide other Service Management processes and IT Management with information related to service and component availability. This includes comparing achieved vs. agreed availability and the identification of areas where availability must be improved.

Definitions

The following ITIL terms and acronyms (information objects) are used in the ITIL Availability Management process to represent process outputs and inputs:

Availability Design Guidelines

  • The Availability Design Guidelines define from a technical point of view how the required availability levels can be achieved, including specific instructions for application development and for externally sourced infrastructure components.

Availability Guidelines for the Service Desk

  • Rules produced by Availability Management on how to manage Incidents causing unavailability, to prevent minor Incidents from becoming major Incidents.

Availability Management Information System

  • A virtual repository of all Availability Management data, usually stored in multiple physical locations.

Availability Plan

  • The Availability Plan contains detailed information about initiatives aimed at improving service and/ or component availability.

Availability/ ITSCM/ Security Testing Schedule

Availability Report

  • The Availability Report provides other Service Management processes and IT Management with information related to service and infrastructure component availability.

Event Filtering and Correlation Rules

  • Rules and criteria used to determine if an Event is significant and to decide upon an appropriate response. Event Filtering and Correlation Rules are typically used by Event Monitoring systems. Some of those rules are defined during the Service Design stage, for example to ensure that Events are triggered when the required service availability is endangered.
  • Note: The output "Event Filtering and Correlation Rules" has been added in ITIL 2011, to emphasize that (some) Event filtering and correlation rules should be designed by Availability Management to support the detection of availability issues.

Maintenance Plan/ SOP

  • Maintenance Plans are part of the operational documentation for applications and infrastructure components, which are sometimes known as Standard Operating Procedures (SOP). They define the frequency and scope of preventative maintenance. Maintenance Plans/ SOPs are typically extracted from technical or administration manuals to define in a concise manner the tasks to be carried out as part of standard operations.

Recovery Plan

  • Recovery Plans are created mainly by Availability Management and IT Service Continuity Management. The plans contain specific instructions for returning specific services and/or systems to a working state, which often includes recovering data to a known consistent state.

Technical/ Administration Manual

  • A document describing the procedures required to run and maintain a type of application or infrastructure component.

Test Report

  • A Test Report provides a summary of testing and assessment activities. A Test Report is created for example during Release tests in the Service Transition stage or during tests carried out by Availability, IT Service Continuity or Information Security Management.

Templates | KPIs

Roles | Responsibilities

Availability Manager - Process Owner

  • The Availability Manager is responsible for defining, analyzing, planning, measuring and improving all aspects of the availability of IT services. He is responsible for ensuring that all IT infrastructure, processes, tools, roles etc. are appropriate for the agreed service level targets for availability.

 

Responsibility Matrix: ITIL Availability Management
ITIL Role / Sub-Process Availability Manager Service Owner[3] Applications Analys[3] Technical Analyst[3] IT Operator[3]
Design Services for Availability A[1]R[2] R R R -
Availability Testing AR - - - R
Availability Monitoring and Reporting AR - - - -

Remarks

[1] A: Accountable Accountable according to the RACI Model: Those who are ultimately accountable for the correct and thorough completion of the Availability Management process.

[2] R: Responsible according to the RACI Model: Those who do the work to achieve a task within ITIL Availability Management.

[3] see → Role descriptions ...

Notes

By:  Stefan Kempter , IT Process Maps.

 

Process Description  › Sub-Processes  › Definitions  › Roles