Service Level Provisions Sample Clauses

Service Level Provisions. (a) Service Level Targets We will use all reasonable efforts to ensure that the Hosting Service is available for 99.70% of each calendar month. The Service will be deemed unavailable if it cannot be reached from a functioning Internet Connection. Any instances of unavailability shall have to be ratified by Our monitoring system. (b) The Hosting Service shall not be deemed unavailable (without limitation) in the event of any of the following: o Periods of scheduled maintenance; o Failure by You or End User connection to the Network (e.g. via the public internet or your own network, or any 3rd party telecommunications tail circuits); o Malfunction of yours or End User’s own computing systems; (c) Recovery Point Objective RPO is the maximum time period in which data might be lost, for SQL Server this is 12 hours, for a Single Virtual Machine this is 12 hours, for a Complete Primary Datacentre Outage this is also 12 hours. (d) Recovery Time Objective RTO is the duration of working time within which Service should be restored after a disaster. This time starts from when a support call is logged with Us, for SQL Server this is 6 hours, for a Single Virtual Machine is 6 hours, for a Complete Datacentre Outage it is 12 hours. (e) Service Level Credits If We fail to achieve the Service Level Target, and if You request Us to do so within twenty (20) Business Days after the target is not met, We will issue to You service credits against future periods of service as detailed in the adjacent table. (f) Service credits issued shall not survive termination of the contract for the Service and are not applicable against other services.
AutoNDA by SimpleDocs
Service Level Provisions 

Related to Service Level Provisions

  • 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 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 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 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 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.

  • Transitional Provisions 24.1. As from the official date of entry into force of the 01 series of amendments to this Regulation, no Contracting Party applying this Regulation shall refuse to grant or refuse to accept type approval under this Regulation as amended by the 01 series of amendments. 24.2. As from 12 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation shall grant approvals only if the type of components to be approved meets the requirements of Part I of this Regulation as amended by the 01 series of amendments to this Regulation. 24.3. Type approvals of components other than fuel rail, as defined in paragraph 4.72., granted according to the original version of this Regulation or of components granted according to the 01 series of amendments, shall remain valid and shall be accepted for the purpose of their installation on vehicles as long as the requirements for the specific component have not changed by any series of amendments. 24.4. As from 18 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation shall grant approvals only if the vehicle type to be approved meets the requirements of Part II of this Regulation as amended by the 01 series of amendments to this Regulation. 24.5. Until 12 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation can continue to grant type approvals for the type of components to the original version of this Regulation without taking into account the provisions of the 01 series of amendments. 24.6. Until 18 months after the date of entry into force of the 01 series of amendments to this Regulation, Contracting Parties applying this Regulation can continue to grant type approvals for the vehicle type to the original version of this Regulation without taking into account the provisions of the 01 series of amendments. 24.7. Notwithstanding the provisions of paragraphs 24.5. and 24.6., Contracting Parties applying this Regulation shall not refuse to grant extensions of type approvals for existing types of component or vehicle types which have been issued according to this Regulation without taking into account the provisions of the 01 series of amendments to this Regulation. 24.8. As from the official date of entry into force of the 02 series of amendments to this Regulation, no Contracting Party applying this Regulation shall refuse to grant or refuse to accept type approval under this Regulation as amended by the 02 series of amendments. 24.9. As from 1 September 2017 Contracting Parties applying this Regulation shall grant approvals only if the type of components to be approved meets the requirements of Part I of this Regulation as amended by the 02 series of amendments to this Regulation. 24.10. As from 1 September 2018 Contracting Parties applying this Regulation shall grant approvals only if the vehicle type to be approved meets the requirements of Part II of this Regulation as amended by the 02 series of amendments to this Regulation. 24.11. As from 1 September 2019 Contracting Parties applying this Regulation may refuse to recognize approvals of a type of vehicle which have not been granted in accordance with Part II of this Regulation as amended by the 02 series of amendments to this Regulation. 24.12. Contracting Parties applying this Regulation shall not refuse to grant extensions of type approvals for existing types of component or vehicle types which have been issued according to this Regulation without taking into account the provisions of the 02 series of amendments to this Regulation. 24.13. Notwithstanding paragraphs 24.11. and 24.12., Contracting Parties applying this Regulation shall continue to accept type approvals granted to the preceding series of amendments, which are not affected by the 02 series of amendments.

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

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

  • Final Provisions Clause 16

  • Data Provisions Subject to the limitations contained in CA Government Code Section 3558, the City shall provide the Union with all required information on newly-hired employees to the extent it is made available to the City. In addition, within ten (10) business days of the conclusion of each NEO, the City agrees to provide the Union with a stand-alone report containing a list of employees, including classification code and division, who were scheduled to, but did not attend each NEO.

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