GTTR Service Level Sample Clauses

GTTR Service Level. Subject to the limitations, conditions and exclusions described in Clause 1.7.2 (5-Hour GTTR Conditions) and Clause 1.9 (Conditions and Exclusions), Orange will repair an Outage of the Business VPN Corporate Service caused by a malfunctioning CPE CE Router or Orange-provided Tail Circuit within 5 hours from the time the GCSC creates the Incident Report (the "5-Hour GTTR Service Level") provided that the Location has either: (a) a Dual or Always-On ADSL continuity solution, or (b) an Always-On SDSL continuity solution. The Business VPN Corporate Service is considered repaired when the GCSC closes the Incident Report in the Incident case management system after informing Customer that the Service is restored; however, the GCSC will keep Incident Report open if Customer informs the GCSC that the Business VPN Corporate is still out of service. Orange will report the achievement or non-achievement of the 5-Hour GTTR Service Level on a Monthly basis. If the actual time-to-repair exceeds 5 hours, then Customer will receive a cumulative maximum credit equal to 10% of the Qualifying Charges for the affected Service at the Location where the Outage occurred; provided, however, if Customer is entitled to receive any Service Level credit under Clause 1.3 (Service Levels for Site Availability) in connection with the same Outage, then Customer will only receive the greater of the credits due and owing to Customer under Clause 1.3 or this clause. For clarity, in no event will Customer be entitled to receive Service Level credits under both Clause 1.3 and this clause for the same Outage.
AutoNDA by SimpleDocs
GTTR Service Level. Subject to the limitations, conditions and exclusions described in this Clause 1.4 and in Clause 1.7 (Conditions and Exclusions), Orange will restore a faulty VMS Internet within the applicable Guaranteed- Time-To-Repair Service Level indicated in Table 3 (GTTR and DTTR Service Levels for Regions A, B, C, D & E Locations†) of Exhibit A to this Service Level Agreement. The Network Service is considered restored when the GCSC closes the Incident Report in the Incident case management system after notifying Customer that the Network Service is restored; however, the GCSC will keep the Incident Report open if Customer informs the GCSC that the VMS Internet is still out of service. Orange will report the achievement or non-achievement of the GTTR Service Level on a Monthly basis.‌ 1. The GTTR Service Level only applies if all of the following conditions are satisfied: (a) The Outage was reported by Customer to the GCSC or detected by the Automation; (b) The Outage, as verified by the GCSC, was caused by a fault in the Orange-provided DIA or a fault in the Orange- Managed Router; (c) Customer gives Orange all information reasonably required to restore the VMS Internet Access(es), and gives Orange remote and physical access to the Orange-Managed Router; and (d) Customer ordered the Service Optimize optional feature of the Service Management in respect to the VMS Internet.
GTTR Service Level. Subject to the limitations, conditions and exclusions described in this Clause 1.4 and in Clause 1.7 (Conditions and Exclusions), if the Service at a Location has an Outage that was caused by a fault in either the Internet Gold circuit or an Orange-Managed CE Router, then Orange will restore the Service within the applicable Guaranteed-Time-To-Repair Service Level indicated in Table 3 (GTTR and DTTR Service Levels for Regions A, B, C, D & E Internet Essentials) of Exhibit A (Tables) to this Service Level Agreement. The Service is considered restored when the GCSC closes the Incident Report in the Incident case management system after notifying Customer that the Service is restored; however, the GCSC will keep the Incident Report open if Customer informs the GCSC that the Service is still out of service. Orange will report the achievement or non-achievement of the GTTR Service Level on a Monthly basis.‌ 1. The GTTR Service Level only applies if all of the following conditions are satisfied: (a) Customer reported the Outage to the GCSC, or the Automation detected the Outage; (b) The Outage, as verified by the GCSC, was caused by a fault in either the Internet Gold circuit or the Orange- Managed CE Router; and (c) Customer gives Orange all information reasonably required to restore the Service and gives Orange remote and physical access to the Orange-Managed CE Router.
GTTR Service Level. The GTTR Service Levels only apply to Full Orange Service with Orange MPLS Architecture. There are no GTTR Service Levels for the Full Orange Service with VMI Access Only Architecture and the Flexible SD- WAN Overlay-only Service Architecture. Subject to the limitations, conditions and exclusions described in Clause 1.4.2 (GTTR Conditions) and Clause 1.7 (Conditions and Exclusions), Orange will restore the Service in accordance with the applicable GTTR Service Level. The GTTR Service Levels are listed in Table 4 (Time-to-Repair Service Levels for Regions A, B, C, D & E Locations†) in Exhibit A to this Service Level Agreement. Orange achievement or non-achievement of the GTTR Service Levels will be measured on a Monthly basis. The time to repair starts when the GCSC creates the Incident Report for the Outage. The Service is considered restored when the GCSC closes the Incident Report in the Incident case management system after informing Customer that the Service is restored; however, the GCSC will keep the Incident Report open if Customer informs the GCSC that the Service is still out of service. If the actual time-to-repair exceeds the applicable GTTR Service Level, then Customer will receive a single cumulative maximum credit equal to 10% of the Monthly Recurring Charges for the affected Service at the Location where the Outage occurred; provided, however, if Customer is also entitled to receive any Service Level credit under Clause 1.3.1 (Site Availability) in connection with the same Outage, then Customer will only receive the greater of the credits due and owing to Customer under Clause 1.3.1 or this Clause 1.4.1; and provided further, Customer will not be entitled to Service Level credit under this Clause 1.4 if a Service Level credit pursuant to Clause 1.3.3 (EMS Global Availability) is due to Customer. For clarity, in no event will Customer be entitled to receive concurrent Service Level credits under Clause 1.3.1, Clause 1.3.3, and this Clause 1.4.1.

