SELECTING LIGHTING

CONTROL SYSTEMS

What’s inside: A systematic approach to networked lighting controls

Controls Objectives System Capability Networking and Documenting a

and Use Cases Considerations Communication Options Lighting System
Introduction TABLE OF CONTENTS:
The objective of this resource is to assist decision-makers in
understanding how networked lighting control system attributes can Focused System Selection...........................................2
satisfy project objectives at an appropriate cost and functionality.
The Process..........................................................2
This resource is intended for members of the project team involved in
the design and selection of lighting control systems, especially team 1 Establish Controls Objectives......................................3
members with limited-to-moderate controls experience.
Objectives and Use Cases................................3
Over the last five years, Pacific Northwest National Laboratory has
conducted extensive research on the problems affecting lighting 2 Define System Capabilities...........................................5
controls, from analysis and evaluation of a wide range of installations
to dozens of interviews with industry participants. Some key Capabilities...........................................................5
challenges that have impacted successful lighting controls installations
3 System Architecture Impacts......................................6
include:
System Scale.......................................................6
● Failure to align lighting control system capabilities to project
objectives Network Options................................................7
● Unclear or incomplete documentation of objectives, desired Wireless Communication Networks...............8
capabilities, and system features
Wired Communication Networks...................9
● Misunderstandings in design and set up due to ambiguity in
terminology. System Components & Functions................10

These challenges can be compounded by reliance on the system Schematic Examples.........................................11

architecture and vocabulary of individual manufacturers, which may
limit one’s understanding of lighting control systems. Developing 4 Documentation..............................................................14
a non-proprietary understanding of lighting control systems can Controls Intent Narrative.................................14
offer broad options for achieving project objectives and desired
performance while minimizing cost and complexity. Sequence of Operations..................................15
This document offers a systematic approach to establish objectives Specifications and Drawings..........................15
for lighting controls, identify relevant system capabilities, and narrow
the choices in system architecture to those that support the desired Capability Details.........................................................16
system capabilities and availability of organizational resources during
Component Details......................................................19
operation.
Additional Resources.................................................20

1
The Focused System Selection Process
The four steps below outline system selection to the point where the required characteristics of a system can be documented in terms of its
capabilities and system architecture. From here, decision-makers can identify products that meet their requirements and select the system with
favorable cost, resiliency, and support.

1 2 3 4
Establish Define Assess Document
Controls System System Design and
Objectives Capabilities Architecture Operation

1 Identify controls-specific 2 Define capabilities needed 3 Understand how the 4 Create documents that
objectives based on the to support objectives. structure and components support accurate
owner’s project requirements Capabilities will include of the system contribute to installation, configuration,
(OPR). those required for energy the desired capabilities and and operation of the
code compliance as well as satisfy project limitations control system. The task of
Use cases can help to set those drawn from more and owner preferences. documenting begins with
priorities. Examples include: than one use case. the Controls Intent
- System Scale Narrative and continues
- Energy Code Compliance - Consider risk factors and throughout the design
- Networking Options
(Required) capability requirements process.
- Wired and Wireless
- Enhanced Lighting Networks - Controls Intent Narrative
Performance
- System Components - Sequence of Operation
- Enhanced Energy
Management - Drawings and
Specifications
- Enhanced Facility
Productivity

Figure 1. Overview of the focused system selection process. Each step of the process is explained in detail in the following pages.

2
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

1
OBJECTIVES CAPABILITIES IMPACTS

Objectives and Use Cases

Owners may provide direction for system performance, cost, occupant considerations, and project goals. Setting clear objectives with the
project team helps to determine the functionality of the system; the four use cases below describe common objectives and can help prioritize
system options.

Energy Code Compliance

Code compliance represents the minimum requirement for most projects and is generally the least costly. Local codes may vary and should
be thoroughly understood. Code compliance alone may not satisfy owner objectives. Depending on local code requirements, supporting
capabilities may include switching and local control, occupancy sensing, time scheduling, daylight-responsive controls, dimming, and plug load
controls.

All projects must comply with local energy codes. Simple projects may only need capabilities supporting this use case. Aspects of other use
cases will likely be added to satisfy more extensive controls objectives.

Enhanced Lighting Performance Enhanced Energy Management Enhanced Facility Productivity

Enhanced lighting aims at improving This use case looks for energy Enhanced facility productivity embraces
workforce productivity, wellness, conservation and management beyond greater spatial and asset efficiency,
satisfaction, and facility appeal. minimal code compliance by optimizing improved retail performance, and increased
Increasingly popular capabilities, such systems through granular feedback on engagement, safety, and security.
as tunable white and task tuning, energy usage and system performance. Capabilities typically require external
can increase cost and programming Some capabilities require additional analytics and application programs,
complexities. Other supporting capabilities communication infrastructure and will which add cost and complexity. Examples
include scene control, motorized system benefit from dedicated operational include asset tracking, indoor positioning,
control, and lumen maintenance. resources. Capabilities include occupant counting, external system
measurement and reporting, external integration, measurement and reporting,
system integration, task tuning, plug and diagnostics and remote monitoring to
load control, diagnostics and monitoring, streamline maintenance.
demand response, lumen maintenance,
and motorized system control.

3
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

1
OBJECTIVES CAPABILITIES IMPACTS

Objectives and Use Cases

