Outages Ercot Iso Sample Clauses

Outages Ercot Iso 
AutoNDA by SimpleDocs

Related to Outages Ercot Iso

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

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

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

  • Outages and Interruptions Outages.

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

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

  • Maintenance Outages If Seller reasonably determines that it is necessary to schedule a Maintenance Outage, Seller shall notify Buyer of the proposed Maintenance Outage at least five (5) days before the outage begins (or such shorter period to which Buyer may reasonably consent in light of then existing conditions). Upon such notice, the Parties shall plan the Maintenance Outage to mutually accommodate the reasonable requirements of Seller and the service obligations of Buyer; provided, however, that, unless Buyer otherwise consents, such consent not to be unreasonably withheld, no Maintenance Outage may be scheduled between the hour ending 0700 through the hour ending 2200, Monday through Saturday, during the time period commencing on May 15 and concluding on September 15. Notice of a proposed Maintenance Outage shall include the expected start date and time of the outage, the amount of Capacity of the Facility that will not be available, and the expected completion date and time of the outage. Seller shall give Buyer notice of the Maintenance Outage as soon as Seller determines that the Maintenance Outage is necessary. Buyer shall promptly respond to such notice and may request reasonable modifications in the schedule for the outage. Seller shall use all reasonable efforts to comply with any request to modify the schedule for a Maintenance Outage. Seller shall notify Buyer of any subsequent changes in Capacity available to Buyer or any changes in the Maintenance Outage completion date and time. As soon as practicable, any notifications given orally shall be confirmed in writing. Seller shall take all reasonable measures and exercise its best efforts in accordance with Prudent Electrical Practices to minimize the frequency and duration of Maintenance Outages.

  • 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

  • Uncontrollable Forces Tariff Provisions Section 14.1 of the CAISO Tariff shall be incorporated by reference into this Agreement except that all references in Section 14.1 of the CAISO Tariff to Market Participants shall be read as a reference to the Participating Generator and references to the CAISO Tariff shall be read as references to this Agreement.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!