Support Services SLA
Last updated: December 19, 2016
This Service Level Agreement is subject to the terms and conditions of Client’s Elasity Subscription Agreement (the “Agreement”), and does not become operative until Client has signed off and is live on the Elasity production environment. For clarity, this Service Level Agreement applies only to “live” environments.
The iTMethods Service Desk will provide 7x24x365 support for Client Elasity Services for:
- First line response for all pro-active monitoring and alerts
- Respond to tickets opened by Client Administrators as a result of inbound calls/requests/emails.
- Outbound calls to Client Administrators will be based on the notification and escalation procedures defined during the Service Desk Onboarding process.
- The existing process for Incident Management will be reviewed to identify any additional Client support group responsibilities relating to ticket generation, updates and closures.
An Incident is as an unplanned interruption to or quality reduction of the Elasity Service. The Incident response process is delivered on a number of levels:
Level 1 – Troubleshooting & Diagnostics
Incidents will be discovered through a variety of means including monitoring system alarming and inbound calls. The Client will report Priority 1 outages via phone call to +1 416-849-3474. iTMethods engineers will respond and create a ticket, and will respond according to the priority matrix. iTMethods will follow support flows to help determine the cause of the incident. Investigation includes but is not limited to:
- Scope as to which AWS infrastructure services, Atlassian application(s) and databases are affected.
- Troubleshooting & diagnostics actions to determine cause of the Incident.
- Identify support procedures to be followed for resolution.
Level 2/3 – Service Restoration / Vendor Escalation / Client Escalation
Incidents are resolved via standard Problem Management processes and accordance with the assigned Incident Priority Level.
iTMethods will complete all fixes within the specified Mean Time To Repair (MTTR) period with the following provisions:
- Overall service restoration is dependent upon AWS service availability within the target Region(s) / Availability Zone(s).
- iTMethods will effect service restoration once any fully dependent AWS Support tickets have been resolved.
- If troubleshooting actions determine the cause of the Incident lies within client-managed application code / Atlassian add-on configuration(s), iTMethods will effect service restoration once the system configuration has been rolled back to the last known working environment or the client development team successfully deploys new customizations to the production environment.
If the out-of-service condition is a result of failures outside the scope of services (Distributed Denial of Service attack, customer-initiated emergency application maintenance, widespread internet outage etc.) iTMethods’ SLA will not be applicable.
Service Levels – Priority Matrix
Incident Priority Levels are assigned and agreed upon by iTMethods and Client when the issue is reported to the iTMethods Service Desk. Client may assign a specific Priority Level through a telephone call to the Service Desk. All email requests are assigned a Priority 3 service level priority. For Priority 1 service level support requests, Client must submit the request through iTMethods’ Service Desk line. This applies to all hours of the day. Email requests will not receive Priority 1 service level priority.
Service Requests – Service requests such as requests for Atlassian configuration changes etc. are not assigned Priority Levels. These requests are handled through the normal Change Management processes.
Priority Response Time – Restoration target means a workaround or temporary circumvention to bring the service back up. Response time will follow any underlying agreements with third party companies that provide iTMethods service (such as AWS) or product (such as Atlassian).
|Priority 1 incidents will receive top priority support and continuous effort until the incident is resolved or no longer in a critical condition.
|1 hour thereafter
4 hours thereafter
|Priority 2 incidents will receive high priority support and continuous effort throughout the iTMethods normal hours.
|2 hours thereafter
8 hours thereafter
|Priority 3 incidents will receive normal priority support and continuous effort throughout the iTMethods normal business hours.
|4 business hours
|1 business day
|2 business days
|5 business days
|Priority 4 includes low impact and medium/low urgency incidents and will receive normal priority support and continuous effort throughout the iTMethods normal business hours.
|1 business day
|2 business days
|3 business days
Figure 1 Incident Response Priority Matrix