The first step in system selection is to identify specific system capabilities that will satisfy the project objectives and owner’s requests.

Use Cases System Capabilities

Switching/Local Control

Time Scheduling
Energy Code
Occupancy Sensing
Compliance
Daylight-Responsive Control

Dimming

Scene Control

Enhanced Lighting Tunable White

Performance
Task Tuning

Lumen Maintenance

Motorized System Control

Plug Load Control

Enhanced Energy
Management Demand Response

External System Integration

Energy Measurement and Reporting

System Diagnostics and Monitoring

Enhanced Facility
Productivity Indoor Positioning

Asset Tracking

Occupant Counting

Figure 2. Common use cases (left) and the system capabilities (right) that functionally support organizational objectives.

4
 DEFINE SYSTEM
ESTABLISH CONTROLS SYSTEM ARCHITECTURE DOCUMENTATION
CAPABILITIES

2
OBJECTIVES IMPACTS
See Capability Details section for
more information.

Capabilities
Many common lighting control system capabilities are listed in Table 1, with associated use cases, design risk factors, and implementation issues.
The legend explains the icons that represent common risk factors: the availability of the technology in the current networked lighting controls
market and the level of communication required for each capability. These two factors can help decision-makers compare different capabilities in
terms of overall risk and reliability.

Le gend System C apabi l i t i es Use C ases R is k Fac tors I mp lementat ion N otes
TA CR
Use C ases Time Scheduling CC
CC Energy Code Compliance Occupancy Sensing CC Sensor location and coverage are critical.
LP Enhanced Lighting Performance
Daylight-Responsive Control CC Zoning and sensor placement are critical.
EM Enhanced Energy Management
Dimming CC LP
FP Enhanced Facility Productivity
Scene Control LP
Risk Fa cto rs
Technology Availability (TA) Tunable White LP Digital control is recommended for best performance.

Capability is ubiquitous in lighting

Task Tuning LP EM
controls systems.
Capability is offered in an upgraded Lumen Maintenance LP EM
tier of most controls systems.
Motorized System Control LP EM FP
Availability in current market is
limited to specialized or advanced An alternative option uses a clock not integrated with the lighting
systems.
Plug Load Control CC EM system.

Communication Requirements (CR) Demand Response EM Communication with external utility is required.

Basic communication or does not External System Integration EM FP A gateway and/or server are typically required.
require an exchange of data.
Requires an additional measurement device, a digital driver, or a
Capability may require Energy Measurement and Reporting EM FP digital load controller.
communication between devices Requires an additional measurement device, a digital driver, or a
within the lighting controls system. System Diagnostics and Monitoring EM FP digital load controller. Diagnostic capabilities differ between systems.
Standardized methods for data
exchange may be required. Indoor Positioning FP Additional devices, server, analytics, and communication required.

Capability requires communication Asset Tracking FP Additional devices, server, analytics, and communication required.
between devices or networks outside
of the lighting controls system. Occupant Counting FP Additional devices, server, analytics, and communication required.

Table 1. Common lighting control system capabilities functionally support one or more use cases, including energy code compliance and
enhanced facility productivity. Technology availability (TA) and communication requirements (CR) can assist in deciding if the capability
is appropriate for the project. Guidance for implementing certain capabilities is also provided; for more information see the Capability
Details (p. 16-18) section.

65
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

System Architecture SINGLE SPACE

During system selection, it is helpful
to understand common system A single-space system provides local control of a single room and does not communicate
architectures and network topologies externally. Internal communication can be wired or wireless. These systems may also be
as they relate to specific capabilities, referred to as room-based or stand-alone systems. Multiple room-based systems can be
project conditions, and scale. While applied across multiple spaces, although each control system will operate independently.
controls products typically identify
their capabilities, system architecture Many capabilities supporting enhanced energy management or facility productivity cannot be
is often less clear in product literature. practically supported by systems that control rooms independently and do not communicate
The following information may help externally.
decision-makers identify the architecture
of different products, along with their
strengths and limitations.
SUITE, FLOOR, OR BUILDING

System Scale A larger scale, networked system can control a suite of several rooms or an entire floor
using gateways (wired or wireless) or large-area wireless mesh networks. Connection
System architecture can be influenced to other local or external servers and systems, such as HVAC and building automation
by project characteristics, such as the systems (BASs), are possible with a gateway.
scale of the project and whether it is
Systems at this scale may also take a hybrid approach with some local, room-based
new construction or a renovation.
controls and some communicating with a central processor, gateway, or server. For
Regardless of system capabilities, example, room-based (non-networked) systems within a suite may implement occupancy
communication needs will increase sensing independently, while all of the corridor lighting is networked and programmed
with the scale or scope of the project. to follow the same operating schedule. Full functionality, especially with capabilities for
Some capabilities require advanced enhanced energy management and facility performance, usually requires a fully networked
communication or control strategies system.
regardless of the system scale.
Retrofit or renovation projects may have
different code requirements than new CAMPUS OR PORTFOLIO
projects, as well as significant challenges
installing the equipment. Wireless A campus-wide or portfolio-managed lighting control system is largely the same as a floor-
control systems may save substantial or building-scale system with an additional layer of communication for building-to-building
labor cost and installation time for most interaction. Given the physical distance involved, the control systems are connected using
projects, but particularly for retrofit intra/internet and report to a central server (physically located on-site or cloud-hosted) that
scenarios. allows the facility staff to remotely monitor and control building systems.

