Street Lighting Management Software: Custom Build Versus Telensa, Itron and Signify

What the off-the-shelf products actually do well

You are paying a bill nobody can check, and the products in this market were built to solve a different problem. Both statements are true, so start with what they genuinely give you.

Telensa built a control system around its own telecells and network, and where it is deployed it does dimming, scheduling and fault reporting competently. Itron Streetlight.Vision is a mature control management system that supports nodes from several vendors, which is a real advantage in a city that bought controllers in three waves rather than one. Signify Interact City is strong inside the Signify ecosystem and is a sensible default if your luminaires and controllers are theirs. Ubicquia and Tvilight are hardware led, delivering devices into the standard ANSI C136.41 dimming receptacle with their own analytics attached.

The TALQ Consortium interoperability standard exists because the industry knows mixed estates are the norm, and it helps. If you have controllers and you want them scheduled, dimmed and reporting faults, buy one of these rather than writing a control system. Nobody should build node communications.

If you own fewer than about 1,500 lights and the utility maintains them under a full service tariff, buy nothing at all. Request the inventory file annually, walk a sample of streets with a clipboard, and put the difference into replacing knocked-down poles. That is the honest recommendation for a small town and we give it regularly.

Where they stop: the fixtures with no hardware on them

Every one of those products sees what it is attached to. Your inventory includes thousands of luminaires with no node on them at all, and those are invisible to a control management system. That is the gap, and it is where the money is.

An unmetered street lighting bill is not a measurement. It is arithmetic: a count of fixtures by wattage class, multiplied by an assumed number of annual burn hours printed on the tariff sheet, multiplied by a rate. The count comes from a file the utility maintains, and most cities have never audited that file against the poles that exist.

The specific way it goes wrong is worth spelling out. Ten years ago a corridor was converted from 250 watt high pressure sodium to light-emitting diode. The contractor did the work and somebody emailed a spreadsheet. Half the records updated. A developer later dedicated a subdivision whose lights were never added. Three poles were knocked down and never replaced, and they are still on the billing file. And where a crew replaced a 400 watt head with a 150 watt fixture, the utility kept the old wattage class because the change form used the old fixture code.

Nobody in your department can reconcile that, because the utility file carries their identifiers, your geographic information system layer carries yours, and the field carries neither. The first honest inventory a city does after a conversion almost always finds discrepancies in both directions, and the direction that matters is the one where you have been paying for wattage you no longer draw.

The second gap is outages. Without controllers the detection system is a resident driving home at 11pm. The report says the light is out near Elm and Fifth, which describes four poles. Even where you do have nodes, the alarm lands in the vendor portal, which is not the system the crew with the bucket truck uses.

The arithmetic: per luminaire per year against a build

Control management platforms are priced per node per year, and that is the right unit for the comparison, so convert everything to cost per luminaire before looking at anything else.

Suppose the software tier is $3 a luminaire a year. An estate of 18,000 lights is $54,000 a year, and that covers only the fixtures with nodes on them, so your effective rate across the whole estate is higher than the quote suggests. A first release build at $80,000 with $16,000 a year of support is $144,000 across five years, about $28,800 a year. The crossover sits near 9,600 luminaires at $3 each, and near 4,800 at $6.

Then there is the number that makes the licence comparison look trivial. Take your annual unmetered charge and divide it by the fixtures on the billing file to get your paid rate per fixture. Now assume a discrepancy rate you would not be surprised by, apply it to your estate, and multiply. Cities routinely find that the first variance report handed to the utility with location evidence attached pays back the whole project inside two billing cycles. That is the business case, not the licence saving.

If your conversion was financed through an energy savings performance contract, there is a second bill nobody checks. Verification for lighting retrofits on unmetered circuits is normally a stipulated calculation under the measurement and verification protocol in the contract, not metered consumption, so the guaranteed saving is only as good as the fixture count and wattage assignment. Which is the same register you cannot currently trust.

What a custom build actually costs

