Notice of Unplanned Outages Sample Clauses

Notice of Unplanned Outages. Any time period during which the Project is offline other than during a Planned Outage is an “Unplanned Outage.” If Owner determines an Unplanned Outage is required, Owner shall coordinate the timing of such Unplanned Outage with CHGE and, subject to Owner’s obligations under Section 6.1, shall accommodate CHGE’s preferences for the scheduling of such Unplanned Outage. In the event of an unexpected Unplanned Outage, Owner shall provide notice to CHGE by telephone at the telephone number(s) listed in Exhibit H as soon as reasonably practicable and, in all cases, no later than fifteen (15) minutes following the occurrence of such Unplanned Outage. Thereafter, Owner shall, as soon as reasonably practicable, provide CHGE with a notice that includes: (i) the event or condition, (ii) the date and time of such event or condition, (iii) the expected end date and time of such event or condition, (iv) the Products available (if any) during such event or condition, and (v) any other information reasonably requested by CHGE. Notwithstanding the delivery of a notice of an Unplanned Outage or coordination with CHGE to resolve an Unplanned Outage, the Project shall be deemed to be unavailable for the duration of an Unplanned Outage as applicable to the calculation of Guaranteed Availability under Section 6.3.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Notice of Unplanned Outages. The Company will provide notice to the County promptly of any outages of or relating to the Facilities that are not Planned Outages and, as soon as practicable and when reliable information becomes available, provide the County with a schedule (date and hour of day) setting forth when the affected Facilities are expected to return to service. During any such outage, the Company will provide the County with updates as to the status and changes in the expected schedule of the resumption of service to the affected Facilities as soon as such information becomes available in a reliable form.
Sample 1
Notice of Unplanned Outages. Seller shall notify Buyer by telephoning Buyer’s Scheduling Coordinator no later than ten (10) minutes following the occurrence of an Unplanned Outage, or if Seller has knowledge that an Unplanned Outage will occur, within twenty
Sample 1

Related to Notice of Unplanned Outages

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

  • Service Outages (a) Service Outages Due to Power Failure or Disruption. 911 Dialing does not function in the event of a power failure or disruption. If there is an interruption in the power supply, the Service, including 911 Dialing, will not function until power is restored. Following a power failure or disruption, you may need to reset or reconfigure the Device prior to utilizing the Service, including 911 Dialing.

  • 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 Due to the nature of server provision, downtime and lost transmissions may occur as part of routine maintenance. You are advised to maintain a copy of your account status and details of Content purchased.

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

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

  • BELLSOUTH OUTAGE Because BellSouth's equipment has varying degrees of impact on the service provided to the CLECs, restoring service from damaged BellSouth equipment is different. The outage will probably impact a number of Carriers simultaneously. However, the ECC will be able to initiate immediate actions to correct the problem. A disaster involving any of BellSouth's equipment locations could impact the CLECs, some more than others. A disaster at a Central Office (CO) would only impact the delivery of traffic to and from that one location, but the incident could affect many Carriers. If the Central Office is a Serving Wire Center (SWC), then traffic from the entire area to those Carriers served from that switch would also be impacted. If the switch functions as an Access Tandem, or there is a tandem in the building, traffic from every CO to every CLEC could be interrupted. A disaster that destroys a facility hub could disrupt various traffic flows, even though the switching equipment may be unaffected. The NMC would be the first group to observe a problem involving BellSouth's equipment. Shortly after a disaster, the NMC will begin applying controls and finding re-routes for the completion of as much traffic as possible. These reroutes may involve delivering traffic to alternate Carriers upon receiving approval from the CLECs involved. In some cases, changes in translations will be required. If the outage is caused by the destruction of equipment, then the ECC will assume control of the restoration.

  • Outages 9.7.1.1 Outage Authority and Coordination. Interconnection Customer and Transmission Owner may each in accordance with Good Utility Practice in coordination with the other Party and Transmission Provider remove from service any of its respective Interconnection Facilities, System Protection Facilities, Network Upgrades, System Protection Facilities or Distribution Upgrades that may impact the other Party’s facilities as necessary to perform maintenance or testing or to install or replace equipment. Absent an Emergency Condition, the Party scheduling a removal of such facility(ies) from service will use Reasonable Efforts to notify one another and schedule such removal on a date and time mutually acceptable to the Parties. In all circumstances, any Party planning to remove such facility(ies) from service shall use Reasonable Efforts to minimize the effect on the other Parties of such removal.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Other Service Outages If there is a Service outage for any reason, such outage will prevent all Service, including 911 Dialing, from functioning. Such outages may occur for a variety of reasons, including, but not limited to, those reasons described elsewhere in this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.