Planned Outage Notification Clause Samples

The Planned Outage Notification clause requires one party, typically a service provider, to inform the other party in advance about any scheduled interruptions to services or system availability. This notification usually includes details such as the expected date, time, and duration of the outage, and may specify the minimum notice period required before the outage occurs. By mandating advance notice, the clause helps affected parties prepare for service disruptions, minimizing operational impact and ensuring transparency in service management.
POPULAR SAMPLE Copied 2 times
Planned Outage Notification. The Registry Operator must notify all of its Registrars of any Planned Outage. The Planned Outage Notification Performance Specification defines the number of days prior to a Planned Outage that the Registry Operator must notify its Registrars. The Planned Outage Notification for the Core Services is as follows:
View SourceView Similar (8)
Planned Outage Notification. The usTLD Administrator will notify all of its registrars of any Planned Outage. The Planned Outage Notification Performance Specification defines the number of days prior to a Planned Outage that the usTLD Administrator will notify its registrars. The Planned Outage Notification for the Core Services is as follows:
View Source
Planned Outage Notification. The Registry Operator shall notify all ICANN-Accredited Registrars of any Planned Outage ("Planned Outage Notification"). The Planned Outage Notification shall set forth the date and time of the Planned Outage. The number of days prior to a Planned Outage that the Registry Operator shall notify the Registrar Community is as follows: (i) Planned Outage Timeframe - SRS = 30 days for general maintenance and 90 days for Updates or Upgrades as defined in the Patch, Update and Upgrade Policy in Section 5 of this Appendix 7; (ii) Planned Outage Timeframe - DNS Name Server = no Planned Outages allowed; and (iii) Planned Outage Timeframe - Whois = no Planned Outages allowed. The Planned Outage Notification metric is a Credit Level 5.
View SourceView Similar (15)
Planned Outage Notification. Genuity may add remove and/or modify network --------------------------- elements to restore/maintain service. Genuity will use commercially reasonable efforts to minimize the impact on ▇▇▇▇ Atlantic Services during such addition/removal/modification of network elements. If Genuity determines that ▇▇▇▇ Atlantic Services will be materially impacted, Genuity shall notify ▇▇▇▇ Atlantic seven (7) calendar days prior to the planned network activity and shall obtain ▇▇▇▇ Atlantic approval prior to commencement of such activity, which approval shall not be unreasonably withheld or delayed. In such event, SLAs shall not apply to such outage. Genuity shall provide the planned maintenance notice to a ▇▇▇▇ Atlantic designated email address followed up by a telephone call to the ▇▇▇▇ Atlantic designated maintenance contact(s) as specified in the POC Information/Escalation, Attachment I. Within four (4) months after the Effective Date of the Agreement, the Parties shall complete a mutually agreeable plan pursuant to which Genuity shall change the notification timeframe to ten (1 0) business days.
View SourceView Similar (2)
Planned Outage Notification. Licensor will provide notification to Reseller of all planned outages with the activation system and paging network no less than two business days prior to the planned outage that could place Reseller's Services at risk. Should emergency maintenance outage be necessary, Licensor shall use its commercially reasonable best effort to notify reseller via the Network Management Center (800-500-8113 or E-mail) of the outage existence.
View Source
Planned Outage Notification. Yesup will notify the Customer at least 48 hours prior to a Planned Outage, except in emergency situations. In emergency situations, Yesup will provide the Customer with such notice as is reasonably practicable under the circumstances. Yesup will inform the Customer’s designated point of contact by e-mail. The Customer is responsible for providing accurate and current information for the designated contact persons. Yesup will provide one Service Credit for every outage if it fails to notify the Customer at least 48 hours in advance.
View Source

Related to Planned Outage Notification

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate ▇▇▇▇▇’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Scheduled Outages (a) Commencing at least sixty (60) days before Initial Synchronization and throughout the Delivery Term, Seller shall, no later than January 1, April 1, July 1 and October 1 of each year, submit to SCE, using the Web Client, Seller’s schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty-four month period. (b) Seller shall provide the following information for each proposed planned outage: (i) Start date and time; (ii) End date and time; and (iii) Capacity online, in MW, during the planned outage. (c) Within thirty (30) days after SCE’s receipt of an Outage Schedule, SCE shall notify Seller in writing of any reasonable request for changes to the Outage Schedule, and Seller shall, consistent with Prudent Electrical Practices, accommodate SCE’s requests regarding the timing of any planned outage. (d) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the CAISO. (e) If a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall promptly provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as required in the CAISO Tariff after the condition causing the change becomes known to Seller. (f) Seller shall promptly prepare and provide to SCE upon request, using the Web Client, all reports of actual or forecasted outages that SCE may reasonably require for the purpose of enabling SCE to comply with Section 761.3 of the California Public Utilities Code or any Applicable Law mandating the reporting by investor owned utilities of expected or experienced outages by electric energy generating facilities under contract to supply electric energy.

  • Downtime Each of Zero Hash and ZHLS uses commercially reasonable efforts to provide the Services in a reliable and secure manner. From time to time, interruptions, errors, delays, or other deficiencies in providing the Services may occur due to a variety of factors, some of which are outside of Zero Hash’s and/or ZHLS’ control, and some which may require or result in scheduled maintenance or unscheduled downtime of the Services (collectively, “Downtime”). You understand and acknowledge that part or all of the Services may be unavailable during any such period of Downtime, and you acknowledge that Zero Hash and ZHLS are not liable or responsible to you for any inconvenience or losses to you as a result of Downtime. Following Downtime, you further understand and acknowledge that the prevailing market prices of cryptocurrency may differ significantly from the prices prior to such Downtime.

  • Forced Outages During any forced outage, the NYISO or Connecting Transmission Owner may suspend interconnection service to the Interconnection Customer to effect immediate repairs on the New York State Transmission System or the Distribution System. The NYISO shall use Reasonable Efforts to provide the Interconnection Customer with prior notice. If prior notice is not given, the NYISO shall, upon request, provide the Interconnection Customer written documentation after the fact explaining the circumstances of the disconnection.

  • Scheduled Downtime For the purposes of this Agreement, Scheduled Downtime will mean those hours, as determined by us but which will not occur between the hours of 9:00 AM and 5:00 PM Eastern Time, Monday through Friday without your authorization or unless exigent circumstances exist, during which time we will perform scheduled maintenance or adjustments to the Environment. We will use our best efforts to provide you with at least twenty-four (24) hours of notice prior to scheduling Scheduled Downtime.