Emergency Travel; Crew Swaps Sample Clauses

Emergency Travel; Crew Swaps. The Requesting Entity will reimburse the Providing Entity for its travel costs incurred (e.g., plane tickets) for travel for personnel who have to return home on an emergency basis from mutual aid assistance. Taking into account due exigencies, the Providing Entity will endeavor to limit or minimize emergency travel costs. The Providing Entity’s costs for swapping crews will be reimbursed on a not less than two- week crew rotation basis. The Requesting Entity will not be responsible for the Providing Entity’s costs in swapping crews on a less than two week basis, or for replacing personnel who have to return home from mutual aid assistance for reasons that are not an emergency. As used in this clause (2) of section 2, “emergency” means an exigent or severe circumstance that requires an individual to return home as soon as reasonably possible to meet family, personal, or similar needs. An example of an emergency includes the death or severe illness (requiring hospitalization or non-elective surgical intervention) of a close family member. As the term is used here, “emergency” does not include planned or elective matters such as vacations, weddings, birthdays, graduations, court dates, elective medical procedures, or similar activities.
Sample 1Sample 2
AutoNDA by SimpleDocs
Emergency Travel; Crew Swaps. The Utility will reimburse the Responder for its travel costs incurred for travel for personnel who have to return home on an emergency basis from mutual aid assistance. Taking into account due exigencies, the Responder will endeavor to limit or minimize emergency travel costs. The Responder’s costs for swapping crews will be reimbursed on a not less than two-week crew rotation basis. The Utility will not be responsible for the Responder’s costs in swapping crews on a less than two week basis, or for replacing personnel who have to return home from mutual aid assistance for reasons that are not an emergency. As used in this clause (2) of section 2, “emergency” means an exigent or severe circumstance that requires an individual to return home as soon as reasonably possible to meet family, personal, or similar needs. An example of an emergency includes the death or severe illness (requiring hospitalization or non-elective surgical intervention) of a close family member. As the term is used here, “emergency” does not include planned or elective matters such as weddings, birthdays, graduations, court dates, or elective medical procedures.
Sample 1

Related to Emergency Travel; Crew Swaps

  • Emergency Transportation Ambulance services for emergencies.

  • Non-Emergency Transportation Routine medical transportation to and from Medicaid-covered scheduled medical appointments is covered by the non-emergency medical transportation (NEMT) broker Medicaid program. This includes transportation via multi-passenger van services and common carriers such as public railways, buses, cabs, airlines, ambulance as appropriate, and private vehicle transportation by individuals. The NEMT broker must approve ambulance, multi-passenger van services, and transportation by common carriers. The MCO must inform enrollees of how to access non-emergency transportation as appropriate.

  • 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 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 Service Leave ‌ Where employees' services are required for emergency operations by request from the Provincial Emergency Program or appropriate police authority, leave from work as required may be granted without loss of basic pay. If any remuneration, other than for expenses, is received, it shall be remitted to the Employer.

  • Emergency Treatment Medically necessary treatment due to an emergency.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!