Vehicle Traffic Control Sample Clauses

Vehicle Traffic Control. The Developer shall always provide a current Traffic Control Plan (“Traffic Plan”) to the Town Engineer. a. The Traffic Plan shall be submitted to the Town Engineer for approval a minimum of 72 hours prior to implementation of the Traffic Plan or changes to the Traffic Plan. The Town Engineer will provide written approval by email of the Traffic Plan or revised Traffic Plan, or request changes to the Traffic Plan prior to approving the Traffic Plan for implementation. b. All traffic control flaggers shall always be professionally certified and under the supervision of a registered Traffic Control Supervisor (TCS). c. The installation and implementation of traffic control devices shall be in conformance with the Manual of Uniform Traffic Control Devices (MUTCD), latest edition thereof. Traffic control devices and their location in the Right of way shall be approved by the Town Engineer. d. The Developer shall implement the current Traffic Plan approved by the Town Engineer and provide construction flaggers as require by the Traffic Plan. In general, a flagger is required anytime traffic stops or blocks W. Anemone Trail or Little Dam Street traffic due to construction activity, or whenever a truck must back into the construction site. Flagging locations shall be part of the Traffic Plan and shall be approved by the Town Engineer.
AutoNDA by SimpleDocs
Vehicle Traffic Control. The Developer shall maintain two lanes of traffic on Dillon Ridge Road and Little Beaver Trail at all times during construction, unless a short-term detour is specifically approved by the Town Engineer for a specific right-of-way construction task.

Related to Vehicle Traffic Control

  • Traffic Control The Surveyor shall control traffic in and near surveying operations adequately to comply with provisions of the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI which can be found on the State’s internet site. In the event field crew personnel must divert traffic or close traveled lanes, a Traffic Control Plan based upon principles outlined in the latest edition of the Texas Manual on Uniform Traffic Control Devices – Part VI shall be prepared by the Surveyor and approved by the State prior to commencement of field work. A copy of the approved plan shall be in the possession of field crew personnel on the job site at all times and shall be made available to the State’s personnel for inspection upon request.

  • Input Control The possibility to subsequently verify and determine whether, and by whom, personal data was entered into, changed or removed from data processing systems must be ensured. • Definition of entry authorisation • Logging of logins

  • Data Input Control It will be possible to retrospectively examine and establish whether and by whom Personal Data have been entered, modified or removed from SAP data processing systems.

  • Job Control Personal Data being processed on commission (i.e., Personal Data processed on a customer’s behalf) is processed solely in accordance with the Agreement and related instructions of the customer.

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • 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.

  • Export Control This Agreement is made subject to any restrictions concerning the export of products or technical information from the United States or other countries that may be imposed on the Parties from time to time. Each Party agrees that it will not export, directly or indirectly, any technical information acquired from the other Party under this Agreement or any products using such technical information to a location or in a manner that at the time of export requires an export license or other governmental approval, without first obtaining the written consent to do so from the appropriate agency or other governmental entity in accordance with Applicable Law.

  • Compliance Control Services (1) Support reporting to regulatory bodies and support financial statement preparation by making the Fund's accounting records available to the Trust, the Securities and Exchange Commission (the “SEC”), and the independent accountants. (2) Maintain accounting records according to the 1940 Act and regulations provided thereunder. (3) Perform its duties hereunder in compliance with all applicable laws and regulations and provide any sub-certifications reasonably requested by the Trust in connection with any certification required of the Trust pursuant to the Xxxxxxxx-Xxxxx Act of 2002 (the “SOX Act”) or any rules or regulations promulgated by the SEC thereunder, provided the same shall not be deemed to change USBFS’s standard of care as set forth herein. (4) Cooperate with the Trust’s independent accountants and take all reasonable action in the performance of its obligations under this Agreement to ensure that the necessary information is made available to such accountants for the expression of their opinion on the Fund’s financial statements without any qualification as to the scope of their examination.

  • Export Control Compliance User acknowledges that Center is an open laboratory for fundamental research that has many foreign persons as its employees and students. User understands and agrees that under no circumstances will User bring export control-listed items, or unpublished software source code or technical information in the form of defense articles or technical data regulated by the International Traffic in Arms Regulations (ITAR), to Center. Use of Center or facilities for activity subject to the ITAR, including the development, assembly or fabrication of defense articles identified on the US Munitions List, is prohibited.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!