Delays Identified in Risk Events Matrix; Excusable Delay Sample Clauses

Delays Identified in Risk Events Matrix; Excusable Delay. 10.4.1 The Risk Events Matrix identifies certain Risk Events which will result in delay in the achievement of identified work or milestones, including NEPA delays, delays in obtaining FHWA or other third party approvals or resulting from the terms and conditions of such approvals, delays due to injunctions or other court orders, Close of Finance delays, delays due to Change in Law, delays due to Major Catastrophe, delays in right-of-way acquisition, and delays or failures by either party to meet milestones for the Initial Scope of Work, Project Milestones or other milestones or deadlines as set forth in this Agreement, the Master Development Plan, or a Facility Implementation Plan. Except as may be otherwise set forth in the Master Development Plan or a Facility Implementation Plan, the grounds for a claim for remedies for delay by either party shall be limited to those Risk Events set forth in the Risk Events Matrix that expressly allow such additional remedies. If any such Risk Event occurs, the parties shall follow the provisions regarding such Risk Event in the Risk Events Matrix to determine their respective rights and remedies, including rights to extend schedules, to remove a Facility from this Agreement, to terminate this Agreement and to receive reimbursement for unpaid costs in accordance with Section 19.6, as applicable. 10.4.2 As soon as practicable and within 14 days of the commencement of any Risk Event giving rise to a claim for excusable delay, the Party suffering the delay shall provide the other Party written notice identifying the cause of delay, estimated impacts and measures that will be taken to mitigate the impacts, and shall follow up with periodic reports regarding continuing impacts and mitigation measures as requested by the other Party. Within 14 days of the cessation of the event causing delay, the parties shall ascertain the total excusable delay and document the time extension.
AutoNDA by SimpleDocs

Related to Delays Identified in Risk Events Matrix; Excusable Delay

  • Excusable Delays Except with respect to defaults of subproviders, the Engineer shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure to progress in the performance of the work) if such failure arises out of causes beyond the control and without the default or negligence of the Engineer. Such causes may include, but are not restricted to, acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, freight embargoes, and unusually severe weather.

  • Excusable Delay The parties shall not be obligated to perform and shall not be deemed to be in default hereunder, if the performance of a non-monetary obligation required hereunder is prevented by the occurrence of any of the following, other than as the result of the financial inability of the party obligated to perform: acts of God, strikes, lock-outs, other industrial disturbances, acts of a public enemy, war or war-like action (whether actual, impending or expected and whether de jure or de facto), acts of terrorists, arrest or other restraint of government (civil or military), blockades, insurrections, riots, epidemics, landslides, lightning, earthquakes, fires, hurricanes, storms, floods, washouts, sink holes, civil disturbances, explosions, breakage or accident to equipment or machinery, confiscation or seizure by any government or public authority, nuclear reaction or radiation, radioactive contamination or other causes, whether of the kind herein enumerated or otherwise, that are not reasonably within the control of the party claiming the right to delay performance on account of such occurrence.

  • Force Majeure Delays In any case where either party hereto is required to do any act (other than the payment of money), delays caused by or resulting from Acts of God or Nature, war, civil commotion, fire, flood or other casualty, labor difficulties, shortages of labor or materials or equipment, government regulations, delay by government or regulatory agencies with respect to approval or permit process, unusually severe weather, or other causes beyond such party’s reasonable control the time during which act shall be completed, shall be deemed to be extended by the period of such delay, whether such time be designated by a fixed date, a fixed time or “a reasonable time.”

  • Force Majeure Events a) Neither Party shall be responsible or liable for or deemed in breach hereof because of any delay or failure in the performance of its obligations hereunder (except for obligations to pay money due prior to occurrence of Force Majeure events under this Agreement) or failure to meet milestone dates due to any event or circumstance (a "Force Majeure Event") beyond the reasonable control of the Party experiencing such delay or failure, including the occurrence of any of the following: i) acts of God; ii) typhoons, floods, lightning, cyclone, hurricane, drought, famine, epidemic, plague or other natural calamities; iii) acts of war (whether declared or undeclared), invasion or civil unrest; iv) any requirement, action or omission to act pursuant to any judgment or order of any court or judicial authority in India (provided such requirement, action or omission to act is not due to the breach by the SPG or of any Law or any of their respective obligations under this Agreement); v) inability despite complying with all legal requirements to obtain, renew or maintain required licenses or Legal Approvals; vi) earthquakes, explosions, accidents, landslides; fire; vii) expropriation and/or compulsory acquisition of the Project in whole or in part by Government Instrumentality; viii) chemical or radioactive contamination or ionizing radiation; or ix) damage to or breakdown of transmission facilities of GETCO/ DISCOMs; x) Exceptionally adverse weather condition which are in excess of the statistical measure of the last hundred (100) years.

  • 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: (a) accident, death or severe injury to any person; (b) damaged or dislodged fixed equipment; (c) flooding of Project Highway; and (d) any other unusual occurrence.

  • Reporting on Utilization of Subject Inventions 1. The Performer agrees to submit, during the term of the Agreement, an annual report on the utilization of a subject invention or on efforts at obtaining such utilization that are being made by the Performer or its licensees or assignees. Such reports shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the Performer, and such other data and information as the agency may reasonably specify. The Performer also agrees to provide additional reports as may be requested by DARPA in connection with any march-in proceedings undertaken by DARPA in accordance with Paragraph I of this Article. DARPA agrees it shall not disclose such information to persons outside the Government without permission of the Performer, unless required by law. 2. All required reporting shall be accomplished, to the extent possible, using the i-Edison reporting website: xxxxx://x-xxxxxx.xxxx.xxx.xxx/iEdison/. To the extent any such reporting cannot be carried out by use of i-Edison, reports and communications shall be submitted to the Agreements Officer and Administrative Agreements Officer.

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

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Permitted and Required Uses/Disclosures of PHI 3.1 Except as limited in this Agreement, Business Associate may use or disclose PHI to perform Services, as specified in the underlying grant or contract with Covered Entity. The uses and disclosures of Business Associate are limited to the minimum necessary, to complete the tasks or to provide the services associated with the terms of the underlying agreement. Business Associate shall not use or disclose PHI in any manner that would constitute a violation of the Privacy Rule if used or disclosed by Covered Entity in that manner. Business Associate may not use or disclose PHI other than as permitted or required by this Agreement or as Required by Law. 3.2 Business Associate may make PHI available to its employees who need access to perform Services provided that Business Associate makes such employees aware of the use and disclosure restrictions in this Agreement and binds them to comply with such restrictions. Business Associate may only disclose PHI for the purposes authorized by this Agreement: (a) to its agents and Subcontractors in accordance with Sections 9 and 17 or, (b) as otherwise permitted by Section 3. 3.3 Business Associate shall be directly liable under HIPAA for impermissible uses and disclosures of the PHI it handles on behalf of Covered Entity, and for impermissible uses and disclosures, by Business Associate’s Subcontractor(s), of the PHI that Business Associate handles on behalf of Covered Entity and that it passes on to Subcontractors.

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