Outages and Interruptions Outages.
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.
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.
Design Requirements 9.2.1. Metal liner The compressive stress in the liner at zero pressure and 15 °C shall not cause the liner to buckle or crease.
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.
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.
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.
Force Majeure, Notice of Delay, and No Damages for Delay The Contractor will not be responsible for delay resulting from its failure to perform if neither the fault nor the negligence of the Contractor or its employees or agents contributed to the delay and the delay is due directly to acts of God, wars, acts of public enemies, strikes, fires, floods, or other similar cause wholly beyond the Contractor’s control, or for any of the foregoing that affect subcontractors or suppliers if no alternate source of supply is available to the Contractor. In case of any delay the Contractor believes is excusable, the Contractor will notify the Department or Customer in writing of the delay or potential delay and describe the cause of the delay either (1) within 10 days after the cause that creates or will create the delay first arose, if the Contractor could reasonably foresee that a delay could occur as a result, or (2) if delay is not reasonably foreseeable, within five days after the date the Contractor first had reason to believe that a delay could result. The foregoing will constitute the Contractor’s sole remedy or excuse with respect to delay. Providing notice in strict accordance with this paragraph is a condition precedent to such remedy. No claim for damages will be asserted by the Contractor. The Contractor will not be entitled to an increase in the Contract price or payment of any kind from the Department or Customer for direct, indirect, consequential, impact or other costs, expenses or damages, including but not limited to costs of acceleration or inefficiency, arising because of delay, disruption, interference, or hindrance from any cause whatsoever. If performance is suspended or delayed, in whole or in part, due to any of the causes described in this paragraph, after the causes have ceased to exist the Contractor will perform at no increased cost, unless the Department or Customer determines, in its sole discretion, that the delay will significantly impair the value of the Contract to the State of Florida or to Customers, in which case the Department or Customer may (1) accept allocated performance or deliveries from the Contractor, provided that the Contractor grants preferential treatment to Customers with respect to commodities or contractual services subjected to allocation, or (2) purchase from other sources (without recourse to and by the Contractor for the related costs and expenses) to replace all or part of the commodity or contractual services that are the subject of the delay, which purchases may be deducted from the Contract quantity, or (3) terminate the Contract in whole or in part.
Construction With Other Parts Of The Tariff This ISA shall not be construed as an application for service under Part II or Part III of the Tariff.
