SYSTEM AVAILABILITY SLA AND CREDITS Sample Clauses

SYSTEM AVAILABILITY SLA AND CREDITS. 3.1 Claim process, Reports
Sample 1Sample 2Sample 3See All (15)
AutoNDA by SimpleDocs
SYSTEM AVAILABILITY SLA AND CREDITS. 2.1. Credit If SAP fails to meet the System Availability SLA for a particular Month, Customer may claim a Credit, which Customer may apply to a future invoice for the Cloud Service that did not meet the System Availability SLA (subject to Sections 2.1.1 and 2.1.2 below). 2.1.1. Claims for a Credit must be made in good faith and through a documented submission of a support case within 30 business days after the end of the relevant Month in which SAP did not meet the System Availability SLA for the Cloud Service. 2.1.2. Customers who have not subscribed to the Cloud Service directly from SAP must claim the Credit from their applicable SAP partner.
Sample 1Sample 2Sample 3See All (8)
SYSTEM AVAILABILITY SLA AND CREDITS. 2.1. Credit If SAP fails to meet the System Availability SLA for a particular Month, Customer may claim a Credit, which Customer may apply to a future invoice relating to the Cloud Service that did not meet the System Availability SLA (subject to Sections 2.1.1 and
Sample 1Sample 2Sample 3See All (5)
SYSTEM AVAILABILITY SLA AND CREDITS. SLA Ketersediaan Sistem dan Kredit 3.1 Claim process, Reports/ Proses Klaim, Laporan-laporan 3.2 System Availability/ Ketersediaan Sistem
Sample 1Sample 2Sample 3
SYSTEM AVAILABILITY SLA AND CREDITS. 3.1 Claim process, Reports.
Sample 1Sample 2
SYSTEM AVAILABILITY SLA AND CREDITS. 2.1. Credit If AN ISLAND fails to meet the System Availability SLA for a particular Month, Customer may claim a Credit, which Customer may applyto a future invoice relating to the Cloud Service that did not meet the System Availability SLA (subject to Sections 2.1.1 and
Sample 1
SYSTEM AVAILABILITY SLA AND CREDITS. 3. 시스템 가용도 SLA 및 크레딧 3.1 Claim process, Reports 3.1 청구 절차, 보고서 Customer may claim a credit in the amount described in the table of Section 3.2 below in case of SAP’s failure to meet the System Availability SLA, which credit Customer may apply to a future invoice relating to the Cloud Service that did not meet the System Availability SLA. SAP가 시스템 가용도 SLA를 달성하지 못한 경우, 고객은 아래 제3.2항의 표에 명시된 금액에서 크레딧을 청구할 수 있으며, 이 크레딧을 시스템 가용도 SLA가 달성되지 않았던 클라우드 서비스와 관련된 향후 청구서에 적용할 수 있습니다. Claims under this Service Level Agreement must be made in good faith and by submitting a support case within thirty (30) business days after the end of the relevant Month in which SAP did not meet the System Availability SLA. 본 서비스 수준 계약에 따른 청구는 SAP가 시스템 가용도 SLA를 달성하지 못했던 해당 역월이 끝난 후 삼십(30) 근무일 내에 지원 사례를 제출함으로써 성실하게 이루어져야 합니다. SAP will provide to customers a monthly report describing the System Availability percentage for the applicable Cloud Service either (i) by email following a customer’s request to its assigned SAP account manager, (ii) through the Cloud Service or (iii) through an online portal made available to customers, if and when such online portal becomes available. SAP는 (i) 고객이 자신에게 배정된 SAP 계정 관리자에게 요청 시 이메일을 통해서, (ii) 클라우드 서비스를 통해서, 또는 (Iii) 고객이 이용할 수 있도록 만든 온라인 포털을 통해서 (그러한 온라인 포털을 이용할 수 있게 되었을 때 또는 경우) 고객에게 해당 클라우드 서비스에 대한 시스템 가용도 비율을 설명하는 월별 보고서를 제공합니다. 3.2 System Availability 3.2 시스템 가용도 (i) 아래 제4조에 설명되어 있는 정규 정기 유지보수를 위한 예정된 다운타임, 또는 (ii) 제4조에 따라 해당 예정된 다운타임의 최소 오(5) 근무일 전 고객에게 통지된 기타 예정된 다운타임 또는 (iii) 합리적인 주의를 기울여도 피할 수 없는 예측하거나 예상할 수 없는 이벤트와 같이 SAP의 합리적 통제를 벗어나는 요인에 의해 야기되는 비가용성 예정된 다운타임 고객이 등록한 해당 클라우드 서비스의 예정된 다운타임은 “클라우드 서비스를 위한 정기 유지보수”라는 제목으로 아래 제4조에 명시되어 있습니다.
Sample 1
AutoNDA by SimpleDocs
SYSTEM AVAILABILITY SLA AND CREDITS. 3.1. Claim process and reporting Customer may claim a credit in the amount described in the table below in case of Lobster’s failure to meet the System Availability SLA, which credit Customer may apply to a future invoice relating to the Service that did not meet the System Availability SLA. Claims under this SLA must be made in good faith and by submitting a written request within thirty (30) days after the end of the relevant Month in which Lobster did not meet the System Availability SLA. Lobster will provide to Customer a report describing the System Availability percentage for the applicable Service for a specific month upon request. System Availability percentage is calculated as follows: System Availability percentage = * 100 System Availability SLA 99.5% System Availability percentage during each Month. Credit 2% of Monthly Subscription Fee for each 1% below System Availability SLA, not to exceed 100% of Monthly Subscription Fee.
Sample 1
SYSTEM AVAILABILITY SLA AND CREDITS. 3.1. Claim process and reporting Customer may claim a credit in the amount described in the table of clause 3.2 below in case of Lobster’s failure to meet the System Availability SLA, which credit Customer may apply to a future invoice relating to the Service that did not meet the System Availability SLA. Claims under this SLA must be made in good faith and by submitting a written request within thirty (30) business days after the end of the relevant Month in which Lobster did not meet the System Availability SLA. Lobster will provide to Customer a report describing the System Availability percentage for the applicable Service for a specific month upon request.
Sample 1

Related to SYSTEM AVAILABILITY SLA AND CREDITS

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

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