Emergency Maintenance Notification Clause Samples
The Emergency Maintenance Notification clause establishes the procedure for informing relevant parties when urgent maintenance is required. Typically, this clause outlines how and when notice must be given, such as via email or phone, and may specify the minimum information to be included in the notification, like the nature of the emergency and expected duration of the maintenance. Its core function is to ensure timely communication during unforeseen maintenance events, minimizing disruption and clarifying responsibilities during emergencies.
POPULAR SAMPLE Copied 12 times
Emergency Maintenance Notification. A. In the event that maintenance is required outside of the Scheduled Maintenance Window and it will adversely affect Client’s Users, Synacor will notify Client about the emergency maintenance window as soon as Synacor determines such emergency maintenance window is needed. Notification will detail the expected degree of adverse effect on the applicable Service or availability thereof. Emergency maintenance windows are counted against Portal or Email Availability percentages (as applicable), unless Synacor and Client mutually agree otherwise in writing (email being sufficient for this purpose).
Emergency Maintenance Notification. Emergency maintenance may be needed in two types of situations. The first is the need to repair an issue that is creating downtime or degradation to the Client Branded Portal (“Reactive Emergency Maintenance”). The second is maintenance Synacor believes would be prudent to be perform prior to the Scheduled Maintenance period to avoid potential issues (“Preventative Emergency Maintenance”). In the event that either type of emergency maintenance is required, Synacor will make reasonable efforts to notify Client about the emergency maintenance window based on practicality and the degree of adverse affect on the applicable service or availability thereof. Reactive Emergency maintenance windows are counted against Portal Availability percentages (as applicable). To the extent Client approves Preventative Emergency Maintenance (which approval expressly excuses such Preventative Emergency Maintenance from the calculation of the Portal Availability percentages), or the need for the emergency maintenance window is necessitated by a Client change as described in Section 1(e) above, such maintenance will not be counted against the Portal Availability percentages.
Emergency Maintenance Notification. In the event that emergency maintenance is required which will adversely affect the Platform, Developer will notify Company of such emergency maintenance. Emergency maintenance windows are not counted against System Availability percentage, provided that the cause for such emergency maintenance results from events beyond Developer’s control (i.e., the cause does not result from Developer’s failure to maintain commercially reasonable hardware, redundancy and security, or from Developer’s failure to timely install third-party patches, bug fixes, updates and the like). Notwithstanding anything herein to the contrary, any failure which causes the Platform or any material functions thereof to be substantially unavailable for more than three (3) business hours shall be deemed a material breach hereof, the cure period for which shall not exceed three (3) days.
Emergency Maintenance Notification. In the event that emergency maintenance (defined as any maintenance that exists that is not within the standard maintenance window described above, or as to which three (3) business days’ prior notification is not given) is required, during which time the System and Services will be unavailable to Client and Users, Synacor will notify the Client as promptly as practicable and, if possible, during the repair window, and so as not to prolong or negatively effect system service or its availability. Emergency maintenance windows are counted against System Availability percentages.
Emergency Maintenance Notification. In the event that emergency maintenance (defined as any maintenance that exists that is not within the Scheduled Maintenance window described above, or as to which three (3) business days’ prior notification is not given) is required, during which time the System and Services will be unavailable to Client and Users, Synacor will notify the Client’s NOC as promptly as practicable and, if possible, prior to the repair window, so as not to prolong or negatively effect the Services, the system, or otherwise Service Availability. Progress updates shall be provided to the Client’s NOC every sixty (60) minutes or less until the maintenance is complete. Emergency maintenance windows are counted against System Availability percentages. The contact number to be used for verbal communications with the Client’s NOC is 1-▇▇▇-▇▇▇-▇▇▇▇ (1-866-CHTRNOC)
Emergency Maintenance Notification. MerlinOne shall make every attempt to give Customer prior notification for any emergency maintenance that falls outside the Normal Maintenance Window.
Emergency Maintenance Notification. In the event that emergency maintenance is required, during which time the system and services will be unavailable to Customer and Customer's Users. Artera will make commercially reasonable efforts to notify the customer during this window where practical and as not to prolong of negatively effect system service or it's availability. Emergency maintenance windows are counted against the 99.5% System Availability benchmark in Section IX.
Emergency Maintenance Notification. Emergency maintenance may be needed in two types of situations. The first is the need to repair an issue that is creating downtime or degradation to the [*] (“Reactive Emergency Maintenance”). The second is maintenance Synacor believes would be prudent to be perform prior to the Scheduled Maintenance period to avoid potential issues (“Preventative Emergency Maintenance”). In the event that either type of emergency maintenance is required, Synacor will BUS_RE/5266520.1 [*] = CERTAIN INFORMATION HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. make reasonable efforts to notify Client about the emergency maintenance window based on practicality and the degree of adverse affect on the applicable service or availability thereof. Reactive Emergency maintenance windows are counted against [*]Availability percentages (as applicable). To the extent Client approves Preventative Emergency Maintenance (which approval expressly excuses such Preventative Emergency Maintenance from the calculation of the [*]Availability percentages), or the need for the emergency maintenance window is necessitated by a Client change as described in Section 1(e) above, such maintenance will not be counted against the [*]Availability percentages.