Response to Outages Sample Clauses

Response to Outages. The Franchisee shall commence efforts to restore service for all Service Outages, whether reported to the Franchisee by the Authorized User or independently identified by the Franchisee, within twenty-four (24) hours. Upon identification of a Service Outage, the Franchisee shall, within such response time, have qualified personnel on site to investigate the outage, assess the cause and commence necessary repairs. To the extent that necessary repairs resulting in restoration of connectivity on the I-Net can be immediately accomplished, the Franchisee shall effect such repairs in connection with its investigation of the cause of the Service Outage. To the extent that repairs cannot be immediately effected, the Franchisee shall, within the response time, inform the County and any other affected Authorized User of the apparent cause of the Service Outage and the anticipated time for restoration of connectivity.
Sample 1
AutoNDA by SimpleDocs
Response to Outages. The response time (the point at which the Franchisee is engaged in restoration of service) for all Service Outages, whether reported to the Franchisee by the User or independently identified by the Franchisee, shall be as specified in Section 4(g)(8)(F). Upon identification of a Service Outage, the Franchisee shall, within such response time, have qualified personnel on site to investigate the outage, assess the cause and commence necessary repairs. To the extent that necessary repairs resulting in restoration of connectivity on the I-Net can be immediately accomplished, the Franchisee shall effect such repairs in connection with its investigation of the cause of the Service Outage. To the extent that repairs cannot be immediately effected, the Franchisee shall, within the response time, inform the County and any other affected User of the apparent cause of the Service Outage, the anticipated time for restoration of connectivity and, in cases where the County bears the cost of maintenance, the estimated cost of restoring connectivity. If the cost of restoring connectivity exceeds $2,000, the County may defer a decision as to such repairs, in which case any time limits for repair or restoration of connectivity shall be suspended until the County requests the Franchisee to undertake such work.
Sample 1
Response to Outages. The response time (the point at which the Grantee is engaged in restoration of service) for all Service Outages, whether reported to the Grantee by the User or independently identified by the Grantee, shall be as specified in Section 6(h)(8)(F). Upon identification of a Service Outage, the Grantee shall, within such response time, have qualified personnel on site to investigate the outage, assess the cause and commence necessary repairs. To the extent that necessary repairs resulting in restoration of connectivity on the I-Net can be immediately accomplished, the Grantee shall effect such repairs in connection with its investigation of the cause of the Service Outage. To the extent that repairs cannot be immediately effected, the Grantee shall, within the response time, inform the City I-Net Coordinator of the apparent cause of the Service Outage, the anticipated time for restoration of connectivity.
Sample 1

Related to Response to Outages

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

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

  • Service Outages (a) Service Outages Due to Power Failure or Disruption. 911 Dialing does not function in the event of a power failure or disruption. If there is an interruption in the power supply, the Service, including 911 Dialing, will not function until power is restored. Following a power failure or disruption, you may need to reset or reconfigure the Device prior to utilizing the Service, including 911 Dialing.

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

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

  • Transmission Delivery Service Implications Network Resource Interconnection Service allows Interconnection Customer's Large Generating Facility to be designated by any Network Customer under the Tariff on Transmission Provider's Transmission System as a Network Resource, up to the Large Generating Facility's full output, on the same basis as existing Network Resources interconnected to Transmission Provider's Transmission System, and to be studied as a Network Resource on the assumption that such a designation will occur. Although Network Resource Interconnection Service does not convey a reservation of transmission service, any Network Customer under the Tariff can utilize its network service under the Tariff to obtain delivery of energy from the interconnected Interconnection Customer's Large Generating Facility in the same manner as it accesses Network Resources. A Large Generating Facility receiving Network Resource Interconnection Service may also be used to provide Ancillary Services after technical studies and/or periodic analyses are performed with respect to the Large Generating Facility's ability to provide any applicable Ancillary Services, provided that such studies and analyses have been or would be required in connection with the provision of such Ancillary Services by any existing Network Resource. However, if an Interconnection Customer's Large Generating Facility has not been designated as a Network Resource by any load, it cannot be required to provide Ancillary Services except to the extent such requirements extend to all generating facilities that are similarly situated. The provision of Network Integration Transmission Service or firm Point-to-Point Transmission Service may require additional studies and the construction of additional upgrades. Because such studies and upgrades would be associated with a request for delivery service under the Tariff, cost responsibility for the studies and upgrades would be in accordance with FERC's policy for pricing transmission delivery services. Network Resource Interconnection Service does not necessarily provide Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on Transmission Provider's Transmission System without incurring congestion costs. In the event of transmission constraints on Transmission Provider's Transmission System, Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in Transmission Provider's Transmission System in the same manner as Network Resources. There is no requirement either at the time of study or interconnection, or at any point in the future, that Interconnection Customer's Large Generating Facility be designated as a Network Resource by a Network Service Customer under the Tariff or that Interconnection Customer identify a specific buyer (or sink). To the extent a Network Customer does designate the Large Generating Facility as a Network Resource, it must do so pursuant to Transmission Provider's Tariff. Once an Interconnection Customer satisfies the requirements for obtaining Network Resource Interconnection Service, any future transmission service request for delivery from the Large Generating Facility within Transmission Provider's Transmission System of any amount of capacity and/or energy, up to the amount initially studied, will not require that any additional studies be performed or that any further upgrades associated with such Large Generating Facility be undertaken, regardless of whether or not such Large Generating Facility is ever designated by a Network Customer as a Network Resource and regardless of changes in ownership of the Large Generating Facility. However, the reduction or elimination of congestion or redispatch costs may require additional studies and the construction of additional upgrades. To the extent Interconnection Customer enters into an arrangement for long term transmission service for deliveries from the Large Generating Facility outside Transmission Provider's Transmission System, such request may require additional studies and upgrades in order for Transmission Provider to grant such request.

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.

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

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

  • Scheduled Outages (a) Commencing at least sixty (60) days before Initial Synchronization and throughout the Delivery Term, Seller shall, no later than January 1, April 1, July 1 and October 1 of each year, submit to SCE, using the Web Client, Seller’s schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty-four month period.

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