SLA Service Level Agreement

Similar documents
Hosted Contact Centre (HCC) Customer Service Plan

Cloud Services Service Level Agreement. Publish Date: 30/06/14 Version: 1.2. Cloud Services Service Level Agreement Page: 1

Publish Date: 19/06/14 Version: 1.2. Internet Connectivity Service Level Agreement. Page: 1. Internet Connectivity Service Level

Schedule Document. Leased Lines & Ethernet Based Services. Node4 Limited 29/11/2007

SCHEDULE DOCUMENT HOSTED TELEPHONY PUBLIC NODE4 LIMITED 03/02/2014

Publish Date: 30/06/14 Version: 1.2

ICT Helpdesk. User Guide. 24 th May Page 1

All other issues are to be submitted via a request ticket utilizing the Web Helpdesk found at

INCIDENT MANAGEMENT SCHEDULE

Publish Date: 19/06/14 Version: 1.2. Call Recording/Logging Service Level Agreement. Page: 1. Call Recording/Logging Service Level

STANDARD SERVICE LEVEL AGREEMENT

ASIAN PACIFIC TELECOMMUNICATIONS PTY LTD STANDARD FORM OF AGREEMENT. Schedule 3 Support Services

Customer Support Handbook

Service Level Agreement and Management By: Harris Kern s Enterprise Computing Institute

The Hotchkiss School Information Technology Services. Service Level Agreement (SLA) with the Hotchkiss Community for Technology User Support

IT Department. Outsourced Solutions for your business. 1 (671)

ISL Development & Support Service Level Agreement (SLA) Infigo Software Limited (ISL)

How To Get A Support Ticket Resolved On Itech

Sheridan/Gillette College IT Help Desk Service Level Agreement

Bronze Silver Gold Telephone Support & Remote Yes 1 hour per month Yes 3 hours per Yes - 5 hours per month

IT Services. Service Level Agreement

CENG Information Technology Services University of North Texas

MDA CUSTOMER SERVICE HELP DESK FREQUENTLY ASKED QUESTIONS (FAQS)

Moodle & Totara Learning Management Systems Service Description G-Cloud 7

Mary Immaculate. ICT Services. ICT Helpdesk. User Guide

Users Guide to the ICT Service Desk

Service Description Document Control Service Description Documentation Approval Service Description Document Reviews

SAP Support Standards for Support Collaboration. Applicable SAP Support Standards for Support Collaboration with Software Solution Partners

For more information, please visit the IST Service Catalog at

Communicate: Data Service Level Agreement. Author: Service Date: October 13. Communicate: Data Service Level Agreementv1.

Fully Managed IT Support. Proactive Maintenance. Disaster Recovery. Remote Support. Service Desk. Call Centre. Fully Managed Services Guide July 2007

How To Use The Pace Help Desk

How To Use An Icc (Ucop) Service Catalog

Service Level Agreement Between: Computing and Informational Technology And The Finance and Business Operations Division

So we can deal with any issues you may face quickly and effectively, it is really important that you log them on your own helpdesk.

Contact / Escalation Guide. For OPENHIVE Managed Services provided by Capita. Version 6.0

ESXi Cluster Services - SLA

UCLA Information Technology Services, Call Center. IT Services Call Center Service Level Agreement. Effective Date: 07/14/11

[Type text] SERVICE CATALOGUE

Batesville Community School Corporation

RJmetis Support Pack

IT Help Desk Call Priorities

Dynamics CRM - Support Service Description

ACDI s Professional Support Services

Product Support and Maintenance Terms & Conditions

Cloud-based Managed Services for SAP. Service Catalogue

To provide an effective, professional and customer focussed ICT Service Desk service to the customers of the Council, NHS and all Hoople customers.

Link-Connect Service Level Agreement

Managed Security Services SLA Document. Response and Resolution Times

Enterprise UNIX Services - Systems Support - Extended

Systems Support - Standard

Service Specification. ICT Support 2014/2015

Get what s right for your business. Technologies.

Information Technology Services Core Services SLA

SERVICE CONTRACT. and

Helpdesk Incident & Request Management Procedure For

Technical Support Services

Customer Service Charter TEMPLATE. Customer Service Charter Version: 0.1 Issue date :

Helpdesk and Technology Support Procedures

Tilgin. Services Description Customer Support Portfolio

FULLY MANAGED SERVICE COMPLETE SUPPORT FOR YOUR MOBILE ENTERPRISE

SCHEDULE 1 SOFTWARE SUPPORT SERVICES AND SERVICE LEVELS

Automation Priority Support

2.1 To define the backup strategy for systems and data within the Cape Winelands District Municipality (CWDM).

GMS NETWORK ADVANCED WIRELESS SERVICE PRODUCT SPECIFICATION

Customer Service Plan Wholesale SIP Trunking. October 2014

Adlib Hosting - Service Level Agreement

Community Anchor Institution Service Level Agreement

