SynC™

SynC · SynC Standards

Lighting Controls

Rev6
IssuedOct 12, 2026
Contents

Revision history

Download
Build a datasheet from this standard Start a project with this standard already attached — one click, no setup.
Use in a project

1 Scope

NOTE 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. (1.1)
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. (1.2)
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. (1.3)
NOTE The following are governed elsewhere and are outside this standard: (1.4)
  • the luminaires, their drivers, and the driver's dimming input as a luminaire component (Lighting FixturesInterior Lighting Fixtures (Luminaires)Resolves to the current adopted revision.sync/lighting-fixtures)
  • the photocontrols, schedules, and zoning of exterior and site lighting (Exterior LightingExterior and Site LightingResolves to the current adopted revision.sync/exterior-lighting)
  • the egress illumination design, the emergency luminaires, unit equipment, inverters, and exit signs (Emergency And Egress LightingEmergency and Egress LightingResolves to the current adopted revision.sync/emergency-and-egress-lighting)
  • the emergency power system, its load classification, the generator, and the transfer switches (Emergency And Standby PowerEmergency and Standby Power SystemsResolves to the current adopted revision.sync/emergency-and-standby-power)
  • the building automation system as a product and the sequences it runs for mechanical equipment (Building Automation SystemBuilding Automation SystemResolves to the current adopted revision.sync/building-automation-system)
  • the occupancy sensors furnished for HVAC zone control alone (HVAC Controls InstrumentationHVAC Instrumentation and Control DevicesResolves to the current adopted revision.sync/hvac-controls-instrumentation)
  • the panelboard assembly that houses remotely operated breakers (PanelboardsPanelboardsResolves to the current adopted revision.sync/panelboards)
  • the motorized shades, their motors, and the shade-side gateway (Window TreatmentsWindow TreatmentsResolves to the current adopted revision.sync/window-treatments)
  • stand-alone wall switches, dimmers, and wall-box sensors with no system connection (Wiring DevicesWiring DevicesResolves to the current adopted revision.sync/wiring-devices)
  • the branch circuits, raceways, and grounding of the controlled lighting (Conductors And CablesConductors and CablesResolves to the current adopted revision.sync/conductors-and-cables, Raceways And ConduitRaceways and ConduitResolves to the current adopted revision.sync/raceways-and-conduit, Grounding And BondingGrounding and Bonding for Electrical SystemsResolves to the current adopted revision.sync/grounding-and-bonding)
  • the identification products applied to electrical equipment (Equipment LabelingElectrical Equipment LabelingResolves to the current adopted revision.sync/equipment-labeling)
1.5 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.

2 Referenced Standards

2.1 Equipment, materials, and installation shall comply with the latest adopted edition of each of the following unless a specific edition is cited.
2.2 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
NOTE 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. (2.3)

3 Submittals

3.1 Action Submittals

3.1.1 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
Action Submittalscheckbox
☑ 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
3.1.2 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.
NOTE 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. (3.1.3)

3.2 Informational Submittals

3.2.1 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
Informational Submittalscheckbox
☑ Installer and programmer qualification statements
☐ Utility program qualification certification
☐ Wireless device and gateway location plan
☑ Software support policy

3.3 Closeout Submittals

3.3.1 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
Closeout Submittalscheckbox
☑ 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
NOTE 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. (3.3.2)

4 Quality Assurance

4.1 Listing and Labeling

4.1.1 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.
4.1.2 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.
4.1.3 Wireless control devices shall comply with 47 CFR Part 15 and shall carry the Federal Communications Commission identifier on the device.
NOTE 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. (4.1.4)

4.2 System Interoperability

4.2.1 The interoperability basis of the control system shall be as indicated in the datasheet.
System Interoperability Basisradio
○ Single manufacturer's product family throughout
○ Open-protocol devices from more than one manufacturer, certified interoperable
NOTE 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. (4.2.2)
4.2.3 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.
4.2.4 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.
4.2.5 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.

4.3 Utility Program Qualification

4.3.1 The utility program qualification required of the control system shall be as indicated in the datasheet.
Utility Program Qualificationradio
● Not required
○ Listed on the DesignLights Consortium Networked Lighting Controls qualified products list
NOTE 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. (4.3.2)
4.3.3 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.

4.4 Installer and Programmer Qualifications

