Smart Controls

Louis Poulsen controls connect scenes, sensors and operating insight

Start with occupancy patterns and daylight availability, then define zones, interfaces and handover responsibilities. A connected lighting plan should make the intended experience repeatable without hiding commissioning complexity.

Technician commissioning connected architectural lighting

Control quality is experienced in transitions: a scene that fades cleanly, a sensor timeout that matches actual use, and daylight response that reduces power without making occupants notice the correction. Louis Poulsen organizes those outcomes around a documented sequence of operation rather than a list of connected devices.

Three layers of a controllable lighting system

Sense

Place occupancy and daylight sensors according to field of view, task zones and reflected daylight. Mounting position matters: an incorrectly aimed sensor can create false vacancy or unstable daylight response.

Connect

Coordinate drivers, gateways and supervisory systems around a defined protocol. DALI-2 supports addressed devices and diagnostics, while 0-10V uses a different wiring and control model; the labels are not interchangeable.

Commission

Record groups, scenes, fade times, minimum dim levels and override behavior. Functional testing should include normal use, after-hours response and recovery after power or network interruption.

A commissioning path with visible checkpoints

1. Capture the sequence of operation

Describe occupied, vacant, daylight and manual-override behavior before device addressing begins.

2. Verify electrical interfaces

Confirm driver compatibility, circuit topology, emergency behavior and any gateway boundaries against the approved submittal.

3. Address zones and scenes

Map each controlled load to room functions and document naming so facilities teams can understand the system after handover.

4. Tune sensor response

Test occupancy coverage, delay periods and daylight thresholds under representative conditions instead of relying on factory defaults.

5. Measure and hand over

Record final settings, operator access and energy baselines. Metered reductions depend on schedule, occupancy and pre-project load, so modeled savings must remain clearly labeled.

Evidence for a maintainable handover

Zone scheduleScene matrixSensor mapInterface recordFunctional test

Request a current device list, addressing backup, final sequence of operation and operator training record. For networked systems, document who owns credentials, firmware policy and fault notifications. Distributed control can improve local resilience, while centralized supervision can simplify portfolio-wide policy; the appropriate balance depends on IT governance, maintenance capability and the consequence of a single-point failure.

Request a controls readiness review

Bring the reflected ceiling plan, fixture schedule, protocol preference and operating narrative. We will identify interface questions before commissioning begins.

Plan the control scope