FORCED OUTAGES OR PARTIAL FORCED OUTAGES Clause Samples

FORCED OUTAGES OR PARTIAL FORCED OUTAGES. The Seller shall notify the Purchaser as soon as practicable after the occurrence of a Forced Outage or Partial Forced Outage, which notice shall set forth the likely cause thereof (if known at the time), together with an estimated time-frame within which such Forced Outage or Partial Forced Outage is likely to end, on the basis of information available to the Seller at that time. The Seller shall, periodically, update any notice provided under this Section 5.14 on the basis of further information that may, from time to time, become available to the Seller.
View SourceView Similar (2)
FORCED OUTAGES OR PARTIAL FORCED OUTAGES. The Seller shall notify the Purchaser as soon as practicable after the occurrence of a Forced Outage or Partial Forced Outage which notice shall set out the likely cause thereof (if known at the time), together with an estimated time frame within which such Forced Outage or Partial Forced Outage is likely to end on the basis of information available to the Seller at the time. The Seller shall, periodically, update any notice provided under this Section 5.14on the basis of further information that may become available to the Seller from time to time.
View SourceView Similar (2)

Related to FORCED OUTAGES OR PARTIAL FORCED OUTAGES

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

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

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

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