4.4.1 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.
Installer Comparable Projectsrange
projects
13510
Default: Not less than 3 projects
4.4.2 The party that performs startup and programming of the control system shall be as indicated in the datasheet.
Startup and Programming Performed Byradio
○ Manufacturer's factory-authorized technician
○ Installing Contractor's manufacturer-trained technician
○ Owner's controls integrator
NOTE 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. (4.4.3)
4.4.4 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.

5 Environmental and Service Conditions

5.1 Control Panel Enclosure

5.1.1 Relay panels, lighting contactor enclosures, controller enclosures, and gateway enclosures shall be of the enclosure type indicated in the datasheet.
Control Panel Enclosure Typeselect
NEMA Type 1
NEMA Type 2
NEMA Type 3R
NEMA Type 4
NEMA Type 4X
NEMA Type 12
NOTE 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. (5.1.2)
5.1.3 A control panel installed outdoors or in a wet location shall have an enclosure of NEMA Type 3R, Type 4, or Type 4X.
5.1.4 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.
5.1.5 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.
5.1.6 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.

5.2 Device Location Ratings

5.2.1 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.
NOTE 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. (5.2.2)
5.2.3 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.
5.2.4 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 Site Ambient Temperature MinimumSite Ambient Temperature MinimumParameterEach project supplies its own value.site-ambient-temperature-minimum to Site Ambient Temperature MaximumSite Ambient Temperature MaximumParameterEach project supplies its own value.site-ambient-temperature-maximum, or across the maintained temperature range of the space where it is narrower.
5.2.5 Devices installed in a hazardous (classified) location shall be listed for the class, division, and group of that location.
5.2.6 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.

6 Control Functions Required by the Energy Code

NOTE 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. (6.1)
6.2 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 Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code requires for that space type.
6.3 The area of a control zone and the extent of a daylight zone shall not exceed the limits Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code places on them.
6.4 Where the lighting control schedule requires a function in a space that the adopted energy code does not require there, the schedule shall govern.
NOTE 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. (6.5)
6.6 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.

7 System Architecture

7.1 Control Architecture

7.1.1 The architecture of the lighting control system shall be as indicated in the datasheet.
Control Architectureselect
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
NOTE 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. (7.1.2)
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. (7.1.3)
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. (7.1.4)
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. (7.1.5)
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. (7.1.6)
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. (7.1.7)
7.1.8 Where the mixed architecture is selected, the architecture serving each area shall be as indicated on the lighting control plans.
7.1.9 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.
7.1.10 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 Structured CablingStructured Cabling SystemsResolves to the current adopted revision.sync/structured-cabling.

7.2 Network Communication Medium

7.2.1 The communication medium of the control network shall be as indicated in the datasheet.
Network Communication Mediumselect
Wired low-voltage control bus
Wired Ethernet
Wireless radio mesh
Wired backbone with wireless room devices
NOTE 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. (7.2.2)
7.2.3 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.
7.2.4 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.
Wireless Device Battery Liferange
years
23571015
NOTE 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. (7.2.5)

7.3 Management Software and Network Connection

7.3.1 The hosting of the system management software shall be as indicated in the datasheet.
Management Software Hostingradio
○ Embedded in the controllers, browser access, no server
○ On-premises server furnished under this standard
○ Cloud service hosted by the manufacturer
7.3.3 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.
7.3.4 The connection between the lighting control network and the Owner's information technology network shall be as indicated in the datasheet.
Connection to the Owner's Networkradio
○ 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
NOTE 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. (7.3.5)
7.3.6 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 Building Automation SystemBuilding Automation SystemResolves to the current adopted revision.sync/building-automation-system.
7.3.7 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 the network riser diagram, or as assigned by the Owner's information technology representative where no riser is provided.

8 Luminaire Control Interface

NOTE The control interface is the signal the control system delivers to a luminaire to set its light level. It is the boundary with Lighting FixturesInterior Lighting Fixtures (Luminaires)Resolves to the current adopted revision.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. (8.1)

8.2 Control Signal and Protocol

