The most expensive mistake on every NLC project
Controls get added as an afterthought. The fixtures are already specified, the circuits are designed, the bid is submitted, and then someone says "can we add controls to this?" At that point, the fixture layout is locked into a configuration that may not match the optimal control zones. The circuit groupings may not support the occupancy response the owner wants. And the budget for commissioning and owner training, which are what determine whether the system actually delivers savings, has already been spent on fixtures.
The original article on this page had exactly one good insight, and it is this: controls must be part of the project from the first conversation, not tacked on at the end. Everything else in this guide flows from that principle. When controls are planned from the start, the fixture selection, circuit design, zone layout, and budget all align. When they are added late, every one of those elements becomes a compromise.
This article walks through the five phases of a networked lighting controls project in the order you should execute them. If you are unfamiliar with what NLC systems are and how they work, read the companion article on networked lighting controls technology first. This guide assumes you understand the basics and are ready to plan a real project.
Phase 1: Client discovery (before you quote)
Before you can design a controls strategy, you need to understand what the building owner actually wants the system to do. Most owners do not think in terms of "occupancy sensing" or "daylight harvesting." They think in terms of outcomes: lower energy bills, fewer complaints about lights being left on, the ability to dim the parking lot after hours, compliance with the energy code.
These are the questions to ask in the first meeting. The answers determine the entire scope.
| Question | What the answer tells you |
|---|---|
| What is the primary goal: energy savings, code compliance, occupant comfort, or all three? | Prioritizes which control strategies to design around. Energy savings drives occupancy + scheduling. Code compliance may mandate specific DLC NLC capabilities. Comfort drives tunable white and manual dimming. |
| What are the building's operating hours? Do they vary by zone? | Determines scheduling requirements. A 24/7 warehouse needs different controls than a 9-5 office. Variable hours across zones means more complex scheduling profiles. |
| Are there areas with regular daylight exposure? | Identifies daylight harvesting opportunity. Perimeter zones near windows or clerestories can dim significantly during daytime. Interior zones cannot. |
| How does occupancy vary across the building? Are there areas that are frequently unoccupied? | Sizes the occupancy sensing strategy. A fully occupied open office gets less savings from occupancy sensors than a warehouse with intermittently used aisles. |
| Does the building have a BMS (building management system)? | Determines whether NLC-HVAC integration is on the table. If the BMS can receive occupancy data from the NLC system, HVAC savings stack on top of lighting savings. The DLC estimates this integration can save up to 30% of HVAC energy. |
| What is the budget tolerance: maximum savings, or minimum upfront cost? | Decides the system tier. Z10-ready fixtures with deferred sensor installation (lowest upfront) vs. full LLLC with per-fixture sensors (maximum savings). Both are valid, but the client needs to make the tradeoff consciously. |
| Is the owner pursuing any building certification (LEED, WELL, ENERGY STAR)? | Some certifications have specific NLC requirements. WELL v2 Feature L03 (circadian lighting) benefits from tunable white NLC. LEED credits are available for energy monitoring and demand response capabilities. |
Write down the answers. This is not a casual conversation. The client discovery answers become the basis of design document, the thing you refer back to when someone asks "why did you put occupancy sensors in the break room?" six months later. Documenting the owner's stated goals protects you from scope creep and from callbacks where the system is working as designed but the owner expected something different.
Phase 2: Site survey and zone mapping
The site survey for an NLC project includes everything from a standard lighting survey (fixture count, types, wattages, mounting heights, operating hours) plus the controls-specific information that determines zone layout and sensor placement.
What to document during the survey
- Fixture locations and types. Every fixture on the plan, marked with its type and wattage. For retrofits, note whether existing fixtures are Z10-ready or will need replacement.
- Circuit assignments. Which fixtures share a circuit. This matters because NLC zones do not have to match circuit boundaries (zones are software-defined), but knowing the circuit layout helps with troubleshooting and emergency bypass scenarios.
- Daylight zones. Identify the perimeter (within 15 ft of windows), transition, and interior zones. These will have different daylight harvesting profiles.
- Occupancy patterns by area. Which areas are occupied all day, which are intermittent (restrooms, break rooms, storage), and which are occupied on schedules (conference rooms, classrooms). This determines occupancy sensor mode: vacancy (manual ON, auto OFF) for intermittent spaces, occupancy (auto ON, auto OFF) for regularly used spaces.
- Sensor line-of-sight obstructions. Tall shelving, partitions, and HVAC ductwork can block PIR sensor coverage. A sensor placed above a 12-ft high rack in a warehouse will not detect someone walking in the adjacent aisle. Map the obstructions during the survey, not during commissioning.
- Gateway location. The NLC gateway (the bridge between the Bluetooth Mesh network and the internet/dashboard) needs power and, ideally, an Ethernet connection or reliable Wi-Fi. Identify the location during the survey. Central placement in the building minimizes the number of mesh hops to the farthest fixture.
Building the zone map
The zone map is the single most important deliverable from the planning phase. It is a floor plan (interior) or site plan (exterior) showing every fixture, color-coded by control zone, with the control profile annotated for each zone.
For exterior projects, start with a satellite image from Google Earth. Overlay the pole positions, fixture types, and property boundaries. For interior projects, use the reflected ceiling plan from the architectural drawings, or create a simple measured sketch if drawings are not available.
Each zone on the map should include three pieces of information: the zone name (descriptive, like "Open Office Perimeter" not "Zone 1"), the control profile (what the system does in that zone), and the target foot-candle level. This becomes the commissioning reference: the installer walks the building, assigns each physical fixture to its zone on the app, and sets the profile that the map specifies.
Phase 3: Verifying system capabilities against project requirements
Not all NLC systems can do the same things. Bluetooth Mesh is the protocol, but the software layer on top of it varies enormously between manufacturers. Before you commit to a system, verify that it supports every capability the project requires.
| Project requirement | System capability to verify | Why it matters |
|---|---|---|
| Multiple zones with different dim levels | Group and zone management with per-zone dim level settings | If the system only supports "all on" or "all off" by group, you cannot deliver the zone profiles on the map. |
| Daylight harvesting on perimeter zones | Ambient light sensor input with closed-loop dimming response | Open-loop systems adjust based on time of day only. Closed-loop systems measure actual light levels and adjust in real time. Closed-loop is more accurate. |
| Vacancy mode in conference rooms | Separate occupancy and vacancy mode settings per zone | Some systems default to occupancy mode (auto ON) with no option for vacancy mode (manual ON only). Conference rooms and restrooms should use vacancy mode per ASHRAE 90.1-2022 Section 9.4.1.1. |
| After-hours scheduling | Time-based scheduling with multiple profiles per zone | A parking lot may need one schedule for weeknights and a different one for weekends. A single-schedule system cannot handle this. |
| Energy monitoring and reporting | Per-zone or per-fixture energy data with exportable reports | Required for DLC NLC QPL listing. Also required for measurement and verification (M&V) to prove rebate-eligible savings to the utility. |
| BMS integration | BACnet or API gateway for sharing occupancy data with HVAC | If the owner wants NLC-HVAC integration, the NLC system must be able to export occupancy data in a format the BMS can read. Not all Bluetooth Mesh systems support this. |
| Utility rebate eligibility | DLC NLC QPL listing | If the system is not on the DLC NLC QPL, it will not qualify for NLC-specific utility incentives. Verify listing status at designlights.org. |
The original article on this page warned: "there is currently a mix of quality systems and also garbage systems." That is accurate. Asking the right questions before specifying a system is how you avoid the garbage ones. If a manufacturer cannot show you DLC NLC QPL listing, documented commissioning workflow, and a live demo of the management dashboard, move on.
Phase 4: Installation and commissioning
The physical installation of NLC-ready fixtures is identical to installing any LED fixture. The controls-specific work happens in two steps: sensor module installation and software commissioning.
Sensor module installation
For Z10-ready fixtures, this is a plug-in operation. The sensor module snaps into the ZHAGA Book 18 receptacle on the fixture. No additional wiring. The fixture provides power to the sensor through the receptacle. Installation adds roughly 30-60 seconds per fixture to the standard install time.
For fixtures that are not Z10-ready, external sensors must be mounted and wired separately, which adds significantly more time and cost. This is one of the reasons Z10-ready fixtures should be specified from the start.
Commissioning workflow
With Bluetooth Mesh systems like JarvisLink, commissioning follows this sequence:
Power on all fixtures
Confirm every fixture is receiving power and the sensor module is detected by the system (usually indicated by an LED status light on the sensor). Walk the building and verify there are no dead fixtures before starting the software side.
Open the commissioning app and create the project
On the phone or tablet, open the NLC app (JarvisLink for Jarvis fixtures). Create a new project and import or recreate the zone map. The app should display the zones you defined in Phase 2.
Walk the building and assign fixtures to zones
Stand under each fixture, tap it in the app to identify it (the fixture will flash or dim momentarily to confirm identity), and drag it into the correct zone. The zone map from Phase 2 is your guide. This is the most time-consuming step: budget 2-4 hours per 100 fixtures.
Configure control profiles for each zone
For each zone, set the parameters from the zone map: target dim level, occupancy/vacancy mode, occupancy timeout (how long the lights stay on after the space is vacated, typically 15-20 minutes per ASHRAE 90.1), daylight harvesting response curve (if applicable), and scheduling profiles (on/off times, reduced-light schedules).
Test each zone
Trigger the occupancy sensors by walking through each zone and verifying that the correct fixtures respond. Verify that daylight harvesting dims the perimeter zone when a flashlight or daylight simulates bright conditions at the sensor. Verify that scheduling advances correctly by manually setting the clock forward. Document any fixtures that do not respond correctly.
Connect the gateway and verify dashboard access
Plug in the gateway device (Ethernet or Wi-Fi to the building network). Confirm that the cloud dashboard shows all zones, fixture counts, and real-time status. Verify that the owner or facility manager can log in from their device.
Phase 5: Owner handoff (the step that prevents callbacks)
This is where most NLC projects fail in practice. The system is installed, commissioned, and working perfectly on the day the contractor walks out. Then the facility manager gets a complaint that "the lights in the conference room keep turning off during long meetings" and does not know how to change the occupancy timeout from 15 minutes to 30. They call the contractor. That is a callback that should never have happened.
The handoff package
At project completion, deliver a physical or digital handoff package that includes:
- Zone map (final version). Updated to reflect any changes made during commissioning. Show every fixture, its zone assignment, and the control profile for that zone.
- Control profile documentation. For each zone: the dim level, occupancy/vacancy mode, timeout duration, daylight harvesting settings, and scheduling profiles. This is the "as-built" for the controls layer.
- Dashboard login credentials. The URL, username, and password for the cloud management dashboard. Also document the phone app name and the project access credentials.
- Quick-reference guide. A single page (or one screen in a PDF) that shows the three things the facility manager will actually need to do: how to change a zone's dim level, how to adjust the occupancy timeout, and how to modify the schedule. Skip the 40-page user manual. Give them the 3 tasks they will actually perform.
- Warranty documentation. For both the fixtures and the control system components (sensors, gateway). Include the manufacturer's support contact information.
The 30-minute walkthrough
Walk the facility manager through the dashboard live, on their own device, in the building. Have them change a schedule, adjust a dim level, and check the energy report while you are standing next to them. Thirty minutes of hands-on training prevents thirty phone calls over the next six months.
| Zone | Mode | Target | Timeout | Schedule |
|---|---|---|---|---|
| AOffice perimeter | Daylight harvest+ occupancy auto ON/OFF | 40 fc | 20 min | 6 AM–8 PMOff after hours |
| BOffice interior | OccupancyAuto ON/OFF | 40 fctuned from 55 | 20 min | 6 AM–8 PMOff after hours |
| CConference | VacancyManual ON, auto OFF | 30 fcdimmable | 15 min | 24/7Always available |
| DPrivate offices | VacancyManual ON, auto OFF | 40 fc | 20 min | 6 AM–8 PMOff after hours |
| ECorridor/Break/RR | OccupancyAuto ON/OFF | 20 fc→ 10 fc standby | 15 min | 24/7Always on |
NLC project planning checklist
Use this as a pre-flight check before starting any networked lighting controls project.
| Phase | Check item |
|---|---|
| Discovery | Client goals documented (energy savings, code compliance, comfort, certification). |
| Discovery | Operating hours by zone confirmed. |
| Discovery | Daylight availability assessed (window locations, orientations). |
| Discovery | BMS integration requirement confirmed or ruled out. |
| Discovery | Budget tier agreed (Z10-ready deferred vs. full LLLC now). |
| Survey | All fixture locations, types, and wattages documented. |
| Survey | Z10-readiness of existing fixtures confirmed (for retrofits). |
| Survey | Daylight zones mapped (perimeter, transition, interior). |
| Survey | Occupancy patterns by area documented. |
| Survey | Sensor line-of-sight obstructions identified. |
| Survey | Gateway location identified (power + network access). |
| Specification | NLC system capabilities verified against project requirements (see Phase 3 table). |
| Specification | DLC NLC QPL listing confirmed for the system. |
| Specification | Zone map completed with control profiles for every zone. |
| Specification | Utility NLC rebate eligibility confirmed. |
| Commission | All fixtures powered and sensor modules detected. |
| Commission | All fixtures assigned to correct zones via commissioning app. |
| Commission | Control profiles configured per zone map. |
| Commission | Occupancy, daylight, and scheduling tested per zone. |
| Commission | Gateway connected and dashboard accessible. |
| Handoff | Final zone map delivered to owner. |
| Handoff | Control profile documentation delivered. |
| Handoff | Dashboard credentials delivered. |
| Handoff | 30-minute live walkthrough completed with facility manager. |
| Handoff | Rebate application submitted with NLC documentation. |
Frequently asked questions
When should controls be introduced in a lighting project?
At the very beginning. Controls should be part of the initial project scope, not added after fixtures are already specified. The control strategy affects fixture selection (Z10-ready or not), circuit design, sensor placement, and the rebate application. Adding controls late limits what the system can do and usually increases installation cost.
How long does commissioning take?
For Bluetooth Mesh systems, budget 2-4 hours per 100 fixtures after all fixtures are installed and powered. The largest time block is walking the building and assigning each fixture to its zone in the app. A well-prepared zone map cuts this time significantly because the installer knows which fixtures go where before they start.
What documentation should I give the building owner?
At minimum: the final zone map, control profile settings for each zone, dashboard login credentials, a one-page quick-reference guide showing how to change dim levels, adjust occupancy timeouts, and modify schedules, and warranty documentation for fixtures and controls. This package prevents the majority of post-installation callbacks.
Can I add NLC to existing LED fixtures?
Yes, if the fixtures are Z10-ready (have a ZHAGA Book 18 sensor receptacle). Plug in the sensor modules, commission via the app, and the system is live without replacing fixtures or pulling new wire. If existing fixtures are not Z10-ready, retrofit options exist but cost more. Most Jarvis indoor fixtures and several outdoor fixtures ship Z10-ready.
What is the biggest mistake contractors make on NLC projects?
Treating controls as an afterthought. When controls are added late, the fixture layout, circuit design, and budget are all locked into configurations that may not support the optimal control zones. The result is a system that technically works but underdelivers on savings and user experience. Controls must be part of the scope from the first site survey.
