Lumeitalia
Dimming based on presence, daylight and traffic: when it really pays off in remote management and smart city.
Adaptive lighting adjusts output based on measured conditions rather than fixed schedules. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This contribution examines under which conditions adaptive control delivers real benefit in remote management and smart city and which mistakes compromise it.
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.
There are three main families: daylight-linked control, presence or passage control, and control based on activity level. Each needs different sensors, placements and calibration. Combining them without a priority logic produces unpredictable behaviour that users perceive as faults.
Adaptive control pays off where there is real, sustained variability: spaces with significant daylight contribution, areas with intermittent occupancy, routes with very different flows across the day. Where conditions are constant, a well-tuned fixed profile achieves the same result with fewer components and fewer failures. In remote management and smart city the assessment must be based on real usage data for the area.
The most common problems are sensor placement in a non-representative area, hold times that are too short and cause switching perceived as annoying, and thresholds set once and never revised. Calibration must be carried out on site with the space in real operating conditions and repeated after the first period of use.
The minimum level required by applicable standards must also be guaranteed at the lowest dimming condition: the saving function cannot reduce performance below the safety requirement.
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.
