Lumeitalia
How to build a defensible baseline and prove the actual savings of a remote management and smart city project.
Savings claimed at bid stage and savings proven in operation coincide only when a properly built baseline exists. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This Centro Studi Lumeitalia piece describes how to set up measurement and verification in a remote management and smart city intervention.
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.
The baseline is not installed power: it is actual consumption over the reference period, reconstructed from meter readings or bills, tied to real operating hours and the period's operating conditions. Any switched-off or failed luminaires must be documented, because including non-working units inflates the savings artificially.
In remote management and smart city contexts it is also worth noting planned changes in use after the intervention: a change in schedule or intended use alters consumption regardless of the installed technology.
The before/after comparison requires declaring which variables may change and how data is corrected: operating hours, served area or length, dimming profile, any extensions. Without written adjustment rules, every deviation becomes a negotiation at the first unusual energy bill.
Measurement can be spot-based (campaigns on representative circuits) or continuous (dedicated meters, data from the remote management system). Continuous measurement is preferable when a guaranteed-performance contract is in place. In any case the post-intervention observation period must cover operating conditions comparable with the baseline.
The result must be reported in a document stating method, raw data, applied adjustments and net savings. It is the document that turns savings into data rather than a marketing claim.
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.
An orderly method drastically reduces variations during works and disputes at commissioning. Three choices make the difference from the earliest stages.
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.
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.
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.
By requiring standard protocols, replaceable nodes and the right to export historical data in open formats.
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.
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.