SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement.

Slides:



Advertisements
Similar presentations
1 CLIENT CONSULTANT AGREEMENT. 2 Negotiations Types of Consulting Contracts Standard Form of Contract Form of Contract General Conditions Special Conditions.
Advertisements

Ch-2 Proposals and Contracts. Introduction Many issues have to be handled in a contract and a proposal including legal concerns, commercial arrangements.
OMB Circular A133 Audits of States, Local Governments, and Non-Profit Organizations 1 Departmental Research Administrators Training Track.
Topics Changes Risk Assessments Cloud Data Security / Data Protection Licenses, Copies, Instances Limits of Liability and Indemnification Requests for.
Issue Identification, Tracking, Escalation, and Resolution.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Chapter 3 Project Initiation
Network Design and Implementation
Intro Matt Reeves – FirsTech Lyle Wolinsky – Global Express Stella Pulliam – Sempra Utilities Kim Folks – Tampa Electric Guidelines for a Successful RFP.
2 Breakout Session # 1411 Robert F. Watts, Senior Consultant, ESI International Date: April 16 Time: 2:40 – 3:40 PM Buying Results Through Service Level.
Management of IT Environment (5) LS 2012/ Martin Sarnovský Department of Cybernetics and AI, FEI TU Košice ITIL:Service Design IT Services Management.
Copyright © 2006, BMC Software, Inc. All rights reserved. Unit 8 – Service Level Management ITIL Foundation – Concepts of IT Service Management (ITSM)
Yale University Information Technology Services Administrative Systems Art Hunt 3/22/04 Software Service Level Agreement with Finance, Procurement and.
Service Level Agreements
Chapter 5 IT Processes Presented by Dr. Mohamed Sammouda.
Managing the Information Technology Resource Jerry N. Luftman
IS Audit Function Knowledge
Date: 03/05/2007 Vendor Management and Metrics. 2 A.T. Kearney X/mm.yyyy/00000 AT Kearney’s IT/Telecom Vendor Facts IT/Telecom service, software and equipment.
1 CDBG Procurement Requirements For Local Officials.
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
SAS 112: The New Auditing Standard Jim Corkill Controller Accounting Services & Controls.
Viktorija Donceva Trajkovski & Partners Management Consulting Ohrid, May 2009.
Vendor Risk: Effective Management is Essential
SERVICE LEVEL AGREEMENTS Bob Goldberg 312/
© 2010 Plexent – All rights reserved. 1 Change –The addition, modification or removal of approved, supported or baselined CIs Request for Change –Record.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Introduction to Software Quality Assurance (SQA)
Customer Service Enforcement After AB 2987 John Risk Communications Support Group, Inc. (c) 2006 John Risk Communications Support Group, Inc. (c) 2006.
1 INTERREG IIIB “ATLANTIC AREA” Main points of community regulation 438/2001 financial management and control systems EUROPEAN COMMISSION SPAIN.
Erica Cummings Grant Coordinator 1.  The New Mexico Department of Homeland Security and Emergency Management (DHSEM) is responsible for:  Monitoring.
INTERNAL CONTROL OVER FINANCIAL REPORTING
Roles and Responsibilities
Foundations of Effective Board Operation Nicole L. Mace Vermont School Boards Association.
Kathy Alexander, Ph.D. Technical Specialist Water Availability Division Texas Commission on Environmental Quality.
Service Transition & Planning Service Validation & Testing
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Reasonable is in Eye of the Beholder Vendor, Customer, & Litigator Perspectives on Software License Provisions Aaron Brodsky Greg Leibold Peter Gergely.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
Audit and Audit Resolution Presented by Wendy Spivey ADECA Audit Manager.
1 Chapter Nine Conducting the IT Audit Lecture Outline Audit Standards IT Audit Life Cycle Four Main Types of IT Audits Using COBIT to Perform an Audit.
WSSB Capacity Enhancement Workshops The Uganda Performance Contract & Purpose 2. Performance Key Elements 3. Water Board’s Rights & Obligations.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin 6-1 Chapter Six Internal Control in a Financial Statement Audit.
Click on Next to continue Next Introductio n Inputs Tools and Techniques Outputs The process of managing procurement relationships, monitoring contract.
Grid Operations Centre LCG SLAs and Site Audits Trevor Daniels, John Gordon GDB 8 Mar 2004.
1 Kingsley Karunaratne, Department of Accounting, University of Sri Jayewardenepura, Colombo - Sri Lanka Practice Management.
Software as a Service (SaaS) Quality Management and Service Level Agreement INFuture2015: e-Institutions – Openness, Accessibility, and Preservation, Zagreb,
Listen. Plan. Deliver. Project Delivery Summit – A Necessary Evil, and Why they are important… December 9, 2015 Project Delivery Summit Service.
State of Georgia Release Management Training
Quality Assurance. Define Quality (product & service) Exceeds the requirements of the customer. General excellence of standard or level. A product which.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
ISO 9001:2015 Subject: Quality Management System Clause 8 - Operation
COTS Software Licensing Service Level Agreement Considerations 2014.
1 AaS 7.1: Understanding SLAs, SLEs, and Provider Managed Metrics Matthew E. Porter Contegix.
Improving Compliance with ISAs Presenters: Al Johnson & Pat Hayle.
Service Design.
Service Level Agreement Considerations
Chapter 6 Internal Control in a Financial Statement Audit McGraw-Hill/IrwinCopyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved.
A LOOK AT AMENDMENTS TO ISO/IEC (1999) Presented at NCSLI Conference Washington DC August 11, 2005 by Roxanne Robinson.
Contracting for the Cloud
Understanding The Cloud
VENDOR ON-BOARDING PROCESS
12.3 Control Procurements The process of managing procurement relationships, monitoring contract performance and making changes or corrections as needed.
Auditing Cloud Services
Service Organization Control (SOC)
ITIL:Service Design IT Services Management Martin Sarnovský
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
NEW SBA Form 159 Notice (a) & 504
Presentation transcript:

SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement

VENDOR ON-BOARDING PROCESS RFP (Request for Proposal) Due Diligence/Risk Assessment Vendor Selection Contract Review Service Level Agreement Contract Negotiation Contract Execution Ongoing Vendor Administration/Oversight

SERVICE LEVEL AGREEMENTS OVERVIEW Definition Purpose Key Requirements Exceptions Review

WHAT IS A SERVICE LEVEL AGREEMENT? A service level agreement (“SLA”) is a formal document describing the level of service a customer expects from a service provider.

EXAMPLES “Vendor shall provide the services set forth in Addendum 1.” WRONG! “Vendor shall provide the services set forth in the Service Level Agreement, attached hereto and incorporated herein as Addendum 1. (“Services”)” CORRECT!

PURPOSE OF AN SLA An SLA is intended to specify performance expectations, responsibilities and metrics. It ensures all parties have the same understanding of and improves each parties ability to reach intended goals.

KEY REQUIREMENTS Services and Objectives Performance Requirements and Responsibilities Performance Metrics and Measurement Accountability

SERVICES AND OBJECTIVES Services: Clear statements setting forth the specific service(s) vendor agrees to provide. Objectives: The intended outcome or goal of the service(s). (What do you want the service to achieve?)

EXAMPLE This Amazon S3 Service Level Agreement (“SLA”) is a policy governing the use of Amazon Simple Storage Service (“Amazon S3”) under the terms of the Amazon Web Services Customer Agreement (the “AWS Agreement”) between Amazon Web Services, Inc. (“AWS”, “us” or “we”) and users of AWS’ services (“you”). This SLA applies separately to each account using Amazon S3. Unless otherwise provided herein, this SLA is subject to the terms of the AWS Agreement and capitalized terms will have the meaning specified in the AWS Agreement. We reserve the right to change the terms of this SLA in accordance with the AWS Agreement.

PERFORMANCE AND DELIVERY REQUIREMENTS Responsibilities of: – all parties (including third party vendors) – service users Contract duration, locations and service times Additional fees and conditions Compliance: – federal and state laws and regulations – internal policies and procedures

PERFORMANCE METRICS AND MEASUREMENTS Metrics: Should include both minimum and expected performance levels for the service as well as conditions under which the service is considered to be unavailable or limited.

