Lumeitalia

Life cycle and total cost of ownership in remote management and smart city installations

A long-term evaluation model for remote management and smart city investments: cost items, assumptions and sensitivity.

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

Overview

The cost of a lighting installation is spread over a long horizon, where the initial investment often weighs less than energy and maintenance combined. Remote management turns a lighting installation into a data infrastructure: it enables diagnostics, point-level dimming and energy reporting. This Centro Studi Lumeitalia white paper proposes an evaluation model applicable to remote management and smart city interventions.

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.

Model boundary

The model considers five items: initial investment (supply, installation, ancillary works), energy consumption over the period, planned maintenance, corrective maintenance and replacements, end-of-life management. Excluding an item is legitimate only if declared: a comparison ignoring maintenance systematically favours the least accessible solutions.

  • Investment — Supply, installation, ancillary works — Bid and bill of quantities
  • Energy — Operating power × hours × dimming profile — Datasheet and control design
  • Planned maintenance — Cycles, access equipment, times — Maintenance plan
  • Corrective and replacements — Expected failure rate and spares — Lifetime data and warranty
  • End of life — Disposal and material recovery — Applicable environmental requirements

Assumptions and sensitivity

Three assumptions dominate the outcome: energy price, operating hours and failure rate. The model should always be presented with a sensitivity analysis on these variables, showing how the result shifts under conservative and optimistic scenarios. A single figure with no range communicates a precision the model does not have.

For remote management and smart city, the cost component tied to luminaire accessibility must also be considered: two solutions with the same failure rate can have very different intervention costs.

Using the model in a decision

The model exists to make assumptions explicit, not to produce a definitive number. In a comparison, the spreadsheet with visible assumptions should be shared so each party can substitute its own values and test the robustness of the conclusion. That transparency is what makes the decision defensible before an audit body.

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.

  • Five cost items included, or exclusions declared
  • Real operating power used instead of nominal rating
  • Maintenance cycles and access equipment quantified
  • Sensitivity analysis on energy, hours and failure rate
  • Assumptions shared in an editable format
  • Time horizon consistent with declared service life

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.