76
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

Network Options Central Control

Networked lighting controls allow for remote monitoring and A system with centralized intelligence uses a system-
adjustment as well as user-initiated or automated demand response. wide processor (i.e., central processor) to signal the
While a campus or portfolio of properties require networked lighting networked components, such as user interfaces,
controls for remote access, some capabilities, such as demand sensors, and controllers, and to receive status reports
response, require networked controls regardless of the project from them. A centrally networked lighting control
scale in order to communicate with systems outside the lighting system may be configured to communicate with the
controls. Networked systems typically use centralized intelligence (or building’s primary control network. Some systems
processing), distributed intelligence, or some combination of the two. may use a gateway as a central processor, which will
For example, luminaire-level lighting controls (LLLC) utilize distributed also translate control signals between the building’s
intelligence at the fixture to enable local capabilities, but can process control network and the lighting control network.
higher level capabilities, such as scheduling, at the central processor. Large-scale central control systems tend to use
Characteristics of two common network designs, a centrally-controlled wired communication at the building scale and may
system and a LLLC, are described to the right. transition to wireless communication at the floor or
suite level.

LLLC
With independent control (i.e., a load controller and
sensor) located in each luminaire, LLLC provides
maximum granularity with more options for creating
lighting effects, reducing energy consumption, and
collecting information. Distributing intelligence to the
luminaire level can protect the lighting control system
LUMINAIRE ZONING against widespread faults and failures and increase
system resiliency because the devices can operate
Zoning is a key system design consideration. A zone is a set of
autonomously. Sensors in LLLC systems typically
luminaires that respond together to a control signal. The smaller
operate as continuous data streams with frequent
the zone, the more refined the lighting and energy management.
status updates that increase the quantity, and therefore
The larger the zone, the simpler and less costly the set up.
granularity, of the data that is collected compared to
With LLLC, each luminaire can be its own zone (the ultimate
other methods (see the Digital subsection in the Wired
in granularity) for certain capabilities (e.g., daylight responsive
Communication Networks section). An LLLC can use
controls) as well as part of larger zones for others (e.g.,
a gateway or central controller to communicate to
occupancy sensing, time scheduling). Zones should consist of
system-wide control schemes or to external systems.
one luminaire type to ensure compatibility between the luminaire
driver and other control devices.

87
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

Hub
Wireless Communication Networks
A central access point, often housed in a hub or gateway,
Wireless communication eliminates the need for controls wiring in fully sends and receives signals from other nodes in the
networked as well as independently controlled room-based systems. networked components, which do not communicate to
Wireless systems are particularly useful in renovation applications and each other. The hub or gateway(s) should be installed
where ceiling access is difficult. Wireless components can also easily in locations that will provide RF coverage for all devices
be reconfigured for future renovations. Wireless control systems use communicating with the device. In some cases, luminaire
digital radio frequency (RF) communication to transmit data and are controllers may have the ability to act as boosters or
typically structured as hub, mesh, or point-to-point topologies, or repeaters to extend signal strength. Providing more hubs
some combination of the three. may increase communication speed and reliability, but will
While some systems employ genuinely open communication also increase the cost. This topology may also be referred
protocols, most systems today are proprietary to some extent. The to as a “star” network.
proprietary nature ensures interoperability between devices within the
ecosystem; however, communication among devices from different
manufacturers can be inconsistent and product compatibility is key. RF Mesh
communication protocols can be applied in a variety of topologies, as In mesh networks, all devices communicate as nodes
product and manufacturers determine. in the network and multiple, redundant paths between
Wireless RF signals are not limited to line-of-sight, but individual devices exist to sustain communication when a single
devices are limited in signal range (typically specified in manufacturer device fails. Employing a mesh network can improve
literature) and can be affected by building materials. Networks also system resilience, increase the signal strength shared
have limits on the number of nodes they can support, which varies between devices, and increase the expanse of the
by system. Common wireless protocols include Zigbee and qualified network. Mesh networks can exist without a gateway if a
Bluetooth mesh. connection to a central server, external building systems,
or applications is not needed.

WHAT IS A NODE?
Point-to-Point
In wireless and wired systems, nodes facilitate communication
between devices and can send and/or receive a control signal. Unlike hub and mesh networks, point-to-point
In a hub network, nodes typically communicate to the gateway, network signals are typically limited to a single space.
while in a mesh network, nodes communicate with each other. Nevertheless, such systems may be connected to
Nodes may be standalone devices; however, they are typically
one another by using a gateway. Often, point-to-point
integrated with controllers, sensors, switches, or gateways. As a
connections may be utilized for communication between
result, many devices in a mesh network are often referred to as
nodes because they are necessary for communication in each components within larger systems or to incorporate
device. battery-powered devices (e.g., audio/visual controls, local
controls, etc.).

98
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

Wired Communication Networks

Against the costs and limitations of running wires to the control system, wired systems offer a degree of cybersecurity compared to wireless
systems due to the need for on-site access. Wired systems transmit control signals using analog or digital communication protocols. A
comparison is provided in Table 2.