Related to GTTR Service Level

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Service Levels All service level requirements will be set forth in Exhibit A (“XXXX.xxx Referral Service Level Requirements”). Recipient Xxxxxx agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the XXXX.xxx Referral Service Level Requirements in effect at the time XXXX.xxx identifies the Referral to Recipient Broker/Agent.

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

  • Service Level Credits If Verint does not meet the Uptime Percentage levels specified below, Customer will be entitled, upon written request, to a service level credit (“Service Level Credit”) to be calculated, with respect to the applicable Hosted Environment, as follows: • If Uptime Percentage is at least 99.95% of the month’s minutes, no Service Level Credits are provided; or • If Uptime Percentage is 99.75% to 99.94% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint; or • If Uptime Percentage is 99.50% to 99.74% (inclusive) of the month’s minutes, Customer will be eligible for a credit of 7.5% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint; or • If Uptime Percentage is less than 99.50% of the month’s minutes, Customer will be eligible for a credit of 10.0% of a monthly average fee derived from one-twelfth (1/12th) of the then-current annual fee paid to Verint. Customer shall only be eligible to request Service Level Credits if Customer notifies Verint in writing within thirty (30) days from the end of the month for which Service Level Credits are due. All claims will be verified against Verint’s system records. In the event after such notification Verint determines that Service Level Credits are not due, or that different Service Level Credits are due, Verint shall notify Customer in writing on that finding. With respect to any Services Level credits due under Orders placed directly by Customer on Verint, Service Level Credits will be applied to the next invoice following Customer’s request and Verint’s confirmation of available credits; with respect to any Service Level Credits due for SaaS Services under Orders placed on Verint by a Verint authorized reseller on Customer’s behalf, Service Level Credits will be issued by such reseller following Customer’s request and Verint’s confirmation of available credits and such Services Level Credits may only be used by Customer with respect to subsequent purchases of Verint offerings through that reseller. Service Level Credits shall be Customer’s sole and exclusive remedy in the event of any failure to meet the Service Levels. Verint will only provide records of system availability in response to Customer’s good faith claims.

  • Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes. 6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services; (i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures. 6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits. 6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.

  • Service Level Standards In addition to all other requirements in this Agreement, and in accordance with the Best Claims Practices & Estimating Guidelines, Vendor shall use reasonable and good faith efforts to meet the Service Level Standards set forth below.

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA): (a) we are liable for any remedy or rebate specified by the SLA; and (b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.

  • Service Level Commitment IBM provides the following service level commitment (“SLA”) for the Cloud Service, after IBM makes the Cloud Service available to you.

  • Directory Assistance Service Updates 8.3.3.1 BellSouth shall update end user listings changes daily. These changes include: 8.3.3.1.1 New end user connections 3.3.1.2 End user disconnections

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!