Networked Lighting Control System Technical Requirements V4.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 effects lighting changes in luminaires, retrofit kits or lamps. Luminaires, retrofit kits and lamps are qualified separately by the DLC’s Solid-State Lighting Technical Requirements and Qualified Products List.
DC and PoE networked lighting control systems are eligible to be qualified, in conjunction with the SSL Testing and Reporting Requirements for DC and PoE Lamps, Luminaires, and Retrofit Kits.
Building Management Systems that control networked lighting plus other building systems such as HVAC, are eligible to be qualified as NLC systems and listed on the QPL, provided that they meet all of the DLC’s requirements for NLC. Note that the DLC does not claim to qualify any HVAC-specific capabilities of these systems at this time.
Horticultural control systems are not eligible to be qualified at this time.
Definition of “Required” vs. “Reported” Capabilities
The Technical Requirements are built on “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 the 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.
The 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.
In order for an applicant to claim a capability listed in Tables 1 and 2, the manufacturer’s customer literature must specify that the system has the capability, with instructions for how to configure and/or use this feature.
“Customer Available Information”:
“Customer available” means the documentation is a finished product available publicly on a website, and/or included with the product packaging, and/or provided to the customer upon request. It should not be a document produced for the sole purpose of obtaining DLC qualification without further use for customers. The DLC reserves the right to accept, reject, or require changes to documentation to satisfy this requirement. Any documentation provided to the DLC will be used for the purpose of verifying compliance with DLC Technical Requirements and will not be made available publicly or distributed.
- Continuous Dimming
- Individual Addressability
- Luminaire Level Lighting Control (LLLC, integrated)
- Ease of Implementation
- Type of User Interface
The 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 for 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, and with complete, final documentation and literature readily available on the manufacturer’s website before they can be listed. The DLC requires that a qualified system has been installed and operated successfully in at least one actual field installation. The 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. For annual re-listings of a previously qualified system for which a recording of a prior presentation is available and the system has not changed extensively, this requirement may be waived or shortened.
All requirements documents, including the Application Form, Instructions, and supporting documentation can be found on the DLC website here.
In order to serve the needs of stakeholders for long term planning, the DLC includes multi-year plans for some topics and/or requirements. These plans outline a general direction for each topic over the next few years, subject to refinement through the stakeholder engagement process.
Energy Monitoring PlanThe DLC’s utility and energy efficiency program members have requested that energy data reports be made available to support networked lighting control incentive/rebate programs. In alignment with the multi-year plan proposed in the prior V3.0 requirements, energy monitoring is now a required capability in V4.0 with an exception for room-based systems. Data is reported via .CSV file and/or API. Methods of energy monitoring may include automated measurement methods and methods that require manual input of wattage to measure energy use. As part of the application or re-application process, each product that qualifies for energy monitoring will provide to the DLC a sample .CSV file or API documentation.
Energy monitoring capability is not required for room-based systemsA “room-based system” is defined as follows: A system that is designed to control lighting in a single room or space and where the control, configuration, and management of the system is contained within the room or space illuminated by the system. In order to interact with the system, (for instance, to change any settings or to download any data), a user must be physically present in, or in close proximity to, the room or space illuminated by the system.
In order for a system to qualify for this exemption, the DLC review process will confirm that the product claims only “Room or Zone” for interior scope as listed on the DLC QPL.
Plan for V5.0 Technical Requirements to be released in June 2020Version 5.0 will focus on specifying requirements for the energy data produced by the system, including required energy data fields and associated characteristics. V5.0 is expected to include a requirement for 15-minute timestamped interval energy data in Wh, and record retention of at least one year. The DLC intends to work within the ANSI/NEMA C137 Committee to develop the specific data requirements to include in V5.0. V5.0 will also consider a reporting requirement for systems to output a Configuration Report that identifies system configuration and settings such as high-end trim, delay dwell times, zoning, and lighting levels at the time of installation/commissioning. The purpose of this report will be to aid efficiency programs and customers in confirming appropriate system configuration.
In alignment with the multi-year plan proposed in the prior V3.0 requirements, the DLC is taking the next step to help ensure qualified systems utilize best-practice standards for cybersecurity.
With these current V4.0 requirements (2019), the DLC has established criteria for cybersecurity standards that will be accepted in order to claim the optional reported “Cybersecurity” capability.
- In order to claim the cybersecurity capability, a system must have a valid certification for one or more of the specified standards at the time of qualification.
- The list of applicable standards in Table CS-1 will be reviewed for each incremental revision to the Technical Requirements, or annually, whichever comes sooner.
- Self-certification is acceptable, provided that it is accredited by a certifying body with a formal procedure to authorize self-certification. For example, UL has a Data Acceptance Program for cybersecurity to authorize self-certification to ANSI/UL 2900-1.
Criteria for acceptable cybersecurity standards
The DLC recognizes cybersecurity standards that meet the following criteria:
- Certifiable with a standardized methodology established through either:
- A voluntary consensus process such as ANSI, ISO, IEC, etc.
- A federal agency of the USA or Canada
- A collaborative multi-stakeholder engagement process such as the Cloud Security Alliance
- Applies to one or more of the following:
- Product development process lifecycle
- Components/Embedded Devices
- Cloud Services
- Includes at least 3 of the following technical content, for (2. b,c,d) above
- Penetration testing
- Communication robustness testing
- Vulnerability identification testing
- Multiple levels of security
- Renewal is required at least every 3 years, in order for a certificate to remain valid.
- Cybersecurity: The practice of defending networked systems and data from malicious attacks.
- Process: Standards that address the development process in order to reduce the number of cybersecurity vulnerabilities that are designed into components, systems, and services, and that manifest over the product lifecycle.
- Components: Standards that address the cybersecurity of each individual component in a networked system.
- System: Standards that address the networked system, including aspects such as authentication, data confidentiality, system integrity, and service availability.
- Cloud Services: Standards for cloud services that address secure integration with services from a remote cloud computing provider.
List of standardsStandards that meet the criteria are listed in Table CS-1. Once a standard is on this list, the DLC does not expect to remove it with less than two years of notice.
|Standard||Process||Components / Embedded Devices||System||Cloud Services|
|ISO 27017 (with 27001)||y|
In V5.0 (scheduled for release in June 2020)
- The DLC will convene a technical working committee on cybersecurity in 2019, in order to refine the cybersecurity plan for V5.0 and beyond.
- All listed systems will be required to be certified with at least one standard that meets the DLC criteria for acceptable cybersecurity standards, as shown in Table CS-1.
- Certification in any one of the four categories (Process, Components, System, Cloud Services) will be sufficient.
- A process will be described for re-certification, in case a system’s certification expires after qualification.
- For room level systems that cannot be upgraded to add a permanent internet connection, an exception or delay in the requirement will be considered in the stakeholder engagement process.
Cybersecurity NotesWhile the standards in Table CS-1 can be applied to NLCs, not all of their requirements may be relevant for lighting control systems. Manufacturers and their certification bodies should review each standard to identify the appropriate requirements for each system being qualified.
Other Future PlansLater in 2019, the NLC QPL will migrate from its current Excel format to an online format similar to the online DLC SSL QPL. In that process, the organization of the data will be modified in order to support a better user experience.
The DLC is currently researching and developing a multi-year plan for interoperability to be included in the V5.0 update in 2020.
The 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.
Annual Revisions and Grace Period
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/lamps and control devices to exchange digital data with other luminaires/lamps and control 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/lamps 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 the 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/lamps 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 lighting control (LLLC) 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||Individual Addressability||The ability to uniquely identify and/or address each individual luminaire/lamp, 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/lamp 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 time-based 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 to report the energy consumption of a luminaire/lamp and/or a group of luminaires/lamps.
|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 or kit, and directly integrated or embedded into the form factor during the luminaire or kit 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 the 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 publicly available information must clearly describe a control interface for use by a single individual who does not have 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 publicly available reference(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 publicly available reference(s).|
|18||External Systems Integration (e.g. BMS, EMS, HVAC, Lighting, API, Cloud)||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 publicly available reference(s).|
|19||Emergency Lighting||Publicly available documentation illustrating how a system’s luminaires connect with an emergency power source.
The QPL will provide the URL(s) for 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||Cybersecurity||The compliance with a cybersecurity standard that meets the DLC criteria. The current standards are shown in Table CS-1 and listed here:
|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||Ease of Implementation||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.|
|23||Scenes||The capability of a system to provide two or more pre-programmed light level settings for a group or multiple groups of luminaires to suit multiple activities in a space, and allow for recall of these settings via a switch, control device, or signal from a BMS or API.|