Common use of Service Level Reporting Clause in Contracts

Service Level Reporting. 4.1. SAP shall track and report to Customer the Service Levels set forth herein in a monthly summary report. 4.2. In the event that one or more of the Service Levels set forth herein are not met, Customer may notify the assigned SAP account manager and request to analyze the Service Level metric statistics based on the monthly summary report provided by SAP. 4.3. SAP will then promptly: 4.3.1. determine the root cause or possible root cause of the failure (if known) to meet the Service Level; and 4.3.2. unless failure is excused, develop a corrective action plan, and submit such plan to Customer for written approval (which will not be unreasonably withheld or delayed) and, following Customer’s written approval implement the plan in a reasonable period of time (and in accordance with any agreed timescales). 4.4. If applicable, SAP will provide the specific Credit as described in Section 5 below. 4.5. SAP will be relieved of its obligation to pay any applicable Credits and will not be in breach of the Service Level where the root cause analysis (as reasonably performed by SAP) indicates the failure to meet the relevant Service Level was caused by Customer and shall therefore be treated as Excluded Downtime. In the event that Customer disagrees with the root cause analysis, the parties will discuss the root cause analysis.

Service Level Reporting. 4.1. 서비스 수준 보고 4.1 Customer must notify SAP shall track and of any claims for any Service Credits within one (1) month after receipt of the monthly System Availability report to Customer the Service Levels set forth herein in by filing a monthly summary reportsupport ticket with SAP. 4.2. 4.2 In the event that one or more of the Service Services Levels set forth herein are not met, Customer may notify the assigned SAP account manager Account Manager and request to analyze the Service Level Levels metric statistics based on the monthly summary report provided by SAP. 4.3. 4.3 SAP will then promptly: 4.3.1. promptly (i) determine the root cause or possible root cause of the failure (if known) to meet the Service Level; and 4.3.2. , and (ii) unless failure is excused, develop a corrective action plan, and submit such plan to Customer for written approval (which will not be unreasonably withheld or delayed) and, following Customer’s written approval implement the plan in a reasonable period of time (and in accordance with any agreed timescales). 4.4. 4.4 If applicable, SAP will provide the specific Service Credit as described in Section 5 below. 4.5. 4.5 SAP will be relieved of its obligation to pay any applicable Service Credits and will not be in breach of the Service Level where the root cause analysis (as reasonably performed by SAP) indicates the failure to meet the relevant Service Level was caused by the Customer and shall therefore be treated as Excluded Downtime. In the event that Customer disagrees with the root cause analysis, the parties will discuss the root cause analysis.