Lumeitalia

Caricamento

Il caricamento sta impiegando più tempo del previsto.

Torna alla home

Lumeitalia

Technical scenario: new remote management and smart city installation

From requirement definition to commissioning of a new remote management and smart city installation, and the decisions that matter most.

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

Overview

In a new installation constraints are fewer and decisions weigh more: geometry, optics selection and control architecture are fixed once. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This methodological scenario reconstructs the typical design path of a new remote management and smart city installation.

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.

Defining requirements

The first decision concerns the performance level to be achieved and the standard it derives from. This is where both over-sizing — paid for over the whole installation life in energy and maintenance — and under-sizing, which surfaces at commissioning, are avoided. The requirement must be written with its reference condition: value, calculation surface or plane, and point in the installation life.

Geometry and optics selection

In a new installation geometry is a design variable, not a constraint: spacings, heights and aiming can be optimised together with the photometric distribution. Optics must be selected on real geometry, not on typical layouts. Generic distributions applied to particular geometries produce insufficient uniformity even when average values are met.

The approach that gives the best results in remote management and smart city combines specifications mandating open protocols and data portability and hybrid architectures with multiple communication technologies, assessing alternatives on annual consumption rather than installed power.

Control and commissioning

The control architecture must be decided at design stage, not added later: wiring, addressing and protocols affect conduits and switchboards. Choosing open protocols preserves freedom of action in later years and avoids being tied to a single supplier for every change.

Commissioning closes the path: agreed protocol, measurement points defined on plan, declared instrumentation, written tolerances. The same information is needed, years later, to check whether the installation is still within requirements.

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.