How to Specify Traffic Signal Battery Backup

Key Takeaways

• Specify traffic signal backup power by the functions that must continue during an outage.
• Ask the project team which functions must continue during an outage, how long they are required, and how normal service resumes.
• Mark the load entries that are measured and those still estimated. If equipment is added later, review whether the earlier runtime conclusion remains applicable.
• Before service, have qualified personnel carry out the approved controlled checks for loss of supply, backup operation, and restoration.

Specify traffic signal backup power by the functions that must continue during an outage. The load may include the controller, detection, and communications as well as signal heads. Battery capacity is meaningful only after that supported scope and the required operating state are defined.

Define the functions and loads that need backup

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.

Start the specification with the operating state to be maintained

Match the approved operating scope to the actual cabinet and connected equipment before requesting a battery quotation. Use the measured and estimated load entries, supported operating state and battery conditions described above as the common basis for comparing offers.

Have qualified personnel carry out the approved controlled checks before service. Retain the configuration, observed behavior and unresolved issues. Connect that initial runtime evidence with the continuing inspection, alarm, replacement and follow-up responsibilities so the accepted arrangement remains maintainable.

Check interfaces and behavior during supply changes

Use the supply-loss, backup-operation and restoration checks above for the backup function. The following system-interface checks apply where relevant to that approved scope.

Controlled system checks

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.

Equipment compatibility and any replacement scope

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.

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.

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 ongoing inspection and alarm responsibilities

For faults observed during backup operation or testing, keep the event record and authorized response responsibilities below.

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.

Include controlled verification in commissioning

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.

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.