A city with forty thousand street lights typically cannot answer a basic question with confidence — exactly how many poles it owns, what fixture type sits on each one, and which arms and drivers are approaching end of life. Street lighting is usually the largest single asset count in a public works inventory by unit volume, yet it is often tracked in the least structured way, split across GIS layers, utility billing records, and outage complaint logs that were never designed to talk to each other. OxMaint gives municipal lighting teams the structured fleet inventory platform that gives every pole, arm, fixture, and driver a single asset record from installation to decommission.
Building a Complete Pole-to-Driver Inventory for Your Street Light Fleet
A practical framework for registering every pole, arm, fixture, and driver in a city lighting network so outage response, LED conversion planning, and energy billing all draw from one accurate asset record.
Why Street Light Fleets Outgrow Spreadsheet Tracking
Most street light networks were installed in phases over fifty or more years, by different contractors, under different utility ownership arrangements. A pole installed in 1985 and one installed in 2019 rarely share a consistent ID scheme, let alone a common record of fixture type or wattage, and successive annexations or utility territory changes only add more inconsistent naming conventions to the mix.
The result is a fleet that is easy to see from a car window but hard to manage from a desk. Outage reports come in by intersection name rather than asset ID. LED conversion planning stalls because nobody has a reliable count of remaining high-pressure sodium fixtures. Energy billing disputes with the utility drag on because pole counts do not match between the city's records and the utility's, leaving staff to reconcile the difference manually every billing cycle instead of pointing to a verified source of truth.
Four Problems a Structured Fleet Inventory Solves Immediately
Once poles, arms, fixtures, and drivers exist as linked asset records rather than a flat spreadsheet row, several long-standing municipal lighting problems become straightforward to manage instead of chronic.
OxMaint links poles, arms, fixtures, and drivers into one hierarchy, so a single outage report, inspection, or conversion project pulls accurate data instead of a best guess from the field.
Building the Inventory: A Phased Approach for Large Fleets
Registering forty thousand or more individual light points is not a weekend project. Cities that succeed break the effort into phases rather than attempting a single citywide data collection push.
Fixture Type Distribution: What a Conversion-Ready Inventory Looks Like
Cities planning an LED conversion need a fixture-level breakdown, not just a total pole count, to build an accurate capital request and phasing plan. The structure below is what that breakdown should contain.
| Fixture Category | Data Needed | Planning Use |
|---|---|---|
| High-pressure sodium (legacy) | Count, wattage, remaining service life | Primary conversion target for energy savings |
| Metal halide | Count, location, failure frequency | Secondary conversion priority based on failure rate |
| LED (already converted) | Install date, warranty term, driver type | Warranty tracking and dimming program eligibility |
| Decorative/historic fixtures | Custom fixture specs, retrofit compatibility | Special-case budgeting outside standard conversion batches |
How OxMaint Supports Municipal Street Light Fleet Management
OxMaint gives lighting teams the structured asset hierarchy and mobile workflow tools to register, maintain, and report on a fleet that can run into the tens of thousands of individual light points.
Energy Billing Reconciliation: Where Inventory Gaps Cost Cities Real Money
Many municipalities pay for street light energy under a fixed-rate tariff based on the number and wattage of fixtures on the utility's books, rather than metered consumption per pole. Under that billing model, the city is charged for exactly what the utility's inventory says exists — which means any mismatch between the utility's pole count and the city's actual fleet becomes a direct financial issue, not just a data quality annoyance that can be addressed whenever staff time allows.
These mismatches accumulate for predictable reasons. Poles removed during road reconstruction projects are not always reported back to the utility for billing removal. Fixtures upgraded from high-pressure sodium to LED during a city-funded retrofit may still be billed at the higher legacy wattage if the utility's rate schedule was never updated to reflect the change. Decorative or historic district fixtures installed under a special agreement sometimes get billed under the wrong tariff class entirely, and that misclassification can persist for years without anyone noticing on a routine invoice review.
A verified, city-maintained inventory gives lighting staff the independent counterweight needed to challenge utility billing statements with specifics — pole ID, fixture wattage, and install or conversion date — rather than a general dispute based on the total bill feeling too high. Cities that have completed a structured inventory project commonly find measurable billing corrections in the first reconciliation cycle simply because the previous count had never been independently verified against the utility's own records.
Setting an Inspection Cadence for a Modern, Partially Converted Fleet
A fleet mid-way through LED conversion needs a different inspection approach than either a fully legacy network or a fully converted one, because failure patterns differ significantly between lamp types. High-pressure sodium and metal halide fixtures tend to fail gradually, with visible dimming or color shift that a routine night patrol can catch before full outage. LED fixtures and their drivers more often fail abruptly, which shifts more of the detection burden onto resident-reported outages and automated monitoring rather than scheduled visual patrols.
This means the inspection cadence and outage response workflow built for a legacy fleet often needs to be revisited as conversion progresses, rather than left unchanged. Cities partway through a multi-year conversion program benefit from tracking outage response time separately for converted versus non-converted segments of the fleet, since a rising resident complaint volume in a recently converted district can be an early signal of a driver batch issue rather than isolated failures, and is easiest to catch when the underlying fixture and driver data is structured enough to filter by conversion date and manufacturer batch, giving staff a chance to raise a warranty claim before the batch issue spreads across the remaining unconverted districts.
Decommissioning and End-of-Life Tracking Across the Fleet
Street light fleets do not only grow — poles get removed during road widening projects, fixtures get retired ahead of schedule when a manufacturer issues a recall, and entire districts sometimes get decommissioned when a private development takes over lighting responsibility. Without a formal decommissioning step in the asset record, removed poles tend to linger indefinitely in both the city's inventory and, more expensively, on the utility's billing records.
A structured decommissioning workflow closes this gap by requiring a formal end-of-life status change — tied to a removal date, reason, and confirming crew — before a pole record is excluded from active reporting. This keeps the historical record intact for audit purposes while ensuring that active fleet counts, billing reconciliation, and outage routing logic never reference equipment that no longer physically exists, which is a surprisingly common source of error in older municipal lighting inventories that were never given a defined retirement process.
Expert Perspective
Frequently Asked Questions
OxMaint gives municipal lighting teams the pole-to-driver hierarchy, mobile field tools, and fleet-wide reporting needed to manage outages, conversions, and billing with confidence.
