By: Tony Lock, Chief Analyst, Bloor Research (Moved)
Published: 29th March 2006
Copyright Bloor Research © 2006
There has been much discussion over the last few years in IT concerning service management and service level management. Much of the dialogue has centred on creating SLAs (Service Level Agreements). In organisations large and small a multitude of SLAs have been introduced between IT and its customers. It is fair to say that frequently the introduction of these SLAs have had little visible impact on the perceived quality of service enjoyed by said customers.
It can also be argued that whilst the introduction of IT SLAs has not been felt by many customers to improve their perception of the IT services they receive, their introduction has, in many cases, materially worsened relationships between IT and its business customers. Why should this be so?
It is my belief that a major factor in the poor reputation enjoyed by most IT SLAs is a direct consequence of the fact that the majority have been written by IT specialists in terms that only make sense to someone with a sound understanding of IT systems and supporting infrastructures. For example, many SLAs focus only on ‘uptime’ or ‘availability’—metrics that are only measurable by IT.
However, it is not unknown for IT systems to be measured as being up and available whilst users of the system consider them to be unavailable or running so slowly as to be regarded as unusable. Such disconnects in communication, SLA generation, SLA measurement and monitoring damage the reputation not just of the SLAs themselves but materially damage the trust between business consumers of IT services and IT departments.
The use of SLAs inevitably leads to the creation of customer expectations that the quality of the IT service delivered will improve. It is essential that such expectations are well managed. Even when service quality does get better, service consumers need to be told so, and they require that they receive such information in language that they understand. Moreover, they need to have tangible proof to back up such claims.
The future of IT and the future of business are absolutely interconnected. It is therefore essential that a new breed of SLA be brought to bear in IT service delivery. Such SLAs must be more meaningful to the consumers of the service. This in turn requires customer input in the SLA generation process. SLAs must measure things that are tangible to the IT service consumer and measure factors of import to them. Availability will have a role to play, but not in isolation. Instead availability will be coupled with factors such as application response time, numbers of transactions executed, security levels achieved or any number of matters that are deemed by the service consumer to be important.
Such new SLAs will also demand that trusted, independent means of measuring and monitoring the SLA be implemented. Equally, the reporting of service levels delivered must become central to the IT – business customer relationship. Such reporting must be at a business level not of a technical nature. If meaningful SLAs can be fashioned, monitored and measured, IT services will meet business needs. More importantly SLA monitoring in this manner provides IT with a means to positively improve its profile within the business itself. Today it is fair to say that most business users of IT services neither trust their colleagues in IT nor understand the true business value that IT delivers.
There is an opportunity here to materially improve these issues. Business needs IT. IT must garner business trust for both IT and the business to enjoy the maximum benefits deliverable by IT. Business-based IT SLAs have immense potential. Tools exist to support such SLAs but there also needs to be a will to do so. Are you ready?
Posted: 1st April 2006 | By Yakov Kogan :
Tom, Great article. I think it raises the most important point in SLA management - effective SLAs state truly business needs and not what is easier to measure. Most e-shops need 100% end-to-end availability during a day and not 99.99% availability of all networking and computer components 24x7. A service meeting the later SLA will cost much more and will not address the business need. Yakov Kogan
Posted: 4th April 2006 | By Steve Penn :
SLAs need to be targetted at metrics that are "critical to success or satisfaction (CTS)" These factors should also be weighted by the business to determine priority. Once these are understood and the services are aligned we are on the right tracks. All causes of issues minor/major changes or project initiatives can be 'scored' according to their impact (good or bad) to these CTS factors so that a yield in business terms can be communicated with the business users. e.g. We should seek approval for funding on project A instead of project B because it will give us a 20% improvement in performance which is a high priority CTS factor. You get the picture. Cheers.
The messages above were all contributed by IT-Director.com readers. Whilst we take care to remove any posts deemed inappropriate, we can take no responsibility for these comments. If you would like a comment removed please contact our editorial team.
We automatically stop accepting comments 180 days after a post is published. If you would like to know more about this subject, please contact us and we'll try to help.
Published by: electronicdawn Ltd.