Extra Trips All trips other than regular runs or supplemental runs shall be awarded to drivers according to the following procedures: 9.7.1 All extra trips shall be assigned in compliance with the following section of this Agreement; provided, however, that no driver shall be eligible to work more than forty (40) hours in any workweek, exclusive of hours worked on Saturday or Sunday, when another eligible driver is available and would not be put into overtime. 9.7.2 Assignment of extra trips shall be made on the basis of a “Trip Board.” The most senior driver who signs up for the extra trip shall be awarded the trip. No driver may give up any extra trip or supplemental run or regular run previously awarded in order to take an extra trip, if Section 9.7.1 above would be violated. There shall be no pre-empting of regular runs by drivers who wish to take extra trips. 9.7.3 Trips are to be dated as they are received by the Transportation Office. All extra trips shall be awarded to the most senior appropriate driver signing the “Trip Board.” If the extra trip is posted before a driver’s regular run clock-out time, the driver has until the driver’s next regular run clock-in time to reply. If there is no reply, the dispatcher shall assign the extra trip to the next senior driver on the sign-up sheet. 9.7.4 Drivers shall not be eligible for extra trips during periods of absence due to illness. Drivers absent for personal illness on the last working day before a Saturday, Sunday, or holiday trip shall not be eligible to drive such trip and will lose his/her turn on the list until the process begins anew. Drivers absent for other reasons will be able to drive such trips provided they contact the Transportation Office by 3:30 p.m. on the last working day prior to the scheduled trip to verify their availability and confirm the start time of the trip. 9.7.5 The dispatch book shall be made available for driver viewing by the Transportation Office.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom 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 Freedom. 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 Freedom (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 Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.
Initiating Interconnection 4.1 If ENT determines to offer Telephone Exchange Services and to interconnect with Verizon in any LATA in which Verizon also offers Telephone Exchange Services and in which the Parties are not already interconnected pursuant to this Agreement, ENT shall provide written notice to Verizon of the need to establish Interconnection in such LATA pursuant to this Agreement. 4.2 The notice provided in Section 4.1 of this Attachment shall include (a) the initial Routing Point(s); (b) the applicable technically feasible Point(s) of Interconnection on Verizon’s network to be established in the relevant LATA in accordance with this Agreement; (c) ENT’s intended Interconnection activation date; (d) a forecast of ENT’s trunking requirements conforming to Section 14.2 of this Attachment; and (e) such other information as Verizon shall reasonably request in order to facilitate Interconnection. 4.3 The interconnection activation date in the new LATA shall be mutually agreed to by the Parties after receipt by Verizon of all necessary information as indicated above. Within ten (10) Business Days of Verizon’s receipt of ENT’s notice provided for in Section 4.1of this Attachment, Verizon and ENT shall confirm the technically feasible Point of Interconnection on Verizon’s network in the new LATA and the mutually agreed upon Interconnection activation date for the new LATA.
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.
Maintenance Period During the Maintenance Period the Developer shall at its own expense maintain repair and otherwise keep the Works in good working order and repair to the reasonable satisfaction of ▇▇▇ ▇▇▇▇▇▇▇▇▇▇ unless ▇▇▇ ▇▇▇▇▇▇▇▇▇▇ shall declare that any required maintenance and/or repair is an emergency in which case the Developer shall carry out the said maintenance and/or repair immediately