Root-Cause Analysis and Resolution. Promptly, but in no event later than five (5) calendar days after ACS’ discovery of, or if earlier, ACS’ receipt of a notice from Symetra regarding, ACS’ failure to provide any of the Services in accordance with the SLRs, ACS shall, as applicable under the circumstances: (i) perform a Root-Cause Analysis to identify the cause of such failure; (ii) provide Symetra with a written report detailing the cause of, and procedure for correcting, such failure; and (iii) provide Symetra with satisfactory evidence that such failure will not recur. ACS’ correction of any such failures shall be performed in accordance with the time frames set forth in the applicable Schedule 2 entirely at ACS’ expense unless it has been determined, by mutual agreement of the Parties or through the Problem-resolution process specified in this Agreement, that: (iv) Symetra (or one of its subcontractors, agents or Third Parties provided by Symetra and not managed by ACS) and/or its self-managed properties and/or systems was the predominant contributing cause of the failure and ACS could not have worked around the failure without expending a material amount of additional time or cost; or (v) Third Party software or firmware directly resulted in such failure; provided that such Third Party software or firmware: (A) was expressly approved by Symetra; (B) was implemented by ACS following its standard, rigorous, documented interoperability testing, quality assurance, user acceptance and change management processes; (C) was unknown, undocumented and unreported prior to ACS’ implementation of such Third Party software or firmware; and (D) ACS could not have worked around the failure without expending a material amount of additional time or cost. In such event: (vi) ACS shall be entitled to temporary relief from its obligation to timely comply with the affected SLR, but only to the extent and for the duration so affected; and (vii) in the case of an event described in subsection (iv), Symetra shall reimburse ACS for ACS’ expenses to correct such failure, but only to the extent Symetra caused such failure, unless the Parties otherwise mutually agree. For purposes hereof, any preexisting condition of those of Symetra’s properties and systems that are used and managed by ACS to deliver the Services shall not be deemed a contributing cause of any failure if such condition was or reasonably should have been identified in ACS’ reasonable, pre-implementation diligence processes, or as a result of ACS’ p...
Root-Cause Analysis and Resolution. Within [***] days of receipt of a written notice from AMEX in respect of (1) Vendor's [***] failure to provide the Services or (2) Vendor's repeated failure to provide any of the Services in accordance with the Service Levels, Vendor shall (a) perform a root-cause analysis to identify the cause of such failure and (b) provide AMEX with a report detailing the cause of, and procedure for correcting, such failure. Within [***] days of receipt of such notice, Vendor shall (i) commence implementation of action to remedy such failure and (ii) provide AMEX with reasonable evidence that such failure will not reoccur. The effectiveness of such remedial action must be evident to AMEX within [***] days of its implementation. If the root-cause analysis shows that the failure was caused by AMEX, then Vendor shall not be in breach of this Agreement or liable to AMEX for performance credits as a result thereof.
Root-Cause Analysis and Resolution. Within ten (10) days (or as otherwise agreed to by the Parties in writing) of receipt of a notice from Gap of Supplier’s failure to provide the Services in accordance with the Service Levels, Supplier shall (a) provide such services necessary to identify the cause of such failure, (b) provide Gap with a written report detailing the cause of, and procedures for correcting, such failure, and (c) provide Gap with reasonable evidence that applicable corrective steps have been taken. The foregoing does not limit other remedies available to Gap under this Agreement for such Service Level failures.
Root-Cause Analysis and Resolution. As soon as reasonably practicable following any material failure of either the Joint Venture or the Bank to provide any of the Services for which such Party is responsible hereunder in accordance with this Agreement and in any event within three days after receipt of a notice from a Party to the other Party in respect thereof, the defaulting Party shall commence and conduct a detailed analysis to identify the cause of such failure; and as soon as reasonably practicable thereafter provide the other Party with a written report detailing the cause of, and procedure for correcting, such failure. In addition, the defaulting Party shall deliver to the other Party, within a commercially reasonable time, a corrective action plan that addresses actions to be taken in an effort to try to avoid a recurrence of such failure.
Root-Cause Analysis and Resolution. Each of NDPS and/or GPI Canada and the Bank shall, promptly after:
Root-Cause Analysis and Resolution. Promptly, but in no event later than five (5) calendar days (unless otherwise agreed) after Service Provider’s discovery of, or if earlier, Service Provider’s receipt of a written notice or corrective action request from County regarding Service Provider’s failure to provide any of the Services in accordance with the Service Levels, Service Provider shall, as applicable under the circumstances: (i) perform a problem analysis process undertaken to identify and quantify the underlying cause(s) of a SLA failure or some other failure, and document the necessary corrective actions to be taken to prevent recurring problems and/or trends (a “Root Cause Analysis”) to identify the cause of such failure; (ii) provide County with a written report detailing the cause of, and procedure for correcting, such failure; and (iii) provide County with satisfactory evidence that such failure will not recur. The correction of any such failures shall be performed in accordance with the time frames set forth in the applicable Service Agreement and entirely at Service Provider’s expense unless it has been determined, by mutual agreement of the Parties or through the Dispute Resolution process specified in this Agreement, that County (or one of its other providers, agents or third party service providers) was the predominant contributing cause of the failure and Service Provider could not have worked around the failure without expending a material amount of additional time or cost. In such event: (iv) Service Provider shall be entitled to temporary relief from its obligation to timely comply with the affected SLA, but only to the extent and for the duration so affected; and (v) County shall reimburse Service Provider for Service Provider’s reasonable, direct and documented expenses to correct such failure, but only to the extent County caused such failure, unless the Parties otherwise mutually agree. For purposes hereof, the preexisting condition of County’s properties, systems, processes and methodologies shall not be deemed a contributing cause of any failures. The foregoing does not limit other remedies available to County under this Agreement for such Service Level failures.
Root-Cause Analysis and Resolution. Promptly, and in no event later than five (5) days after Contractor’s discovery of, or, if earlier, Contractor’s receipt of a notice from the County regarding, (i) as specified in the Standards and Procedures Manual or otherwise as requested by the County, Contractor’s failure to provide any of the Services, (ii) Contractor’s failure to meet a Transition Milestone or Critical Milestone, or
Root-Cause Analysis and Resolution. Each of NDPS and the Bank ---------------------------------- shall, promptly after:
Root-Cause Analysis and Resolution. Within ten (10) days (or as otherwise agreed to by the Parties in writing) of IBM’s failure to provide the Services in accordance with the Service Levels, IBM shall (a) perform root cause analysis to identify the cause of such failure, (b) provide VMU with a written report detailing the cause of, and procedures for correcting, such failure, (c) provide VMU with reasonable evidence that applicable corrective steps have been taken; and (d) provide VMU with assurance satisfactory to VMU that such failure will not recur after the procedure has been completed. The foregoing does not limit other remedies available to VMU or otherwise excuse IBM from its Service Level obligations under this Agreement for such Service Level failures.
Root-Cause Analysis and Resolution. As part of the Services, within two (2) Business Days of: (i) SAVVIS' material failure to provide any of the Services in accordance with the Service Levels, or (ii) SAVVIS' repeated failure to provide any of the Services in accordance with the Service Levels, SAVVIS shall (a) perform an analysis to identify the cause of such failure, (b) correct such failure if within the scope of the Services, (c) provide Moneyline with a report, including direct electronic access to the CRM Trouble Ticket and/or affected Work Order. Within three (3) Business Days of this report under subsection (c), SAVVIS shall provide additional reporting detailing the cause of, and procedure for correcting, such failure, (d) compare such failures mean time to repair ("MTTR") to the expected MTTR for such failures, and (e) discuss and agree to implement changes to Circuits, Systems, or procedures that both parties agree shall improve the likelihood of avoiding or lengthening the time between such failures known as Mean Time To Failure.
