Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.
Emergency Procedure An employee may be immediately placed on an off-duty status (without pay) by the Employer, but remain on the rolls where the allegation involves intoxication (use of drugs or alcohol), pilferage, or failure to observe safety rules and regulations, or in cases where retaining the employee on duty may result in damage to U.S. Postal Service property, loss of mail or funds, or where the employee may be injurious to self or others. The employee shall remain on the rolls (non-pay status) until disposition of the case has been had. If it is proposed to suspend such an employee for more than thirty (30) days or discharge the employee, the emergency action taken under this Section may be made the subject of a separate grievance.
Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.
Emergency Procedures All residents and guests are required to exit the building during emergencies that require evacuation and follow instructions given by authorized University emergency personnel (e.g., Security Services, Emergency Response Wardens and Building Emergency Captains). Residents and guests FIRE PROCEDURES AND FIRE ALARMS: All residents and guest(s) are required to exit the residences at the sound of a fire alarm. In the event of fire, residents and guest(s) are required to follow instruction given by Fire Services personnel.
Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.
Under-Frequency and Over Frequency Conditions The New York State Transmission System is designed to automatically activate a load- shed program as required by the NPCC in the event of an under-frequency system disturbance. Developer shall implement under-frequency and over-frequency relay set points for the Large Generating Facility as required by the NPCC to ensure “ride through” capability of the New York State Transmission System. Large Generating Facility response to frequency deviations of predetermined magnitudes, both under-frequency and over-frequency deviations, shall be studied and coordinated with the NYISO and Connecting Transmission Owner in accordance with Good Utility Practice. The term “ride through” as used herein shall mean the ability of a Generating Facility to stay connected to and synchronized with the New York State Transmission System during system disturbances within a range of under-frequency and over-frequency conditions, in accordance with Good Utility Practice and with NPCC Regional Reliability Reference Directory # 12, or its successor.
Emergency Work Employees who are required to report for emergency work on non- workdays, or outside of their regular hours of work on a scheduled workday or on holidays which they are entitled to have off, shall be paid overtime compensation for the actual work time and for travel time in connection therewith, but such travel time shall not exceed one-half (1/2) hour.
CONDITIONS FOR EMERGENCY/HURRICANE OR DISASTER - TERM CONTRACTS It is hereby made a part of this Invitation for Bids that before, during and after a public emergency, disaster, hurricane, flood, or other acts of God that Orange County shall require a “first priority” basis for goods and services. It is vital and imperative that the majority of citizens are protected from any emergency situation which threatens public health and safety, as determined by the County. Contractor agrees to rent/sell/lease all goods and services to the County or other governmental entities as opposed to a private citizen, on a first priority basis. The County expects to pay contractual prices for all goods or services required during an emergency situation. Contractor shall furnish a twenty-four (24) hour phone number in the event of such an emergency.
Emergency Transition Registry Operator agrees that, in the event that any of the emergency thresholds for registry functions set forth in Section 6 of Specification 10 is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD (an “Emergency Operator”) in accordance with ICANN’s registry transition process (available at <xxxx://xxx.xxxxx.xxx/en/resources/registries/transition-‐processes>) (as the same may be amended from time to time, the “Registry Transition Process”) until such time as Registry Operator has demonstrated to ICANN’s reasonable satisfaction that it can resume operation of the registry for the TLD without the reoccurrence of such failure. Following such demonstration, Registry Operator may transition back into operation of the registry for the TLD pursuant to the procedures set out in the Registry Transition Process, provided that Registry Operator pays all reasonable costs incurred (i) by ICANN as a result of the designation of the Emergency Operator and (ii) by the Emergency Operator in connection with the operation of the registry for the TLD, which costs shall be documented in reasonable detail in records that shall be made available to Registry Operator. In the event ICANN designates an Emergency Operator pursuant to this Section 2.13 and the Registry Transition Process, Registry Operator shall provide ICANN or any such Emergency Operator with all data (including the data escrowed in accordance with Section 2.3) regarding operations of the registry for the TLD necessary to maintain operations and registry functions that may be reasonably requested by ICANN or such Emergency Operator. Registry Operator agrees that ICANN may make any changes it deems necessary to the IANA database for DNS and WHOIS records with respect to the TLD in the event that an Emergency Operator is designated pursuant to this Section 2.13. In addition, in the event of such failure, ICANN shall retain and may enforce its rights under the Continued Operations Instrument.
EVENTS OUTSIDE OUR CONTROL 10.1 We will not be liable or responsible for any failure to perform, or delay in performance of, any of our obligations under this XXXX that is caused by any act or event beyond our reasonable control, including failure of public or private telecommunications networks (Event Outside Our Control). 10.2 If an Event Outside Our Control takes place that affects the performance of our obligations under this XXXX: (a) our obligations under this XXXX will be suspended and the time for performance of our obligations will be extended for the duration of the Event Outside Our Control; and (b) we will use our reasonable endeavours to find a solution by which our obligations under this XXXX may be performed despite the Event Outside Our Control.