Lumeitalia

Data governance in remote management for urban street lighting

Data ownership, interoperability and service continuity in a remotely managed urban street lighting installation.

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

Overview

A remotely managed installation produces data for years: who owns it, in which format it can be exported and what happens at contract expiry are contractual questions before they are technical ones. The urban road network is the largest lit infrastructure managed by Italian municipalities and accounts for the biggest share of municipal energy spending. This Centro Studi Lumeitalia analysis covers data governance in urban street lighting installations.

Applicable standards

The regulatory reference for urban street lighting 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.

  • EN 13201-2 — performance requirements for M, C and P classes.
  • EN 13201-3 — calculation of performance.
  • UNI 11248 — road classification and selection of lighting classes.

Data ownership and portability

The contract must state that operating data belongs to the client and can be exported in an open, documented format, at a defined frequency and at no extra cost. Without this clause, changing operator means losing the history — the very basis for maintenance decisions.

In urban street lighting installations the history is especially valuable because it allows failures to be correlated with operating conditions and maintenance intervals to be revised on a statistical basis.

Interoperability and lock-in

Adopting standard protocols at luminaire level and documented interfaces at platform level reduces single-supplier lock-in. The specification should require documentation of the integration interfaces and the ability to replace the supervision layer while keeping the installed field devices.

Service continuity and security

The installation's behaviour when the network or platform is unavailable must be defined: lighting must keep operating on a predefined local profile. Access management, configuration change logging and a device update procedure with agreed windows must also be established.

Data collected by a public lighting installation is largely technical, yet the platform managing it still holds credentials and operational information: its handling must fall under the authority's security policies and not be left to the supplier's default configuration.

Recurring critical points

The difficulties that most often emerge in urban street lighting projects are not about product selection, but about defining requirements and verifying results.

  • Classifying the road correctly, avoiding oversizing that turns into wasted energy.
  • Achieving uniformity and glare control on pole spacings inherited from legacy installations.
  • Meeting regional light-pollution limits without reducing perceived safety.

Design approach

An orderly method drastically reduces variations during works and disputes at commissioning. Three choices make the difference from the earliest stages.

  • Risk analysis per UNI 11248 with adaptive lighting classes.
  • Optics designed for the real carriageway geometry instead of generic distributions.
  • Flux regulation by time band and traffic, with profiles set during commissioning.

Parameters to verify

  • Lighting class — UNI 11248 / EN 13201-2 — set by risk analysis, not by road width
  • Overall uniformity U0 — EN 13201-2 — minimum requirement per class
  • Threshold increment TI — EN 13201-2 — to be verified in the calculation
  • ULOR — regional laws — upward flux to be brought to zero

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.

  • Data ownership assigned to the client by contract
  • Export in an open, documented format at no cost
  • Standard protocols at luminaire level
  • Documented integration interfaces
  • Local operating profile when the network is unavailable
  • Access management, change logs and update windows

Key takeaways

A urban street lighting 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

Who decides the lighting class of a road?+

The designer, through the risk analysis required by UNI 11248, based on traffic, vulnerable users, visual complexity and accident rate.

Can light levels be reduced at night?+

Yes. UNI 11248 allows adaptive regulation when risk parameters change, provided the profile is documented in the design and verifiable at commissioning.

Where should a urban street lighting 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.