Traffic Signal Commissioning Before an Intersection Opens

Key Takeaways

• Identify suppliers, retained equipment, integration responsibilities, platform contacts, network access, and accounts so missing dependencies do not leave commissioning incomplete.
• Use the approved plan to check required operation, monitoring, detection, communications, backup behavior, agreed abnormal conditions, and recovery for the actual installation.
• Qualified personnel must use controlled conditions for protection and operational tests; do not improvise disconnections, power cuts, or live-traffic detection trials.
• Retain tested models, versions, settings, results, and owners of unfinished items; resolve required issues and follow the responsible authority's opening arrangements.

Commissioning establishes how the traffic signal system operates as an installation, including normal behavior, agreed abnormal handling, and recovery. Delivered equipment, illuminated indications, or a network connection alone do not establish readiness to open an intersection.

Assign the complete commissioning scope and dependencies

Define supply, installation, integration, and acceptance separately. Include heads, supports, cabinet, detection, communications, backup power, and commissioning as applicable. Identify the integration organizer, existing platform contact, and providers of network access and accounts. Delivered equipment can remain unusable if these dependencies are unresolved.

Acceptance should cover normal operation, agreed abnormal handling, and recovery, with unfinished items retained for closure. Lighting up, switching, and appearing online are individual observations rather than complete commissioning. Resolve the required issues and follow the responsible authority’s opening arrangements before the intersection enters service.

Traffic signal equipment cannot be assumed interchangeable between countries because it looks similar. Indications, control, installation, power, and acceptance requirements can vary by destination and project. State the location and intended use, then obtain the applicable requirements rather than requesting compliance with an unspecified international standard.

Check that certificates and reports identify the product, version, and test scope. A component test does not verify every function of a complete signal system. Documents used in one market do not automatically establish approval in another. Ask the technical lead to explain what evidence is needed and what each document demonstrates.

Using the UK’s Traffic Signs Manual or US requirements calls for confirmation of the adopted version and local context. They should not be copied into another destination’s acceptance criteria without confirmation by the responsible project authority.

Record responsibilities, controlled checks, and closure

• Responsibilities: Before commissioning, identify every participating organization and the equipment each supplies or retains.
• Controlled checks: Qualified personnel need a controlled arrangement for the relevant checks, especially those affecting protection or operation.
• Closure record: Record unfinished items with a responsible party and a clear closure check. Keep the tested models, versions, and settings so later changes can be assessed against a known configuration.

Installation Handover Before Signal Commissioning

Use this handover record before commissioning begins, with the actual installation and current approved documents. Each “To confirm” entry needs a project record or a responsible decision; it is not a passed inspection or a test result.

Installation Handover Before Signal Commissioning — project records and scope to confirm

Handover / quotation item	Information or record to provide	Review and scope confirmation	Project record
Approved design and test basis	Current intersection drawings, approved operating plan and commissioning procedure	Identify destination, authority, document revisions and the party approving the test arrangement. Do not substitute another jurisdiction’s requirements.	To confirm
Installed and retained equipment identity	Equipment schedule, model/version records and installation references	Identify heads, poles, cabinet/controller, detection, communications and backup equipment as applicable. Record what is retained, replaced and provided by each party.	To confirm
Mechanical installation handover	Approved support, mounting, connection and foundation records	Have the responsible installation/engineering party confirm the installed arrangement against approved documents. This checklist supplies no structural result, torque or mounting value.	To confirm
Power and electrical boundary	Approved electrical drawings, actual supply details and applicable inspection records	Assign supply, isolation, earthing, protection and connection responsibilities to the qualified parties. Unconfirmed voltage, wiring or inspection status remains open.	To confirm
Control and equipment interfaces	Wiring/interface records and identified controller, output, head and detector versions	Confirm that the actual combination is ready for the approved checks. A matching connector or illuminated head alone does not establish compatibility.	To confirm
Configuration and communication readiness	Approved program/configuration reference, required functions and access arrangements	Identify who configures control, who provides authorized platform/network access and who reviews changes. Record local operation and communication-loss requirements without assuming a protocol.	To confirm
Detection and backup test inputs	Approved detection scope, load list and required backup behavior where applicable	Identify the conditions and functions to be tested with the actual equipment. Runtime, capacity and test outcomes are not established by this checklist.	To confirm
Controlled work and test responsibilities	Named installer, integrator, tester, witness and accepting authority	Confirm the approved site/traffic-control arrangement, qualified personnel and test responsibilities. Do not improvise fault or power-loss tests at an open intersection.	To confirm
Outstanding items and readiness decision	Defect/dependency register, responsible owner and closure evidence	Keep unresolved items visible and obtain the responsible party’s documented decision before the affected test proceeds. Delivery completion is not commissioning acceptance.	To confirm
Handover record and opening boundary	Signed handover, final drawing/configuration references and acceptance plan	Record what has been handed over for testing and what remains. Readiness for commissioning does not authorize opening the intersection; follow the authority’s separate acceptance and opening arrangements.	To confirm

