Lumeitalia
Structure of the standards applicable to remote management and smart city, main requirements and verification pitfalls.
Knowing which standard applies is the first step; understanding how its requirements are structured is what separates a compliant design from a merely complete one. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This note summarises the structure of the references applicable to remote management and smart city.
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.
Lighting standards generally separate three levels: classification of the field of application, performance requirements attached to each class, and the calculation or measurement methods to prove compliance. Skipping the first level is the commonest mistake: the product is chosen before the class is determined, and the design ends up justifying a decision already taken.
Compliance is demonstrated through the design calculation and, where required, field measurements taken with the prescribed method. Verification conditions must be documented, because the same installation can pass or fail depending on the measurement grid, maintenance status and ambient conditions. A report showing only results, without conditions, is not verifiable.
Watch out for updates: standards are periodically revised, and a specification citing a superseded edition can create misalignment between design, supply and commissioning. Citing the standard with its edition year and referring to the edition in force avoids the issue.
Lighting requirements overlap with electrical, safety and environmental ones, plus local rules that may be stricter. In case of conflict the most severe applicable rule prevails, but the choice must be justified in the technical report to prevent later disputes.
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.
