Authority Event of Default Any of the following events shall constitute an event of default by the Authority ("Authority Event of Default”), when not caused by a Developer Event of Default:
Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:
Unbundled Network Element Combinations 4.1 For purposes of this Section, references to “Currently Combined” Network Elements shall mean that the particular Network Elements requested by NewPhone are in fact already combined by BellSouth in the BellSouth network. References to “
RETAILER OF LAST RESORT EVENT If we are no longer entitled by law to sell energy to you due to a Retailer of Last Resort (RoLR) event occurring in relation to us, we are required under the National Energy Retail Law and the Rules to provide relevant information (including your name, billing address and metering identifier) to the entity appointed as the relevant designated retailer for the RoLR event and this contract will come to an end.
Offtake constraints due to Backdown The Solar Power Developer and Buying Entity shall follow the forecasting and scheduling process as per the regulations in this regard by the Appropriate Commission. The Government of India, as per Clause 5.2(u) of the Indian Electricity Grid Code (IEGC), encourages a status of “must-run” to solar power projects. Accordingly, no solar power plant, duly commissioned, should be directed to back down by a Discom/ Load Dispatch Centre (LDC). In the eventuality of backdown, including backdown on account of non-dispatch of power due to non-compliance with “Order No. 23/22/2019- R&R dated 28.06.2019 of Ministry of Power regarding Opening and maintaining of adequate Letter of Credit (LC) as Payment Security Mechanism under Power Purchase Agreements by Distribution Licensees” and any clarifications or amendment thereto, except for the cases where the Backdown is on account of events like consideration of grid security or safety of any equipment or personnel or other such conditions, subject to the submission of documentary evidences from the competent authority, the SPD shall be eligible for a minimum generation compensation, from Buying Entity, restricted to the following and there shall be no other claim, directly or indirectly against SECI: Duration of Backdown Provision for Generation Compensation Hours of Backdown during a monthly billing cycle. Generation Compensation = 100% of [(Average Generation per hour during the month) X (number of backdown hours during the month)] X PPA tariff Where, Average Generation per hour during the month (kWh) = Total generation in the month (kWh) ÷ Total hours of generation in the month
Regulatory Event New Taxes If, after the Effective Date, a Regulatory Event occurs or New Taxes are imposed, and such event or taxes have a direct, material and adverse effect on the economic benefits to a Party of this ESA, the affected Party shall send written notice to the other Party, setting forth the Regulatory Event or New Taxes and reasonably demonstrating the effect of the same on the affected Party. Upon delivery of such notice, the Parties shall use reasonable efforts to negotiate an amendment to this ESA to mitigate such effect. Alternatively, if as a direct result of such a Regulatory Event or New Taxes, the Competitive Supplier incurs additional, material costs, the Competitive Supplier shall provide a written notice to the Town that documents: a) the effective date of the Regulatory Event or New Taxes; b) a detailed explanation and reasonable demonstration of the material costs incurred as a result of the Regulatory Event or New Taxes; c) the timing of the cost impact to be incurred by the Competitive Supplier; d) the proposed price increase per kWh to be passed on to Participating Consumers; and e) a proposed plan for coordinating with the Local Distributor for an increase in the price per kWh that is billed by the Local Distributor, designed to reimburse the Competitive Supplier for such cost impact. If the Town and the Competitive supplier cannot agree on the amendment to this ESA or reimbursement contemplated by this section, the matter may be subject to dispute resolution in accordance with section 12.2. In no event shall a price change become effective without providing Participating Consumers with a 30-day advance notice of the price change.
Safety, breakdowns and accidents 17.5.1 The Concessionaire shall ensure safe conditions for the Users and passengers, and in the event of unsafe conditions, it shall follow the relevant operating procedures and undertake removal of obstruction and debris without delay. Such procedures shall conform to the provisions of this Agreement, Applicable Laws, Applicable Permits and Good Industry Practice.
Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).
Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.
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:
