Rail Corridor Crossing
Rail Corridor Crossing Sample Clauses
Related to Rail Corridor Crossing
Drainage Systems (1) Clear culvert inlets, outlets, and sediment catching basins. (2) Maintain waterbars, drainage dips, and other water diversion measures. (3) During active use, patrol and maintain functional drainage. (4) Repair damaged culvert ends.
Pipelines Developer shall have no interest in the pipeline gathering system, which gathering system shall remain the sole property of Operator or its Affiliates and shall be maintained at their sole cost and expense.
Environmental Services 1. Preparation of Environmental Documentation (CEQA/NEPA) including but not limited to the following: a. Initial Study b. Categorical Exemption (CE) c. Notice of Exemption (XXX) d. Negative Declaration (ND) e. Mitigated Negative Declaration (MND) f. Notice of Preparation (NOP) g. Environmental Impact Report (EIR) i. Initial Document (Screen Check/Administrative Draft) ii. Addendum iii. Supplemental
Loop A transmission path that extends from a Main Distribution Frame or functionally comparable piece of equipment in a Customer's serving End Office, to the Rate Demarcation Point (or NID if installed at the Rate Demarcation Point) in or at the Customer's premises. The actual transmission facilities used to provide a Loop may utilize any of several technologies.
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.
ELECTRICAL SERVICES The Company must construct and reticulate electrical requirements for all amenities and facilities. The Company must construct sub-station and distribution boards necessary to reticulate power to all Company owned or leased facilities which provide amenities to the public. The electrical installation must be to the design and installation standards of the State Energy Commission of Western Australia. All electrical reticulation must be placed underground.
Two-Way Interconnection Trunks 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PCS, PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Prior to ordering any Two-Way Interconnection Trunks from Verizon, PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three
Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.
Logistics The Client shall arrange their own transportation and accommodation, unless Client and Performer agree otherwise. If requested, the Performer shall arrange transport within Ostrava, and provide accommodation in a hotel.
Electric Storage Resources Developer interconnecting an electric storage resource shall establish an operating range in Appendix C of its LGIA that specifies a minimum state of charge and a maximum state of charge between which the electric storage resource will be required to provide primary frequency response consistent with the conditions set forth in Articles 9.5.5, 9.5.5.1, 9.5.5.2, and 9.5.5.3 of this Agreement. Appendix C shall specify whether the operating range is static or dynamic, and shall consider (1) the expected magnitude of frequency deviations in the interconnection; (2) the expected duration that system frequency will remain outside of the deadband parameter in the interconnection; (3) the expected incidence of frequency deviations outside of the deadband parameter in the interconnection; (4) the physical capabilities of the electric storage resource; (5) operational limitations of the electric storage resources due to manufacturer specification; and (6) any other relevant factors agreed to by the NYISO, Connecting Transmission Owner, and Developer. If the operating range is dynamic, then Appendix C must establish how frequently the operating range will be reevaluated and the factors that may be considered during its reevaluation. Developer’s electric storage resource is required to provide timely and sustained primary frequency response consistent with Article 9.5.5.2 of this Agreement when it is online and dispatched to inject electricity to the New York State Transmission System and/or receive electricity from the New York State Transmission System. This excludes circumstances when the electric storage resource is not dispatched to inject electricity to the New York State Transmission System and/or dispatched to receive electricity from the New York State Transmission System. If Developer’s electric storage resource is charging at the time of a frequency deviation outside of its deadband parameter, it is to increase (for over-frequency deviations) or decrease (for under-frequency deviations) the rate at which it is charging in accordance with its droop parameter. Developer’s electric storage resource is not required to change from charging to discharging, or vice versa, unless the response necessitated by the droop and deadband settings requires it to do so and it is technically capable of making such a transition.
