Lighting Controls

Revision 5 · Sep 26, 2026 +1458 −728

SynC Standards Team — Specifier (Platform Standards) ✓ OfficialDiscloses employment SynC (SynC Platform Team)

Remade from scratch under the authoring cheatsheet: control functions tied to the adopted energy code parameter, architecture and signal as independent decisions, the UL 924 override owned here with its sensing point, a trade-off note beside every choice

Showing changes from Rev 4 to Rev 5 in Lighting Controls.

−---

−title: Lighting Controls

−category: Electrical / Lighting

−toc_depth: 3

−description: >

− When to use: The building lighting control system for commercial, institutional, and industrial projects — the sensors, switches, dimmers, time switches, relay and contactor panels, photosensors, and networked or luminaire-level control equipment that turn lighting on, off, and to intermediate levels in response to occupancy, daylight, schedule, and manual command. Covers the control devices, the dimming and control interface to the luminaire driver (0–10V, DALI/DALI-2, phase-cut), networked and luminaire-level control systems, the emergency lighting control interface required by UL 924, the low-voltage control wiring, the documented sequences of operation, and the commissioning and functional testing the energy code requires.

− Not intended for: The luminaires themselves and their integral drivers and fixture-level dimming hardware (see [[sync/lighting-fixtures]]); exterior, site, and roadway lighting controls, photocontrols, and scheduling, which are covered with the exterior luminaires (see [[sync/exterior-lighting]]); the emergency and standby power sources, inverters, transfer equipment, and the egress illumination design itself (see [[sync/emergency-and-standby-power]]); integration of lighting into a building-wide control and monitoring network beyond the lighting control system's own gateway (see [[sync/building-automation-system]]); and wall switches and dimmers furnished as ordinary wiring devices where no automatic control is provided (see [[sync/wiring-devices]]).

−---

−

−# Scope {toc}

−

−## This specification covers the lighting control system — the devices and the logic that determine when and how much the building's lighting operates. {note}

−## It governs occupancy and vacancy sensors, photosensors for daylight response, time switches and astronomical schedules, manual switches and dimmers, relay and contactor panels, the dimming interface to the luminaire driver, networked and luminaire-level control systems, the emergency lighting control interface, the low-voltage control wiring, and the commissioning and functional testing that adopted energy codes require. {note}

−## The luminaires and their integral drivers are specified separately under [[sync/lighting-fixtures]]; this standard governs everything that tells those luminaires what to do. {note}

−

−## This standard is organized from the general to the specific: the administrative requirements first, then the individual control devices, then the dimming and control interface to the luminaire, then networked and luminaire-level systems, then the documented sequences of operation, then the installation and low-voltage wiring, and finally the commissioning and functional testing that closes out the work. {note}

−## The control intent — which spaces are controlled how, where sensors and switches are located, and how zones are bounded — is project-specific and is established on the contract drawings; this standard provides the framework, performance, and quality requirements that make those drawings buildable and compliant. {note}

−

−## Lighting controls are a code-compliance requirement under the adopted energy code — ANSI/ASHRAE/IES 90.1, the IECC, or in California Title 24, Part 6 — which mandates automatic shutoff, occupancy-based control, daylight-responsive control, and in many cases demand-responsive control for most interior spaces.

−

−## A lighting installation that meets every photometric and power-density target but lacks compliant controls shall not be accepted, because it does not pass plan review.

−

−## The control system shall be specified as outcomes the system is to achieve rather than as a particular manufacturer's product family.

−

−## Where lighting on the egress path is switched, dimmed, or otherwise controlled, the control of that lighting shall be overridden to full output on loss of normal power through equipment listed to UL 924, in accordance with NFPA 70 (National Electrical Code) Article 700.

−

−## The emergency and standby power sources, the inverters and transfer equipment, and the egress illumination design itself are outside this standard and shall be coordinated under [[sync/emergency-and-standby-power]].

−

−# Referenced Standards {toc}

−

−## Equipment, materials, and installation shall comply with the latest adopted edition of the following standards and codes.

−

−| Standard | Title |

−|----------|-------|

−| UL 924 | Emergency Lighting and Power Equipment |

−| UL 916 | Energy Management Equipment |

−| UL 508 | Industrial Control Equipment |

−| UL 2043 | Fire Test for Heat and Visible Smoke Release for Discrete Products in Air-Handling Spaces |

−| NFPA 70 | National Electrical Code (Articles 700 — Emergency Systems; 725 — Class 1, Class 2, and Class 3 Remote-Control, Signaling, and Power-Limited Circuits; 410 — Luminaires) |

−| NFPA 101 | Life Safety Code |

−| ANSI/ASHRAE/IES 90.1 | Energy Standard for Sites and Buildings Except Low-Rise Residential Buildings |

−| IECC | International Energy Conservation Code (Commercial Provisions, Section C405 — Electrical Power and Lighting Systems) |

−| California Title 24, Part 6 | California Building Energy Efficiency Standards |

−| ANSI C137.1 | Lighting Systems — 0–10V Dimming Interface for LED Drivers, Fluorescent Ballasts, and Controls |

−| ANSI C137.3 | Lighting Systems — Minimum Requirements for Installation of Energy Efficient Power Sources for Use with Light Emitting Diode Drivers |

−| ANSI C137.4 | Lighting Systems — Digital Interface with Auxiliary Power |

−| IEC 62386 | Digital Addressable Lighting Interface (DALI / DALI-2 / D4i) |

−| NEMA WD 7 | Occupancy Motion Sensors Standard |

−| NEMA 410 | Performance Testing for Lighting Controls and Switching Devices with Electronic Drivers and Discharge Ballasts (Inrush Current) |

−| FCC Part 15 | Radio Frequency Devices (for wireless control nodes) |

−

−## Where the contract documents, the adopted building or energy code, or a referenced standard conflict, the more stringent requirement shall govern unless the Engineer of Record directs otherwise in writing.

−

−## DesignLights Consortium (DLC) Networked Lighting Control (NLC) and Luminaire Level Lighting Control (LLLC) qualified-products lists are utility-incentive programs, not consensus standards; where this standard references them it references the program's published technical requirements as a procurement screen, not as a code requirement. {note}

−

−## The Engineer shall confirm which energy code and edition the authority having jurisdiction has adopted, because the control requirements differ materially between ASHRAE 90.1, the IECC, and Title 24.

−

−# Submittals {toc}

−

−## Action Submittals {toc}

−

−### Contractor shall submit the following for the Engineer's review prior to procurement.

−

−- Product data for each control device type — occupancy/vacancy sensors, photosensors, time switches, manual switches and dimmers, relay/contactor panels, network controllers, gateways, and power packs — including coverage patterns, ratings, and the dimming interface supported

−- A control system narrative and point-to-point wiring diagrams showing every device, its zone assignment, its power source, and its connection to the luminaire driver

−- A written sequence of operations for each space type, describing the response to occupancy, vacancy, daylight, schedule, manual override, and loss of normal power

−- A zoning and device-location plan reconciled against the reflected ceiling plan and the lighting plan

−- For networked systems, the network architecture, addressing scheme, gateway and integration points, and the commissioning and programming plan

−- For emergency lighting control, UL 924 listing documentation for each automatic load control relay, emergency control unit, or shunt device, and a diagram showing how each controlled egress luminaire is forced to full output on loss of normal power

−- A commissioning and functional-test plan describing how each required control function will be demonstrated and documented

−

−```datasheet

−label: Action Submittals Required

−type: checkbox

−options:

− - "Product data for each control device type"

− - "Control system narrative and point-to-point wiring diagrams"

− - "Written sequences of operation by space type"

− - "Zoning and device-location plan"

− - "Network architecture and commissioning/programming plan"

− - "UL 924 documentation for emergency control devices"

− - "Commissioning and functional-test plan"

−default: "Product data for each control device type"

−```

−

−### A bill of devices alone is not a sufficient submittal; the system shall be documented well enough to confirm it implements the required sequences of operation and satisfies the adopted energy code.

−

−## Closeout Submittals {toc}

−

−### Contractor shall provide the following at substantial completion.

−

−- Operation and maintenance data for each device and for the network controller, including the configuration and programming software where applicable

−- As-built control drawings, sequences of operation, and the final zone and device schedule reflecting installed conditions

−- The completed and signed functional-test (acceptance-test) documentation required by the adopted energy code, with the date, result, and tested setpoints for each control function

−- The final programmed settings — time-of-day schedules, occupancy time delays, daylight setpoints, dimming levels, and demand-response levels — recorded so the Owner can restore them after a controller replacement

−- Training records for the Owner's operating staff

−- For self-testing emergency control devices, documentation of the initial automatic test result

−

−```datasheet

−label: Closeout Submittals Required

−type: checkbox

−options:

− - "Operation and maintenance data for each device and the network controller"

− - "As-built control drawings, sequences, and final zone/device schedule"

− - "Signed functional-test (acceptance-test) documentation"

− - "Final programmed settings recorded for restoration"

− - "Training records for the Owner's operating staff"

− - "Initial automatic test result for self-testing emergency control devices"

−default:

− - "Operation and maintenance data for each device and the network controller"

− - "As-built control drawings, sequences, and final zone/device schedule"

− - "Signed functional-test (acceptance-test) documentation"

− - "Final programmed settings recorded for restoration"

− - "Training records for the Owner's operating staff"

−```

−

−# Quality Assurance {toc}

−

−## Listing and Labeling {toc}

−

−### Control devices shall be listed and labeled by a Nationally Recognized Testing Laboratory for the application in which they are installed — energy management equipment to UL 916, industrial control equipment such as relay and contactor panels to UL 508, and emergency lighting control devices to UL 924.

−

−### An unlisted control device shall not be installed regardless of its apparent quality.

−

−### The listing establishes the device's voltage, current, and environmental ratings and its fitness for the circuit it controls. {note}

−

−## Plenum-Rated Devices {toc}

−

−```datasheet

−label: Plenum-Rated Devices Required

−type: radio

−options:

− - "Not required (devices not in air-handling plenums)"

− - "Required for devices installed in air-handling plenums (UL 2043)"

−default: "Required for devices installed in air-handling plenums (UL 2043)"

−```

−

−### Control devices and power packs installed above an accessible ceiling that serves as an air-handling plenum shall be listed to UL 2043 for fire and smoke release.

−

−### Devices in the plenum airstream contribute to smoke loading in a fire, an unlisted device is a code violation in that location, and most commercial ceilings return air through the plenum, so plenum-rated devices are the common case. {note}

−

−## Manufacturer System Compatibility {toc}

−

−### All components of a given control subsystem — sensors, controllers, dimmers, and the network — shall be from a compatible product family confirmed by the manufacturer to interoperate, or shall be certified to an open interoperability standard such as DALI-2 (IEC 62386).

−

−### Compatibility shall be confirmed at submittal, not discovered in the field.

−

−### Mixing devices that share only a nominal interface name but were never tested together is the most common cause of erratic dimming, failed daylight harvesting, and a system that cannot be commissioned. {note}

−

−## Qualified Products Screening {toc}

−

−```datasheet

−label: Qualified Products Listing Required

−type: radio

−options:

− - "Not required"

− - "DLC Networked Lighting Control (NLC) listed"

− - "DLC Luminaire Level Lighting Control (LLLC) listed"

−default: "Not required"

−```

−

−### A DLC listing should be required where utility incentives are pursued.

−

−### The Engineer shall confirm the specific qualified-products list referenced by the relevant utility program.

−

−### Specifying a DLC NLC- or LLLC-listed system screens the controls against an independently verified set of capability and reporting requirements and is frequently a prerequisite for utility incentives, which can be substantial for networked controls. {note}

−

−# Energy Code Control Requirements {toc}

−

−## The adopted energy code dictates the minimum control functions for each space, and these requirements drive most of the device selections that follow. {note}

−

−## The Engineer shall confirm the adopted code and edition, because the three dominant codes differ in their thresholds and prescriptions, and the design shall meet whichever governs the project.

−

−## Applicable Energy Code {toc}

−

−```datasheet

−label: Governing Energy Code

−type: select

−options:

− - "ANSI/ASHRAE/IES 90.1"

− - "IECC (International Energy Conservation Code)"

− - "California Title 24, Part 6"

− - "Other state or local energy code"

−default: "IECC (International Energy Conservation Code)"

−```

−

−### Where the project is in California, Title 24 governs and shall be confirmed as the basis of design.

−

−### The IECC and ASHRAE 90.1 are the predominant commercial energy codes across most US jurisdictions, and a project may comply through either where both are adopted; California Title 24 is materially stricter — it mandates more space types for occupancy and daylight control, prescribes specific acceptance tests, and requires those tests be performed by a certified acceptance-test technician. {note}

−

−## Automatic Shutoff {toc}

−

−### Interior lighting in each space shall be provided with an automatic means to shut the lighting off when the space is unoccupied, accomplished by occupancy sensing, a time-of-day schedule, or a combination, in accordance with the adopted energy code.

−

−### A manual wall switch alone does not satisfy automatic shutoff.

−

−### Where a time switch is the means of shutoff, an override that returns lighting for a limited period shall be provided so occupants working after hours are not left in the dark.

−

−### The override shall affect only a limited area so that one occupant does not light an entire floor.

−

−## Occupancy and Vacancy Control {toc}

−

−### Spaces required by the energy code to have occupancy-based control shall reduce or extinguish lighting after the space is vacated within the time the code allows — generally not more than 20 minutes.

−

−### The controlled zone served by a single sensor shall not exceed the area the code permits, which the energy codes have progressively reduced.

−

−### Certain space types, notably enclosed offices, conference and meeting rooms, classrooms, restrooms, and storage rooms, are specifically required to have occupancy or vacancy control; the required space types shall be taken from the adopted code.

−

−## Daylight-Responsive Control {toc}

−

−### Lighting in daylit zones adjacent to windows (sidelit) and below skylights (toplit) shall be controlled by photosensors that reduce the electric lighting in response to available daylight, where the connected lighting load in the daylit zone exceeds the threshold the adopted code sets.

−

−### The control shall dim the daylit lighting continuously and shall be capable of reducing it to the low level the code requires.

−

−### Daylit zones that overlap shall be controlled together so that the controls do not fight one another.

−

−## Demand-Responsive Control {toc}

−

−```datasheet

−label: Automatic Demand-Responsive Control

−type: radio

−options:

− - "Not required"

− - "Required (large buildings per adopted energy code)"

−default: "Not required"

−```

−

−### Where the adopted energy code requires it — typically for buildings above a floor-area threshold — the lighting control system shall be capable of receiving a demand-response signal and automatically reducing the total building lighting power by the percentage the code prescribes without manual intervention.

−

−### Where required, the system's ability to accept the demand-response signal shall be confirmed and demonstrated.

−

−### Demand-responsive control is mandatory under Title 24 for qualifying buildings and is an option under ASHRAE 90.1 and the IECC. {note}

−

−# Control Devices {toc}

−

−## Occupancy and Vacancy Sensors {toc}

−

−### An occupancy sensor turns lighting on automatically when it detects presence and off after a vacancy delay (automatic-on). {note}

−### A vacancy sensor turns lighting on only by manual switch and off automatically after the space is vacated (manual-on, auto-off). {note}

−

−### Occupancy Control Mode {toc}

−

−```datasheet

−label: Occupancy Control Mode

−type: radio

−options:

− - "Vacancy (manual-on, automatic-off)"

− - "Occupancy (automatic-on, automatic-off)"

− - "Partial-on (automatic to a reduced level, manual to full)"

−default: "Vacancy (manual-on, automatic-off)"

−```

−

