| LED luminaire and controls | Budgetary allowance: approximately $250–$900 per LED roadway luminaire and $40–$150 per control node, before installation. A central management platform may have a separate recurring fee. | Compare delivered luminaire output, input wattage, optical distribution, dimming support, warranty, and whether the price includes a control receptacle or node. | Compare total cost of ownership, not fixture price alone. Include installation, communications, software, energy, repairs, and replacement parts. |
| Installation and commissioning | For budgeting, allow approximately $150–$600 per existing pole for a straightforward luminaire retrofit. New poles, wiring, traffic management, or difficult access can raise costs substantially. | Confirm whether the scope includes lift equipment, electrical work, pole inspection, aiming, network setup, system testing, and disposal of old equipment. | Site surveys and commissioning reduce the risk of unplanned civil work, poorly aimed lights, and control-system outages. |
| Lighting design and road safety | Specify lighting performance by road classification and applicable design criteria; there is no single illuminance target suitable for every street. | Request a photometric layout showing maintained illuminance or luminance, uniformity, glare, light trespass, mounting height, spacing, and dimming levels. Review against the applicable edition of IES RP-8 and local requirements. | Good optical design can improve visibility while avoiding unnecessary energy use, glare, and spill light. Validate dimmed settings in the field. |
| Electrical and product safety | Use luminaires and components evaluated for the intended roadway application and local electrical code. | Check applicable product listings and requirements, such as UL 1598 for luminaires where relevant, and confirm electrical ratings, grounding, surge protection, and installation instructions. | Documented compliance and correct installation support safe operation and simplify inspection, insurance, and maintenance procedures. |
| Controls interoperability | A 7-pin control receptacle conforming to ANSI C136.41 can support dimming and control connections when matched with compatible equipment. | Verify the receptacle, control node, driver, communications protocol, and management software work together. Confirm data ownership, APIs, security updates, and export options. | Interoperability helps avoid dependence on a single control component and can make future upgrades or supplier changes easier. |
| Ingress protection and environment | Choose enclosure protection and materials for the actual exposure to rain, dust, salt, heat, cold, and vibration. | Check the stated IP rating under IEC 60529, operating-temperature range, corrosion protection, wind loading, and suitability for the local climate. | Appropriate environmental ratings reduce premature failures, especially in coastal, dusty, or extreme-temperature locations. |
| Energy and dimming strategy | Estimate energy use from measured input watts, annual operating hours, and the proposed dimming schedule. For example, 100 W operating for 4,000 hours uses 400 kWh per year before dimming. | Obtain a documented schedule, confirm safe minimum output, and check that photocells, clocks, sensors, and remote commands behave as intended. | Energy savings depend on the baseline fixture, operating hours, tariff, and actual dimming levels; use measured or commissioned settings in forecasts. |
| Service life and maintenance | Compare rated LED life using a defined lumen-maintenance metric, such as L70, rather than treating a rated-hour figure as a guaranteed fixture lifetime. | Review luminaire and driver warranties, replaceable components, spare-parts availability, maintenance access, and the control node’s separate warranty. | Plan for cleaning, inspections, driver or node replacement, software support, and failures over the project life—not only LED module aging. |
| Cybersecurity and data | Require documented access controls, secure communications, update procedures, and an incident-response process for connected equipment. | Ask how devices are authenticated, how vulnerabilities are handled, how long security updates are provided, and who can access operational data. | Clear security responsibilities reduce operational risk and help maintain the system through software and network changes. |
| Project evaluation | Compare options over a consistent study period, commonly 10–20 years for a planning analysis, using the same discount rate and energy-price assumptions. | Include capital cost, energy, maintenance, communications, software, replacements, and end-of-life costs. State assumptions and test energy-price and failure-rate scenarios. | A transparent lifecycle-cost model makes alternatives comparable and shows which assumptions have the greatest effect on payback. |