Airport Maintenance Obligations Sample Clauses

Airport Maintenance Obligations 
AutoNDA by SimpleDocs

Related to Airport Maintenance Obligations

  • Maintenance Obligations In the event the Project includes construction then the following provisions are incorporated into 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.

  • Planned Maintenance (a) Sellers may designate up to twenty (20) Days of Planned Maintenance on Sellers’ Facilities during each Contract Year. Sellers shall be entitled to reduce (including down to zero (0)) its Gas scheduling under Clause 8 and Exhibit 3 for each Day of Planned Maintenance.

  • Facility Maintenance Seller shall perform, or cause to be performed, all scheduled and unscheduled maintenance required on the Facilities in order to meet the Warranty Specifications and Performance Standards. In that regard, Seller’s responsibilities hereunder shall include, without limitation, promptly correcting any Bloom System or BOF malfunctions, either by (i) recalibrating or resetting the malfunctioning Bloom System or BOF, or (ii) subject to Section 5.7(b), repairing or replacing Bloom System or BOF components which are defective, damaged, worn or otherwise in need of repair or replacement.

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

  • Equipment Maintenance If this Contract involves computer or telecommunications hardware or other mechanical or electrical Equipment (use of the word "Equipment" means all the foregoing) as a Deliverable, then, during the warranty period and during any period covered by annual maintenance, the Contractor will provide Equipment maintenance to keep the Equipment in or restore the Equipment to good working order. This maintenance will include preventative and remedial maintenance, installation of safety changes, and installation of engineering changes based upon the specific needs of the individual item of Equipment. This maintenance will also include the repair, replacement, or exchange deemed necessary to keep the Equipment in good working order. For purposes of this Contract, Equipment restored to good working condition means Equipment that performs in accordance with the manufacturer's published specifications. The Contractor will exert its best efforts to perform all fault isolation and problem determination attributed to the Equipment covered under this Contract. The following services are outside the scope of this Contract:

  • Installation and Maintenance Except for the bi‐directional and production metering equipment owned by the City, all equipment on Customer’s side of the delivery point, including the required disconnect device, shall be provided and maintained in satisfactory operating condition by Customer and shall remain the property and responsibility of the Customer. The City will bear no responsibility for the installation or maintenance of Customer’s equipment or for any damage to property as a result of any failure or malfunction thereof. The City shall not be liable, directly or indirectly for permitting or continuing to allow the interconnection of the Facility or for the acts or omissions of Customer or the failure or malfunction of any equipment of Customer that causes loss or injury, including death, to any party.

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

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.

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

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