Lighting
Occupancy Sensor Savings Calculator
Use Occupancy Sensor Savings Calculator to calculate annual energy saved from controlled lighting power and avoided operating hours. Keep the entered conditions with the answer so later comparisons are fair.
Calculate Annual energy saved
Use one Occupancy Sensor Savings case at a time; save a new run when a condition changes.
What annual energy saved means here
The displayed annual energy saved answers one bounded question: calculate annual energy saved from controlled lighting power and avoided operating hours. Treat it as a case record rather than a general approval.
Occupancy Sensor Savings changes with mounting height, beam shape, surface reflectance, and driver limits.
If two cases differ in controlled lighting power, save them as separate runs. A blended entry can hide the reason the annual energy saved changed.
Avoided operating hours and the other entries
On Occupancy Sensor Savings, confirm decimal placement and unit scale before using annual energy saved; small prefixes can move an electrical result by orders of magnitude.
- Controlled lighting power. Example value: 2.5 kW. Enter controlled lighting power in kW.
- Avoided operating hours. Example value: 900 h. Enter avoided operating hours in h.
If this answer becomes an input to Candela Lumens, copy the value with its units and source note attached.
The Occupancy Sensor Savings equation
Only the entries shown on Occupancy Sensor Savings feed annual energy saved. If another correction factor matters, keep it in the notes or make a separate run.
The formula uses Controlled lighting power, and Avoided operating hours to produce Annual energy saved. Unit mistakes usually show up as an answer that is off by a factor of 10, 100, or 1,000.
The Annual energy saved value and any supporting metrics belong to this same Occupancy Sensor Savings case, not to a nearby run with different inputs.
Sample Occupancy Sensor Savings run
Using the sample values, Controlled lighting power = 2.5 kW; Avoided operating hours = 900 h, the primary result is 2,250.00 kWh.
This Occupancy Sensor Savings one-input test is a scale check, showing direction and sensitivity without turning the changed case into a recommendation.
If the changed controlled lighting power comes from a real measurement, keep the original Occupancy Sensor Savings run so the source of the difference remains clear.
Turning annual energy saved into a decision
Read annual energy saved together with the input values, not as a standalone fact. The same number can imply different decisions under a different equipment rating or operating period.
Occupancy Sensor Savings changes with mounting height, beam shape, surface reflectance, and driver limits.
Changing controlled lighting power while leaving avoided operating hours fixed is a useful way to see which assumption controls the answer.
What not to assume from Occupancy Sensor Savings
Measure actual schedule changes where possible.
- Driver headroom
- Beam angle
- Surface reflectance
When annual energy saved is close to a rating, use the stricter review path instead of relying on the extra decimals shown by Occupancy Sensor Savings.
Notes to save with Occupancy Sensor Savings
Keep fixture model, mounting height, distribution angle, and target plane with the Occupancy Sensor Savings result.
| Input set | Controlled lighting power, and Avoided operating hours |
|---|---|
| Result | Annual energy saved |
| Condition note | Measure actual schedule changes where possible. |
Keep screenshots or notes only when they identify the Occupancy Sensor Savings source values. A saved final number without entries is hard to audit.
Common Occupancy Sensor Savings questions
Should nameplate and measured values be mixed?
Only mix nameplate and measured values in Occupancy Sensor Savings when that mix represents the actual case. Otherwise keep them in separate runs.
What should be recorded with the answer?
Save the Occupancy Sensor Savings inputs, unit basis, operating case, and result note so annual energy saved can be reproduced later.