How to Record Intermittent Traffic Signal Faults

Key Takeaways

• Intermittent traffic signal faults may disappear before maintenance arrives. A timed record of the affected approach, indication, duration, weather, and associated equipment gives the investigation something to compare.
• An intermittent fault may disappear before a technician arrives, so note the time, affected approach or indication, duration, weather, and any power event.
• Preserve the operating configuration and recent change history. Do not restart, disconnect, or alter an open intersection simply to reproduce the symptom.
• At closeout, ask what cause was identified, what work was completed, and how the result was verified.

Intermittent traffic signal faults may disappear before maintenance arrives. A timed record of the affected approach, indication, duration, weather, and associated equipment gives the investigation something to compare. Do not erase that pattern through unauthorized restarts or setting changes.

Preserve the sequence of the intermittent event

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.

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.

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.

Make separate observations useful as one fault history

Preserve the operating configuration and recent change history alongside the time-aligned event record. Keep repeated incidents together so the team can compare time, weather, power, equipment versions, and road changes.

Qualified personnel need a controlled investigation. Link each reported event to the cause identified, work completed, verification and any continued observation; the reporting, traffic-management, operation and restoration responsibilities are set out above.

Keep equipment identities and interface changes available

If the investigation involves equipment compatibility, replacement equipment or changed interfaces, keep the following compatibility evidence with the fault history.

Equipment compatibility and replacement interfaces

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.

Network functions and configuration records

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 power events and backup behavior where relevant

Where the event involves power loss or backup behavior, relate the fault record to the approved backup scope and the checks below.

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.

Separate detection symptoms from control treatment

If the reported event is a waiting movement that receives no expected response, distinguish detection from control treatment as follows.

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.