Planned Outage Timeframe Sample Clauses

Planned Outage Timeframe. The Planned Outage Timeframe defines the hours and days in which a Planned Outage may occur ("Planned Outage Timeframe"). The Planned Outage Timeframe for the System Services is as follows:
AutoNDA by SimpleDocs
Planned Outage Timeframe. Nameserver =(no planned outages allowed); and
Planned Outage Timeframe. Whois = 0600-1400 UTC Sunday.
Planned Outage Timeframe. SRS = 3 days;
Planned Outage Timeframe. Whois = 3 days.
Planned Outage Timeframe. The Planned Outage Timeframe defines the hours and days in which the Planned Outage can occur. The Planned Outage Timeframe for the Core Services is as follows: • Planned Outage Timeframe–SRS = 1201-0800 UTC Sunday; • Planned Outage Timeframe–Nameserver =(no planned outages allowed); and • Planned Outage Timeframe–Whois = 0600-1400 UTC Sunday. ▪ Planned Outage Notification. The xxxx.xx Administrator will notify all of its registrars of any Planned Outage. The Planned Outage Notification Performance Specification defines the number of days prior to a Planned Outage that the xxxx.xx Administrator will notify its registrars. The Planned Outage Notification for the Core Services is as follows: • Planned Outage Timeframe–SRS = 3 days; • Planned Outage Timeframe–Nameserver =(no planned outages allowed); and • Planned Outage Timeframe–Whois = 3 days.

Related to Planned Outage Timeframe

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

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

  • Response Times (a) LogRhythm will respond to new support cases whether received via a telephone call or email within (i) four (4) Support Hours after receipt if received during a Business Day or (ii) by 12:00 p.m. Mountain Time the following Business Day if received after the end of a Business Day. LogRhythm will respond to new support cases via email or by directly contacting the applicable designated users. Response times for open support cases will vary depending on the specifics of the case and any Escalation required. If a response will require more than one business day to prepare, Customer will be notified and informed when a response can be expected.

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