Availability Management

 

Availability management is a key topic in virtually all service management frameworks and standards:

 

Availability management in the ITSM frameworks (examples)

Frame­work	Realization
ITIL® 4	ITIL® 4 includes the practice of availability management. As per ITIL 4, availability management aims to "ensure that services deliver agreed levels of availability to meet the needs of customers and users". It is essentially about identifying the availability requirements of the services determining how service availability can be ensured in an economical way monitoring service availability and taking corrective action if needed.
ITIL V3	ITIL V3 defines availability management as a service lifecycle process.
ISO 20000	ISO 20000 specifies require­ments for the management of service availability.
SIAM	SIAM refers to availability manage­ment as one of the processes within a SIAM ecosystem.
VeriSM	In VeriSM, availability management is a key element in the VeriSM high-level stages for services.
COBIT	In the COBIT® 5 process reference model we find 'Manage Availability and Capacity' as part of the 'Build, Acquire and Implement (BAI)' processes.
CMMI-SVC	CMMI for services (CMMI-SVC®) contains a process area called 'Capacity and Availability Management (CAM)'.
USMBOK	USMBOK™ refers to 'Service Availability Management' as a knowledge area in the knowledge domain of 'Service Delivery Management'.

 

So it is commonly accepted that the management of service availability is critical for any service provider, but still many organizations find it difficult to implement availability management in practice.

The problem may be the way it is presented: Availability management is usually described as a distinct process, practice or capability, using its own set of plans and reports. It has numerous interfaces with other processes because it needs to spring into action whenever service availability issues need to be dealt with.

This kind of complex interfacing makes it hard to understand how all the processes are supposed to work together, which in turn makes it difficult to implement a working set of processes in practice.

Availability management in YaSM

To get around these problems in YaSM, we decided that availability management does not need to be a service management process of its own.

Fig. 1: Availability management
Managing service availability in the YaSM service management process model.

Instead, YaSM takes the view that service availability is an aspect to be considered at every stage of the service lifecycle - for instance when defining services, during service operation, and when continuously improving services.

There are thus, for instance, activities in the service design processes to identify and define the required levels of service availability. Service availability is continually monitored as part of service operation, and if any availability issues are detected, corrective action will be taken - either in the form of pre-defined routine operational activities or service improvement initiatives.

As a result, it is very clear in YaSM how service availability can be managed by embedding appropriate activities in the service lifecycle processes. Implementing an availability management capability in practice is thus quite straightforward.

On a side note, the YaSM way of managing service availability is quite in tune with the latest thinking in service management:

F.e., ITIL V4 describes availability management as a practice and lists the key activities, but does not say there must be an availability management process. Rather, ITIL 4 encourages service providers to define tailor-made processes that work for the organization.

Related pages

• YaSM service management processes
• Comparison: ITIL 4 practices and YaSM processes
• YaSM and ISO 20000

References

[a] IT Process Wiki - ITIL Availability Management. -- S. Kempter: IT Process Wiki, "ITIL Availability Management". - IT Process Maps; Lindau (Bodensee), Germany.
[AXELOS, 2019]. -- AXELOS: ITIL^® Foundation, ITIL 4 Edition. - The Stationery Office; Norwich, UK, February 2019.

By:  Stefan Kempter , IT Process Maps.