Distribution System Forced Outage Sample Clauses

Distribution System Forced Outage. In the event of a --------------------------------- Forced Outage of a system element of the Distribution System adversely affecting the Transmission System, the Local Distribution Company will use Good Utility Practice to promptly restore that system element to service.
AutoNDA by SimpleDocs

Related to Distribution System Forced Outage

  • Distribution System The Transmission Owner’s facilities and equipment used to transmit electricity to ultimate usage points such as homes and industries directly from nearby generators or from interchanges with higher voltage transmission networks which transport bulk power over longer distances. The voltage levels at which Distribution Systems operate differ among areas. Distribution Upgrades – The additions, modifications, and upgrades to the Transmission Owner’s Distribution System at or beyond the Point of Interconnection to facilitate interconnection of the Small Generating Facility and render the transmission service necessary to effect the Interconnection Customer’s wholesale sale of electricity in interstate commerce.

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

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

  • Downtime There may be downtime during the Migration. The duration of the downtime will depend on the amount of data that Agency is migrating. Axon will work with Agency to minimize any downtime. Any VIEVU mobile application will need to be disabled upon Migration.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

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

  • Distribution Services 3.1. Distributor will have the right, as agent for the Fund, to enter into dealer agreements with responsible investment dealers, and to sell Shares to such investment dealers against orders therefor at the public offering price (as defined below) stated in the Fund’s effective Registration Statement on Form N-2 under the 1940 Act and the Securities Act of 1933, as amended (the “Securities Act”), including the then-current prospectus and statement of additional information (the “Registration Statement”). Upon receipt of an order to purchase Shares from a dealer with whom Distributor has a dealer agreement, Distributor will promptly cause such order to be filled by the Fund. 3.2. Distributor will also have the right, as agent for the Fund, to sell such Shares to the public against orders therefor at the public offering price (as defined below) and in accordance with the Registration Statement. 3.3. Distributor will also have the right to take, as agent for the Fund, all actions which, in Distributor’s reasonable judgment, are necessary to carry into effect the distribution of the Shares. 3.4. The “public offering price” for the Shares of the Fund shall be the net asset value (“NAV”) of the Shares then in effect, plus any applicable sales charge determined in the manner set forth in the Registration Statement or as permitted by the 1940 Act and the rules and regulations promulgated by the SEC or other applicable regulatory agency or self-regulatory organization under the oversight of the SEC. In no event shall any applicable sales charge exceed the maximum sales charge permitted by the Rules of FINRA. 3.5. The NAV of the Shares of the Fund shall be determined in the manner provided in the Registration Statement, and when determined shall be applicable to transactions as provided for in the Registration Statement. The NAV of the Shares shall be calculated by the Fund or by another entity on behalf of the Fund. Distributor shall have no duty to inquire into or liability for the accuracy of the NAV per Share as calculated. 3.6. On every sale, the Fund shall receive the applicable NAV of the Shares promptly, but in no event later than the third business day following the date on which Distributor shall have received an order for the purchase of the Shares. 3.7. Upon receipt of purchase instructions, Distributor will transmit such instructions to the Fund or its transfer agent for the issuance and registration of the Shares purchased. 3.8. Distributor, as agent of and for the account of the Fund, may repurchase the Shares at such prices and upon such terms and conditions as shall be specified in the Registration Statement. 3.9. Distributor shall maintain membership with the National Securities Clearing Corporation (“NSCC”) and any other similar successor organization to sponsor a participant number for the Fund so as to enable the Shares to be traded through FundSERV. The Distributor shall not be responsible for any operational matters associated with FundSERV or networking transactions. 3.10. Distributor will review all proposed advertising materials and sales literature for compliance with Applicable Law and shall file such materials with appropriate regulators as required by current laws and regulations. Distributor agrees to furnish the Fund with any comments provided by regulators with respect to such materials. 3.11. Distributor shall prepare or cause to be prepared reports for the Board of Trustees (the “Board”) of the Fund regarding its activities under this Agreement as reasonably requested by the Board.

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

  • Scheduled Outages (1) No later than five (5) Business Days prior to the dates required by the ISO for delivery of schedules for planned outages (which such ISO required delivery dates are currently January 15th, April 15th, July 15th and October 15th of each calendar year during the Facility Term), and at least sixty (60) days prior to the later of: (A) Initial Synchronization, or (B) SCE becoming Seller’s Scheduling Coordinator, Seller shall submit to SCE its schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty four-month period using the Web Client. If Seller fails to submit an Outage Schedule for any period as required under this Section 3.19, then Seller shall not be permitted to schedule or have any planned outages with respect to such period. The foregoing shall not prevent Seller from modifying its Outage Schedule in cooperation with SCE and the ISO. SCE shall provide Notice to Seller in the event that the ISO changes the ISO required delivery dates for schedules for planned outages. In addition, no later than thirty (30) days prior to October 15 of each year, Seller shall submit to SCE its estimate of its planned outages for the following year. (2) Seller shall provide the following information for each proposed planned outage: (A) Start date and time; (B) End date and time; and (C) Capacity expected to be online, in MW, during the planned outage. (3) Within twenty (20) Business Days after SCE’s receipt of an Outage Schedule, SCE shall notify Seller in writing of any reasonable request for changes to the Outage Schedule, and Seller shall, consistent with Prudent Electrical Practices and as permitted by the ISO, accommodate SCE’s requests regarding the timing of any planned outage. (4) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the ISO. (5) In the event a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as soon as practicable after the condition causing the change becomes known to Seller. (6) Seller shall promptly prepare and provide to SCE upon request, using the Web Client, all reports of actual or forecasted outages that SCE may reasonably require for the purpose of enabling SCE to comply with Section 761.3 of the California Public Utilities Code or any Applicable Law mandating the reporting by investor owned utilities of expected or experienced outages by electric energy generating facilities under contract to supply electric energy.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!