Downtime Event Sample Clauses

Downtime Event. In the event that CNP discovers or is notified by Customer that Customer is experiencing a Downtime Event, CNP will take all actions necessary to determine the source of the Downtime Event. a. Time to Discover Source of Downtime Event; Notification of Customer. CNP will handle Downtime Events according to the following schedule: [*] Confidential information has been omitted and separately filed with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. i. Severity 1: CNP will communicate with Customer within twenty (20) minutes of discovering, or being notified of such a Downtime Event. Subsequently, CNP will communicate at least once with Customer within two (2) hours with a notification of resolution of the Downtime Event or a schedule for resolution. ii. Severity 2: CNP will communicate with Customer within forty-five (45) minutes of discovering, or being notified of such a Downtime Event. Subsequently, CNP will communicate at least once with Customer within four (4) hours with a notification of resolution of the Downtime Event or a schedule for resolution. iii. Severity 3: CNP will communicate with Customer within two (2) hours of discovering, or being notified of such a Downtime Event. Subsequently, CNP will communicate at least once with Customer within eight (8) hours with a notification of resolution of the Downtime Event or a schedule for resolution. iv. Severity 4: CNP will communicate with Customer within eight (8) hours of discovering, or being notified of such a Downtime Event. Subsequently, CNP will communicate at least once with Customer within one (1) calendar day with a notification of resolution of the Downtime Event or a schedule for resolution. b. Resolution of Downtime: CNP will use commercially reasonable efforts to resolve all Downtime Events based on the severity levels set forth above and in accordance with the commercial impact to Customer caused by the Downtime Event, and which resolution period will not materially adversely affect Customer's benefits set forth in this Agreement. c. If the source of and remedy to the Downtime Event reside outside of the CNP LAN or WAN, CNP will use commercially reasonable efforts to notify the party(ies) responsible for the source of the Downtime Event and cooperate with such party(ies) to resolve such problem as soon as possible.
View SourceView Similar (2)
Downtime Event. (1) any outages of any public internet backbones, networks, servers or other utilities,
View Source

Related to Downtime Event

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

  • Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.

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

  • Termination due to Force Majeure 13.5.1 If the Force Majeure Event or its effects continue to be present beyond the period as specified in Article 4.5.3, either Party shall have the right to cause termination of the Agreement. In such an event, this Agreement shall terminate on the date of such Termination Notice.

  • Termination Notice for Force Majeure Event 21.7.1 If a Force Majeure Event subsists for a period of 60 (sixty) days or more within a continuous period of 120 (one hundred and twenty) days, either Party may in its discretion terminate this Agreement by issuing a Termination Notice to the other Party without being liable in any manner whatsoever, save as provided in this Article 21, and upon issue of such Termination Notice, this Agreement shall, notwithstanding anything to the contrary contained herein, stand terminated forthwith; provided that before issuing such Termination Notice, the Party intending to issue the Termination Notice shall inform the other Party of such intention and grant 15 (fifteen) days time to make a representation, and may after the expiry of such 15 (fifteen) days period, whether or not it is in receipt of such representation, in its sole discretion issue the Termination Notice.