Event of Breach 7.1 The following circumstances shall be deemed Event of Default: 7.1.1 Pledgor’s any breach to any obligations under the Transaction Documents and/or this Agreement. 7.1.2 Party C’s any breach to any obligations under the Transaction Documents and/or this Agreement. 7.2 Upon notice or discovery of the occurrence of any circumstances or event that may lead to the aforementioned circumstances described in Section 7.1, Pledgor and Party C shall immediately notify Pledgee in writing accordingly. 7.3 Unless an Event of Default set forth in this Section 7.1 has been successfully resolved to Pledgee’s satisfaction within twenty (20) days after the Pledgee and /or Party C delivers a notice to the Pledgor requesting ratification of such Event of Default, Pledgee may issue a Notice of Default to Pledgor in writing at any time thereafter, demanding the Pledgor to immediately exercise the Pledge in accordance with the provisions of Section 8 of this Agreement.
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).
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.
Occurrence of Default Any Transfer hereunder shall be subordinate and subject to the provisions of this Lease, and if this Lease shall be terminated during the term of any Transfer, Landlord shall have the right to: (i) treat such Transfer as cancelled and repossess the Subject Space by any lawful means, or (ii) require that such Transferee attorn to and recognize Landlord as its landlord under any such Transfer. If Tenant shall be in default under this Lease, Landlord is hereby irrevocably authorized, as Tenant’s agent and attorney-in-fact, to direct any Transferee to make all payments under or in connection with the Transfer directly to Landlord (which Landlord shall apply towards Tenant’s obligations under this Lease) until such default is cured. Such Transferee shall rely on any representation by Landlord that Tenant is in default hereunder, without any need for confirmation thereof by Tenant. Upon any assignment, the assignee shall assume in writing all obligations and covenants of Tenant thereafter to be performed or observed under this Lease. No collection or acceptance of rent by Landlord from any Transferee shall be deemed a waiver of any provision of this Article 14 or the approval of any Transferee or a release of Tenant from any obligation under this Lease, whether theretofore or thereafter accruing. In no event shall Landlord’s enforcement of any provision of this Lease against any Transferee be deemed a waiver of Landlord’s right to enforce any term of this Lease against Tenant or any other person. If Tenant’s obligations hereunder have been guaranteed, Landlord’s consent to any Transfer shall not be effective unless the guarantor also consents to such Transfer.
Commercial General Liability – Occurrence Form The policy shall include bodily injury, property damage, personal and advertising injury and broad form contractual liability coverage. • General Aggregate $2,000,000 • Products – Completed Operations Aggregate $1,000,000 Products and completed operations coverage shall be maintained for three (3) years after completion of design • Personal and Advertising Injury $1,000,000 • Blanket Contractual Liability – Written and Oral $1,000,000 • Damage to Rented Premises $50,000 • Each Occurrence $1,000,000 $0 to $5,000,000 $1,000,000 Each Occurrence; $2,000,000 Aggregate $5,000,001 to $15,000,000 $5,000,000 Each Occurrence; $5,000,000 Aggregate $15,000,001 to $50,000,000 $5,000,000 Each Occurrence; $10,000,000 Aggregate $50,000,001 & up $25,000,000 Each Occurrence; $25,000,000 Aggregate a. The Consultant shall be responsible for monitoring the Contract value as it increases and the Consultant shall be responsible for purchasing additional insurance to be in compliance with this Contract should the increase in Contract value require a higher limit of insurance. The Consultant shall provide a new certificate of insurance that reflects the increase in limits as required in 4.20(E) below. b. The policy shall be endorsed to include the following additional insured language: “The State of Arizona, its departments, agencies, boards, commissions, universities and its officers, officials, agents, and employees shall be named as additional insureds with respect to liability arising out of the activities performed by or on behalf of the Consultant.” Such additional insured shall be covered to the full limits of liability purchased by the Consultant, even if those limits of liability are in excess of those required by this Contract. c. The policy shall contain a waiver of subrogation endorsement in favor of the State of Arizona, its departments, agencies, boards, commissions, universities and its officers, officials, agents, and employees for losses arising from work performed by or on behalf of the Consultant.
Force Majeure Event After giving effect to any applicable provision, disruption fallback or remedy specified in, or pursuant to, the relevant Confirmation or elsewhere in this Agreement, by reason of force majeure or act of state occurring after a Transaction is entered into, on any day:— (1) the Office through which such party (which will be the Affected Party) makes and receives payments or deliveries with respect to such Transaction is prevented from performing any absolute or contingent obligation to make a payment or delivery in respect of such Transaction, from receiving a payment or delivery in respect of such Transaction or from complying with any other material provision of this Agreement relating to such Transaction (or would be so prevented if such payment, delivery or compliance were required on that day), or it becomes impossible or impracticable for such Office so to perform, receive or comply (or it would be impossible or impracticable for such Office so to perform, receive or comply if such payment, delivery or compliance were required on that day); or (2) such party or any Credit Support Provider of such party (which will be the Affected Party) is prevented from performing any absolute or contingent obligation to make a payment or delivery which such party or Credit Support Provider has under any Credit Support Document relating to such Transaction, from receiving a payment or delivery under such Credit Support Document or from complying with any other material provision of such Credit Support Document (or would be so prevented if such payment, delivery or compliance were required on that day), or it becomes impossible or impracticable for such party or Credit Support Provider so to perform, receive or comply (or it would be impossible or impracticable for such party or Credit Support Provider so to perform, receive or comply if such payment, delivery or compliance were required on that day), so long as the force majeure or act of state is beyond the control of such Office, such party or such Credit Support Provider, as appropriate, and such Office, party or Credit Support Provider could not, after using all reasonable efforts (which will not require such party or Credit Support Provider to incur a loss, other than immaterial, incidental expenses), overcome such prevention, impossibility or impracticability;
Event of Default; Notice (a) The Guarantee Trustee shall, within 90 days after the occurrence of an Event of Default known to the Guarantee Trustee, transmit by mail, first class postage prepaid, to the Holders, notice of any such Event of Default known to the Guarantee Trustee, unless such Event of Default has been cured before the giving of such notice, provided that, except in the case of a default in the payment of a Guarantee Payment, the Guarantee Trustee shall be protected in withholding such notice if and so long as the board of directors, the executive committee or a trust committee of directors and/or Responsible Officers of the Guarantee Trustee in good faith determines that the withholding of such notice is in the interests of the Holders. (b) The Guarantee Trustee shall not be deemed to have knowledge of any Event of Default unless the Guarantee Trustee shall have received written notice, or a Responsible Officer charged with the administration of this Guarantee Agreement shall have obtained written notice, of such Event of Default.
Termination due to Force Majeure 13.5.1 If the Force Majeure Event or its effects continue to be present beyond the period as specified in Article 4.5.3, either Party shall have the right to cause termination of the Agreement. In such an event, this Agreement shall terminate on the date of such Termination Notice.
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 <xxxx://xxxxxxxx.xxxxx.xxx/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) <xxxxx://xxx.xxx-‐xxxx.xxx/xxxx/xxxx/xxxx>. 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 <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-‐ new-‐gtld-‐annex-‐1-‐07oct13-‐en.pdf>.
Name Collision Occurrence Management 6.1. No-‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
