EMERGENCY REDUCTION IN Sample Clauses

EMERGENCY REDUCTION IN. OPERATIONS (1-2 DAYS) 18-6 In the event of short term emergency conditions (lasting no longer than two calendar days) due to severe weather, natural disaster, major utility failures or other unforeseen circumstances, the University may declare an Emergency Reduction in Operations. The President, or designee, with advice from the Executive Vice Presidents and the Executive Director, Division of Public Safety and Security, will make the decision as to the level of operations which will be maintained. Leadership on the Flint and Dearborn campuses will be responsible for decisions and procedures to reduce operations at their respective campuses. 18-7 Critical services are defined as those services or activities required to provide for the full and complete delivery of care to students and patients; protection of the health and safety of humans and animals in research capacities; and all services of security, police and regulatory personnel. Critical services shall include those providing continuous access to buildings and grounds, communications, and indirect support such as building operations, preservation of infrastructure, utility systems, material procurement and certain contract and legal activities. Critical employees in these functional areas will be expected to report to work during emergency periods in accordance with their unit’s specific designation. Units will annually review their continuity of operations plans and notify their employees of each individual’s critical designation.
AutoNDA by SimpleDocs

Related to EMERGENCY REDUCTION IN

  • Emergency Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-­‐shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.

  • Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above.

  • Emergency Repairs a) The landlord must post and maintain in a conspicuous place on the residential property, or give to the tenant in writing, the name and telephone number of the designated contact person for emergency repairs. b) If emergency repairs are required, the tenant must make at least two attempts to telephone the designated contact person, and then give the landlord reasonable time to complete the repairs. c) If the emergency repairs are still required, the tenant may undertake the repairs, and claim reimbursement from the landlord, provided a statement of account and receipts are given to the landlord. If the landlord does not reimburse the tenant as required, the tenant may deduct the cost from rent. The landlord may take over completion of the emergency repairs at any time. d) Emergency repairs must be urgent and necessary for the health and safety of persons or preservation or use of the residential property and are limited to repairing i) major leaks in pipes or the roof,

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

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

  • Emergency Maintenance LightEdge reserves the right to perform emergency Service maintenance as needed outside the Scheduled Maintenance window, in which case LightEdge will make a reasonable effort to notify the Customer if feasible under the circumstances. Any such maintenance will be considered an “Emergency Maintenance”. All Service SLAs will apply during Emergency Maintenance.

  • Emergency Rate Redetermination Forest Service shall redetermine rates if, upon Purchaser's application, Forest Service determies that, because of changes in the timber market since the award date or the last rate redetermination under this provision, the Producer Price Index identified in A20 has declined by 25 percent. Rates shall be redetermined under B3.3 and shall be considered established under B3.1 for timber Scaled subsequent to Purchaser's application. This Subsection shall not apply during Contract Term Extension.

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

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