My WebLink
|
Help
|
About
|
Sign Out
20
City of Pleasanton
>
CITY CLERK
>
AGENDA PACKETS
>
2020
>
012120
>
20
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/15/2020 3:59:55 PM
Creation date
1/15/2020 3:59:52 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
AGENDA REPORT
DOCUMENT DATE
1/21/2020
DESTRUCT DATE
15Y
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
20
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
Tyler's website or by calling software support directly. <br /> Incident Priority <br /> Each incident is assigned a priority number,which corresponds to the client's needs and deadlines.The client is <br /> responsible for reasonably setting the priority of the incident per the chart below.The goal of this structure is to help <br /> the client clearly understand and communicate the importance of the issue and to describe expected responses and <br /> resolutions. <br /> Priority v �. - u <br /> Level Characteristics of Support Incident b Resolution Targets <br /> Support:incident that causes (a)complete Tyler shall provide an initial response to Priority Level 1 <br /> application failure or application incidents within one (1) business hour of receipt of the <br /> unavailability; (b)application failure or support.incident. Tyler shall use commercially reasonable <br /> 1 unavailability in:one or more of the client's efforts to resolve such support incidents or provide a <br /> Critical remote location; or(c) systemic loss of circumvention procedure within one (1) business day• T. ler''s <br /> multiple essential system functions. responsibility for lost or corrupted data is limited to assisting <br /> the client in restoring its last available database. <br /> Support incident that causes(a) repeated, Tyler shall provide an initial response to Priority Level 2 <br /> consistent failure of essential functionality incidents within four(4) business hours of receipt of the <br /> 2 <br /> affecting more than one user or(b) loss or support incident. Tyler shall use commercially reasonable <br /> High 1 corruption of data. efforts to resolve such support incidents or provide a <br /> circumvention procedure within ten (10) business days. <br /> Tyler's responsibility for loss or corrupted data is limited to <br /> assisting the client in restoring its last available database. <br /> Priority Level 1 incident with an existing Tyler shall provide an initial response to Priority Level 3 <br /> circumvention procedure, or a Priority Level incidents within one (1) business day of receipt of the support <br /> 2 incident that affects only one user or for , incident. Tyler shall use commercially reasonable efforts to . <br /> 3. which there is an:existing circumvention resolve such support incidents without the need for a <br /> Medium , procedure. circumvention procedure with the next published' <br /> maintenance update or service pack. Tyler's responsibility for <br /> lost or corrupted data is limited to assisting the client in <br /> restoring its last available database. <br /> Support incident that causes failure of non- Tyler shall provide an initial response to Priority Level 4 <br /> 4 essential functionality or a cosmetic or incidents within two (2) business days. Tyler shall use <br /> Non- other issue that does not qualify as any commercially reasonable efforts to resolve such support <br /> critical other Priority Level. incidents, as well as cosmetic issues,with a future version <br /> release. <br /> Incident Escalation <br /> Tyler.Technology's software support consists of four levels of personnel: <br /> (1) Level 1:front-line representatives <br /> (2) Level 2: more senior in their support role,they assist front-line representatives and take on escalated issues <br /> (3) Level 3: assist in incident escalations and specialized client issues <br /> (4) Level 4: responsible for the management of support teams for either a single product ora product group <br /> If a clientfeelsthey are not receiving the service needed,they may contact the.appropriate Software Support Manager. <br /> After receiving the incident tracking number,the manager will follow up on the open issue and determine the necessary <br /> action to meet the client's needs. <br /> On occasion,the priority or immediacy of a software support incident may change after initiation.Tyler encourages <br /> Amendment-Pleasanton CA-Brazos-JW 11.18.19(2019-29730 11.15).doc <br />
The URL can be used to link to this page
Your browser does not support the video tag.