−#### Vacancy (manual-on) control should be the default for private offices, conference rooms, classrooms, and similar enclosed spaces because it both saves the most energy and satisfies the manual-on requirement that several codes place on these spaces.

−

−#### Automatic-on control is appropriate for spaces where hands-free operation is important for safety or convenience, such as restrooms, corridors, and stairwells; partial-on control automatically brings lighting to a reduced level on entry and requires a manual action for full output. {note}

−

−### Sensor Detection Technology {toc}

−

−```datasheet

−label: Sensor Detection Technology

−type: select

−options:

− - "Passive infrared (PIR)"

− - "Ultrasonic"

− - "Dual-technology (PIR + ultrasonic)"

− - "Microphonic / acoustic-assisted"

−default: "Dual-technology (PIR + ultrasonic)"

−```

−

−#### Dual-technology sensors are the appropriate default for the majority of enclosed spaces.

−

−#### Single-technology sensors should be selected only where the space clearly favors one technology and cost is a concern.

−

−#### Passive infrared sensors detect the heat motion of an occupant and require an unobstructed line of sight; they are immune to false triggering from air movement but miss small motions and occupants behind partitions. Ultrasonic sensors detect motion by Doppler shift, fill a space around obstructions, and catch small motions such as typing, but can false-trigger on airflow from diffusers. Dual-technology sensors require both signals to turn lighting on and either to hold it on, which suppresses false-on and false-off. {note}

−

−### Occupancy Vacancy Time Delay {toc}

−

−```datasheet

−label: Occupancy Vacancy Time Delay

−type: select

−unit: minutes

−options:

− - "5 minutes"

− - "10 minutes"

− - "15 minutes"

− - "20 minutes (code maximum)"

−default: "15 minutes"

−```

−

−#### The time delay shall not exceed the maximum the adopted code permits.

−

−#### The time delay is how long the sensor holds lighting on after it last detects occupancy; too short a delay produces nuisance switching that annoys occupants and stresses the driver, too long wastes the energy the control is meant to save, and a delay of about 15 minutes balances comfort against savings for most office and classroom use. {note}

−

−### Sensor Mounting and Coverage {toc}

−

−```datasheet

−label: Sensor Mounting / Coverage Type

−type: select

−options:

− - "Ceiling-mounted (360-degree)"

− - "Wall-switch replacement (integral to switch)"

− - "Wall/corner mounted (wide angle)"

− - "High-bay / aisle (long-throw)"

− - "Fixture-integral (luminaire-level)"

−default: "Ceiling-mounted (360-degree)"

−```

−

−#### The mounting type and coverage pattern shall match the geometry of the space so the entire occupied area is reliably detected without gaps or false triggers.

−

−#### Sensor type, location, and coverage shall be [[drawing: as indicated on the lighting control plan]].

−

−#### A wall-switch occupancy sensor is economical for small enclosed rooms; ceiling sensors cover open areas; long-throw sensors suit warehouse aisles and high-bay spaces; and fixture-integral sensors are part of a luminaire-level control system addressed below. {note}

−

−## Photosensors (Daylight) {toc}

−

−### Photosensor Control Method {toc}

−

−```datasheet

−label: Photosensor Control Method

−type: radio

−options:

− - "Closed-loop (measures total light at the task)"

− - "Open-loop (measures available daylight only)"

−default: "Closed-loop (measures total light at the task)"

−```

−

−#### The photosensor control method shall match the daylit zone geometry, and the sensor location shall be [[drawing: as indicated on the lighting control plan]].

−

−#### A closed-loop photosensor measures the combined daylight and electric light at the controlled surface and adjusts the electric lighting to hold a target level, and is the common choice for an interior daylit zone; an open-loop photosensor measures incoming daylight only, away from the influence of the electric lighting it controls, and is suited to large toplit areas and skylight wells where a single sensor governs many luminaires. {note}

−

−### Daylight Response {toc}

−

−```datasheet

−label: Daylight Response

−type: radio

−options:

− - "Continuous dimming"

− - "Stepped switching"

−default: "Continuous dimming"

−```

−

−#### Continuous dimming is the appropriate default and is required by most codes for the primary daylit zone; stepped control may be acceptable only in secondary daylit areas or where the code permits it.

−

−#### Continuous dimming smoothly reduces the electric lighting as daylight rises and is far less noticeable to occupants than stepped switching, which changes light in visible increments and can be distracting. {note}

−

−## Time Switches and Scheduling {toc}

−

−```datasheet

−label: Scheduling Control Type

−type: select

−options:

− - "Astronomical time switch (tracks sunrise/sunset)"

− - "7-day programmable time switch"

− - "Networked schedule (central controller)"

− - "Not used (occupancy-based shutoff only)"

−default: "Networked schedule (central controller)"

−```

−

−### Where schedule control is the means of shutoff, a manual local override of limited duration and limited area shall be provided as required by the energy code.

−

−### Schedule-based control turns lighting off during programmed unoccupied hours and is one of the accepted means of automatic shutoff; a networked schedule maintained at a central controller is the practical default for any building with a control network, while a standalone programmable time switch is appropriate for small projects without a network. {note}

−

−## Manual Switches and Dimmers {toc}

−

−### Each enclosed space shall have a readily accessible manual control that allows occupants to turn the lighting off and, where the space is dimmable, to reduce it, in addition to and independent of the automatic controls, as required by the energy code.

−

−### Ordinary wall switches and dimmers furnished where no automatic control is associated with them are wiring devices specified under [[sync/wiring-devices]]; this standard governs manual controls that are part of, or interface with, the automatic control system.

−

−### Manual control gives occupants the ability to turn lighting off when the automatic controls would leave it on, which both saves energy and satisfies the manual-control mandate. {note}

−

−### Manual Dimming Control Type {toc}

−

−```datasheet

−label: Manual Dimming Control Type

−type: select

−options:

− - "Manual low-voltage dimmer (to driver dimming input)"

− - "Manual line-voltage (phase-cut) dimmer"

− - "Digital wall station (networked / DALI)"

− - "On/off switch only (non-dimming spaces)"

−default: "Digital wall station (networked / DALI)"

−```

−

−#### A line-voltage phase-cut dimmer is used only where the luminaire driver is controlled directly from the line-voltage wall control and shall be confirmed compatible with the driver.

−

−#### An on/off switch is appropriate only where the energy code permits non-dimming control.

−

−#### In a space with dimmable luminaires and a networked or digital control system, a digital wall station that commands the controller is preferred because it allows scenes, multi-zone control, and reprogramming without rewiring; a low-voltage manual dimmer that drives the luminaire's 0–10V input directly suits a simple standalone dimmable space. {note}

−

−## Relay and Contactor Panels {toc}

−

−```datasheet

−label: Relay / Contactor Panel Use

−type: radio

−options:

− - "Not used (control at device / driver level)"

− - "Used for branch-circuit switching of zones"

−default: "Used for branch-circuit switching of zones"

−```

−

−### The relay or contactor panel shall be listed to UL 508.

−

−### The panel's relays shall be rated for the inrush current of the LED driver loads they switch in accordance with NEMA 410.

−

−### Relay panel locations and zone-to-circuit assignments shall be [[drawing: as indicated on the lighting control plan and panel schedules]].

−

−### A relay or contactor panel switches whole branch circuits on and off under the command of the control system and is the means of switching large zones, exterior and parking circuits, and non-dimmed loads; LED drivers draw a high momentary inrush that welds relay contacts not rated for it. {note}

−

−# Dimming and Control Interface {toc}

−

−## The control interface is the electrical means by which a control device commands the luminaire's driver to a light level. {note}

−## It is the boundary between this standard and [[sync/lighting-fixtures]]: the luminaire's driver provides the dimming input, and the control system provides the signal to it. {note}

−

−## The interface selected here shall match the dimming input specified for the luminaire so the two are compatible, because a control system and a driver that speak different protocols cannot be made to dim together.

−

−## Control Interface Protocol {toc}

−

−```datasheet

−label: Lighting Control Interface

−type: select

−options:

− - "0-10V analog (ANSI C137.1)"

− - "DALI / DALI-2 (IEC 62386)"

− - "Phase-cut (forward/reverse)"

− - "Networked / proprietary digital with gateway"

− - "Integral wireless control"

−default: "0-10V analog (ANSI C137.1)"

−```

−

−### The 0–10V analog interface (ANSI C137.1) is the default for commercial interior LED control.

−

−### DALI/DALI-2 (IEC 62386) should be specified where individual addressable control, software grouping, scene control, and two-way driver feedback and diagnostics are required, as in reconfigurable open offices and tunable spaces.

−

−### Phase-cut control may be used where the luminaire is dimmed from an existing line-voltage wall dimmer, but it is more prone to flicker, audible buzz, and dimmer-driver incompatibility and is not preferred for new commercial work.

−

−### The interface shall match the driver dimming input specified under [[sync/lighting-fixtures]].

−

−### The 0–10V interface is simple, low-cost, and universally supported but is one-way with no feedback, each zone needs its own control pair, and it does not address individual luminaires; DALI is bidirectional, polarity-insensitive, and supports up to 64 control devices on a bus, and DALI-2 certification confirms cross-manufacturer interoperability. {note}

−

−## Minimum Controlled Dimming Level {toc}

−

−```datasheet

−label: Minimum Controlled Dimming Level

−type: select

−unit: percent of full output

−options:

− - "10% (standard commercial)"

− - "5% (offices, conference, hospitality)"

− - "1% (theaters, lecture, premium hospitality)"

−default: "10% (standard commercial)"

−```

−

−### A deeper minimum of 5 percent or 1 percent should be specified for conference rooms, auditoria, and hospitality where low-light scenes are expected.

−

−### The control device and the driver shall be confirmed compatible at the specified low end.

−

−### The minimum controlled level is the lowest output the control system and driver together can reach smoothly without flicker or dropout; a 10 percent minimum is adequate for general commercial spaces, and the achievable minimum is a property of the pair, not of either alone, so a control system that commands 1 percent against a driver that bottoms out at 10 percent will not deliver the scene. {note}

−

−## Color-Tuning Control {toc}

−

−```datasheet

−label: Color-Tuning Control

−type: radio

−options:

− - "Not required (fixed CCT)"

− - "Tunable white (independent CCT and intensity control)"

−default: "Not required (fixed CCT)"

−```

−

−### Where the luminaires are color-tunable, the control system shall provide the additional channels needed to command color temperature independently of intensity.

−

−### Color-tuning control is required only where tunable-white or warm-dim luminaires are specified under [[sync/lighting-fixtures]], such as in healthcare, education, and circadian-lighting applications; a single 0–10V pair cannot command color temperature independently, which is the principal reason DALI or a multi-channel networked system is selected for tunable spaces. {note}

−

−# Networked and Luminaire-Level Lighting Control {toc}

−

−## A networked lighting control (NLC) system connects the control devices, luminaires, and controllers on a digital network so that zones, schedules, sensor responses, and dimming levels are configured and reconfigured in software rather than by rewiring. {note}

−

−## Networked control is increasingly the practical means of meeting the layered control requirements of current energy codes, of accepting a demand-response signal, and of reporting energy use, and it is a prerequisite for the utility incentives available to NLC and LLLC systems. {note}

−

−## Control System Architecture {toc}

−

−```datasheet

−label: Control System Architecture

−type: select

−options:

− - "Standalone / room-based (no network)"

− - "Networked wired (digital bus)"

− - "Networked wireless (mesh)"

− - "Luminaire-level lighting control (LLLC)"

−default: "Networked wired (digital bus)"

−```

−

−### A networked wireless mesh shall use devices compliant with FCC Part 15.

−

−### The architecture shall be coordinated with the project's control intent and incentive strategy.

−

−### A standalone, room-based system is appropriate for small projects and tenant fit-outs where no central management is needed; a networked wired system is robust and free of radio-frequency concerns but requires control wiring throughout; a networked wireless mesh reduces control wiring and eases reconfiguration but depends on radio coverage; and luminaire-level lighting control places an occupancy sensor, a photosensor, and a controller in or on each luminaire so that every fixture is its own control zone, providing the finest-grained control and the greatest measured savings at a higher device cost. {note}

−

−## Network Integration {toc}

−

−```datasheet

−label: Building Network Integration

−type: radio

−options:

− - "Standalone (no external integration)"

− - "Integrated with building automation / management system"

−default: "Standalone (no external integration)"

−```

−

−### Where the lighting control system must report to or take commands from a building-wide control and monitoring system, integration shall be through a documented gateway and open protocol, and the points exchanged shall be coordinated with [[sync/building-automation-system]].

−

−### The lighting control system shall retain full local control of all life-safety and code-required functions independent of the building management network, so that a failure or outage of the building network does not disable required lighting control or emergency operation.

−

−## Low-Voltage Control Power {toc}

−

−```datasheet

−label: Control Circuit Class

−type: radio

−options:

− - "Class 2 (low-voltage, power-limited per NEC 725)"

− - "Class 1 (where required by device or distance)"

−default: "Class 2 (low-voltage, power-limited per NEC 725)"

−```

−

−### Class 1 wiring shall be used only where a device's power demand or the circuit length requires it.

−

−### The class of every control circuit shall be confirmed against Article 725 and the wiring methods kept consistent with that class throughout.

−

−### Most lighting control wiring is Class 2 power-limited wiring under NFPA 70 Article 725, supplied by a listed power pack or controller, which simplifies installation and reduces shock and fire risk. {note}

−

−# Emergency Lighting Control {toc}

−

−## Lighting that serves the means of egress is frequently switched, dimmed, or scheduled along with the general lighting, but it shall never be left off when normal power fails.

−

−## NFPA 70 Article 700 requires that any control on an emergency or egress luminaire be overridden so the luminaire goes to full output on loss of normal power, regardless of the position of any switch, dimmer, occupancy sensor, or schedule, accomplished with a device listed to UL 924.

−

−## Emergency Control Device {toc}

−

−```datasheet

−label: Emergency Lighting Control Device

−type: select

−options:

− - "None (egress lighting not switched/dimmed)"

− - "Automatic load control relay (UL 924)"

− - "Emergency control unit / shunt relay (UL 924)"

− - "UL 924-listed function within networked control system"

−default: "Automatic load control relay (UL 924)"

−```

−

−### Where the egress lighting is not switched or dimmed, no emergency control device is needed; where the lighting control network itself is UL 924 listed for this function, that listed capability may serve in place of a discrete relay.

−

−### The device shall be located and connected so it senses the normal power that serves the area it protects.

−

−### An automatic load control relay (ALCR) — a UL 924-listed device commonly called a shunt relay — monitors normal power and bypasses the local control to drive the controlled egress luminaire to full output when normal power is lost, locking out occupancy, dimming, and switching until normal power returns, and is the standard means of allowing an egress luminaire to be controlled like any other fixture during normal operation while guaranteeing it cannot be dark in an emergency. {note}

−

−## Transfer Timing {toc}

−

−### The emergency control device shall force the controlled egress lighting to full output within the time NFPA 101 and the adopted code require following loss of normal power, and shall return control to the normal control system only after normal power is restored and stable.

−

−### The device shall monitor the normal power source for the area it serves, not merely the presence of power at the device, so that a localized loss of the normal circuit is detected.

−

−### The egress illumination levels, the emergency power source, and the duration are a design responsibility outside this standard and shall be coordinated with [[sync/emergency-and-standby-power]].

−

−## Self-Testing {toc}

−

−```datasheet

−label: Emergency Control Self-Test

−type: radio

−options:

− - "Manual test only"

− - "Self-testing / self-diagnostic"

−default: "Manual test only"

−```

−

−### Self-testing should be specified for installations with many distributed emergency control devices.

−

