Holiday shutdown lighting savings notes
Holiday shutdown lighting savings compares the normal operating period with a defined shutdown window for the same load.
Shutdown sequence
Describe the normal lighting case, then remove it for the shutdown window and read the avoided cost.
- 1Name the load
Choose the lighting group that shuts down.
- 2Enter the normal hours
Use the usual daily operating period.
- 3Enter the shutdown days
Use the closure or holiday day count.
- 4Add the rate
Enter the cents per kWh used for the estimate.
- 5Read the avoided cost
Keep the shutdown basis visible.
Application estimate fit
Match the search phrase to one lighting load, period and assumption set before reading the result.
| Search phrasing | Calculator case | Carry forward |
|---|---|---|
| Holiday shutdown savings | One lighting group that is off during a defined closure. | Saved kWh and saved cost for the shutdown window. |
| Office closure period | A load that would otherwise run during holiday days. | Normal hours and shutdown days. |
| School or business closure | A period where the lighting would normally run but does not. | Keep the same load and annual rate. |
| Seasonal shut-off | A repeating closure or outage period with a known date range. | The shutdown day count used for the estimate. |
Reading the result
Each output belongs to a bounded lighting energy estimate and should travel with its assumptions.
| Output | Technical meaning | Review item |
|---|---|---|
| Shutdown cost saved | Avoided kWh multiplied by the entered rate. | Keep the shutdown period visible. |
| Shutdown kWh saved | Connected kW multiplied by avoided hours. | This is the energy avoided during the closure. |
| Avoided hours | Normal hours per day multiplied by shutdown days. | Use the same daily hours as the normal case. |
| Connected load | Lighting load included in the shutdown estimate. | Confirm the group basis before comparing results. |
Assumptions that stay visible
Small changes in load, hours, rate or factor can move the result, so the assumptions stay beside the number.
| Assumption | Why it matters | Where it belongs |
|---|---|---|
| Normal hours | The usual daily period that would otherwise run. | Keep the normal schedule visible. |
| Shutdown days | The number of days the lighting period is avoided. | Write the closure or holiday basis beside it. |
| Load basis | Connected watts should match the same lighting group. | Do not mix unrelated areas. |
| Energy rate | The avoided cost changes when the entered rate changes. | Keep the rate beside the result. |
shutdown lighting group before the number
A useful holiday shutdown lighting savings estimate begins with the exact shutdown lighting group, not a whole-site average. The same building can include reception lights, display lights, warehouse aisles, amenity rooms and exterior signs that all run for different hours. Naming the group keeps the load, hours and money value tied to one visible lighting job.
That boundary also makes later revision easier. If the fittings, scene level or operating period changes, the row can be revised without rebuilding unrelated areas. Write the space name, fitting family and control group beside the result so another person can check the same case later.
Connected load remains the anchor
Energy and cost estimates move when connected load changes. Count the fittings or enter the load that belongs to the named group, then keep the wattage basis visible. Complete fitting input watts are stronger than a bare lamp value because drivers, control gear and luminaire packages can change the actual load.
The connected-load note does not prove the light level is suitable. A lower load can still be too dim, glary or uneven, while a higher load may support a harder task. Keep lux, beam, colour and measured-light pages nearby when the lighting quality also needs checking.
Hours carry much of the movement
Normal hours and shutdown days can move the annual result more than a small wattage change. Seven-day corridors, hospitality scenes, office task rows, seasonal stores and after-hours security lights may all have different operating patterns even when the fittings look similar.
Enter the hours for the same lighting group named in the result. If the group has a normal scene and an after-hours scene, split those cases rather than hiding both in one average. A tidy input line with hours, days and control state is easier to revise than a single unexplained total.
Controls change energy without changing installed load
Shutdown state can reduce energy by shortening operating time or lowering average output. Occupancy sensing, daylight dimming, timeclocks, scene presets and holiday shutdowns all change the energy case while the installed wattage may remain the same.
Keep full connected load and controlled operation visible as different ideas. That separation lets a user compare the installed capacity, the normal operating case and the reduced-energy case without implying that the electrical installation has changed.
Rates and factors are user-entered assumptions
The entered energy rate belongs beside the result because it can change while the lighting kWh stays fixed. A rate comparison, carbon estimate or simple payback note is only as current as the entered cents per kWh, emissions factor or annual saving value.
For Australian lighting notes, keep the rate date, account basis or factor source in the project file if the result will be reused. This page keeps the arithmetic transparent; it does not choose an electricity plan, account structure, rebate or finance outcome.
Read comparisons as bounded arithmetic
Normal operation versus shutdown window is helpful when the two cases share the same lighting group and schedule basis. Rate A and Rate B, old hours and new hours, or full output and dimmed output should describe the same load before the numbers are compared.
A comparison can show the size of a difference, but it does not decide whether the lighting change is appropriate. Light level, comfort, controls, maintenance access and site operating needs still need their own notes when they affect the decision.
Monthly, annual and period values are different
Monthly values are useful for a short period or a local cost note. Annual values are useful for longer operating schedules, carbon factors and simple payback. After-hours and shutdown values describe only the named period, not the whole lighting account.
Keep the period wording in the result. A monthly cost, an annual kWh value and a holiday shutdown saving should not be compared until the period, hours and days have been made consistent.
Australian energy estimate limits
holiday shutdown lighting savings pages on AuLumens are planning estimates for lighting load, kWh, user-entered cost rates, carbon factors or simple payback. They do not model demand items, metered account totals, rebates, tax treatment, electrical design, emergency lighting or certification.
It is a period-saving estimate, not a full operational forecast. Keep account-specific charges, landlord agreements, emissions reporting basis and electrical installation details in the appropriate site file. The value of the lighting estimate is that it records the load, period and assumptions before those wider checks begin.
A concise calculation note
A readable note includes the lighting group, connected load, operating period, output state, user-entered rate or factor, and whether the result is monthly, annual or limited to a named period. For split cases, include both sides of the comparison.
Keep timeclock and after-hours pages nearby when the shutdown is part of a wider control pattern. That context makes the result practical. Another person can change the hours, revise the rate, adjust the control state or compare the result with measured energy data without guessing how the original number was produced.