8.2.1 The control signal delivered to the luminaire drivers shall be as indicated in the datasheet.
Luminaire Control Signalselect
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
NOTE 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. (8.2.2)
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. (8.2.3)
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. (8.2.4)
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. (8.2.5)
8.2.6 Where the signal is mixed by luminaire type, the signal to each luminaire type shall be as indicated on the luminaire schedule.
8.2.7 The dimming input of every luminaire driver furnished under Lighting FixturesInterior Lighting Fixtures (Luminaires)Resolves to the current adopted revision.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.
8.2.8 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.
8.2.9 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.

8.3 Minimum Controlled Light Level

8.3.1 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.
Minimum Controlled Light Levelrange
% of full output
0.11510
Default: Not more than 10 % of full output
NOTE 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. (8.3.2)
8.3.3 The minimum dimming level of the drivers furnished under Lighting FixturesInterior Lighting Fixtures (Luminaires)Resolves to the current adopted revision.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.
8.3.4 In a daylight-responsive zone, the control system shall dim the electric lighting to the level Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code requires of the daylit zone before it turns the lighting off, and shall turn it off where that code requires.

8.4 Color Control Channels

8.4.1 The color control channels the control system shall provide in each zone shall be as indicated in the datasheet.
Color Control Channelsradio
○ Intensity only
○ Intensity and correlated color temperature
○ Intensity, color temperature, and color
Derived — the color tuning behavior selected for the luminaires under [[sync/lighting-fixtures]] (by default)
NOTE 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. (8.4.2)
8.4.3 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.

9 Occupancy and Vacancy Sensing

NOTE 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. (9.1)

9.2 Sensor Control Mode

9.2.1 The sensor control mode of each space shall be as indicated in the datasheet.
Sensor Control Moderadio
○ 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
Per drawings — the lighting control schedule (deferred by default)
NOTE 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. (9.2.2)
9.2.3 Where a space is required by Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.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.
9.2.4 Where partial-on control is selected, the level to which the lighting rises automatically shall be as indicated in the datasheet.
Partial-On Levelrange
% of full output
203040506075
NOTE 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. (9.2.5)

9.3 Detection Technology

9.3.1 The detection technology of the occupancy and vacancy sensors shall be as indicated in the datasheet.
Sensor Detection Technologyselect
Passive infrared
Ultrasonic
Dual-technology, passive infrared and ultrasonic
Passive infrared with acoustic hold-on
Microwave
Optical or thermal occupant counting
NOTE 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. (9.3.2)
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. (9.3.3)
9.3.4 Sensors shall comply with NEMA WD 7 and shall be furnished with a field-adjustable sensitivity on every detection technology they carry.

9.4 Vacancy Time Delay

9.4.1 The time delay from the last detection of occupancy to automatic shutoff shall be as indicated in the datasheet.
Vacancy Time Delayrange
minutes
1510152030
NOTE 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. (9.4.2)
9.4.3 The time delay shall not exceed the maximum that Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.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.
9.4.4 The time delay shall be adjustable in the field, at the device or in the software, without replacing the device.

9.5 Sensor Coverage and Mounting

9.5.1 The type, mounting, location, and coverage pattern of each occupancy and vacancy sensor shall be as indicated on the lighting control plans.
9.5.2 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.
9.5.3 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.
NOTE 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. (9.5.4)
9.5.5 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.
9.5.6 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 Wiring DevicesWiring DevicesResolves to the current adopted revision.sync/wiring-devices for the plate opening and finish.

9.6 Occupancy Signal Sharing with HVAC

9.6.1 The means by which the occupancy state of a space is shared with the HVAC control system shall be as indicated in the datasheet.
Occupancy Signal Sharing with HVACradio
○ Not shared
○ Shared through the building automation interface as a networked point
○ Shared by an auxiliary contact from the sensor or power pack
NOTE 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. (9.6.2)
9.6.3 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 HVAC Controls InstrumentationHVAC Instrumentation and Control DevicesResolves to the current adopted revision.sync/hvac-controls-instrumentation.
9.6.4 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 the controls drawings.

10 Daylight-Responsive Control

NOTE 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. (10.1)
10.2 The boundaries of each daylight zone and the luminaires it contains shall be as indicated on the lighting control plans.

10.3 Daylight Sensing Method

10.3.1 The daylight sensing method shall be as indicated in the datasheet.
Daylight Sensing Methodradio
○ Closed-loop, sensor views the task surface
○ Open-loop, sensor views the daylight aperture
○ Luminaire-integral sensor at each luminaire
NOTE 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. (10.3.2)
10.3.3 Daylight sensors shall be located as indicated on 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.
10.3.4 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.

