Forced Outages and Maintenance Outages Sample Clauses

Forced Outages and Maintenance Outages. (a) In the event that in a year “n” the sum of: (i) the Equivalent Forced Outages Energy for the Facility (“a”); plus (ii) the Maintenance Outages Energy (“b”); plus (iii) the Scheduled Outages Energy (“c”);, shall : exceed Ω MWh in any Contract Year where Ω MWh equals the Average Dependable Capacity for that Contract Year multiplied by eight hundred and seventy six (876) hours in all Contract Years; then, the Company shall pay BPDB , as liquidated damages, the Capacity Factor Amount multiplied by (a+b+c)- Ω) for that Contract Year. (b) The Capacity Factor Amount in any Contract Year “n” shall be equal to the product of (i) Average Capacity Pricen (as defined in Section 8.3(c) below) and (ii) 1.522.
Sample 1
AutoNDA by SimpleDocs
Forced Outages and Maintenance Outages. (a) In the event that the sum of: (i) the Equivalent Forced Outages Energy for the Facility (“a”); plus (ii) the Maintenance Outages Energy (“b”); plus (iii) the Scheduled Outages Energy (“c”), shall exceed Ω MWh in any Contract Year and during simple cycle operation, where Ω MWh equals the Average Dependable Capacity for that Contract Year multiplied by: (1) One thousand three hundred and seventy six (1376) hours in the third Contract Year (the “Major Maintenance Year”) and every third Contract Year after the Major Maintenance Year; provided, that the Company may at its sole discretion elect that the Major Maintenance Year shall occur in the Contract Year immediately preceding or immediately following any such Contract Year (instead of such Contract Year) and each subsequent Major Maintenance Year shall be adjusted accordingly; and (2) Eight hundred and seventy six (876) hours in all Contract Years including simple cycle operation period other than those Contract Years referred to in sub paragraphs (a)(1) above, then, the Company shall owe BPDB, as liquidated damages, the Capacity Factor Amount multiplied by ((a + b + c) - Ω) for that Contract Year. (b) In computing liquidated damages payable by the Company for the first Contract Year and during simple cycle operation, the sum of (a + b + c) in this Section 8.3 shall be adjusted by multiplying (a + b + c) by 0.75. There shall be no adjustment in any subsequent Contract Year. (c) The Capacity Factor Amount in any Contract Year “n” shall be equal to the product of (i) Average Capacity Pricen (as defined in Section 8.3(d) below) and (ii) 1.522. (d) In respect of this Section 8.3, the Average Capacity Pricen in Taka per kW – Month for Contract Year, n, shall be calculated as follows to determine any liquidated damages payable under this Section: Average Capacity Pricen = ∑(((RNECPn + RECP(US)n x FIIF qm) x CEinvoicem) + (RECP(Tk)mn x LIIFqm))/12 m where, = 1 to 12 RNECPn, RECP(US)n, RECP(Tk)n, FIIFqm, LIIFqm and CEinvoicem shall have the meanings set out in Section 13.
Sample 1
Forced Outages and Maintenance Outages. (a) In the event that the sum of: (i) the Equivalent Forced Outages Energy for the Facility (“a”); plus (ii) the Maintenance Outages Energy (“b”); plus (iii) the Scheduled Outages Energy (“c”), shall exceed Ω MWh in any Contract Year and during operation, where Ω MWh equals the Average Dependable Capacity for that Contract Year multiplied by: (1) One thousand four hundred and forty (1440) hours in the fifth Contract Year (the “Major Maintenance Year”) and every fifth Contract Year after the Major Maintenance Year; provided, that the Company may at its sole discretion elect that the Major Maintenance Year shall occur in the Contract Year immediately preceding or immediately following any such Contract Year (instead of such Contract Year) and each subsequent Major Maintenance Year shall be adjusted accordingly; and (2) One thousand three hundred and fourteen (1314) hours in all Contract Years other than those Contract Years referred to in sub paragraphs (a)(1) above, then, the Company shall owe BPDB, as liquidated damages, the Capacity Factor Amount multiplied by ((a + b + c) - Ω) for that Contract Year. (b) In computing liquidated damages payable by the Company for the first Contract Year and during operation, the sum of (a + b + c) in this Section 8.3 shall be adjusted by multiplying (a + b + c) by 0.75. There shall be no adjustment in any subsequent Contract Year.
Sample 1

Related to Forced Outages and Maintenance Outages

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

  • Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

  • Unscheduled Maintenance Unscheduled maintenance may be required to resolve issues that are critical for Customer and/or performance of the Cloud Services. Druva will use its commercially reasonable efforts to notify Customer at least six (6) hours prior to the unscheduled maintenance.

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

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

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

  • Scheduled Maintenance Maintenance window for disruptive work to Service will be limited 12:00 A.M. to 4:00 A.M., Central Daylight Time (CDT), any day with requirement of one (1) calendar week notification to Customer prior to maintenance. LightEdge will send an e-mail notification of such disruptive maintenance to Service to Authorized Contacts of Customer. Once notification is sent to Customer this will be considered a “Scheduled Maintenance”. Any Service SLAs will NOT apply during a Scheduled Maintenance.

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

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