Excused Events Sample Clauses

POPULAR SAMPLE Copied 1 times
Excused Events. 17 7.8 Establishment of Performance Standards Applicable to Managed Data Network Services (MDNS).....
Excused Events. Any failure by ▇▇▇▇▇ to meet the KPI Target is excused to the extent to which it is caused by:
Excused Events. FIS will not be obligated or liable for a Service Level default that is attributable to any of the events listed below in this Section (each an “Excused Event”), although FIS will use commercially reasonable efforts to resume the Services after any Excused Event. FIS shall document the Excused Event and provide sufficient supporting information for Client to review and validate FIS’s determination. To the extent any non-availability or Incident would otherwise constitute a Service Level default but is attributable to circumstances that constitute an Excused Event, then notwithstanding anything to the contrary in this or any other Schedule to the Agreement or elsewhere, FIS shall be excused from any obligations to meet the corresponding Service Level associated with such Service Level default. 5.1.1 Equipment and Software owned or licensed by Client and managed by FIS, for which Client has elected not to pay maintenance; or Client pays maintenance and the vendor is unwilling or unable to support the Equipment or Software; in each case to the extent the lack of maintenance caused or contributes to the Service Level Event;
Excused Events. The following types of events are excluded from the calculation of the KPI:
Excused Events. IBM will be excused from a failure to provide a Service in accordance with this Schedule B if and to the extent that: (a) such failure is excused as a Force Majeure Event pursuant to Section 19.3 of the Agreement; or (b) such failure is caused by (i) an action or omission of MSDW, or (ii) an action or omission of MSDW's third party vendors to the extent that such action or omission is not within the scope of those management or other responsibilities that IBM has assumed under the Agreement with respect to such third party vendors that materially adversely affects IBM's ability to perform the Services hereunder or to meet its obligations in a timely manner, and to the extent upon learning of such problem IBM: (i) promptly notifies MSDW of the problem and, if known, the acts or omissions believed to be causing such problem and their ramifications; (ii) promptly takes commercially reasonable steps to mitigate the adverse impact of the acts or omissions on the Services; and (iii) works with MSDW or such third party vendor(s) (if any) diligently and in good faith to avoid, minimize and circumvent such problem or delay to the Services. MSDW, upon learning of any problem which may adversely impact or affect the Services, will: (i) promptly notify IBM of the problem and, if known, of the acts or omissions believed to be causing such problem and their ramifications; (ii) promptly take commercially reasonable steps to mitigate the adverse impact of the acts or omissions on the Services; and (iii) work with IBM and instruct its third party vendor(s) (if any) to work with IBM diligently and in good faith to avoid, minimize and circumvent such problem or delay.

Related to Excused Events

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”): 1. the Recipient has amounts owing to the IESO in respect of another funding agreement or other program, contract or arrangement with the IESO that have not been paid after due notice; 2. the IESO notifies the Recipient that it is in default of any existing agreements with the IESO, its predecessor entities, or any of their third party funds managers, including funding agreements; 3. the Recipient fails to complete or submit to the IESO any Activities set out in Schedule C by the applicable Target Completion Date; or 4. the Recipient fails to notify the IESO of any of the events set out in Section 6.1. (b) Should a Default Event occur, the IESO will be entitled to deliver to the Recipient a written notice that the Recipient is in default of the obligations under the Funding Agreement (the “Notice of Default”). The Notice of Default will set out the nature of the Default Event and a reasonable period of time by which the Default Event must be cured.

  • Termination Events If the Early Termination Date results from a Termination Event:—

  • Force Majeure Events a) Neither Party shall be responsible or liable for or deemed in breach hereof because of any delay or failure in the performance of its obligations hereunder (except for obligations to pay money due prior to occurrence of Force Majeure events under this Agreement) or failure to meet milestone dates due to any event or circumstance (a "Force Majeure Event") beyond the reasonable control of the Party experiencing such delay or failure, including the occurrence of any of the following: i) acts of God; ii) typhoons, floods, lightning, cyclone, hurricane, drought, famine, epidemic, plague or other natural calamities; iii) acts of war (whether declared or undeclared), invasion or civil unrest; iv) any requirement, action or omission to act pursuant to any judgment or order of any court or judicial authority in India (provided such requirement, action or omission to act is not due to the breach by the SPG or of any Law or any of their respective obligations under this Agreement); v) inability despite complying with all legal requirements to obtain, renew or maintain required licenses or Legal Approvals; vi) earthquakes, explosions, accidents, landslides; fire; vii) expropriation and/or compulsory acquisition of the Project in whole or in part by Government Instrumentality; viii) chemical or radioactive contamination or ionizing radiation; or ix) damage to or breakdown of transmission facilities of GETCO/ DISCOMs; x) Exceptionally adverse weather condition which are in excess of the statistical measure of the last hundred (100) years.

  • Acceleration Events Each of the following events shall constitute an “Acceleration Event”:

  • Triggering Events The events referred to in Sections 3(f) and 5(a) hereof are as follows: