When a Signal Fault Can't Be Traced to a Record
The call comes in: signal head dark on the secondary approach at a mid-block crossing. Your crew gets there and finds a 150mm mastarm pole with a 300mm 6-aspect circular-and-right-arrow lantern on one arm and what appears to be a halogen 200mm 3-aspect on another — but there's no record confirming what was installed, by whom, or under which contract. The installation date field in the old spreadsheet is blank. The contract number, if it ever existed, is buried in a PDF somewhere on a decommissioned shared drive.
This is the operational reality of traffic signal management when asset records are maintained casually: every fault event starts with field verification of what should already be known. You're paying crew time to rediscover the inventory instead of fixing the problem.
What a Complete Signal Record Actually Contains
A functional signal asset record has two distinct halves: the physical infrastructure, and the administrative provenance. Most systems either handle one or the other.
The Pole Type field distinguishes between 150mm mastarm poles and 100mm signal poles — a distinction that matters for load calculations, mounting hardware specs, and the lantern configurations each structure can support. Paired with GPS Location and Pole Number, each record is unambiguously tied to a physical structure. You're not managing a description; you're managing an asset at a coordinate.
The lantern configuration is where this template gets specific. Five separate Lantern Type fields — each a multichoice from fifteen options — allow you to document every head mounted on a structure independently. A complex intersection approach might run a 300mm 3-aspect circular on the primary through movement, a 200mm 4-aspect right-arrow on the dedicated turn phase, and a pedestrian lantern (Red Man/Green Man) on the crossing. That configuration needs to be recorded per head, not collapsed into a single "traffic signal" entry. When the 4-aspect lantern fails and you're ordering the replacement, you need the exact spec: 200mm, 4-aspect, right arrow. Not an educated guess.
Lantern Luminaire Type — Halogen or LED — drives maintenance scheduling. Halogen heads in your network are on a predictable replacement cycle; LED heads are not. Filtering by luminaire type across your full asset inventory tells you exactly which sites still have halogen technology and where the next failures are statistically likely to emerge. It's the difference between reactive maintenance and a planned LED retrofit program.
Field Conditions and the Vehicle Detection Record
Three sentences: Vehicle Detection Type — Induction Loop, Radar, Camera — is the field that changes your fault response protocol entirely. A reported Phase 3 failure at a radar-detected approach is a different diagnostic process than the same fault at an inductive loop installation. Log it at commissioning and every technician who responds to that site afterward knows what they're walking into.
The Administrative Layer That Protects You at Contract Renewal
Contract No and Installation Date are the fields that look administrative but carry operational weight. Installation date, cross-referenced against equipment age and failure history, is your evidence base when arguing for infrastructure replacement funding. When a 2009 halogen installation at a high-incident intersection has logged multiple lamp failures in the past eighteen months, the installation date in the record is what makes that argument quantitative rather than anecdotal.
Contract number links every asset to the procurement event that created it, which matters when a warranty dispute arises with a contractor who has since changed company names. You have the contract number; they have the obligation. The Pedestrian Push Button field — simple yes/no — rounds out the ADA compliance picture when auditing which intersections have pedestrian accommodation and which are still on the list for retrofit.
A traffic signal inventory that can't be queried by lantern type, detection technology, or installation age isn't an asset management system. It's a list.