Laserfiche WebLink
tyler <br />Exhibit C <br />Service Level Agreement <br />I. Agreement Overview <br />Exhibit C <br />••.: <br />This SLA operates in conjunction with, and does not supersede or replace any part of, the Agreement. It <br />outlines the information technology service levels that we will provide to you to ensure the availability of <br />the application services that you have requested us to provide. All other support services are documented <br />in the Support Call Process. <br />II. Definitions. Except as defined below, all defined terms have the meaning set forth in the <br />Agreement. <br />Attainment: The percentage of time the Tyler Software is available during a calendar quarter, with <br />percentages rounded to the nearest whole number. <br />Client Error Incident: Any service unavailability resulting from your applications, content or equipment, or <br />the acts or omissions of any of your service users or third -party providers over whom we exercise no <br />control. <br />Downtime: Those minutes during which the Tyler Software is not available for your use. Downtime does <br />not include those instances in which only a Defect is present. <br />Service Availability: The total number of minutes in a calendar quarter that the Tyler Software is capable <br />of receiving, processing, and responding to requests, excluding maintenance windows, Client Error <br />Incidents and Force Majeure. <br />III. Service Availability <br />The Service Availability of the Tyler Software is intended to be 24/7/365. We set Service Availability goals <br />and measures whether we have met those goals by tracking Attainment. <br />a. Your Responsibilities <br />Whenever you experience Downtime, you must make a support call according tot he procedures outlined <br />in the Support Call Process. You will receive a support incident number. <br />You must document, in writing, all Downtime that you have experienced during a calendar quarter. You <br />must deliver such documentation to us within 30 days of a quarter's end. <br />The documentation you provide must evidence the Downtime clearly and convincingly. It must include, <br />for example, the support incident number(s) and the date, time and duration of the Downtime(s). <br />b. Our Resoonsibilities <br />When our support team receives a call from you that Downtime has occurred or is occurring, we will work <br />with you to identify the cause of the Downtime (including whether it may be the result of a Client Error <br />Incident or Force Majeure). We will also work with you to resume normal operations. <br />••:;:•. tyler <br />