Analog Digital
Analog communication sends a control signal over low-voltage Digital communication also requires dedicated low-voltage
conductors wired to each luminaire. Two common analog control conductors. Importantly, digital networks can provide a one-way or
methods used in lighting systems, phase dimming and 0–10V, only two-way transfer of information, including system commands and
support one-way communication which limits system feedback and data reporting. Addressable devices permit granular data collection
reporting. Analog control zones are determined by the control wiring; and communication as well as reconfigurable zones of control.
changing control zones requires rerouting the control wires, which can Rezoning is typically implemented from a software application.
be quite costly.
Data exchange may occur in a continuous or repetitive scheme, or a
0–10 V is a commonly used analog control signal, widely supported by command-and-response scheme in which the data are sent once and are
manufacturers and familiar to most commercial installers. For luminaire not resent until there is a change in the conditions or a different response
control, 0–10 V load capacities limit the number of fixtures that can is received. Trade-offs in data quantity and quality should be considered
belong to a single group. 0–10 V controls require 0–10 V compatible for capabilities that require data capture from lighting equipment.
drivers and other components.
Wired digital protocols include the Digital Addressable Lighting
Some advanced capabilities are not compatible with 0–10 V Interface (DALI) standard, manufacturer-specific protocols, proprietary
luminaires, but can be successfully implemented with a digital load variations, and the entertainment-oriented DMX512, which is widely
converter. These include lumen maintenance, external system used for multi-channel color mixing.
integration, demand response, energy measurement and reporting,
As a network technology, low-voltage direct current (DC) systems
system diagnostics and reporting, wayfinding, asset tracking, and
with digital controls can send and receive data from each connected
occupant counting. unit or device.
DC power and control signals can be delivered independently or in
SYSTEM ATTRIBUTE ANALOG DIGITAL
a single ethernet cable, as in a Power over Ethernet (PoE) system.
Data Exchange One-way Two-way These systems can support Wi-Fi access points, security cameras,
Luminaire Addressability No Yes and telephones, as well as light-emitting diode (LED) luminaires and
Zoning Flexibility Determined by wiring Can be reconfigured in software
sensors. PoE systems require a network device, called a switch, for
signal and power, as well as DC luminaire drivers.
Table 2. Analog and digital wired system comparison.

109
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS
See Component Details section
for more information.

System Components and Functions

System components have different communication strategies depending on the scale of the system and the task at hand. Some control devices
can facilitate one or more functions depending on the specific system, as summarized below. Each manufacturer or controls system may use
unique language or terminology for the same controls components; see the Component Details section for examples.

Servers store and share data captured by sensors or other Servers st

IN THE LUMINAIRE sensors o
building systems and house the programming information for dedicated
IN THE SPACE
the lighting system. A local or cloud-hosted server typically acts building a
IN THE BUILDING serve as i
as the central controller and houses most of the intelligence for control sy

a centrally controlled lighting system. ANALOG Gateways,

Wired bridges) tr
Wired different p
In some systems, the function and intelligence of the server DIGITAL LUMINAIRE connected
or Wired LOAD
SERVER GATEWAY DRIVER gateway(s)
is integrated into the gateway itself, eliminating the need for Wirelesss or CONTROLLER
considered
Wirelesss
a server unless there is a requirement for storing and sharing to commu

data or remote monitoring. User Inter

touchscre
They send
Gateways (also known as a hubs or bridges) translate between LED MODULE some can
networks with different protocols. The gateway may also house
USER Sensors d
network routing and access points, which create the network INTERFACE SENSORS environme
sensors m
and enable communication. The location of the gateway(s) in personnel
Figure 3. Schematic system architecture describing the location of each controls component and
wayfinding
wireless systems should be considered to ensure adequate the possible communication methods used for data exchange.
on the cei
signal strength to communicate with other devices. wallbox de

Nodes sen
User Interfaces include wall switches, touchscreens, computers, radio wave
but are typ
and mobile devices. They send commands to load controllers
for wireles
and some can display system information.
SERVER Load Contr
Sensors detect occupancy, light levels, or other environmental Load Controllers, typically relays, power packs, or dimming modules, send and/or and/or rec
change. Lo
conditions. More advanced sensors may be employed to track receive commands to execute a lighting change. Load controllers may be separate or package
sensor.
assets or personnel, count occupants, or assist with wayfinding devices or packaged with a driver, user interface, or sensor.
Luminaire
capabilities. Sensors can be installed on the ceiling or wall, in a Luminaire Drivers, together with the LED array(s), are part of the load. Critically, the module(s)
signal proto
luminaire, or in a wall switch. signal or protocol of the control system and that of the driver must be compatible. the driver m
GATEWAY

1110
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

Schematic Example - Centralized Intelligence

The following schematic diagrams depict how distinct lighting control components communicate with one another and where each component is
typically located: within the luminaire itself, within the room or space, or within the building. They are examples and will not represent all lighting control
systems.

Networked Lighting Control System - Centralized Intelligence

IN THE LUMINAIRE
A Internet
IN THE SPACE
B HARD-WIRED:
IN THE BUILDING Ethernet
E WIRELESS:
ANALOG Wi-Fi
B D
OR
C HARD-WIRED:
LOAD DIGITAL LUMINAIRE Ethernet
SERVER* GATEWAY* DRIVER
CONTROLLER WIRELESS:
Bluetooth Low Energy (BLE), Zigbee, Thread, etc.
A C
D HARD-WIRED:
Ethernet

