For professionals

Adaptive lighting you can put your signature on.

You are the one who has to defend the design class, the verification and the behaviour of the installation on the night something fails. This page is about those three things — not about energy percentages.

A two-lane road with LED luminaires and a pole carrying a weather station

Stretch under adaptive control — installed site

What the standard actually allows.

Adaptive operation is not a discount on the design. It is the rule that lets a road be lit for the traffic it is carrying now, as long as that traffic is measured and the reduction is bounded.

UNI 11248

TAI and FAI

Traffic-adaptive and full-adaptive installations, with the conditions each one has to satisfy and how much each may reduce.

EN 13201-2 / -4

Classes and verification

The luminance and uniformity requirements per class, and how the installation is verified once built.

CEN/TR 13201-1

Selecting the class

The parameters that put a road in a class in the first place — the starting point of every adaptive design.

What you specify

Six clauses that decide whether an adaptive tender is real.

Written this way, they are open to any supplier who can actually do it — and closed to a dimming calendar dressed up as adaptive lighting.

01The quantity that drives the reduction must be measured on the stretch — traffic flow, and road luminance for full adaptive — not inferred from a calendar or from online data.
02The maximum reduction is stated in classes, not in percentages of power, and is bounded by the standard.
03Reaction time — the system must return to the design class within a declared time when conditions change; green procurement criteria commonly ask for under a minute.
04Fail-safe — on sensor, network or node failure the installation returns to the design class. Written explicitly, this single clause removes most of the market.
05Weather — reduction suspended in fog and reduced visibility, with the measurement that triggered it recorded.
06Traceability — every applied class stored with the measurement that justified it, exportable for inspection.
Get these as drop-in clauses →
Where designers get caught

A specification that says "adaptive dimming up to 70 %" without naming the measured quantity will be answered by a timer profile, and you will be the one explaining to the client why the road is under-lit at 23:00 on a Friday. Percentages belong in the business case, classes belong in the specification.

Dependent side roads

Where a side road takes its class from the main road it joins, the reduction has to propagate consistently. We handle this as a design question — which stretches are dependent on which — before it becomes a configuration.

What it costs the design

A few devices per stretch — a traffic counter, a luminance unit for full adaptive, a weather station — plus a node per luminaire. Not one sensor per pole, which is the assumption that makes most adaptive proposals unaffordable.

What we bring to a design

We work on your drawing, not on ours.

Bring the stretches, the classes and the luminaires you have chosen. We say what adaptive operation is worth there, where sensors go, and where it is not worth doing at all.

Class profile

Which classes the standard allows on each stretch, given its traffic profile through the night.

Sensor layout

Where counting and luminance measurement go, and how many stretches can share them.

Network plan

Gateways, clusters and backhaul, from the pole layout you already have.

Clause review

We will read your draft specification and flag the lines that accidentally exclude everyone but one supplier — including us.

Send the stretches and the classes.

Lengths, design classes, luminaire models and a traffic count if you have one. You get back a class profile and an honest view of where the saving comes from.

Talk to an engineer