Browse
Search
Agenda 08-26-2025; 8-e - Approval of Tyler Software as a Service (SaaS) MUNIS to the Cloud
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2020's
>
2025
>
Agenda - 08-26-2025 Business Meeting
>
Agenda 08-26-2025; 8-e - Approval of Tyler Software as a Service (SaaS) MUNIS to the Cloud
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/21/2025 11:55:11 AM
Creation date
8/21/2025 11:56:44 AM
Metadata
Fields
Template:
BOCC
Date
8/26/2025
Meeting Type
Business
Document Type
Agenda
Agenda Item
8-e
Document Relationships
Agenda for August 26, 2025 BOCC Meeting
(Message)
Path:
\Board of County Commissioners\BOCC Agendas\2020's\2025\Agenda - 08-26-2025 Business Meeting
OTHER-2025-075-Order of the board of county commissioners in accordance with G.S. 105-321
(Message)
Path:
\Board of County Commissioners\Various Documents\2020 - 2029\2025
PRO-2025-025-Labor Day Proclamation
(Message)
Path:
\Board of County Commissioners\Proclamations\2020-2029\2025
RES-2025-037-Tax Collector’s Annual Settlement for Fiscal Year 2024-25
(Message)
Path:
\Board of County Commissioners\Resolutions\2020-2029\2025
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
42
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
41 <br /> Exhibit C <br /> Schedule 1 <br /> Priority Characteristics of Support Incident Resolution Targets' <br /> Level <br /> Support incident that causes(a) Tyler shall provide an initial response to Priority Level <br /> repeated, consistent failure of 2 incidents within four(4) business hours of receipt of <br /> essential functionality affecting more the incident. Once the incident has been confirmed, <br /> than one user or(b) loss or corruption Tyler shall use commercially reasonable efforts to <br /> 2 of data. resolve such support incidents or provide a <br /> High circumvention procedure within ten (10) business <br /> days. For non-hosted customers,Tyler's <br /> responsibility for loss or corrupted data is limited to <br /> assisting the Client in restoring its last available <br /> database. <br /> Priority Level 1 incident with an Tyler shall provide an initial response to Priority Level <br /> existing circumvention procedure, or 3 incidents within one(1) business day of receipt of <br /> a Priority Level 2 incident that affects the incident. Once the incident has been confirmed, <br /> only one user or for which there is an Tyler shall use commercially reasonable efforts to <br /> 3 existing circumvention procedure. resolve such support incidents without the need for a <br /> Medium circumvention procedure with the next published <br /> maintenance update or service pack,which shall <br /> occur at least quarterly. For non-hosted customers, <br /> Tyler's responsibility for lost or corrupted data is <br /> limited to assisting the Client in restoring its last <br /> available database. <br /> Support incident that causes failure of Tyler shall provide an initial response to Priority Level <br /> 4 non-essential functionality or a 4 incidents within two(2) business days of receipt of <br /> cosmetic or other issue that does not the incident. Once the incident has been confirmed, <br /> Non- qualify as any other Priority Level. Tyler shall use commercially reasonable efforts to <br /> critical resolve such support incidents, as well as cosmetic <br /> issues,with a future version release. <br /> Response and Resolution Targets may differ by product or business need <br /> Incident Escalation <br /> If Tyler is unable to resolve any priority level 1 or 2 defect as listed above or the priority of an issue has <br /> elevated since initiation,you may escalate the incident to the appropriate resource, as outlined by each <br /> product support team. The corresponding resource will meet with you and any Tyler staff to establish a <br /> mutually agreeable plan for addressing the defect. <br /> Remote Support Tool <br /> Some support calls may require further analysis of the Client's database, processes or setup to diagnose <br /> a problem or to assist with a question.Tyler will, at its discretion, use an industry-standard remote <br /> support tool.Tyler's support team must have the ability to quickly connect to the Client's system and <br /> view the site's setup, diagnose problems, or assist with screen navigation. More information about the <br /> remote support tool Tyler uses is available upon request. <br /> ••�•• tyler <br /> 0 <br /> 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.