Service Level Management - Best Practices


Introduction

  • In an August 2000 study, 182 middle and executive management respondents from large organizations (average 7,000 users/site) answered 35 questions regarding their business, sites, operations and their Service Level Management implementations. They were asked to profile a mission critical service. The objective of the study was to develop a baseline of best practices information and use it as a basis for an on-line assessment tool. The assessment tool can be found at www.nextslm.org/benchmark.
  • As part of the study, a survey was conducted on the web. Five thousand information technology managers and executives from large North American organizations were invited via email to participate.
  • The survey tested the impact of 22 factors on user satisfaction. The factors included key measurements of availability and performance, recovery, Service Level Management features (agreements, reporting, measurement, monitoring, and documentation), resource use, and trends in help desk use and software costs. A Service Level Management Rating (scale: 0 to 100) was developed based on the relationships between these factors and user satisfaction.
  • An international survey will soon be engaged to compare and contrast differences in Service Level Management thought leadership by geographic region. The survey results will be posted on this site.

Highlights

  • The top factors contributing to user satisfaction were:

    - meeting availability requirements
    - having an improving or stable availability trend
    - meeting performance requirements
    - having short recovery times from unplanned outages

These top-mentioned four factors (of 22 measured) accounted for close to 30% of the variation in the rating.

  • Technical Managers had the highest opinion of their performance of Service Level Management tasks and their end users' satisfaction with their service. Technical Management respondents were twice as likely as any other group of respondents to rate their service levels in the top 25% of Service Level Management Ratings. CIOs and Applications Managers tended to describe their SLM near the overall average for the ratings, while Operations Managers tended to rate their operations more critically.
  • Sixty-one (61%) percent of the respondents had service level agreements in place for the mission critical service they were profiling. Most of those agreements had goals, objectives, roles and responsibilities defined, and they generally included specifications of support availability. Penalties for non-performance or missed objectives (25%) and incentives for exceptional performance (17%) were in place in significantly fewer agreements.
  • The study shows clear evidence of an evolutionary pattern in Service Level Management. Three clear groups of respondents exhibit low, medium or high performance in SLM. A key difference between the groups is the performance of the service in meeting basic needs - both the medium and high performing groups accomplish this. High performance appears to be contingent both on meeting basic needs and extending service level management to customer care.
  • Fifty-six (56%) percent of the respondents chose to profile an application they described as a "custom-in-house" application. This highlights the importance of using Service Level Management tools and processes that extend beyond packaged application boundaries.

Attaining Excellence

The following three factors stand out as key to the high performance of a service.

1) Underlying Infrastructure
A solid infrastructure is critical to any underlying SLM effort. If a service is meeting availability and performance requirements then users are generally satisfied. Meeting availability and performance expectations appear to be conditions that must exist for high levels of user satisfaction. They are the "basic" requirements (needs) for user satisfaction to be achieved.

2) Customer Care
What distinguished the "stars" of this study is that they did many things right. Not only did they provide high availability and performance, but also they provided a "customer care" approach to SLM in the form of robust service level agreements, high quality reporting to their users and formal measurement of user satisfaction. Customer focus is what separated the solid SLM performers from the stars. Stars distinguished themselves through high quality communications with their customer-users.

Three distinct groups of responses were observed. Their differences are described below:

  Meeting Basic User Needs? Providing Customer Care? Average SLM Rating User Satisfaction Development Status
Stars
(48%)
YES YES 80 Very Satisfied Customer Care Implemented
Solid Performers
(42%)
YES NO 67 Satisfied to Very Satisfied Infrastructure Needs and Basic User Needs Satisfied
Low Performers (10%) NO YES/NO 48 Neutral to Dissatisfied Early SLM Development

The average SLM rating for all respondents was 71. Solid Performers (42% of respondents) delivered on users' basic needs, and their performance on 19 of 22 factors closely followed the Stars (48% of respondents). Both groups scored high on availability status and trend, performance status and trend, had short recovery times and effectively managed their operations.

The primary difference between Stars and Solid Performers was their implementation of "customer care" service based on three factors:

  • Robustness of Service Level Agreement
  • Sophistication of Reporting Methods to Users
  • Use of a Formal User Satisfaction Measurement System

Low Performers (10% of respondents) did not meet basic requirements, and in general did not have significant SLM implementations - although some elements described above as customer care were present in several members of this group.

We have inferred that the Low Performers are just that - not merely respondents discussing low priority services. This is based on our request that respondents "focus on what you consider to be the most mission-critical application(s) group that you service." As these are all mission critical services, we see stages of development in SLM implementation - and clear evidence that meeting basic user needs should be everyone's first step in the evolution. The elevation of the IT organization to business leadership is achieved from extending consistency and stability into high quality customer care.

3) Industry/Role of Information
The role of information in the business was also a key contributor to user satisfaction and SLM performance. The type of business the organization was engaged in had a strong correlation to user satisfaction and SLM performance.

Above Average Performing Industry Sectors:

  • Services
  • Healthcare
  • Financial Services

Below Average Performing Sectors:

  • Utilities
  • Communications
  • Government/Education
  • Manufacturing
  • Distribution

