by: Alpha Serve
| Excerpt | ||
|---|---|---|
| ||
Effective Date: March 10, 2020
Document Owner: | Alpha Serve |
Versions
Version | Date | Description | Author |
|---|---|---|---|
1.0 | 17-01-2019 | Service Level Agreement | Anton Storozhuk |
2.0 | 10-03-2020 | Service Level Agreement 2.0 | Anton Storozhuk |
Table of Contents
...
...
...
...
...
...
...
Agreement Overview
This Agreement represents a Service Level Agreement (
...
SLA
...
or
...
Agreement
...
) between Alpha
...
Serve (Service Provider) and you, either as an individual or single entity (Customer)
...
for the provisioning of IT services required to support and sustain the product.
This Agreement remains valid until superseded by a revised agreement mutually endorsed by the stakeholders.
This Agreement outlines the parameters of all IT services covered, as they are mutually understood by the primary stakeholders. This Agreement does not supersede current processes and procedures unless explicitly stated herein.
...
Goals
...
and Objectives
...
The purpose of this Agreement is to ensure that the proper elements and commitments are in place to provide consistent IT service support and delivery to the Customer(s) by the Service Provider
...
.
...
The goal of this Agreement is to obtain mutual agreement for IT service provision between the Service Provider
...
and Customer(s).
...
The objectives of this Agreement are to:
...
Provide clear reference to service ownership, accountability, roles, and/or responsibilities.
...
Present a clear, concise, and measurable description of service provision to the customer.
...
Match perceptions of expected service provision with actual service support & delivery.
...
Stakeholders
The following Service Provider
...
and Customer(s) will be used as the basis of the Agreement and represent
...
the primary stakeholders associated with this SLA:
IT Service Provider
...
: Alpha Serve (
...
Provider
...
)
IT Customer(s): You (
...
Customer
...
)
...
Periodic Review
This Agreement is valid from
...
the Effective Date outlined herein and is valid until further notice. This Agreement should be reviewed at a minimum once per fiscal year; however, in lieu of a review during any period specified, the current Agreement will remain in effect.
...
The Business Relationship
...
Manager (
...
Document Owner
...
) is responsible for facilitating regular reviews of this document. Contents of this document may be amended as required, provided mutual agreement is obtained from the primary stakeholders and communicated to all affected parties. The Document Owner will incorporate all subsequent revisions and obtain mutual agreements/approvals as required.
Business Relationship Manager: Alpha Serve
Review Period:
...
Yearly (12 months)
Previous Review Date: March 10, 2020
Next Review Date: March 10, 2021
...
Service Agreement
The following detailed service parameters are the responsibility of the Service Provider in the ongoing support of this Agreement.
...
1. Service Scope
The following Services are covered by this Agreement for all products from the Service Provider portfolio
...
:
...
Monitored email support.
Monitored Jira Service Desk support.
Online configuration and Set-up support (upon request).
Manned telephone support for High priority issues within business
...
hours (
...
EEST time zone).
Remote assistance using Remote Desktop and a Virtual Private Network (where available
...
Planned or Emergency Onsite assistance (extra costs apply)
...
Monthly system health check
The following Services are covered by this Agreement for 2FA for Crowd: U2F & TOTP and U2F for Jira:
...
Monitored email support
...
Monitored Jira Service Desk support
...
Remote assistance using Remote Desktop and a Virtual Private Network where available
).
Other services may be available at extra cost.
...
Please contact Service Provider for more details.
...
2. Customer Requirements
...
Customer responsibilities and/or requirements in support of this Agreement include:
Payment for all support costs at the agreed interval.
Reasonable availability of customer
...
representatives when resolving a service-related incident or request.
...
3. Service Provider Requirements
Service
...
Provider responsibilities and/or requirements in support of this Agreement include:
Meeting response times associated with service-related incidents.
Appropriate notification to Customer for all scheduled maintenance.
...
4. Service Assumptions
Assumptions related to in-scope services and/or components include:
Changes to services will be communicated and documented to all stakeholders.
...
5.
...
Service Availability
Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services, and related components.
6.1. Service Availability
Coverage parameters specific to the service(s) covered in this Agreement are as follows:
Telephone support: 9:00 A.M. to 5:00 P.M. Monday – Friday (
...
EEST time zone).
Calls received out of office hours will be forwarded to a mobile phone and best efforts will be made to answer / action the call, however, there will be a backup answer phone service.
Email support: Monitored 9:00 A.M. to 5:00 P.M. Monday – Friday (
...
EEST time zone).
Emails received outside of office hours will be collected, however, no action can be guaranteed until the next working day.
Assistance guaranteed within 72 hours during the business week.
6.
...
Service Requests
In support of services outlined in this Agreement, the Service Provider will respond to service-related incidents and/or requests submitted by the Customer within the following time frames:
...
48 hours (during business hours) for issues classified
...
as High priority.
Within
...
72 hours for issues classified
...
as Medium priority.
Within 5 working days for issues classified
...
as Low priority.
Remote assistance will be provided in-line with the above timescales dependent on the priority of the support request.
...