Monthly lighting running cost notes
Monthly running cost turns a counted lighting group into kWh and AUD for a user-entered month, without modelling a whole energy account.
Monthly cost sequence
Name one lighting group, enter the monthly period and read kWh before money.
- 1Name the group
Choose the room, row, common area or lighting scene included in the month.
- 2Enter the connected load
Count fittings and enter input watts for the same group.
- 3Set the monthly period
Enter daily hours and days in the month or selected period.
- 4Add the energy rate
Enter the cents per kWh value used for this estimate.
- 5Read the period result
Keep the cost tied to the same month, group and rate.
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 |
|---|---|---|
| Lighting running cost per month | One lighting group with fitting count, watts, daily hours, monthly days and c/kWh. | Monthly kWh, monthly cost and connected load. |
| Home lighting cost | A room, shed, hallway or outdoor group with a known monthly pattern. | Room label, control state and entered energy rate. |
| Business lighting cost | A shopfront, office row or shared area for a short cost check. | Operating-days basis and later annual kWh note if needed. |
| Common area lighting | Long-hour lobby, corridor or amenity group for one month. | After-hours, sensor or shutdown cases when the pattern changes. |
Reading the result
Each output belongs to a bounded lighting energy estimate and should travel with its assumptions.
| Output | Technical meaning | Review item |
|---|---|---|
| Monthly cost | Monthly kWh multiplied by the entered energy rate. | Check the period before comparing with another month. |
| Monthly kWh | Connected kW multiplied by monthly run hours. | Carry to carbon or rate comparison only with the same period. |
| Connected load | Fitting count multiplied by watts per fitting. | Confirm the wattage basis for the included fittings. |
| Monthly hours | Hours per day multiplied by monthly days. | Keep weekends, closures and night operation visible. |
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 |
|---|---|---|
| Fitting count | Affects connected load directly. | Count only the lighting group being costed. |
| Watts per fitting | Turns fitting count into connected watts. | Prefer complete fitting input watts where known. |
| Monthly days | A short month, long trading month or closure period changes the total. | Write the month or period beside the result. |
| Energy rate | Money changes when the entered rate changes. | Keep the c/kWh value visible with the cost note. |
monthly lighting group before the number
A useful monthly lighting running cost estimate begins with the exact monthly 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
Monthly operating days and hours 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
Switching, dimming and sensors 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
A monthly comparison 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
monthly lighting running cost 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 not a metered account total or energy-plan choice. 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 annual kWh and energy-savings pages nearby when the estimate needs a full-year view. 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.