Force Majeure, Notice of Delay, and No Damages for Delay The Contractor will not be responsible for delay resulting from its failure to perform if neither the fault nor the negligence of the Contractor or its employees, subcontractors, or agents contributed to the delay and the delay is due directly to acts of God, wars, acts of public enemies, strikes, fires, floods, or other similar cause wholly beyond the Contractor’s control, or for any of the foregoing that affect suppliers if no alternate source of supply is available to the Contractor. In case of any delay the Contractor believes is excusable, the Contractor shall notify the Department in writing of the delay or potential delay and describe the cause of the delay either (i) within ten (10) calendar days after the cause that creates or will create the delay first arose, if the Contractor could reasonably foresee that a delay could occur as a result; or (ii) if a delay is not reasonably foreseeable, within five (5) calendar days after the date the Contractor first had reason to believe that a delay could result. THE FOREGOING WILL CONSTITUTE THE CONTRACTOR’S SOLE REMEDY OR EXCUSE WITH RESPECT TO ANY DELAY except if such delay is caused by the fraud, bad faith, or active interference of the Department. Providing notice in strict accordance with this paragraph is a condition precedent to such remedy, and a rebuttable presumption of prejudice will exist based on Contractor’s untimely notice. The Contractor shall not assert any claim for damages related to such delay. The Contractor will not be entitled to an increase in the Term Contract price or payment of any kind from the Department for direct, indirect, consequential, impact, or other costs, expenses, or damages, including costs of acceleration or inefficiency, arising because of delay, disruption, interference, or hindrance from any cause whatsoever. If performance is suspended or delayed, in whole or in part, due to any of the causes described in this subsection, the Department may unilaterally (and with no recourse on the part of the Contractor) identify and use an alternate source to complete any work under the Term Contract as the Department deems necessary, in its sole discretion. After the causes have ceased to exist, the Contractor shall perform at no increased cost, unless the Department determines, in its sole discretion, that the delay will significantly impair the value of the Contract to the Department or State, in which case the Department may (i) accept allocated performance or deliveries from the Contractor, provided that the Contractor grants preferential treatment to the Department with respect to Products subjected to allocation; or (ii) terminate the Term Contract in whole or in part.
Major Damage In the event of Major Damage to a Property prior to the Closing Date, then the applicable Seller shall have no obligation to repair such Major Damage and shall notify Purchaser in writing of such damage or destruction (the “Damage Notice”). Within ten (10) days after Purchaser’s receipt of the Damage Notice, Purchaser may elect at its option to give a Termination Notice for the damaged Property to Seller’s Representative. If Purchaser does not elect to terminate this Agreement with respect to the damaged Property, this transaction shall be closed in accordance with the terms of this Agreement either, at the election of the applicable Seller, (a) for the full Purchase Price for the damaged Property notwithstanding any such damage or destruction, and Purchaser shall, at Closing, execute and deliver an assignment and assumption (in a form reasonably required by the applicable Seller) of such Seller’ rights and obligations with respect to the insurance claim and related to such casualty, and thereafter Purchaser shall receive all remaining insurance proceeds pertaining to such claim (plus a credit against the applicable Purchase Price at Closing in the amount of any deductible payable by the applicable Seller in connection therewith and not spent by such Seller for demolition, site cleaning, restoration or other repairs); or (b) Purchaser shall receive a credit against the Base Purchase Price for the damaged Property for the full replacement costs of repair to the subject Property, plus, to the extent covered by such Seller’s insurance policy, any costs required pursuant to local code or zoning requirements, as determined by an independent third party reasonably acceptable to such Seller and Purchaser. In the event a Seller elects to assign such Seller's rights and obligations with respect to the insurance claim and related casualty to Purchaser as provided above, and if an AIMCO employee is the adjuster for the claim related thereto, Sellers covenant and agree that the adjuster shall act in accordance with standard insurance industry protocols in processing such claim (including, without limitation, the time taken to process such claim).
Default under Specified Transaction The party, any Credit Support Provider of such party or any applicable Specified Entity of such party (1) defaults under a Specified Transaction and, after giving effect to any applicable notice requirement or grace period, there occurs a liquidation of, an acceleration of obligations under, or an early termination of, that Specified Transaction, (2) defaults, after giving effect to any applicable notice requirement or grace period, in making any payment or delivery due on the last payment, delivery or exchange date of, or any payment on early termination of, a Specified Transaction (or such default continues for at least three Local Business Days if there is no applicable notice requirement or grace period) or (3) disaffirms, disclaims, repudiates or rejects, in whole or in part, a Specified Transaction (or such action is taken by any person or entity appointed or empowered to operate it or act on its behalf);
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. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-‐level domain names identified by ICANN and set forth at <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/en/announcements-‐and-‐ media/announcement-‐2-‐17nov13-‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-‐OARC) <▇▇▇▇▇://▇▇▇.▇▇▇-‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Termination Damages If the Term of this Lease is terminated for default, unless and until Landlord elects lump sum liquidated damages described in the next paragraph, Tenant covenants, as an additional, cumulative obligation after any such termination, to pay punctually to Landlord all the sums and perform all of its obligations in the same manner as if the Term had not been terminated. In calculating such amounts Tenant will be credited with the net proceeds of any rent then actually received by Landlord from a reletting of the Premises after deducting all Rent that has not then been paid by Tenant, provided that Tenant shall never be entitled to receive any portion of the re-letting proceeds, even if the same exceed the Rent originally due hereunder.
