Why do Service Level Agreements frequently achieve the opposite effect to that intended? Do the parties really understand what risk they are taking on in signing up to these contracts? This paper looks at some of the wilder myths and fundamental errors perpetrated by this burgeoning business practice. The paper takes a sometimes light-hearted, but always focussed, look at the big wide world of the SLA and the industry that has grown up to support it.
Did you find this white paper useful?
4 out of 50 users found this white paper useful
Related white papers
Achieving a Cultural Revolution
The Service Support and Service Delivery ITIL publications refer to "service culture" as one in which the entire organization embraces the concept of service and customer care, where the satisfaction...
Event and Service Impact Management: Managing IT for the Business
Gain valuable insight on managing complex IT environments from the Meta Group. Learn how to better assess service problems and understand how your business is impacted when failures do occur....
24*7 Data Center Support for a Manufacturing Company
The client is the world's largest manufacturer of disk drives, magnetic discs & read-write heads and a leader in storage area network (SAN) solutions and server appliances. The customer required...
Service Level Agreement for Security Services
This paper is a service level agreement for security services. A service level agreement (SLA) defines the services, primary jobs, responsibilities of each agency/group, the methods for delivery of support...
SLA Management
A service level agreement (SLA) is a contract between a service provider and a customer. Here the service provider may be an Internet service provider, a telecommunications carrier, or any...
Trialware: Improving Customer Support and Help Desk Efficiencies with On-Demand Remote Support
Now you can sit at your desk and solve the toughest support problems, remotely. Sure, you can visit all your employees or customers and solve their support issues at their...
Amdocs Case Study: Georgia-Pacific
In 1995, Georgia-Pacific had a 60,000-person, multi-national, multi-location workforce and an IT management operation with 11 separate and inefficient 'island' systems. A review of its IT support function revealed infrastructure...