The above average group consists predominately of high-technology service providers, other professional services providers (e.g. facilities, logistics, etc.), large-scale healthcare organizations, healthcare services organizations, and insurance and financial services organizations. These business types are generally characterized by a high reliance on information. Hence their information technology organizations are not a business adjunct, but rather a significant part of the core business. They have high SLM ratings (71 to 78 points) and the group's leading scorers are well on their way to implementing customer care. They are managing their information assets as a business function, and are managing their relationships with their end users. Most of the Stars are from these sectors.

The below average performing sectors (65 to 70 points) have demonstrated limited to no customer care implementation. They are generally meeting basic user needs. These businesses are also dependent on information technology but also tend to manage large physical assets. Information technology is more frequently a business adjunct than a core business. Generally the Solid Performers are prevalent in these sectors.

It must be noted that the preceding statements are about tendencies. Certainly there are high performing distributors in terms of SLM and user satisfaction. Likewise there are low performing services organizations. However the industry relationships discussed above are generally statistically significant.


SLM Implementation Insights

It is clear that the basic availability and performance needs of users must be met for user satisfaction to be high. Service Level Management, and more specifically, its customer care aspects, are a leverage point to a higher level of user satisfaction. One of the many questions left unresolved by this baseline study is the causative relationship between the elements. That is, if you attack basic availability issues first, and then address customer care are you any better off than using the converse strategy or a parallel strategy? The research only suggests that there is a hierarchy of needs that must be met for high satisfaction and that our respondents tend to cluster around "stations" on that need hierarchy. There are strong indications that implementations are clustered in their self-assessment of SLM, inferring that there are stages of SLM development and that success (as measured by user satisfaction) is achieved in steps.

Industry comparisons point to a relationship between user satisfaction, the importance of information to the organization and the steps taken to manage information as a business asset.

The study sponsors have found from their experiences in SLM service engagements that their clients tend to follow four distinct stages of evolution in Service Level Management.

  • The initial stage, "foundation monitoring," which includes metric collection, repository and reporting, threshold management and central event management, is fundamental to serving the basic needs of the user community.
  • This stage is followed either by a focus on the business impact of SLM and the implementation of real-time SLA notification, SLA reporting, and a service view of system components or a focus on the information systems impact of SLM as evidenced by the implementation of automating collective actions, incident management, and event analysis.
  • In any event, both steps are taken in the drive to the most advanced state, "predictive service assurance." The respondents of this study show behaviors that re-enforce this evolutionary view of Service Level Management.

Service Level Benchmark - Key Findings

Over 60% of respondents reported having service level agreements in place for the particular service on which they reported. Generally, these agreements were broad, including definition of roles and responsibilities, goals, reporting polices and support availability. A significantly smaller percentage reported performance penalties or incentives. About half included procedures for adjusting to changing conditions.

Over half (62%) of the respondents with agreements in place provided reporting based on aggregated indicators of infrastructure or components. Thirty-six (36%) percent reported having automated reporting systems that provided customized reports to users. Twenty-two (22%) percent of those with agreements did not provide reports to end-users.

Generally, respondents felt that their problem documentation was somewhat effective or very effective. Only 8% felt their documentation was ineffective. Key reasons why documentation was not very effective included lack of sufficient details, ineffective use of documentation, and out of date or difficult to access documentation.

Respondents reported availability as meeting user requirements 92% of the time. Only 5% reported declining availability.

Similarly, 87% of the respondents indicated performance as meeting requirements and 11% reported performance as declining.

Use of staff resources to support availability and performance issues was relatively low. About half (45-55%) of respondents reported less than 20% use of their systems administrators', applications administrators' and database administrators' time to support availability or performance issues. Only 5% of the respondents indicated that 60% of their administrators' time was engaged in availability and performance issues.

Infrastructure implemented to support high service levels was prevalent. Approximately 70% reported a high availability server configuration or a parallel sysplex, more than 50% mirrored disk and over 42% reported network failover configurations. Only 11% reported no specific high availability infrastructure features.

Respondents were very positive about their end users' satisfaction. Only 17% reported neutral or dissatisfied users. In general, user satisfaction was positively related to all elements of sophisticated service level management. Fifty-six (56%) percent of respondents reported having a formal user satisfaction measurement program. Respondents with formal programs were more likely to report higher user satisfaction than those without a formal measurement program.

Respondents and Sites

The 182 respondents came from a broad spectrum of industries - dominated by commercial, financial and services sector organizations.

Sixty (60%) percent of respondents were from sites with over 20 terabytes of on-line data. Thirteen (13%) percent had over 80 TB.

Approximately 50% of the sites had more than 7,000 users, and half of those had more than 15,000 users.

About a third (31%) of the respondents were in technical management roles, 20% were in applications management roles, and 15% were IT executives.


Methodology

This survey was conducted by CustomerSat.Com using a web-based approach.


Sponsors

The study was sponsored by BMC Software, Sun Microsystems and PricewaterhouseCoopers.

home


sponsored by
BMC Software
Remedy



White Paper: Implementing Service Level Management: Practical Guidelines for the IT Support Organization
by Char LaBounty


White Paper: Implementing ITIL with Remedy (pdf, 198kb)


Datasheet:
Remedy's Comprehensive ITIL Solution (pdf, 624kb)

 

 


Copyright (c) 2000-2003, nextslm.org. All Rights Reserved. Legal Statement.