Networked Lighting Controls Technical Requirements V2.0
Scope of Technical Requirements
These are requirements for Interior and Exterior Networked Lighting Control (NLC) systems associated with commercial and industrial buildings, roadways, and exterior environments. NLC systems are defined for the purposes of these requirements as the combination of sensors, network interfaces, and controllers that effect lighting changes to luminaires, but does not include the luminaires themselves. Any luminaire-specific control requirements are addressed separately by the DLC’s Solid-State Lighting Technical Requirements and Qualified Products List.
Please note that NLCs intended for DC (Direct Current) and PoE (Power over Ethernet) luminaires are excluded from the requirements while a corresponding Policy to qualify DC and PoE luminaires for DLC’s SSL QPL is developed. A future revision of this Technical Requirements document will be modified to accept DC and PoE NLCs in conjunction with the SSL Luminaire DC and PoE Policy.
Definition of “Required” vs. “Reported” Capabilities
The Technical Requirements are built upon “Required” and “Reported” system capabilities.
Required Capabilities shall be available in all systems to be listed on the QPL. Systems that do not offer these capabilities are not eligible to be listed. A successful application will provide information on the availability of these capabilities and characteristics. Key information provided by the manufacturer will be published on the QPL.
Note: While the DLC requires systems to offer a particular capability, the DLC does not specify whether a capability must be installed on a project. For instance, while DLC requires systems to have daylight harvesting / photocell capability, the DLC does not specify which rooms or luminaires on a project must be installed with daylight harvesting / photocell capability. Project-specific requirements for rebates and incentives are determined by individual efficiency programs. DLC intends to develop best-practice guidelines that individual utilities may adopt, in whole or in part, to guide installation of capabilities on a project. These guidelines will be developed in late 2017 separately from this Technical Requirements document with input from DLC stakeholders.
DLC will report on the presence or absence of, type, and/or characteristics of each Reported capability for qualified systems. While systems are not required to include these capabilities, a successful application will provide information on the presence or absence of these capabilities and their characteristics. Key information provided by the manufacturer will be published on the QPL.
- Warranty: DLC requires a minimum warranty of at least 5 years for all components of the system addressed by the requirements, with the exception of software, on-premises computer server, and cloud service. An optional warranty extension to 5 years is acceptable in meeting this requirement, however the QPL will identify that an extended warranty must be purchased to meet the requirements.
- Commercial Availability and Verification: All systems must be fully commercially available, able to be purchased, with complete, final documentation and literature readily available on the manufacturer’s website before they can be listed. DLC requires that a qualified system has been installed and operated successfully in at least one actual field installation. DLC will verify this through a case study and/or a customer reference. See the Application Form for more information.
- System Overview Presentation: As part of the Application Review Process, the DLC requires a system overview to be presented via webinar or in-person to the DLC. See the Application Form for more information.
All specification documents, including the Application Form, Instructions, and supporting documentation can be found on the DLC website here.
Annual Revisions and Grace PeriodThe DLC revises the Networked Lighting Controls Technical Requirements annually, with final revisions completed on June 1 of each year. Each manufacturer must requalify and relist a system each year with the annual Technical Requirements revision schedule.
Grace Period Policy: A twelve month listing grace period will be provided for systems that have been qualified under a previous version of the Technical Requirements, but do not meet revised requirements. These systems can be requalified and listed under the previous version of the Technical Requirements. This will allow a period of one year to develop an updated or new system that can be submitted for evaluation according to the most current Technical Requirements.
Table 1 – Interior Lighting SystemsTable 1 provides a Summary of “Required” and “Reported” System Capabilities for Interior Lighting Systems.
'Required' Interior System Capabilities
'Reported' Interior System Capabilities
Table 2 – Exterior Lighting Systems
Table 2 provides a Summary of “Required” and “Reported” System Capabilities for Exterior Lighting Systems.
'Required' Exterior System Capabilities
'Reported' Exterior System Capabilities
Table 3: Capability and Requirement Definitions
Table 3 provides the detailed definitions for each Capability or Technical Requirement. This Table applies to both Interior and Exterior, except where noted. Please note that the Application Form specifies in more detail what information the DLC requires from manufacturers for each capability and what information will be published on the QPL.
|1||Networking of Luminaires and Devices||The capability of individual luminaires and control devices to exchange digital data with other luminaires and controls devices on the system. This capability is required at the room, space, or area level, but not at the whole building level or beyond (e.g. non-lighting systems, or the internet).|
|2||Occupancy Sensing||The capability to affect the operation of lighting equipment based upon detecting the presence or absence of people in a space or exterior environment.
Exterior systems must include either Occupancy Sensing or Traffic Sensing. They may include both, but that is not required.
|3||Traffic Sensing||The capability to affect the operation of lighting or other equipment based upon detecting the presence or absence of moving vehicles in an area.
Systems may satisfy this requirement through External Systems Integration as described below in lieu of in-system sensors if another source of data is used for presence or absence detection.
Exterior systems must include either Occupancy Sensing or Traffic Sensing. They may include both, but that is not required.
|4||Daylight Harvesting / Photocell Control||The capability to automatically affect the operation of lighting or other equipment based on the amount of daylight and/or ambient light that is present in a space, area, or exterior environment. This capability is typically called Daylight Harvesting for Interior systems, and Photocell Control for Exterior systems.|
|5||High-End Trim*||The capability to set the maximum light output to a less-than-maximum state of an individual or group of luminaires at the time of installation or commissioning. High-End Trim must be field reconfigurable. This capability is distinct from automatic compensation for lumen depreciation, which automatically increases output as a system operates over time.
*While DLC specifically requires “High-End Trim”, some manufacturers refer to this capability as “Task Tuning” or “Tuning” within their system interfaces. Refer to NEMA LSD 64-2014 for definitions of Lighting Controls Terminology.
|6||Zoning||The capability to group luminaires and form unique lighting control zones for a control strategy via software-defined means, and not via physical configuration of mechanical or electrical installation details (e.g. wiring).
Interior: Zoning is required for Occupancy Sensing, High End Trim, and Daylight Harvesting control strategies except for systems that feature Luminaire Level Control (LLC) capabilities as defined in these requirements under “Reported Capabilities”, in which case zoning is only required for Occupancy Sensing and High-End Trim control strategies.
Exterior: Zoning is required for High End Trim
|7||Luminaire and Device Addressability||The ability to uniquely identify and/or address each individual luminaire, sensor, controller, and user interface device in the lighting system, allowing for configuration and re-configuration of devices and control zones independent of electrical circuiting.|
|8||Continuous Dimming||The capability of a control system to provide control with sufficient resolution in output (100+ steps) to support light level changes perceived as smooth (as opposed to step dimming with a small number of discrete light levels).|
|9||Control Persistence||The capability of a networked lighting control system’s lowest-level (“edge device”) luminaire controllers to execute three energy saving strategies (occupancy sensing, daylight harvesting, and high-end trim) at a room-level, or finer, resolution in the absence of communications with the next higher networked element in the system’s topology.|
|10||Scheduling||The capability to automatically affect the operation of lighting equipment based on time of day. Scheduling capability is Reported for Interior systems and Required for Exterior systems. Exterior systems are required to have event scheduling, and "astronomical" scheduling functionality for sunrise and sunset programming, based on geographical location and time of year.|
|11||Energy Monitoring||The capability of a system, luminaire, or device to report its own energy consumption, or the energy consumption of any controlled device via direct measurement or other methodology. The method by which the system implements this capability must be clearly described. The sampling frequency and accuracy of reported data must be specified.|
|12||Device Monitoring / Remote Diagnostics||The capability to monitor, diagnose, and report operational performance including system and/or component failures.|
|13||Type of User Interface||The type of interface provided by the control system for users to read and adjust control system settings during system start-up, commissioning, and/or ongoing operation.|
|14||Luminaire Level Lighting Control (LLLC, integrated)||The capability to have a networked occupancy sensor and ambient light sensor installed for each luminaire, and directly integrated or embedded into the luminaire form factor during the luminaire manufacturing process.
In addition to these required integrated components, LLLC systems must have Control Persistence capability as described in this document.
To demonstrate commercial availability of the integrated component options, at least one family, luminaire or kit with integrated control must be verified by DLC. Manufacturers may choose whether or not to list this information publicly on the QPL.
|15||Personal Control||The capability for individual users to adjust to their personal preferences, via networked means, the illuminated environment of a light fixture or group on of light fixtures in a specific task area. The system must be clearly designed for this purpose with a control interface designed for a single individual user that does not provide access to system-wide settings.
A wireless dimmer switch may only be considered a personal control interface if product documentation:
|16||Load Shedding (Demand Response)||The capability to reduce the energy consumption of a lighting system, in a pre-defined way, on a temporary basis, in response to a demand response signal. The method by which the system implements this capability must be clearly described in the reference document(s).|
|17||Plug Load Control||The capability to control the power delivered to receptacles through scheduling or occupancy sensing. The method by which the system implements this capability must be clearly described in the reference document(s).|
|18||External Systems Integration (e.g. BMS, EMS, HVAC, Lighting, API)||The capability to exchange data with other networked systems such as Building or Energy Management Systems (BMS/EMS), Heating Ventilation and Air Conditioning (HVAC) Systems, or other Lighting and Building Systems via BACnet, Application Program Interface (API) or other methods. The method, including formats and languages, by which the system implements this capability must be clearly described in the reference document(s).|
|19||Emergency Lighting||The capability of a system’s luminaires to interact with one or more of the following emergency power sources: 1) on-luminaire battery backup, 2) remote source (generator or central battery), switched at luminaire, 3) remote source (generator or central battery), switched at central location.
Information provided on the QPL about this capability is not intended to fully characterize emergency lighting. It is intended to provide information about the lighting control system as a point of reference for the emergency lighting design process. The QPL will identify online documentation provided by manufacturers for system designers to refer to. This documentation will identify wiring diagrams, required components, and/or application guides needed to understand design considerations for integrating the system into an emergency lighting system.
|20||Security||DLC is providing an optional field on the QPL for system manufacturers to list a link to security information of their choice about their system.|
|21||Color Changing / Tuning||The capability to alter the output and color of tunable white and/or variable color output luminaires via a dedicated control interface(s). To demonstrate compliance with this capability, the interface(s) must be clearly described in the product literature and allow for at least two CCT settings. These settings may be described in terms of CCT, such as 3000K or 5000K, or simple descriptive terms for the desired setting such as 'Night' or 'Day'. The product literature must also specify installation and configuration requirements to implement this functionality.|
|22||Start-up and Configuration Party||The QPL will identify the most typical responsible party and their required level of training to start-up and configure the system to the extent that all Required Capabilities are functioning. Documentation is not required.