Emergency Back-Up Vehicles Sample Clauses

Emergency Back-Up Vehicles. In the event, one or more of the vehicles licensed to CONTRACTOR by CITY breaks down or is otherwise inoperable or unavailable, CONTRACTOR will utilize one or more of CONTRACTOR’s vehicles for the CITY Transportation Program in accordance with the terms and conditions of this Agreement, at no additional cost to CITY.
AutoNDA by SimpleDocs

Related to Emergency Back-Up Vehicles

  • Emergency Alert System The Franchisee shall comply with the applicable requirements of the FCC with respect to the operation of an Emergency Alert System (“EAS”) requirements of the FCC and applicable state and local EAS plans in order that emergency messages may be distributed over the Cable System.

  • 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 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 Call Back Employees called back by the District in emergency situations shall be guaranteed four (4) hours work, or equivalent compensatory time off, or salary compensation as mutually agreed by the District and the employee.

  • Safe Equipment The City shall furnish and maintain in the best possible working condition, within the limits of its financial capability, the necessary tools, facilities, vehicles, supplies, and equipment required for members to safely carry out their duties. Members are responsible for reporting unsafe conditions or practices, for avoiding negligence, and for properly using and caring for tools, facilities, vehicles, supplies, and equipment provided by the City.

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

  • Physical Collocation (a) If space for Physical Collocation is immediately available at the time of CLEC's request, SBC-AMERITECH shall include in its notice to CLEC: (i) the space to be provided, and (ii) whether SBC- AMERITECH can deliver the space to CLEC by the date set forth in Section 12.15.2(d).

  • 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 Replacement SAP may replace a Subprocessor without advance notice where the reason for the change is outside of SAP’s reasonable control and prompt replacement is required for security or other urgent reasons. In this case, SAP will inform Customer of the replacement Subprocessor as soon as possible following its appointment. Section 6.3 applies accordingly.

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