−### A self-testing emergency control device automatically exercises its transfer function on the periodic schedule the code requires and signals a fault, relieving the Owner of manual testing, which for dispersed relays is labor-intensive and frequently neglected. {note}

−

−# Sequences of Operation {toc}

−

−## The sequence of operation is the written description of how the lighting in each space responds to occupancy, vacancy, daylight, schedule, manual command, and loss of normal power. {note}

−

−## It is the heart of the controls specification: the devices are only the means, and a system installed exactly to the device schedule but programmed to the wrong sequence does not meet the design intent or the code. {note}

−

−## Documented Sequences Required {toc}

−

−### A written sequence of operation shall be provided for each space type and control zone, and the system shall be programmed and commissioned to implement it.

−

−### Each sequence shall state the automatic-on or manual-on behavior, the vacancy time delay, the daylight response and setpoints, the schedule and override behavior, the manual-control behavior, and the emergency override behavior.

−

−### The space-by-space sequences and zone assignments shall be [[drawing: as indicated on the lighting control plan and sequence-of-operations schedule]], because which spaces are controlled how is project-specific and is established by the design.

−

−## Override and Manual Control Behavior {toc}

−

−### Each automatic sequence shall define how a manual override interacts with it — how long an after-hours override holds lighting on, what area the override affects, and whether the automatic controls resume after the override expires.

−

−### Overrides shall be limited in time and area as the energy code requires, so that a single occupant's override cannot defeat the automatic shutoff for an entire floor or for the remainder of the day.

−

−# Installation {toc}

−

−## Coordination with Ceiling and Luminaires {toc}

−

−### The Contractor shall coordinate the location of ceiling-mounted sensors, photosensors, and wall stations with the reflected ceiling plan, the luminaire layout, and the furniture and partition plan before rough-in, so that sensors have the required coverage and are not blocked by ductwork, structure, partitions, or tall furniture.

−

−### Devices shall be installed level, aligned, and at the locations shown.

−

−### A sensor placed without regard to obstructions and air movement is the most common cause of a control system that fails its functional test. {note}

−

−## Sensor Placement and Aiming {toc}

−

−### Occupancy sensors shall be located and aimed so their coverage pattern includes the entire occupied area without extending into adjacent spaces or corridors where it would falsely hold lighting on.

−

−### Ultrasonic sensors shall be kept away from supply-air diffusers whose airflow can false-trigger them.

−

−### Photosensors shall be located so they sense the daylight or task surface they are intended to regulate and are shielded from direct view of the luminaires they control and from spill light from adjacent zones.

−

−## Low-Voltage Control Wiring {toc}

−

−### Class 2 control wiring shall be installed in accordance with NFPA 70 Article 725, separated from line-voltage power wiring as required by the code and the device manufacturer, and supported independently of luminaires and ductwork.

−

−### Control conductors shall be of the type and size the manufacturer requires for the run length so that voltage drop on the 0–10V or low-voltage signal does not corrupt the control level.

−

−### Wiring methods and raceway shall comply with [[sync/conductors-and-cables]] and [[sync/raceways-and-conduit]]; line-voltage circuits switched by the controls shall be installed under those standards.

−

−## Grounding and Bonding {toc}

−

−### Control panels, network controllers, and metal device enclosures shall be grounded and bonded in accordance with [[sync/grounding-and-bonding]].

−

−### Shielded control cabling, where used, shall be grounded at one end only as the manufacturer directs, because grounding a shield at both ends creates a ground loop that injects noise into the control signal.

−

−## Labeling and Identification {toc}

−

−### Each control device, relay, controller, and zone shall be labeled to identify the circuits and zones it controls, and the labeling shall agree with the as-built control drawings and zone schedule.

−

−### Labeling and identification shall be consistent with [[sync/equipment-labeling]].

−

−### Unlabeled controls are uncommissionable and unmaintainable, because no one can later determine which device governs which lighting. {note}

−

−# Commissioning and Functional Testing {toc}

−

−## The adopted energy code requires that the lighting controls be functionally tested — verified to be installed correctly, calibrated, and operating as the sequences of operation describe — before the building is accepted. {note}

−

−## The work is not complete until this testing is performed, documented, and accepted, because a control that is installed but mis-calibrated saves no energy and may not comply.

−

−## ASHRAE 90.1 and the IECC call this functional testing; California Title 24 calls it acceptance testing and, unlike the model codes, requires it be performed by a certified acceptance-test technician working under a certified employer. {note}

−

−## Functional Test Scope {toc}

−

−```datasheet

−label: Functional Test Documentation

−type: checkbox

−options:

− - "Occupancy/vacancy sensor operation and time delay verified per zone"

− - "Daylight photosensor setpoint and dimming response verified"

− - "Time-of-day schedule and after-hours override verified"

− - "Manual switching and dimming verified per zone"

− - "Demand-response reduction verified (where required)"

− - "Emergency override to full output on power loss verified (UL 924)"

− - "Calibration setpoints and programmed values recorded"

−default: "Occupancy/vacancy sensor operation and time delay verified per zone"

−```

−

−### The Contractor shall demonstrate and document each required control function: that occupancy and vacancy sensors turn lighting on and off correctly and hold for the programmed delay; that daylight photosensors dim the electric lighting in response to daylight and hold the design level; that schedules turn lighting off and that overrides behave as specified; that manual controls operate each zone; that demand-response reduction occurs where required; and that the emergency control forces egress lighting to full output on a simulated loss of normal power.

−

−### The tested setpoints and the result of each test shall be recorded.

−

−## Daylight Sensor Calibration {toc}

−

−### Daylight-responsive photosensors shall be calibrated under representative daylight and electric-light conditions so that the controlled lighting holds the design level as daylight varies.

−

−### The calibration shall be verified by measurement, not assumed from the factory setting.

−

−### Daylight controls that are installed but never calibrated are a frequent finding and deliver none of the savings the code anticipates, because an uncalibrated sensor either fails to dim or dims so aggressively that occupants override it. {note}

−

−## Acceptance-Test Certification {toc}

−

−```datasheet

−label: Acceptance-Test Certification

−type: radio

−options:

− - "Functional test by qualified installer/commissioning agent"

− - "Certified acceptance-test technician (Title 24 jurisdictions)"

−default: "Functional test by qualified installer/commissioning agent"

−```

−

−### In jurisdictions governed by California Title 24, the acceptance testing shall be performed by a certified Lighting Control Acceptance Test Technician under a certified employer, and the signed certificate shall be submitted as a condition of occupancy.

−

−### In jurisdictions under ASHRAE 90.1 or the IECC, the functional testing may be performed by a qualified installer or the commissioning agent, and the documented results submitted to the authority having jurisdiction; the testing is no less required, only less prescriptive.

−

−## Owner Training {toc}

−

−### The Contractor shall train the Owner's operating staff in the operation, adjustment, and basic troubleshooting of the control system, including how to change schedules, adjust setpoints, and add or move zones in a networked system.

−

−### Training is essential because a control system that the Owner cannot adjust will be overridden, disabled, or left in a non-compliant state the first time the building's use changes. {note}

−

−# Warranty {toc}

−

−```datasheet

−label: Control System Warranty Period

−type: select

−options:

− - "1 year from substantial completion"

− - "2 years from substantial completion"

− - "5 years from substantial completion"

−default: "2 years from substantial completion"

−```

−

−## The control devices, controllers, and network shall be warranted against defects in materials and workmanship for the warranty period, and the warranty shall include the manufacturer's support for the programming and configuration software.

−

−## A one-year warranty is the minimum; a longer warranty should be specified for networked systems, where the controller and software support are the components most likely to need vendor attention after installation.

−

−# Spare Parts {toc}

−

−```datasheet

−label: Spare Parts

−type: checkbox

−options:

− - "Spare occupancy/vacancy sensors (per type)"

− - "Spare photosensors (per type)"

− - "Spare power packs / relays (per type)"

− - "Spare wall stations / dimmers (per type)"

− - "Spare network controller / gateway"

−default: "Spare power packs / relays (per type)"

−```

−

−## The Contractor shall furnish spare devices matching the installed types so the Owner can replace a failed device without re-engineering or a long lead time.

−

−## Spare power packs and relays are the highest-value spare because they switch load and fail more often than sensors; a spare network controller or gateway should be furnished for a networked system whose product line may change, since a controller mismatch can require reprogramming the whole system. {note}

+---

+title: Lighting Controls

+category: Electrical / Lighting

+description: >

+ When to use: The interior lighting control system of a commercial, institutional, or industrial building: the occupancy and vacancy sensors, daylight sensors, time schedules, manual control stations, relay panels, lighting contactors, lighting-control panelboards, room controllers, networked and luminaire-level control systems, and the management software that together decide when each luminaire is on, off, or at an intermediate level. Covers the control architecture and its network, the control signal and protocol delivered to the luminaire driver and the minimum light level the system commands, occupancy and vacancy sensing, daylight-responsive control, time scheduling and override, manual control, branch-circuit switching equipment, automatic receptacle control, demand-responsive control, the interfaces to the building automation system, motorized shades, and other building systems, the UL 924 override device that returns a controlled egress luminaire to full output, the low-voltage control wiring, the documented sequences of operation, startup, programming, functional testing, training, warranty, and spares.

+ Not intended for: The luminaires, their LED drivers, and the driver's response to a control signal, which are properties of the luminaire (see [[sync/lighting-fixtures]]); photocontrols, time-based control, and control zoning of exterior, site, parking-structure, and building-mounted area lighting (see [[sync/exterior-lighting]]); the egress illumination design, the unit equipment, battery packs, inverters, and exit signs that provide it, and the emergency power source (see [[sync/emergency-and-egress-lighting]]); the classification of emergency loads, the generator, the transfer switches, and the emergency distribution (see [[sync/emergency-and-standby-power]]); the controllers, network, programming, graphics, and mechanical-system supervision of the building automation system (see [[sync/building-automation-system]]); detection devices that provide an occupied signal to an HVAC zone controller and to nothing else (see [[sync/hvac-controls-instrumentation]]); the cabinet, bus, main device, ratings, and ordinary branch devices of any panelboard, including one built as a lighting-control panelboard (see [[sync/panelboards]]); the motorized shades, their motors, shade-side controllers, and the gateway through which they accept commands (see [[sync/window-treatments]]); wall switches, wall-box dimmers, and wall-box occupancy sensors installed as stand-alone wiring devices with no connection to a control system (see [[sync/wiring-devices]]); the line-voltage conductors, raceways, and grounding that serve the controlled circuits (see [[sync/conductors-and-cables]], [[sync/raceways-and-conduit]], [[sync/grounding-and-bonding]]); theatrical, stage, and performance dimming systems; and horticultural and germicidal lighting control.

+---

+# Scope {toc}

+## This standard governs the equipment and the logic that decide when the interior lighting of a building operates and at what level: the sensors that detect people and daylight, the schedules and manual stations that command the lighting, the relays, contactors, remotely operated breakers, and room controllers that switch and dim it, the network that connects them, and the software that holds their configuration. {note}

+## The standard treats the control system as a set of independent decisions rather than as one product: the architecture and its network medium, the control signal delivered to each luminaire, the sensing and scheduling functions applied to each space, the switching equipment, the interfaces to other building systems, and the emergency override. Every combination of these selections is manufactured, and this standard does not assume that one selection implies another. {note}

+## The control intent for each space, meaning which functions apply to it, where its sensors and stations sit, and how its zones are bounded, is a design decision recorded on the contract drawings; this standard supplies the performance, product, wiring, and testing requirements that make that intent buildable, verifiable, and compliant with the adopted energy code. {note}

+## The following are governed elsewhere and are outside this standard: {note}

+- the luminaires, their drivers, and the driver's dimming input as a luminaire component ([[sync/lighting-fixtures]])

+- the photocontrols, schedules, and zoning of exterior and site lighting ([[sync/exterior-lighting]])

+- the egress illumination design, the emergency luminaires, unit equipment, inverters, and exit signs ([[sync/emergency-and-egress-lighting]])

+- the emergency power system, its load classification, the generator, and the transfer switches ([[sync/emergency-and-standby-power]])

+- the building automation system as a product and the sequences it runs for mechanical equipment ([[sync/building-automation-system]])

+- the occupancy sensors furnished for HVAC zone control alone ([[sync/hvac-controls-instrumentation]])

+- the panelboard assembly that houses remotely operated breakers ([[sync/panelboards]])

+- the motorized shades, their motors, and the shade-side gateway ([[sync/window-treatments]])

+- stand-alone wall switches, dimmers, and wall-box sensors with no system connection ([[sync/wiring-devices]])

+- the branch circuits, raceways, and grounding of the controlled lighting ([[sync/conductors-and-cables]], [[sync/raceways-and-conduit]], [[sync/grounding-and-bonding]])

+- the identification products applied to electrical equipment ([[sync/equipment-labeling]])

+## The Contractor shall coordinate the control signal, the luminaire driver, the emergency override, the shade interface, and the building automation interface with the standards named in this section before any control equipment or luminaire is released for procurement.

+# Referenced Standards {toc}

+## Equipment, materials, and installation shall comply with the latest adopted edition of each of the following unless a specific edition is cited.

+## Where the contract documents, the Authority Having Jurisdiction, or two referenced standards impose conflicting requirements, the more stringent requirement shall govern unless the Engineer of Record directs otherwise in writing.

+| Standard | Title |

+|----------|-------|

+| NFPA 70 | National Electrical Code (Articles 404, 410, 700, 725, and 726) |

+| NFPA 101 | Life Safety Code (Section 7.9) |

+| ANSI/ASHRAE/IES 90.1 | Energy Standard for Sites and Buildings Except Low-Rise Residential Buildings (Section 9) |

+| IECC | International Energy Conservation Code (Section C405) |

+| California Title 24, Part 6 | Building Energy Efficiency Standards |

+| UL 916 | Energy Management Equipment |

+| UL 508 | Industrial Control Equipment |

+| UL 924 | Emergency Lighting and Power Equipment |

+| UL 1472 | Solid-State Dimming Controls |

+| UL 67 | Panelboards |

+| UL 2043 | Fire Test for Heat and Visible Smoke Release for Discrete Products and Their Accessories Installed in Air-Handling Spaces |

+| ANSI C137.1 | Lighting Systems: 0–10 V Dimming Interface for LED Drivers, Fluorescent Ballasts, and Controls |

+| ANSI C137.4 | Lighting Systems: Digital Interface with Auxiliary Power |

+| IEC 62386 | Digital Addressable Lighting Interface (DALI-2 and D4i) |

+| NEMA WD 7 | Occupancy Motion Sensors Standard |

+| NEMA 410 | Performance Testing for Lighting Controls and Switching Devices with Electronic Drivers and Discharge Ballasts |

+| ANSI/IES LP-6 | Lighting Control Systems: Properties, Selection, and Specification |

+| ANSI/IES LP-16 | Documenting Control Intent Narratives and Sequences of Operation |

+| ASHRAE 135 | BACnet, A Data Communication Protocol for Building Automation and Control Networks |

+| OpenADR 2.0b | Open Automated Demand Response Profile Specification |

+| IEEE 802.3 | Ethernet (Power over Ethernet clauses) |

+| 47 CFR Part 15 | Federal Communications Commission Rules, Radio Frequency Devices |

+| DLC NLC | DesignLights Consortium Networked Lighting Controls Technical Requirements |

+## The DesignLights Consortium technical requirements are a utility incentive program rather than a consensus standard; where this standard references them it references the published capability requirements as a procurement screen, and nothing in them is a code requirement. {note}

+# Submittals {toc}

+## Action Submittals {toc}

+### The Contractor shall submit the following for review before any lighting control equipment is procured:

