Root Cause Analysis. Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.
Root Cause Analysis. 13.1. Freshwave shall, perform a root cause analysis on any Chronic Outage or any material or persistent problem affecting the Services and provide Customer with a summary of such analysis upon request.
Root Cause Analysis. In the event of the Contractor's failure to perform required services or meet agreed upon service levels or other Contractor service standards as required by the State under this Contract, the Contractor shall perform an analysis of the cause of the service level problem and implement remediation steps as appropriate. The State shall have the right to review the analysis and approve the remediation steps prior to or subsequent to their implementation, as deemed appropriate by the State, if the remediation steps impact State assets or operational processes.
Root Cause Analysis. In the event Ridge Local Affiliate has a Service Level failure that is not insignificant, Ridge Local Affiliate shall perform a root-cause analysis as described in Section 1.C of the Master Services Agreement.
Root Cause Analysis. Upon receipt of a notice from Novation or any of the Alliances of Service Provider’s failure to provide the Services in accordance with this Agreement or upon Service Provider’s knowledge of a failure to provide the Services in accordance with this Agreement, Service Provider shall, as soon as reasonably practicable, (i) perform a root-cause analysis to identify the cause of such failure and (ii) provide Novation and each of the Alliances with a report detailing the cause of, and procedure for correcting, such failure. If the root cause of such failure is due to the fault of Service Provider (whether determined pursuant to the foregoing or pursuant to Section 17), Service Provider will implement such procedure and provide Novation and the Alliances with reasonable assurance that such failure will not recur; provided that Novation and each of the Alliances shall retain any and all applicable rights and remedies hereunder with respect to such failure. If Service Provider concludes that the root cause of such failure is due to the fault of any Person other than Service Provider, Service Provider shall promptly give Novation and each of the Alliances notice of, and information supporting, such conclusion, subject to Novation’s and the Alliances’ right to disagree with Service Provider’s conclusion and to have the root cause determined in accordance with Section 17. The Parties shall submit to the process set forth in Section 17 any Disputed Matter regarding the root cause of any such failure to provide the Services in accordance with the applicable Service Levels.
Root Cause Analysis. Following the resolution of a Severity Level 1 OR Level 2 incident, Contractor will discuss with City the cause of the failure, the actions Contractor took to resolve the failure, a timeline of the event and the actions Contractor plans to take to prevent such failure from recurring, and, if requested, Contractor will provide City a written summary of such discussion. Contractor will, on request, provide detailed documentation of the root cause analysis and preventative actions taken or planned with clear dates for completion of the action(s).
Root Cause Analysis. Service Provider’s responsibilities include:
1. Effective execution of Root Cause Analysis (RCA) in compliance with the processes defined in the Service Management Manual.
2. Provide for an RCA Coordinator to act as the day-to-day interface into the RCA process.
3. Initiate RCA for all Incidents not resolved within Service Levels.
4. Provide a process for DIR and DIR Customers to request an RCA.
4.1. Track all such requests and provide status.
5. Assign RCAs to a specific RCA Analyst to facilitate data gathering, interviews, analysis, and formulation of report.
6. Ensure that all appropriate roles are engaged to perform RCA tasks.
7. Document the RCA activity and outcomes in records associated with Problems, Known Errors, workarounds and Major Problem reviews, including the following at a minimum:
7.1. Identification of associated Problem / Known Error record.
7.2. Details of action taken to analyze the Root Cause, including details regarding the use of standard problem analysis tools.
7.3. Details of findings from analysis of Root Cause.
7.4. Details of business impact resulting from the Root Cause.
7.5. Details regarding all services, systems, components, etc. effected by the Root Cause.
7.6. Details regarding any considerations that should be included in business cases and cost benefit analyses.
7.7. Provide tracking and reporting of RCA actions to completion.
8. Track open RCAs and identify any RCA that requires increased focus to meet committed service levels.
9. Accomplish Root Cause Analysis, as documented in the Service Management Manual, and which should include processes for:
9.1. Addressing the primary root causes of Problems
9.2. Investigating and identifying the root cause of the Problem in order to transform the Problem to a Known Error.
9.3. Take all available information for a Problem Resolution, analyze it, formulate a hypothesis of the actual cause, promote peer review, adjust as needed, and finally close the acceptable investigation.
9.4. Minimize the duration of Problems.
9.5. Reduce the number of Problems.
9.6. Minimize Problem life cycles.
9.7. Optimize time and effort spent resolving Problems.
9.8. Identify and address any contributing factors which increased the duration of the outage.
9.9. Prevent recurrence of Incidents and Problems.
9.10. Identify, address and implement all possible and reasonable preventive actions to permanently resolve the Problem and any contributing factors to prevent recurrence.
9.11. Providing useful infor...
Root Cause Analysis. With respect to any (a) AMD failure to provide the Services in accordance with the applicable Service Levels that gives rise to a Severity Level 1 failure (as defined in Exhibit 6.4), or (b) AMD failure to provide the Services in accordance with the applicable Service Levels that gives rise to a repeated Severity Level 2 failure (as defined in Exhibit 6.4), AMD shall, as soon as reasonably practicable, (x) perform a root-cause analysis to identify the cause of such failure or incident, (y) provide Spansion with a report detailing the cause of, and procedure for correcting, such failure or incident, and (z) implement such procedure for correcting such failure or incident.
Root Cause Analysis. Following the resolution of a Severity Level 1 OR Level 2 incident, Contractor will discuss with City the cause of the failure, the actions Contractor took to resolve the failure, a timeline of the event and the actions Contractor plans to take to prevent such failure from recurring, and, if requested, Contractor will provide City a written summary of such discussion. Contractor will, on request, provide detailed documentation of the root cause analysis and preventative actions taken or planned with clear dates for completion of the action(s).
A. Time is of the Essence. For the term of this Agreement, Contractor shall provide SaaS Services, Force Majeure events excepted, during the applicable Service Windows and in accordance with the applicable Service Levels as described herein, time being of the essence.
Root Cause Analysis. In the event of an Epidemic Failure or Product Recall, as described in Sections 21 and 22 above, Supplier shall use its best efforts to (i) identify the root cause of any such product failure or non-conformance (“Defect”) of any product supplied by Supplier to Leviton and (ii) propose a resolution, fix solution, or other acceptable and reasonable remedy to correct or eliminate the Defect. If Supplier refuses or unreasonably delays its response to a notification from Leviton of a Defect, then Supplier shall be liable to Leviton for all costs associated with the product failures, including the costs associated with replacing the defective products, including labor and shipping costs, and the costs of an independent laboratory hired by Leviton to examine the failed Products.
