Catastrophic Occurrences Sample Clauses

Catastrophic Occurrences. In the event of an economic or natural condition of such magnitude as to affect all businesses in the geographic area of a Dental Practice, Dental Cooperative will implement appropriate steps to mitigate the impact of such occurrence on the obligations of both parties under this Agreement, but any such mitigating measures shall in no way affect Provider’s and/or Dentist(s)’ obligations to Lender.
AutoNDA by SimpleDocs
Catastrophic Occurrences. In the event of an economic or natural condition of such magnitude as to affect all businesses in the geographic area of a Dental Practice, the parties will implement appropriate steps to mitigate the impact of such occurrence on the obligations of both parties under this Agreement.

Related to Catastrophic Occurrences

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

  • Catastrophic Leave The County will administer a Catastrophic Leave procedure designed to permit individual donations of annual leave, vacation, healthcare leave (8 hours maximum per fiscal year), compensatory and/or PIP leave time to an employee who is required to be on an extended unpaid leave due to a catastrophic medical condition or other serious circumstances.

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

  • Catastrophic Leave Program Leave credits, as defined below, may be transferred from one (1) or more employees to another employee, on an hour-for-hour basis, in accordance with departmental policies upon the request of both the receiving employee and the transferring employee and upon approval of the employee's appointing authority, under the following conditions: A. The receiving employee is required to be absent from work due to injury or the prolonged illness of the employee, employee's spouse, registered domestic partner, a domestic partner listed on an “Affidavit for Enrollment of Domestic Partners,” submitted to employee benefits, parent or child, has exhausted all earned leave credits, including but not limited to sick leave, compensatory time, holiday credits and disability leave and is therefore facing financial hardship. B. The transfers must be for a minimum of four (4) hours and in whole hour increments thereafter. C. Transfers shall be allowed to cross-departmental lines in accordance with the policies of the receiving department. D. The total maximum leave credits received by an employee shall normally not exceed five hundred twenty (520) hours; however, if approved by his/her appointing authority, the total leave credits may be up to one thousand forty (1,040) hours. Total leave credits in excess of one thousand forty (1,040) hours will be considered on a case-by-case basis by the appointing authority subject to the approval of the Chief Administrative Officer. E. The transfers are irrevocable, and will be indistinguishable from other leave credits belonging to the receiving employee. Transfers will be subject to all taxes required by law. F. Leave credits that may be transferred under this program are defined as the transferring employee’s vacation credits or up to twenty-four (24) hours of sick leave per fiscal year. G. Transfers shall be administered according to the rules and regulations of the Auditor and Controller, and made on a form prescribed by the Auditor and Controller. Approvals of the receiving and donating employee, the donating employee's appointing authority and the receiving employee's appointing authority (in the case of an interdepartmental transfer) will be provided for on such form. H. This program is not subject to the Grievance Procedure of this Agreement.

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

  • Catastrophic Leave Bank The City agrees to establish a Catastrophic Leave Bank to assist employees who have exhausted accrued leave time due to a serious or catastrophic illness or injury. The Catastrophic Leave Bank (CLB) will allow the bargaining unit employees to donate time to affected employees within and outside the unit, so that he/she can remain in a paid status for a longer period of time, thus partially ameliorating the financial impact of the illness, injury or condition. This donated time will be placed in a CLB and drawn down from the CLB by the eligible employee. Eligibility To be eligible for this benefit, the receiving employee must: 1) Be a regular full time employee, 2) Have sustained or have an immediate family member who has sustained a life threatening or debilitating illness, injury or condition which may require confirmation by a physician, 3) Have exhausted all accumulated paid leave including vacation, holiday, sick leave, and/or compensatory time off, 4) Be unable to return to work for at least 30 days or in the case of the condition affecting the immediate family member, that member must be in need of prolonged and significant personal care; and 5) Conformed with the requirements of the Family Medical Leave Act and/or Worker's Compensation.

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

  • Material Occurrences Promptly notify Agent in writing upon the occurrence of (a) any Event of Default or Default; (b) any event, development or circumstance whereby any financial statements or other reports furnished to Agent fail in any material respect to present fairly, in accordance with GAAP consistently applied, the financial condition or operating results of any Borrower as of the date of such statements; (c) any accumulated retirement plan funding deficiency which, if such deficiency continued for two plan years and was not corrected as provided in Section 4971 of the Code, could subject any Borrower to a tax imposed by Section 4971 of the Code; (d) each and every default by any Borrower which might result in the acceleration of the maturity of any Indebtedness, including the names and addresses of the holders of such Indebtedness with respect to which there is a default existing or with respect to which the maturity has been or could be accelerated, and the amount of such Indebtedness; and (e) any other development in the business or affairs of any Borrower which could reasonably be expected to have a Material Adverse Effect; in each case describing the nature thereof and the action Borrowers propose to take with respect thereto.

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

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

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