THIRD PARTY LED MODULE WIRELESS:

SOFTWARE USER BLE, Zigbee, Thread, etc.
APPLICATIONS INTERFACE SENSORS
E HARD-WIRED:
Low-voltage wiring

Analog (one-way) - 0-10V

*In most systems, the gateway or a local server will act as the central controller. Digital (two-way) - DALI 2, DMX 512, manufacturer
specific, etc.
Not all systems will require a connection to external applications or other building systems via a gateway or server.
In some systems, the load controller may be integral to the driver, the sensors, or the user interfaces.

Figure 4. Schematic diagram of lighting control system components and possible communication strategies for a networked system with centralized intelligence.

1211
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

Schematic Example - Room-Based System

Room-Based Lighting Control System

IN THE LUMINAIRE
A HARD-WIRED:
IN THE SPACE Ethernet
B WIRELESS:
A ANALOG BLE, Zigbee, Thread, etc.
OR B HARD-WIRED:
DIGITAL Low-voltage wiring
USER LOAD LUMINAIRE
INTERFACE CONTROLLER DRIVER Analog (one-way) - 0-10V
Digital (two-way) - DALI 2 (including
A D4i drivers), DMX 512, manufacturer specific, etc.

SENSOR LED MODULE

Figure 5. Schematic diagram of lighting control system components and possible communication strategies for a room-based system.

1312
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

3
OBJECTIVES CAPABILITIES IMPACTS

Schematic Example - Luminaire Level Lighting Control System (LLLC)

Luminaire Level Lighting Control System

IN THE LUMINAIRE
A Internet
IN THE SPACE
B HARD-WIRED:
IN THE BUILDING Ethernet
E WIRELESS:
D ANALOG Wi-Fi
B
OR
C HARD-WIRED:
DIGITAL LUMINAIRE Ethernet
LOAD
SERVER GATEWAY DRIVER
CONTROLLER WIRELESS:
BLE, Zigbee, Thread, etc.
A C
D D D/D HARD-WIRED:
Ethernet

LED MODULE WIRELESS:

THIRD PARTY USER SENSOR BLE, Zigbee, Thread, etc.
SOFTWARE
INTERFACE
APPLICATIONS
E HARD-WIRED:
Low-voltage wiring

Not all systems will require a connection to external applications or other building systems via a gateway or server. Analog (one-way) - 0-10V
In some systems, the load controller may be integral to the driver, the sensors, or the user interfaces. Digital (two-way) - DALI 2 (including
D4i drivers), DMX 512, manufacturer specific, etc.

Figure 6. Schematic diagram of lighting control system components and possible communication strategies for an LLLC system. Lighting control systems may not contain each
component described; however, it is important to understand how each component interacts with the rest of the system.

1413
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

4
OBJECTIVES CAPABILITIES IMPACTS

Control Intent Narrative (CIN)

The earliest version of the CIN is typically developed during Schematic
Design and translates the owner’s objectives into the general control
capabilities that will be applied to each space or function of the
project.
WHAT SHOULD BE
Control capabilities above and beyond owner requests that are
INCLUDED IN A CONTROL
implemented to satisfy code requirements should be documented INTENT NARRATIVE?
explicitly to avoid misunderstanding. The design should reflect the The CIN is typically organized by space
interpretation of local enforcement authorities (i.e., authority having type. Include an overview of the control
jurisdiction [AHJ]), as well as the written code requirements. strategies and capabilities deployed in
During Design Development, the next iteration of the CIN should also each space to satisfy project objectives
include the intended approaches to system scale, networking, building and code requirements.
integration, communication, and user-interfaces. Decisions, such as ● System scale
the use of digital protocols or integral sensors that support luminaire-
level lighting control, are also incorporated into the CIN. ● Networking and communication
requirements
Although the CIN often benefits from the clarity of minimal detail,
the intent and desired outcome should be unambiguous. The CIN ● Existing conditions (where applicable)
should be written in plain language to clearly communicate the design
● Sensor functionality requirements
objectives to all members of the project team.
● User interface and local control intent
● Application of automatic and/or
manual lighting control
● Accent or specialized lighting
features
● Emergency lighting approach

1514
 ESTABLISH CONTROLS DEFINE SYSTEM SYSTEM ARCHITECTURE DOCUMENTATION

4
OBJECTIVES CAPABILITIES IMPACTS

Sequence of Operations (SOO)

The SOO provides installers and commissioning personnel with the
detailed instructions necessary to set up the system so that it can
realize the expected outcomes of the use cases and CIN. Like the CIN,
the SOO applies to each space or function. The SOO is typically written
during Design Development. WHAT SHOULD BE
After the final system has been selected, review the specific INCLUDED IN A SEQUENCE
terminology and forms used during programming to ensure all items OF OPERATIONS?
are addressed and clearly stated in the SOO. Be sure to align the
The SOO should document specific
description of desired behaviors within the scope or operation of the
behaviors and settings described in the
specific, final system.
CIN. Language should be prescriptive
and contractually enforceable.
Specifications and Drawings
Specifications and drawings also provide critical information necessary ● Light levels
for the unambiguous implementation of the controls system. These ● User interface engraving and
may include specifications for controls equipment, protocols, and functionality
single-line diagrams for wiring. Directions for system integrators and
user training also form part of the specification document. Maintaining ● Scene programming
a comprehensive record of decisions, including why a certain system ● Occupancy or vacancy sensor
or luminaire was not selected, will help resolve questions as design
setpoints and methods
progresses; it will also strengthen the specification.
● Time-based controls and schedules
Locations for control equipment are typically shown on electrical
drawings, along with single-line wiring diagrams. Directions for labeling ● Daylight-response setpoints and
user interfaces may be located on schedules, incorporated in the methods
SOO, or added as notes on drawings. As long as repetitive information
in documents is not inconsistent, placing information in multiple ● Night lighting and emergency lighting
documents can reinforce helpful information and respond to the methods, zoning, and triggers
varying practices of installers and other members of the project team.
All materials in the controls design and specification need to be
complete and consistent. Gaps and conflicts in the various documents
often leave installers and commissioning personnel uncertain as to
what is desired or how to accomplish general objectives and who
may be contractually responsible for any additional labor required to
address system performance shortcomings.