+- product data for each control device, controller, relay panel, contactor, lighting-control panelboard controller, power pack, gateway, and wall station, identifying the listing, the input voltage, the load rating, the control signal supported, the sensor coverage pattern, and the environmental rating of each

+- a system architecture diagram showing every controller, gateway, network segment, and power supply, the communication medium of each segment, and the connection to the building automation system, the shade system, and any other system interfaced

+- a control device layout on the lighting plans showing every sensor with its coverage pattern, every wall station, every room controller, and every relay panel, reconciled against the luminaire layout and the ceiling plan

+- point-to-point wiring diagrams for each control zone type showing the control signal to each luminaire type, the sensor and station connections, and the power source of every device

+- a written sequence of operation for each space type in the format required under this standard

+- the zone schedule listing every control zone, the luminaires and receptacles it contains, the sensors and stations that command it, and the relay or controller output that switches it

+- the compatibility statement between the control system and each luminaire driver type, at the control signal and the minimum light level selected under this standard

+- for each UL 924 override device, the listing, the wiring diagram showing the normal source it senses, and the luminaires it returns to full output

+- the network design, addressing plan, and the cybersecurity configuration required under this standard, where the system is networked

+- the functional test plan required under this standard

+```datasheet

+label: Action Submittals

+type: checkbox

+options:

+ - "Product data for every control device and controller"

+ - "System architecture diagram"

+ - "Control device layout with sensor coverage patterns"

+ - "Point-to-point wiring diagrams by zone type"

+ - "Sequences of operation by space type"

+ - "Zone schedule"

+ - "Driver compatibility statement"

+ - "UL 924 override device documentation"

+ - "Network design and cybersecurity configuration"

+ - "Functional test plan"

+default:

+ - "Product data for every control device and controller"

+ - "Control device layout with sensor coverage patterns"

+ - "Point-to-point wiring diagrams by zone type"

+ - "Sequences of operation by space type"

+ - "Zone schedule"

+ - "Driver compatibility statement"

+ - "UL 924 override device documentation"

+ - "Functional test plan"

+```

+### Lighting control equipment and the luminaires it controls shall not be procured until the action submittals covering the control signal and the driver compatibility have been reviewed and returned.

+### A bill of devices is the submittal that most often comes back deficient, because a list of listed products proves nothing about whether the sensors cover the rooms, whether the controller can drive the luminaires furnished, or whether the sequences the code requires are the sequences the system will run. {note}

+## Informational Submittals {toc}

+### The Contractor shall submit the following with or before the action submittals:

+- the installer and programmer qualification statements required under Quality Assurance

+- the manufacturer's certification that the products offered satisfy the utility program qualification selected under this standard, where one is selected

+- the radio frequency survey or site plan showing the planned locations of wireless devices and gateways, where the system is wireless

+- the manufacturer's published software support policy, stating the period for which firmware and software updates are provided and the terms of any subscription

+```datasheet

+label: Informational Submittals

+type: checkbox

+options:

+ - "Installer and programmer qualification statements"

+ - "Utility program qualification certification"

+ - "Wireless device and gateway location plan"

+ - "Software support policy"

+default:

+ - "Installer and programmer qualification statements"

+ - "Software support policy"

+```

+## Closeout Submittals {toc}

+### The Contractor shall submit the following before the lighting control system is accepted:

+- the completed functional test report, recording for every control zone the test date, each function tested, the result, and the final setting of every time delay, daylight setpoint, level, and schedule

+- as-built control drawings, the as-built zone schedule, and the as-built sequences of operation reflecting installed conditions

+- a configuration backup of every controller and of the management software in a form from which the system can be restored after a controller replacement, together with the software, licenses, and credentials the Owner needs to open it

+- operation and maintenance data for every device and for the management software, including the procedure for changing a schedule, adjusting a setpoint, replacing a device, and adding a zone

+- the training record for the Owner's operating staff

+- the warranty documentation for the equipment and for the software support

+- a signed receipt from the Owner for the spare parts delivered

+```datasheet

+label: Closeout Submittals

+type: checkbox

+options:

+ - "Functional test report with final settings"

+ - "As-built control drawings, zone schedule, and sequences"

+ - "Configuration backup, software, licenses, and credentials"

+ - "Operation and maintenance data"

+ - "Training record"

+ - "Warranty documentation"

+ - "Spare parts receipt"

+default:

+ - "Functional test report with final settings"

+ - "As-built control drawings, zone schedule, and sequences"

+ - "Configuration backup, software, licenses, and credentials"

+ - "Operation and maintenance data"

+ - "Training record"

+ - "Warranty documentation"

+```

+### The configuration backup is the closeout item whose absence costs the Owner most, because a networked system whose controller fails without a backup is reprogrammed from the sequences by hand, and a system whose credentials left with the installer cannot be opened at all. {note}

+# Quality Assurance {toc}

+## Listing and Labeling {toc}

+### Every control device, controller, power pack, relay panel, and gateway shall be listed and labeled by a Nationally Recognized Testing Laboratory for its application: energy management equipment to UL 916, industrial control equipment to UL 508, solid-state dimming controls to UL 1472, and emergency lighting control equipment to UL 924.

+### A device that switches or dims a lighting load shall be listed for the load type it controls and for the inrush current of that load, tested in accordance with NEMA 410.

+### Wireless control devices shall comply with 47 CFR Part 15 and shall carry the Federal Communications Commission identifier on the device.

+### The listing establishes the voltage, current, and environmental ratings of a device and its fitness for the circuit it controls, and NEMA 410 exists because an LED driver draws a momentary inrush many times its running current, which welds the contacts of a relay rated for its running current alone. {note}

+## System Interoperability {toc}

+### The interoperability basis of the control system shall be as indicated in the datasheet.

+```datasheet

+label: System Interoperability Basis

+type: radio

+options:

+ - "Single manufacturer's product family throughout"

+ - "Open-protocol devices from more than one manufacturer, certified interoperable"

+```

+### A single-manufacturer system is commissioned and supported by one party and its devices are tested together before they are sold, so a failed daylight loop or an erratic dimmer has one responsible manufacturer; an open-protocol system lets the luminaire manufacturer furnish the sensor and the controls manufacturer furnish the head-end, and holds its value when one of them leaves the market, at the cost of an interoperability certification that has to be checked device by device. {note}

+### Where the open-protocol basis is selected, every device on a shared bus shall be certified to the same version of the protocol by the certifying body, and the certification shall be identified in the submittal.

+### Where the single-manufacturer basis is selected, every sensor, station, controller, power pack, and gateway of the system shall be a product of one manufacturer or shall be listed by that manufacturer as a component of its system.

+### Compatibility between the control system and every luminaire driver type on the project shall be confirmed in the submittal at the control signal and the minimum light level selected under this standard, and shall not be left to be discovered at startup.

+## Utility Program Qualification {toc}

+### The utility program qualification required of the control system shall be as indicated in the datasheet.

+```datasheet

+label: Utility Program Qualification

+type: radio

+options:

+ - "Not required"

+ - "Listed on the DesignLights Consortium Networked Lighting Controls qualified products list"

+default: "Not required"

+```

+### Most projects claim no incentive for the control system and carry no qualification requirement, which is why the field defaults to none; a qualified-products listing is required where the Owner pursues a utility incentive that names the list, and it screens the system against a published set of capabilities, among them networked sensing, scheduling, high-end trim, and energy monitoring, that some product families do not offer. {note}

+### Where a qualification is required, the Contractor shall confirm with the utility program the version of the list in force at the date of the incentive application, and shall furnish a system listed on that version.

+## Installer and Programmer Qualifications {toc}

+### The installer shall have completed lighting control installations of the architecture selected under this standard on not fewer than the number of projects indicated in the datasheet.

+```datasheet

+label: Minimum Installer Comparable Projects

+type: range

+unit: projects

+options:

+ min: 0

+ max: 10

+ setpoints: [0, 1, 3, 5, 10]

+default: 3

+```

+### The party that performs startup and programming of the control system shall be as indicated in the datasheet.

+```datasheet

+label: Startup and Programming Performed By

+type: radio

+options:

+ - "Manufacturer's factory-authorized technician"

+ - "Installing Contractor's manufacturer-trained technician"

+ - "Owner's controls integrator"

+```

+### A stand-alone room-based system is programmed at each device and any trained installer configures it; a networked system is programmed in software whose tools the manufacturer controls, and factory startup is where the manufacturer's warranty on the software usually begins, so the three parties trade the cost of a factory visit against who carries responsibility when a zone does not behave as the sequence says. {note}

+### Whoever performs the programming shall hold the manufacturer's current training credential for the software furnished, and the credential shall be identified in the qualification statement.

+# Environmental and Service Conditions {toc}

+## Control Panel Enclosure {toc}

+### Relay panels, lighting contactor enclosures, controller enclosures, and gateway enclosures shall be of the enclosure type indicated in the datasheet.

+```datasheet

+label: Control Panel Enclosure Type

+type: select

+options:

+ - "NEMA Type 1"

+ - "NEMA Type 2"

+ - "NEMA Type 3R"

+ - "NEMA Type 4"

+ - "NEMA Type 4X"

+ - "NEMA Type 12"

+default: "NEMA Type 1"

+```

+### A dry electrical room or a closet inside the conditioned envelope is where control panels are installed on most projects, which is why Type 1 is the default; the harsher locations named in the clauses that follow require the higher type at that location, and the rest of the project is not upgraded with it. {note}

+### A control panel installed outdoors or in a wet location shall have an enclosure of NEMA Type 3R, Type 4, or Type 4X.

+### A control panel installed where it is exposed to wash-down, salt air, chemical vapor, or another corrosive agent shall have an enclosure of NEMA Type 4X.

+### A control panel installed where dust, lint, or dripping non-corrosive liquid is present shall have an enclosure of NEMA Type 12, Type 4, or Type 4X.

+### Where the enclosure type these clauses require exceeds the datasheet selection at an installed location, the higher type shall be furnished at that location and the conflict reported to the Engineer of Record before procurement.

+## Device Location Ratings {toc}

+### Sensors, power packs, room controllers, and wireless nodes installed above a ceiling that serves as an air-handling plenum shall be listed to UL 2043 or shall be installed in an enclosure listed for the plenum.

+### Most commercial ceilings return air through the plenum, so the plenum listing is the common case rather than the exception; an unlisted device above such a ceiling is a code violation at inspection and a smoke contributor in a fire. {note}

+### Devices installed in a damp location shall be listed for damp locations, and devices installed outdoors or in a wet location shall be listed for wet locations.

+### Devices installed in an unconditioned space, a parking structure, a loading dock, or a cold-storage area shall be rated for continuous operation across the range from [[parameter: site-ambient-temperature-minimum]] to [[parameter: site-ambient-temperature-maximum]], or across the maintained temperature range of the space where it is narrower.

+### Devices installed in a hazardous (classified) location shall be listed for the class, division, and group of that location.

+### Sensors installed in a gymnasium, a corridor of a detention or correctional occupancy, or another location where they can be struck shall be furnished with a listed guard or in a vandal-resistant housing.

+# Control Functions Required by the Energy Code {toc}

+## The adopted energy code fixes the minimum control function for each interior space, including which spaces are shut off automatically, which are sensed for occupancy, which respond to daylight, where a manual control is required, how large a control zone can be, how long a time delay or an override can run, which receptacles are controlled, and whether the building responds to a demand signal. Those requirements are project facts that follow from the code in force, and this standard applies them through the reference below rather than restating a particular edition. {note}

+## Interior lighting in every space shall be provided with the automatic shutoff, occupancy-based control, daylight-responsive control, manual control, automatic receptacle control, and demand-responsive control that [[parameter: adopted-energy-code]] requires for that space type.

+## The area of a control zone and the extent of a daylight zone shall not exceed the limits [[parameter: adopted-energy-code]] places on them.

+## Where the lighting control schedule requires a function in a space that the adopted energy code does not require there, the schedule shall govern.

+## A lighting installation that meets its power density target but lacks a required control function does not pass plan review, and a control function that is installed but never verified does not pass final inspection under the codes that require functional testing, so the control system is a compliance item and not a comfort item. {note}

+## Where the project is a renovation, the control functions the adopted energy code requires shall be applied to every space in which the luminaires or the control devices are replaced, to the extent the code requires for that scope of work.

+# System Architecture {toc}

+## Control Architecture {toc}

+### The architecture of the lighting control system shall be as indicated in the datasheet.

+```datasheet

+label: Control Architecture

+type: select

+options:

+ - "Stand-alone room-based controls, not networked"

+ - "Networked, centralized relay-panel controllers"

+ - "Networked, distributed room controllers"

+ - "Networked, luminaire-level lighting control"

+ - "Networked, Power over Ethernet luminaires and devices"

+ - "Mixed, by area"

+```

+### No architecture is the norm across projects, because the choice follows from the size of the building, whether the Owner will operate a management system, the incentive strategy, and how often the spaces will be reconfigured. {note}

+### Stand-alone room-based controls place a power pack or room controller in each space and configure it at the device, so the system has no head-end, no network, and nothing to maintain beyond the devices themselves; the cost is that every change is made in the field, no schedule or demand signal reaches the rooms, and nothing is reported. {note}

+### Centralized relay-panel controllers switch and dim from panels in the electrical rooms over control wiring to every zone, so the intelligence sits where the electrician already works and the panels also serve as the emergency override point; the cost is control wiring from every sensor and station back to a panel, and zones that are changed by rewiring. {note}

+### Distributed room controllers place a networked controller in each space that switches and dims the room and reports to a head-end, so zones are changed in software, schedules and demand signals reach every room, and the loss of the network leaves each room running on its own controller; the cost is a controller in every space and a network to every controller. {note}

+### Luminaire-level lighting control places a sensor and a controller in or on each luminaire, so each luminaire is its own zone, grouping is done in software, and the measured savings are the largest of the architectures; the cost is a control node in every luminaire, radio coverage or a bus to every luminaire, and a commissioning effort that scales with the luminaire count. {note}

+### Power over Ethernet delivers both the power and the control data to each luminaire over a structured cable from a network switch, so the luminaire wiring is Class 2 and no line-voltage branch circuit reaches the ceiling; the cost is a switch and a cable to every luminaire, a wattage limit per port that bounds the luminaire, and a structured cabling scope that the electrical and telecommunications trades have to divide. {note}

+### Where the mixed architecture is selected, the architecture serving each area shall be as indicated on [[drawing: the lighting control plans]].

+### Where the architecture is networked, each room or zone controller shall continue to operate its occupancy, daylight, schedule, manual, and emergency functions on the last configuration downloaded to it when the network, the head-end, or the internet connection to a cloud service is lost.

+### Where the architecture is Power over Ethernet, the network switches serving luminaires shall be furnished under this standard, shall be listed as Class 2 power sources under NFPA 70 Article 725, shall comply with the Power over Ethernet clauses of IEEE 802.3, and the structured cabling shall comply with [[sync/structured-cabling]].

+## Network Communication Medium {toc}

+### The communication medium of the control network shall be as indicated in the datasheet.

+```datasheet

+label: Network Communication Medium

+type: select

+options:

+ - "Wired low-voltage control bus"

+ - "Wired Ethernet"

+ - "Wireless radio mesh"

+ - "Wired backbone with wireless room devices"

+```

+### A wired bus is immune to radio interference and to the loss of a battery, and is the medium of systems whose devices are line-powered and reachable by control wiring; wireless devices need no control wiring, which in a renovation with hard ceilings is the difference between a control project and a ceiling project, at the cost of radio coverage that has to be surveyed, batteries or energy harvesters that have to be maintained, and a gateway count that grows with the floor plate; a wired backbone with wireless room devices keeps the head-end and the panels on wire and puts only the sensors and stations on radio. {note}

