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.
Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.
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.
(b) Service Outages Due to Internet Outage or Suspension or Termination of Broadband Service or ISP Service. Service outages or suspensions or terminations of service by your broadband provider or ISP will prevent all Service, including 911 Dialing, from functioning.
(c) Service Outage Due to Suspension or Termination of Your Citi-Tel Account. Service outages due to suspension or termination of your account will prevent all Service, including 911 Dialing, from functioning.
(d) Service Outages Due to ISP or Broadband Provider Blocking of Ports or Other Acts. Your ISP or broadband provider or other third party may intentionally or inadvertently block the ports over which the Service is provided or otherwise impede the usage of the Service. In that event, provided that you alert us to this situation, we will attempt to work with you to resolve the issue. During the period that the ports are being blocked or your Service is impeded, and unless and until the blocking or impediment is removed or the blocking or impediment is otherwise resolved, your Service, including the 911 Dialing feature, may not function. You acknowledge that Citi-Tel is not responsible for the blocking of ports by your ISP or broadband provider or any other impediment to your usage of the Service, and any loss of service, including 911 Dialing, that may result. In the event you lose service as a result of blocking of ports or any other impediment to your usage of the Service, you will continue to be responsible for payment of the Service charges unless and until you terminate the Service in accordance with this Agreement.
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.
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.
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.
Scheduled Outages (1) No later than five (5) Business Days prior to the dates required by the ISO for delivery of schedules for planned outages (which such ISO required delivery dates are currently January 15th, April 15th, July 15th and October 15th of each calendar year during the Facility Term), and at least sixty (60) days prior to the later of: (A) Initial Synchronization, or (B) SCE becoming Seller’s Scheduling Coordinator, Seller shall submit to SCE its schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty four-month period using the Web Client. If Seller fails to submit an Outage Schedule for any period as required under this Section 3.19, then Seller shall not be permitted to schedule or have any planned outages with respect to such period. The foregoing shall not prevent Seller from modifying its Outage Schedule in cooperation with SCE and the ISO. SCE shall provide Notice to Seller in the event that the ISO changes the ISO required delivery dates for schedules for planned outages. In addition, no later than thirty (30) days prior to October 15 of each year, Seller shall submit to SCE its estimate of its planned outages for the following year.
(2) Seller shall provide the following information for each proposed planned outage:
(A) Start date and time;
(B) End date and time; and
(C) Capacity expected to be online, in MW, during the planned outage.
(3) Within twenty (20) Business 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 and as permitted by the ISO, accommodate SCE’s requests regarding the timing of any planned outage.
(4) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the ISO.
(5) In the event a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as soon as practicable after the condition causing the change becomes known to Seller.
(6) 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.
System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades.
5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2
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.
Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.
