LLP Occurrence Sample Clauses

LLP Occurrence. 1. Each Party shall adopt or maintain policies or approaches designed to facilitate the management of any LLP Occurrence.
AutoNDA by SimpleDocs

Related to LLP Occurrence

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

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

  • Notice of Event of Default If the Mortgagee shall have Actual Knowledge of an Event of Default or of a Default arising from a failure to pay Rent, the Mortgagee shall give prompt written notice thereof to the Owner Trustee, the Owner Participant, Lessee, and each Note Holder. Subject to the terms of Sections 2.13, 4.03, 4.04, 4.08, 5.02 and 5.03 hereof, the Mortgagee shall take such action, or refrain from taking such action, with respect to such Event of Default or Default (including with respect to the exercise of any rights or remedies hereunder) as the Mortgagee shall be instructed in writing by a Majority in Interest of Note Holders. Subject to the provisions of Section 5.03, if the Mortgagee shall not have received instructions as above provided within 20 days after mailing notice of such Event of Default to the Note Holders, the Mortgagee may, subject to instructions thereafter received pursuant to the preceding provisions of this Section 5.01, take such action, or refrain from taking such action, but shall be under no duty to take or refrain from taking any action, with respect to such Event of Default or Default as it shall determine advisable in the best interests of the Note Holders; PROVIDED, HOWEVER, that the Mortgagee may not sell the Aircraft or any Engine without the consent of a Majority in Interest of Note Holders. For all purposes of this Trust Indenture, in the absence of Actual Knowledge on the part of the Mortgagee, the Owner Trustee or the Owner Participant, the Mortgagee, the Owner Trustee or the Owner Participant, as the case may be, shall not be deemed to have knowledge of a Default or an Event of Default (except, in the case of the Mortgagee, the failure of Lessee to pay any installment of Basic Rent within one Business Day after the same shall become due, if any portion of such installment was then required to be paid to the Mortgagee, which failure shall constitute knowledge of a Default) unless notified in writing by Lessee, the Owner Trustee, the Owner Participant or one or more Note Holders.

  • Default Events (a) Any material breach of the Funding Agreement by the Recipient, including those set out below, will be an event of default (“Default Event”):

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

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

  • Developer Default Each of the following shall be an Event of Default by Developer:

  • Termination due to Event of Default (a) Termination due to Parties Event of Default

  • 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).

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