Issue Handling Sample Clauses

Issue Handling. Incident Tracking Every support incident is logged into Tyler’s Customer Relationship Management System and given a unique incident number. This system tracks the history of each incident. The incident tracking number is used to track and reference open issues when clients contact support. Clients may track incidents, using the incident number, through the portal at Tyler’s website or by calling software support directly. Incident Priority Each incident is assigned a priority number, which corresponds to the client’s needs and deadlines. The client is responsible for reasonably setting the priority of the incident per the chart below. This chart is not intended to address every type of support incident, and certain “characteristics” may or may not apply depending on whether the Tyler software has been deployed on customer infrastructure or the Tyler cloud. The goal is to help guide the client towards clearly understanding and communicating the importance of the issue and to describe generally expected responses and resolutions. Priority Level Characteristics of Support Incident Resolution Targets 1 Critical Support incident that causes (a) complete application failure or application unavailability; (b) application failure or unavailability in one or more of the client’s remote location; or (c) systemic loss of multiple essential system functions. Tyler shall provide an initial response to Priority Xxxxx 0 incidents within one (1) business hour of receipt of the support incident. Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within one (1) business day. For non- hosted customers, Tyler’s responsibility for lost or corrupted data is limited to assisting the client in restoring its last available database. 2 High Support incident that causes (a) repeated, consistent failure of essential functionality affecting more than one user or (b) loss or corruption of data. Tyler shall provide an initial response to Priority Level 2 incidents within four (4) business hours of receipt of the support incident. Tyler shall use commercially reasonable efforts to resolve such support incidents or provide a circumvention procedure within ten (10) business days. For non- hosted customers, Tyler’s responsibility for loss or corrupted data is limited to assisting the client in restoring its last available database. 3 Medium Priority Level 1 incident with an existing circumvention procedure, or a Priority Le...
Sample 1See All (5)
AutoNDA by SimpleDocs

Related to Issue Handling

  • Claims Handling We may use any or all of the following to determine the value of any damages, loss or claim that may be covered by this policy:

  • Information Handling Implement new/improved system; update incoming publications; circulate publications; identify information source(s) inside and outside the organisation. Grade 5 - Communication: Obtain data from external sources; produce reports; identify need for documents and/or research. Grade 5 - Enterprise: Assist with the development of options for future strategies; assist with planning to match future requirements with resource allocation.

  • Incident handling As defined by the EGI Default Operational Level Agreement.

  • COMPLAINTS HANDLING 44.1 Either Party shall notify the other Party of any Complaints made by Other Contracting Bodies, which are not resolved by operation of the Supplier's usual complaints handling procedure within five (5) Working Days of becoming aware of that Complaint and, if the Supplier is the Party providing the notice, such notice shall contain full details of the Supplier's plans to resolve such Complaint.

  • Handling In order to protect such Confidential Information from improper disclosure, each Party agrees:

  • Risk Warning 7.1. The Client unreservedly accepts, acknowledges and understands that CFDs trading: • is highly speculative; • carry a high level of financial risk, as they are subject to excessive price fluctuations which may cause substantial losses; • in the case of CFDs with underlying asset a virtual currency, there might be sudden changes in prices of certain instruments. This can happen during economic events or market announcements or geopolitical events, news, or even due to adverse media or fake news. Gaps can occur when markets open or close or even during normal trading hours. If the market is closed when these factors occur, the opening price of the underlying asset can be substantially different from the closing price, giving you no opportunity to close your trade in-between. Pricing gaps can result in losses. Therefore, CFDs on virtual currencies may be subject to large price fluctuations and in some instances, due to the early stages of their lifecycle, they may lose entire value. • the losses may include all of the Client’s investment and also any additional commissions and other expenses; • is only suitable for persons who are able to cope with the associated risks by bearing the financial losses; • the Company does not guarantee the capital of the Client’s Account or its value at any time or any money invested in any Financial Instrument;

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA.

  • Procurement All goods, works and services required for the Project and to be financed out of the proceeds of the Financing shall be procured in accordance with the provisions of Section III of Schedule 2 to the Financing Agreement.

  • Scheduling Regulations F-1 Scheduling Provisions for Extended Tours - 11.25 Hour Tours

  • Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”). Data Escrow. Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).

Time is Money Join Law Insider Premium to draft better contracts faster.