Infrequency of Occurrence Sample Clauses

Open Split View

Download

Share

Cite

Infrequency of Occurrence the repair is of a type that would not reasonably be expected to recur in the foreseeable future.”

Sample 1

Save

Copy

Related to Infrequency of Occurrence

• Frequency of Evaluation Long form employees shall be evaluated at least one (1) time each year, which evaluation shall be completed no later than June 1.

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

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

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

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

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

• Cost of the Work The sum of all allowable costs necessarily incurred and paid by Contractor in the proper performance of the Work.

• Tenant Delays A "Tenant Delay” shall be defined as any delay in the design, permitting or performance of the Base Building Work to the extent that such delay is actually caused by any act or, where there is a duty to act under this Lease, any failure to act by Tenant or Tenant's contractors, architects, engineers, or anyone else engaged by or on behalf of Tenant in connection with the construction of the Tenant Improvement Work as set forth in this Article III (including, without limitation, any delays resulting from the Approved Tenant Finishes under Section 3.l(C) above) and disclosed to Tenant as hereinafter provided. Notwithstanding the foregoing, in no event shall any delays in the completion of the Base Building Work caused by Tenant’s use of non-union labor constitute a Tenant Delay hereunder. Notwithstanding the foregoing, no event shall be deemed a Tenant Delay unless and until Landlord has given Tenant written notice (the "Tenant Delay Notice") advising Tenant: (x) that a Tenant Delay is occurring and setting forth Landlord's good faith estimate as to the likely length of such Tenant Delay; (y) of the basis on which Landlord has determined that a Tenant Delay is occurring; and (z) the actions which Landlord believes that Tenant must take to eliminate such Tenant Delay. No event shall be deemed to be a Tenant Delay unless and until Tenant has failed to rectify the situation causing the Tenant Delay within forty-eight (48) hours after Tenant's receipt of the Tenant Delay Notice (which for the purposes of determining receipt may be delivered by hand to Tenant's Construction Representative, with copies to follow to Tenant at the notice address set forth in Section 1.2 of this Lease within five (5) days thereafter); provided, however, that if Tenant shall fail to eliminate the delay within the aforesaid 48-hour period, then the 48-hour cure period shall be included in the period of time charged to Tenant pursuant to such Tenant Delay Notice (it being understood and agreed that if Tenant shall in fact eliminate the Tenant Delay within the 48-hour cure period, no Tenant Delay shall be deemed to have occurred for the purposes of this Article III). In addition, any delay to the extent caused by (i) Landlord Delay or (ii) subject to the limitations of subsection (D) below, Tenant's Force Majeure (as defined in said subsection (D)) shall not constitute Tenant Delay. Tenant covenants that no Tenant Delay shall delay commencement of the Term or the obligation to pay Annual Fixed Rent or Additional Rent. The Delivery Dates and/or the date of substantial completion of the Base Building Work, as applicable, shall be deemed to have occurred as of the date when such Delivery Dates and/or date of substantial completion of the Base Building Work, as applicable, would have occurred but for any Tenant Delays, as determined by Landlord in the exercise of its good faith business judgment (it being understood and agreed that the foregoing shall not be construed so as to relieve Landlord of its obligation to actually complete the Base Building Work, notwithstanding the fact that substantial completion may have been deemed to have occurred prior to actual completion as the result of Tenant Delays).

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

• Tenant Delay Except as otherwise provided in the Lease, Delivery of the Premises shall occur when Landlord’s Work has been Substantially Completed, except to the extent that completion of Landlord’s Work shall have been actually delayed by any one or more of the following causes (“Tenant Delay”): (i) Tenant’s Representative was not available to give or receive any Communication or to take any other action required to be taken by Tenant hereunder within a reasonable period of time (not to exceed 2 business days) after written request from Landlord; (ii) Tenant’s request for changes to the Building Shell, whether or not such changes are actually performed; (iii) The construction of any changes to the Building Shell requested by Tenant and agreed upon by Landlord; (iv) Tenant’s request for Change Requests (as defined in Section 4(a) below) whether or not any such Change Requests are actually performed; (v) Construction of any Change Requests; (vi) Tenant’s request for materials, finishes or installations requiring unusually long lead times (provided Landlord will request that the General Contractor inform Tenant of any long lead time items and identify substitutes for such items as soon as reasonably possible); (vii) Tenant’s delay in reviewing, revising or approving plans and specifications beyond the periods set forth herein; (viii) Tenant’s delay in providing any information that is reasonably required to come from Tenant which is critical to the normal progression of the Project within a reasonable period of time after request. Tenant shall provide such information as soon as reasonably possible, but in no event longer than one week after receipt of any request for such information from Landlord; (ix) Tenant’s delay in making payments to Landlord for Excess TI Costs (as defined in Section 5(d) below) for more than 10 business days after such Excess TI Costs are required to be paid to Landlord; or (x) Any other act or omission by Tenant or any Tenant Party (as defined in the Lease), or persons employed by any of such persons that continues for more than 1 business day after Landlord’s notice thereof to Tenant. If Delivery is delayed for any of the foregoing reasons, then Landlord shall cause the TI Architect to certify the date on which the Tenant Improvements would have been Substantially Completed but for such Tenant Delay and such certified date shall be deemed to be the Commencement Date for purposes of Tenant’s obligation to pay Base Rent, Operating Expenses, Excess TI Costs and TI Rent; however, Tenant will not have any obligation to pay any amounts to third parties pursuant to the Lease (and will not occupy the Premises) until the date upon which the Premises is Delivered to Tenant with the Landlord’s Work Substantially Complete. Upon request, Landlord shall advise Tenant of any materials, finishes or installations which are required as part of any Change Request that will result in unusually long lead times.