Type of Pavement Sample Clauses

Type of Pavement. Main carriageway including loops & ramps, raising of existing road, bypasses, realignment, reconstruction, Truck Lay Byes, Rest Areas, Bus Bays, Service Road, Slip Road sections are proposed to be constructed with flexible pavement with Cement Treated Base (CTB) and Cement Treated Sub-base (CTSB). However, the design is in the scope of EPC Contractor who may propose any other alternate design which shall conform to the specification and standards and any modification shall not qualify for Change of Scope (CoS).
Type of Pavement. Type of pavement shall be provided as per Section 5 of the Manual. However, in the sections given in Table B-3 the type of pavement shall be as specified therein.
Type of Pavement. Flexible pavement shall be adopted for Project Highway. The pavement shall be designed as given below.
Type of Pavement. Type of pavement shall be flexible pavements, except for the sections given in Appendix B-VI, wherein the type of pavement shall be as specified therein. Further the pavement type at all Toll Plazas including tapering zone shall be rigid.
Type of Pavement. Proposed pavement shall be flexible pavement of bituminous type.

Related to Type of Pavement

  • Number Resources, Rate Center Areas and Routing Points 13.1 Nothing in this Agreement shall be construed to limit or otherwise adversely affect in any manner either Party’s right to employ or to request and be assigned any Central Office Codes (“NXX”) pursuant to the Central Office Code Assignment Guidelines and any relevant FCC or Commission orders, as may be amended from time to time, or to establish, by Tariff or otherwise, Rate Center Areas and Routing Points corresponding to such NXX codes. 13.2 It shall be the responsibility of each Party to program and update its own switches and network systems pursuant to information provided on ASRs as well as the LERG in order to recognize and route traffic to the other Party’s assigned NXX codes. Except as expressly set forth in this Agreement, neither Party shall impose any fees or charges whatsoever on the other Party for such activities. 13.3 Unless otherwise required by Commission order, the Rate Center Areas will be the same for each Party. During the term of this Agreement, Onvoy shall adopt the Rate Center Area and Rate Center Points that the Commission has approved for Frontier within the LATA and Tandem serving area. Onvoy shall assign whole NPA-NXX codes to each Rate Center Area unless otherwise ordered by the FCC, the Commission or another governmental entity of appropriate jurisdiction, or the LEC industry adopts alternative methods of utilizing NXXs. 13.4 Onvoy will also designate a Routing Point for each assigned NXX code. Onvoy shall designate one location for each Rate Center Area in which the Onvoy has established NXX code(s) as the Routing Point for the NPA-NXXs associated with that Rate Center Area, and such Routing Point shall be within the same LATA as the Rate Center Area but not necessarily within the Rate Center Area itself. Unless specified otherwise, calls to subsequent NXXs of Onvoy will be routed in the same manner as calls to ▇▇▇▇▇’s initial NXXs. 13.5 Notwithstanding anything to the contrary contained herein, nothing in this Agreement is intended, and nothing in this Agreement shall be construed, to in any way constrain Onvoy’s choices regarding the size of the local calling area(s) that Onvoy may establish for its Customers, which local calling areas may be larger than, smaller than, or identical to Frontier’s local calling areas.

  • Volunteer Firefighting Leave Leave without pay will be granted when an employee who is a volunteer firefighter is called to duty to respond to a fire, natural disaster or medical emergency.

  • Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)

  • SPECIALIZED JOB CLASSES Where there is a particular specialized job class in which the pay rate is below the local market value assessment of that job class, the parties may use existing means under the collective agreement to adjust compensation for that job class.

  • Registry-­‐Level Fees (a) Registry Operator shall pay ICANN a registry-­‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-­‐level transaction fee (collectively, the “Registry-­‐Level Fees”). The registry-­‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-­‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-­‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-­‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-­‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls. (b) Subject to Section 6.1(a), Registry Operator shall pay the Registry-­‐Level Fees on a quarterly basis to an account designated by ICANN within thirty (30) calendar days following the date of the invoice provided by ICANN.