On narrow screens, scroll the table sideways to read every column.

Separate equipment delivery, installation handover, commissioning acceptance and authority permission to open. Keep missing records or unresolved interfaces with their assigned owner. The signal-system interface checklist supports the retained/new equipment review, while the project RFQ information checklist helps identify divided supply and service scope.

Verify required operation, monitoring, and recovery

An approved test plan should go beyond manually illuminating each color. Include normal indications, transitions, fault monitoring, agreed abnormal conditions, and recovery. Protection or conflict-related testing belongs in controlled conditions with qualified personnel, not improvised disconnections at an open intersection. Do not disable monitoring merely to silence an alarm after a replacement.

Matching voltage and connecting wires are only part of compatibility. The cabinet also needs to interpret operation and faults correctly. Some old equipment and replacement LED heads can produce unexpected alarms, faint illumination, or other behavior, depending on the configuration.

Collect the cabinet, controller, output equipment, and existing head identities, plus wiring and operating records. Ask the existing maintenance party to resolve missing information. An exterior photograph is not enough to establish these interfaces. The quotation should identify retained equipment, required changes, and the party responsible for integration.

For networked systems, list the information and operations actually required. An online icon does not prove that fault details are available or that every requested remote operation is supported. Confirm interface versions, functions, permissions, and local operation if communication fails.

Use a sample or confirmed configuration to verify the required functions. Retain models, software versions, settings, results, and unresolved items. If a significant component or version changes afterward, review whether the earlier conclusion still applies. Agree each supplier’s responsibilities so an interface problem is not left between organizations.

Include the approved backup behavior

A backup supply may need to support more than the visible lights. The controller, detection, communications, and related equipment can belong to the approved operating scope. Identify which functions must continue, for how long, and how normal operation resumes before comparing battery capacity.

Request a complete load list and identify which entries are measured or estimated. Match the list to the actual cabinet. Adding communication devices or other equipment can change demand, so an earlier runtime result may no longer describe the installation. Do not connect extra loads without reviewing the backup arrangement.

Runtime also depends on battery condition, temperature, charge state, and switching behavior. A longest advertised duration under particular conditions is not automatically a field guarantee. Compare quotations under the same supported operating state and test conditions.

Before service, the responsible organization should arrange controlled tests of supply loss, backup operation, and restoration. Record the connected loads, signal behavior, control operation, and faults observed. Buyers may witness and review the records; they should not cut power at an open intersection to try the system.

Include ongoing battery condition, charging, alarms, testing, spare parts, and replacement conditions in maintenance planning. A long period without a power failure does not prove that backup capacity remains ready. Clarify who receives alarms and how follow-up is organized so deterioration is not discovered only during an actual outage.

Check detection against representative use

A vehicle waiting unusually long does not necessarily indicate a failed signal head. First establish whether the movement uses detection and how demand is submitted. Timing arrangements, congestion, or other control conditions may also explain the observation.

Maintenance personnel need to answer two separate questions: was the vehicle’s demand detected, and was the resulting request handled as intended? The first involves detection area, equipment, and output. The second involves control settings and operating conditions. A detector shown as online does not demonstrate reliable recognition of every relevant road user.

Use an approved safe validation arrangement covering representative vehicles and positions. Small vehicles, motorcycles, edge positions, and relevant rain or strong-light conditions can expose different limitations. The appropriate conditions depend on the detection method and site requirements; one successful vehicle passage is not comprehensive evidence.

Review recent road work as well. Resurfacing, revised markings, moved equipment, or intersection changes can separate the original detection area from where vehicles now stop. Provide construction dates and change records so the technical team can distinguish a fault from a configuration that no longer fits the site.

After intervention, record the cause found, adjustments made, vehicles and positions checked, and results. A restart or replacement without follow-up does not establish that the recurring problem has ended. Ordinary users should report location, direction, time, and behavior rather than changing stopping positions or testing equipment in live traffic.