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.

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

Search