1615
 CAPABILITY DETAILS

Capability Details
The functional capabilities of a lighting system determine the range of outcomes it can deliver and the use case(s) it supports. Some capabilities are
mandated by state energy codes; others are discretionary. The task and use of the space typically drives the need for control functions. Most spaces
will employ several control strategies and control system capabilities.

R is k Fa c to rs
Technology Availability (TA) TIME SCHEDULING CODE COMPLIANCE

Capability is ubiquitous in lighting A programmable clock signals lights to turn on or off, dim, or change color, according to the hour or day of the week. Astronomical clocks adjust for
controls systems. seasonal, latitude-related differences in sunrise and sunset. As an alternative to sensor-based control for automatic shutoff, time-based control provides
Capability is offered in an upgraded lower savings and requires override capability for interior spaces.
tier of most controls systems.
IMPLEMENTATION NOTES: In non-networked systems, scheduling can be easily implemented with timeclocks that control lighting circuits or switchlegs at
Availability in current market is the panel. Hybrid or fully networked lighting control systems use computer software or the building management system to implement time scheduling.
limited to specialized or advanced
systems.

Communication Requirements (CR) OCCUPANCY SENSING CODE COMPLIANCE

Basic communication or does not

Turning lights on, off, or dimming automatically when a space is occupied or unoccupied is one of the simplest and most cost-effective strategies for
require an exchange of data.
localized energy savings. Lighting that is controlled in occupancy mode will automatically turn the lights on when an occupant is sensed and off when the
Capability may require space is unoccupied; vacancy mode will turn the lights off when the room is unoccupied and a manual switch is required to turn lights on. False triggering
communication between devices that turns lights off in occupied spaces is a major source of user complaints, which often leads users to disable the sensor, contributing to energy
within the lighting controls system. inefficiencies. Inadequate coverage, poor location, and inappropriate sensitivity settings all contribute to false triggering. The sensitivity of some sensors
Standardized methods for data
can be adjusted in the field to improve performance.
exchange may be required.

Capability requires communication

between devices or networks outside DAYLIGHT-RESPONSIVE CONTROL CODE COMPLIANCE
of the lighting controls system.
Also Known As: Daylight-Responsive Dimming and Daylight Harvesting

Daylight-responsive control – prioritizing daylight by dimming electric light – is mandated by energy codes for many interior spaces. Photosensors with
closed-loop logic adjust electric lighting to maintain the contribution of electric light and daylight so that the horizontal illuminance does not drop below a
target level. Open-loop logic, typical for exterior lighting, switches lights on and off, or dims to preset levels, based only on incident daylight or time of day.
Some systems use both open- and closed-loop logic in the same system depending on the application.

CODE COMPLIANCE
DIMMING ENHANCED LIGHTING PERFORMANCE

Adjusting lighting levels (and power) for different visual tasks, personal preference, or environmental conditions both improves the luminous environment
and saves energy. The quality of dimming (range, curve, consistency, and cost) varies with drivers and dimming protocols.

16
 CAPABILITY DETAILS

ENHANCED LIGHTING PERFORMANCE

SCENE CONTROL ENHANCED LIGHTING PERFORMANCE MOTORIZED SYSTEM CONTROL ENHANCED ENERGY MANAGEMENT
ENHANCED FACILITY PRODUCTIVITY

The light output (or color) of multiple luminaires is adjusted to create different overall lighting effects. Control over simple motorized systems, such as window shades, projection screens, and audiovisual (A/V)
Each effect is configured as a preset in the control system and is recalled by pressing a button on a user equipment, provides convenience and can be provided manually, through preset controls, by sensors or scheduling.
interface or a signal from a clock, sensor, or external device. Preset scene control provides conveniently
initiated lighting effects for different activities or times of day.
CODE COMPLIANCE
PLUG LOAD CONTROL ENHANCED ENERGY MANAGEMENT
TUNABLE WHITE ENHANCED LIGHTING PERFORMANCE
The sensors or timeclocks that control luminaires can also control the outlets that supply plug loads,
Light-emitting diode (LED) arrays of different colors can be separately dimmed to create a blended color of which can consume significant amounts of energy when in idle mode for long periods. Cost can be high
light at different levels of light output. Color tuning can be used to stimulate both visual and physiological (especially for smaller projects) and user annoyance and circumvention is a major risk. Plug load control
responses. “Tunable white” generally combines two arrays: one with warm color temperature and the other can be a capability of the lighting control system, or it can be achieved with sensors located with the
with cool. Two control channels and two-channel drivers (or two drivers) are required. controlled outlets, which may be a simpler and less costly approach.

