VENDOR ON-BOARDING PROCESS

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.
SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement.
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.
WORKSHOP SLA SPECIFICATION BY ETIENNE WERY Lawyer at the Paris & Brussels Bar, Partner ULYS IT OUTSOURCING SUMMIT 27/11/2003.
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.
Network security policy: best practices
SERVICE LEVEL AGREEMENTS Bob Goldberg 312/
Indefeasible Right to Use Agreements (IRU’s): Key Legal Considerations
© 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.
Kathy Alexander, Ph.D. Technical Specialist Water Availability Division Texas Commission on Environmental Quality.
Assurance Report on Controls at Service Organizations SAE 3402
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.
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.
Listen. Plan. Deliver. Project Delivery Summit – A Necessary Evil, and Why they are important… December 9, 2015 Project Delivery Summit Service.
Ch. 5.4 Deposit Account Documents. When an account is opened, customers receive documentation outlining the rights and responsibilities associated with.
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 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
ATS Service Assurance Suite presentation
Auditing & Investigations II
Managing Expectations and SLA
CONTRACT ADMINISTRATION
Dispute Resolution Between ICT Service Providers in Saudi Arabia
Managing Expectations and SLA
12.3 Control Procurements The process of managing procurement relationships, monitoring contract performance and making changes or corrections as needed.
EPA CONTRACT TEMPLATE Overview
12.2 Conduct Procurements The process of obtaining seller responses, selecting a seller and awarding the contract The team applies selection criteria.
Auditing Cloud Services
EPA SUBCONTRACT TEMPLATE Overview September 2017
Service Organization Control (SOC)
ITIL:Service Design IT Services Management Martin Sarnovský
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Credit Cards: More Than Plastic
Alabede, Collura, Walden, Zimmerman
SocialBoards Self-Service, Multichannel Support Ticket Notifications in Microsoft Office 365 Groups Help Customer Care Teams to Provide Better Care OFFICE.
Health & Consumer Protection Directorate-General : TRACES Service Level Agreement Consultancy project S t r a t e g i z e P l a n E x e c u t e M a n.
Teaming Agreement Clinic
It’s About Time – ScheduleMe Outlook Add-In for Office 365 Enables Users to Schedule Meetings Easily with People Outside of Your Organization Partner Logo.
Commercial Contract Financing
Internal control - the IA perspective
Relate to Clients on a business level
Current Privacy Issues That May Affect Your Credit Union
EEU Scanner PILOT leasing program
General Data Protection Regulation
CONTRACT ADMINISTRATION
Understanding Back-End Systems
Find the Problems with the Provisions May 11, 2016 Presented By:
Working With Cloud - 3.
DSC Default Process January 2019
NEW SBA Form 159 Notice (a) & 504
Neopay Practical Guides #2 PSD2 (Should I be worried?)
Internal Control Internal control is the process designed and affected by owners, management, and other personnel. It is implemented to address business.
Second Avenue Subway Project Execution Strategy
POST-ISSUANCE COMPLIANCE
Chapter 6 Initiating and Planning Systems Development Projects
University of Pittsburgh
Definition IPPF Audit Standard 2120 – Risk Management
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. NOTE: An SLA should incorporated into the master agreement as an attachment or addendum.  NOTE: Should always be a contract/executed to ensure enforceability. NOTE: Make sure it’s attached and incorporated!

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. NOTE: Important for PROTECTION and RECOURSE. If you aren’t able to measure service, then difficult to hold parties accountable. EXAMPLE: TIME WARNER CABLE vs. Office Internet Connectivity

KEY REQUIREMENTS Services and Objectives Performance Requirements and Responsibilities Performance Metrics and Measurement Accountability NOTE: MEAT AND POTATOES OF AN SLA

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?)   purpose, scope (what to include and exclude), dependant business processes and the impact of loss of service

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 NOTE: This is where EXCEPTIONS come into play.

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. NOTE: “expected level” = what the customer is actually paying for. “minimum level” is what the lowest the customer will accept. Significant failure of the vendor. NOTE: Metrics must be set to REASONABLE, ATTAINABLE performance levels. NOTE: Unless strong HISTORICAL MEASUREMENT DATA is available, be prepared to revisit and readjust the settings at a future date through a predefined process specified in the SLA.

PERFORMANCE METRICS AND MEASUREMENTS Measurements: Should state how the metrics are going to be monitored, reported and evaluated. NOTE: Choose measurements that are EASILY COLLECTED. Avoid choosing an excessive number of metrics or metrics that produce a voluminous amount of data that no one will have time to analyze.

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 year Downtime per month Downtime per week 90% ("one nine") 36.5 days 72 hours 16.8 hours 95% 18.25 days 36 hours 8.4 hours 97% 10.96 days 21.6 hours 5.04 hours 98% 7.30 days 14.4 hours 3.36 hours 99% ("two nines") 3.65 days 7.20 hours 1.68 hours 99.50% 1.83 days 3.60 hours 50.4 minutes 99.80% 17.52 hours 86.23 minutes 20.16 minutes 99.9% ("three nines") 8.76 hours 43.8 minutes 10.1 minutes 99.95% 4.38 hours 21.56 minutes 5.04 minutes 99.99% ("four nines") 52.56 minutes 4.32 minutes 1.01 minutes 100.00% 26.28 minutes 2.16 minutes 30.24 seconds 99.999% ("five nines") 5.26 minutes 25.9 seconds 6.05 seconds 99.9999% ("six nines") 31.5 seconds 2.59 seconds 0.605 seconds 99.99999% ("seven nines") 3.15 seconds 0.259 seconds 0.0605 second

EXAMPLES Unscheduled Downtime per Calendar Month Approximate Service Credit Equivalent Service Credit Amount based on monthly charge for affected Service 0 minutes – 5 minutes none 0% 5 minutes – 119 minutes 1 day 3% 120 minutes – 239 minutes 1 week 25% 240 minutes – 479 minutes 2 weeks 50% 480 minutes and greater 1 month 100% 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 NOTE: UPTIME and AVAILABILITY are not synonymous. A system can be up, but not available, as in the case of a network outage.  NOTE: Expect to pay less for 99 percent availability. Providers will offer near 100 percent availability, but it will be more expensive.

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 NOTE: Penalties are usually CAPPED and//or CUMULATIVE across all SLAs

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 skohlhausen@coastalfcu.org 919.412.8113