News

Service Level Agreement (SLA): What You Need to Know

October 18, 20184 min read
Service Level Agreement (SLA): What You Need to Know

A service level agreement (SLA) is a way of defining the scope of the services provided and the terms on which they are delivered, agreeing in advance which indicators will be used to measure service delivery, what action will be taken in the event of disruptions and how they will be resolved. An SLA is one of the essential components of any technology services agreement.

“We get a lot of questions about SLAs and we notice there is plenty of uncertainty in the market: what an SLA is, why it matters to an organisation, and why it is essential to clarify the organisation’s needs before talking to IT service providers. We want to clear up this fog,” said Dominykas Palšis, Cloud Services Sales Manager.

In this article we answer some of the main and most frequently asked questions about service level agreements.

Why should an organisation care about a service level agreement?

In most cases, an SLA goes hand in hand with a technology services contract. It clearly documents the services provided and the agreed and expected reliability of service delivery. The agreement sets out the metrics, responsibilities and expectations on which the services will be based, so that all parties named in it understand the terms of service delivery in the same way.

How do you determine the right SLA?

“Ideally, an SLA should reflect the organisation’s goals and how it uses technology. The client should assess what impact technology disruptions have on the organisation – perhaps an hour of downtime will inflate production costs or seriously affect customer satisfaction, or perhaps the disruption will not hinder normal work at all,” Dominykas advised.

Technology service providers usually have a standard SLA, or several of them – a great starting point for negotiations. Once the client states the tolerable period of disruption, the provider will propose the solution that best meets their expectations.

Of course, a very strict SLA with instant response to incidents will also affect the price of the services. And if uninterrupted operation is important to the client, additional technology solutions may be needed – for example, duplicating the servers where data is stored, preparing a disaster recovery plan or choosing other solutions that help ensure work without disruptions.

What are the components of an SLA?

An SLA should cover two sides of service delivery: the service components and their management. The service part usually details the services provided, service availability and terms of use, response and resolution times during and outside business hours, each party’s responsibilities and the ways incidents are communicated.

The service management part usually covers the methods for measuring service reliability, reporting (its content and frequency), the dispute resolution procedure, compensation for damages and the procedures for updating the SLA.

Which SLA metrics should you choose and track?

“There are no universal metrics – they should be set according to the type of services provided. It is important to stress that you can measure a great deal against agreed indicators, but the list of measured indicators should be justified, genuinely necessary and as simple as possible, so that neither you nor the provider gets lost and tracking does not incur unreasonably high costs,” advised Dominykas Palšis.

In practice, the most common indicator is service availability, measured as a percentage of time – for example, 99.9% means that services may be unavailable or degraded for 0.1% of the time. Another indicator is the number of errors, counting incomplete work, missed deadlines and other types of errors. IT infrastructure management is also increasingly being measured as part of overall business performance – arguably the best approach, provided the service provider has enough influence.

A service level agreement makes services easier to deliver and receive

Negotiating a service level agreement can take time and become a long process before services begin, especially where needs are non-standard, but its benefits are indisputable – without it, the provider and the client can become entangled in endless disputes that would fundamentally hinder effective cooperation.

It is also important to remember that the work does not end when the agreement is signed. To reflect the client’s needs and the provider’s capabilities as closely as possible, an SLA should be reviewed periodically, taking into account changes in the environment, the nature of the business and other factors.

Dominykas Palšis is a Cloud Services Sales Manager with a strong understanding of both technical and business processes who can suggest the most suitable cloud computing solution for your organisation. Contact Dominykas by email at dominykas.palsis@skaylink.lt or by phone on [+370 610 11180](tel:+37061011180).

Get in touch

Let's talk about your IT

Tell us what matters to you – we will suggest a solution and reply within one business day.

  • A Vodafone Group company, 20 years in Lithuania
  • 100+ IT and Cloud specialists in Vilnius, Kaunas, Klaipėda and Šiauliai
  • 24/7 IT support: +370 5 203 4380
Book a 30-min call →
Skaylink
Privacy Policy

We use cookies on this website to ensure smooth website performance and improve your browsing experience. Cookies help us save your preferences, recognize returning visitors, and analyze which parts of the website are most relevant to you.

Privacy Policy