A Datasheet Cannot Prove a Road Will Be Lit Correctly
A product datasheet describes what a luminaire can produce under controlled test conditions: nominal wattage, lumen output, efficacy, CCT, and sometimes a photometric file. It does not describe the light level at the middle of a roadway, the darkest point between two poles, or the glare seen by an approaching driver.
Those are layout questions. Road lighting is a geometric system in which the luminaire's distribution interacts with road width, pole height, setback, outreach, spacing, arrangement, tilt, surface reflectance, and maintenance assumptions. DIALux lighting design converts those variables into a performance check against the project's required lighting class or illuminance target.
That makes the simulation an engineering control, not a decorative image attached to a quotation. The most important benefit of a no-fee design is timing: an optic, mounting height, or pole spacing can be changed in a model before equipment is manufactured. Once foundations, cables, and luminaires are installed, the same correction becomes a construction claim.
The Same Luminaire Can Pass and Fail
Consider an illustrative two-lane road with an 8-meter carriageway, 10-meter mounting height, single-side poles, and a 150 W luminaire using the same asymmetric optic in both tests. Assume the project requires 15 lux average illuminance and an overall uniformity U₀ of at least 0.40.
- At 35-meter spacing, a hypothetical model might return 17 lux average, 7.1 lux minimum, and U₀ = 0.42. It passes those two assumed criteria.
- At 50-meter spacing, the same model might return 14 lux average, 2.8 lux minimum, and U₀ = 0.20. It fails both, even though the product, wattage, and pole height have not changed.
The numbers are illustrative, but the engineering relationship is not. Spacing changes the distance and angle from each luminaire to every calculation point. A datasheet cannot reveal that behavior by itself.
Increasing wattage is not a universal fix. If the 50-meter layout is simply scaled from 150 W to 200 W with the same optical distribution, the average may rise to roughly 18.7 lux and the minimum to roughly 3.7 lux in a proportional example, while uniformity remains close to 0.20. More light raises the bright areas and the dark areas together; it does not necessarily fill the gap between poles. A different optic, shorter spacing, greater mounting height, or a different arrangement may be required. The correct choice comes from the modeled geometry, not from selecting the next higher wattage on a product list.
Average Illuminance Is Only Half the Answer
An average is an arithmetic summary. It can look acceptable while the road contains uncomfortable or unsafe transitions between bright patches and dark gaps. The ratio that exposes that problem is commonly expressed as U₀ = Emin / Eavg.
At the same 20 lux average:
- U₀ = 0.20 means the minimum point is only 4 lux.
- U₀ = 0.50 means the minimum point is 10 lux.
Depending on the project target, the second layout may provide much better continuity of illumination even though both layouts have the same average. A high-wattage product can make the first layout appear impressive while leaving its uniformity ratio largely unchanged.
A credible DIALux report should therefore show more than a colored false-color plan. It should include:
- The target class or maintained illuminance requirement used for the calculation.
- Average and minimum illuminance.
- Overall uniformity and any longitudinal or transverse uniformity required by the governing standard.
- Glare results where the project standard calls for them.
- The calculation grid and assumptions, so the result can be reproduced and reviewed.
The minimum value is particularly sensitive to pole spacing and the calculation grid. If the grid is too coarse or the model omits the relevant road edges, a report can create an impression of compliance without testing the places most likely to fail.
DIALux itself is not a compliance certificate. It is a calculation tool. Its output is only as defensible as the target, geometry, photometric data, surface assumptions, and maintenance factor entered into it.
Maintained Performance Must Be Modeled Before Purchase
A new luminaire and a maintained installation are not the same design condition. LEDs lose output over time, optics accumulate contamination, and solar systems operate under changing battery and environmental conditions. If the contract requires maintained illuminance, the calculation should apply the specified maintenance factor rather than presenting initial output as the long-term result.
For example, a layout that produces 20 lux initially with a maintenance factor of 0.80 yields 16 lux on the maintained basis. That may pass a 15-lux requirement with some margin, but it would fail an 18-lux requirement. The result changes without any change to the pole or luminaire because the question has changed from how bright it is on day one to what performance the project can depend on.
This distinction matters in procurement language. A supplier can quote impressive initial lumens while the project acceptance test is based on a maintained value. The design file, quotation, and acceptance criteria should use the same basis. Otherwise, the disagreement appears after installation, when each party can point to a different number and claim that it was correct.
The Photometric File Is Part of the Specification
A DIALux result is tied to the exact light distribution used in the model. A 150 W street light from one manufacturer is not automatically equivalent to every other 150 W street light. Two luminaires with the same wattage and total lumens can send very different proportions of light down the road, across the road, or into adjacent property.
A buildable specification should preserve the assumptions that made the layout pass:
- Luminaire model and photometric file revision.
- Wattage, drive current, optical distribution, and tilt.
- Pole height, arm or outreach, setback, and installation arrangement.
- Pole positions and approved spacing.
- Road geometry, surface assumptions, calculation grid, and maintenance factor.
- Required illuminance, uniformity, and glare criteria.
- Dimming or operating profile when the project uses controls.
Changing the optic after approval is not a harmless substitution. Changing the mounting height is not merely a civil detail. Moving a pole to avoid a tree, driveway, or utility can create a new photometric problem. Each change can alter the evidence on which the specification was accepted and should trigger a revised calculation.
For solar lighting, the same connection extends to energy sizing. At full output, a 150 W luminaire operating for 12 hours uses 1.8 kWh per night before controller, battery, and driver losses. A 200 W version uses 2.4 kWh, a one-third increase. Dimming can reduce the actual energy requirement, but only if the operating profile is included in the design. The photometric choice therefore affects both whether the road meets its lighting target and how much panel and battery capacity the system needs.
Early Simulation Protects the Project From Expensive Corrections
The cost of correcting a design grows sharply as the project moves from calculation to concrete.
At the design stage, an engineer can test a narrower optic, a different spacing, a higher pole, or a staggered arrangement without touching the site. During procurement, a correction may require a revised bill of materials, a different luminaire, or a changed solar configuration. After installation, it can involve replacement equipment, new foundations, cable changes, lifting equipment, traffic control, and a second acceptance test.
A simple route example shows the scale. A 5-kilometer road at nominal 50-meter spacing requires roughly 100 single-side pole positions, ignoring end conditions. At 40-meter spacing, it requires roughly 125. If inadequate uniformity is discovered after the foundations are poured, the difference is not a line on a drawing; it can mean about 25 additional foundations, luminaires, cable runs, and installation operations.
The opposite error is also costly. Over-lighting a road to compensate for an untested layout can increase glare, power consumption, and equipment size without solving the distribution problem. In a solar project, that may mean larger panels and batteries. In a grid-connected project, it may mean higher operating cost and an installation that exceeds the intended lighting class.
The value of free DIALux design is therefore not the absence of an invoice alone. It is the ability to test the project assumptions before an incorrect assumption is embedded in manufactured equipment. A supplier that is willing to show a configuration that fails, explain why it fails, and revise it has provided more useful engineering than one that only supplies a favorable rendering.
A Practical Standard for Evaluating a Free Design
A no-fee simulation is worth using when it answers the same question the project owner, consultant, or authority will ask at handover: does this exact installation meet the specified performance?
The deliverable should make the answer auditable:
- Inputs are visible. Road width, lanes, pole arrangement, mounting height, setback, spacing, and obstructions are identified.
- The target is explicit. The applicable lighting class or illuminance and uniformity thresholds are stated, along with whether they are initial or maintained values.
- The product is exact. The model, optic, wattage, tilt, and photometric file are named rather than represented by a generic product family.
- The outputs are complete. Average, minimum, uniformity, and relevant glare results are reported, not just a bright-colored layout.
- Failures are visible. If the first arrangement misses the target, the revision identifies what changed: spacing, optic, height, power, or arrangement.
- The specification can be carried forward. The approved calculation can be matched to the quotation, production configuration, installation drawings, and commissioning checks.
A design that only reports lumens per watt has not answered the layout question. A design that reports an average without a minimum has not shown continuity. A design that uses one photometric file and ships another has not preserved the basis of compliance.
The Real Deliverable Is a Defensible Decision
The strongest reason to request DIALux lighting design before ordering is that it changes the procurement question. Instead of asking whether a luminaire sounds powerful enough, the project team can ask whether a defined product, at a defined height and spacing, produces the required maintained performance on the actual road.
That shift reduces ambiguity between the consultant, supplier, installer, and maintaining contractor. It also makes alternatives comparable: two products can be judged by the same layout, target, maintenance assumptions, and output metrics rather than by headline wattage or lumen claims.
When a supplier carries those validated assumptions into specification and commissioning, Mast Lighting's full project support closes the gap between a calculation and a built installation. The design has done its job when it prevents a specification that looked reasonable on paper from becoming a failed road in the field.