Controls change the lighting note
A lighting estimate can give a fitting count, lumen allowance or connected load, but controls decide when that load is active. A broad switch group can make an energy estimate look worse than the actual occupied pattern. An optimistic daylight or sensor assumption can make it look better than the real condition.
The control note should name the lighting zone, operating hours, dimming range, daylight condition, occupancy pattern and fallback state. The lighting control note table keeps those fields together before the energy savings calculator or lighting power density table is read.
| Control field | What to write | Why it matters |
|---|---|---|
| Zone boundary | Room, perimeter row, task bench, aisle, display wall or after-hours group. | Energy and lux comparisons change when zones are grouped too broadly. |
| Operating hours | Hours per day, days per year and seasonal or after-hours condition. | Annual kWh moves directly with time. |
| Dimming range | Minimum, normal task state and full-output state. | Partial output may change energy without changing installed load. |
| Fallback condition | Low daylight, override, cleaning mode or sensor bypass. | The fallback may define the highest load or lowest-light case. |
What the control question is really asking
Control searches often mix light level, energy, switching and daylight. A stronger lighting note separates the visual zone from the time schedule before any annual kWh or payback number is read.
| Search intent | Start with | Matching page |
|---|---|---|
| How many hours should go into the energy estimate? | Hours per day, days per year and seasonal condition for the exact lighting zone. | Energy savings calculator |
| What is the lighting zone? | The room, row, task surface or after-hours group that shares one control state. | Lighting zone glossary |
| How does dimming affect the estimate? | Normal output level, minimum level and full-output fallback. | Dimming range glossary |
| How should a sensor-controlled zone be recorded? | Observed on, off, dimmed, delay, daylight state and measured plane for one zone. | Occupancy sensor lighting control notes |
| How should daylight be recorded? | Orientation, daylight condition, control state and fallback condition. | Daylight factor calculator |
| Does the measured lux still apply? | Plane, meter point, active group and daylight condition. | How to measure lux levels |
Note owner for each control job
Control notes become easier to maintain when the page owns the right part of the question. A dimming state, annual kWh estimate, measured lux check and operating-hour schedule should not be collapsed into one note.
| Control job | Existing owner page | Keep in the zone note |
|---|---|---|
| Installed load | Connected load notes | Fitting group, input watts and zone boundary. |
| Annual energy | Annual lighting kWh calculator and annual kWh formulas | Load multiplied by the named hours only. |
| Control savings assumption | Lighting control kWh assumptions | Baseline state, changed state and evidence level. |
| Dimming behaviour | Dimming range calculator | Minimum, normal and full-output state. |
| Operating schedule | Operating-hours lighting schedule | Weekday, weekend, seasonal and after-hours rows. |
| Measured-light check | Lux meter reading notes | Same plane, point, daylight condition and active group. |
Separate the visual zone from the electrical group
A lighting zone is the area served by one lighting assumption. It may not match a circuit, switch plate or whole room. For lighting notes, the useful zone is the one that shares a task plane, control state and operating schedule.
In a home, the kitchen ambient group, bench lighting and dining pendant may need separate entries. In an office, perimeter desks, internal desks, meeting rooms and circulation paths may need separate entries. In a warehouse, aisles, packing benches, dispatch and after-hours movement paths may not share the same hours.
| Space | Better zone note | Weak note |
|---|---|---|
| Open-plan kitchen | Ambient, bench task and dining scene recorded separately. | Whole open plan area under one lighting note. |
| Office floor | Desk rows, meeting rooms, circulation and daylight perimeter rows separated. | Tenancy hours applied to every fitting. |
| Warehouse | Picking aisle, packing bench, loading zone and security mode separated. | All high-bays assumed to run the same hours. |
| Outdoor edge | Entry path, facade, car approach and spill-sensitive edge separated. | Exterior lighting treated as one group. |
Operating hours need a real basis
Annual energy is power multiplied by time. If the hours are guessed, the result is only a sensitivity check. Note the normal occupied hours, cleaning or stocking periods, after-hours security state, weekends and seasonal changes where they materially affect the estimate.
The operating hours glossary and connected load glossary keep the difference clear: connected load describes installed input watts, while operating hours decide annual kWh. The operating-hours lighting schedule table gives a compact note shape for repeated zones.
| Estimate input | Example note | Risk if omitted |
|---|---|---|
| Normal occupied hours | 8 h/day, 5 days/week for desk zone. | Full building hours may overstate energy. |
| After-hours mode | Circulation only at reduced output for cleaning. | Cleaning or security load disappears from the estimate. |
| Seasonal effect | Longer exterior hours in winter. | Annual result may be too low for outdoor groups. |
| Override condition | Manual override or sensor bypass noted. | Control savings may be overstated. |
Daylight and dimming are conditions, not shortcuts
Daylight may reduce electric-light demand in some zones and create glare or contrast in others. A perimeter office row, skylit kitchen bench or roof-lit warehouse bay should carry a daylight note and a fallback condition. The daylight factor calculator can explain the daylight relationship, but controls still need real operating assumptions.
Dimming also needs a defined state. A group that is normally at 60 percent output but occasionally at full output should note both states if the result matters. The dimming range glossary keeps this distinct from driver compatibility and wiring details.
| Control condition | Note | Boundary |
|---|---|---|
| Daylight row | Orientation, blind state, time condition and separate perimeter group. | A bright reading at midday does not prove night-time lighting. |
| Occupancy sensing | Sensor area, time delay, normal mode and bypass note, with sensor control notes where the observed state is the main note. | Public pages do not commission controls. |
| Dimming | Normal output, minimum output and full-output fallback. | Compatibility sits with driver and control gear notes. |
| Scene setting | Task, cleaning, after-hours or presentation mode. | Scene labels still need task-plane evidence. |
Same-zone comparison row
Before comparing energy or measured-light results, write one row that proves the same zone is being discussed. The row can stay compact while still separating visual evidence from load and time assumptions.
| Zone row field | Example wording | Why it matters |
|---|---|---|
| Zone ID | Office perimeter row P1, warehouse packing bench B2 or apartment lobby L1. | Prevents whole-building hours from replacing the actual zone. |
| Visual surface | Desk plane, bench plane, display face, aisle floor or corridor path. | Lux readings depend on the assessed surface. |
| Active group | Normal scene, daylight-dimmed row, sensor hold or full-output fallback. | Values from different states should not be merged. |
| Load basis | Connected watts for the same group only. | Annual kWh should not include unrelated luminaires. |
| Hours basis | Occupied hours, cleaning period, after-hours mode or seasonal row. | Time drives the energy result. |
| Measured condition | Point label, meter plane, daylight condition and date. | Keeps the lux note repeatable. |
Application notes
Operating hours are most useful when they are tied to a real application. A residential kitchen, a retail display row, an office perimeter row and an apartment corridor can carry very different schedules even when the connected load is similar.
| Application | Zone and hours issue | Note beside the estimate |
|---|---|---|
| Residential kitchen | Bench task light may run for shorter periods than general ambience. | Bench group, ambient group, evening scene and dimming range. |
| Office perimeter row | Daylight and blinds can change the normal output during occupied hours. | Orientation, daylight row, occupied hours and fallback condition. |
| Retail display | Display rows may run longer than back-of-house or circulation lighting. | Display zone, trading hours, cleaning mode and colour-quality note. |
| Warehouse aisle | Picking, packing, loading and security modes may not share one schedule. | Aisle group, packing bench group, after-hours path and sensor note. |
| Apartment common area | Long operating hours can make small load changes material. | Corridor, lobby, stair and emergency-lighting boundary kept distinct. |
Carry controls into the final estimate
Controls should not be an afterthought added after the lumen and load numbers. The note should sit beside the estimate so another person can repeat the assumptions or change one zone without rewriting the whole room.
| Note field | Example wording | Related page |
|---|---|---|
| Zone | Office perimeter desk row, daylight side. | Lighting zone glossary |
| Load | 12 luminaires x 18 W = 216 W connected load. | Lighting power density examples |
| Hours | 9 h/day, 240 days/year, separate cleaning scene. | Operating hours glossary |
| Schedule | Weekday, weekend, seasonal and after-hours rows kept distinct. | Operating-hours lighting schedule |
| Control state | Dimming normal 70 percent, full-output fallback recorded. | Dimming and driver terms |
| Boundary | Wiring, commissioning, emergency operation and formal verification sit outside the planning estimate. | Disclaimer |
Keep visual and energy notes side by side
A control note can explain both light levels and energy use, but those are different readings of the same zone. The measured-light line should name plane, point and state. The energy line should name load, hours and state. When those fields are aligned, a later reader can see whether the annual kWh change came from a load change, a schedule change, a dimming assumption or a different measured condition.
| Final check | Keep with the note | Related page |
|---|---|---|
| Zone and controls | Zone boundary, active group, dimmed state, sensor state and fallback. | Lighting control notes |
| Schedule | Normal, cleaning, after-hours, weekend and seasonal rows. | Operating-hours lighting schedule |
| Energy result | Connected load, hours and annual kWh for the same zone. | Annual lighting kWh |
| Control assumption | Baseline state, changed state and daylight or sensor condition. | Lighting control kWh assumptions |
| Measured evidence | Point label, plane, lux value and same active group. | Lux meter reading notes |
When zones and hours are clear, energy results become easier to challenge and maintain. The same note also helps explain why a room can have enough installed capacity while operating at different light levels during the day.