Train Service Description Clause Samples

The Train Service Description clause defines the specific details and characteristics of the train services to be provided under the agreement. It typically outlines aspects such as routes, schedules, frequency, types of trains, and service standards that the operator must meet. By clearly specifying these operational parameters, the clause ensures both parties have a mutual understanding of service expectations, reducing the risk of disputes and providing a benchmark for performance assessment.
Train Service Description for a Train Service Type means the description of, specifications for, and constraints on, the Access Rights for that Train Service Type specified in schedule 2.
Train Service Description. If the Parties and the End User are unable to agree to such variations then the existing Performance Levels shall continue to apply unless varied by QR Network in accordance with the provisions of Clause 6.6(e).
Train Service Description. [Bracketed text is only included where Operator pays non-TOP Access Charges]
Train Service Description 

Related to Train Service Description

  • Service Description 2.1 General

  • Service Descriptions 2.4.1 The switch’s LRN software determines if the called party is in a portable NXX. If the called party is in a portable NXX, a query is launched to the LNP database to determine whether or not the called number is ported. 2.4.2 When the called number with a portable NXX is ported, an LRN is returned to the switch that launched the query. Per industry standards, the LRN appears in the Called Party Number (CdPN) field of the SS7 message and the called number then appears in the GAP (Generic Address Parameter) field. 2.4.3 When the called number with a portable NXX is not ported, the call is completed as in the pre-LNP environment. 2.4.4 The Forward Call Identifier (FCI) field entry is changed from 0 to 1 by the switch triggering the query when a query is made, regardless of whether the called number is ported or not. 2.4.5 The WSP shall populate the Jurisdictional Identification Parameter (JIP) field with the first six (6) digits (NPA NXX format) of the appropriate LRN of the originating switch.

  • System Description The wet detention basin is designed to trap 80% of sediment in runoff and maintain pre-development downstream peak flows. The basin has two forebays (smaller ponds) located at the low end of two grass ▇▇▇▇▇▇. In addition to runoff conveyance, the grass ▇▇▇▇▇▇ also allow infiltration and filtering of pollutants, especially from smaller storms. The forebays are each 4 feet deep. They are connected to the main pool by 18 and 24-inch metal pipes that outlet onto a rock chute. The forebays will trap coarse sediments in runoff, such as road sands, thus reducing maintenance of the main basin. The main pool will trap the finer suspended sediment. To do this, the pond size, water level and outlet structures must be maintained as specified in this Agreement (see Figures 1, 2 and 3). The main basin receives runoff from a 67.1 acre drainage area (41.2 acres within the subdivision and 25.9 acres off- site drainage coming from the east). During high rainfall or snow melt events, the water level will temporarily rise and slowly drain down to the elevation of the control structure. The water level is controlled by a 12-inch concrete pipe extending through the berm in the northwest corner of the basin (see Figures 1 and 3). On the face of the 12- inch pipe, there is metal plate with a 3-inch drilled hole (orifice) with stone in front of it. This orifice controls the water level and causes the pond to temporarily rise during runoff events. Washed stone (1-2” diameter) is placed in front of the orifice to prevent clogging. High flows may enter the grated concrete riser or flow over the rock lined emergency spillway. “As-built” construction drawings of the basin, showing actual dimensions, elevations, outlet structures, etc. will be recorded as an addendum(s) to this agreement within 60 days after Waukesha County accepts verification of construction from the project engineer.