Warm dimming, which emulates the dimming of incandescent sources, is a simplified approach where a IMPLEMENTATION NOTES: Plug load controls are required by many energy codes; however, they are
single channel provides a preset combination of color and light output. not required to be incorporated into the lighting system. The most basic form of plug load control is
accomplished using a timeclock that is not integrated with the lighting control system. If plug load
Three or more LED arrays offer more color options but require more complex and generally costly controls
controls are integrated with the lighting system, they may utilize occupancy status or timeclock control.
than for static white lighting; current experience suggests that problems are more common as well.

IMPLEMENTATION NOTES: Tunable white control can be handled by either familiar analog or digital signals.
If analog controls are used, response to the same signal may vary between luminaire manufacturers. Color DEMAND RESPONSE ENHANCED ENERGY MANAGEMENT
mixing, on the other hand, typically requires special digital control, such as digital multiplex (DMX; see
System Architecture). Also Known As: Load Shedding and Grid Interaction

During a demand response event, a utility offers an opportunity or incentive to reduce lighting and reduce
ENHANCED LIGHTING PERFORMANCE
TASK TUNING ENHANCED ENERGY MANAGEMENT
motor loads when peak electricity demand stresses the grid and the generating stations that supply it. For
buildings, the primary benefit of grid interaction is improved grid reliability and resiliency. Participating in
Also Known As: High-end Trim and Institutional Tuning; related to Personal Tuning demand response utility programs can better align peak loads to available renewable energy sources and
contribute to decarbonization of the grid.
Luminaires are configured by the control system to operate at a dimmed level (until reconfigured), setting a
lower maximum output than the luminaire can otherwise deliver. High-end trim is a popular energy-saving IMPLEMENTATION NOTES: This capability requires installation of a server or dedicated end node that can
strategy where the lighting system in its full-output mode exceeds light level requirements. Task tuning communicate externally. Cybersecurity risks should be discussed with the appropriate members of the
at the room, floor, or building level is also called institutional tuning. Personal tuning is a more complex project team.
approach that refers to individual luminaire control often manipulated by end users via a mobile app or Demand response operational profiles may be incorporated directly into a system during programming
other software interface. or accessed via an Application Programming Interface (API). API queries (e.g., the workflow to be
implemented to send and receive a signal or exchange data) should be thoroughly tested before
deployment. Open Automated Demand Response (OpenADR) is a non-proprietary, standardized interface
ENHANCED LIGHTING PERFORMANCE
LUMEN MAINTENANCE ENHANCED ENERGY MANAGEMENT commonly used to communicate demand response signals.

To compensate for the loss of light output over LED lifetimes, luminaires may be selected that initially
provide higher light levels when the system is new, so that when the light levels depreciate over time, there
is still adequate light. The control system can be programmed to reduce this “excess” light output at the
outset to match the target light level and save energy, and then gradually increase luminaire output as
light output depreciates.
IMPLEMENTATION NOTES: Lumen maintenance can be programmed into capable drivers, monitored by
photosensors, or achieved by reconfiguring the institutional tuning level over time.

17
 CAPABILITY DETAILS

ENHANCED ENERGY MANAGEMENT

EXTERNAL SYSTEM INTEGRATION ENHANCED FACILITY PRODUCTIVITY INDOOR POSITIONING ENHANCED FACILITY PRODUCTIVITY

Connection to more complex systems, sharing sensors and their measurements, reporting, and monitoring Also Known As: Real-time Location Services and Wayfinding
dashboards can assist facility managers in optimizing building systems, such as HVAC and security, as
Nodes or sensors communicate with enabled personal devices, such as phones or ID badges, to provide
well as streamlining operations. Setup and troubleshooting are major contributors to cost.
indoor positioning. Combined with mapping applications, this capability can assist in navigating
IMPLEMENTATION NOTES: Typically requires a gateway, server, or other device to interface with the central unfamiliar facilities or guiding users through retail or cultural displays. User concerns about privacy
control system and a server to store and transmit data to third-party applications. BACnet is a commonly should be considered upfront.
used ASHRAE, ANSI, ISO standardized communication protocol for building automation and controls (BAC).
IMPLEMENTATION NOTES: While the lighting system contains the sensors or nodes used to facilitate indoor
positioning, most of the functionality stems from components outside of the lighting system. A local or
cloud-based server is required to store data and communicate with other software applications.
ENERGY MEASUREMENT AND ENHANCED ENERGY MANAGEMENT
ENHANCED FACILITY PRODUCTIVITY
REPORTING
ASSET TRACKING ENHANCED FACILITY PRODUCTIVITY
Energy data collected from advanced LED drivers (e.g., D4i or ANSI C137.4 compliant drivers) or dedicated
measurement equipment can be used to track system performance, optimize system parameters, and secure Also Known As: Real-time Location Services
utility incentives. Quality and format of the data will vary between systems, which can affect usefulness;
utility incentive programs often mandate specific requirements. A variety of technologies – sensors, RF tags, and beacons – can identify and locate valuable equipment
and therefore minimize idle, misplaced, or stolen assets. Data capture and display are key to effective
IMPLEMENTATION NOTES: Energy reporting at the luminaire level requires two-way (digital) communication utilization of this capability and add to system cost.
between the driver and central system processor or gateway or a dedicated measurement device.
IMPLEMENTATION NOTES: Similar to indoor positioning, advanced sensors embedded in the lighting
system can facilitate the communication required to locate assets; however, most of the functionality
SYSTEM DIAGNOSTICS AND ENHANCED ENERGY MANAGEMENT occurs outside of the lighting system in third-party software applications. A local or cloud-based server is
ENHANCED FACILITY PRODUCTIVITY required to store data and communicate with other software applications.
MONITORING
Remote system diagnostics permit maintenance and service personnel to address problems rapidly and
with reduced cost. Reporting that compiles data also aids in improving performance. The alternative, on- OCCUPANT COUNTING ENHANCED FACILITY PRODUCTIVITY

