Laserfiche WebLink
SMA RTGOV <br />3.1. Maintenance Services. We will continuously mainta in 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 bye-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 />Support Description of the support request comprising or causing any of the events or Request effects set forth below: Classification <br />• Application Service is down or unavailable <br />Severity 1: • Data integrity at risk <br />Critical Problem • Material financial impact <br />• Widesprea'd access interruptions <br />• Application Service is operational; however, performance is highly degraded to Severity 2: the pOint of material impact on usage Major Problem • Data entry or access is materially impaired on a limited basis <br />Severity 3: • Application Service is operating with minor issues that can be addressed with a <br />Minor Problem work around <br />• Minor problem not impacting service functionality <br />Severity 4: • Enhancement requests, missing or erroneous documentation Cosmetic Issue • Minor problem or question that does not affect delivery of services <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 />Support Required Target Resolution Request Response Time Resolution Effort <br />Classification Time <br />48 hours or Critical situations may require personnel from <br />Severity 1: 1 business agreement to both organizations to be at their respective <br />Critical Problem hour work locations or available on an around-the-reasonable date clock basis . <br />Severity 2: 4 business We will resolve with a fix or a workaround, at <br />10 calendar days its discretion. If a workaround is provided, the Major Problem hours severity is downgraded . <br />Severity 3: 8 business 30 calendar days We will resolve with a fix or a workaround, at <br />Minor Problem hours its discretion . <br />Severity 4: 12 business At Our discretion We will resolve with a fix or a workaround, at <br />Cosmetic Issue hours its discretion . <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 />v416 <br />• If the monitoring services report that the System is unavailable and We confirm the System to be unavailable, <br />then Unscheduled Down ti me 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 <br />Page 2 of 3