Lumeitalia

Data governance in remote management for roundabout and pedestrian crossing lighting

Data ownership, interoperability and service continuity in a remotely managed roundabout and pedestrian crossing lighting installation.

Studio illuminotecnico con planimetria, ottiche e simulazione della luce
Studio illuminotecnico con planimetria, ottiche e simulazione della luce. 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. Roundabouts, junctions and crossings are conflict areas: their lighting must make the pedestrian recognisable before entering the vehicle path. This Centro Studi Lumeitalia analysis covers data governance in roundabout and pedestrian crossing lighting installations.

Applicable standards

The regulatory reference for roundabout and pedestrian crossing 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 — C classes for conflict areas.
  • UNI 11248 — identification of conflict zones.
  • CIE 115 — lighting for motorised and pedestrian traffic.

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 roundabout and pedestrian crossing 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 roundabout and pedestrian crossing lighting projects are not about product selection, but about defining requirements and verifying results.

  • Achieving positive pedestrian contrast against the background, not just average illuminance.
  • Avoiding glare for drivers entering the ring.
  • Coordinating dedicated lighting with the adjacent street installation.

Design approach

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

  • Dedicated crossing lighting with asymmetry aimed at the pedestrian.
  • Poles placed upstream of the crossing in the direction of travel.
  • Controlled level increase over the adjacent section, per C class.

Parameters to verify

  • C class — EN 13201-2 — illuminance requirements for conflict areas
  • Vertical illuminance — CIE 115 — makes the pedestrian recognisable
  • Pedestrian/background contrast — good practice — verified during calculation
  • Glare — EN 13201-2 — TI control and shielding

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 roundabout and pedestrian crossing 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

Is increasing lux on the crossing enough?+

No. Vertical illuminance on the pedestrian and contrast with the background matter: a brightly lit crossing with a backlit pedestrian is still unsafe.

Where should the dedicated pole go?+

Before the crossing in the direction of travel, so the pedestrian is lit from the side the approaching driver sees.

Where should a roundabout and pedestrian crossing 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.