How to compare two technical bids for remote management and smart city
A method for reading remote management and smart city bids side by side: what is comparable, what is not and where the differences hide.
Viale urbano e percorso ciclabile illuminati da apparecchi LED. Immagine illustrativa generata con AI.
Overview
Two bids with the same luminaire count and installed power can describe profoundly different installations. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This methodological comparison by Centro Studi Lumeitalia explains how to read two remote management and smart city proposals in parallel without stopping at price.
Applicable standards
The regulatory reference for remote management and smart city is not a single document but a coordinated set of standards covering performance, safety and environmental impact. In design practice the following documents drive the main choices.
DALI-2 / D4i — interoperability of drivers and control nodes.
NEMA / Zhaga — standard mechanical interfaces for nodes.
GDPR — processing of data collected in urban environments.
Bringing bids onto a common basis
The first step is checking that both proposals assume the same requirements, the same geometry and the same maintenance factor. If one calculates for a new installation and the other at end of life, comparison is impossible until the assumptions are realigned. The same check applies to annual operating hours and the planned dimming profile.
In remote management and smart city projects, differences frequently arise from a different reading of site conditions: clarifying this point in writing is worth more than any comparison table.
Where the differences hide
Photometry — File of the proposed luminaire, not an equivalent — Calculation not reproducible
Maintenance factor — Value and associated cleaning cycle — Below-target performance at end of life
Control — Protocol, dimming curve, signal-loss behaviour — Declared savings not achieved
Maintenance — Cycles, access, spares and lead times — Operating cost above budget
Warranty — Duration, exclusions, validity conditions — Unplanned burden on the client
From price to cost of ownership
A meaningful economic comparison spans the whole operating period: initial investment, annual consumption under the planned dimming conditions, cost of planned maintenance and an estimate of replacements. Energy price and inflation assumptions must be declared: changing them changes the outcome, and undeclared they make the comparison non-reproducible.
The selection criterion must be written before bids are received. Setting parameter weights afterwards is the practice that generates the most disputes in comparative procedures.
Recurring critical points
The difficulties that most often emerge in remote management and smart city projects are not about product selection, but about defining requirements and verifying results.
Avoiding proprietary solutions that tie the municipality to a single supplier.
Ensuring network coverage across wide or complex territories.
Making data genuinely usable by technical departments.
Design approach
An orderly method drastically reduces variations during works and disputes at commissioning. Three choices make the difference from the earliest stages.
Specifications mandating open protocols and data portability.
Hybrid architectures with multiple communication technologies.
Node interface — NEMA / Zhaga — controller replaceability
Data portability — specification — export in open formats
Cyber security — good practice — updates and access management
Most frequent mistakes
Non-conformities found at commissioning almost always come from three causes: requirements not declared or declared without a reference standard, calculation run on idealised geometry, and an optimistic maintenance factor. All three can be avoided at zero cost during design.
Same assumptions on requirements, geometry and operating hours
Maintenance factor aligned across proposals
Photometric files of the luminaires actually offered
Maintenance and spare-part items quantified
Economic assumptions (energy, inflation) declared
Selection criterion defined before bids are opened
Key takeaways
A remote management and smart city project holds up over time when requirements are declared, the calculation reproduces real conditions and on-site verification follows an agreed protocol. Component selection matters, but comes later: without measurable requirements even the best product delivers a result that cannot be demonstrated. Centro Studi Lumeitalia makes its technical office available to review requirements and design checks.
Methodological note: This content is written for technical information purposes by Centro Studi Lumeitalia and does not replace the lighting design or a full reading of the standards cited. Applicable performance values are those of the standards in force at design time.
Domande frequenti
Is remote management always worth it?+
It pays off when the installation is large or hard to supervise: value comes from fewer maintenance trips and fine dimming, not from consumption data alone.
How is supplier lock-in avoided?+
By requiring standard protocols, replaceable nodes and the right to export historical data in open formats.
Where should a remote management and smart city project start?+
From a written definition of performance requirements and verification conditions: this step drives every later choice and makes the result either disputable or defensible at commissioning.
Which documents should be requested from the supplier?+
Photometric files of the proposed luminaires, declaration of conformity, lifetime data declared per IES LM-80 with its conditions, the maintenance schedule and warranty terms.
Lumeitalia — Sistemi LED professionali
Lumeitalia è il brand di illuminazione LED professionale di Mya Tech S.r.l., azienda italiana fondata nel 2011 a Trezzano sul Naviglio (MI); il brand è attivo dal 2020.