Over-runs Sample Clauses

Over-runs. (a) For the purposes of this paragraph 2.12, an over-run ("Over-run") occurs where: (i) there is a Restriction of Use which is not an Operator Restriction of Use (the "First Restriction"); (ii) following the end of the relevant period of difference between timetables referred to in sub-paragraphs (a) and (b) of the definition of Restriction of Use which served to establish the existence of that Restriction of Use (the "First Restriction Period"), there is either: (A) a further period of at least one hour during which Services are Disrupted due to (1) any incident attributed under Schedule 8 to circumstances arising from any restriction of operation of the Network which are a consequence of the First Restriction or (2) any act or omission in connection with any activities planned or undertaken which are directly attributable to the First Restriction (including any failure to remove the First Restriction by the time scheduled for its removal in the Applicable Engineering Access Statement) but excluding any act or omission by the Train Operator for which it would be allocated responsibility under this contract (the "Unplanned Over-run Period"); and/or (B) a further Restriction of Use is taken which is at the same location as all or part of the First Restriction and directly connected with or attributable to any activities undertaken or planned to be undertaken under the First Restriction (a "Further Restriction" ), in each case without there being any intervening period between the First Restriction and the relevant Unplanned Over-run Period or Further Restriction, which is not either a White Period, Unplanned Over-run Period or a Further Restriction. (b) Where a Restriction of Use is subject to one or more Over-runs, then the entire duration from the start of the First Restriction to the end of the last Over-run in respect of the Restriction of Use shall be treated as making up a single Restriction of Use. (c) Where there is an Over-run which results in a Service being Disrupted which: (i) is not part of either a Type 2 or Type 3 Restriction of Use; (ii) lasts for more than one hour; and (iii) results in the Train Operator incurring costs in the category of RoU Direct Costs in relation to the Over-run in excess of £10,000, then the Unplanned Over-run Period element of that Over-run (but not the relevant First Restriction Period or the period of any Further Restriction) shall for the purposes only of calculating RoU Direct Costs be deemed to constitute a Type...
Over-runs. For the purposes of this paragraph 2.12, an over-run (“Over-run”) occurs where:
Over-runs. Unless otherwise agreed, the timescales for claiming RoU Losses shall still apply.
Over-runs. (a) For the purposes of this paragraph 2.12, an over-run ("Over-run") occurs where: (i) there is a Restriction of Use which is not an Operator Restriction of Use (the "First Restriction"); (ii) following the end of the relevant period of difference between timetables referred to in sub-paragraphs (a) and (b) of the definition of Restriction of Use which served to establish the existence of that Restriction of Use (the "First Restriction Period"), there is either: (A) a further period of at least one hour during which Services are Disrupted due to (1) any incident attributed under Schedule 8 to circumstances arising from any restriction of operation of the CVL which are a consequence of the First Restriction or
Over-runs. In the event of the agreed use extending beyond the time or expiration of the license as specified in Part 2 of the Agreement the Hirer will pay to the Owner a further amount for each half hour or part thereof during which the agreed use extends beyond the time of expiration of the license as agreed in Part 6 of the Agreement. In accordance with Local Government Award Legislation, each Technician must have a half-hour (30 minute) break every five hours. Please ensure you arrange for this break accordingly within your access times. If breaks are not scheduled the hirer will be charged a penalty fee accordingly.

Related to Over-runs

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including RTU for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG shall immediately after each synchronization/tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Under-Frequency and Over Frequency Conditions The New York State Transmission System is designed to automatically activate a load- shed program as required by the NPCC in the event of an under-frequency system disturbance. Developer shall implement under-frequency and over-frequency relay set points for the Large Generating Facility as required by the NPCC to ensure “ride through” capability of the New York State Transmission System. Large Generating Facility response to frequency deviations of predetermined magnitudes, both under-frequency and over-frequency deviations, shall be studied and coordinated with the NYISO and Connecting Transmission Owner in accordance with Good Utility Practice. The term “ride through” as used herein shall mean the ability of a Generating Facility to stay connected to and synchronized with the New York State Transmission System during system disturbances within a range of under-frequency and over-frequency conditions, in accordance with Good Utility Practice and with NPCC Regional Reliability Reference Directory # 12, or its successor.

  • Commercial Milestones (a) Within [*****] calendar days after the end of the first Calendar Year in which aggregate annual Net Sales for that Calendar Year for the Licensed Product in the Territory reach any threshold indicated in the Commercial Milestone Events listed below, EverInsight shall notify VistaGen of the achievement of such Commercial Milestone Event and VistaGen shall invoice EverInsight for the corresponding non-refundable, non-creditable Milestone Payment set forth below and EverInsight shall remit payment to VistaGen within [*****] Business Days after the receipt of the invoice, as described in Section 8.6 (Currency; Exchange Rate; Payments). Annual Net Sales Milestones for Licensed Product Milestone Payments (in Dollars) (each a “Commercial Milestone Event”): (1). [*****] (2). [*****] (3). [*****] (4). [*****] (5). [*****] (b) For the purposes of determining whether a Net Sales Milestone Event has been achieved, Net Sales of Licensed Product(s) in the Territory shall be aggregated. For clarity, the annual Net Sales Milestone Payments set forth in this Section 8.3 (Commercial Milestones) shall be payable only once, upon the first achievement of the applicable Commercial Milestone Event, regardless of how many times such Commercial Milestone Event is achieved. (c) If a Commercial Milestone Event in Section 8.3 (Commercial Milestones) is achieved and payment with respect to any previous Commercial Milestone Event in Section 8.3 has not been made, then such previous Commercial Milestone Event shall be deemed achieved and EverInsight shall notify VistaGen within fifteen (15) calendar days of such achievement. VistaGen shall then invoice EverInsight for such unpaid previous Commercial Milestone Event(s) and EverInsight shall pay VistaGen such unpaid previous milestone payment(s) within thirty (30) Business Days of receipt of such invoice. (d) In the event that, VistaGen believes any Commercial Milestone Event under Section 8.3(a) has occurred but EverInsight has not given VistaGen the notice of the achievement of such Commercial Milestone Event, it shall so notify EverInsight in writing and shall provide to EverInsight data, documentation or other information that supports its belief. Any dispute under this Section 8.3(d) (Commercial Milestones - subsection (d)) that relates to whether or not a Commercial Milestone Event has occurred shall be referred to the JSC to be resolved in accordance with ARTICLE 3 (Governance) and shall be subject to resolution in accordance with Section 14.10 (Dispute Resolution). The Milestone Payments made for each Commercial Milestone Event shall be non-creditable and non-refundable.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities (including required control technologies and protection systems) and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer’s Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.