| Road-lighting safety | Confirm the luminaire is tested for the applicable road and outdoor-lighting requirements in the installation market. | Ask for test documentation covering IEC 60598-1 and, where applicable, IEC 60598-2-3 for luminaires used in road and street lighting. | These standards address luminaire safety and application-specific requirements. The exact applicable edition and local regulations should be verified for the project. |
| Ingress and impact protection | Check dust and water protection for the complete assembled luminaire, plus impact resistance where required. | Look for an IP rating classified under IEC 60529 and an IK rating classified under IEC 62262. Select ratings based on site exposure and the authority’s specification. | IP and IK ratings describe different properties: ingress protection and resistance to mechanical impact. They are not interchangeable. |
| Control interface | Verify the physical connector, pin arrangement, control method, and supported dimming functions. | ANSI C136.41 defines a standardized interface for roadway and area-lighting control devices. Confirm the luminaire and controller use compatible receptacles, contacts, and functions. | A matching connector does not by itself guarantee that every control feature or software function will work. |
| Sensor and node interchangeability | Check whether the luminaire accepts the intended sensing or communication module and whether the mechanical and electrical interfaces match. | For systems using the Zhaga interface, verify the relevant Zhaga Book 18 requirements and confirm that the specific luminaire and module have been tested together. | A standardized interface can support interchangeability, but it does not automatically ensure end-to-end network or application compatibility. |
| Lighting-control protocol | Identify the control protocol, device roles, dimming behavior, and whether the system is wired, wireless, or hybrid. | For DALI-based control, check the applicable IEC 62386 parts and verify product-level interoperability evidence. Confirm that gateways and management software support the same functions. | Protocol support can vary by device and feature. Confirm commissioning, group control, scheduling, status reporting, and fault monitoring in the actual system. |
| Cybersecurity baseline | Ask how devices are protected during onboarding, operation, maintenance, and decommissioning. | Look for documented device capabilities aligned with the NISTIR 8259A IoT device cybersecurity baseline, such as unique identification, secure configuration, data protection, access control, and secure software updates. | A published security process helps buyers assess device-level safeguards and maintenance responsibilities over the product’s service life. |
| Network and system security | Review network segmentation, authentication, encryption, logging, vulnerability handling, and update procedures. | Request a security architecture and update policy. Where relevant to the control environment, assess the system against applicable IEC 62443 requirements and the owner’s cybersecurity policies. | Street-light networks may connect to wider operational or municipal systems. Security depends on devices, gateways, networks, software, and operating practices. |
| Interoperability and data access | Check integration with the existing management platform, asset database, and maintenance workflow. | Require a written interface list, documented APIs or supported data exports, a test plan, and a demonstration of device discovery, alarms, energy data, and control commands. | Clear interfaces and data ownership terms reduce integration effort and help avoid dependence on undocumented system behavior. |
| Operational fit and lifecycle | Assess dimming schedules, power measurement, fault reporting, replacement parts, warranties, and long-term software support. | Compare documented operating temperatures, electrical ratings, expected maintenance arrangements, spare-part availability, and the duration of security and firmware support. | Lifecycle planning affects service continuity, maintenance costs, and the ability to keep the system secure after installation. |
| Procurement verification | Validate claims against project requirements and local rules before purchase or deployment. | Recommended Request certificates or test reports, compatibility matrices, cybersecurity documentation, and a pilot using the intended network and management platform. | Independent evidence and a realistic pilot help identify compliance gaps and integration issues before large-scale rollout. |