Emergency Call Back Emergency Call Back is defined as those instances when unit members have not been placed on-call, but are contacted to return to their work location or to perform work on short notice during an off-duty period. Non-exempt employees shall be paid a minimum of four (4) hours at the appropriate rate of pay on each non- work day they are called back. Exempt employees shall receive compensatory time on an hour-for-hour basis at not less than four (4) hours for call back work. In the event employees are required to report to work, both exempt and non-exempt employees shall be paid for mileage incurred in reporting to and returning from work for call back duties. If the call-back duties require work in excess of the four (4)-hour minimum, the employee shall be compensated at the appropriate rate of pay for the actual number of hours worked. If the call back duties occur during a week in which the District is closed as the result of a recognized holiday, the holiday hours shall count as hours worked for the purposes of computing overtime compensation for non-exempt employees pursuant to the provisions of this section.
Emergency Call-In When an employee is called in to perform unanticipated extra work, and the work is not an extension of his normal workday, he shall be compensated for the hours worked. Such compensation shall be for a minimum of four (4) hours in the event the employee works less than this amount of time. However, actual time worked will be considered for the computation of overtime.
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.