Forced Outage Communication Sample Clauses

Forced Outage Communication. If an unanticipated Unplanned Outage occurs, the Owner shall call the O&R Scheduling Desk no later than fifteen (15) minutes after the Project is offline and provide the best available information reporting the cause and the expected duration of the unplanned outage. As soon as reasonably practicable, the Owner will follow up with an email communication notifying O&R of Project condition, date and time of event, approximate return time, products available, and any other pertinent information. The Scheduling Desk will inform the NYISO of the assets change in status.
Sample 1See All (4)
AutoNDA by SimpleDocs
Forced Outage Communication. If an unanticipated Unplanned Outage occurs, the Owner shall call the CHGE Scheduling Desk no later than fifteen (15) minutes after the Project is offline and provide the best available information reporting the cause and the expected duration of the unplanned outage. As soon as reasonably practicable, the Owner will follow up with a secured email communication notifying CHGE of Project condition, date and time of event, approximate return time, products available, and any other pertinent information. The CHGE Scheduling Desk will inform the NYISO of the assets change in status.
Sample 1Sample 2
Forced Outage Communication. If an unanticipated Unplanned Outage occurs, Owner shall call the CECONY Scheduling Desk no later than fifteen (15) minutes after the Project is offline and provide the best available information reporting the cause and the expected duration of the unplanned outage. As soon as reasonably practicable, Owner will follow up with an email communication notifying CECONY of Project condition, date and time of event, approximate return time, products available, and any other pertinent information. The Scheduling Desk will inform the NYISO of the assets change in status.
Sample 1
Forced Outage Communication. If an unanticipated Unplanned Outage occurs, the Owner shall call the NYSEG Scheduling Desk no later than fifteen (15) minutes after the Project is offline and provide the best available information reporting the cause and the expected duration of the unplanned outage. As soon as reasonably practicable, the Owner will follow up with a secured email communication notifying NYSEG of Project condition, date and time of event, approximate return time, products available, and any other pertinent information. The NYSEG Scheduling Desk will inform the NYISO of the assets change in status. Return to Service Communications: Expected return from a forced or planned extended outage, shall be communicated to NYSEG via secured email as soon as possible but no later than 10:00 am EPT on the second Calendar Day prior to the Operating Day in order to receive a Dispatch Notice for the Operating Day. If returning to service on the same Operating Day as the forced outage the Owner shall notify NYSEG as soon as reasonably possible via a telephone communication no later than two (2) hours prior to the top of the hour that the Project is expected to return to service.
Sample 1
Forced Outage Communication. If an unanticipated Unplanned Outage occurs, the Owner shall call the NYSEG Scheduling Desk no later than fifteen (15) minutes after the Project is offline and provide the best available information reporting the cause and the expected duration of the unplanned outage. As soon as reasonably practicable, the Owner will follow up with an email communication notifying NYSEG of Project condition, date and time of event, approximate return time, products available, and any other pertinent information. The Scheduling Desk will inform the NYISO of the assets change in status.
Sample 1
Forced Outage Communication. If an unanticipated Unplanned Outage occurs, the Owner shall call the RG&E Scheduling Desk no later than fifteen (15) minutes after the Project is offline and provide the best available information reporting the cause and the expected duration of the unplanned outage. As soon as reasonably practicable, the Owner will follow up with a secured email communication notifying RG&E of Project condition, date and time of event, approximate return time, products available, and any other pertinent information. The RG&E Scheduling Desk will inform the NYISO of the assets change in status. Return to Service Communications: Expected return from a forced or planned extended outage, shall be communicated to RG&E via secured email as soon as possible but no later than 10:00 am EPT on the second Calendar Day prior to the Operating Day in order to receive a Dispatch Notice for the Operating Day. If returning to service on the same Operating Day as the forced outage the Owner shall notify RG&E as soon as reasonably possible via a telephone communication no later than two (2) hours prior to the top of the hour that the Project is expected to return to service.
Sample 1

Related to Forced Outage Communication

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

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

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

  • BELLSOUTH OUTAGE Because BellSouth's equipment has varying degrees of impact on the service provided to the CLECs, restoring service from damaged BellSouth equipment is different. The outage will probably impact a number of Carriers simultaneously. However, the ECC will be able to initiate immediate actions to correct the problem. A disaster involving any of BellSouth's equipment locations could impact the CLECs, some more than others. A disaster at a Central Office (CO) would only impact the delivery of traffic to and from that one location, but the incident could affect many Carriers. If the Central Office is a Serving Wire Center (SWC), then traffic from the entire area to those Carriers served from that switch would also be impacted. If the switch functions as an Access Tandem, or there is a tandem in the building, traffic from every CO to every CLEC could be interrupted. A disaster that destroys a facility hub could disrupt various traffic flows, even though the switching equipment may be unaffected. The NMC would be the first group to observe a problem involving BellSouth's equipment. Shortly after a disaster, the NMC will begin applying controls and finding re-routes for the completion of as much traffic as possible. These reroutes may involve delivering traffic to alternate Carriers upon receiving approval from the CLECs involved. In some cases, changes in translations will be required. If the outage is caused by the destruction of equipment, then the ECC will assume control of the restoration.

  • Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

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

  • Manual Disconnect Switch 5.1 U.L.1741 Listed, inverter-based Tier 1 customer-owned renewable generation systems do not require a customer-installed manual disconnect switch.

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

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

  • Interconnection Customer Provided Services The services provided by Interconnection Customer under this LGIA are set forth in Article 9.6 and Article 13.5.1. Interconnection Customer shall be paid for such services in accordance with Article 11.6.

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