A first release runs $50,000 to $110,000 over 10 to 14 weeks, covering the luminaire and pole register with a field survey application, utility billing file reconciliation, and citizen report to work order flow with deduplication.

A full platform adding multi-vendor controller adapters, energy and burn hour modelling, savings verification, capital programme tracking and a public outage map runs $140,000 to $300,000 phased over 6 to 10 months.

Data migration is 10 to 25 percent of the build, and in street lighting it is the register itself. You are merging a contractor closeout file, a geographic information system layer and a utility billing extract whose identifiers do not agree, then flagging every record with how it was established. That last field matters more than it sounds: a record confirmed by field survey in the last two years is a different thing from one inherited from a spreadsheet, and a system that hides the difference is as wrong as what it replaced, only cleaner looking.

Year two runs 15 to 20 percent annually: tariff schedule changes, a new controller vendor during a transition, additional dedicated subdivisions, and the council reporting that appears once the data exists.

What pushes the number up: the number of controller vendors to adapt, whether the utility will provide the billing file in a machine readable format or only as a portable document, whether your 311 platform exposes an interface, and how much of the estate needs a physical survey before anyone trusts the register.

The four situations where building wins

Regulatory and contractual fit. If a council member reads the energy savings performance contract schedule and asks in a public meeting whether the guaranteed savings are being realised, the correct answer states how many fixtures of what type operate for how many hours, traceable to something other than the contractor's closeout spreadsheet. Roadway lighting design expectations under IESNA RP-8 and any dark sky ordinance you have adopted also live in the register rather than in a control system.

Scale economics. Past roughly 9,600 luminaires at $3 a node a year, or 4,800 at $6, licence arithmetic has turned before you count the billing recovery.

A workflow that is your advantage. Billing reconciliation is the one that pays. Ingest the utility file each cycle, match to your register on identifier and location, and produce three lists: billed but not in your register, in your register but not billed, and billed at a wattage that disagrees. Then compute the expected charge yourself from the tariff schedule using its printed burn hours, and show the variance with location evidence attached. No control vendor will ever build this, because it is an argument with their channel partner.

Integration sprawl across three or more systems. A dark pole should produce one work order from three input channels: a 311 report, a controller alarm and a crew patrol, deduplicated so four residents create one job and four notification subscriptions. That join sits across your 311 platform, two or three controller portals and your work order system.

How to decide in a week

Send two people out for one day with a tablet and a printed extract of the utility billing file for four streets you converted more than five years ago.

Walk every pole. Record what is actually there: pole present or absent, fixture type, wattage marking, node fitted or not. Compare against the billing extract line by line and count three things: fixtures billed that do not exist, fixtures that exist and are not billed, and wattage classes that disagree. Extrapolate the wattage discrepancies across your estate at your paid rate.

• If the four streets reconcile cleanly, keep asking the utility for the file annually and spend nothing.
• If the extrapolated wattage variance exceeds the first release cost, build the register and the reconciliation before anything else.
• If a resident report cannot be matched to a pole identifier, build citizen intake and deduplication in the same phase.
• If you have controllers from two vendors, build the adapter layer before buying a third.

Then commission a paid discovery phase rather than accepting a proposal. At Digital Heroes that is two to three weeks producing a signed product requirements document covering the register schema with its source-of-truth handling, the billing file format, the controller adapters in scope and the acceptance criteria. You keep it whether or not you hire us and can put it out to bid.

Who we are wrong for: a city whose main need is dimming, scheduling and node fault reporting. Buy Itron Streetlight.Vision or Interact City and let the vendor own the radios. We are more than fifty specialists with over 2,000 projects delivered, verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and by D-U-N-S number. Our own products, ShopScore, HeroCheckout and Section Vault, are commerce and documentation tools rather than lighting ones, so judge us on delivered client work. Our India LLP, US LLC and UK LTD entities mean intellectual property assigns under your own law, which your city attorney will check. You meet the named team before you sign.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.