SERVICE LEVEL AGREEMENT

cpouta - IaaS Cloud Computing Service Service Level Agreement

Contact / Escalation Guide. For OPENHIVE Managed Services provided by Capita. Version 3.0

University Systems Desktop Support Service Level Commitment

BridgeConnex Statement of Work Managed Network Services (MNS) & Network Monitoring Services (NMS)

Interoute Application Management comprises the following managed services for application and database software:

Salford BSF Managed Service Handbook

Information Services Department

How To Use Bbt (Bbt) For Business

HELP DESK SERVICE LEVEL EXPECTATIONS

Privia Support hours and methods

For FY 2016 the new Desktop Support Program rates will be: Business Class - $481/device Enterprise Class - $721/device

Excelsior Springs School District Technology Department Service Level Agreement

Managed IT Services. Maintain, manage and report

SUBJECT: Network Support Partnership Silver Support Level for FY 2013

Audit Management. service definition document

Statement of Service. Enterprise Services - WATCH MySQL Database. Customer. MANAGE Services for MySQL

McDonough School of Business: MSBTC SLA 2014

MSP Service Matrix. Servers

Service Level Agreement (SLA)

ICT HELPDESK PROCEDURES

Transcription:

SLA Service Level Agreement

Contents SLA Service Level Agreement 1 1. Objectives 3 2. Single Point of Contact 3 3. Reporting a fault 3 3.1. Fault reporting by customers 3 3.2. Fault reporting by an automated monitoring system 3 3.3. Prioritising the fault 4 3.4. Service business hours 4 4. Reply times 5 4.1. Response time 5 4.2. Intervention times 6 4.3. Restoration time 6 4.4. Completion of the fault resolution process 6 5. Target service availability 7 6. Reporting 7 7. Entry into force and amendments to the SLA 7 Annex: Service overview 8 A.1. Mission-critical services 8 A.2. Business-critical services 9 A.3. Standard services 10 A.4. Change control 11 Page 2 of 11

1. Objectives This Service Level Agreement (SLA) sets out the ICT services of in terms of fault reports and resolution. 2. Single Point of Contact The customer's single point of contact for ICT services at at all times is Customer Service Desk (ICT hotline) Internal 6 73 00 International +41 (0)43 816 73 00 Telephone business hours 24 x 7 E-mail E-mail business hours customerservicedesk@zurich-airport.com Daily 8 a.m. - 5 p.m. (incl. weekends and public holidays) 3. Reporting a fault Faults can be reported to the Customer Service Desk at any time by telephone and will be entered in the ticket system. Reports sent by e-mail will be processed according to the information in section 4.1. Critical faults should always be reported to the ICT by telephone to ensure that the guaranteed response times in section 4 can be upheld. The following processes do not apply to fault reports submitted to other hotline organisations, e.g. Service 24 or SITA Helpdesk. 3.1. Fault reporting by customers If a customer reports a fault to the Customer Service Desk the first step whenever possible is to attempt to troubleshoot the fault or remedy it directly on the telephone. In parallel, a service request is generated and activated. The following information is required for troubleshooting and remedying the fault: A description of the fault and the consequences Location of the faulty system or connection with clear official designation (e.g. computer name) Customer's full contact information in the event further clarification is required If further processing is required the service request will be sent on to the relevant support organisation. A contact person from the customer should remain contactable by means of this information until the fault has been remedied. 3.2. Fault reporting by an automated monitoring system If a monitoring system, for example a network management system, reports a fault, a service request is immediately generated and activated on the basis of this information. Fault reporting by an automated system is equivalent to fault reporting by a customer over the telephone for the purposes of the timeframes guaranteed in the SLA.

3.3. Prioritising the fault The Customer Service Desk prioritises the fault in accordance with the reported impairment according to the following system: Classification Severity Description Priority 1 Priority 2 Outage or critical fault Average impairment The customer is unable to use the service (e.g. application). For technical reasons it is not possible to switch to other equipment. The customer is unable to perform key tasks. The customer can use the service (e.g. application) only to a limited extent. The problem can be mitigated by using different terminals. Priority 3 Minor impairment Operation of the customer's systems is impaired to only a minor degree. Overall the service (e.g. application) can still be used by the customer. 3.4. Service business hours The service business hours describe the time windows within which faults are processed by the support organisation. The three service times "bronze", "silver" and "gold" correspond to the three levels of support hours. Support hours designate the times during which the support organisation works to resolve problems. Zeit Mo Di Mi Do Fr Sa So 00:00 01:00 02:00 03:00 04:00 05:00 06:00 07:00 08:00 09:00 10:00 11:00 12:00 13:00 14:00 15:00 16:00 17:00 18:00 19:00 20:00 21:00 22:00 23:00 Bronze ( Bürozeit) Bronze Montag (office bis Freitag hours) 08:00Uhr bis 17:00Uhr ohne Monday gesetzliche to Friday Feiertage 8 a.m. to 5 p.m. excl. public holidays Silver Silber (airport ( Flughafen-Betriebszeit) operating hours) Montag bis Sonntag 05:00Uhr bis 23:00Uhr Monday to Friday 5 a.m. to 11 p.m. Gold (7x24) Gold (7x24) Montag bis Sonntag 00:00Uhr bis 24:00Uhr Monday to Friday 24 hours/day

