Laserfiche WebLink
<br />Page 2 of 3 <br />v416 <br /> <br />3.1. Maintenance Services. We will continuously maintain the Application Service to optimize availability that meets <br />or exceeds the Service Standard. Such maintenance services shall include providing to You all such services and <br />repairs, as needed, to maintain the Application Service or are ancillary, necessary, or otherwise related to Your <br />access to, or use of, the Application Service, so that the Application Service operates properly in accordance with <br />this SLA. <br />3.2. Support Services. We will: (i) provide unlimited telephone support during business hours; and (ii) respond to and <br />resolve support requests, as specified in Sections 3.3 and 3.4. <br />3.3. Support Requests. You shall notify Us of support request by e-mail, telephone, or such other means as the <br />Parties may hereafter agree to in writing. We shall classify Your support requests in accordance with the <br />descriptions set forth in the following chart: <br /> <br />Support <br />Request <br />Classification <br />Description of the support request comprising or causing any of the events or <br />effects set forth below: <br />Severity 1: <br />Critical Problem <br /> Application Service is down or unavailable <br /> Data integrity at risk <br /> Material financial impact <br /> Widespread access interruptions <br />Severity 2: <br />Major Problem <br /> Application Service is operational; however, performance is highly degraded to <br />the point of material impact on usage <br /> Data entry or access is materially impaired on a limited basis <br />Severity 3: <br />Minor Problem <br /> Application Service is operating with minor issues that can be addressed with a <br />work around <br />Severity 4: <br />Cosmetic Issue <br /> Minor problem not impacting service functionality <br /> Enhancement requests, missing or erroneous documentation <br /> Minor problem or question that does not affect delivery of services <br /> <br />3.4. Response Service Levels. Response times to support requests will be measured from the time We receive a <br />support request until the time We have responded to such support request. We will respond to all support <br />requests, based on the severity of the request, within the times set forth in the following chart: <br /> <br />Support <br />Request <br />Classification <br />Required <br />Response <br />Time <br />Target Resolution <br />Time Resolution Effort <br />Severity 1: <br />Critical Problem <br />1 business <br />hour <br />48 hours or <br />agreement to <br />reasonable date <br />Critical situations may require personnel from <br />both organizations to be at their respective <br />work locations or available on an around-the- <br />clock basis. <br />Severity 2: <br />Major Problem <br />4 business <br />hours 10 calendar days <br />We will resolve with a fix or a workaround, at <br />its discretion. If a workaround is provided, the <br />severity is downgraded. <br />Severity 3: <br />Minor Problem <br />8 business <br />hours 30 calendar days We will resolve with a fix or a workaround, at <br />its discretion. <br />Severity 4: <br />Cosmetic Issue <br />12 business <br />hours At Our discretion We will resolve with a fix or a workaround, at <br />its discretion. <br /> <br />4.1. System Monitoring and Measurement. We will provide for monitoring of System Availability on an ongoing <br />basis. All measurements of System Availability will be calculated on the Service Year period during the term. This <br />monitoring will be performed through a combination of monitoring services of Our choice. These monitoring <br />services are intended to serve as an initial alert to Us that the System may be unavailable. We will then conduct <br />a series of tests to confirm System Availability. <br /> If the monitoring services report that the System is unavailable and We confirm the System to be unavailable, <br />then Unscheduled Downtime will be calculated as the amount of time between the initial notification and <br />when We confirm the System is available. <br /> If the monitoring services report that the System is unavailable, but Our tests and assessments confirm that <br />the System is available, then Unscheduled Downtime will be calculated as the time between when the initial