SERVICE LEVEL AGREEMENTService Level Agreement • December 15th, 2023
Issue Date Comment Author v0.1 20/03/2020 Initial SLA draft Enol Fernández v0.2 13/05/2020 Extended SLA with the CETA-GRID OLA Giuseppe La Rocca v0.3 05/05/2021 Extended agreement with the Customer Giuseppe La Rocca v0.4 21/06/2021 Move resources from IISAS-GPUCloud to IISAS-FedCloud. Giuseppe La Rocca
ANDService Level Agreement • February 9th, 2004 • Perusahaan Perseroan Persero Pt Telekomunikasi Indonesia TBK • Telephone communications (no radiotelephone)
SERVICE LEVEL AGREEMENTService Level Agreement • June 12th, 2018
The purpose of this Service Level Agreement (SLA) is to describe the key services to be provided and the quality standards we have agreed in terms of service delivery.
SERVICE LEVEL AGREEMENTService Level Agreement • February 12th, 2024
Issue Date Comment Author FINAL 21/05/2019 SLA agreed with the Customer. Giuseppe La RoccaMałgorzata Krakowian v0.1 29/10/2019 Increased the GB of RAM of the VM hosting theSOS web service Giuseppe La Rocca v0.2 17/01/2020 Extended agreement with the Customer till05/2021 Giuseppe La Rocca v0.3 11/06/2021 Extended the agreement with the Customer till05/2022. Added The EGI-AAI Check-In service Giuseppe La RoccaValeria Ardizzone v0.4 20/12/2021 Changed Component Provider. Sebastian Luna-Valero v0.5 01/12/2022 Extended agreement till 30/2023 Sebastian Luna-Valero
Big Kirk Hallam c/o Kirk Hallam Community Academy Godfrey Drive, Kirk Hallam, Ilkeston, Derbyshire DE7 4HH Email: Su.BigKH@aol.comService Level Agreement • November 21st, 2023
The purpose of this Service Level Agreement (SLA) is to describe the key services to be provided and the quality standards we have agreed in terms of service delivery.
SERVICE LEVEL AGREEMENTService Level Agreement • August 17th, 2023
Customer GEO-DAB/vo.geoss.eu Service Provider EGI Foundation First day of service delivery 01/12/2018 Last day of service delivery 01/12/2021 Status FINAL Agreement finalization date 17/12/2018 SLA link https://documents.egi.eu/document/3406 OLA Link https://documents.egi.eu/document/3406
SERVICE LEVEL AGREEMENTService Level Agreement • April 19th, 2022
This Service Level Agreement (this “SLA”) between NEC Cloud Communications America, Inc. or the reseller of Services from which the applicable Service has been purchased (“Company”) and the customer entity purchasing any of the Services (as defined below) (“You”) governs the use of the Cloud Voice Services under the terms of the Master Service Agreement (the “MSA”) between Company and customer (“You”) and the relevant product Schedules between Company and You and is incorporated into the MSA by reference. This SLA applies separately to each of Your Accounts and only if You receive the relevant Cloud Voice Services pursuant to an applicable product Schedule. Company may update, amend, modify or supplement this SLA from time to time. Capitalized terms used herein but not otherwise defined will have their respective meanings set forth in the MSA. In the event of any conflict between this SLA and the MSA, the MSA will govern.
SERVICE LEVEL AGREEMENT TO ENABLE COMMUNITY PHARMACISTS IN SHEFFIELD CLINICAL COMMISSIONING GROUP TO SUPPLY NICOTINE REPLACEMENT THERAPY AND VARENICLINE TO CLIENTS OF SHEFFIELD SMOKE FREE SERVICEService Level Agreement • August 28th, 2020
PREPARED BY: Sheffield Smoke Free Service (soon to be called Yorkshire Smokefree (Sheffield) on behalf of The South West Yorkshire Partnership NHS Foundation Trust
SERVICE LEVEL AGREEMENTService Level Agreement • August 3rd, 2021 • England and Wales
(1)The Service Provider is engaged in the business of providing services in relation to the healthcare sector and has reasonable skill, knowledge, qualifications and experience in that field.
NAVER CLOUD PLATFORM VOD Station Service Level AgreementService Level Agreement • February 10th, 2020
This VOD Station Service Level Agreement (this “SLA”) applies separately to each account using the VOD Station Service (the “Service”). This SLA forms a part of the Service Terms and Conditions and the matters not stipulated herein shall be subject to the Service Terms and Conditions, and in the event of a conflict between the terms of this SLA and the terms of the Service Terms and Conditions, the terms and conditions of this SLA shall apply, but only to the extent of such conflict.
AGREEMENT FOR THE PROVISION OF SUPPORT SERVICESService Level Agreement • January 14th, 2021
THIS AGREEMENT is made the [27th] of [January] two thousand and twenty one BETWEEN DURHAM COUNTY COUNCIL (“the Council”) and CENTRAL DURHAM
SERVICE LEVEL AGREEMENT FOR PRIVATE CLOUD EDITION SERVICES AND TAILORED OPTION SERVICESService Level Agreement • February 17th, 2023
This Service Level Agreement for RISE with SAP S/4HANA Cloud, private edition (formerly, SAP S/4HANA, private cloud edition); SAP ERP, private cloud edition (collectively, “Private Cloud Edition Services”); RISE with SAP S/4HANA Cloud, private edition, tailored option; and SAP ERP, private cloud edition, tailored option (collectively, “Tailored Option Services”) (each, a “Cloud Service”) sets forth the applicable Service Levels for Private Cloud Edition Services, Tailored Option Services, and Server Provisioning to which Customer has subscribed in an Order Form with SAP.
AGREEMENT FOR THE PROVISION OF SUPPORT SERVICESService Level Agreement • January 20th, 2020
THIS AGREEMENT is made the [28th] of [January] two thousand and twenty BETWEEN DURHAM COUNTY COUNCIL (“the Council”) and MOUNTSETT
Service Level Agreement for University FacilitiesService Level Agreement • October 13th, 2021
• Services and Funding Sources exhibit, which identifies the baseline services that will be funded by the fiscal year 2022 facilities management cost allocation, and those agreed upon optional services that, if requested by customers, will be charged back to their organizations;
SERVICE LEVEL AGREEMENT FOR PRIVATE CLOUD EDITION SERVICES, TAILORED OPTION SERVICES, EX SERVICES, HEC SERVICESService Level Agreement • August 11th, 2022
This Service Level Agreement for SAP HANA Enterprise Cloud services (“HEC Services”); RISE with SAP S/4HANA Cloud, private edition (formerly, SAP S/4HANA, private cloud edition); SAP ERP, private cloud edition (collectively, “Private Cloud Edition Services”); SAP S/4HANA Cloud, extended edition which was previously known as S/4HANA Cloud, single tenant edition (“EX Services”); RISE with SAP S/4HANA Cloud, private edition, tailored option; and SAP ERP, private cloud edition, tailored option (collectively, “Tailored Option Services”) (each, a “Cloud Service”) sets forth the applicable Service Levels for HEC Services, Private Cloud Edition Services, EX Services, Tailored Option Services, and Server Provisioning to which Customer has subscribed in an Order Form with SAP.
SERVICE LEVEL AGREEMENTService Level Agreement • January 12th, 2024
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
SERVICE LEVEL AGREEMENT FORService Level Agreement • March 18th, 2021
This Service Level Agreement for SAP HANA Enterprise Cloud services (“HEC Services”); RISE with SAP S/4HANA Cloud, private edition; SAP S/4HANA, private cloud edition; SAP ERP, private cloud edition (collectively, “Private Cloud Edition Services”); and SAP S/4HANA Cloud, extended edition which was previously known as S/4HANA Cloud, single tenant edition (“EX Services”) (each, a “Cloud Service”) sets forth the applicable Service Levels for the HEC Services, Private Cloud Edition Services, EX Services and Server Provisioning to which Customer has subscribed in an Order Form with SAP.
OFFICIALService Level Agreement • August 2nd, 2022
P1.1 Tables 11.2, 11.3 and 11.6 populated following the release of figures. Wording changed throughout to make the document compliant with ORA. 09-01-15
Service Level Agreement (SLA) forService Level Agreement • July 21st, 2023
PUBLICATION 1 SERVICE LEVEL AGREEMENT FOR BUSINESS VPN SERVICEService Level Agreement • January 22nd, 2020
SERVICE LEVEL AGREEMENT (SLA 2)Service Level Agreement • April 10th, 2014
This Service Level Agreement (“SLA”) shall apply to all services, where it was ordered and where its delivery has been confirmed by the signature of the product specification (service contract). This agreement is valid for the whole duration of the service operation. Dial Telecom is not obliged in accordance with the Czech law number 172/2005 Sb. and its amendments to cover the loss caused by the service interruption or fault.
SERVICE LEVEL AGREEMENT BETWEEN NHS England London-‐RegionService Level Agreement • February 1st, 2022
NEC UNIVERGE BLUE® SHAREService Level Agreement • February 2nd, 2021
This Service Level Agreement (this “SLA”) governs the use of the NEC UNIVERGE BLUE® SHARE service under the terms of the Master Service Agreement (the “MSA”) between NEC Australia Pty Ltd or the reseller of Services from which the applicable Service has been purchased (“Company”) and customer ( “ You”) and is incorporated into the MSA by reference. This SLA applies separately to each of Your Accounts. Company may update, amend, modify or supplement this SLA from time to time. The terms and conditions of this SLA are applicable to the SHARE service only, and “Service” or “Services” as used in this SLA refers only to the SHARE service.
Service Level Agreement (SLA) for the Maintenance of Generators & UPS including Electrical WorksService Level Agreement • July 6th, 2022
ContractService Level Agreement • August 10th, 2018
This Service Level Agreement (“SLA”) sets forth the specific terms and conditions under which LightEdge Solutions, Inc. (“LightEdge”) shall supply all Services to Customer. The Master Service Agreement entered into between LightEdge and Customer fully incorporates the terms herein and provides that this Service Level Agreement, and Customer’s execution of the Master Service Agreement (“MSA”) constitutes acceptance of the terms and conditions stated herein. Capitalized terms used but not defined herein shall have the meanings set forth in the Master Service Agreement.
Service Level AgreementService Level Agreement • May 20th, 2022
State Bank of India, a statutory body constituted under the State Bank of India Act, 1955 having its Corporate Centre at State Bank Bhavan, Madame Cama Road, Nariman Point, Mumbai-21, through its Marketing & Communication Department hereinafter referred to as “the Bank/SBI/Client” which expression shall, unless it be repugnant to the context or meaning thereof, be deemed to mean and include its successors in title and assigns of the First Part:
Service Level Agreement (SLA) Office of Technology ServicesService Level Agreement • November 25th, 2015
SERVICE LEVEL AGREEMENTService Level Agreement • March 9th, 2020
The Service Level Agreement (“SLA”) describes the current practices of the Company with regard to its provision of Support to customers that have entered into an agreement for the software Tricentis Tosca (“Tosca”) and/or for the platform service Tricentis qTest (“qTest”) and/or for the software Tricentis RPA (“RPA”) and/or for the software Tricentis LiveCompare. In this Service Level Agreement, Tricentis Tosca, qTest, RPA, and LiveCompare will be referred to as “Tricentis Products” if the described terms are applicable for all products. Capitalized terms used but not defined herein shall have the meaning ascribed to them in the agreement between the Customer and the Company.
MASTER SERVICE AGREEMENTService Level Agreement • April 25th, 2013 • Quebec
PLEASE READ VERY CAREFULLY THESE TERMS AND CONDITIONS BEFORE USING SHERWEB’S SERVICES. IF YOU DO NOT ACCEPT THESE TERMS AND CONDITIONS, PLEASE CLOSE YOUR BROWSER AND DO NOT PROCEED WITH ORDERING OR USING THE SERVICES.
SERVICE LEVEL AGREEMENTService Level Agreement • July 3rd, 2023
Table of Contents 2 Glossary 3 1.0 Scope 4-5 1.1 Parties to the Agreement 1.2 Products and Services 1.3 Resource Assumptions 1.4 Contacts 1.5 Renegotiations 2.0 Service Details 5-7 2.1 Service Categories 2.2 Service Delivery Expectations 2.3 Dispute Resolution and Escalation 2.4 Funding and Responsibilities 2.5 Service Hours
SERVICE LEVEL AGREEMENT FOR SAP HANA ENTERPRISE CLOUD ANDService Level Agreement • April 28th, 2020
This Service Level Agreement for SAP HANA Enterprise Cloud services (“HEC Services”) and SAP S/4HANA Cloud, extended edition services, previously known as S/4HANA Cloud, single tenant edition, (“EX Services”) (“EX Services”) (each, a “Cloud Service”) sets forth the applicable Service Levels for the HEC Services, EX Services, and Server Provisioning to which Customer has subscribed in an Order Form with SAP.
SERVICE LEVEL AGREEMENTService Level Agreement • May 23rd, 2019
ContractService Level Agreement • March 19th, 2020
This Service Level Agreement (“SLA”) is subject to the terms and conditions of the applicable Agreement between First Communications and Customer regarding Essential T1 Service (for purposes of this SLA only, “Service”). Defined and/or capitalized terms used herein and not otherwise defined shall have the meanings given to them in the Company’s Terms and Conditions of Business Services posted on the www.firstcomm.com website.
SERVICE LEVEL AGREEMENTService Level Agreement • June 21st, 2019
The Service Level Agreement (“SLA”) describes the current practices of Company with regard to its provision of Support to customers that have entered into an agreement for the software Tricentis Tosca (“Tosca”) and/or for the platform service Tricentis qTest (“qTest”) and/or for the software Tricentis RPA (“RPA”) and/or for the software Tricentis LiveCompare. In this Service Level Agreement, Tricentis Tosca, qTest, RPA, LiveCompare will be referred to as “Tricentis Products” if the described terms are applicable for all products. Capitalized terms used but not defined herein shall have the meaning ascribed to them in the agreement between Customer and Company.
EGI VO SERVICE LEVEL AGREEMENTService Level Agreement • November 24th, 2015
For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