+### Where wireless devices are furnished, the Contractor shall furnish gateways in the quantity and at the locations the manufacturer's coverage survey requires, and shall demonstrate at functional testing that every wireless device communicates with its gateway with the signal margin the manufacturer publishes.

+### Where wireless devices are battery-powered, the published battery life at the sensing rate configured shall be not less than the period indicated in the datasheet, and the battery shall be a stocked type replaceable without tools.

+```datasheet

+label: Minimum Wireless Device Battery Life

+type: range

+unit: years

+options:

+ min: 2

+ max: 15

+ setpoints: [2, 3, 5, 7, 10, 15]

+```

+### A battery life is bought as a larger battery, a lower reporting rate, or an energy-harvesting station that has no battery at all, and the Owner's maintenance program sets which of those it will accept, so no period is the norm and the field carries no default. {note}

+## Management Software and Network Connection {toc}

+### The hosting of the system management software shall be as indicated in the datasheet.

+```datasheet

+label: Management Software Hosting

+type: radio

+options:

+ - "Embedded in the controllers, browser access, no server"

+ - "On-premises server furnished under this standard"

+ - "Cloud service hosted by the manufacturer"

+```

+### Embedded software is reached through a browser at each controller or gateway and needs nothing installed, which suits a system of a few controllers and an Owner with no operations staff; an on-premises server holds the whole building in one database, runs trending and energy reporting, and stays inside the Owner's network, at the cost of a server the Owner patches and backs up; a cloud service moves the server and its maintenance to the manufacturer and adds remote access and analytics, at the cost of a subscription, an internet dependency for the management functions, and data that leaves the building. {note}

+### Where the software is cloud-hosted, the subscription terms, the data the service collects, and the functions that depend on the connection shall be stated in the software support policy submitted under this standard.

+### The connection between the lighting control network and the Owner's information technology network shall be as indicated in the datasheet.

+```datasheet

+label: Connection to the Owner's Network

+type: radio

+options:

+ - "Isolated lighting control network, no connection"

+ - "Connected on a dedicated virtual local area network assigned by the Owner"

+ - "Connected through the building automation system's operational technology network"

+```

+### An isolated network cannot be reached from the Owner's network and cannot be attacked from it, and it also cannot be managed from an operator's desk or report to anything; a dedicated virtual local area network gives the operator and the building automation system a route to the lighting head-end while the Owner's firewall rules bound what else can reach it; a connection through the building automation system's operational technology network puts lighting under the same segmentation and monitoring the mechanical controls already have. {note}

+### Where the lighting control network is connected to the Owner's network, the default credentials of every controller, gateway, and software account shall be changed before the connection is made, the credentials shall be delivered to the Owner at closeout, every unused port and service shall be disabled, and the configuration shall be coordinated with the cybersecurity baseline of [[sync/building-automation-system]].

+### Where the lighting control network is connected to the Owner's network, the network addresses, the virtual local area network assignment, and the firewall rules shall be as indicated on [[drawing: the network riser diagram]], or as assigned by the Owner's information technology representative where no riser is provided.

+# Luminaire Control Interface {toc}

+## The control interface is the signal the control system delivers to a luminaire to set its light level. It is the boundary with [[sync/lighting-fixtures]]: that standard selects the driver and its dimming input as properties of the luminaire, and this standard selects the signal, the protocol, and the lowest level the system commands, and requires the two to match. {note}

+## Control Signal and Protocol {toc}

+### The control signal delivered to the luminaire drivers shall be as indicated in the datasheet.

+```datasheet

+label: Luminaire Control Signal

+type: select

+options:

+ - "0–10 V analog"

+ - "DALI-2 digital addressable bus"

+ - "D4i digital addressable bus with auxiliary power"

+ - "Forward-phase or reverse-phase line-voltage dimming"

+ - "Manufacturer's wired digital protocol"

+ - "Wireless node integral to the luminaire"

+ - "Power over Ethernet data"

+ - "DMX512 for color-changing architectural luminaires"

+ - "Mixed, by luminaire type"

+default: "0–10 V analog"

+```

+### The 0–10 V analog interface is the signal on the large majority of commercial interior projects, which is why it is the default; it is one-way, it needs a separate control pair to every dimmed zone, it cannot address one luminaire on a shared pair, and the level it produces depends on the dimming curve of each driver, so two drivers on one pair from two manufacturers can sit at different levels on the same voltage. {note}

+### A DALI-2 bus is two-way and polarity-insensitive, addresses each luminaire, groups and regroups them in software, and reports driver faults and energy, and its certification is checked against a public database; D4i adds the auxiliary power and the data model that let a sensor node be powered from the luminaire itself. Both cost a bus to every luminaire and a bus power supply per segment, and the addressing is a commissioning step of its own. {note}

+### Line-voltage phase dimming uses the lighting circuit itself as the control path and needs no control wiring, which suits a renovation of a wall-dimmed space; it is the signal most prone to flicker, audible noise, and a driver that will not dim on the dimmer furnished, and every dimmer and driver pairing has to be confirmed. {note}

+### A wired manufacturer's protocol, a wireless node integral to the luminaire, and Power over Ethernet data each tie the signal to the architecture selected under this standard and to that manufacturer's node in the luminaire; DMX512 is the signal of color-changing architectural luminaires and is carried on a dedicated cable to a controller that also owns the color sequences. {note}

+### Where the signal is mixed by luminaire type, the signal to each luminaire type shall be as indicated on [[drawing: the luminaire schedule]].

+### The dimming input of every luminaire driver furnished under [[sync/lighting-fixtures]] shall accept the control signal selected here, and a luminaire whose driver does not accept it shall not be furnished for a controlled zone.

+### 0–10 V control conductors shall be violet for the positive conductor and gray for the negative conductor, in accordance with ANSI C137.1, and the control system's 0–10 V outputs shall be of the sinking type that ANSI C137.1 defines for the driver side of the interface.

+### The 0–10 V output of each controller channel shall be rated for the number of drivers connected to it, and the Contractor shall not connect more drivers to a channel than its rating or the manufacturer's published limit for the run length permits.

+## Minimum Controlled Light Level {toc}

+### The lowest light level the control system shall command in a dimmed zone, as a percentage of full output, shall be as indicated in the datasheet.

+```datasheet

+label: Minimum Controlled Light Level

+type: range

+unit: '% of full output'

+options:

+ min: 0.1

+ max: 10

+ setpoints: [0.1, 1, 5, 10]

+default: 10

+```

+### The lowest level a zone reaches is a property of the controller and the driver together, not of either alone, so the value selected here binds the two: a controller commanded to 1 percent against a driver that drops out at 10 percent delivers a dark scene at 10 percent and a flicker below it. A 10 percent floor is the level general commercial spaces are controlled to and the level most drivers reach without qualification, which is why it is the default; a 5 percent floor is bought where a conference room, a lecture room, or a hospitality space holds a low-light scene, and a 1 percent floor where the scene has to fade to near dark. {note}

+### The minimum dimming level of the drivers furnished under [[sync/lighting-fixtures]] for a dimmed zone shall be not higher than the level selected here, and the control system shall command that level smoothly, without visible steps, flicker, or dropout.

+### In a daylight-responsive zone, the control system shall dim the electric lighting to the level [[parameter: adopted-energy-code]] requires of the daylit zone before it turns the lighting off, and shall turn it off where that code requires.

+## Color Control Channels {toc}

+### The color control channels the control system shall provide in each zone shall be as indicated in the datasheet.

+```datasheet

+label: Color Control Channels

+type: radio

+derived: "the color tuning behavior selected for the luminaires under [[sync/lighting-fixtures]]"

+options:

+ - "Intensity only"

+ - "Intensity and correlated color temperature"

+ - "Intensity, color temperature, and color"

+default: derived

+```

+### The channels follow the luminaires: a fixed-color luminaire needs one channel, a tunable-white luminaire needs a second channel for color temperature or a digital protocol that carries it, and a color-changing luminaire needs a channel per color. A single 0–10 V pair carries one channel, which is the reason a tunable space is controlled over a digital bus, a second analog pair, or a wireless node. {note}

+### Where the luminaires are color-tunable, the control system shall command color temperature independently of intensity, and the sequence of operation for the space shall state the color temperature schedule and the stations from which it is changed.

+# Occupancy and Vacancy Sensing {toc}

+## An occupancy sensor turns the lighting on when it detects a person and off after a period of no detection; a vacancy sensor leaves the turning on to the occupant and performs only the turning off. The difference is a configuration of the same device, and the adopted energy code names the mode required in many space types. {note}

+## Sensor Control Mode {toc}

+### The sensor control mode of each space shall be as indicated in the datasheet.

+```datasheet

+label: Sensor Control Mode

+type: radio

+drawing_ref: "the lighting control schedule"

+options:

+ - "Vacancy, manual-on and automatic-off"

+ - "Occupancy, automatic-on and automatic-off"

+ - "Partial-on, automatic to a reduced level and manual to full"

+ - "Selectable at the device"

+default: deferred

+```

+### The mode is decided space by space and recorded on the schedule, because a private office and a corridor in the same building need different answers: manual-on saves the energy of a space entered briefly or already daylit and is the mode most codes require in enclosed offices, conference rooms, and classrooms; automatic-on suits a corridor, a restroom, or a stair where an occupant enters with full hands or in the dark; partial-on brings the lighting to a reduced level on entry and asks for a manual action for full output, which the codes accept in place of manual-on; a device that is selectable in the field is configured to one of the three at startup and can be changed later without replacement. {note}

+### Where a space is required by [[parameter: adopted-energy-code]] to have manual-on or partial-on control, the sensor in that space shall not be configured for automatic-on to full output.

+### Where partial-on control is selected, the level to which the lighting rises automatically shall be as indicated in the datasheet.

+```datasheet

+label: Partial-On Level

+type: range

+unit: '% of full output'

+options:

+ min: 20

+ max: 75

+ setpoints: [20, 30, 40, 50, 60, 75]

+default: 50

+```

+### The model energy codes accept an automatic rise to not more than half of full output as the equivalent of manual-on, which is why 50 percent is the default; a lower level saves more and asks more of the occupant, and a level above 50 percent is available only where the adopted code permits it. {note}

+## Detection Technology {toc}

+### The detection technology of the occupancy and vacancy sensors shall be as indicated in the datasheet.

+```datasheet

+label: Sensor Detection Technology

+type: select

+options:

+ - "Passive infrared"

+ - "Ultrasonic"

+ - "Dual-technology, passive infrared and ultrasonic"

+ - "Passive infrared with acoustic hold-on"

+ - "Microwave"

+ - "Optical or thermal occupant counting"

+```

+### A passive infrared sensor detects the movement of a warm body across its field of view and needs a clear line of sight, so it does not see behind a partition or a tall cabinet and does not false-trigger on air movement; an ultrasonic sensor fills the space with sound and detects the shift a moving body returns, so it sees around obstructions and catches a hand on a keyboard, and it can also see a diffuser's airflow or a door in the corridor; a dual-technology sensor requires both to turn on and either to hold on, which suppresses both the false-off and the false-on and is what an enclosed room with obstructions is served with; acoustic hold-on keeps a passive infrared sensor on while it hears occupancy it cannot see; a microwave sensor penetrates thin partitions and suits a high-bay or an aisle; an occupant-counting sensor reports how many people are present rather than whether anyone is, which feeds ventilation and space analytics as well as lighting. {note}

+### No technology is the norm across a whole project, because the enclosed rooms, the open floor, the corridors, and the high-bay spaces each favor a different one, so the field carries no default and a project whose sensors vary by space defers the field to the schedule. {note}

+### Sensors shall comply with NEMA WD 7 and shall be furnished with a field-adjustable sensitivity on every detection technology they carry.

+## Vacancy Time Delay {toc}

+### The time delay from the last detection of occupancy to automatic shutoff shall be as indicated in the datasheet.

+```datasheet

+label: Vacancy Time Delay

+type: range

+unit: minutes

+options:

+ min: 1

+ max: 30

+ setpoints: [1, 5, 10, 15, 20, 30]

+```

+### The delay trades nuisance shutoff against wasted operation: a short delay turns the lighting off on an occupant sitting still and produces the complaints that get sensors disabled, and a long delay keeps an empty room lit. The model energy codes have capped the delay at 20 minutes for several editions, a 15-minute setting is common in offices and classrooms, a 5-minute setting in restrooms and storage rooms, and a 30-minute setting is available only where the adopted code permits it, so no single value is the norm and the field carries no default. {note}

+### The time delay shall not exceed the maximum that [[parameter: adopted-energy-code]] permits for the space, and shall be set in the field to the value the sequence of operation states for that space.

+### The time delay shall be adjustable in the field, at the device or in the software, without replacing the device.

+## Sensor Coverage and Mounting {toc}

+### The type, mounting, location, and coverage pattern of each occupancy and vacancy sensor shall be as indicated on [[drawing: the lighting control plans]].

+### Sensors shall be located and aimed so that the coverage pattern includes the entire occupied area of the space, including the area behind partitions and inside stalls, and does not extend into an adjacent space or corridor from which it would hold the lighting on.

+### Sensors shall be located so that they do not view a supply-air diffuser, a door swing from an adjacent space, or a window through which movement outside the space is visible, and ultrasonic sensors shall be kept out of the airflow of a diffuser.

+### A sensor placed without regard to the furniture, the partitions, and the diffusers is the most common cause of a control system that fails its functional test, because a missed occupant produces a dark room and a seen corridor produces a room that never turns off. {note}

+### Where a sensor is powered through a power pack, the power pack shall be listed with the sensor and shall be installed in an accessible location above the ceiling or in the control panel.

+### Wall-box sensors that replace a wall switch shall be furnished only where the lighting control plans indicate them, shall be powered with a grounded conductor at the switch box in accordance with NFPA 70 404.2(C), and shall be of the device family selected under [[sync/wiring-devices]] for the plate opening and finish.

+## Occupancy Signal Sharing with HVAC {toc}

+### The means by which the occupancy state of a space is shared with the HVAC control system shall be as indicated in the datasheet.

+```datasheet

+label: Occupancy Signal Sharing with HVAC

+type: radio

+options:

+ - "Not shared"

+ - "Shared through the building automation interface as a networked point"

+ - "Shared by an auxiliary contact from the sensor or power pack"

+```

+### Sharing a sensor lets the HVAC zone go to setback when the lighting sensor sees the room empty and avoids a second sensor in every ceiling; a networked point carries the state for every zone over one interface and needs the interface to exist, while an auxiliary contact carries one zone over one pair of conductors to the zone controller and needs nothing but the wiring. Not sharing keeps the two systems independent, which is what a project without a building automation system or with an HVAC standard that furnishes its own sensors does. {note}

+### Where the occupancy signal is shared, the sensor furnished under this standard shall serve both systems, the sensor's time delay shall serve the lighting, and the HVAC delay shall be applied at the HVAC zone controller under [[sync/hvac-controls-instrumentation]].

+### Where the occupancy signal is shared by an auxiliary contact, the contact shall be voltage-free, rated for the zone controller's input, and wired to the terminal indicated on [[drawing: the controls drawings]].

+# Daylight-Responsive Control {toc}

+## Daylight-responsive control reduces the electric lighting in a zone that receives daylight from a window or a skylight so that the combined light holds near the design level rather than adding the two, and the adopted energy code defines the zones that require it by their distance from the aperture and their connected lighting load. {note}

+## The boundaries of each daylight zone and the luminaires it contains shall be as indicated on [[drawing: the lighting control plans]].

