We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Traffic Movements Sample Clauses

Traffic Movements. The arterial characteristics inherent in the Project require uniformity in information and regulations to the end that traffic may be safely and expeditiously served. The City shall adopt and enforce rules and regulations governing traffic movements as may be deemed necessary or desirable by the Secretary and the FHWA.
Traffic MovementsSubject to any temporary closures pursuant to applicable legislation, following commencement of the operation of the Opening Day Plan, Alberta will provide all of the traffic movements listed in Schedule 8.

Related to Traffic Movements

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Traffic Management 6.5.1 Developer shall be responsible for the management of traffic on (a) Phase 1 from NTP2 through the end of the Term, and (b) Phase 2 from issuance of NTP3 until Substantial Completion of Phase 2. 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 6.5.2 Developer shall prepare and submit to TxDOT for its approval a Traffic Management Plan, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) from NTP3 through the date of Project Final Acceptance, orderly and safe movement and diversion of traffic on Phase 2, (c) throughout the Term, orderly and safe movement and diversion of traffic on Phase 1, and (d) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with Renewal Work or with field maintenance and repair work 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 concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 6.5.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 by Developer and during the Utility Adjustment Work. 6.5.4 TxDOT shall have at all times, without obligation or liability to Developer, the right to (a) issue Directive Letters to Developer regarding traffic management and control (with which Developer shall comply), or directly assume traffic management and control, of the Project during any period that the Executive Director determines such action will be in the public interest as a result of an emergency or natural disaster; and (b) provide on the Project, via message signs or other means consistent with Good Industry Practice, traveler and driver information, and other public information (e.g., amber alerts).

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.