Availability Management: Difference between revisions

From IT Process Wiki
No edit summary
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
<itpmch><title>Availability Management | IT Process Wiki</title>
<itpmch><title>Availability Management | IT Process Wiki</title>
<meta name="keywords" content="availability management, itil availability management, availability management itil, availability management process, availability itil v3" />
<meta name="keywords" content="availability management, itil availability management, availability management itil, availability management process, availability itil v3" />
<meta name="description" content="Availability Management: ITIL process definition - Sub-processes - Terms - Additional information on ITIL Availability Management." />
<meta name="description" content="ITIL Availability Management aims to define, analyze, plan, measure and improve all aspects of the availability of IT services. It is responsible for ensuring that all IT infrastructure, processes, tools, roles etc are appropriate for the agreed availability targets." />
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Availability_Management" />
<meta property="og:url" content="https://wiki.en.it-processmaps.com/index.php/Availability_Management" />
<meta property="og:title" content="Availability Management | IT Process Wiki" />
<meta property="og:title" content="Availability Management | IT Process Wiki" />
Line 11: Line 11:
<meta property="fb:admins" content="100002592864414" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/3/3d/Availability-management.jpg" />
<meta property="og:image" content="https://wiki.en.it-processmaps.com/images/3/3d/Availability-management.jpg" />
<meta property="og:image:width" content="960" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="866" />
<meta property="og:image:height" content="1200" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
<link href="https://plus.google.com/108613479011811316823/posts" rel="publisher" />
</itpmch>
</itpmch>
<imagemap>
<imagemap>
Image:ITIL-Wiki-de-es.jpg|DE - ES - Availability Management|100px
Image:ITIL-Wiki-de-es.jpg|right|DE - ES - Availability Management|163px
rect 0 0 50 30 [https://wiki.de.it-processmaps.com/index.php/Availability_Management diese Seite auf Deutsch]
rect 81 0 114 36 [https://wiki.de.it-processmaps.com/index.php/Availability_Management diese Seite auf Deutsch]
rect 50 0 100 30 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_la_Disponibilidad esta página en español]
rect 115 0 163 36 [https://wiki.es.it-processmaps.com/index.php/ITIL_Gestion_de_la_Disponibilidad esta página en español]
desc none
desc none
</imagemap>
</imagemap>
<br style="clear:both;"/>
<br style="clear:both;"/>
<p>&nbsp;</p>


'''<span id="Overview">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description"><i>ITIL Availability Management</i> 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.</span></p>
'''<span id="Overview">Objective:</span>''' <html><span id="md-webpage-description" itemprop="description"><i>ITIL Availability Management</i> 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.</span></p>
Line 34: Line 32:
==Process Description==
==Process Description==


[[Image:Availability-management.jpg|right|thumb|500px|alt=Availability Management ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Availability-management.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_availability_management_itilv3.pdf ITIL Availability Management]]]
There are no major differences between Availability Management in ITIL V3 (2007) and ITIL 2011.
There are no major differences between Availability Management in ITIL V3 (2007) and ITIL 2011.
[[Image:Availability-management.jpg|right|thumb|375px|alt=Availability Management ITIL|link=https://wiki.en.it-processmaps.com/index.php/File:Availability-management.jpg|[https://wiki.en.it-processmaps.com/images/pdf/process_overview_availability_management_itilv3.pdf ITIL Availability Management]]]


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 Fig. 1).
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)]] shows the key information flows (see fig. 1).


[[ITIL 4]] refers to 'Availability Management' as a [[ITIL_4#Service_management_practices|service management practice]].
<p>&nbsp;</p>
<p>&nbsp;</p>


Line 47: Line 46:
<p><span itemprop="name" content="Availability Management sub-processes:">These are the <strong class="selflink">ITIL Availability Management</strong> sub-processes and their process objectives:</span>
<p><span itemprop="name" content="Availability Management sub-processes:">These are the <strong class="selflink">ITIL Availability Management</strong> sub-processes and their process objectives:</span>
</p>
</p>
<p>&#160;</p>
<p><b><span id="Availability_Management_Design" itemprop="itemListElement">Design Services for Availability</span></b>
<p><b><span id="Availability_Management_Design" itemprop="itemListElement">Design Services for Availability</span></b>
</p>
</p>
<ul><li itemprop="description">Process Objective: To design the procedures and technical features required to fulfill the agreed availability levels.
<ul><li itemprop="description">Process Objective: To design the procedures and technical features required to fulfill the agreed availability levels.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_Management_Testing" itemprop="itemListElement">Availability Testing</span></b>
</p><p><b><span id="Availability_Management_Testing" itemprop="itemListElement">Availability Testing</span></b>
</p>
</p>
<ul><li itemprop="description">Process Objective: To make sure that all availability, resilience and recovery mechanisms are subject to regular testing.
<ul><li itemprop="description">Process Objective: To make sure that all availability, resilience and recovery mechanisms are subject to regular testing.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="ITIL_Availability_Management_Reporting" itemprop="itemListElement">Availability Monitoring and Reporting</span></b>
</p><p><b><span id="ITIL_Availability_Management_Reporting" itemprop="itemListElement">Availability Monitoring and Reporting</span></b>
</p>
</p>
<ul><li itemprop="description">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.
<ul><li itemprop="description">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.
</li></ul>
</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>
</div><!-- end of schema.org/ItemList --><p></html>
<p>&nbsp;</p>


== Definitions ==
== Definitions ==
Line 69: Line 64:
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<html><div itemscope="itemscope" itemtype="https://schema.org/ItemList"><!-- define schema.org/ItemList -->
<meta itemprop="itemListOrder" content="Ascending" />
<meta itemprop="itemListOrder" content="Ascending" />
<p><span itemprop="name">The following <a href="/index.php/ITIL%20Glossary#ITIL%20Glossary%20A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in the ITIL Availability Management process to represent process outputs and inputs:</span>
<p><span itemprop="name">The following <a href="/index.php/ITIL_Glossary#ITIL_Glossary_A-Z" title="ITIL Glossary">ITIL terms and acronyms</a> (<i>information objects</i>) are used in the ITIL Availability Management process to represent process outputs and inputs:</span>
</p>
</p>
<p>&#160;</p>
<p><b><span id="Availability_Design_Guidelines" itemprop="itemListElement">Availability Design Guidelines</span></b>
<p><b><span id="Availability_Design_Guidelines" itemprop="itemListElement">Availability Design Guidelines</span></b>
</p>
</p>
<ul><li itemprop="description">The <a href="/index.php/Availability_Management#Availability_Management_Design" title="Availability Management">Availability Design</a> 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.
<ul><li itemprop="description">The <a href="/index.php/Availability_Management#Availability_Management_Design" title="Availability Management">Availability Design</a> 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.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_Guidelines_for_the_Service_Desk" itemprop="itemListElement">Availability Guidelines for the Service Desk</span></b>
</p><p><b><span id="Availability_Guidelines_for_the_Service_Desk" itemprop="itemListElement">Availability Guidelines for the Service Desk</span></b>
</p>
</p>
<ul><li itemprop="description">Rules produced by Availability Management on how to manage Incidents causing unavailability, to prevent minor Incidents from becoming major Incidents.
<ul><li itemprop="description">Rules produced by Availability Management on how to manage Incidents causing unavailability, to prevent minor Incidents from becoming major Incidents.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_Management_Information_System" itemprop="itemListElement">Availability Management Information System</span></b>
</p><p><b><span id="Availability_Management_Information_System" itemprop="itemListElement">Availability Management Information System</span></b>
</p>
</p>
<ul><li itemprop="description">A virtual repository of all Availability Management data, usually stored in multiple physical locations.
<ul><li itemprop="description">A virtual repository of all Availability Management data, usually stored in multiple physical locations.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_Plan" itemprop="itemListElement">Availability Plan</span></b>
</p><p><b><span id="Availability_Plan" itemprop="itemListElement">Availability Plan</span></b>
</p>
</p>
<ul><li itemprop="description">The Availability Plan contains detailed information about initiatives aimed at improving service and/ or component availability.
<ul><li itemprop="description">The Availability Plan contains detailed information about initiatives aimed at improving service and/ or component availability.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_ITSCM_Security_Testing_Schedule" itemprop="itemListElement">Availability/ ITSCM/ Security Testing Schedule</span></b>
</p><p><b><span id="Availability_ITSCM_Security_Testing_Schedule" itemprop="itemListElement">Availability/ ITSCM/ Security Testing Schedule</span></b>
</p>
</p>
<ul><li itemprop="description">A schedule for the regular <a href="/index.php/Availability_Management#Availability_Management_Testing" title="Availability Management">testing of all availability</a>, continuity and security mechanisms, jointly maintained by <strong class="selflink">Availability</strong>, <a href="/index.php/IT_Service_Continuity_Management" title="IT Service Continuity Management">IT Service Continuity</a> and <a href="/index.php/IT_Security_Management" title="IT Security Management">Information Security Management</a>.
<ul><li itemprop="description">A schedule for the regular <a href="/index.php/Availability_Management#Availability_Management_Testing" title="Availability Management">testing of all availability</a>, continuity and security mechanisms, jointly maintained by <strong class="selflink">Availability</strong>, <a href="/index.php/IT_Service_Continuity_Management" title="IT Service Continuity Management">IT Service Continuity</a> and <a href="/index.php/IT_Security_Management" title="IT Security Management">Information Security Management</a>.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_Report" itemprop="itemListElement">Availability Report</span></b>
</p><p><b><span id="Availability_Report" itemprop="itemListElement">Availability Report</span></b>
</p>
</p>
<ul><li itemprop="description">The Availability Report provides other Service Management processes and IT Management with information related to service and infrastructure component availability.
<ul><li itemprop="description">The Availability Report provides other Service Management processes and IT Management with information related to service and infrastructure component availability.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Availability_Management_Rules" itemprop="itemListElement">Event Filtering and Correlation Rules</span></b>
</p><p><b><span id="Availability_Management_Rules" itemprop="itemListElement">Event Filtering and Correlation Rules</span></b>
</p>
</p>
<ul><li itemprop="description">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.
<ul><li itemprop="description">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.
</li><li><i>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.</i>
</li><li><i>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.</i>
</li></ul>
</li></ul>
<p><br />
<p><b><span id="SOP" itemprop="itemListElement">Maintenance Plan/ SOP</span></b>
</p><p><b><span id="SOP" itemprop="itemListElement">Maintenance Plan/ SOP</span></b>
</p>
</p>
<ul><li itemprop="description">Maintenance Plans are part of the operational documentation for applications and infrastructure components, which are sometimes known as <i>Standard Operating Procedures (SOP)</i>. They define the frequency and scope of preventative maintenance. Maintenance Plans/ SOPs are typically extracted from <a href="/index.php/Availability_Management#Technical_Manual" title="Availability Management">technical or administration manuals</a> to define in a concise manner the tasks to be carried out as part of standard operations.
<ul><li itemprop="description">Maintenance Plans are part of the operational documentation for applications and infrastructure components, which are sometimes known as <i>Standard Operating Procedures (SOP)</i>. They define the frequency and scope of preventative maintenance. Maintenance Plans/ SOPs are typically extracted from <a href="/index.php/Availability_Management#Technical_Manual" title="Availability Management">technical or administration manuals</a> to define in a concise manner the tasks to be carried out as part of standard operations.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Recovery_Plan" itemprop="itemListElement">Recovery Plan</span></b>
</p><p><b><span id="Recovery_Plan" itemprop="itemListElement">Recovery Plan</span></b>
</p>
</p>
<ul><li itemprop="description">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.
<ul><li itemprop="description">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.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Technical_Manual" itemprop="itemListElement">Technical/ Administration Manual</span></b>
</p><p><b><span id="Technical_Manual" itemprop="itemListElement">Technical/ Administration Manual</span></b>
</p>
</p>
<ul><li itemprop="description">A document describing the procedures required to run and maintain a type of application or infrastructure component.
<ul><li itemprop="description">A document describing the procedures required to run and maintain a type of application or infrastructure component.
</li></ul>
</li></ul>
<p><br />
<p><b><span id="Test_Report" itemprop="itemListElement">Test Report</span></b>
</p><p><b><span id="Test_Report" itemprop="itemListElement">Test Report</span></b>
</p>
</p>
<ul><li itemprop="description">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 <strong class="selflink">Availability</strong>, <a href="/index.php/IT_Service_Continuity_Management" title="IT Service Continuity Management">IT Service Continuity</a> or <a href="/index.php/IT_Security_Management" title="IT Security Management">Information Security Management</a>.
<ul><li itemprop="description">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 <strong class="selflink">Availability</strong>, <a href="/index.php/IT_Service_Continuity_Management" title="IT Service Continuity Management">IT Service Continuity</a> or <a href="/index.php/IT_Security_Management" title="IT Security Management">Information Security Management</a>.
</li></ul>
</li></ul>
</div><!-- end of schema.org/ItemList --><p></html>
</div><!-- end of schema.org/ItemList --><p></html>
<p>&nbsp;</p>


==<span id="Checklists_.7C_KPIs">Templates | KPIs</span>==
==<span id="Checklists_.7C_KPIs">Templates | KPIs</span>==
Line 141: Line 124:
</ul></li>
</ul></li>
</ul><p></html>
</ul><p></html>
<p>&nbsp;</p>


==Roles | Responsibilities==
==Roles | Responsibilities==
Line 150: Line 132:
<p>&nbsp;</p>
<p>&nbsp;</p>


{| border="1" cellpadding="5" cellspacing="0" style="margin-left: auto; margin-right: auto; text-align:center;" valign="top"
{| class="wikitable" style="background: white;"
|-
|-
|style="vertical-align:top; text-align:center" colspan="6" style="background:#ffffdd;"| '''Responsibility Matrix: ITIL Availability Management'''
|+ style="background:#013b5e; color:#ffffff; font-size: 120%" colspan="6"|'''Responsibility Matrix: ITIL Availability Management'''
|-
|-
!tyle="background:#ffffee; width: 50%; text-align:center" | ITIL Role | Sub-Process
!style="background:#ffffee; width: 50%; text-align:center" | ITIL Role / Sub-Process
! style="background:#ffffee;" | [[Availability Management#Availability Manager|Availability Manager]]
! style="background:#eeeeee;" | [[Availability Management#Availability Manager|Availability Manager]]
! style="background:#ffffee;" | Service Owner[[Availability Management#ITIL-Rollen|<small>[3]</small>]]
! style="background:#eeeeee;" | Service Owner[[Availability Management#ITIL-Rollen|<small>[3]</small>]]
! style="background:#ffffee;" | Applications Analys[[Availability Management#ITIL Roles|<small>[3]</small>]]
! style="background:#eeeeee;" | Applications Analys[[Availability Management#ITIL Roles|<small>[3]</small>]]
! style="background:#ffffee;" | Technical Analyst[[Availability Management#ITIL Roles|<small>[3]</small>]]
! style="background:#eeeeee;" | Technical Analyst[[Availability Management#ITIL Roles|<small>[3]</small>]]
! style="background:#ffffee;" | IT Operator[[Availability Management#ITIL Roles|<small>[3]</small>]]
! style="background:#eeeeee;" | IT Operator[[Availability Management#ITIL Roles|<small>[3]</small>]]
|-
|-
|style="text-align:left;" |[[#Availability Management Design|Design Services for Availability]]
|style="text-align:left;" |[[#Availability Management Design|Design Services for Availability]]
Line 183: Line 165:
|-
|-
|}
|}
<p>&nbsp;</p>


'''Remarks'''
'''Remarks'''
Line 193: Line 173:


<span id="ITIL Roles">[3] see [[ITIL Roles|&#8594; Role descriptions ...]]</span>
<span id="ITIL Roles">[3] see [[ITIL Roles|&#8594; Role descriptions ...]]</span>
<p>&nbsp;</p>


==Notes==
==Notes==


<html>By:&#160;&#160;Stefan Kempter&#160;<a rel="author" href="https://plus.google.com/111925560448291102517/about"><img style="margin:0px 0px 0px 0px;" src="/skins/Vector/images/itpm/bookmarking/gplus.png" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p>
<html>By:&#160;&#160;Stefan Kempter&#160;<a rel="author" href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/images/bookmarking/linkedin.png" width="16" height="16" title="By: Stefan Kempter | Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>, IT Process Maps.</p>


<p>&nbsp;</p>
<p>&nbsp;</p>


<p><small>
<p><small>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<span itemprop="breadcrumb" itemscope itemtype="http://schema.org/BreadcrumbList">
<a href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Process_Description" itemprop="url"><span itemprop="title">Process Description</span></a>
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
</span>
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Process_Description">
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<span itemprop="name">Process Description</span></a>
<a href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Sub-Processes" itemprop="url"><span itemprop="title">Sub-Processes</span></a>
<meta itemprop="position" content="1"></span>
</span>
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Sub-Processes">
<a href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Definitions" itemprop="url"><span itemprop="title">Definitions</span></a>
<span itemprop="name">Sub-Processes</span></a>
</span>
<meta itemprop="position" content="2"></span>
<span itemscope="itemscope" itemtype="http://data-vocabulary.org/Breadcrumb">
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Roles_.7C_Responsibilities" itemprop="url"><span itemprop="title">Roles</span></a>
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Definitions">
<span itemprop="name">Definitions</span></a>
<meta itemprop="position" content="3"></span>
<span itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem">
<a itemprop="item" href="https://wiki.en.it-processmaps.com/index.php/Availability_Management#Roles_.7C_Responsibilities">
<span itemprop="name">Roles</span></a>
<meta itemprop="position" content="4" /></span>
</span>
</span>
</small></p>
</small></p>
Line 228: Line 212:
   <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" />
   <link itemprop="isPartOf" href="https://wiki.en.it-processmaps.com/index.php/ITIL_Service_Design" />
   <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/3/3d/Availability-management.jpg" />
   <link itemprop="primaryImageOfPage" href="https://wiki.en.it-processmaps.com/images/3/3d/Availability-management.jpg" />
   <link itemprop="author" href="https://plus.google.com/111925560448291102517/about" />
  <span id="https://wiki.en.it-processmaps.com/images/3/3d/Availability-management.jpg" itemprop="image" itemscope itemtype="https://schema.org/ImageObject">
  <meta itemprop="caption" content="Availability Management">
  <meta itemprop="contentUrl" content="https://wiki.en.it-processmaps.com/images/3/3d/Availability-management.jpg" />
  <meta itemprop="width" content="1200" />
  <meta itemprop="height" content="1200" />
  <meta itemprop="representativeOfPage" content="true"/>
  <meta itemprop="dateCreated" content="2011-09-19" />
  <meta itemprop="dateModified" content="2020-06-20" />
  <span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
    <meta itemprop="url" content="https://wiki.en.it-processmaps.com/images/thumb/3/3d/Availability-management.jpg/600px-Availability-management.jpg" />
    <meta itemprop="width" content="600" />
    <meta itemprop="height" content="600" />
  </span>
  <meta itemprop="keywords" content="Availability Management" />
  <meta itemprop="keywords" content="ITIL Availability Management" />
  </span>
   <link itemprop="author" href="https://www.linkedin.com/in/stefankempter" />
   <meta itemprop="author" content="Stefan Kempter" />
   <meta itemprop="author" content="Stefan Kempter" />
   <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
   <meta itemprop="creator copyrightHolder publisher" content="IT Process Maps" />
Line 234: Line 234:


<!-- This page is assigned to the following categories: -->
<!-- This page is assigned to the following categories: -->
[[Category:ITIL V3]][[Category:ITIL 2011]][[Category:ITIL process]][[Category:Service Design|Availability Management]][[Category:Availability Management|!]]
[[Category:ITIL 4]][[Category:ITIL 2011]][[Category:ITIL V3]][[Category:ITIL practice]][[Category:ITIL process]][[Category:Service Design|Availability Management]][[Category:Availability Management|!]]
<!-- --- -->
<!-- --- -->

Latest revision as of 12:52, 31 December 2023

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