Signal Heads, Controllers, and Detectors Explained

Key Takeaways

• Heads display the indications, controllers execute the signal arrangement, and detectors provide relevant demand; replacing one component does not automatically fix another's problem.
• Investigate detection and handling of demand separately when waits are unusual; an online detector or brighter head does not establish correct operation.
• List retained equipment and separate display, control, detection, and integration scope, assigning responsibility for cabinet, wiring, communication, and programming interfaces.
• Use qualified personnel and approved controlled tests for system changes; do not reproduce faults in live traffic or disable monitoring to suppress alarms.

A traffic signal system includes distinct jobs: heads display information, the controller executes the signal arrangement, and detectors provide relevant demand. These components work together, but replacing one does not automatically correct a problem in another.

Identify what the head, controller, and detector each does

• Signal head: displays information such as red, yellow, and green indications.
• Controller: executes the signal arrangement.
• Detectors: provide relevant vehicle or pedestrian demand to the system.

A head that illuminates correctly demonstrates only part of the installation’s operation.

If the complaint is congestion, establish whether the problem is visibility, equipment failure, detection, or the release arrangement. Brighter signal heads may improve recognition, but they do not create road space or automatically correct unsuitable control settings. A turning movement that waits too long may need investigation of demand and control rather than replacement displays.

List existing equipment and the proposed changes. A head-only replacement needs interface checks with the retained cabinet and wiring. Replacing the controller also involves detection, communications, programs, and maintenance. A new intersection needs a coordinated design and commissioning arrangement; a set of product photographs is not a system design.

Ask for separate quotation lines for displays, control, detection, and integration, showing what remains in place. This makes clear whether the supplier is providing equipment alone or participating in system modification and verification.

Circular and arrow indications serve different purposes under the approved local design. Do not add an arrow simply because it appears clearer or copy a foreign intersection photograph as a universal configuration. Traffic engineering and management personnel must confirm operating logic, protection, and opening arrangements before the installation enters service.

Use the component roles to define the purchase boundary

Use the separate quotation lines described above to distinguish a product supply, a partial replacement, and help verifying a complete system change. A list of signal-head photographs cannot describe all those responsibilities.

For a head replacement, the cabinet and wiring still need compatibility review. For a controller change, detection, communication, programming, and maintenance may also be involved. The owner should know which party checks the combination and who resolves a mismatch, rather than assuming that independently functioning products will necessarily operate correctly together.

For faults, keep the cause, work, and verification with the actual models and versions. Understanding the roles does not require the buyer to configure the system personally.

Traffic Signal Controller Cabinet: Scope and Interface Questions

Buying a traffic signal controller cabinet starts with an agreed equipment boundary. A cabinet or enclosure, a controller and a complete intersection system are different quotation scopes. Use these questions to identify what the project needs and what an offer includes; the worksheet does not establish that any named supplier manufactures or supplies each item.

Traffic Signal Controller Cabinet: Scope and Interface Questions — project details to confirm

Procurement question / selection item	Information to provide	Confirmation or review required	Project record
What exactly is included?	Itemized scope and existing equipment list	Separate the enclosure, controller, internal equipment, accessories, cabling and site work. Identify inclusions, exclusions and who provides each item.	To confirm
What stays, and what changes?	Retained and proposed equipment identities, drawings and revisions	Identify each retained or replacement part. Ask for a documented interface review; a cabinet name alone does not establish compatibility.	To confirm
Who approves the arrangement?	Destination, project authority and approved design documents	Identify the governing project requirements, approving party and quotation drawing revision. Do not substitute requirements from another destination.	To confirm
What are the power and electrical interfaces?	Actual site supply information and approved electrical drawings	Have the responsible specialist confirm supply, protection, isolation, earthing and connection responsibilities against the proposed equipment. No electrical values are assumed here.	To confirm
What enclosure and site conditions apply?	Installation location, environmental exposure and access information	Request the enclosure, access and environmental requirements for this site and evidence for the offered arrangement. No enclosure rating is specified by this checklist.	To confirm
How will it fit and connect on site?	Approved mounting, available space, cable routes and entry drawings	Confirm mounting, access for maintenance, internal space and cable interfaces against the actual drawing. Do not infer dimensions from an image.	To confirm
How will equipment exchange signals or data?	Controller, detection, display and monitoring interface details	List required inputs, outputs, connection information, software/configuration and communication requirements. Obtain confirmation for the identified equipment and versions.	To confirm
What will be checked before handover?	Approved operating plan, inspection and commissioning requirements	Agree on test scope, interface and abnormal-state checks, responsible parties, records and the authority that accepts the result.	To confirm
What documents and service are included?	Required manuals, drawings, configuration records and support scope	Confirm the offered documentation, access arrangements, replacement-part identification and service responsibilities in writing.	To confirm
What is the quotation based on?	Quantity, destination, delivery terms and unresolved decisions	Reference the approved scope and drawing revision; record exclusions, unpriced items and decisions needed before order release. Missing scope is not a zero-cost item.	To confirm

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

Is the cabinet included with the controller or signal heads?

Confirm it in the itemized offer. Request separate identification of the enclosure, controller, internal equipment and accessories, together with the installation and commissioning responsibilities. Do not infer a complete cabinet package from a signal-head quotation.

Does an existing controller prove that a new cabinet is compatible?

Keep compatibility open until the actual equipment, versions, drawings and required behavior have been reviewed by the responsible parties. Use the signal-system interface checklist to document retained and new equipment.

Trace demand from the road into the system

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.

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.

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.

Check the interfaces between retained and new equipment

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.

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.

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.

Assign maintenance according to the actual fault

Agree who receives reports, who may operate equipment, who arranges traffic management, and who authorizes restoration. A promise to repair quickly is less useful than a procedure linked to the fault’s effect. Spare parts need to match actual models and versions, rather than a generic description such as signal head.

Intermittent faults can disappear before a technician arrives. Record the date, time, approach, indication or equipment affected, duration, weather, and any associated outage. Note whether other equipment was abnormal at the same moment.

Where logs or video are available, align them to a common time. Photographs can show appearance, while continuous video may better describe flickering or transition behavior. Collect material safely without disrupting traffic. Do not unplug equipment, restart it, or alter settings in an operating system merely to reproduce a fault.

At repair closeout, record the cause identified, work completed, replaced parts, and verification result. If the cause remains uncertain, state that and arrange continued observation. Restarted successfully does not mean permanently resolved. Repeated events should be examined together for common weather, time, or construction changes.

Periodic checks should cover the relevant attachments, obstructions, cable entries, backup supply, detection, and communications as well as illumination. The maintenance organization should set the project-specific scope. Owners need a traceable outcome for each recorded issue; a folder of inspection photographs without findings or follow-up is not a complete maintenance record.