site investigation by third parties to identify and address problems in the lighting and control systems can
be very costly. Systems with remote access can allow service companies or manufacturers into the lighting Special sensors that determine the number of occupants in a space provide granular data that can
control system for support, updates, service, and troubleshooting. improve long-term facility planning, emergency intervention, and real-time space allocation. Data capture
and display are key to effective utilization of this capability and add to overall system cost.
IMPLEMENTATION NOTES: Requires two-way (digital) communication between the driver and central
system processor or gateway. Diagnostic capabilities range from simple status alerts to detailed, product- IMPLEMENTATION NOTES: Advanced sensors (and cameras) capable of counting individual occupants (as
specific maintenance information. opposed to detecting occupancy) are required. A local or cloud-based server is required to store data and
communicate with other software applications.

18
 COMPONENT DETAILS

GATEWAYS SENSORS
Also Known As: Hubs, Bridges, and Central Processors
Simple sensors may be employed to detect occupancy, light, or other environmental conditions. More
advanced sensors may be employed to track assets or personnel, count occupants, or assist with
A gateway is a physical device that acts as a translator between networks with different protocols. Gateways wayfinding capabilities.
may also include an access point that establishes the network and routing functionality to connect to a
server or external building system. Gateways that are not connected to the internet can facilitate capabilities Sensors may be integral to the luminaire or wall switch or they may be mounted in the ceiling. For simple
such as scheduling and energy monitoring across the installation; however, an internet connection is sensor capabilities, this decision will most likely be driven by the form factor of each luminaire, as not all
necessary for more advanced capabilities. The location of the gateway(s) in wireless systems should be luminaires (e.g., downlights) accommodate integral sensors. If more complex sensor capabilities, such
considered to ensure adequate signal strength to communicate with other devices. as asset or personnel tracking, are desired, sensors integrated into some or all luminaires can provide
a more granular sensor network and adequate coverage for better performance. Luminaire-integrated
sensors can provide granular coverage and reduce installation cost; however, luminaire location
determines the sensor locations, which may not be ideal.
LOAD CONTROLLERS
Also Known As: Power Packs, Dimming Modules, and Relays
SERVERS
A controller is a device that sends and/or receives a command to execute a change. Load controllers
may be separate physical devices or integral to a luminaire driver (common for digital systems) or other Lighting-control servers may include BACnet servers, specifically dedicated for building system
control device such as a user interface or sensor. management, or locally or cloud-hosted servers that facilitate remote management, connect to utility
programs for demand response incentives, or store data for other purposes such as space utilization or
asset tracking. Servers can store and share data captured by sensors or other building systems.
LUMINAIRE DRIVER
In some systems, the function and intelligence of the server is integrated into the gateway itself,
eliminating the need for a server unless there is a requirement for storing and sharing data or remote
Although luminaire drivers are typically included in luminaire specifications, it is critical to document the monitoring.
compatibility between the luminaires, drivers, and the controls system, as some controls manufacturers
only interface with specific drivers (and luminaires).
It is the driver manufacturers responsibility to identify the correct protocol for its driver; the specifiers role USER INTERFACE
is to specify appropriate luminaires and a controls system that use the same protocol.

User interfaces can include wall switches, remote control devices, scene controllers, touchscreens,
central computer-based systems, or software-based control. They send commands to load controllers and
NODE
some can display system information.

A node is a communication device that sends and/or receives control signals in both wired and wireless
systems. Nodes may be standalone devices but are typically packaged with sensors, controllers, or user
interfaces. Nodes in a mesh network pass information node-to-node, while centrally controlled nodes will
typically communicate via a gateway. Some systems limit the number of nodes that can be connected to
each gateway.

19
Additional Resources

For more information regarding the specification and documentation of a lighting control system, see the following:
● ANSI/IES LP-6-20 “Lighting Control Systems – Properties, Selection, and Specification”
● ANSI/IES LP-16-22 “Documenting Control Intent Narratives and Sequences of Operations”
● Pacific Northwest National Laboratory “Understanding the Potential of Connected Lighting Systems”
● Pacific Northwest National Laboratory “Strategies for Success with Connected Lighting Systems”
● Integrated Lighting Campaign “Integrated Lighting Resources”
https://integratedlightingcampaign.energy.gov/resources
● Lighting Controls Association Web Resources
https://lightingcontrolsassociation.org/resources/

Contact:

Ruth Taylor
[email protected]
503.417.7570

PNNL-SA-180668 | Updated November 21, 2022

20