Cleaning factor scenario calculator Australia
Compare maintained lumens under two user-entered cleaning or maintenance factor scenarios.
Compare factor scenarios
Name both factors, then compare the maintained-output difference.
- 1Enter initial lumens
Use one lighting group.
- 2Enter factor A
Label the first scenario.
- 3Enter factor B
Label the second scenario.
- 4Read the difference
Carry the result to maintenance notes.
Application formula fit
Match the query to the exact lighting quantity and calculation direction before using the output.
| Search phrasing | Calculator case | Carry forward |
|---|---|---|
| maintenance factor lighting | Two factor assumptions need a visible comparison. | Carry maintained-output difference. |
| cleaning factor lighting | Cleaning state changes useful output. | Keep scenario labels visible. |
| lighting calculation methods | Scenario arithmetic before a fuller maintenance note. | Pair with maintained lumens. |
Reading the technical output
Each result supports a calculation note, measurement comparison or next calculator input.
| Output | Technical meaning | Later check |
|---|---|---|
| Scenario B lumens | Initial lumens multiplied by factor B. | Compare with scenario A. |
| Scenario A lumens | Initial lumens multiplied by factor A. | Carry to maintenance note. |
| Difference | Scenario B minus scenario A. | Review practical significance. |
Assumptions that stay visible
Formula pages are clearest when units, factors and measurement state stay beside the number.
| Assumption | Why it matters | Where it belongs |
|---|---|---|
| Scenario labels | A and B need clear meanings. | Maintenance note. |
| Initial lumens | Must match the same group. | Fitting group note. |
| Factor values | User-entered assumptions. | Source note. |
Maintained output under two factors before the number
A useful cleaning factor scenario note starts by naming the quantity being estimated. Candela, lux, luminance, reflectance, room cavity ratio, lumen depreciation, colour temperature and control-zone load are not interchangeable values.
That boundary keeps the result from becoming a vague lighting promise. Write the source value, the unit, the measured surface or operating state and the reason for the conversion beside the number.
Formula pages are support pages
Scenario multiplication helps explain one calculation step. It does not replace a full lighting design, photometric file, site measurement, glare review, equipment data or formal project criterion.
The value is still high when the number travels with its assumptions. A calculated candela, weighted reflectance or control-zone load can make the next lighting note easier to review because the intermediate step is visible.
Inputs need a matching source
Factor values need a cleaning or maintenance assumption source. A measured value, fitting data value, user-entered factor and planning target carry different confidence levels. Do not blend them without noting where each input came from.
If a value comes from a data sheet, keep the direction, operating state and measurement condition visible. If it comes from a site reading, keep the meter position and active scene visible.
Direction matters
Many photometric equations reverse cleanly on paper but mean different things in a project note. Candela-to-lux estimates a received level from directional intensity, while lux-to-candela asks how much intensity would be needed at a distance.
Reflectance and luminance pages also depend on surface assumptions. A diffuse approximation is not the same as a glossy surface, an angled view or a measured luminance camera result.
Avoid hidden thresholds
These calculators avoid pass/fail thresholds. A ratio, loss percentage, RCR value or capacity margin can inform a lighting note, but the page does not decide whether a workplace, public space, healthcare room, school room or emergency path meets a formal requirement.
If the number will be compared with a formal criterion, keep that criterion outside the arithmetic and cite the correct project source.
Rounding should match the use
Photometry can produce many decimals, but most planning notes need practical precision. Lux, candela, lumens, percent, CCT and load values should be rounded enough to read without pretending the inputs are exact.
Use more digits only when the input measurement really supports them. A short explanatory note is often more useful than a long decimal.
Measured checks close the loop
same-group lux checks before and after maintenance can reveal whether the calculation direction was useful. A calculated lux value may look tidy while the real surface is blocked, glossy, dirty, dimmed or aimed differently.
Keep measured and calculated values on the same plane or operating state. If they differ, investigate the input source before changing the target.
Show uncertainty without hiding the number
A support formula often combines values with different confidence levels. A measured lux value, a published intensity value, a user-entered allowance, a reflectance estimate and an operating-hour assumption should not be treated as equally certain. The note should say which input is measured, which is copied from data, and which is an assumption.
That uncertainty note does not weaken the calculator. It makes the result easier to improve later. If a better reflectance reading, cleaner lumen-depreciation value, confirmed CCT mix or measured control-zone load becomes available, only that input needs to change while the calculation direction stays clear.
Give the note a review condition rather than a vague review date. Recheck when the fitting data changes, when a surface finish is repainted, when cleaning intervals change, when a new control zone is added, or when a measured reading disagrees with the calculated value. That keeps the formula useful without turning it into a broad promise.
For multi-row notes, label the row that drove the decision. A high reflectance surface, longest distance, weakest cleaning factor, largest zone load or lowest remaining lumen value may be more important than the average. Naming that driver makes the formula easier to check.
Add the comparison basis as well: measured value, calculated value, data value, user-entered assumption or rounded planning value. That single label helps another reader understand why two numbers that look similar may carry different confidence.
Connect the formula to a visible lighting job
Photometry support pages are easiest to trust when the final note names the visible lighting job. A candela conversion might support a point on a path, a luminance estimate might describe a wall surface, a room cavity ratio might support a lumen-method check, and a control-zone load might support a switching note.
Without that visible job, the value can drift into a loose number that nobody can verify on site. Add the surface, zone, operating state and linked calculator beside the result. The follow-on calculation might be measured lux, beam coverage, room lighting, strip load, maintenance output or energy cost, depending on what decision the formula supports.
Australian scope limits
cleaning factor scenario pages on AuLumens are formula and diagnostic calculators for lighting notes in Australia. They stay outside emergency lighting, public roads, sports lighting, school spaces, healthcare tasks, car parks, wiring design and certification decisions.
Do not treat the scenario comparison as a maintenance instruction or compliance result. Keep specialist criteria, site modelling and installer decisions in the proper project review. The calculator result is a transparent arithmetic step.
A concise technical note
A readable note includes the input values, units, calculation direction, output value, rounding, measurement state and any factor used. For multi-surface or multi-zone pages, name each surface or zone rather than hiding it in a total.
Pair it with utilisation-maintenance-factor and maintenance-interval-lumen-loss when documenting assumptions. That context lets another person repeat the calculation, compare a measured value or move the result into the calculator that owns the next lighting decision.