Election by non-Operator Sample Clauses

Election by non-Operator. The non-Operator may elect, on delivering notice in writing to the Operator within 60 days of the approval of each Program by the Management Committee, to participate in the Program to the extent of the non-Operator's then Joint Venture Interest (but not to any lesser extent).
Sample 1Sample 2
AutoNDA by SimpleDocs
Election by non-Operator. (1) After the Hoidas Lake Option Period, the non-Operator may elect, on delivering notice in writing to the Operator within 30 days following the approval of any Program and Budget by the JV Management Committee (including any alteration to any Program and Budget), to participate in the Program and Budget up to the extent of the non-Operator’s then Hoidas Lake Joint Venture Interest (but not to any lesser extent). If the non-Operator does not give such notice then: (a) except where that notice is given after the Operator has adopted an alteration to a Program and Budget, it shall not be entitled or obliged to contribute to Joint Venture Expenditure incurred from the commencement of the period covered by the Budget in relation to which the notice was given until it becomes entitled and obliged to recommence contributing to Joint Venture Expenditure by operation of Section 6.3(1) of this Hoidas Lake JV Agreement, and such period for which a Participant is not entitled nor obliged to so contribute (either at all or in full), such Participant’s Hoidas Lake Joint Venture Interest shall dilute as provided for in Section 3.4 of this Hoidas Lake JV Agreement; and (b) in the case where the Operator has adopted an alteration to a Budget, it shall not be entitled or obliged to contribute to Joint Venture Expenditure from the date on which the Joint Venture Expenditure incurred in carrying out that Budget reaches the total amount budgeted for Joint Venture Expenditure in that Budget before it was so altered until it becomes entitled and obliged to recommence contributing to Joint Venture Expenditure by operation of Section 6.3(1) of this Hoidas Lake JV Agreement, and during such period for which a Participant is not entitled nor obliged to so contribute (either at all or in full), such Participant’s Hoidas Lake Joint Venture Interest shall dilute as provided for in Section 3.4 of this Hoidas Lake JV Agreement.
Sample 1

Related to Election by non-Operator

  • Termination by Owner The Owner may terminate this Agreement in whole or in part, for the failure of the Consultant to: 1) Perform the services within the time specified in this contract or by Owner approved extension; 2) Make adequate progress so as to endanger satisfactory performance of the Project; 3) Fulfill the obligations of the Agreement that are essential to the completion of the Project. Upon receipt of the notice of termination, the Consultant must immediately discontinue all services affected unless the notice directs otherwise. Upon termination of the Agreement, the Consultant must deliver to the Owner all data, surveys, models, drawings, specifications, reports, maps, photographs, estimates, summaries, and other documents and materials prepared by the Engineer under this contract, whether complete or partially complete. Owner agrees to make just and equitable compensation to the Consultant for satisfactory work completed up through the date the Consultant receives the termination notice. Compensation will not include anticipated profit on non-performed services. Owner further agrees to hold Consultant harmless for errors or omissions in documents that are incomplete as a result of the termination action under this clause. If, after finalization of the termination action, the Owner determines the Consultant was not in default of the Agreement, the rights and obligations of the parties shall be the same as if the Owner issued the termination for the convenience of the Owner.

  • Termination by Registry Operator (a) Registry Operator may terminate this Agreement upon notice to ICANN if (i) ICANN fails to cure any fundamental and material breach of ICANN’s covenants set forth in Article 3, within thirty (30) calendar days after Registry Operator gives ICANN 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 ICANN is in fundamental and material breach of such covenants, and (iii) ICANN 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) Registry Operator may terminate this Agreement for any reason upon one hundred eighty (180) calendar day advance notice to ICANN.

  • Termination by Manager Manager shall have the right to terminate this Agreement at any time, with or without cause, upon sixty (60) days written notice to Owner. Manager shall also have the right to terminate this Agreement upon thirty (30) days written notice to Owner for non-payment of fees and expenses due Manager under the terms of this Agreement

  • Termination by Notice Notwithstanding any provision of this Agreement, it may be terminated at any time without penalty, by the Trustees of the Trust or, with respect to any series or class of the Trust's shares, by the vote of the majority of the outstanding voting securities of such series or class, or by MM-LLC, upon thirty days written notice to the other party.

  • 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 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 Lessee Subject to Subparagraph 18D, and without limiting any other rights and remedies to which Lessee may be entitled by common law, statutory law, or as elsewhere provided in this Lease, this Lease may be terminated by Lessee at any time after the happening, and during the existence, of one of more of the following events: i. The City’s permanent abandonment of the Premises at the Airport; ii. The lawful assumption by the United States Government, or any authorized agency thereof, of the operation, control, or use of the Airport, or any substantial part or parts thereof, that substantially restricts any sublessee from operating for at least one hundred fifty (150) calendar days; iii. The issuance by any court of competent jurisdiction of an injunction that prevents or restrains the use of the Airport or the Premises, that continues for at least one hundred fifty (150) calendar days; iv. The default by the City in the performance of any covenant or obligation on the part of the City to be performed, and the failure of the City to remedy the default for sixty (60) calendar days after receipt from Lessee of written notice to remedy the same; or v. Lessee’s decision to terminate the Lease as provided in Paragraph 11(B) of the Lease.

  • Termination by Xxxxx 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 Contractor Contractor may, at its option, terminate this Contract upon the failure of MPS to pay any amount, which may become due hereunder for a period of sixty (60) days following submission of appropriate billing and supporting documentation. Upon said termination, Contractor shall be paid the compensation due for all services rendered through the date of termination including any retainage.

  • TERMINATION BY MPS MPS further reserves the right to terminate this Contract at any time for any reason by giving Contractor written notice by Registered or Certified Mail of such termination. MPS will attempt to give Contractor 20 days’ notice, but reserves the right to give immediate notice. In the event of said termination, Contractor shall reduce its activities hereunder, as mutually agreed to, upon receipt of said notice. Upon said termination, Contractor shall be paid for all services rendered through the date of termination, including any retainage. This section also applies should the Milwaukee Board of School Directors fail to appropriate additional monies required for the completion of the Contract.

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