10.4 Daylight Response

10.4.1 The response of the electric lighting to daylight shall be as indicated in the datasheet.
Daylight Responseradio
● Continuous dimming
○ Stepped dimming in multiple levels
○ Stepped switching by luminaire row
NOTE 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. (10.4.2)
10.4.3 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.
10.4.4 A stepped response shall be furnished only where Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code accepts it for the daylight zone, and shall include the number of steps and the switching sequence that code requires.
10.4.5 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.

10.5 Daylight Target Illuminance

10.5.1 The illuminance the daylight-responsive control shall hold at the task surface of each daylight zone shall be as indicated in the datasheet.
Daylight Control Target Illuminancerange
fc
5102030405075100
Derived — the maintained illuminance the lighting design establishes for each daylit space (by default)
NOTE 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. (10.5.2)
10.5.3 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.

11 Time Scheduling and Override

11.1 Scheduling Means

11.1.1 The means by which time-of-day schedules are applied to the lighting shall be as indicated in the datasheet.
Time Scheduling Meansselect
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
NOTE 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. (11.1.2)
11.1.3 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 the lighting control schedule.
11.1.4 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.
Time Switch Program Retention Through Power Lossrange
hours
2472168240
Default: Not less than 72 hours
NOTE 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. (11.1.5)
11.1.6 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.

11.2 After-Hours Override

11.2.1 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.
After-Hours Override Durationrange
hours
0.250.5124
NOTE 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. (11.2.2)
11.2.3 The override duration shall not exceed the maximum that Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code permits, and the override shall affect only the area that code permits a single override to control.
11.2.4 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.

11.3 Scheduled-Off Warning

11.3.1 The warning given to occupants before a scheduled shutoff shall be as indicated in the datasheet.
Scheduled-Off Warningradio
○ Lighting flashes off and on once before shutoff
○ Lighting steps down to a reduced level before shutoff
○ No warning
NOTE 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. (11.3.2)
11.3.3 Where a warning is provided, it shall be given not less than the period indicated in the datasheet before the scheduled shutoff.
Warning Lead Time Before Scheduled Shutoffrange
minutes
1251015
Default: Not less than 5 minutes
NOTE 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. (11.3.4)

12 Manual Control Stations

12.1 Station Type

12.1.1 The type of manual control station shall be as indicated in the datasheet.
Manual Control Station Typeselect
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
NOTE 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. (12.1.2)
12.1.3 Where the station type is mixed by space, the station type in each space shall be as indicated on the lighting control plans.
12.1.4 Every station shall be located as indicated on 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 Wiring DevicesWiring DevicesResolves to the current adopted revision.sync/wiring-devices requires for switches.
12.1.5 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.

12.2 Station Functions and Finish

12.2.1 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 the lighting control schedule indicates on-off control for the space.
12.2.2 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.
12.2.3 Scene control shall be provided at the stations indicated on the lighting control plans, and the scenes at each station shall be as stated in the sequence of operation for that space.
12.2.4 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.
12.2.5 The color and finish of wall stations shall be as indicated in the datasheet.
Wall Station Finishselect
White
Light almond
Ivory
Gray
Black
Brushed stainless steel
Custom color matched to a sample
Derived — the wiring device color and finish selected under [[sync/wiring-devices]] (by default)
NOTE 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. (12.2.6)
12.2.7 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 Raceways And ConduitRaceways and ConduitResolves to the current adopted revision.sync/raceways-and-conduit.

13 Branch-Circuit Switching Equipment

13.1 Switching Means

13.1.1 The equipment that switches lighting branch circuits under the command of the control system shall be as indicated in the datasheet.
Branch-Circuit Switching Meansselect
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
NOTE 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. (13.1.2)
13.1.3 Where the switching means is mixed by area, the means serving each area shall be as indicated on the electrical plans.
13.1.4 The location of each relay panel, contactor enclosure, and lighting-control panelboard shall be as indicated on the electrical plans.
13.1.5 The circuits each relay panel, contactor, and lighting-control panelboard switches shall be as indicated on the panel schedules.
13.1.6 The continuous current rating of each relay, contactor pole, or remotely operated breaker shall be as indicated in the datasheet.
Switching Device Continuous Current Ratingrange
A
15203060100
Derived — the rating of the branch-circuit overcurrent device of each switched circuit, under [[sync/panelboards]] (by default)
NOTE 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. (13.1.7)

