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 LOOPS Sample Clauses

TRAFFIC LOOPS. 1. Traffic Loops removed during the resurfacing shall be replaced and operational within 4 days of applying final surface course.
TRAFFIC LOOPS. A. Traffic loop detector sensor units shall be furnished by the Contractor. B. The third paragraph in Section 86-5.01A(4), "Construction Materials," of the CALTRANS Standard Specifications is amended to read: C. Loop detector lead-in cable, from the pull box adjacent to the loop to the field terminals in the cabinet, shall conform to the DC resistance (ohms per 1,000 feet) specifications of ASTM Designation: B 286, or shall conform to the calculated cross sectional area in circular mils of ASTM Designation: B 286, Table 1. The lead-in cable shall conform to the following: D. Type A lead-in cable shall consist of 2 No. 12 solid copper conductors with each conductor insulated with 30 mils minimum, at any point, high molecular weight, heat- stabilized, colored polyethylene, conforming to the requirements of ASTM Designation: D1248, Type I, Class B, Grade 4. The conductors shall be twisted together with not less than 2 turns per foot; Non-Hygroscopic fillers shall be used to form a firm compact cylindrical core. A non-hygroscopic core tape shall be applied spirally over the core. The cable shall be provided with an outer jacket consisting of extruded, black polyvinyl chloride conforming to ASTM Designation: D1047. The cable shall conform to the International Municipal Signal Association's Specifications: 19 E. In lieu of the requirements in the fourth paragraph of Section 86-5.01A(5), "Installation Details," of the CALTRANS Standard Specifications, slots in asphalt concrete pavement shall be filled as follows: F. After conductors are installed in the slots cut in the pavement, paint binder shall be applied to all vertical surfaces of slots in accordance with the provisions in Section 94, "Asphaltic Emulsions," of the CALTRANS Standard Specifications. The slots shall then be filled with asphaltic concrete sealant. G. Temperature of sealant material during installation shall be above 70 degrees Fahrenheit. Air temperature during installation shall be above 50 degrees Fahrenheit. Sealant placed in the slots shall be compacted by use of an 8-inch diameter by 1/8 inch thick steel hand roller or other tool approved by the Engineer. Compacted sealant shall be flushed with the pavement surface. Minimum conductor coverage shall be 5/8 inch. Excess sealant remaining after rolling shall not be re-used. Traffic may be released immediately over impacted materials. H. Full compensation for conforming to requirements of “Traffic Loop” will be considered as included in the Co...
TRAFFIC LOOPSTraffic loop detector sensor units shall be furnished by the Contractor.
TRAFFIC LOOPS. 1. Traffic Loops removed during the resurfacing shall be replaced and operational within 5 days of applying final surface course. Failure to have replacement traffic loops operational within the time specified will result in the assessment of Liquidated Damages as specified in Special Provision 108.08.
TRAFFIC LOOPS. Traffic Loops removed during resurfacing shall be replaced and operational within five (5) days of the intersection being complete.
TRAFFIC LOOPS. Traffic Loops removed during the resurfacing shall be repl aced and operational within forty-eight (48) hours. Failure in having replacement traffic loops operational within the xxx e specified will result in the assessm ent of penalties as specified in Special Provision 108.08.

Related to TRAFFIC LOOPS

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

  • Traffic The provisions in this Section apply regardless how the ISP-bound traffic is determined.

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

  • Internet Traffic Any traffic that is transmitted to or returned from the Internet at any point during the duration of the transmission.

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

  • Human Trafficking BY ACCEPTANCE OF CONTRACT, CONTRACTOR ACKNOWLEDGES THAT FORT BEND COUNTY IS OPPOSED TO HUMAN TRAFFICKING AND THAT NO COUNTY FUNDS WILL BE USED IN SUPPORT OF SERVICES OR ACTIVITIES THAT VIOLATE HUMAN TRAFFICKING LAWS.

  • TRAFFIC INFRACTIONS The State will not be liable for any expense incurred by the Contractor for any parking fees or as a consequence of any traffic infraction or parking violations attributable to employees of the Contractor.

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

  • Human Trafficking Prohibition Pursuant to Section 2155.0061 of the Texas Government Code, Contractor certifies that it is not ineligible to receive this Contract and acknowledges that this Contract may be terminated and payment withheld if Contractor’s certification in this matter is inaccurate. TFC may not award a contract, including a contract for which purchasing authority is delegated to a state agency, that includes proposed financial participation by a person who, during the five-year (5) period preceding the date of the award, has been convicted of any offense related to the direct support or promotion of human trafficking.

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