+## Daylight Sensing Method {toc}

+### The daylight sensing method shall be as indicated in the datasheet.

+```datasheet

+label: Daylight Sensing Method

+type: radio

+options:

+ - "Closed-loop, sensor views the task surface"

+ - "Open-loop, sensor views the daylight aperture"

+ - "Luminaire-integral sensor at each luminaire"

+```

+### A closed-loop sensor looks down at the task surface and sees daylight and electric light together, so it holds a measured level and corrects for anything that changes it, and it is calibrated with the electric lighting on and off in that zone; an open-loop sensor looks at the window or the skylight well, sees daylight alone, and drives the electric lighting by a programmed ratio, so one sensor serves a large toplit zone without being influenced by the luminaires it controls; a luminaire-integral sensor is a closed-loop sensor at every luminaire, which makes each luminaire its own daylight zone and follows the luminaire-level architecture. {note}

+### Daylight sensors shall be located as indicated on [[drawing: the lighting control plans]], shall be shielded from a direct view of the luminaires they control and of the luminaires in an adjacent zone, and shall not view a surface whose reflectance is changed by furniture or by an occupant.

+### Daylight zones that overlap or that view the same aperture shall be controlled by the same sensor or by sensors that are configured together, so that two loops do not chase one another.

+## Daylight Response {toc}

+### The response of the electric lighting to daylight shall be as indicated in the datasheet.

+```datasheet

+label: Daylight Response

+type: radio

+options:

+ - "Continuous dimming"

+ - "Stepped dimming in multiple levels"

+ - "Stepped switching by luminaire row"

+default: "Continuous dimming"

+```

+### Continuous dimming lowers the electric lighting without a visible step and is what occupants do not notice, which is why it is the default; stepped dimming moves between a few programmed levels and is available on a driver that cannot dim continuously, and stepped switching turns rows nearer the window off before rows farther away, which is the response of luminaires that do not dim at all. Both stepped responses produce a change occupants see, and the adopted energy code limits where each is accepted. {note}

+### Continuous dimming shall lower the electric lighting in the daylight zone from full output to the minimum controlled light level selected under this standard without a visible step.

+### A stepped response shall be furnished only where [[parameter: adopted-energy-code]] accepts it for the daylight zone, and shall include the number of steps and the switching sequence that code requires.

+### The daylight response shall include a dead band and a time delay between adjustments so that a passing cloud does not produce a visible cycling of the electric lighting.

+## Daylight Target Illuminance {toc}

+### The illuminance the daylight-responsive control shall hold at the task surface of each daylight zone shall be as indicated in the datasheet.

+```datasheet

+label: Daylight Control Target Illuminance

+type: range

+unit: fc

+derived: "the maintained illuminance the lighting design establishes for each daylit space"

+options:

+ min: 5

+ max: 100

+ setpoints: [5, 10, 20, 30, 40, 50, 75, 100]

+default: derived

+```

+### The target is the design level of the space, not a control decision, so the field derives from the lighting design; the control holds that level as daylight varies and lets the electric lighting fall as low as the minimum controlled level permits when daylight alone reaches it. {note}

+### The setpoint shall be set at calibration to the target illuminance and recorded in the functional test report, and a zone whose target is not stated in the lighting design shall be calibrated to the level the Engineer of Record directs.

+# Time Scheduling and Override {toc}

+## Scheduling Means {toc}

+### The means by which time-of-day schedules are applied to the lighting shall be as indicated in the datasheet.

+```datasheet

+label: Time Scheduling Means

+type: select

+options:

+ - "Astronomical time switch, stand-alone"

+ - "Seven-day programmable time switch, stand-alone"

+ - "Schedule held in the lighting control system's controllers"

+ - "Schedule issued by the building automation system through the interface"

+ - "None, automatic shutoff by occupancy sensing throughout"

+```

+### A stand-alone time switch holds one or a few schedules at the panel it is mounted in and is what a small building or a single tenant space runs; an astronomical time switch adds sunrise and sunset so that lighting near the envelope follows the season without reprogramming; a schedule held in the control system's controllers reaches every zone the system knows and is edited from the management software; a schedule issued by the building automation system keeps one schedule for the whole building across lighting and mechanical equipment and depends on the interface being present and the building automation system being the master. A building whose every space is occupancy-sensed needs no schedule for shutoff, and the field records that as a selection rather than as an absence. {note}

+### Where a schedule is the means of automatic shutoff for a space, the schedule shall turn the lighting in that space off at the end of the occupied period stated in the sequence of operation for that space, and the occupied periods shall be as indicated on [[drawing: the lighting control schedule]].

+### A time switch shall hold its program and its clock through a power outage of not less than the period indicated in the datasheet, without a battery that the Owner has to replace within the warranty period.

+```datasheet

+label: Time Switch Program Retention Through Power Loss

+type: range

+unit: hours

+options:

+ min: 24

+ max: 240

+ setpoints: [24, 72, 168, 240]

+default: 72

+```

+### A retention of three days covers a weekend outage, which is the outage a time switch most often sees, and is the retention most products provide from a supercapacitor or a sealed cell, which is why it is the default; a longer retention is bought where the building is left unattended for longer than a weekend. {note}

+### Where the schedule is issued by the building automation system, the lighting control system shall hold a default schedule of its own that takes effect when the interface is lost, and the default schedule shall be stated in the sequence of operation.

+## After-Hours Override {toc}

+### Where a schedule turns the lighting in a space off, a manual override shall be provided in that space that returns the lighting for the period indicated in the datasheet.

+```datasheet

+label: After-Hours Override Duration

+type: range

+unit: hours

+options:

+ min: 0.25

+ max: 4

+ setpoints: [0.25, 0.5, 1, 2, 4]

+```

+### The override is what keeps a person working late from sitting in the dark and what keeps the scheduled shutoff from being defeated: a short override sends the occupant back to the switch every quarter hour, a long override lights the space for the rest of the night after the occupant leaves. The model energy codes cap the override at two hours, a one-hour setting is common where the stations are within reach, and a four-hour setting is available only where the adopted code permits it, so no value is the norm and the field carries no default. {note}

+### The override duration shall not exceed the maximum that [[parameter: adopted-energy-code]] permits, and the override shall affect only the area that code permits a single override to control.

+### The override shall be initiated from the manual control station in the space or from a station within the area the override controls, and shall not require access to the control panel or to the management software.

+## Scheduled-Off Warning {toc}

+### The warning given to occupants before a scheduled shutoff shall be as indicated in the datasheet.

+```datasheet

+label: Scheduled-Off Warning

+type: radio

+options:

+ - "Lighting flashes off and on once before shutoff"

+ - "Lighting steps down to a reduced level before shutoff"

+ - "No warning"

+```

+### A flash is the warning occupants recognize and is the warning a stand-alone time switch or a relay panel gives with no dimming; a step down to a reduced level gives the same notice without the flash and is available where the zone dims; no warning is what a space that is occupancy-sensed as well as scheduled uses, because the sensor holds the lighting on while anyone is present and the schedule only sets the period after which the sensor governs. {note}

+### Where a warning is provided, it shall be given not less than the period indicated in the datasheet before the scheduled shutoff.

+```datasheet

+label: Warning Lead Time Before Scheduled Shutoff

+type: range

+unit: minutes

+options:

+ min: 1

+ max: 15

+ setpoints: [1, 2, 5, 10, 15]

+default: 5

+```

+### Five minutes is the lead time the model energy codes have named for the warning and the lead time products are configured to from the factory, which is why it is the default; a longer lead time is bought where the space is large and the stations are far from where the occupants sit. {note}

+# Manual Control Stations {toc}

+## Station Type {toc}

+### The type of manual control station shall be as indicated in the datasheet.

+```datasheet

+label: Manual Control Station Type

+type: select

+options:

+ - "Line-voltage switch or dimmer wired in the load circuit"

+ - "Low-voltage momentary pushbutton station"

+ - "Digital wall station on the control bus"

+ - "Wireless wall station, battery-powered or self-powered"

+ - "Touch-screen station"

+ - "Mixed, by space"

+```

+### A line-voltage station switches or dims the circuit itself and is the station of a stand-alone dimmed space with no controller; a low-voltage momentary station sends a contact closure to a relay panel or a room controller and needs a control pair to it; a digital station on the bus is addressed and programmed in software, so its buttons are assigned and reassigned without rewiring and it can command scenes and several zones; a wireless station needs no wiring at all and is mounted on glass or on a partition that is moved later; a touch-screen station presents scenes, zones, and shades on one panel in a conference room or a lobby. A project with an open office, a conference center, and a stair mixes them by space. {note}

+### Where the station type is mixed by space, the station type in each space shall be as indicated on [[drawing: the lighting control plans]].

+### Every station shall be located as indicated on [[drawing: the lighting control plans]], and where no location is indicated shall be located at the latch side of the entry door to the space at the mounting height [[sync/wiring-devices]] requires for switches.

+### Line-voltage dimmers furnished as manual stations shall be listed to UL 1472, shall be rated for the driver type they dim, and shall be derated for gang mounting as the manufacturer directs.

+## Station Functions and Finish {toc}

+### Each space that the adopted energy code requires to have a manual control shall have a station in that space from which an occupant can turn its lighting off, and, where the luminaires in the space are dimmable, can raise and lower their level, unless [[drawing: the lighting control schedule]] indicates on-off control for the space.

+### The manual control shall act on the zone it serves regardless of the state of the occupancy sensor or the schedule, and an off command from the station shall hold until the occupant turns the lighting on again or the space is vacated and re-entered.

+### Scene control shall be provided at the stations indicated on [[drawing: the lighting control plans]], and the scenes at each station shall be as stated in the sequence of operation for that space.

+### Each station button shall be engraved or labeled with the zone or scene it commands, in the format the Engineer of Record approves in the submittal, and a station whose buttons are unlabeled shall not be accepted.

+### The color and finish of wall stations shall be as indicated in the datasheet.

+```datasheet

+label: Wall Station Finish

+type: select

+derived: "the wiring device color and finish selected under [[sync/wiring-devices]]"

+options:

+ - "White"

+ - "Light almond"

+ - "Ivory"

+ - "Gray"

+ - "Black"

+ - "Brushed stainless steel"

+ - "Custom color matched to a sample"

+default: derived

+```

+### A station sits beside the switches and receptacles of the same wall, so its finish follows the wiring device finish rather than being chosen a second time; a custom color is matched where the architecture specifies a wall finish the device families do not carry. {note}

+### Wall stations shall be furnished with a wall plate of the same finish, and the plate opening and the mounting shall be compatible with the boxes furnished under [[sync/raceways-and-conduit]].

+# Branch-Circuit Switching Equipment {toc}

+## Switching Means {toc}

+### The equipment that switches lighting branch circuits under the command of the control system shall be as indicated in the datasheet.

+```datasheet

+label: Branch-Circuit Switching Means

+type: select

+options:

+ - "Relay panel with individually addressed low-voltage relays"

+ - "Lighting contactors in a contactor enclosure"

+ - "Lighting-control panelboard with remotely operated breakers"

+ - "Distributed room controllers switching at the load, no central switching"

+ - "Mixed, by area"

+```

+### A relay panel switches each circuit with a relay commanded from a low-voltage input or a network, holds a time switch and the emergency override in the same enclosure, and is the equipment of centralized architectures; a lighting contactor switches a large load or several circuits at once from one coil and is what a warehouse, a parking level, or a bank of exterior circuits is switched with; a lighting-control panelboard puts a remotely operated breaker on each circuit in the panelboard itself, so the switching and the overcurrent protection share one cabinet and no separate relay panel is installed; distributed room controllers switch each zone where it is and leave nothing in the electrical room. A building with a networked open office and a warehouse mixes them by area. {note}

+### Where the switching means is mixed by area, the means serving each area shall be as indicated on [[drawing: the electrical plans]].

+### The location of each relay panel, contactor enclosure, and lighting-control panelboard shall be as indicated on [[drawing: the electrical plans]].

+### The circuits each relay panel, contactor, and lighting-control panelboard switches shall be as indicated on [[drawing: the panel schedules]].

+### The continuous current rating of each relay, contactor pole, or remotely operated breaker shall be as indicated in the datasheet.

+```datasheet

+label: Switching Device Continuous Current Rating

+type: range

+unit: A

+derived: "the rating of the branch-circuit overcurrent device of each switched circuit, under [[sync/panelboards]]"

+options:

+ min: 15

+ max: 100

+ setpoints: [15, 20, 30, 60, 100]

+default: derived

+```

+### The switching device is rated to the circuit it switches, so the rating follows the panel schedule rather than being chosen here; a relay is rated at 20 A on the great majority of lighting circuits, and the higher ratings are contactor poles serving multi-circuit loads. {note}

+## Relay Panels {toc}

+### Relay panels shall be listed to UL 916 or UL 508 as an assembly and shall separate the line-voltage relay compartment from the low-voltage control compartment with a barrier that maintains the separation NFPA 70 Article 725 requires.

+### The relay type furnished in relay panels shall be as indicated in the datasheet.

+```datasheet

+label: Relay Panel Relay Type

+type: radio

+options:

+ - "Mechanically latching relay"

+ - "Electrically held relay"

+ - "Electrically held relay with a selectable state on loss of control power"

+default: "Mechanically latching relay"

+```

+### A latching relay stays where it was last commanded when its control power is lost, so a control fault leaves the lighting as it was, and it draws no coil current at rest, which is why it is the relay of most lighting panels and the default; an electrically held relay drops to one state when its coil loses power, which is either a building that goes dark or a building that lights up on a control fault, and a selectable state lets the Engineer choose which for each circuit. {note}

+### Each relay shall be individually replaceable from the front of the panel without disturbing the adjacent relays or the line-voltage wiring, and shall carry a manual override that operates the relay at the panel.

+### The relay panel shall be furnished with the number of spare relay positions indicated in the datasheet, wired to the controller and ready for a relay to be added.

+```datasheet

+label: Spare Relay Positions per Panel

+type: range

+unit: '% of installed relay count'

+options:

+ min: 0

+ max: 50

+ setpoints: [0, 10, 20, 25, 50]

+default: 20

+```

+### A panel is ordered to a circuit count that grows before the building opens, and a fifth again of spare positions is what most specifications carry so that a circuit added at the last change order does not require a second panel, which is why 20 percent is the default; a larger allowance is bought where the tenant fit-out is undefined at the time the panels are ordered. {note}

+### Relay panels shall hold every relay's assignment, schedule, and group in non-volatile memory, and shall return to the programmed state after a loss of control power without reprogramming.

+## Lighting Contactors {toc}

+### Lighting contactors shall be listed to UL 508 for the lighting load type they switch and shall be furnished with an auxiliary contact that reports the contactor position to the control system where the system is networked.

+### The contactor type shall be as indicated in the datasheet.

+```datasheet

+label: Lighting Contactor Type

+type: radio

+options:

+ - "Mechanically held, with a two-coil latching mechanism"

+ - "Electrically held"

+```

+### A mechanically held contactor is latched by a momentary coil pulse and holds without current, so it is silent, draws nothing at rest, and stays where it was on a control power loss; an electrically held contactor holds only while its coil is energized, hums, and drops out on a control power loss, which suits a load that is meant to turn off whenever its control fails. {note}

+### Each contactor shall be furnished with a hand-off-automatic selector at the enclosure so that the circuits it switches can be operated locally while the control system is out of service.

+## Lighting-Control Panelboards {toc}

+### Where the switching means is a lighting-control panelboard, the remotely operated breakers, their controller, and their control power supply shall be furnished under this standard, shall be listed with the panelboard under UL 67, and shall be installed by the panelboard manufacturer in the panelboard interior furnished under [[sync/panelboards]].

