Where a Review Event occurs Sample Clauses

Where a Review Event occurs. (a) QR Network must, within sixty (60) days of QR Network knowing that a Review Event has occurred, submit a variation of the relevant Reference Tariff (including evidence that the Review Event has occurred and details of the methodology, data and assumptions used to vary the Reference Tariff);
AutoNDA by SimpleDocs

Related to Where a Review Event occurs

  • Termination Payment for Force Majeure Event 34.9.1 If Termination is on account of a Non-Political Event, the Authority shall make a Termination Payment to the Concessionaire in an amount equal to 90% (ninety per cent) of the Debt Due less Insurance Cover.

  • Termination due to Event of Default (a) Termination due to Parties Event of Default

  • 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.

  • Contract Renegotiation, Suspension, or Termination Due to Change in Funding If the funds DSHS relied upon to establish this Contract or Program Agreement are withdrawn, reduced or limited, or if additional or modified conditions are placed on such funding, after the effective date of this contract but prior to the normal completion of this Contract or Program Agreement:

  • Termination Notice for Force Majeure Event If a Force Majeure Event subsists for a period of 180 (one hundred and eighty) days or more within a continuous period of 365 (three hundred and sixty five) days, either Party may in its discretion terminate this Agreement by issuing a Termination Notice to the other Party without being liable in any manner whatsoever, save as provided in this Article 34, and upon issue of such Termination Notice, this Agreement shall, notwithstanding anything to the contrary contained herein, stand terminated forthwith; provided that before issuing such Termination Notice, the Party intending to issue the Termination Notice shall inform the other Party of such intention and grant 15 (fifteen) days time to make a representation, and may after the expiry of such 15 (fifteen) days period, whether or not it is in receipt of such representation, in its sole discretion issue the Termination Notice.

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

  • Payment in the Event Losses Fail to Reach Expected Level On the date that is 45 days following the last day (such day, the “True-Up Measurement Date”) of the Final Shared Loss Month, or upon the final disposition of all Shared Loss Assets under this Single Family Shared-Loss Agreement at any time after the termination of the Commercial Shared-Loss Agreement, the Assuming Institution shall pay to the Receiver fifty percent (50%) of the excess, if any, of (i) twenty percent (20%) of the Intrinsic Loss Estimate less (ii) the sum of (A) twenty-five percent (25%) of the asset premium (discount) plus (B) twenty-five percent (25%) of the Cumulative Shared-Loss Payments plus (C) the Cumulative Servicing Amount. The Assuming Institution shall deliver to the Receiver not later than 30 days following the True-Up Measurement Date, a schedule, signed by an officer of the Assuming Institution, setting forth in reasonable detail the calculation of the Cumulative Shared-Loss Payments and the Cumulative Servicing Amount.

  • Notice of Event of Default If the Mortgagee shall have Actual Knowledge of an Event of Default or of a Default arising from a failure to pay Rent, the Mortgagee shall give prompt written notice thereof to the Owner Trustee, the Owner Participant, Lessee, and each Note Holder. Subject to the terms of Sections 2.13, 4.03, 4.04, 4.08, 5.02 and 5.03 hereof, the Mortgagee shall take such action, or refrain from taking such action, with respect to such Event of Default or Default (including with respect to the exercise of any rights or remedies hereunder) as the Mortgagee shall be instructed in writing by a Majority in Interest of Note Holders. Subject to the provisions of Section 5.03, if the Mortgagee shall not have received instructions as above provided within 20 days after mailing notice of such Event of Default to the Note Holders, the Mortgagee may, subject to instructions thereafter received pursuant to the preceding provisions of this Section 5.01, take such action, or refrain from taking such action, but shall be under no duty to take or refrain from taking any action, with respect to such Event of Default or Default as it shall determine advisable in the best interests of the Note Holders; PROVIDED, HOWEVER, that the Mortgagee may not sell the Aircraft or any Engine without the consent of a Majority in Interest of Note Holders. For all purposes of this Trust Indenture, in the absence of Actual Knowledge on the part of the Mortgagee, the Owner Trustee or the Owner Participant, the Mortgagee, the Owner Trustee or the Owner Participant, as the case may be, shall not be deemed to have knowledge of a Default or an Event of Default (except, in the case of the Mortgagee, the failure of Lessee to pay any installment of Basic Rent within one Business Day after the same shall become due, if any portion of such installment was then required to be paid to the Mortgagee, which failure shall constitute knowledge of a Default) unless notified in writing by Lessee, the Owner Trustee, the Owner Participant or one or more Note Holders.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.

  • Termination for Concessionaire Default 37.1.1 Save as otherwise provided in this Agreement, in the event that any of the defaults specified below shall have occurred, and the Concessionaire fails to cure the default within the Cure Period set forth below, or where no Cure Period is specified, then within a Cure Period of 60 (sixty) days, the Concessionaire shall be deemed to be in default of this Agreement (the “Concessionaire Default”), unless the default has occurred solely as a result of any breach of this Agreement by the Authority or due to Force Majeure. The defaults referred to herein shall include:

Time is Money Join Law Insider Premium to draft better contracts faster.