13.2 Relay Panels

13.2.1 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.
13.2.2 The relay type furnished in relay panels shall be as indicated in the datasheet.
Relay Panel Relay Typeradio
● Mechanically latching relay
○ Electrically held relay
○ Electrically held relay with a selectable state on loss of control power
NOTE 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. (13.2.3)
13.2.4 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.
13.2.5 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.
Spare Relay Positions per Panelrange
% of installed relay count
10202550
Default: Not less than 20 % of installed relay count
NOTE 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. (13.2.6)
13.2.7 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.

13.3 Lighting Contactors

13.3.1 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.
13.3.2 The contactor type shall be as indicated in the datasheet.
Lighting Contactor Typeradio
○ Mechanically held, with a two-coil latching mechanism
○ Electrically held
NOTE 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. (13.3.3)
13.3.4 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.

13.4 Lighting-Control Panelboards

13.4.1 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 PanelboardsPanelboardsResolves to the current adopted revision.sync/panelboards.
13.4.2 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.
13.4.3 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.
13.4.4 The lighting-control panelboard shall be designated as such on the panel schedules, and the circuits that are remotely operated shall be identified on the panel schedule and on the panelboard directory.

14 Automatic Receptacle Control

NOTE 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. (14.1)
14.2 The means by which controlled receptacles are switched shall be as indicated in the datasheet.
Controlled Receptacle Switching Meansselect
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
NOTE 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. (14.2.1)
14.2.2 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.
14.2.3 The controlled receptacles in each space, and the circuits they are on, shall be as indicated on the panel schedules, and the receptacle devices shall be the marked controlled receptacles furnished under Wiring DevicesWiring DevicesResolves to the current adopted revision.sync/wiring-devices.
14.2.4 A plug-load controller or a networked receptacle shall be listed to UL 916 or UL 508 for the receptacle load it switches.

15 Demand-Responsive Control

15.1 The demand-response capability of the lighting control system shall be as indicated in the datasheet.
Demand-Response Capabilityradio
○ 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
Derived — the demand-responsive control that Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code requires for the building's floor area and occupancy (by default)
NOTE 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. (15.2)
15.3 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.
Demand-Response Lighting Power Reductionrange
% of controlled lighting power
10152025304050
Derived — the reduction Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code requires on a demand signal (by default)
15.4 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.
15.5 Where demand-responsive control is provided, the system shall return every zone to its prior state when the demand signal ends.

16 Integration with Other Building Systems

16.1 Building Automation System Interface

16.1.1 The interface between the lighting control system and the building automation system shall be as indicated in the datasheet.
Building Automation System Interfaceradio
○ No interface
○ Status reporting to the building automation system
○ Two-way, status reporting and commands accepted from the building automation system
NOTE 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. (16.1.2)
16.1.3 Where an interface is provided, the protocol of the interface shall be as indicated in the datasheet.
Building Automation Interface Protocolselect
BACnet/IP
BACnet MS/TP
Modbus TCP
Modbus RTU
Dry-contact interface
Manufacturer application programming interface over IP
NOTE 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. (16.1.4)
16.1.5 Where an interface is provided, the points exchanged shall be as indicated on the points list, and the point names shall follow the naming convention of Building Automation SystemBuilding Automation SystemResolves to the current adopted revision.sync/building-automation-system.
16.1.6 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.
16.1.7 Where an interface is provided, the gateway between the two systems shall be furnished under this standard.

16.2 Motorized Shade Control

16.2.1 The system that commands the motorized shades shall be as indicated in the datasheet.
Motorized Shade Command Sourceradio
○ 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
NOTE 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. (16.2.2)
16.2.3 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 Window TreatmentsWindow TreatmentsResolves to the current adopted revision.sync/window-treatments.
16.2.4 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.

16.3 Additional Interfaces

16.3.1 The lighting control system shall provide the additional interfaces indicated in the datasheet.
Additional System Interfacescheckbox
☐ 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
16.3.2 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 Fire Alarm SystemsFire Alarm SystemsResolves to the current adopted revision.sync/fire-alarm-systems.
16.3.3 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.

16.4 Energy Reporting