+### The remotely operated breakers shall switch under the command of the controller and shall also trip on overcurrent as ordinary breakers, and a remote command shall not defeat the overcurrent function or prevent a manual operation of the breaker handle.

+### The controller shall accept the low-voltage inputs, the network connection, and the schedule the architecture selected under this standard provides, and shall report the position of each breaker to the management software where the system is networked.

+### The lighting-control panelboard shall be designated as such on [[drawing: the panel schedules]], and the circuits that are remotely operated shall be identified on the panel schedule and on the panelboard directory.

+# Automatic Receptacle Control {toc}

+## The adopted energy code requires that a share of the receptacles in offices, conference rooms, classrooms, copy rooms, and similar spaces be switched off automatically when the space is unoccupied or after hours, so that the equipment plugged into them does not run all night. The receptacle is a wiring device, and the means of switching it is part of this control system. {note}

+## The means by which controlled receptacles are switched shall be as indicated in the datasheet.

+```datasheet

+label: Controlled Receptacle Switching Means

+type: select

+options:

+ - "Switched circuit from the relay panel or lighting-control panelboard"

+ - "Plug-load controller above the ceiling serving the controlled receptacles"

+ - "Networked receptacle with an integral relay"

+ - "None, automatic receptacle control not required"

+```

+### Switching the receptacle circuit at the panel controls every receptacle on the circuit at once and uses the equipment already in the electrical room, and it needs the controlled receptacles to be on circuits of their own; a plug-load controller above the ceiling switches the circuit at the room and follows the room's occupancy sensor without a run back to the panel; a networked receptacle carries its own relay and is addressed like a luminaire, so the controlled and uncontrolled receptacles can share a circuit and be reassigned in software. A project whose adopted code does not require receptacle control, or whose spaces are exempt from it, records that here. {note}

+### Controlled receptacles shall be switched by the same occupancy sensor or schedule that controls the lighting in the space they serve, and the receptacle state shall follow the lighting state with the time delay stated in the sequence of operation for that space.

+### The controlled receptacles in each space, and the circuits they are on, shall be as indicated on [[drawing: the panel schedules]], and the receptacle devices shall be the marked controlled receptacles furnished under [[sync/wiring-devices]].

+### A plug-load controller or a networked receptacle shall be listed to UL 916 or UL 508 for the receptacle load it switches.

+# Demand-Responsive Control {toc}

+## The demand-response capability of the lighting control system shall be as indicated in the datasheet.

+```datasheet

+label: Demand-Response Capability

+type: radio

+derived: "the demand-responsive control that [[parameter: adopted-energy-code]] requires for the building's floor area and occupancy"

+options:

+ - "Not provided"

+ - "Provided, reduction commanded manually by the operator"

+ - "Provided, automatic reduction on a signal from the utility or the building automation system"

+ - "Provided, automatic reduction through an OpenADR-certified interface"

+default: derived

+```

+## Whether the building responds to a demand signal follows from the adopted energy code, which requires it above a floor-area threshold in some jurisdictions and not at all in others, so the field derives from the code; where an Owner provides it beyond the code, a manual reduction is a button the operator presses when the utility calls, an automatic reduction on a building automation signal ties the lighting to whatever demand program the building already runs, and an OpenADR interface lets the utility signal the lighting system directly through a certified client. {note}

+## The reduction in lighting power the system shall achieve on a demand signal, as a percentage of the total controlled lighting power, shall be as indicated in the datasheet.

+```datasheet

+label: Demand-Response Lighting Power Reduction

+type: range

+unit: '% of controlled lighting power'

+derived: "the reduction [[parameter: adopted-energy-code]] requires on a demand signal"

+options:

+ min: 10

+ max: 50

+ setpoints: [10, 15, 20, 25, 30, 40, 50]

+default: derived

+```

+## Where demand-responsive control is provided, the reduction shall be achieved by dimming or by switching the zones designated in the sequence of operation, without reducing the lighting in a space below the level the sequence names as its demand-response floor, and without affecting egress lighting.

+## Where demand-responsive control is provided, the system shall return every zone to its prior state when the demand signal ends.

+# Integration with Other Building Systems {toc}

+## Building Automation System Interface {toc}

+### The interface between the lighting control system and the building automation system shall be as indicated in the datasheet.

+```datasheet

+label: Building Automation System Interface

+type: radio

+options:

+ - "No interface"

+ - "Status reporting to the building automation system"

+ - "Two-way, status reporting and commands accepted from the building automation system"

+```

+### No interface is what a building with no building automation system or with stand-alone room controls records; status reporting lets the operator see zone states, energy, and device faults on the building automation graphics without giving that system any authority over the lighting; a two-way interface adds schedules, demand signals, and occupancy from the building automation system as commands, which puts one schedule on the whole building and makes the lighting depend on the interface for those functions. {note}

+### Where an interface is provided, the protocol of the interface shall be as indicated in the datasheet.

+```datasheet

+label: Building Automation Interface Protocol

+type: select

+options:

+ - "BACnet/IP"

+ - "BACnet MS/TP"

+ - "Modbus TCP"

+ - "Modbus RTU"

+ - "Dry-contact interface"

+ - "Manufacturer application programming interface over IP"

+```

+### The protocol follows the building automation system rather than the lighting system: BACnet over IP or over a serial trunk is what most building automation systems accept natively and is the protocol of ASHRAE 135; Modbus is what a metering or an industrial supervisory system reads; a dry-contact interface carries a handful of states over relay contacts and needs no network at all; a manufacturer's application programming interface exposes everything the lighting software knows and binds the interface to that software's version. {note}

+### Where an interface is provided, the points exchanged shall be as indicated on [[drawing: the points list]], and the point names shall follow the naming convention of [[sync/building-automation-system]].

+### The lighting control system shall retain full local control of every occupancy, daylight, manual, and emergency function independent of the building automation interface, so that a failure of the interface or of the building automation system does not disable a code-required control function.

+### Where an interface is provided, the gateway between the two systems shall be furnished under this standard.

+## Motorized Shade Control {toc}

+### The system that commands the motorized shades shall be as indicated in the datasheet.

+```datasheet

+label: Motorized Shade Command Source

+type: radio

+options:

+ - "No motorized shades, or shades commanded only from their own stations"

+ - "Shades commanded by the lighting control system"

+ - "Shades commanded by the building automation system"

+```

+### Shades commanded by the lighting control system share the wall stations, the scenes, and the daylight sensors with the lighting, so a conference room scene sets both, and a daylight zone lowers the shade before it dims the lighting; shades commanded by the building automation system follow a facade or a solar-tracking sequence that also runs the perimeter heating, and the lighting system sees the shades only through the building automation interface. Shades commanded only from their own stations need no interface from either system. {note}

+### Where the shades are commanded by the lighting control system, the sequence that commands them shall be written under this standard, and the shade-side controllers and the gateway shall be furnished under [[sync/window-treatments]].

+### Where the shades are commanded by the lighting control system, the daylight-responsive sequence for a zone with shades shall state the order in which the shade and the electric lighting respond so that the two do not oscillate.

+## Additional Interfaces {toc}

+### The lighting control system shall provide the additional interfaces indicated in the datasheet.

+```datasheet

+label: Additional System Interfaces

+type: checkbox

+options:

+ - "Audiovisual control system, scene and zone commands"

+ - "Fire alarm system, lighting to full output on alarm"

+ - "Security or access control system, occupancy and after-hours state"

+ - "Room scheduling system, occupied periods"

+ - "Space analytics, occupancy and count data export"

+```

+### Where an interface to the fire alarm system is provided, the interface shall be a listed control module output of the fire alarm system, shall raise the lighting in the designated areas to full output on alarm, and shall be coordinated with [[sync/fire-alarm-systems]].

+### Where an interface to an audiovisual control system is provided, the audiovisual system shall command scenes and zones through the interface and shall not switch or dim the lighting circuits directly.

+## Energy Reporting {toc}

+### The energy reporting the lighting control system shall provide shall be as indicated in the datasheet.

+```datasheet

+label: Lighting Energy Reporting

+type: radio

+options:

+ - "Not provided"

+ - "Energy reported per control zone from the controller's load model"

+ - "Energy measured and reported per luminaire or per circuit"

+```

+### A reporting function is what lets the Owner see what the controls save and is a capability the utility incentive lists require; a load model reports energy from the programmed wattage and the commanded level and needs no metering hardware, while a measured value comes from a driver that reports its power over a digital bus or from a current sensor on the circuit and is what a measurement-and-verification program accepts. A project with no incentive and no energy program records none. {note}

+### Where energy reporting is provided, the report shall be available from the management software by zone and by period, shall be retained for not less than the period indicated in the datasheet, and shall be exportable in a tabular file.

+```datasheet

+label: Energy Data Retention Period

+type: range

+unit: months

+options:

+ min: 1

+ max: 60

+ setpoints: [1, 3, 12, 24, 36, 60]

+default: 12

+```

+### A year of data covers every season once and is what an incentive program's verification and an Owner's annual review look at, which is why 12 months is the default; a longer retention is bought where the Owner tracks year-on-year performance in the lighting system rather than in an energy management platform. {note}

+# Emergency Lighting Control Interface {toc}

+## A luminaire that lights the means of egress is often switched, dimmed, and scheduled with the rest of the lighting during normal operation, and NFPA 70 Article 700 requires that every such control be overridden so the luminaire returns to full output when normal power is lost, through equipment listed to UL 924. The override device is selected, located, and wired under this standard; the egress illumination design that decides which luminaires it serves is made under [[sync/emergency-and-egress-lighting]]. {note}

+## Override Device {toc}

+### The device that returns a controlled egress luminaire to full output on loss of normal power shall be as indicated in the datasheet.

+```datasheet

+label: Emergency Lighting Override Device

+type: select

+options:

+ - "None, egress luminaires are unswitched and undimmed"

+ - "UL 924 automatic load control relay, one per controlled egress circuit"

+ - "UL 924 emergency lighting control unit in the relay panel or lighting-control panelboard"

+ - "UL 924 listed bypass function within the networked control system"

+ - "UL 924 listed override at each emergency luminaire's control node"

+```

+### An egress luminaire that is never switched or dimmed needs no override, and a project that leaves its egress lighting unswitched records that here; an automatic load control relay is a discrete device at each controlled circuit that bypasses the local control and is the equipment of a stand-alone or relay-panel system; an emergency lighting control unit does the same for several circuits from inside the panel; a listed bypass function in a networked system uses the controller's own listing to force the emergency luminaires on and is available only from a manufacturer whose system holds that listing; an override at each luminaire's control node serves a luminaire-level architecture where no circuit-level device exists. No device is the norm across the architectures, so the field carries no default. {note}

+### Every egress luminaire that is switched, dimmed, or scheduled during normal operation, as identified under [[sync/emergency-and-egress-lighting]], shall be controlled through an override device selected here.

+### The override device shall be listed to UL 924 for the specific function it performs, whether as a discrete relay, a panel-mounted unit, a luminaire node, or a function of a networked controller, and the listing category shall be identified in the submittal.

+## Sensing and Transfer {toc}

+### The override device shall sense the normal branch circuit or the normal feeder that serves the area the egress luminaire lights, and shall not sense only the switched leg at the luminaire or the control power of the panel.

+### On loss of the normal source it senses, the override device shall return the controlled egress luminaires to full output within the time NFPA 101 and [[parameter: adopted-building-code]] allow for the restoration of egress illumination, regardless of the state of any sensor, station, schedule, dimmer, or demand-response command.

+### The override device shall return the egress luminaires to the control of the lighting control system only after the normal source it senses is restored and stable, and shall do so without manual reset.

+### Where the egress luminaires are on a generator-backed or inverter-backed circuit, the override device shall be located and wired so that the transfer of that circuit to the emergency source does not itself appear to the device as a restoration of normal power while the area's normal lighting is still dark.

+### The location and the sensing point of each override device shall be as indicated on [[drawing: the electrical lighting plans]].

+### A device that senses only its own control power sees nothing when the normal lighting circuit of the room trips, and the room goes dark with the egress luminaire still obeying its dimmer; the sensing point is the single detail on which the whole interface depends, and it is the one an inspector opens the box to check. {note}

+## Override Device Testing {toc}

+### The test method of the override devices shall be as indicated in the datasheet.

+```datasheet

+label: Override Device Test Method

+type: radio

+derived: "the emergency lighting test method selected under [[sync/emergency-and-egress-lighting]]"

+options:

+ - "Manual test switch at the device with written records"

+ - "Self-testing and self-diagnostic device"

+ - "Self-testing device reporting to the monitoring system"

+default: derived

+```

+### The override device is tested on the same schedule as the emergency lighting it serves, so its test method follows the method the egress standard selects rather than being chosen twice; a self-testing device exercises its transfer on the periodic schedule NFPA 101 requires and shows the result at the device, and a reporting device sends the result to the monitoring system so that a failed relay above a corridor ceiling is reported rather than found. {note}

+### Every override device shall carry a test means that simulates loss of the normal source without de-energizing the emergency circuit, reachable without opening a line-voltage compartment.

+# Low-Voltage Control Wiring {toc}

+## Circuit Class {toc}

+### The class of the control circuits under NFPA 70 Article 725 shall be as indicated in the datasheet.

+```datasheet

+label: Control Circuit Class

+type: select

+options:

+ - "Class 2 power-limited"

+ - "Class 1"

+ - "Class 3"

+ - "Class 4 fault-managed power"

+default: "Class 2 power-limited"

+```

+### A Class 2 circuit is limited at its source to a level that neither shocks nor ignites, so its wiring is installed by the power-limited methods of Article 725 without a raceway in most locations, and it is the class of the sensor, station, 0–10 V, and bus wiring of nearly every lighting control system, which is why it is the default; a Class 1 circuit carries more power or a higher voltage at the cost of being wired like a power circuit, and is used where a device's demand or a run length exceeds the Class 2 limit; a Class 3 circuit permits a higher voltage than Class 2 for a long run of signaling; a Class 4 fault-managed power circuit delivers power at a level above Class 2 over a monitored cable and is the class of some Power over Ethernet and direct-current lighting systems. {note}

+### Where a device or a circuit length requires a class other than the datasheet selection, that circuit shall be wired to the class it requires, and the class of every circuit shall be identified on the point-to-point wiring diagrams.

+### Class 2 circuits shall be supplied only from a listed Class 2 power source, and the conductors of a Class 2 circuit shall not occupy the same cable, raceway, or enclosure compartment as line-voltage conductors except as NFPA 70 Article 725 permits.

+## Wiring Method {toc}

+### The wiring method of the low-voltage control wiring shall be as indicated in the datasheet.

+```datasheet

+label: Low-Voltage Control Wiring Method

+type: select

+options:

+ - "Cable in raceway throughout"

+ - "Cable in raceway where exposed or in walls, open plenum-rated cable above accessible ceilings"

+ - "Open cable throughout, supported independently"

+```

+### Raceway throughout protects the cable in every location and is what an industrial building, a school, or a health care facility with a raceway policy for all wiring requires; raceway where the cable is exposed or in a wall, with open plenum-rated cable above the accessible ceiling, is the method of most commercial construction and the least costly that still protects the cable where it can be damaged; open cable throughout is available where the cable is never exposed and the Owner accepts it. {note}

+### Control cable installed in an air-handling plenum shall be plenum-rated, and control cable installed in a raceway shall comply with [[sync/raceways-and-conduit]] for the raceway, its fill, and its support.

+### Open control cable shall be supported independently of the ceiling grid, the luminaires, the ductwork, and the piping, at intervals not exceeding those the manufacturer publishes, and shall not rest on the ceiling tiles.

