Availability Management: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
<seo metakeywords="availability management, itil availability management, availability management itil, availability management process, availability itil v3" metadescription="Availability Management: ITIL process definition - | <seo metakeywords="availability management, itil availability management, availability management itil, availability management process, availability itil v3" metadescription="Availability Management: ITIL process definition - Sub-processes - Terms - Additional information on ITIL Availability Management." /> | ||
<imagemap> | <imagemap> | ||
Image:ITIL-Wiki-de-es.jpg|DE - ES - Availability Management|100px | Image:ITIL-Wiki-de-es.jpg|DE - ES - Availability Management|100px | ||
Line 8: | Line 8: | ||
<br style="clear:both;"/> | <br style="clear:both;"/> | ||
<p> </p> | |||
''' | ==<span id="ITIL Availability Management">Overview</span>== | ||
'''Objective''': ''ITIL Availability Management'' aims to define, analyze, plan, measure and improve all aspects of the availability of IT services. Availability Management is responsible for ensuring that all IT infrastructure, processes, tools, roles etc are appropriate for the agreed availability targets. | |||
'''Part of''': [[ITIL V3 Service Design|Service Design]] | '''Part of''': [[ITIL V3 Service Design|Service Design]] | ||
'''Process Owner''': [[Availability Management# | '''Process Owner''': [[Availability Management#Availability Manager|Availability Manager]] | ||
<p> </p> | |||
== Process Description == | |||
[[Image:Availability-management.jpg|right|thumb|375px|alt=Availability Management ITIL|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_availability_management_itilv3.pdf ITIL Availability Management]]] | |||
There are no major differences between Capacity 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 [[Media:Availability-management.jpg|ITIL Availability Management (.JPG)]] is showing the most important interfaces (see Figure 1). | |||
<p> </p> | |||
== Sub-Processes == | |||
These are the ITIL Availability Management sub-processes and their process objectives: | |||
<p> </p> | |||
< | |||
= | ;<span id="Availability Management Design">Design Services for Availability</span> | ||
:Process Objective: To design the procedures and technical features required to fulfill the agreed availability levels. | :Process Objective: To design the procedures and technical features required to fulfill the agreed availability levels. | ||
;Availability Testing | ;<span id="Availability Management Testing">Availability Testing</span> | ||
:Process Objective: To make sure that all availability, resilience and recovery mechanisms are subject to regular testing. | :Process Objective: To make sure that all availability, resilience and recovery mechanisms are subject to regular testing. | ||
;Availability Monitoring and Reporting | ;<span id="ITIL Availability Management Reporting">Availability Monitoring and Reporting</span> | ||
: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. | :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. | ||
<p> </p> | |||
==== | == Definitions == | ||
The following ITIL terms and acronyms (''information objects'') are used in ITIL Availability Management to represent process outputs and inputs: | |||
<p> </p> | |||
;<span id="Availability Design Guidelines">Availability Design Guidelines</span> | ;<span id="Availability Design Guidelines">Availability Design Guidelines</span> | ||
: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. | :The [[Availability Management#Availability Management Design|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. | ||
;<span id="Availability Guidelines for the Service Desk">Availability Guidelines for the Service Desk</span> | ;<span id="Availability Guidelines for the Service Desk">Availability Guidelines for the Service Desk</span> | ||
Line 60: | Line 65: | ||
;<span id="Availability ITSCM Security Testing Schedule">Availability/ ITSCM/ Security Testing Schedule</span> | ;<span id="Availability ITSCM Security Testing Schedule">Availability/ ITSCM/ Security Testing Schedule</span> | ||
:A schedule for the regular testing of all availability, continuity and security mechanisms, jointly maintained by Availability, IT Service Continuity and IT Security Management. | :A schedule for the regular [[Availability Management#Availability Management Testing|testing of all availability]], continuity and security mechanisms, jointly maintained by [[Availability Management|Availability]], [[IT Service Continuity Management|IT Service Continuity]] and [[IT Security Management|Information Security Management]]. | ||
;<span id="Availability Report">Availability Report</span> | ;<span id="Availability Report">Availability Report</span> | ||
Line 66: | Line 71: | ||
;<span id="SOP">Maintenance Plan/ SOP</span> | ;<span id="SOP">Maintenance Plan/ SOP</span> | ||
: | :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 [[Availability Management#Technical Manual|technical or administration manuals]] to define in a concise manner the tasks to be carried out as part of standard operations. | ||
;<span id="Recovery Plan">Recovery Plan</span> | ;<span id="Recovery Plan">Recovery Plan</span> | ||
:Recovery Plans are created mainly by Availability and IT Service Continuity Management. The plans contain | :Recovery Plans are created mainly by Availability and IT Service Continuity Management. The plans contain specific instructions for returning services and/or systems to a working state, which often includes recovering data to a known consistent state. | ||
;<span id="Technical Manual">Technical/ Administration Manual</span> | |||
:A document describing the procedures required to run and maintain a type of application or infrastructure component. | |||
;<span id="Test Report">Test Report</span> | ;<span id="Test Report">Test Report</span> | ||
:A report of the preparation, progress and evaluation of a test, created for example during the various tests carried out by Availability, IT Service Continuity or IT Security Management. | :A report of the preparation, progress and evaluation of a test, created for example during the various tests carried out by [[Availability Management|Availability]], [[IT Service Continuity Management|IT Service Continuity]] or [[IT Security Management|Information Security Management]]. | ||
<p> </p> | |||
== | == Checklists | KPIs == | ||
* [[ITIL KPIs Service Design#ITIL KPIs Availability Management|Key Performance Indicators (KPIs) Availability Management]] | * [[ITIL KPIs Service Design#ITIL KPIs Availability Management|Key Performance Indicators (KPIs) Availability Management]] | ||
* [[ITIL-Checklists#Checklists for Availability Management|Checklists Availability Management]]: | |||
** [[Checklist Availability Improvement Plan]] | |||
** [[Checklist Availability Report]] | |||
<p> </p> | |||
== Roles | Responsibilities == | |||
;<span id="Availability Manager">Availability Manager - Process Owner</span> | |||
: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. | |||
<p> </p> | |||
{| border="1" cellpadding="5" cellspacing="0" style="text-align:center;" valign="top" | |||
|- | |||
| valign="top" colspan="6" style="background:#ffffdd;" align="center"| '''Responsibility Matrix: ITIL Availability Management''' | |||
|- | |||
! width="50%" align="center" style="background:#ffffee;" | ITIL Role | Sub-Process | |||
! style="background:#ffffee;" | [[Availability Management#Availability Manager|Availability Manager]] | |||
! style="background:#ffffee;" | Service Owner[[Availability Management#ITIL-Rollen|<small>[3]</small>]] | |||
! style="background:#ffffee;" | Applications Analys[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
! style="background:#ffffee;" | Technical Analyst[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
! style="background:#ffffee;" | IT Operator[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
|- | |||
| align="left" |[[#Availability Management Design|Design Services for Availability]] | |||
| A[[Availability Management#Accountable|<small>[1]</small>]]R[[Availability Management#Responsible|<small>[2]</small>]] | |||
| R[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
| R[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
| R[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
| | |||
|- | |||
| align="left" |[[#Availability Management Testing|Availability Testing]] | |||
| AR | |||
| | |||
| | |||
| | |||
| R[[Availability Management#ITIL Roles|<small>[3]</small>]] | |||
|- | |||
| align="left" |[[#ITIL Availability Management Reporting|Availability Monitoring and Reporting]] | |||
| AR | |||
| | |||
| | |||
| | |||
| | |||
|- | |||
|} | |||
<p> </p> | |||
'''Remarks''' | |||
<span id="Accountable">[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.</span> | |||
<span id="Responsible">[2] ''R: Responsible'' according to the RACI Model: Those who do the work to achieve a task within ITIL Availability Management.</span> | |||
<span id="ITIL Roles">[3] siehe [[Roles within ITIL V3|→ Role descriptions ...]]</span> | |||
< | <p> </p> | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V3]][[Category:ITIL process]][[Category:Service Design|Availability Management]][[Category:Availability Management|!]] | [[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Design|Availability Management]][[Category:Availability Management|!]] | ||
<!-- --- --> | <!-- --- --> |
Revision as of 15:32, 29 November 2011
<seo metakeywords="availability management, itil availability management, availability management itil, availability management process, availability itil v3" metadescription="Availability Management: ITIL process definition - Sub-processes - Terms - Additional information on ITIL Availability Management." />
Overview
Objective: ITIL Availability Management aims to define, analyze, plan, measure and improve all aspects of the availability of IT services. Availability Management 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
There are no major differences between Capacity 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) is showing the most important interfaces (see Figure 1).
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 ITIL Availability Management 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
- A schedule for the regular testing of all availability, continuity and security mechanisms, jointly maintained by Availability, IT Service Continuity and Information Security Management.
- Availability Report
- The Availability Report provides other Service Management processes and IT Management with information related to service and infrastructure component availability.
- 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 and IT Service Continuity Management. The plans contain specific instructions for returning 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 report of the preparation, progress and evaluation of a test, created for example during the various tests carried out by Availability, IT Service Continuity or Information Security Management.
Checklists | 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[3] | R[3] | R[3] | |
Availability Testing | AR | R[3] | |||
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] siehe → Role descriptions ...