16.4.1 The energy reporting the lighting control system shall provide shall be as indicated in the datasheet.
Lighting Energy Reportingradio
○ Not provided
○ Energy reported per control zone from the controller's load model
○ Energy measured and reported per luminaire or per circuit
NOTE 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. (16.4.2)
16.4.3 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.
Energy Data Retention Periodrange
months
1312243660
Default: Not less than 12 months
NOTE 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. (16.4.4)

17 Emergency Lighting Control Interface

NOTE 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 Emergency And Egress LightingEmergency and Egress LightingResolves to the current adopted revision.sync/emergency-and-egress-lighting. (17.1)

17.2 Override Device

17.2.1 The device that returns a controlled egress luminaire to full output on loss of normal power shall be as indicated in the datasheet.
Emergency Lighting Override Deviceselect
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
NOTE 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. (17.2.2)
17.2.3 Every egress luminaire that is switched, dimmed, or scheduled during normal operation, as identified under Emergency And Egress LightingEmergency and Egress LightingResolves to the current adopted revision.sync/emergency-and-egress-lighting, shall be controlled through an override device selected here.
17.2.4 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.

17.3 Sensing and Transfer

17.3.1 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.
17.3.2 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 Adopted Building CodeAdopted Building CodeParameterEach project supplies its own value.adopted-building-code allow for the restoration of egress illumination, regardless of the state of any sensor, station, schedule, dimmer, or demand-response command.
17.3.3 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.
17.3.4 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.
17.3.5 The location and the sensing point of each override device shall be as indicated on the electrical lighting plans.
NOTE 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. (17.3.6)

17.4 Override Device Testing

17.4.1 The test method of the override devices shall be as indicated in the datasheet.
Override Device Test Methodradio
○ Manual test switch at the device with written records
○ Self-testing and self-diagnostic device
○ Self-testing device reporting to the monitoring system
Derived — the emergency lighting test method selected under [[sync/emergency-and-egress-lighting]] (by default)
NOTE 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. (17.4.2)
17.4.3 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.

18 Low-Voltage Control Wiring

18.1 Circuit Class

18.1.1 The class of the control circuits under NFPA 70 Article 725 shall be as indicated in the datasheet.
Control Circuit Classselect
Class 2 power-limited
Class 1
Class 3
Class 4 fault-managed power
NOTE 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. (18.1.2)
18.1.3 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.
18.1.4 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.

18.2 Wiring Method

18.2.1 The wiring method of the low-voltage control wiring shall be as indicated in the datasheet.
Low-Voltage Control Wiring Methodselect
Cable in raceway throughout
Cable in raceway where exposed or in walls, open plenum-rated cable above accessible ceilings
Open cable throughout, supported independently
NOTE 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. (18.2.2)
18.2.3 Control cable installed in an air-handling plenum shall be plenum-rated, and control cable installed in a raceway shall comply with Raceways And ConduitRaceways and ConduitResolves to the current adopted revision.sync/raceways-and-conduit for the raceway, its fill, and its support.
18.2.4 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.
18.2.5 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.
18.2.6 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.

18.3 Conductor Identification and Grounding

18.3.1 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 Equipment LabelingElectrical Equipment LabelingResolves to the current adopted revision.sync/equipment-labeling.
18.3.2 Control panels, controllers, and metal device enclosures shall be grounded and bonded in accordance with Grounding And BondingGrounding and Bonding for Electrical SystemsResolves to the current adopted revision.sync/grounding-and-bonding.
18.3.3 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.
NOTE 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. (18.3.4)

19 Sequences of Operation

NOTE 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. (19.1)
19.2 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.
19.3 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.
19.4 The space-by-space sequences and the zone assignments shall be as indicated on the lighting control schedule, and the Contractor's submitted sequences shall reproduce them and shall add the device-level settings that implement them.
19.5 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.
19.6 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.

20 Installation

20.1 Coordination Before Rough-In

20.1.1 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.
20.1.2 The Contractor shall coordinate the branch-circuit assignment of controlled luminaires and controlled receptacles with PanelboardsPanelboardsResolves to the current adopted revision.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.
NOTE 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. (20.1.3)

20.2 Device Mounting

