Facility Outages and Maintenance Protocol Sample Clauses

Facility Outages and Maintenance Protocol. Seller, in its capacity as Scheduling Coordinator, is responsible for submitting requests for CAISO approvals for Facility outages, including changes in its outage schedules when CAISO disapproves Seller’s schedules or cancels previously approved outages and for entering Facility outages in the CAISO’s Outage Management System or successor system. As Scheduling Coordinator, Seller shall put forth commercially reasonable efforts to request and communicate CAISO approvals for Project outages in a timely manner to Buyer. No later than sixty (60) days prior to commencing Facility construction, Seller shall deliver to Buyer for its review and approval (such approval not to be unreasonably delayed or withheld) a supplement to this Agreement with additional and supplementary details, procedures and requirements for planning and carrying out Facility maintenance, testing and related activities (including for warranty maintenance and to maximize equipment longevity and performance), and including the scheduling of such activities, all based on the then current design of the Facility (“Maintenance Protocol”). Thereafter, from time to time, Seller may deliver to Buyer for its review and approval (such approval not to be unreasonably delayed or withheld) any Seller recommended updates to the then current Maintenance Protocol. The initial Maintenance Protocol (and each update thereto), once approved by Buyer, shall be deemed an amendment to this Agreement. The Maintenance Protocol shall, among other items, include provisions allowing for up to one hundred 100 hours per Contract Year for scheduled Facility maintenance during days and hours as designated by Seller (“Approved Maintenance Hours”).
Sample 1
AutoNDA by SimpleDocs

Related to Facility Outages and Maintenance Protocol

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

  • SYSTEM CHANGES AND MAINTENANCE/SUPPORT The Contractor shall give a minimum of 5 business days advance Written notice to the designated Authorized User contact of any upgrades, system changes and Maintenance/support actions that may potentially impact services described in the Authorized User Agreement. Upgrades, system changes, and Maintenance/support actions which are required by system vulnerabilities or emergency situations shall be carried out by the Contractor to protect the system. Authorized Users shall be notified by the Contractor as soon as possible after the change has taken place. Contractor shall provide documentation of upgrades, system changes and Maintenance/support actions upon request from an Authorized User. EXPIRATION, TERMINATION OR SUSPENSION OF SERVICES Return of Data The Contractor shall return Data in a format agreed upon within the Authorized User Agreement or as agreed to with the Authorized User. This can, if specified within the Authorized User Agreement, be carried out by providing application programmable interface or other such efficient electronic tools. The Contractor must certify all Data has been removed from its system and removed from backups within timeframes established in the Authorized User Agreement or as agreed to with the Authorized User. Suspension of Services During any period of suspension of service, the Authorized User shall have full access to all Data at no charge. This can, if specified within the Authorized User Agreement, be carried out by providing an application programmable interface or other such efficient electronic tools. The Contractor shall not take any action to erase and/or withhold any Authorized User Data, except as directed by the Authorized User. Expiration or Termination of Services Upon expiration or termination of an Authorized User Agreement, the Authorized User shall have full access to all Data for a period of 60 calendar days. Unless noted in the original Authorized User Agreement, this period will be covered at no charge. This can, if specified within the Authorized User Agreement, be carried out by providing application programmable interface or other such efficient electronic tools. During this period, the Contractor shall not take any action to erase and/or withhold any Data, except as directed by the Authorized User. An Authorized User shall have the right to specify a period in excess of 60 calendar days in its RFQ. SECURE DATA DISPOSAL When requested by the Authorized User, the Contractor shall destroy Data in all of its forms, including all back-ups. Data shall be permanently deleted and shall not be recoverable, according ITS Policy S13-003 Sanitization/Secure Disposal or successor and S14-003 Information Security Controls or successor. Certificates of destruction, in a form acceptable to the Authorized User, shall be provided by the Contractor to the Authorized User.

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

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

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

  • TECHNICAL SUPPORT AND MAINTENANCE If technical support and maintenance is a part of the Goods that Contractor provides under the Contract, Contractor will use commercially reasonable efforts to respond to the Department in a reasonable time when the Department makes technical support or maintenance requests regarding the Goods.

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

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

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

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

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