Picture two tenders for a 2,000-luminaire municipal project landing on the same desk. One quotes a node at $45, the other at $38. On the surface, the cheaper option appears to be the obvious choice. Yet two years into operation, the project that initially seemed more expensive may turn out to have the lower cost per luminaire.
Situations like this are more common than many people in the industry would expect.
The reason is straightforward: in smart street lighting, the controller is only one element of a much larger cost structure.
How costs are actually distributed
Different manufacturers distribute costs differently across their system architectures.
Some bundle software into the hardware price. Others provide the management platform through annual subscriptions. Some include gateways and communication infrastructure as part of the solution, while others treat them as separate components.
As a result, comparing node prices across vendors often means comparing only parts of entirely different systems. Two proposals with similar hardware costs can diverge significantly once the complete architecture is taken into account.
The factors that are routinely overlooked
Beyond the controllers themselves, a real-world smart lighting deployment involves several cost categories that are often underestimated during the early stages of project evaluation.
Drivers
One of the most overlooked variables is driver selection.
If a project requires electrical monitoring at every luminaire, Zhaga-based architectures typically rely on D4i-compatible drivers, which are more expensive than standard alternatives.
Certain NEMA controller architectures can perform electrical measurements independently and operate with simpler driver types, including:
- DALI-1;
- DALI-2;
- 0–10V.
On large-scale projects, differences in driver selection may have a greater impact on project economics than differences in controller pricing.
Gateways
Data aggregation devices are another part of the infrastructure that is frequently underestimated during the budgeting phase, despite being essential elements of the system.
Software
The management platform may be:
- included in the system price;
- supplied under a perpetual licence;
- delivered through a Software-as-a-Service (SaaS) model.
The selected licensing model can significantly influence long-term operating costs.
Communications
SIM cards, NB-IoT, LoRaWAN, RF mesh networks and other communication technologies introduce additional costs that may be either one-time expenses or recurring charges, depending on the system architecture.
Commissioning
System setup and commissioning costs vary according to project scale, architecture and integration complexity.
Ongoing support and updates
Software maintenance, technical support and future updates rarely appear prominently in an initial proposal, yet they become part of the operating cost structure from the moment the system enters service.
From a Total Cost of Ownership (TCO) perspective, the controller itself represents only one element of the overall architecture. The economics of a project are ultimately determined by the combination of capital expenditure and long-term operating costs.
How one manufacturer approaches project evaluation
DITRA Solutions, a European manufacturer of street lighting control systems, has moved away from component-level comparisons when evaluating projects.
According to the company, the most meaningful benchmark is the cost of controlling a single luminaire over a five-to-ten-year period rather than the price of any individual device.
The methodology used by the company can be expressed as follows:
Cost per luminaire = (Nodes + Drivers + Gateways + Software + Licences and subscriptions + Communications + Commissioning + Technical support) ÷ Number of luminaires
This approach provides a more realistic basis for comparing different architectures and licensing models than simply looking at hardware prices.
In the company’s view, there is no such thing as a universally inexpensive controller. The economics of a smart street lighting system should always be evaluated in the context of the complete architecture.
What this means in practice
For municipalities, utilities and system integrators, the practical implication is straightforward: ask suppliers for a complete cost breakdown covering the expected lifetime of the system, rather than focusing solely on controller prices.
Two proposals with similar equipment costs may look very different once software licensing, communication infrastructure, commissioning and technical support are taken into account. Conversely, a controller with a higher purchase price may ultimately prove to be the more economical option over the lifetime of the installation.
For this reason, the industry is gradually shifting from comparing component prices to evaluating the cost of controlling each luminaire throughout the entire lifecycle of the system.
Projects where this approach is adopted from the beginning tend to produce fewer budget surprises during operation, which ultimately is the point.
