Traffic surveillance system integration on an active highway is not just a matter of installing cameras and detection equipment. It also depends on coordinating communications infrastructure, electrical work, traffic-control stages and adjacent construction activities. The Illinois Department of Transportation’s 2018 contract for westbound I-90 between Cumberland Avenue and Harlem Avenue offers a useful example of how these elements can be brought together in a major roadway project.
The Cook County project combined roadway reconstruction, widening and resurfacing with drainage, lighting, retaining walls, signing and pavement markings. Its plans also included a substantial intelligent transportation systems (ITS) scope: traffic surveillance equipment, fiber-optic infrastructure, vehicle detection, cabinets, cameras and an advanced traffic management system integration item. The contract context highlights a practical lesson for engineers and project leaders: ITS work has to be planned as part of the construction sequence, not treated as a separate technology package.
Traffic surveillance system integration within roadway construction
The contract’s ITS-related work covered several connected parts of a roadway monitoring system. Listed items included closed-circuit television (CCTV) cameras, a radar vehicle detection system, digital loop detector sensor units, induction loops, communications vaults, handholes, equipment cabinets, Ethernet switches and fiber-optic cable and termination panels. The contents also identify fiber-optic fusion splicing and ATMS system integration.
These items serve different roles in a surveillance and traffic-management architecture. Cameras provide video monitoring, while radar and loop-based equipment detect vehicles. Fiber, switches, termination panels and related pathways support communications between field equipment and the broader system. Cabinets and foundations provide locations for equipment and its installation. The contract lists these work elements but does not, in the material provided, define a complete system architecture or explain how each device communicates with a central platform.
That distinction matters during project planning. A list of equipment is not, by itself, an integration plan. Teams still need to coordinate where devices and pathways will be installed, how they relate to other roadway work, and when systems can be modified or connected without disrupting traffic or neighboring projects.
Coordinate ITS work with construction staging
The project took place on westbound I-90 over an approximately 2.3-mile corridor in Chicago. The work area included multiple types of construction, and the contract identified overlapping or adjacent projects, including eastbound I-90 reconstruction and work at the I-190/I-90 Cumberland interchange. It called for the contractor to coordinate with other contractors on work sequencing and timing, with critical interfaces including maintenance of traffic and, where applicable, overhead sign panel placement and coordination with the Chicago Transit Authority.
For an ITS installation, these interfaces can shape when crews have access to locations and how installation activities fit around roadway changes. Civil work may affect the areas needed for foundations, underground raceways or drainage. Electrical and communications tasks need to be aligned with the construction sequence. Equipment installation and integration also need to account for traffic-control stages and access restrictions.
The contract required affected work items to be identified as separate line items in the contractor’s proposed construction progress schedule and coordinated through the Engineer. It also stated that additional compensation or contract time would not be allowed for delays caused by a lack of required coordination. This places a clear responsibility on project teams to surface dependencies early rather than relying on informal coordination once field work is underway.
Traffic management is a system-level requirement
The contract emphasizes maintaining safe travel through the construction zone and minimizing lane and road closures. It required the contractor to coordinate traffic-management changes with the Illinois Tollway, including submitting a proposed deviation plan 21 days before a change and attending a review meeting two days before implementation. These provisions show how traffic-control decisions are tied to the delivery of a highway project.
Surveillance and detection work must be considered in that operating context. Construction staging affects where equipment can be accessed and when field changes can be made. Conversely, the availability and maintenance of traffic surveillance equipment can matter to the agencies responsible for observing and managing the roadway. The contract’s contents also identify maintenance of existing traffic surveillance as a separate work area, reinforcing that ongoing operations and new construction have to be addressed together.
For project teams, a useful coordination checklist includes:
- Map interfaces: Identify where surveillance, detection, communications, electrical, drainage and roadway work intersect.
- Schedule dependencies: Show ITS-related activities as distinct tasks and align them with traffic-control stages and access requirements.
- Coordinate changes: Follow the applicable agency review and notice process before implementing revised traffic patterns.
- Plan for existing assets: Account for work on operating surveillance equipment as well as installation of new components.
- Clarify responsibilities: Establish which contractor or party is responsible for shared access areas, work sequencing and restoration.
Design and integration considerations for project teams
The contract’s named components point to several areas that engineers and integrators should verify during detailed planning. Fiber-optic cable, innerduct, termination panels and fusion splicing need to be coordinated as parts of the communications pathway. Cabinets, handholes and vaults need to align with the planned field installation. Cameras and detection equipment need to be considered alongside foundations, power and roadway work. The listed ATMS integration item signals that bringing field equipment into the wider traffic-management environment is part of the project scope.
However, the contract excerpt does not provide enough detail to infer specific network topology, protocols, bandwidth, camera performance, detector configuration or acceptance criteria. Those requirements must be taken from the applicable plans, specifications and approved submittals. Keeping this boundary clear helps teams avoid treating a general scope list as a substitute for project-specific design documentation.
Practical implications
The I-90 contract demonstrates that traffic surveillance system integration is closely linked to construction management. A complete delivery approach must account for field devices, communications pathways, electrical infrastructure, existing system maintenance, traffic-control staging and coordination with neighboring projects. These are interdependent workstreams, and overlooking their interfaces can complicate scheduling and implementation.
For industrial automation and infrastructure professionals, the broader takeaway is to manage ITS as an integrated operational system while planning its delivery as coordinated construction work. Define dependencies early, document interfaces, schedule agency reviews and verify detailed technical requirements against the governing project documents. That discipline helps align installation and integration activities with both roadway construction and the needs of the operating traffic network.