Planned Shutdown Sample Clauses

A Planned Shutdown clause defines the procedures and requirements for temporarily suspending operations or services for scheduled maintenance or upgrades. It typically outlines the notice period that must be given to affected parties, the duration and timing of the shutdown, and any obligations to minimize disruption or provide alternative arrangements. This clause ensures that all parties are aware of and can prepare for interruptions, thereby reducing operational risks and misunderstandings during necessary maintenance periods.
POPULAR SAMPLE Copied 2 times
Planned Shutdown. In the event a planned shutdown becomes necessary for either Seller or Buyer on a non-emergency basis, such party shall provide thirty (30) Days notice to the other as provided in the Article XVI hereof.
View SourceView Similar (4)
Planned Shutdown. Zhima Credit shall not assume any liability for interruption of services caused by the Planned Shutdown, but Zhima Credit shall resume the operation of Zhima Credit Platform or the regular access to and use of the services as soon as possible. “Planned Shutdown” means a period of closedown, suspension or interference in the operation of Zhima Credit Platform or the supply of Zhima Credit Services which is arranged by Zhima Credit in advance for the following purposes: (1) to promote any new services or update the existing services to the party receiving the services; (2) to carry out defensive maintenance of the system; (3) to install or make significant adjustment to the basic equipment; or (4)to carry out maintenance of the services and the platform.
View SourceView Similar (2)

Related to Planned Shutdown

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

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

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

  • Commissioning Commissioning tests of the Interconnection Customer’s installed equipment shall be performed pursuant to applicable codes and standards. The ISO and Connecting Transmission Owner must be given at least five Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Day Work The Company shall structure the Project Working Hours to include one (1) half-hour rest break to be taken without deduction of pay by Employees working the Project Working Hours on any day, Monday to Friday.