OCTA Harbor Boulevard Transit Signal Priority: RFQ Inputs for Pole-Side Infrastructure

OCTA describes a 12-mile Harbor Boulevard study across five cities. Its pilot scope evaluated cloud-based transit signal priority and multiple detection technologies at nine signalized intersections in the City of Fullerton. OCTA identifies Route 43 and Rapid Route 543 as the corridor services considered; the public project page says the study was completed in December 2025.

USDOT’s June 2026 final implementation report identifies the Stage 1 project as a smart-traffic-signals effort. It describes integration of existing signal systems, new multimodal ITS devices and proactive signal operations. The report discusses video detection, lidar, radar and other technology considerations, and it records coordination across OCTA, the City of Fullerton and the relevant operating systems.

The published sources are about a particular OCTA corridor, not a product drawing. Their procurement lesson is nevertheless practical: do not quote a “smart traffic pole” from a concept phrase alone. The request should identify whether the supplied item is a replacement signal support, a new mast arm, a camera or detector mount, a communications enclosure interface, a roadway-lighting support, or only one element of a coordinated intersection package.

A cloud platform does not establish shaft geometry, attachment loads, signal-head layout, cabinet terminations, conduit responsibility, access clearances, traffic-control staging, permits or acceptance tests. Those decisions belong to the issuing agency and responsible project team. A supplier can propose a configuration against the issued documents; it should not fill an open civil, electrical or authority scope with an assumed answer.

OCTA’s report notes that establishing a consistent connection to the city traffic-signal system required coordination to understand hardware and software minimum requirements. That is an important distinction for manufacturers. System integration requirements may affect where devices are located and how they are serviced, but they do not by themselves state a mounting detail that can be fabricated.

Before releasing steel or aluminum, a buyer should provide the current intersection plan, signal equipment schedule, approved attachment locations, device dimensions and weights where available, cable/conduit interface, cabinet and power boundary, structural review path, finish, delivery point and release revision. Keep “supplied pole hardware” separate from traffic-system commissioning, network configuration and field installation unless the contract expressly joins them.

Use the current plan set as the controlling record. Mark each device as selected, owner-furnished, supplier-furnished, pending or excluded. Attach the responsible party to every open interface. This makes it easier to compare quotations without treating a missing detector bracket, cabinet adapter or installation scope as a price difference in the pole itself.

The existing traffic signal pole RFQ guide can organize pole-side inputs, while the multifunctional pole guide helps distinguish communications and lighting equipment from the core shaft. For roadway lighting installed near the intersection, use the Roadway Light Poles family only after the project’s own layout and equipment schedule are known.

In a confirmed-interface case, the agency issues an intersection plan, signal and detection schedule, pole/mast-arm locations, attachment and cable data, cabinet interface, construction staging notes, finish and review requirements. The supplier prices a defined support assembly, identifies its supplied accessories and shows any exclusions. The agency and its design team retain responsibility for traffic operations, electrical design, civil work and acceptance.

This produces comparable bids because the same device list and interface record reach each bidder. It also gives the fabricator a revision-controlled basis for shop drawings rather than a verbal instruction to make a support “ready for smart signals.”

In an open-item case, an owner knows it wants transit priority but has not selected sensor types, locations, cabinet architecture or the agency responsible for maintenance. A preliminary budget discussion can still be useful when it is clearly marked as preliminary and records assumptions. It is not a fabrication release.

The next request should close the selected versus pending equipment list, location drawings, device/interface responsibility, access needs, owner review route and required delivery condition. The shop-drawing release guide explains why the fabrication package must track approved interfaces rather than an early concept.

The table below is a buyer checklist, not a requirement imposed by OCTA or USDOT. It gives a project team a way to turn an infrastructure-news item into a controlled inquiry.