20.2.1 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.
20.2.2 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 Seismic Design CategorySeismic Design CategoryParameterEach project supplies its own value.seismic-design-category requires nonstructural components to be restrained.
20.2.3 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 Electrical RoomsElectrical RoomsResolves to the current adopted revision.sync/electrical-rooms where they are installed in an electrical room.
20.2.4 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.

20.3 Identification

20.3.1 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.
20.3.2 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.
20.3.3 The labeling shall agree with the as-built control drawings and the zone schedule, and the label products shall comply with Equipment LabelingElectrical Equipment LabelingResolves to the current adopted revision.sync/equipment-labeling.
NOTE A control device that cannot be identified cannot be commissioned or serviced, because no one can determine later which sensor governs which room. (20.3.4)

21 Startup, Programming, and Functional Testing

21.1 Startup and Programming

21.1.1 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.
21.1.2 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.
21.1.3 The Contractor shall set the high-end trim of each dimmed zone to the value indicated in the datasheet.
High-End Trimrange
% of full output
506070808590100
NOTE 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. (21.1.4)

21.2 Functional Testing

NOTE 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. (21.2.1)
21.2.2 The party that performs functional testing shall be as indicated in the datasheet.
Functional Testing Performed Byselect
Installing Contractor
Manufacturer's factory-authorized technician
Commissioning authority independent of the installer
Certified lighting controls acceptance test technician
Derived — the qualifications Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code requires of the party that performs lighting control functional testing (by default)
NOTE 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. (21.2.3)
21.2.4 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
Functional Test Documentationcheckbox
☑ 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
21.2.5 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.
21.2.6 The functional testing shall be witnessed by the Owner's representative where the datasheet requires witnessing.
Functional Test Witnessingradio
○ Witnessed by the Owner's representative
● Recorded by the testing party without witnessing
21.2.7 The functional test report shall be in a form the Authority Having Jurisdiction accepts as the documentation Adopted Energy CodeAdopted Energy CodeParameterEach project supplies its own value.adopted-energy-code requires, and shall be submitted before the certificate of occupancy is requested.

21.3 Daylight Sensor Calibration

21.3.1 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.
21.3.2 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.
NOTE 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. (21.3.3)

21.4 Post-Occupancy Tuning and Training

21.4.1 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.
Post-Occupancy Tuning Periodrange
months
13612
NOTE 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. (21.4.2)
21.4.3 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.
Owner Trainingrange
hours
2481624
NOTE 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. (21.4.4)
21.4.5 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.

22 Delivery, Storage, and Handling

22.1 Control equipment shall be delivered in the manufacturer's packaging with the listing marks intact, and shall be inspected for damage at receipt.
22.2 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.
22.3 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.
NOTE 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. (22.4)
22.5 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.

23 Warranty

23.1 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.
Control Equipment Warranty Periodrange
years
123510
23.2 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.
Software Support Periodrange
years
123510
NOTE 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. (23.3)
23.4 Where the contract documents state a longer period than the datasheet, the longer period shall govern.
23.5 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.
23.6 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.

24 Spare Parts

24.1 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.
Spare Control Devices Furnishedrange
% of installed count of each device type
251025
24.2 The spare device types to be furnished shall be as indicated in the datasheet.
Spare Device Typescheckbox
☐ 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
NOTE 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. (24.3)
24.4 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.
24.5 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.

Edit this page

SynC Standards are reference material provided for informational purposes only and as a guide. They are not engineering, architectural, or legal advice and are not a substitute for the judgment of a licensed design professional. It is the responsibility of the user to determine the applicability of any standard to a specific project and to verify all requirements against the governing codes, manufacturer data, and project conditions. SynC does not render professional services and forms no professional relationship by publishing this content. Provided "as is," without warranty of any kind, including fitness for a particular purpose. See our Terms of Use for the complete terms. Moderation log.

This standard is published by SynC and licensed under Creative Commons Attribution-ShareAlike 4.0. You may share and adapt it, including commercially, provided you give credit, link to the license, indicate any changes, and license your adaptations under the same terms. Keep the attribution and notice below with any copy — it includes the warranty disclaimer the license requires you to retain.

Attribution & reuse notice — keep this with any copy:
"Lighting Controls." SynC Standards. Licensed under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). Source: https://synergyinconstruction.com/wiki/sync/lighting-controls — reference material only; not professional engineering advice and provided without warranty. Verify against governing codes and have a licensed professional review before use.