+### Control conductors shall be of the type, gauge, and construction the control manufacturer requires for the run length, so that the voltage drop on a 0–10 V pair or the attenuation on a bus does not alter the level or the data the system delivers, and the maximum run length of each circuit type shall be stated in the submittal.

+### Low-voltage control wiring shall be separated from line-voltage wiring, from the wiring of other systems, and from sources of electrical noise by the distance the manufacturer requires, and the control bus shall not be run in the same cable as the 0–10 V pair unless the manufacturer's cable is listed for both.

+## Conductor Identification and Grounding {toc}

+### Every control conductor shall be identified at both ends with the zone or device it serves, in a form that agrees with the point-to-point wiring diagrams and the zone schedule, and the identification products shall comply with [[sync/equipment-labeling]].

+### Control panels, controllers, and metal device enclosures shall be grounded and bonded in accordance with [[sync/grounding-and-bonding]].

+### The shield of a shielded control cable shall be grounded at one end only, at the end the manufacturer directs, and shall be insulated from ground at the other.

+### A shield grounded at both ends carries the difference in ground potential between the two ends as a current, and that current appears as noise on the signal the shield was meant to protect. {note}

+# Sequences of Operation {toc}

+## A sequence of operation is the written statement of how the lighting in a space responds to occupancy, vacancy, daylight, the schedule, the manual stations, a demand signal, and the loss of normal power. It is the part of the specification the system is programmed to and tested against, and a system installed exactly to the device schedule but programmed to the wrong sequence meets neither the design intent nor the code. {note}

+## A sequence of operation shall be prepared for every space type and every control zone, in the narrative and tabular format of ANSI/IES LP-16, and the system shall be programmed and tested to it.

+## Each sequence shall state the control mode on entry, the vacancy time delay, the daylight response and its target, the schedule and the after-hours override, the scheduled-off warning, the manual station functions and scenes, the receptacle control, the demand-response floor, the color temperature schedule where the luminaires are tunable, and the emergency override behavior.

+## The space-by-space sequences and the zone assignments shall be as indicated on [[drawing: the lighting control schedule]], and the Contractor's submitted sequences shall reproduce them and shall add the device-level settings that implement them.

+## Each sequence shall state how a manual command interacts with the automatic functions: how long an override holds, what area it affects, and whether the automatic function resumes when the override expires.

+## Where the sequence of operation and the datasheet selections of this standard conflict, the sequence of operation shall govern for the space it describes, and the conflict shall be reported to the Engineer of Record before programming.

+# Installation {toc}

+## Coordination Before Rough-In {toc}

+### Before rough-in, the Contractor shall coordinate the location of every ceiling sensor, daylight sensor, wireless gateway, and wall station with the architectural reflected ceiling plans, the luminaire layout, the ductwork and piping, and the furniture and partition plan, so that each sensor has the coverage its pattern requires and is not blocked by a duct, a beam, a partition, or a tall cabinet.

+### The Contractor shall coordinate the branch-circuit assignment of controlled luminaires and controlled receptacles with [[sync/panelboards]] before the panel schedules are finalized, so that every zone the control system switches at the panel is on a circuit of its own.

+### A control zone that shares a circuit with lighting outside the zone cannot be switched at the panel without switching the other lighting, and a controlled receptacle on a general receptacle circuit cannot be switched at all; both are found at functional testing, when the fix is a new circuit. {note}

+## Device Mounting {toc}

+### Devices shall be mounted level and aligned with adjacent devices and with the ceiling grid, and every sensor shall be aimed in the field to the coverage pattern the manufacturer publishes.

+### Ceiling sensors, gateways, and luminaire-level nodes installed in a suspended ceiling shall be supported from the ceiling grid or from structure as the manufacturer directs, and shall be seismically restrained where [[parameter: seismic-design-category]] requires nonstructural components to be restrained.

+### Relay panels, contactor enclosures, and controllers shall be mounted with their tops not more than the height NFPA 70 permits for the operating handle of the highest device, with the working space NFPA 70 requires in front of them, and in a space that satisfies [[sync/electrical-rooms]] where they are installed in an electrical room.

+### Wireless gateways shall be mounted in the open, above or outside the ceiling as the manufacturer directs, and not inside a metal enclosure or behind a metal ceiling that attenuates the radio signal.

+## Identification {toc}

+### Every relay panel, contactor enclosure, controller, gateway, power pack, and room controller shall be labeled with its designation from the zone schedule, and every relay and contactor shall be labeled with the circuit and the zone it switches.

+### Every sensor and wall station shall carry a discreet label with its zone or device address, in a location the manufacturer provides for it, so that the device can be identified from the floor at commissioning and at a service call.

+### The labeling shall agree with the as-built control drawings and the zone schedule, and the label products shall comply with [[sync/equipment-labeling]].

+### A control device that cannot be identified cannot be commissioned or serviced, because no one can determine later which sensor governs which room. {note}

+# Startup, Programming, and Functional Testing {toc}

+## Startup and Programming {toc}

+### The party selected under this standard shall start the system, address every networked device, download the sequences of operation to every controller, and set every time delay, daylight target, level, schedule, and scene to the value the sequence of operation states, before functional testing begins.

+### Where the system is networked, the Contractor shall confirm before functional testing that every device on the zone schedule is present on the network, is addressed as the schedule indicates, and reports to the management software.

+### The Contractor shall set the high-end trim of each dimmed zone to the value indicated in the datasheet.

+```datasheet

+label: High-End Trim

+type: range

+unit: '% of full output'

+options:

+ min: 50

+ max: 100

+ setpoints: [50, 60, 70, 80, 85, 90, 100]

+default: 100

+```

+### High-end trim caps the output a zone reaches on a full command, so a space whose luminaires exceed the design illuminance is held at the level it needs; a trim of 100 percent is no trim at all and is where a system starts unless the lighting design calls for one, which is why it is the default, and a lower trim is bought where the luminaires were selected with a margin or where the incentive program counts the trim as savings. {note}

+## Functional Testing {toc}

+### The adopted energy code requires that the lighting controls be functionally tested and documented before the building is accepted, so that a sensor that is installed but mis-aimed, a daylight loop that is installed but never calibrated, and a schedule that is installed but never programmed are found before occupancy rather than never. {note}

+### The party that performs functional testing shall be as indicated in the datasheet.

+```datasheet

+label: Functional Testing Performed By

+type: select

+derived: "the qualifications [[parameter: adopted-energy-code]] requires of the party that performs lighting control functional testing"

+options:

+ - "Installing Contractor"

+ - "Manufacturer's factory-authorized technician"

+ - "Commissioning authority independent of the installer"

+ - "Certified lighting controls acceptance test technician"

+default: derived

+```

+### The codes differ on who performs the test: some accept the installer, some require a party independent of the installer or the designer above a size threshold, and one state requires a technician certified under its own acceptance test program, so the field derives from the adopted code and the Owner raises it where the Owner's commissioning program asks for more. {note}

+### The Contractor shall demonstrate and document the following functions in every control zone, and the functions documented shall be as indicated in the datasheet:

+- that the occupancy or vacancy sensor turns the lighting on in the configured mode, holds it on while the space is occupied throughout its area, and turns it off after the programmed time delay when the space is vacant

+- that the daylight-responsive control dims the electric lighting as daylight rises, holds the target illuminance, and returns the lighting as daylight falls

+- that the schedule turns the lighting off at the programmed time, that the scheduled-off warning is given, and that the after-hours override returns the lighting for the programmed period and area

+- that every manual station operates the zones and scenes assigned to it and that the manual control acts on the zone as required under this standard

+- that the controlled receptacles follow the lighting state

+- that the demand-response reduction occurs on a simulated signal and that every zone returns to its prior state when the signal ends

+- that the emergency override returns every controlled egress luminaire to full output on a simulated loss of the normal source, switched off and dimmed

+- that every point on the building automation points list, every shade command, and every additional interface reads and writes as specified

+- the final setting of every time delay, daylight target, level, schedule, trim, and scene, recorded so that the Owner can restore them after a controller is replaced

+```datasheet

+label: Functional Test Documentation

+type: checkbox

+options:

+ - "Occupancy and vacancy sensing, mode, coverage, and time delay by zone"

+ - "Daylight-responsive control, response and target by zone"

+ - "Schedule, warning, and after-hours override by zone"

+ - "Manual station functions and scenes by zone"

+ - "Controlled receptacle operation by space"

+ - "Demand-response reduction and restoration"

+ - "Emergency override to full output, switched off and dimmed"

+ - "Building automation, shade, and additional interface points"

+ - "Final programmed settings by zone"

+default:

+ - "Occupancy and vacancy sensing, mode, coverage, and time delay by zone"

+ - "Daylight-responsive control, response and target by zone"

+ - "Schedule, warning, and after-hours override by zone"

+ - "Manual station functions and scenes by zone"

+ - "Emergency override to full output, switched off and dimmed"

+ - "Final programmed settings by zone"

+```

+### A zone that fails any function shall be corrected and retested, and the cost of the correction and of every repeated test shall be borne by the Contractor.

+### The functional testing shall be witnessed by the Owner's representative where the datasheet requires witnessing.

+```datasheet

+label: Functional Test Witnessing

+type: radio

+options:

+ - "Witnessed by the Owner's representative"

+ - "Recorded by the testing party without witnessing"

+default: "Recorded by the testing party without witnessing"

+```

+### The functional test report shall be in a form the Authority Having Jurisdiction accepts as the documentation [[parameter: adopted-energy-code]] requires, and shall be submitted before the certificate of occupancy is requested.

+## Daylight Sensor Calibration {toc}

+### Every daylight sensor shall be calibrated after the ceiling, the finishes, the furniture, and the window treatments are in place, under representative daylight and with the electric lighting at full output and off, so that the controlled lighting holds the target illuminance as daylight varies.

+### The calibration shall be verified by measurement at the task surface with a calibrated illuminance meter, and shall not be assumed from the factory setting or from the sensor's own reading.

+### A daylight sensor calibrated before the carpet and the furniture arrive is calibrated to a different room, and a sensor left at its factory setting either never dims or dims so hard that the occupants cover it; uncalibrated daylight controls are the most frequent finding of a post-occupancy review and deliver none of the savings the code counted on. {note}

+## Post-Occupancy Tuning and Training {toc}

+### The Contractor shall return after occupancy, within the period indicated in the datasheet, to adjust sensor sensitivity, time delays, daylight targets, and schedules to the building's actual use and to record the adjusted settings.

+```datasheet

+label: Post-Occupancy Tuning Period

+type: range

+unit: months

+options:

+ min: 0

+ max: 12

+ setpoints: [0, 1, 3, 6, 12]

+```

+### The settings that pass functional testing in an empty building are not the settings that suit it occupied, and the return visit is where the nuisance shutoffs and the over-lit corridors are corrected before the Owner disables the sensors; a period of zero records that the Owner performs the tuning with its own staff, and the period an Owner chooses depends on when the building is fully occupied, so no period is the norm and the field carries no default. {note}

+### The Contractor shall train the Owner's operating staff in the operation, adjustment, and basic troubleshooting of the system, including changing a schedule, adjusting a time delay and a daylight target, replacing a device, adding or moving a zone in a networked system, and restoring a configuration from the backup, for not less than the number of hours indicated in the datasheet.

+```datasheet

+label: Owner Training

+type: range

+unit: hours

+options:

+ min: 0

+ max: 24

+ setpoints: [0, 2, 4, 8, 16, 24]

+```

+### The training a system needs scales with its architecture: a stand-alone system is explained at the devices in an hour or two, and a networked system with management software and an interface takes a day or more with the software open, so no duration is the norm and the field carries no default. {note}

+### Training shall be recorded, the record shall name the attendees and the topics covered, and a recording of the software training shall be furnished to the Owner where the software is networked.

+# Delivery, Storage, and Handling {toc}

+## Control equipment shall be delivered in the manufacturer's packaging with the listing marks intact, and shall be inspected for damage at receipt.

+## Control devices, controllers, and relay panels shall be stored indoors in a dry space within the manufacturer's published storage temperature and humidity range, off the floor, and protected from dust, paint, and construction debris until they are installed.

+## Sensors shall be installed after the ceiling is closed and the dust-producing work in the space is complete, or shall be protected in place with their lens covers until that work is complete.

+## A sensor lens fogged by drywall dust or overspray reads the room through a haze and fails its coverage test, and the sensor is replaced rather than cleaned because the lens is the detector. {note}

+## Battery-powered wireless devices shall be delivered with their batteries within the shelf life the manufacturer publishes, and the date by which each battery must be replaced shall be stated in the operation and maintenance data.

+# Warranty {toc}

+## The manufacturer shall warrant every control device, controller, relay panel, contactor, gateway, and station against defects in materials and workmanship for the period indicated in the datasheet, measured from the date of substantial completion.

+```datasheet

+label: Control Equipment Warranty Period

+type: range

+unit: years

+options:

+ min: 1

+ max: 10

+ setpoints: [1, 2, 3, 5, 10]

+```

+## The manufacturer shall provide firmware and software updates, and support for the management software, for the period indicated in the datasheet, measured from the date of substantial completion.

+```datasheet

+label: Software Support Period

+type: range

+unit: years

+options:

+ min: 1

+ max: 10

+ setpoints: [1, 2, 3, 5, 10]

+```

+## Manufacturers warrant sensors and relay panels for periods that range from one year to ten across the market, and a networked system's value sits in software whose support runs on terms of its own, so neither period is the norm and neither field carries a default; the longer periods are bought where the Owner will not have a controls integrator on call and where the system is networked, because the controller and the software are the components that most often need the manufacturer after the first year. {note}

+## Where the contract documents state a longer period than the datasheet, the longer period shall govern.

+## The Contractor shall warrant the installation, including the sensor coverage, the wiring, the programming, and the calibration, for the project warranty period, and shall correct a zone that fails to perform its sequence of operation during that period at no cost to the Owner.

+## A repair or replacement performed under this warranty shall itself be warranted for a full new term equal to the original period from the date the repair is completed, or for the remainder of the original period, whichever ends later.

+# Spare Parts {toc}

+## The Contractor shall deliver spare control devices of each type furnished, in the quantity indicated in the datasheet as a percentage of the installed count of each type, and shall obtain a signed receipt for them.

+```datasheet

+label: Spare Control Devices Furnished

+type: range

+unit: '% of installed count of each device type'

+options:

+ min: 0

+ max: 25

+ setpoints: [0, 2, 5, 10, 25]

+```

+## The spare device types to be furnished shall be as indicated in the datasheet.

+```datasheet

+label: Spare Device Types

+type: checkbox

+options:

+ - "Occupancy and vacancy sensors, each type"

+ - "Daylight sensors, each type"

+ - "Power packs and relays, each type"

+ - "Wall stations, each type and finish"

+ - "Room controllers, each type"

+ - "Wireless gateway"

+ - "Network or panel controller"

+ - "UL 924 override devices, each type"

+ - "Batteries for wireless devices, one replacement set"

+```

+## A spare quantity is sized to the installed count and to the Owner's maintenance program, so no quantity is the norm and the field carries no default; power packs and relays switch load and fail before sensors do, a spare controller or gateway matters where the product line changes and a mismatched replacement means reprogramming, and a zero records that the Owner stocks nothing and replaces on failure. {note}

+## Spare parts shall be of the same manufacturer, model, firmware version, and finish as the installed items, shall be delivered in their original packaging, and shall be labeled with the zone type they serve.

+## Spare devices shall be delivered with the software, the licenses, and the addressing instructions needed to put them into service in the installed system without the manufacturer's attendance.

View current revision