4. Reply times The following reply times apply within the fault rectification process. Prozess zur Störungsbehebung Betriebszeit 7x24h Wiederherstellungszeit Reaktionszeit Interventionszeit Störungsbehebung Regulärer Service Beeinträchtigter Service Regulärer Service Automatische Sörungsmeldung oder Störungsmeldung durch Kunde Reaktion = Eröffnung des Trouble Tickets Intervention = Beginn Störungsbehebung durch Techniker Störung behoben 4.1. Response time The response time measures the time between the fault being reported by the customer to the Customer Service Desk and successful entry of the report in a ticket system. The customer receives a confirmation e- mail (provided an e-mail address was supplied) with the description of the reported and entered fault. The maximum response time is guaranteed as part of the Service Level Agreement and is defined as follows. Response time Daytime Daily 8 a.m. 5 p.m. Extended to include Zurich Airport's operating hours Daily from 5 a.m. 8 p.m. Daily from 5 p.m. 11 p.m. Extended to include nighttime hours (7 x 24h) Daily 11 p.m. 5 a.m. Telephone report 15 minutes 15 minutes 30 minutes Report by e-mail 4 hours Daily between 8 a.m. 5 p.m. within 4 hours Daily between 8 a.m. 5 p.m. within 4 hours

4.2. Intervention times Intervention time measures the length of time between the recording of the fault report in the ticket system and the expert, effective remote or on-site intervention of a service technician for the purpose of remedying the fault. The maximum intervention time is guaranteed taking the customer's service hours (section 3.4) into account and is defined as follows. Intervention times Mission-critical services 1 Business-critical services 1 Standard services Mon - Fri. 8 a.m. 5 p.m. Other hours Mon - Fri. 8 a.m. 5 p.m. Other hours Mon - Fri. 8 a.m. 5 p.m. Other hours Priority 1 15 minutes 30 minutes 30 minutes 60 minutes 2 hours 4 hours Priority 2 30 minutes 60 minutes 60 minutes 120 minutes 4 hours 8 hours Priority 3 8 hours 8 hours 16 hours 4.3. Restoration time The restoration time commences when a fault report is received and ends when functionality has been restored. Functionality is deemed to have been restored when the connected systems are able to operate and the service is available again. The restoration time cannot be guaranteed. The support organisation attempts, following an initial analysis, to make a qualified statement about the expected restoration time. 4.4. Completion of the fault resolution process The successful resolution of a fault is documented in the service request. Once this has been entered, the fault resolution process is complete. The resolution of the fault is reported to the customer. The customer can enquire at the Customer Service Desk at any time regarding the status of the fault resolution or provide feedback about the fault resolution, quoting the service request number. 1 The service levels are set out in the Annex. Mission-critical = direct impact on flight operations Business-critical = direct impact on airport operations

5. Target service availability Unless any special conditions are stipulated, all systems can be used 24 hours a day on all days of the week. The defined maintenance windows are the only exception. The respective target service availability of the core infrastructure 2 is measured in an annual time window and excludes scheduled maintenance windows. Service availability Gold Silver Bronze Mission-critical 99.9% 99.7% 99.5% Business-critical 99.7% 99.5% 99.3% Standard n/a n/a n/a 6. Reporting The quality of the services is set out in a periodic report and can be requested at the Customer Service Desk. 7. Entry into force and amendments to the SLA This SLA comes into force on 1 January 2014. Amendments to the SLA may be made by at any time. Customers must be informed of these in writing. 2 Core infrastructure is understood to mean the central server infrastructures, network connections, server applications, databases, interfaces and connections to third parties. Core infrastructure does not include terminals such as desktops, mobile devices, printers, microphones, etc.

Annex: Service overview A.1. Mission-critical services AIMS Alarmstern BRTS Trunked radio CUTE Darts EAI GSA IT IP-MPLS network PVIS Sally ZUKO

A.2. Business-critical services Operating WLAN (Outdoor & indoor) Byron CUSS CUT Long-term parking application (DPA) Document Management System (DMS) Exos locking technology FEV routing systems FIDS GAVS / BKK Intercom Customer workplace infrastructure (incl. VDI) PAMOS Parking Skidata Car park routing system (PLS) PWS RTC FZAG SAP Telephony Video

A.3. Standard services Unless explicitly stated, all services are standard services with the bronze support level.

A.4. Change control Version Date Name Comments 1.1 28.01.2014 Fabio Morandi Layout amendments Publication details Author: Division/Department: ICT Shared Services Services / ICT