Emergency Thresholds Sample Clauses

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. Critical Function Emergency Threshold 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 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. Critical Function DNS Service DNSSEC proper resolution EPP RDDS Data Escrow

Related to Emergency Thresholds

  • Emergency Conditions “Emergency Condition” shall mean a condition or situation: (1) that in the judgment of the Party making the claim is imminently likely to endanger life or property; or (2) that, in the case of the Transmission Provider, is imminently likely (as determined in a non-discriminatory manner) to cause a material adverse effect on the security of, or damage to the Transmission System, the Transmission Owner’s Interconnection Facilities or the Transmission Systems of others to which the Transmission System is directly connected; or (3) that, in the case of the Interconnection Customer, is imminently likely (as determined in a non-discriminatory manner) to cause a material adverse effect on the security of, or damage to, the Small Generating Facility or the Interconnection Customer’s Interconnection Facilities. Under Emergency Conditions, the Transmission Owner may immediately suspend interconnection service and temporarily disconnect the Small Generating Facility. The Transmission Provider shall notify the Interconnection Customer promptly when it becomes aware of an Emergency Condition that may reasonably be expected to affect the Interconnection Customer’s operation of the Small Generating Facility. The Interconnection Customer shall notify the Transmission Provider promptly when it becomes aware of an Emergency Condition that may reasonably be expected to affect the Transmission Owner’s Transmission System or other Affected Systems. To the extent information is known, the notification shall describe the Emergency Condition, the extent of the damage or deficiency, the expected effect on the operation of both Parties’ facilities and operations, its anticipated duration, and the necessary corrective action.

  • Emergency/Declared Disaster Requirements In the event of an emergency or if Orange County is declared a disaster area by the County, state or federal government, this Contract may be subjected to unusual usage. The Contractor shall service the County during such an emergency or declared disaster under the same terms and conditions that apply during non-emergency/disaster conditions. The pricing quoted by the Contractor shall apply to serving the County’s needs regardless of the circumstances. If the Contractor is unable to supply the goods/services under the terms of the Contract, then the Contractor shall provide proof of such disruption and a copy of the invoice for the goods/services from the Contractor’s supplier(s). Additional profit margin as a result of supplying goods/services during an emergency or a declared disaster shall not be permitted. In the event of an emergency or declared disaster, emergency purchase order numbers will be assigned. All applicable invoices from the Contractor shall show both the emergency purchase order number and the Contract number.

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

  • Emergency Situations If the condition is an emergency, this will be communicated to the Contractor with the request that corrections are to be accomplished immediately. The Contractor shall respond to the notice in emergency situations within twenty-four hours. If the Contractor fails to respond within this time limit, the Owner may correct the defect and charge the Contractor for the Work. If it is determined the complaint is not the responsibility of the Contractor, the Contractor shall be promptly paid for the cost of the corrective work. The Contractor shall give notice in writing to the Owner when corrections have been completed.

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