Lumeitalia
How to set up a measurement and verification plan to prove the results of a remote management and smart city project.
A saving that cannot be demonstrated is a saving that can be disputed. The measurement and verification plan defines, before the works, how the result will be calculated, from which data and with which normalisations. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting.
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 plan defines the measurement boundary, the baseline period, the independent variables affecting consumption, the normalisation method, the instruments and reading frequency, plus each party's responsibilities. Agreeing it before the works prevents the method being chosen after the fact, when results are already known.
You need consumption data granular enough to distinguish operating profiles, actual burning hours, maintenance events and configuration changes. Where a remote management system exists, most of these data are already available and only need structuring into recurring reports.
Data quality matters more than quantity: a continuous, verified series over a representative period is worth more than a large archive full of unexplained gaps.
Periodic reporting has two functions: proving the result and detecting deviations early. Consumption departing from the forecast almost always signals a concrete issue — altered dimming profiles, undetected faults, usage changes — better addressed immediately than at period end.
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.
