Outdoor lighting design starts with the site
A road-lighting purchase is often reduced to one number: LED wattage. That shortcut misses the actual engineering problem. Lighting performance comes from the interaction of the luminaire, optic, mounting height, spacing, road geometry, pole, power system, climate, and maintenance plan.
A 100 W luminaire installed at 7 m over a narrow residential street is not doing the same job as a 100 W luminaire installed at 10 m over a broad arterial. The electrical label is identical; the throw distance, illuminated footprint, glare exposure, overlap, and energy demand are not.
A useful application-based lighting solution begins with those site variables and selects the fixture after the performance target is clear. That order matters because a catalog can show which products exist, but only a project design can show whether a product works at the proposed location.
Wattage is an input, not proof of performance
LED wattage describes electrical consumption. It does not describe where the light lands. Two luminaires with the same wattage can have different lumen outputs, beam distributions, optical efficiencies, and glare characteristics. Mounting height, tilt, pole spacing, pavement reflectance, and maintenance factor can change the result just as much as the nominal power rating.
The application ranges illustrate the difference in scale. Residential streets often begin with 60 W–150 W luminaires on 6 m–8 m poles, while urban arterials may begin around 200 W–320 W on 10 m–12 m poles. These are starting points, not universal prescriptions. The correct value depends on the road class, geometry, optic, and governing standard.
Consider two preliminary layouts using the same 120 W roadway luminaire:
- An 8 m road with 7 m poles and 25 m spacing.
- A 12 m road with 10 m poles and 35 m spacing.
The second layout asks the optic to cover more area from a higher mounting point and over longer intervals. It may require a different distribution, spacing, tilt, or output. Simply increasing the wattage can raise average illuminance while leaving poor uniformity or adding unwanted glare. The simulation has to identify which variable is actually limiting performance.
A proposal that lists only fixture wattage leaves the most important questions unanswered:
- Is the light reaching the edges of the road?
- Are the gaps between poles adequately illuminated?
- Is the optic appropriate for the mounting height?
- Does the layout meet the required lighting class?
- Is the energy use justified by the operating schedule?
DIALux turns a sales claim into a testable design
A proper DIALux model uses the luminaire’s photometric data and the project’s actual geometry, not a wattage estimate. The model should include road or area dimensions, pole height, spacing, mounting arrangement, tilt, maintenance assumptions, and the lighting class stated in the tender or local standard.
The resulting report should make at least three performance measures visible:
- Average illuminance across the relevant calculation area.
- Uniformity ratio, including the relationship between minimum and average illuminance.
- The applicable glare result or glare evaluation.
Average illuminance alone can hide a serious design difference. Suppose two layouts both produce an average of 15 lux. In one layout, the minimum point may be 6 lux, producing a minimum-to-average ratio of 0.40. In another, the minimum may be 10.5 lux, producing a ratio of 0.70. The averages are identical, but the second layout distributes light far more evenly. The threshold that applies depends on the governing standard, yet the comparison shows why average lux cannot stand in for complete photometric performance.
DIALux also gives the project team a way to test alternatives before production. A designer can compare a narrower roadway optic with a wider optic, change pole spacing, adjust mounting height, or evaluate a lower-power fixture with better distribution. Those changes are cheaper and safer on a computer model than after foundations have been poured and poles installed.
A free design is useful only when its assumptions are visible. A polished report based on an unknown road width or a generic pole spacing may look precise without representing the actual project. A decision-grade simulation identifies the input geometry, luminaire, calculation area, maintenance factor, and standard used for evaluation.
Solar lighting turns photometric design into energy reliability
Off-grid lighting adds a second performance test. The luminaire must provide the required light at night, while the photovoltaic module, battery, controller, and operating schedule must keep it running through poor weather. A high-output fixture paired with undersized storage is not a reliable lighting system.
A simple load calculation shows the relationship. Assume a 100 W luminaire runs at full output for 12 hours each night:
100 W × 12 hours = 1.2 kWh per night.
Five consecutive rainy nights would require 6.0 kWh delivered to the lighting load before accounting for controller and wiring losses. If only 80% of a battery’s nominal energy is treated as usable, the simplified nominal requirement becomes 7.5 kWh before additional allowance for conversion losses, temperature effects, aging, and reserve capacity.
Actual projects may use adaptive dimming, which reduces consumption during low-traffic hours. That can lower the battery and photovoltaic requirements, but the schedule must be included in the calculation. A battery sized for a 30 W average overnight load is not equivalent to one sized for a 120 W fixture operating at full power for the same number of hours.
Standard solar configurations can be designed for 3 to 7 consecutive rainy days of autonomy. The number has meaning only when tied to the local climate, load profile, and recovery conditions. A monsoon project may need more storage, a larger photovoltaic array, or a carefully controlled dimming schedule. Increasing the battery alone does not solve the problem if the array cannot restore the energy after the cloudy period.
LiFePO4 batteries commonly carry a service expectation of roughly 5 to 8 years, while a complete solar street light may have a 3-year warranty. Those figures answer different questions. Service life concerns expected operation; warranty concerns the supplier’s defined coverage. The design should also account for battery access, replacement logistics, enclosure protection, and controller compatibility.
The pole and local climate change the lighting result
Photometric calculations assume that the luminaire remains at the designed height and angle. The pole is therefore part of the optical system, not merely a support purchased after the fixture has been chosen. Excessive deflection, an unsuitable arm, or a weak connection can change the aiming angle and alter the illuminated pattern.
Wind conditions affect both conventional and solar lighting. A solar pole carries the projected area of the luminaire, photovoltaic module, bracket, and sometimes battery housing. The structural design may need different wall thickness, foundation dimensions, anchor arrangements, or material specifications for a high-wind zone. A coastal or industrial location may also require closer attention to galvanizing, coatings, fasteners, and inspection of corrosion-prone interfaces.
Other environmental inputs have direct design consequences:
- Temperature: Battery capacity, charging behavior, and component ratings can change across the site’s temperature band.
- Rain and cloud cover: Consecutive overcast days affect both autonomy and the time required for photovoltaic recovery.
- Soil conditions: Foundation design depends on the ground, not just the pole height.
- Mounting scale: A 6 m–8 m residential pole, a 10 m–12 m arterial pole, and a 20 m–60 m high mast impose very different structural and maintenance requirements.
- Corrosion exposure: Marine air, road salt, and industrial pollutants can shorten the life of exposed connections if protection is not specified.
A standard galvanized pole may be suitable for one project and inadequate for another with a different wind zone or foundation condition. The same principle applies to high-mast systems: the mast, head cluster, foundation, access method, and aiming arrangement must be considered together.
Integration closes responsibility gaps
System-level design also changes procurement risk. An integrated manufacturer that handles research and development, production, engineering, and export can coordinate the luminaire, pole, photovoltaic module, LiFePO4 battery, controller, and mounting hardware as one configuration. The practical benefit is not simply one invoice. It is one set of technical assumptions.
With several disconnected suppliers, each item can satisfy its own data sheet while the installed system fails to meet the project requirement. A common chain of errors looks like this:
- The luminaire is tested at an 8 m mounting height.
- The pole supplier provides a 10 m pole with a different arm geometry.
- The solar supplier sizes the battery from rated wattage without using the actual dimming schedule.
- The installer changes spacing to avoid utilities without requesting a revised simulation.
No individual component is necessarily defective, but the finished road no longer matches the original design. Responsibility becomes difficult to assign because no party owns the interaction between optics, structure, energy, and installation.
Integration is valuable only when it produces verifiable evidence. A serious project package should include:
- A project-specific DIALux report using the proposed luminaire and geometry.
- A battery autonomy calculation tied to the operating schedule and weather assumption.
- A photovoltaic sizing basis that explains daily energy production and recovery after cloudy periods.
- A structural basis for pole height, wind load, projected area, foundation, and mounting interfaces.
- Component drawings, inspection records, commissioning guidance, and a defined support path.
One supplier is not automatically better than several suppliers. The advantage appears when one engineering team is accountable for the complete configuration and can revise the design when a site variable changes.
Specify the system before comparing prices
The strongest project brief starts with information rather than a requested wattage. At minimum, it should provide:
- Application geometry: Road or area dimensions, number of lanes, pole position, mounting height under consideration, and proposed spacing.
- Performance target: Lighting class, applicable standard, required illuminance, uniformity, glare criteria, and maintenance assumptions.
- Energy profile: Nightly operating hours, dimming schedule, autonomy requirement, photovoltaic conditions, and local temperature range.
- Structural and environmental conditions: Wind zone, soil information, corrosion exposure, rainfall pattern, and access requirements.
- Verification and handoff: DIALux results, configuration drawings, inspection documentation, installation guidance, and commissioning responsibility.
A credible proposal should return a complete configuration rather than a single wattage: luminaire and optic, pole and mounting arrangement, photovoltaic module, battery, controller, operating schedule, structural basis, and photometric evidence.
The better buying question is not whether a 120 W fixture is cheaper than a 150 W fixture. It is whether the complete configuration produces the required light, withstands local conditions, maintains energy through the expected weather cycle, and remains serviceable over time. Once that standard is applied, wattage becomes a design result rather than a sales headline.