Testing and Traffic Control Compliance Requirements Sample Clauses

Testing and Traffic Control Compliance Requirements. To demonstrate compliance, a program of testing at the individual component, sub-system, and system level is required, as described herein. The tests are separated into, Level A, Level B, and Level C testing. Ensure all test procedures and equipment is furnished and maintained by the contractor and coordinated with the manufacturer. Coordinate through the manufacturer to obtain certified tests and fulfill the requirements of this specification. Ensure all testing occurs overnight within the specified road closure restrictions of each site. Ensure all testing involving vehicles (provided by the Contractor) traveling the wrong way on the roadway is conducted with New Jersey State Police officers (provided by the Contractor) present at all times. All traffic control set up and take down is the responsibility of the contractor and will follow applicable New Jersey Department of Transportation Traffic Control Details (Index 100). Submit a traffic control plan to the Department fourteen
Sample 1
AutoNDA by SimpleDocs

Related to Testing and Traffic Control Compliance Requirements

  • CONTRACT COMPLIANCE REQUIREMENT The HUB requirement on this Contract is 0%. The student engagement requirement of this Contract is 0 hours. The Career Education requirement for this Contract is 0 hours. Failure to achieve these requirements may result in the application of some or all of the sanctions set forth in Administrative Policy 3.10, which is hereby incorporated by reference.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Compliance Requirements K. If using volunteers as provided for in this Contract during FY19, which encompasses the Contract term of July 1, 2019 to June 30, 2020, then the Grantee must either:

  • DRUG-FREE WORKPLACE REQUIREMENTS Contractor will comply with the requirements of the Drug-Free Workplace Act of 1990 and will provide a drug-free workplace by taking the following actions:

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • Interface Requirements 9.3.1 BellSouth shall offer LIDB in accordance with the requirements of this subsection.

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

  • E-Verify Compliance The contractor represents and covenants that the contractor and its subcontractors comply with the requirements of Article 2 of Chapter 64 of the North Carolina General Statutes (NCGS). In this E-Verify Compliance section, "contractor," "its subcontractors," and "comply" shall have the meanings intended by NCGS 160A-20.1(b). The City is relying on this section in entering into this contract. The parties agree to this section only to the extent authorized by law. If this section is held to be unenforceable or invalid in whole or in part, it shall be deemed amended to the extent necessary to make this contract comply with NCGS 160A-20.1(b).

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

Time is Money Join Law Insider Premium to draft better contracts faster.