Severity Classification and Response Time Goals Sample Clauses

Severity Classification and Response Time Goals. Issues are classified according to severity of impact on the use of the Software, according to the Support Response Time Goal chart below. All disputes regarding severity classification will be resolved by TCP in its sole discretion.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Severity Classification and Response Time Goals. Issues are classified according to severity of impact on the use of the Software, according to the Support Response Time Goal chart below. All disputes regarding severity classification will be resolved by TCP in its sole discretion. Support Response Time Goals Severity Impact Response Time Goal Level 1 Production system is down, impacting all applications and associated business systems. No Workaround exists. A Level 1 Issue will immediately be assigned to a TCP Support Technician who will contact Client within one (1) business hour with an initial response. The support technician will then work without interruption on the Issue until a resolution is reached, either in the form of a complete fix, or an interim Workaround solution that will cause the level of urgency to drop to Level 2. Level 2 Production system performance is degraded, but operational; Issue affects essential functions and no Workaround exists; or Issue is blocking critical systems tests or deliverables. A Level 2 Issue will immediately be assigned to a TCP Support Technician who will contact Client within two (2) business hours with an initial response. The support technician will then work without interruption during standard support hours until a resolution is reached, either in the form of a complete fix, or an interim Workaround solution that will cause the level of urgency to drop to Level 3. Level 3 General product questions relating to development, feature issues, or Documentation. A Level 3 Issue will be assigned to a TCP Support Technician who will contact Client within one (1) business day with an initial response. The support technician will work on the issue during Standard Support Hours.
Sample 1Sample 2Sample 3See All (5)
Severity Classification and Response Time Goals. Issues are classified according to severity of impact on the use of the Supported Hardware, according to the Support Response Time Goal chart below. All disputes regarding severity classification will be resolved by TCP in its sole discretion. Support Response Time Goals Severity Impact Response Time Goal Level 1 Production system is down, impacting all applications and associated business systems. No Workaround exists. A Level 1 Issue will immediately be assigned to a TCP support technician who will contact Client within one (1) business hour with an initial response. The support technician will then work without interruption on the Issue until a resolution is reached, either in the form of a complete fix, or an interim Workaround solution that will cause the level of urgency to drop to Level 2. Level 1 Issues qualify for 24/7 Support for Clients who have purchased this Support Plan. Level 2 Production system performance is degraded, but operational; Issue affects essential functions and no Workaround exists; or Issue is blocking critical systems tests or deliverables. A Level 2 Issue will immediately be assigned to a TCP Support Technician who will contact Client within two (2) business hours with an initial response. The support technician will then work without interruption during standard support hours until a resolution is reached, either in the form of a complete fix, or an interim Workaround solution that will cause the level of urgency to drop to Level 3. Level 2 Issues qualify for 24/7 Support for Clients who have purchased this Support Plan. Level 3 General product questions relating to development, feature issues, or Documentation. A Level 3 Issue will be assigned to a TCP Support Technician who will contact Client within one (1) business day with an initial response. The support technician will work on the issue during Standard Support Hours. Level 3 Issues do not qualify for 24/7 Support for Clients who have purchased this Support Plan.
Sample 1Sample 2See All (4)
Severity Classification and Response Time Goals. Issues are classified by Service Provider according to severity of impact on the use of the Application, according to the chart below. All disputes regarding severity classification will be resolved by Service Provider in its sole discretion. Standard Support Response Time Goals Severity Impact Response Time Goal 1 Production system is down, impacting all applications and associated business systems. 4 business hours (via the Customer Support Portal) 2 Production system performance is degraded, but operational; Issue affects essential functions; or Issue is blocking critical systems tests or deliverables. 12 business hours 3 General product questions relating to development, feature issues, or documentation. 2 business days 3. GOLD SUPPORT
Sample 1
Severity Classification and Response Time Goals. Issues are classified according to the severity of impact on the use of the Software, according to the Support Response Time Goal chart below. TCP will resolve all disputes regarding severity classification at its sole discretion. Support Response Time Goals Severity Impact Response Time Goal Level 1 Production system is down, impacting all applications and associated business systems. No Workaround exists. A Level 1 Issue will immediately be assigned to a TCP Support Technician who will contact Client within one (1) business hour with an initial response. The support technician will then work without interruption on the Issue until a resolution is reached, either in the form of a complete fix, or an interim Workaround solution that will cause the level of urgency to drop to Level 2.
Sample 1

Related to Severity Classification and Response Time Goals

  • Switching System Hierarchy and Trunking Requirements For purposes of routing iNetworks traffic to Verizon, the subtending arrangements between Verizon Tandems and Verizon End Offices shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to iNetworks, the subtending arrangements between iNetworks Tandems and iNetworks End Offices shall be the same as the Tandem/End Office subtending arrangements that iNetworks maintains for the routing of its own or other carriers’ traffic.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Goals Goals define availability, performance and other objectives of Service provisioning and delivery. Goals do not include remedies and failure to meet any Service Goal does not entitle Customer to a Service credit.

  • Contract Goals A. For purposes of this procurement, OGS conducted a comprehensive search and determined that the Contract does not offer sufficient opportunities to set goals for participation by MWBEs as subcontractors, service providers, or suppliers to Contractor. Contractor is, however, encouraged to make every good faith effort to promote and assist the participation of MWBEs on this Contract for the provision of services and materials. The directory of New York State Certified MWBEs can be viewed at: xxxxx://xx.xxxxxxxxxxxxxx.xxx/FrontEnd/VendorSearchPublic.asp?TN=ny&XID=2528. Additionally, following Contract execution, Contractor is encouraged to contact the Division of Minority and Women’s Business Development ((000) 000-0000; (000) 000-0000; or (000) 000-0000) to discuss additional methods of maximizing participation by MWBEs on the Contract.

  • Performance Measure The specific representation of a process or outcome that is relevant to the assessment of performance; it is quantifiable and can be documented

  • Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 5.6.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Performance Goals A. The Trust and State Street have developed mutually acceptable performance goals dated March 1, 2011 , and as may be amended from time to time, regarding the manner in which they expect to deliver and receive the services under this Agreement (hereinafter referred to as “Service Level Agreement”). The parties agree that such Service Level Agreement reflects performance goals and any failure to perform in accordance with the provisions thereof shall not be considered a breach of contract that gives rise to contractual or other remedies. It is the intention of the parties that the sole remedy for failure to perform in accordance with the provisions of the Service Level Agreement, or any dispute relating to performance goals set forth in the Service Level Agreement, will be a meeting of the parties to resolve the failure pursuant to the consultation procedure described in Sections V. B. and V.C. below. Notwithstanding the foregoing, the parties hereby acknowledge that any party’s failure (or lack thereof) to meet the provisions of the Service Level Agreement, while not in and of itself a breach of contract giving rise to contractual or other remedies, may factor into the Trust’s reasonably determined belief regarding the standard of care exercised by State Street hereunder.

  • PERFORMANCE OBJECTIVES 4.1 The Performance Plan (Annexure A) sets out-

  • Temperature Measurement Temperature will be measured by the nearest automatic Melbourne Bureau of Meteorology Monitoring Station for example (but not limited to): Melbourne, Moorabbin, Dunns Hill, Melbourne Airport, Frankston, and Point Xxxxxx. At the commencement of each project, the onsite management and employee representatives shall agree which is to be the applicable automatic weather monitoring station.

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