Scheduling of Maintenance to Avoid High Flow Periods Sample Clauses

Scheduling of Maintenance to Avoid High Flow Periods. Chelan PUD began an aggressive program in 2000 to limit the incidence of spill due to maintenance outages during periods of the year and times of day when river flows approach the hydraulic capacity of the powerhouse. The hydraulic capacity of the powerhouse, when all 11 turbines are operating, is 204,000 cfs at the most efficient operating point and 212,000 cfs can be passed without needing to spill. Typically, these flow levels are not reached during river management for power generation. The hydraulic capacity of the powerhouse, when 10 turbines are available, is reduced to either 182,000 cfs or 187,000 cfs, depending on the type of turbine out of service for maintenance. The planning process schedules lengthy maintenance outages to the months in the year when flow releases from Grand Coulee and power demand are typically the lowest, with most turbine overhaul scheduled for March to mid-May or September to mid- November. Short duration outages, such as inspections, trash rack cleaning and smaller repair jobs are either scheduled for nighttime and weekends or, if scheduled during the day, are of a nature that work can be suspended or postponed to avoid spill if river flows approach the hydraulic capacity. Outage planning is focused on the shape of the daily flow pattern. The use of the Hourly Coordination Agreement gives the project operations personnel sufficient advance warning to cancel planned outages and avoid spill if the flow pattern changes to higher levels than predicted.
Sample 1
AutoNDA by SimpleDocs

Related to Scheduling of Maintenance to Avoid High Flow Periods

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

  • INTERIM MAINTENANCE PERIOD During the interim maintenance period between obtaining of the completion certificate of such Project and formation and operationalization of the Association the Promoter shall through itself or through a facility management company to run, operate, manage and maintain the Common Areas. The Promoter shall endeavour that the committee responsible for the maintenance and operation of the Common Areas will be required to provide manpower for maintaining the Common Areas, wherever required, and to collect maintenance charges and also guest charges and the user charges for the utilities being provided on “pay by use” basis, if any. The maintenance and management of Common Areas by the committee will primarily include but not limited to maintenance of water works, common electrical installations, DG Sets, landscaping, driveways, parking areas, lobbies, lifts and staircases, AMC’s etc. It will also include safety and security of the Project such as fire detection and protection and management of general security control of the Project. The Rules/ Bye Laws to regulate the use and maintenance of the Common Areas shall during the interim maintenance period shall be framed by the Promoter with such restrictions as may be necessary for proper maintenance and all the Allottees are bound to follow the same. After the Common Areas of the Project are handed over to the Association, the Association may adopt the Rules and the Bye laws framed by the Promoter, with or without amendments, as may be deemed necessary by the Association.

  • Maintenance Scheduling The NTO shall schedule maintenance of its facilities designated as NTO Transmission Facilities Under ISO Operational Control and schedule any outages (other than forced transmission outages) of said transmission system facilities in accordance with outage schedules approved by the ISO. The NTO shall comply with maintenance schedules coordinated by the ISO, pursuant to this Agreement, for NTO Transmission Facilities Under ISO Operational Control. The NTO shall be responsible for providing notification of maintenance schedules to the ISO for NTO Transmission Facilities Requiring ISO Notification. The NTO shall provide notification of maintenance schedules to affected Transmission Owners for NTO Transmission Facilities Requiring ISO Notification and Local Area Transmission Facilities pursuant to Section 3.5.3 of the ISO Services Tariff.

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

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Maintenance Period During the Maintenance Period the Developer shall at its own expense maintain repair and otherwise keep the Works in good working order and repair to the reasonable satisfaction of xxx Xxxxxxxxxx unless xxx Xxxxxxxxxx shall declare that any required maintenance and/or repair is an emergency in which case the Developer shall carry out the said maintenance and/or repair immediately

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

  • Penalties for Non-compliance to Service Level Agreement Where the Supplier/Service Provider fails to deliver the Goods/Services within the agreed and accepted milestone timelines and provided that the cause of the delay was not due to a fault of Transnet, penalties shall be imposed at …………………………………………………… .

  • Support and Maintenance Where Licensee purchases support and/or maintenance services, Licensee’s initial support and/or maintenance term will begin upon delivery to Licensee of the Licensed Software and continue for one (1) year thereafter (or the length of the term if less than a year for any subscription/term license) unless otherwise specified in the applicable annual support and/or maintenance agreement, Product Order, or other written agreement executed between Licensor and Licensee. Where Licensee purchases support and/or maintenance for any Licensed Software, Licensee hereby agrees that it shall purchase such support and/or maintenance services for all of Licensee’s licensed units of such Licensed Software product. Support and/or maintenance services provided by Licensor will be subject to Licensor’s then current applicable standard annual support and/or maintenance agreement unless otherwise agreed by the parties in writing.

  • Operations and Maintenance Notice Each Party shall notify the other Parties in writing of the identity of the person(s) that it designates as the point(s) of contact with respect to the implementation of Articles 9 and 10.

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