Emergency Task Unit Sample Clauses

Emergency Task Unit. The Emergency Task Unit shall be divided into two (2) platoons comprised of two (2) units on each platoon. Each platoon will work a ten (10) hour shift schedule based on a four (4) week rotation and will work two (2) shifts comprised of days and afternoons. The hours of work for each shift are as follows:
AutoNDA by SimpleDocs
Emergency Task Unit. 10.23 All members will choose annual leave within their respective unit. The senior rank on the unit is in charge of the annual leave draw.
Emergency Task Unit ii. Forensic Identification Unit
Emergency Task Unit i. Provided no member of confirmed rank applies, the Chief may consider any candidate within the top five (5) on the current promotional standing list provided that candidate meets the conditions set out in 29.09 and:

Related to Emergency Task Unit

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

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

  • 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 Transportation Ambulance services for emergencies.

  • Emergency Treatment Medically necessary treatment due to an emergency.

  • Emergency Use In the case of any civil emergency or disaster, the Licensee shall, upon request of the Issuing Authority, make available to the Town a channel for use during the civil emergency or disaster period. The Licensee shall adhere to any new Emergency notification standards as established by the Federal Communications Commission.

  • Emergency Room Services This plan covers services received in a hospital emergency room when needed to stabilize or initiate treatment in an emergency. If your condition needs immediate or urgent, but non-emergency care, contact your PCP or use an urgent care center. This plan covers bandages, crutches, canes, collars, and other supplies incidental to your treatment in the emergency room as part of our allowance for the emergency room services. Additional services provided in the emergency room such as radiology or physician consultations are covered separately from emergency room services and may require additional copayments. The amount you pay is based on the type of service being rendered. Follow-up care services, such as suture removal, fracture care or wound care, received at the emergency room will require an additional emergency room copayment. Follow- up care services can be obtained from your primary care provider or a specialist. See Dental Services in Section 3 for information regarding emergency dental care services.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

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

Time is Money Join Law Insider Premium to draft better contracts faster.