Unexpected Outages Sample Clauses

Unexpected Outages. GDI will use commercially provided or approved for use by GDI, (B) any modification of reasonable efforts to avoid unexpected outages and to restore Access promptly as practicable. If you do not have Access for more than two (2) consecutive hours within any 24-hour period because of an unexpected outage caused by GDI, you may request credit for one day of the applicable fees (based on an average of that month’s invoice). THIS IS YOUR SOLE AND EXCLUSIVE REMEDY AND GDI’S ENTIRE LIABILITY FOR UNSCHEDULED DOWNTIME OR OUTAGES, AND GDI WILL NOT BE LIABLE FOR ANY DAMAGES RELATED TO ANY UNSCHEDULED DOWNTIME OR OUTAGES.
Sample 1
AutoNDA by SimpleDocs
Unexpected Outages. GDI will use commercially reasonable efforts to avoid unexpected outages and to restore Access promptly as practicable. If you do not have Access for more than two (2) consecutive hours within any 24- hour period because of an unexpected outage caused by GDI, you may request credit for one day of the applicable fees (based on an average of that month’s invoice). THIS IS YOUR SOLE AND EXCLUSIVE REMEDY AND GDI’S ENTIRE LIABILITY FOR UNSCHEDULED DOWNTIME OR OUTAGES, AND GDI WILL NOT BE LIABLE FOR ANY DAMAGES RELATED TO ANY UNSCHEDULED DOWNTIME OR OUTAGES.
Sample 1

Related to Unexpected Outages

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

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

  • Expected Outcomes The educational goals and objectives for improving student achievement, including how much academic improvement students are expected to show each year, how student progress and performance will be evaluated and the specific results to be attained, as described in Section 5a of the application: Student Performance, Assessment and Evaluation.

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

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

  • Expected Outcome With this waiver, the school will be able to implement its program and evaluate its teachers in accordance with its Performance Appraisal System, which is designed to produce greater accountability and be consistent with the school’s goals and objectives. This will benefit staff members as well as students and the community. Non-Automatic Waivers: Statute Description and Rationale and Replacement Plan

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

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

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

  • Force Majeure Event 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event.

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