Termination by FCERA for Service Level Failure Sample Clauses

Termination by FCERA for Service Level Failure. FCERA may terminate this Agreement and any SOWs, in whole in part, by providing notice of such termination to TEGRIT, upon the occurrence of any of the following: (i) Failure of the same service level in three (3) or more consecutive months; (ii) Ten (10) or more Failures in a rolling six (6)-month period; or (iii) Fifteen (15) or more Failures in any rolling twelve (12)-month period. As used in this Section 11(g), "Failure" means any separate instance in which a service credit is owed TEGRIT to FCERA under Schedule C (Service Level Agreement (SLA)).
Sample 1
AutoNDA by SimpleDocs

Related to Termination by FCERA for Service Level Failure

  • Termination for Force Majeure 15.5.1. The License Agreement may be terminated for Force Majeure Reasons as specified in Article -14.

  • Termination for continuing Force Majeure Event Either Party may, by written notice to the other, terminate this Framework Agreement if a Force Majeure Event endures for a continuous period of more than one hundred and twenty (120) Working Days.

  • Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.

  • Termination due to Force Majeure 13.5.1 If the Force Majeure Event or its effects continue to be present beyond the period as specified in Article 4.5.3, either Party shall have the right to cause termination of the Agreement. In such an event, this Agreement shall terminate on the date of such Termination Notice.

  • Termination by CAISO Subject to Section 5.2, the CAISO may terminate this Agreement by giving written notice of termination in the event that the Participating Load commits any material default under this Agreement and/or the CAISO Tariff which, if capable of being remedied, is not remedied within thirty (30) days after the CAISO has given, to the Participating Load, written notice of the default, unless excused by reason of Uncontrollable Forces in accordance with Article X of this Agreement. With respect to any notice of termination given pursuant to this Section, the CAISO must file a timely notice of termination with FERC, if this Agreement was filed with FERC, or must otherwise comply with the requirements of FERC Order No. 2001 and related FERC orders. The filing of the notice of termination by the CAISO with FERC will be considered timely if: (1) the filing of the notice of termination is made after the preconditions for termination have been met, and the CAISO files the notice of termination within sixty (60) days after issuance of the notice of default; or (2) the CAISO files the notice of termination in accordance with the requirements of FERC Order No. 2001. This Agreement shall terminate upon acceptance by FERC of such a notice of termination, if filed with FERC, or thirty (30) days after the date of the CAISO’s notice of default, if terminated in accordance with the requirements of FERC Order No. 2001 and related FERC orders.

  • Termination by ICANN (a) ICANN may, upon notice to Registry Operator, terminate this Agreement if: (i) Registry Operator fails to cure (A) any fundamental and material breach of Registry Operator’s representations and warranties set forth in Article 1 or covenants set forth in Article 2, or (B) any breach of Registry Operator’s payment obligations set forth in Article 6 of this Agreement, each within thirty (30) calendar days after ICANN gives Registry Operator notice of such breach, which notice will include with specificity the details of the alleged breach, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in fundamental and material breach of such covenant(s) or in breach of its payment obligations, and (iii) Registry Operator fails to comply with such determination and cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (b) ICANN may, upon notice to Registry Operator, terminate this Agreement if Registry Operator fails to complete all testing and procedures (identified by ICANN in writing to Registry Operator prior to the date hereof) for delegation of the TLD into the root zone within twelve (12) months of the Effective Date. Registry Operator may request an extension for up to additional twelve (12) months for delegation if it can demonstrate, to ICANN’s reasonable satisfaction, that Registry Operator is working diligently and in good faith toward successfully completing the steps necessary for delegation of the TLD. Any fees paid by Registry Operator to ICANN prior to such termination date shall be retained by ICANN in full. (c) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator fails to cure a material breach of Registry Operator’s obligations set forth in Section 2.12 of this Agreement within thirty (30) calendar days of delivery of notice of such breach by ICANN, or if the Continued Operations Instrument is not in effect for greater than sixty (60) consecutive calendar days at any time following the Effective Date, (ii) an arbitrator or court of competent jurisdiction has finally determined that Registry Operator is in material breach of such covenant, and (iii) Registry Operator fails to cure such breach within ten (10) calendar days or such other time period as may be determined by the arbitrator or court of competent jurisdiction. (d) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator makes an assignment for the benefit of creditors or similar act, (ii) attachment, garnishment or similar proceedings are commenced against Registry Operator, which proceedings are a material threat to Registry Operator’s ability to operate the registry for the TLD, and are not dismissed within sixty (60) calendar days of their commencement, (iii) a trustee, receiver, liquidator or equivalent is appointed in place of Registry Operator or maintains control over any of Registry Operator’s property, (iv) execution is levied upon any material property of Registry Operator, (v) proceedings are instituted by or against Registry Operator under any bankruptcy, insolvency, reorganization or other laws relating to the relief of debtors and such proceedings are not dismissed within sixty (60) calendar days of their commencement, or (vi) Registry Operator files for protection under the United States Bankruptcy Code, 11 U.S.C. Section 101, et seq., or a foreign equivalent or liquidates, dissolves or otherwise discontinues its operations or the operation of the TLD. (e) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement pursuant to Section 2 of Specification 7 or Sections 2 and 3 of Specification 11, subject to Registry Operator’s right to challenge such termination as set forth in the applicable procedure described therein. (f) ICANN may, upon notice to Registry Operator, terminate this Agreement if (i) Registry Operator knowingly employs any officer who is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such officer is not terminated within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing, or (ii) any member of Registry Operator’s board of directors or similar governing body is convicted of a misdemeanor related to financial activities or of any felony, or is judged by a court of competent jurisdiction to have committed fraud or breach of fiduciary duty, or is the subject of a judicial determination that ICANN reasonably deems as the substantive equivalent of any of the foregoing and such member is not removed from Registry Operator’s board of directors or similar governing body within thirty (30) calendar days of Registry Operator’s knowledge of the foregoing. (g) ICANN may, upon thirty (30) calendar days’ notice to Registry Operator, terminate this Agreement as specified in Section 7.5. (h) [Applicable to intergovernmental organizations or governmental entities only.] ICANN may terminate this Agreement pursuant to Section 7.16.

  • TERMINATION BY MPS - BREACH BY CONTRACTOR If Contractor fails to fulfill its obligations under this Contract in a timely or proper manner, or violates any of its provisions, MPS shall thereupon have the right to terminate it by giving five (5) days written notice before the effective date of termination of the Contract, specifying the alleged violations, and effective date of termination. The Contract shall not be terminated if, upon receipt of the notice, Contractor promptly cures the alleged violation with five (5) days. In the event of termination, MPS will only be liable for services rendered through the date of termination and not for the uncompleted portion, or for any materials or services purchased or paid for by Contractor for use in completing the Contract.

  • TERMINATION FOR CAUSE BY CONTRACTOR 4.06.1 Contractor may terminate its performance under this Agreement only if the City defaults and fails to cure the default after receiving written notice of it. Default by the City occurs if the City fails to perform one or more of its material duties under this Agreement. If a default occurs and Contractor wishes to terminate the Agreement, then Contractor must deliver a written notice to the Director describing the default and the proposed termination date. The date must be at least 30 days after the Director receives the notice. Contractor, at its sole option, may extend the proposed termination date to a later date. If the City cures the default before the proposed termination date, then the proposed termination is ineffective. If the City does not cure the default before the proposed termination date, then Contractor may terminate its performance under this Agreement on the termination date

  • SUSPENSION & TERMINATION FOR DEFAULT Enterprise Services may suspend Contractor’s operations under this Master Contract immediately by written cure notice of any default. Suspension shall continue until the default is remedied to Enterprise Services’ reasonable satisfaction; Provided, however, that, if after thirty (30) days from such a suspension notice, Contractor remains in default, Enterprise Services may terminate Contractor’s rights under this Master Contract. All of Contractor’s obligations to Enterprise Services and Purchasers survive termination of Contractor’s rights under this Master Contract, until such obligations have been fulfilled.

  • Termination for Material Breach Either Party (the “Terminating Party”) may terminate this Agreement in its entirety, or on a country-by-country and Product-by-Product basis, in the event the other Party (the “Breaching Party”) has materially breached this Agreement, and such material breach has not been cured within sixty (60) days after receipt of written notice of such breach by the Breaching Party from the Terminating Party (the “Cure Period”). The written notice describing the alleged material breach shall provide sufficient detail to put the Breaching Party on notice of such material breach. Any termination of this Agreement pursuant to this Section 10.3 shall become effective at the end of the Cure Period, unless the Breaching Party has cured any such material breach prior to the expiration of such Cure Period; provided that in the event a claim of material breach is being contested diligently and in good faith by appropriate proceedings hereunder, any termination pursuant to this Section shall not become effective unless and until such material breach has been established in such proceedings and, in the event that, following such establishment, a cure may then be accomplished by the payment of money or the taking of certain actions, such payment or actions are not paid or taken within sixty (60) days of the conclusion of such proceedings. The right of either Party to terminate this Agreement as provided in this Section 10.3 shall not be affected in any way by such Party’s waiver of or failure to take action with respect to any previous breach under this Agreement.

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