Sunday, 29 January 2017

Making A Service Level Agreement With Your Hosting Services Provider


By Sachin Bhardwaj, eHosting DataFort, Director, Marketing & Business Development

With the increasing adoption of Managed and Cloud services, where either an entire or a part of IT function is outsourced to a third-party services provider, the need for unambiguous, easy to apply and easy to follow service agreements are becoming more important. The level of effort that goes into preparation of a Service Level Agreement (SLA) between a services provider and the end-customer, is usually proportionate to the duration of the engagement. Typically, a longer term contractual engagement will have more detailed and rigorous descriptions.
A Service Level Agreement is defined as an official undertaking between a Hosting Services Provider and an end-customer. This agreement describes various aspects of the service including quality, availability, and responsibilities. The SLA converts the Hosting Provider’s services into a known function. This is particularly important where continuity and consistency of services from the Hosting Provider is important for the end-customer.
In fact, SLAs are now widely used in a range of IT related services. These include IT administration services, managed application services, Cloud Computing, amongst others. Another spin off is the use of SLAs by IT teams within an organisation to manage the expectations of in-house stakeholders and customers. This helps the IT team of the organisation to have its services justified, measured and benchmarked with other external IT service providers.
Hosting Service Providers need such agreements in order to manage customer expectations. They also need to define the situations under which they are liable and not liable for deviations from the expected performance. For the end-customer having a prepared SLA allows the services of one provider to be objectively compared with another.
A well written and legally comprehensive SLA may include as many as two dozen different heads. This covers Definitions and Interpretation, Term of Agreement, Service Provider’s Obligations, Client’s Obligations, Fees and Payment, Provision of the Hosting Services, Service Levels, Scheduled Downtime, Service and Performance Monitoring, Confidentiality, Intellectual Property Rights, Termination, Post-Termination, Liability and Indemnity, Nature of the Agreement, Severance, Relationship of the Parties, Notices, Law and Jurisdiction, etc.
Notwithstanding the above, a few of the more important clauses used in a Hosting Services Provider agreement appear below:

  • Services - This is a detailed description of the services that will be provided and the end-customer groups that will receive specific services.

  • Availability - This is a description of the uptime limits of a service. The service may also be described in terms of performance, business expectations and outcomes. The higher the availability requirement, the more expensive the service.

  • Downtime- This is a description of the situation when the service is not available, exclusions for responsibility and force majeure, and the process of rebate linked to established failure.

  • Response time- This is a description of the time to respond and rectify based on the nature of the failure or complaint.

  • Escalation - For an externally hosted service, especially when there are time zone differences, this description is the most important for rectification of a fault. Going through a help desk or call centre repeatedly may not ensure timely rectification of the fault.

  • Schedules for notification- This describes the lead time required to be provided when there are any planned shutdowns or disruptions in the service. Planned maintenance cycles are usually known well in advance and can be built into business outcomes.

  • Benchmarks - This is a description of the parameters used to gauge the upkeep of the SLA and the point of responsibility for producing, monitoring and escalating these benchmarks.

  • Help desk - This is a description of how the help desk will respond based on the nature of the complaint or fault and the end-customer flagging the complaint.

In conclusion, just because a Service Level Agreement exists, it does not mean that the service provider and the end-customer will meet each other's expectations. Leveraging the terms in the Service Level Agreement must be the means of last resort. There is much that can also be accomplished without resorting to it.


=