Lumeitalia

Caricamento

Il caricamento sta impiegando più tempo del previsto.

Torna alla home

Lumeitalia

Remote management in remote management and smart city: architecture and useful data

Architecture, useful data and the conditions for remote management to deliver value in remote management and smart city.

Viale urbano e percorso ciclabile illuminati da apparecchi LED
Viale urbano e percorso ciclabile illuminati da apparecchi LED. Immagine illustrativa generata con AI.

Overview

Remote management delivers value only if someone uses the data it generates. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This contribution describes the typical architecture of a remote management system applied to remote management and smart city and the organisational conditions that determine its usefulness.

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.

Typical architecture

Three layers: nodes on board the luminaire that measure and actuate, a communication layer (wired, low-power radio or cellular) and a supervision platform. The choice of communication layer depends on point density, available coverage and acceptable recurring cost. Lumeitalia's Lume-Fi ecosystem sits on this architecture with documented protocols.

Which data is actually needed

A well-instrumented installation provides operating status, energy consumed, running hours, alarms and driver operating parameters. These are enough for predictive maintenance, profile verification and energy reporting. Collecting more data than can be analysed increases transmission and storage costs without producing better decisions.

The most immediate benefit in remote management and smart city is fewer inspections: automatic fault reporting replaces the inspection round and cuts the time between failure and restoration.

Conditions for a return

Three organisational elements are needed: a person receiving the alarms, a procedure defining what to do when they arrive, and a periodic data review to adjust profiles. Without these, remote management remains a recurring cost. The project should include staff training and definition of operating procedures from the outset.

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.
  • Decision-oriented dashboards: faults, consumption, intervention priorities.

Parameters to verify

  • Interoperability — DALI-2 / D4i — specification requirement
  • 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.

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.