Skip to main content

The Best of Service Design, Part 3

The Importance of Availability Management
Originally Published on July 5, 2011

The Availability Management process ensures that the availability of systems and services matches the evolving agreed needs of the business. The role of IT is now integral to the success of the business. The availability and reliability of IT services can directly influence customer satisfaction and the reputation of the business. The proactive activities of Availability Management involve the proactive planning, design and improvement of availability. These activities are principally involved within design and planning roles.
The proactive activities consist of producing recommendations, plans and documents on design guidelines and criteria for new and changed services, and the continual improvement of service and the reduction of risk in existing services wherever it can be cost-justified. There are several guiding principles that should underpin the Availability Management process and its focus:
  • Service availability is at the core of customer satisfaction and business success: there is a direct connection between the service availability and customer and user satisfaction, where poor service performance is defined as being unavailable.  
  • Recognizing that when services fail, it is still possible to achieve business, customer and user satisfaction and how quickly a service can be restored to normal operation can have a profound effect on user perception and expectation.
  • Improving availability can only begin after understanding how the IT services support the operation of the business and defining which services support those Vital Business Functions (VBF).
  • Service availability is only as good as the weakest link in the chain: it can be greatly increased by the elimination of Single Points of Failure (SPoFs) or an unreliable or weak component. Availability Management using historical incident and problem data can identify and then remove these fragile Configuration items (CI). 
  • It is cheaper to design the right level of service availability into a service from the start rather than try to ‘bolt it on’ subsequently. Adding resilience into a service or component is invariably more expensive than designing it in from the start.
Underpinning these key principles are the following proactive activities of availability management:
  • Determining the availability requirements from the business for a new or enhanced IT service and formulating the availability and recovery design criteria for the supporting IT components. 
  • Determining the VBFs, in conjunction with the business and ITSCM.
  • Determining the impact arising from IT service and component failure in conjunction with ITSCM and, where appropriate, reviewing the availability design criteria to provide additional resilience to prevent or minimize impact to the business.
  • Defining the targets for availability, reliability and maintainability for the IT infrastructure components that underpin the IT service to enable these to be documented and agreed within SLAs, OLAs and contracts.
  • Establishing measures and reporting of availability, reliability and maintainability that reflect the business, user and IT support organization perspectives.
  • Monitoring and trend analysis of the availability, reliability and maintainability of IT components. 
  • Reviewing IT service and component availability and identifying unacceptable levels.
  • Investigating the underlying reasons for unacceptable availability.
  • Producing and maintaining an Availability Plan that prioritizes and plans IT availability improvements.


Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with