Downtime Events Sample Clauses

Downtime Events. If during any Month (as applicable, the “Applicable Month”), (i) one or more Downtime Events occur with respect to a Facility Segment, (ii) such Downtime Events caused the Downtime Percentage for such Facility Segment during the Applicable Month to exceed the lowest percentage specified on Exhibit B during such Month, and (iii) Producer has waived its right to a temporary release of Dedicated Production under Section 2.4(b), then the Individual Fee for the applicable Facility Segment shall be reduced by the reduction percentage corresponding to the applicable Downtime Percentage on the chart on Exhibit B during each hour in which such Facility Segment is available to provide Services (an “Operating Hour”) during the subsequent Month until the reduced Individual Fee has been applied to an aggregate number of Operating Hours equal to the aggregate number of Downtime Hours during the Applicable Month. If the aggregate number of Operating Hours during the subsequent Month is less than the aggregate number of Downtime Hours during the Applicable Month, the applicable reduced Individual Fee shall be applied to Operating Hours during the next-subsequent Month or Months until the reduced Individual Fee has been applied to an aggregate number of Operating Hours equal to the aggregate number of Downtime Hours during the Applicable Month. A reduced Individual Fee that would otherwise apply during any Month subsequent to an Applicable Month shall not be applied until all Downtime Hours from previous Applicable Months have been addressed as provided in this Section.
AutoNDA by SimpleDocs
Downtime Events. (i) If during any Month (A) there has been a Downtime Event, (B) such Downtime Event was not a result of Producer’s (1) production exceeding the production forecast in the Development Report on which the Individual System was based or (2) non-compliance with this Agreement, (C) such Downtime Event caused the Curtailment Percentage for any Individual System during any such Month to exceed the Curtailment Allowance during such Month, and (D) Producer has waived its right to a temporary release of Dedicated Production under Section 2.4(b), then the Individual Fee with respect to such Individual System used to calculate the amounts owed for such Month under Section 6.1(i)(y) shall be reduced as set forth on Exhibit B. (ii) Midstream Co may curtail up to 7% of the volume of Producer’s Dedicated Production that is less than or equal to the capacity for the Individual System as set forth in the applicable System Plan for an Individual System (and there shall be no limit on curtailment of any volumes over the capacity as set forth in the applicable System Plan) (such 7% allowance, the “Curtailment Allowance”). (iii) The actual percentage of Producer’s Dedicated Production that has been curtailed as a result of Downtime Events (as described in Section 6.2(c)(i)(B)) during each Month (the “Curtailment Percentage”) on an Individual System shall be calculated as: Curtailment Percentage (expressed as a percentage) = (1 – [ (A / B) / C ] ) x ( B / D ), where A = (expressed as a number) the aggregate volume (in Barrels) of Producer’s Dedicated Production delivered into and received on such Individual System on any and all Days that a Downtime Event (as described in Section 6.2(c)(i)(B)) occurred during such Month; B = the number of Days that a Downtime Event (as described in Section 6.2(c)(i)(B)) occurred during such Month;
Downtime Events. If (i) there has been a Downtime Event and (ii) such Downtime Event caused the Downtime Duration for any facility on an Individual System during any such calendar quarter to extend for the duration shown on Exhibit B, then the applicable Individual First Phase Fee shall be reduced as set forth in Exhibit B for such duration. To the extent that, as a result of a Downtime Event, Producer exercises its right to a temporary release pursuant to Section 2.4(b), Producer shall be entitled to both such release and the reduction of the applicable Individual First Phase Fee pursuant to this Section 6.2(c).
Downtime Events. Downtime is defined as any event, within YPS control, which includes the physical facility and direct internet connections of YPS facilities and contracted hosts, which prohibits access for a period of time that is greater than 5 minutes, except as allowed for in Exhibit C, paragraph B. An example of a non-YPS controlled event is a Pacific Bxxx service interruption, which renders the entire internet backbone inoperable, for 3 hours due to a switching station fire.
Downtime Events. If during any Month (i) there has been a Downtime Event, (ii) such Downtime Event was not a result of Producer’s production exceeding the production forecast in the Development Report on which the Individual System was based, (iii) such Downtime Event caused the Downtime Percentage for any Individual System during such Month to exceed the lowest percentage specified on Exhibit B during such Month, and (iv) Producer has waived its right to a temporary release of Dedicated Production under Section 2.4(b), then the Individual Fee with respect to such Individual System used to calculate the amounts owed for such Month under Section 6.1(y) shall be reduced by the reduction percentage corresponding to the applicable Downtime Percentage on the chart on Exhibit B.
Downtime Events. Subject to any applicable exclusions described below, the following shall be events that qualify as Downtime: html web pages hosted by Licensor that are used by Customer access and control the Licensor Service are not accessible to Licensor’s standard and customary monitoring tools over 4 successive polling attempts.
Downtime Events. Consistent with DAC's quality assurance policy, DAC will use all commercially reasonable efforts to avoid Downtime Events, including the following:
AutoNDA by SimpleDocs

Related to Downtime Events

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

  • Uncontrollable Events BISYS assumes no responsibility hereunder, and shall not be liable for any damage, loss of data, delay or any other loss whatsoever caused by events beyond its reasonable control.

  • Force Majeure Events a) Neither Party shall be responsible or liable for or deemed in breach hereof because of any delay or failure in the performance of its obligations hereunder (except for obligations to pay money due prior to occurrence of Force Majeure events under this Agreement) or failure to meet milestone dates due to any event or circumstance (a "Force Majeure Event") beyond the reasonable control of the Party experiencing such delay or failure, including the occurrence of any of the following: i) acts of God; ii) typhoons, floods, lightning, cyclone, hurricane, drought, famine, epidemic, plague or other natural calamities; iii) acts of war (whether declared or undeclared), invasion or civil unrest; iv) any requirement, action or omission to act pursuant to any judgment or order of any court or judicial authority in India (provided such requirement, action or omission to act is not due to the breach by the SPG or of any Law or any of their respective obligations under this Agreement); v) inability despite complying with all legal requirements to obtain, renew or maintain required licenses or Legal Approvals; vi) earthquakes, explosions, accidents, landslides; fire; vii) expropriation and/or compulsory acquisition of the Project in whole or in part by Government Instrumentality; viii) chemical or radioactive contamination or ionizing radiation; or ix) damage to or breakdown of transmission facilities of GETCO/ DISCOMs; x) Exceptionally adverse weather condition which are in excess of the statistical measure of the last hundred (100) years.

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

  • Adverse Events Subsequent to the date hereof, there shall not have occurred any of the following: (i) a suspension or material limitation in trading in securities generally on the New York Stock Exchange, the NASDAQ National Market or the NASDAQ Global Market, (ii) a general moratorium on commercial banking activities in the People’s Republic of China or New York, (iii) the outbreak or escalation of hostilities involving the United States or the People’s Republic of China or the declaration by the United States or the People’s Republic of China of a national emergency or war if the effect of any such event specified in this clause (iii) in your reasonable judgment makes it impracticable or inadvisable to proceed with the public offering or the delivery of the Shares on the terms and in the manner contemplated in the Prospectus, or (iv) such a material adverse change in general economic, political, financial or international conditions affecting financial markets in the United States or the People’s Republic of China having a material adverse impact on trading prices of securities in general, as, in your reasonable judgment, makes it impracticable or inadvisable to proceed with the public offering of the Shares or the delivery of the Shares on the terms and in the manner contemplated in the Prospectus.

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

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.

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

  • Service Interruptions The Company may need to interrupt Your access to the Website to perform maintenance or emergency services on a scheduled or unscheduled basis. You agree that Your access to the Website may be affected by unanticipated or unscheduled downtime, for any reason, but that the Company shall have no liability for any damage or loss caused as a result of such downtime.

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