How to Calculate the Cost of DALI Lighting Control: A Seven-Step Build-Up You Can Run Before Quoting

What “calculating the cost” of DALI control actually involves

A DALI controls estimate is not a product price multiplied by a fixture count. It is a build-up in which hardware quantities are derived from a design decision — zones, addresses, subnets and control functions — and then a labour build-up is added for commissioning. Get the quantities wrong and no amount of unit-price negotiation rescues the budget. This article gives a step-by-step calculation method you can run on a spreadsheet before you request quotes, so that the quotes you receive can be compared line by line instead of in total.

Inputs in the worked example are explicitly illustrative. Where a number comes from a published source, the source is named and the date of access is stated.

Step 0: Fix the scope boundary first

Decide, in writing, what the estimate covers. The method below covers:

• DALI-2 control gear (LED drivers with integrated DALI interface) — one per addressable luminaire or group;
• input devices: occupancy sensors, daylight sensors, scene plates, multifunction push-buttons;
• bus power supplies and bus cable;
• application controllers, gateways or network interfaces;
• commissioning, addressing, scene programming, integration and handover documentation.

Excluded from this method: luminaires, optics, mains distribution, ceiling and containment works, energy consumption, and ongoing service contracts. If an emergency-lighting layer is required, add it as a separate sub-model (see Step 6).

Step 1: Count addressable control gear, not fixtures

Start from the lighting layout and mark every luminaire that needs independent control. Then classify each by wattage and colour capability. This matters because DALI-2 driver pricing is strongly tiered: public price surveys for DALI-2 LED drivers group compact 10–40 W single-colour DT6 units in the tens of dollars, mid-power tunable-white or 50–100 W DT8 units several times higher, and high-capacity or multi-channel industrial gear in the low hundreds of dollars per unit (trade price surveys, accessed November 2026).

Build a small matrix: rows for wattage bands and colour capability, columns for quantity. That matrix is your driver cost line.

Step 2: Derive subnet count from the electrical rules

Subnets drive bus power supplies, cable and commissioning groups. The limits come from the standard rather than from vendor preference: under IEC 62386-101 the bus supports a maximum of about 300 m of cable between the furthest devices on 1.5 mm² conductor, with shorter limits for smaller cross-sections (in the region of 100 m at 0.5 mm² and 150 m at 0.75 mm²); a bus power supply provides roughly 16 V and up to 250 mA per subnet; and one subnet supports up to 64 control gear plus 64 control devices. Devices are commonly cited as drawing around 2 mA each.

Formula:

Subnets = MAX( CEIL(control gear ÷ 64), CEIL(control + input devices cross-check against 250 mA ÷ device current), CEIL(longest cable run ÷ 300 m) )

Take the largest of the three results. Then round up once more for practical spare capacity if the brief requires headroom — and price that headroom consciously rather than discovering it later.

Step 3: Price the input-device layer by zone

Input devices are cheap individually and expensive collectively. Count them per zone: presence detection per enclosed room, daylight sensing per perimeter façade bay, a plate per control point. In DALI-2, input devices can themselves be certified, individually addressed products, which means they appear in both the hardware list and the commissioning address count.

Deliberately define the zone plan here. Every zone redefined after commissioning is a second bill.

Step 4: Choose the controller tier, then price its licence terms

Controllers range from a simple gateway that presents a local interface to a site-wide lighting management platform. The hardware price is the visible cost; the licence and hosting terms are the one that recurs. Ask for the licence model (perpetual, subscription, per-seat, per-site), what happens when the site exceeds its device count, and which features are enabled in the base tier.

If the brief requires energy or asset reporting from the driver level — DALI Part 252 for energy and power reporting, Part 251 for luminaire and asset data, Part 253 for diagnostics — confirm that the controller supports those data parts, because a controller that cannot read them makes the data-capable drivers a cost with no output.

Step 5: Build the commissioning labour model

Commissioning is labour with a countable shape. Use a driver-based estimate rather than a square-metre rate:

Commissioning hours = (addresses × h_address) + (scenes × h_scene) + (integration points × h_integration) + (documentation, fixed)

Where h_address, h_scene and h_integration are your own productivity assumptions from comparable projects. Retrofit projects need an additional discovery allowance when the existing address map is unknown. Then apply a labour rate, and treat the result as the second-largest line in the estimate — in most DALI budgets it is.

Step 6: Add the regulatory and emergency layer

Two additive sub-models:

• Emergency lighting: emergency-capable drivers or conversion modules, plus automated test and reporting, plus a scheduled verification regime that must be documented.
• Energy-code compliance: automatic shut-off, dimming, or demand-response capability, each of which raises the controller tier required.

Both should be priced as separate lines so a bidder cannot quietly include or exclude them.

Step 7: Apply sensitivities and a contingency

Run at least three scenario cases on the finished model:

1. Driver price movement: trade reporting in 2026 recorded several LED driver suppliers announcing increases in the 5–15% range on selected products; model a 10% and a 15% driver-line increase as separate cases. Note this is supplier announcement reporting, not a published index.
2. Scope change: add a fourth colour channel for 25% of gear, or add a second subnet, and see what the total does.
3. Commissioning overrun: test the total with commissioning hours 30% above your base assumption.

Contingency should follow the sensitivity result rather than a habit. A project where commissioning dominates carries a different risk profile from one dominated by driver count.

Worked example: 120-luminaire clinic fit-out (illustrative inputs)

Assumptions: 120 addressable luminaires, all 20 W single-colour DT6; 40 input devices; longest run 210 m; 2 subnets required for spare capacity; 25 scenes; one BMS integration point. All unit costs invented for arithmetic.

The calculation here is broken down as: 96 commissioning hours built from 160 addresses × 0.35 h, plus 25 scenes × 0.8 h, plus one integration point × 8 h, plus 8 h documentation. Change any of those productivity assumptions and the total moves more than a driver discount would.

Common calculation errors

• Counting fixtures instead of addresses. Ganged luminaires on one driver collapse the count; individually addressable ones inflate it.
• Forgetting the 64 + 64 ceiling. A 70-driver area is two subnets even if the cable run is short.
• Pricing hardware but not licences. The recurring controller line is often omitted from capital estimates entirely.
• Assuming commissioning from area. Hours scale with addresses, scenes and integration points.
• Comparing totals instead of lines. Require every bidder to submit the same seven-line breakdown.

Lifecycle note

Keep the model after handover. The same spreadsheet that priced the installation becomes the asset register: address map, driver part numbers, zone plan and licence expiry. Because DALI-2 certification is verified against a public product database (DALI Alliance, accessed 11 November 2026), a replacement driver can be checked for compatibility before purchase, which is where most retrofit surprises begin.

Sources and date

• DALI Alliance, DALI data specifications overview (Part 251 luminaire data, Part 252 energy and power reporting, Part 253 diagnostics): https://www.dali-alliance.org/data/ (accessed 11 November 2026).
• IEC 62386-101 installation and electrical requirements as summarised in industry technical material: ~300 m bus at 1.5 mm², shorter at smaller cross-sections, ~16 V bus, up to 250 mA per subnet, 64 control gear plus 64 control devices per subnet (accessed 11 November 2026).
• Public DALI-2 LED driver price surveys by wattage and channel type, accessed 11 November 2026 — used to establish relative price tiers only.
• 2026 trade reporting of LED driver supplier price increases in the 5–15% range, accessed 11 November 2026 — supplier announcements as reported, not a published price index.

Membership, certification and standard details are as published by the named bodies. All project-level quantities and unit costs in the worked example are illustrative model inputs for demonstrating the calculation method, not quoted prices.