Disaster Occurrence Sample Clauses

The Disaster Occurrence clause defines the rights and obligations of the parties in the event that a natural or man-made disaster impacts the performance of the contract. Typically, this clause outlines what constitutes a disaster, such as earthquakes, floods, or government-declared emergencies, and specifies the procedures to follow if such an event prevents one or both parties from fulfilling their contractual duties. Its core function is to allocate risk and provide a clear process for suspending or modifying obligations, thereby protecting both parties from liability due to circumstances beyond their control.
Disaster Occurrence. Fiserv shall notify Client as soon as possible after a Disaster is declared by Fiserv and shall comply with the Business Continuity Plan. Fiserv shall move the processing of Client’s standard services to the recovery site as expeditiously as possible if operations cannot be satisfactorily restored (in Fiserv’s sole discretion) at the primary location. If a recovery site is used, Fiserv shall coordinate the cut-over to back-up telecommunication facilities with the appropriate carriers. Client shall maintain adequate records of all transactions under the reasonable control of Client during the period of service interruption and shall have personnel available to assist Fiserv in implementing the switchover to the recovery site. During a Disaster, optional or on-request services shall be provided by Fiserv only to the extent adequate capacity exists at the recovery site and only after stabilizing the provision of base services.
View SourceView Similar (2)
Disaster Occurrence. StoneRiver shall notify Client as soon as possible after the occurrence of a Disaster and shall comply with the Business Continuity Plan. StoneRiver shall move the processing of Client’s standard services to the recovery site as expeditiously as possible if operations cannot be satisfactorily restored (in StoneRiver’s sole discretion) at the primary location. If a recovery site is used, StoneRiver shall coordinate the cut-over to back-up telecommunication facilities with the appropriate carriers. Client shall maintain adequate records of all transactions under the reasonable control of Client during the period of service interruption and shall have personnel available to assist StoneRiver in implementing the switchover to the recovery site. During a Disaster, optional or on-request services shall be provided by StoneRiver only to the extent adequate capacity exists at the recovery site and only after stabilizing the provision of base services.
View Source
Disaster Occurrence. In the event of a disaster covered by the DRP, Supplier shall reinstate the Services within the applicable RTOs. In the event the applicable Services are not reinstated within the applicable RTOs or the Services are not returned to their state of delivery prior to the subject disaster within the time specified in the DRP, then at its option: (1) Unless Supplier has notified Company that Supplier has already done so, Company may procure the affected Services from an alternate source, and Supplier shall be liable for payment of the reasonable fees for such Services from the alternate source until the Services are restored;
View Source
Disaster Occurrence. Contractor shall provide all labor, materials and supplies necessary to properly fasten, restrain, and secure all hazardous wastes for the occurrence of inclement weather as well as a major earthquake, natural or unnatural disaster. Contractor shall have available on-site supplies for containment of incidental and large spills. Contractor may be expected to provide necessary resources, facilities and equipment as covered in this scope of work for response and recovery operations as needed by County following a major disaster.
View Source

Related to Disaster Occurrence

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

  • 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 <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/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>.

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

  • Force Majeure Event 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event. 16.2 A party that becomes aware of a Force Majeure Event which gives rise to, or which is likely to give rise to, any failure or delay in that party performing any obligation under this Agreement, must: (a) promptly notify the other; and (b) inform the other of the period for which it is estimated that such failure or delay will continue. 16.3 A party whose performance of its obligations under this Agreement is affected by a Force Majeure Event must take reasonable steps to mitigate the effects of the Force Majeure Event.