Availability Management - ITIL V2: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 22: | Line 22: | ||
==Sub-Processes== | ==Sub-Processes== | ||
[[Image:overview_am.jpg| | [[Image:overview_am.jpg|thumb|723px|none|link=https://wiki.en.it-processmaps.com/index.php/File:Overview_am.jpg|Overview of Availability Management]] | ||
'''Define Guidelines for High Availability''' | '''Define Guidelines for High Availability''' | ||
*Process objective: Definition of guidelines for applications and infrastructure components, so that these can be taken into consideration at an early stage (e.g. during their development or acquisition). | *Process objective: Definition of guidelines for applications and infrastructure components, so that these can be taken into consideration at an early stage (e.g. during their development or acquisition). | ||
'''Identify Need for Action with Regards to Availability''' | '''Identify Need for Action with Regards to Availability''' | ||
*Process objective: Analysis of availability levels required within the SLAs, and identification of areas within the IT infrastructure where action is needed in order to ensure sufficiently high availability. | *Process objective: Analysis of availability levels required within the SLAs, and identification of areas within the IT infrastructure where action is needed in order to ensure sufficiently high availability. | ||
'''Compile [[ITIL Glossary#Availability Improvement Plan|Availability Improvement Plan]]''' | '''Compile [[ITIL Glossary#Availability Improvement Plan|Availability Improvement Plan]]''' | ||
*Process objective: Design of concrete suggestions for measures aimed at the increase in availability, based on previously identified needs for action; compilation of corresponding RFCs. | *Process objective: Design of concrete suggestions for measures aimed at the increase in availability, based on previously identified needs for action; compilation of corresponding RFCs. | ||
'''Commission Measures for the Increase in Availability''' | '''Commission Measures for the Increase in Availability''' | ||
*Process objective: After the successful clearance of the Change, the implementation planning is to be detailed; subsequently the implementation is commissioned to suitable technical experts within Application or Infrastructure Management. | *Process objective: After the successful clearance of the Change, the implementation planning is to be detailed; subsequently the implementation is commissioned to suitable technical experts within Application or Infrastructure Management. | ||
'''Monitor Availability''' | '''Monitor Availability''' | ||
*Process objective: Monitoring of the availabilities agreed within the SLAs and where necessary, identification of needs for action for ensuring the agreed Service Levels. | *Process objective: Monitoring of the availabilities agreed within the SLAs and where necessary, identification of needs for action for ensuring the agreed Service Levels. | ||
'''Carry out [[ITIL Glossary#Availability Report|Availability Reporting]]''' | '''Carry out [[ITIL Glossary#Availability Report|Availability Reporting]]''' | ||
*Process objective: Reporting on the adherence to availability agreements, and on counter-measures for the correction to occurred infringements or projected availability issues. | *Process objective: Reporting on the adherence to availability agreements, and on counter-measures for the correction to occurred infringements or projected availability issues. | ||
==Involved Roles== | ==Involved Roles== | ||
*'''<span id="Availability-Manager-ITIL-V2">Availability Manager</span>''': In ITIL V2 the Availability Manager ensures the sufficient availability of the IT Infrastructure, so that the availability-levels agreed in the SLAs can be adhered to. He ensures the regular measurement of availability, and when necessary the undertaking of measures for its improvement. | *'''<span id="Availability-Manager-ITIL-V2">Availability Manager</span>''': In ITIL V2 the Availability Manager ensures the sufficient availability of the IT Infrastructure, so that the availability-levels agreed in the SLAs can be adhered to. He ensures the regular measurement of availability, and when necessary the undertaking of measures for its improvement. | ||
==Related Checklists and KPIs== | ==Related Checklists and KPIs== | ||
Line 63: | Line 52: | ||
====KPIs==== | ====KPIs==== | ||
*[[KPIs Availability Management|Key Performance Indicators "Availability Management" according to ITIL V2]] | *[[KPIs Availability Management|Key Performance Indicators "Availability Management" according to ITIL V2]] | ||
==Related [[ITIL Glossary]] Terms== | ==Related [[ITIL Glossary]] Terms== | ||
*[[ITIL Glossary/_ITIL_Terms_A#Availability Improvement Plan|Availability Improvement Plan]] | *[[ITIL Glossary/_ITIL_Terms_A#Availability Improvement Plan|Availability Improvement Plan]] | ||
*[[ITIL Glossary/_ITIL_Terms_A#Availability Report|Availability Report]] | *[[ITIL Glossary/_ITIL_Terms_A#Availability Report|Availability Report]] | ||
<!-- This page is assigned to the following categories: --> | <!-- This page is assigned to the following categories: --> | ||
[[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Delivery|Availability Management - ITIL V2]][[Category:Availability Management]] | [[Category:ITIL V2]][[Category:ITIL process]][[Category:Service Delivery|Availability Management - ITIL V2]][[Category:Availability Management]] | ||
<!-- --- --> | <!-- --- --> |
Latest revision as of 17:56, 4 February 2016
ITIL Version: ITIL V2 → see also Availability Management - ITIL V3
Process-Objective: Availability Management allows IT Organisations to sustain the availability of the IT infrastructure in order to meet the agreed Service Levels defined in SLAs. It constantly monitors the achieved availability levels and where necessary, undertakes corrective measures.
Part of: Service Delivery
Process Owner: Availability Manager
Sub-Processes
Define Guidelines for High Availability
- Process objective: Definition of guidelines for applications and infrastructure components, so that these can be taken into consideration at an early stage (e.g. during their development or acquisition).
Identify Need for Action with Regards to Availability
- Process objective: Analysis of availability levels required within the SLAs, and identification of areas within the IT infrastructure where action is needed in order to ensure sufficiently high availability.
Compile Availability Improvement Plan
- Process objective: Design of concrete suggestions for measures aimed at the increase in availability, based on previously identified needs for action; compilation of corresponding RFCs.
Commission Measures for the Increase in Availability
- Process objective: After the successful clearance of the Change, the implementation planning is to be detailed; subsequently the implementation is commissioned to suitable technical experts within Application or Infrastructure Management.
Monitor Availability
- Process objective: Monitoring of the availabilities agreed within the SLAs and where necessary, identification of needs for action for ensuring the agreed Service Levels.
Carry out Availability Reporting
- Process objective: Reporting on the adherence to availability agreements, and on counter-measures for the correction to occurred infringements or projected availability issues.
Involved Roles
- Availability Manager: In ITIL V2 the Availability Manager ensures the sufficient availability of the IT Infrastructure, so that the availability-levels agreed in the SLAs can be adhered to. He ensures the regular measurement of availability, and when necessary the undertaking of measures for its improvement.