Plan support at the same time as procurement
A traffic controller lifecycle plan should define how the fleet will be diagnosed, restored, repaired, updated and retired before the first production order. Waiting for failures to reveal spare-board, firmware or documentation gaps increases restoration time and encourages uncontrolled substitutions.
Choose repair levels
| Level | Typical work | Required resources |
|---|---|---|
| Field replacement | Swap controller, board, modem, fuse or surge device | Approved spares, configuration restore and commissioning test |
| Local workshop | Diagnosis, board exchange and controlled functional test | Fixture, manuals, training and failure records |
| Manufacturer repair | Component-level repair, analysis and firmware recovery | Return process, turnaround target and traceability |
Size spares from failure impact and lead time
Classify parts by whether failure stops the intersection, reduces a function or can wait for planned maintenance. Combine installed quantity, expected demand, repair turnaround, procurement lead time and distribution distance. Include configured replacement controllers, not only unprogrammed boards.
Control component and firmware changes
Require notification before a board, processor, modem, power component, connector or firmware dependency changes. The notice should identify affected models, reason, compatibility, validation evidence, last-order date and recommended action for existing fleets.
Keep service records useful
Record controller and board serial numbers, firmware, configuration checksum, fault symptoms, measurements, replaced parts, repair result and technician. Use consistent failure codes so the buyer and manufacturer can identify repeat causes and improve future production or maintenance.
Define end-of-life before it arrives
Agree the notification period, final purchase option, repair-support period, replacement compatibility and data/configuration migration path. A successor controller should be tested with the existing cabinet, central platform and field procedures before the original product becomes unavailable.
Frequently asked questions
How many spare traffic controllers should a project buy?
There is no universal percentage. Calculate spares from fleet size, failure impact, repair turnaround, supply lead time, geographic distribution and service target. Include at least the configurations needed to restore the most critical intersections without waiting for factory programming or international shipment.
What component changes require customer notification?
Notify changes that affect fit, function, firmware, protocol behavior, test coverage, reliability, regulatory evidence, repair compatibility or appearance promised to the customer. The notice should identify affected models and dates, explain validation and state whether mixed old and new units can share one fleet.
What should be included in controller end-of-life planning?
Define advance notice, last-order timing, remaining spares, repair support, firmware support, successor model, cabinet and protocol compatibility, training and configuration migration. Validate the replacement before the old controller becomes unavailable so procurement and operations are not forced into an emergency transition.