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.
Scheduled Downtime For the purposes of this Agreement, Scheduled Downtime will mean those hours, as determined by us but which will not occur between the hours of 9:00 AM and 5:00 PM Eastern Time, Monday through Friday without your authorization or unless exigent circumstances exist, during which time we will perform scheduled maintenance or adjustments to the Environment. We will use our best efforts to provide you with at least twenty-four (24) hours of notice prior to scheduling Scheduled Downtime.
Shared Transport The Shared Transport Network Element (“Shared Transport”) provides the collective interoffice transmission facilities shared by various Carriers (including Qwest) between end-office switches and between end-office switches and local tandem switches within the Local Calling Area. Shared Transport uses the existing routing tables resident in Qwest switches to carry the End User Customer’s originating and terminating local/extended area service interoffice Local traffic on the Qwest interoffice message trunk network. CLEC traffic will be carried on the same transmission facilities between end- office switches, between end-office switches and tandem switches and between tandem switches on the same network facilities that Qwest uses for its own traffic. Shared Transport does not include use of tandem switches or transport between tandem switches and end-office switches for Local Calls that originate from end users served by non- Qwest Telecommunications Carriers (“Carrier(s)”) which terminate to QLSP End Users.
Unscheduled Maintenance Unscheduled maintenance may be required to resolve issues that are critical for Customer and/or performance of the Cloud Services. Druva will use its commercially reasonable efforts to notify Customer at least six (6) hours prior to the unscheduled maintenance.
Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,
Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
Switching All of the negotiated rates, terms and conditions set forth in this Section pertain to the provision of local and tandem switching.
Unbundled Digital Loops 2.3.1 BellSouth will offer Unbundled Digital Loops (UDL). UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service. 2.3.2 BellSouth shall make available the following UDLs, subject to restrictions set forth herein:
Points of Interconnection and Trunk Types 2.1 Point(s) of Interconnection. 2.1.1 Each Party, at its own expense, shall provide transport facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA selected by PNG.