PERFORMANCE METRICS AND MEASUREMENTS Measurements: Should state how the metrics are going to be monitored, reported and evaluated.

EXAMPLES Availability Guarantee. Hardware Availability. Vendor guarantees that all Vendor-owned hardware operated and maintained on behalf of Customer or used to provide hosting services will be operational a minimum of 99.99% of the time in each calendar month for standard Data Center Service. In the event of a dedicated hardware failure, Vendor will repair or replace the faulty equipment within 2 hours of the diagnosed condition.

EXAMPLES Availability %Downtime per yearDowntime per monthDowntime per week 90% ("one nine")36.5 days72 hours16.8 hours 95%18.25 days36 hours8.4 hours 97%10.96 days21.6 hours5.04 hours 98%7.30 days14.4 hours3.36 hours 99% ("two nines")3.65 days7.20 hours1.68 hours 99.50%1.83 days3.60 hours50.4 minutes 99.80%17.52 hours86.23 minutes20.16 minutes 99.9% ("three nines")8.76 hours43.8 minutes10.1 minutes 99.95%4.38 hours21.56 minutes5.04 minutes 99.99% ("four nines")52.56 minutes4.32 minutes1.01 minutes %26.28 minutes2.16 minutes30.24 seconds % ("five nines")5.26 minutes25.9 seconds6.05 seconds % ("six nines")31.5 seconds2.59 seconds0.605 seconds % ("seven nines")3.15 seconds0.259 seconds second

EXAMPLES Unscheduled Downtime per Calendar MonthApproximate Service Credit Equivalent Service Credit Amount based on monthly charge for affected Service 0 minutes – 5 minutesnone0% 5 minutes – 119 minutes1 day3% 120 minutes – 239 minutes1 week25% 240 minutes – 479 minutes2 weeks50% 480 minutes and greater1 month100% Maximum service unavailability due to unscheduled downtime is 5 minutes per month. In any calendar month, if there is a period of Unavailability of 5 minutes or greater due to unscheduled downtime, the Customer will receive Service Credit based on the following schedule. Customer may obtain no more than one (1) month Service Credit for any given month and in no event shall the total amount credited to customer exceed the total fee paid by customer for the affected services

TYPES OF METRICS Service Availability Defect Rates Technical Quality Security

ACCOUNTABILITY Escalation Procedures Define the steps to be taken when service levels do not meet the expected and agreed- upon standards. May include: – Issue and status reporting requirements – Issue resolution within a specified time – Intervention of senior management

ACCOUNTABILITY Costs and Penalties Estimate the costs and/or value of lost services to determine penalties and damages. Penalties may include: – a percentage of monthly recurring fees that scale up with failure severity. May be capped and/or cumulative across all SLAs – liquidated damages – contract termination for recurring or very severe issues

EXCLUSIONS Exclusions are events or issues that are exempt from the overall SLA measurement. Common exclusions include: – scheduled and/or emergency maintenance (e.g.upgrading equipment, reboots, backups) – failure of a third party outside service provider’s direct control – “force majeure” events – failure to make “reasonable efforts” – customer changes

REVIEW As businesses change, so do its service requirements. An SLA should be reviewed periodically, specifically if: – The client's business needs have changed – The technical environment has changed – Workloads have changed – Metrics, measurement tools and processes have improved

SLA Checklist Does the SLA cover? Service objectives Parties included People responsible for the agreement Coverage period Definition of terms Procedures for updating/changing/amending the agreement

SLA Checklist Does the agreement include the following service factors? Definition of the service(s) Service hours and dates Service exclusions

SLA Checklist Does the agreement detail coverage of customer and service provider factors? Procedures for adding or changing services Arrangements for service interruptions Escalation procedures Customer / service provider responsibilities

SLA Checklist Does the agreement cover communication channels? Contact points included for both customer and service provider Communication channels and methods

SLA Checklist Does the agreement state what and how performance monitoring will occur? Service targets (expected and minimum levels) How to monitor and report on performance Frequency of reporting Auditing of reports and monitoring Quality assurance measurements Complaints handling

SLA Checklist Does the agreement delineate service costs and penalties for substandard performance? Service cost and financial penalties

Want more information? Susan Kohlhausen