Start with the structure of the three agreements
Before you assess the SLA, check how the documents fit together. The model consists of three agreements: a licence agreement with the producer, and a maintenance and an implementation agreement with the partner. Each has a different party and scope, so the clauses should neither duplicate nor contradict each other.
The producer licence agreement sets out the customer's right to use the system, the scope of the licences and the continuity guarantee, with no payment due to the producer. The licence does not depend on the duration of cooperation with the partner, so the partner's contract should contain no clause that makes the right to the system conditional on its services.
Scope and subscription in the maintenance contract
The partner's maintenance contract sets reaction and repair times, 99.5% availability and a monthly subscription with a choice of licence package and optional modules. Check whether the subscription names the licence package, options such as BLE transmitters or SMS, and how active users are counted.
An active user is an account with at least one login in the month, and guests, employees of external companies and drivers are not counted. If the draft counts users differently, ask for an explanation, because the difference directly changes the cost.
Sample repair times by fault category
Fault categories A, B and C
A sample SLA from the partner contract draft looks as follows: category A means reaction within 12 hours and repair within 8 hours, category B means reaction by the next day and repair within 1 day, category C means repair within 7 days. What matters most is that the contract clearly defines what counts as a fault A, B or C, because the deadlines depend on it.
Ask how faults are reported, during which hours reports are accepted and who classifies a fault. If only the partner classifies faults, add the customer's right to appeal the classification.
SLA parameters set in the contract
SLA parameters (availability, reaction and repair times) are set in the maintenance contract, for example 99.5% availability per month. For purchasing, the key point is that the contract clearly states the measurement method, the settlement period and how breaches are reported.
Availability and how it is measured
Availability of 99.5% on a monthly basis means total downtime should not exceed about 3.6 hours in a 30-day month (0.5% of 720 hours). Check whether the contract defines the measurement method, exclusions such as planned maintenance work, and the reporting method.
If the system runs in the customer's network, part of the outages may have causes on the customer's side. Record how responsibility is divided and name a shared point of contact.
Checklist
Video
Frequently asked questions
Where are SLA parameters set?
In the maintenance contract: availability, reaction and repair times, for example 99.5% availability per month.
How much downtime does 99.5% availability allow?
About 3.6 hours in a 30-day month. Check whether planned maintenance work is excluded from the measurement.
Who is responsible for a fault on the customer's network side?
The contract should divide this. It is good when it records a shared point of contact and how to show on which side the outage arose.
Let's review the contract draft together
Send the partner's maintenance contract draft. We will point out the clauses to clarify and compare them with the sample SLA.
Let's talk