B - Fully Executed - Laserfiche WebLink

Home Browse Search

Cayenta Managed Services - Schedule "A" Docusign Envelope lD: AA214E95-42B1-41 D3-BCDC-24DD6584CA02 Response Times Response times will vary and are dependent on the priority of the ticket/issue/call (hereafter references as tickets). We do our best to ensure that we deal with incoming tickets in the order that they are received, however tickets will be escalated based on the urgency of the issue reported' Our response time guidelines are as follows (based on Standard CMS Support Hours specified in item 11 of the General Assumptions sub-section): e Priority 1: 3 4 hours r Priority 2: 1- 8 hours r Priority 3: 1- 24 hours Response time is defined as the amou nt of time between when the Customer first creates a ticket (which includes submission via any methods mentioned in General Assumption 8 under the General Assumptions for the Standard Manae€d Services section) and when a Cayenta Technical Consultant responds' Ticket Priorities To assign our resources to incoming tickets as effectively as possible, we have identified three types of ticket priorities, L,2and 3. A Priority l ticket is a deemed by our CMS staff to be an Urgent/Critical Priority ticket, priority 2 is classified as a High or Medium Priority and Priority 3 is deemed to be a Low Priority' The criteria used to establish guidelines for these tickets are as follows: Priority 1 - Critical/Urgent r Production System Down* r Technical issues with data integration and updates causing the integration to fail o Performance issues of severe nature impacting critical processes . Data security issues . Applying application patches for critical issues within the application, that do not have a work around Priority 2 - High or Medium . System errors that have workarounds r Failure of integration components like APls o printer related issues (related to interfaces with our software and not the printer itself) r Performance issues not impacting critical processes . Assistance with workstation connectivity issues (workstation specific) r Assistance with application or database access issues . Provide direct access to database for privileged or approved users r Assistance with ODBC configuration . Applying high/medium priority patches for issues that have a work around Priority 3 - low r Recommendations for enhancements on system changes r lssues with routine maintenance of application and database Note: the existence of a reasonable workaround precludes a Priority 1 or Priority 2 ticket in most cases' *System down issues are defined as issues where all users are unable to access the system. lssues isolated to a subset ofthe users are not considered a system down event. davc'tff -rG Cayerlta, A Division of N. l-larris Computer Corporation Page 5