Delay Due to Authority’s Fault or Neglect Sample Clauses

Delay Due to Authority’s Fault or Neglect. Should Redeveloper be obstructed or delayed in the prosecution of or completion of the Project as a result of a delay due to fault or neglect of the Authority or the County (the “Public Entities”), Redeveloper shall notify Authority in writing within thirty (30) Business Days after the commencement of such delay, stating the cause or causes thereof. Failure to provide that thirty (30) Business Days written notice shall be deemed a waiver of any claim Redeveloper otherwise may have had with respect to such delay. Notwithstanding any performance extension of Redeveloper’s obligations hereunder resulting from such an Authority-caused obstruction or delay, Redeveloper shall use commercially reasonable efforts to cure, correct or otherwise mitigate the impact from such event to allow Redeveloper to as quickly as possible commence and complete the Project. No such delay shall be deemed to be caused by Authority unless Redeveloper notifies Authority in writing of the occurrence of such an event within thirty (30) Business Days after its occurrence and any extension or increase shall only be for the period or amount equal to the delay related to such an event.
Sample 1
AutoNDA by SimpleDocs

Related to Delay Due to Authority’s Fault or Neglect

  • Act of God Days A. Scheduled days of student instruction which are not held because of conditions not within the control of school authorities, such as inclement weather, fires, epidemics, mechanical breakdowns, or health conditions (as defined by city, county, or state health authorities) will be rescheduled to ensure that there are a minimum number of days of student instruction as prescribed by Michigan law.

  • 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

  • Authority to act on behalf of Concessionaire 36.2.1 During the period of Suspension, the Authority shall, on behalf of the Concessionaire, collect all Fee and revenues under and in accordance with this Agreement and deposit the same in the Escrow Account. The Authority shall be entitled to make withdrawals from the Escrow Account for meeting the costs incurred by it for remedying and rectifying the cause of Suspension, and thereafter for defraying the expenses specified in Clause 31.3.

  • TOTAL OR PARTIAL FAILURE TO PERFORM 20.1 In the case of Goods to be specially manufactured for it, if Transnet at any time ascertains that:

  • 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 Lack Of Funding Appropriation If, in the judgment of the Director of Accounts and Reports, Department of Administration, sufficient funds are not appropriated to continue the function performed in this agreement and for the payment of the charges hereunder, State may terminate this agreement at the end of its current fiscal year. State agrees to give written notice of termination to contractor at least 30 days prior to the end of its current fiscal year, and shall give such notice for a greater period prior to the end of such fiscal year as may be provided in this contract, except that such notice shall not be required prior to 90 days before the end of such fiscal year. Contractor shall have the right, at the end of such fiscal year, to take possession of any equipment provided State under the contract. State will pay to the contractor all regular contractual payments incurred through the end of such fiscal year, plus contractual charges incidental to the return of any such equipment. Upon termination of the agreement by State, title to any such equipment shall revert to contractor at the end of the State's current fiscal year. The termination of the contract pursuant to this paragraph shall not cause any penalty to be charged to the agency or the contractor.

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

  • De-commissioning due to Emergency 17.6.1 If, in the reasonable opinion of the Concessionaire, there exists an Emergency which warrants de-commissioning and closure of the whole or any part of the Bus Terminal, the Concessionaire shall be entitled to de- commission and close the whole or any part of the Bus Terminal to Users and passengers for so long as such Emergency and the consequences thereof warrant; provided that such de-commissioning and particulars thereof shall be notified by the Concessionaire to the Authority without any delay, and the Concessionaire shall diligently carry out and abide by any reasonable directions that the Authority may give for dealing with such Emergency.

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

  • Failure to Make Payment In the event a participating Authorized User fails to make payment to the Contractor for Products delivered, accepted and properly invoiced, within thirty calendar days of such delivery and acceptance, the Contractor may, upon five business days advance written notice to both the Commissioner and the Authorized User’s purchasing official, suspend additional shipments of Product or provision of services to such entity until such time as reasonable arrangements have been made and assurances given by such entity for current and future Contract payments.

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