Campus time-based dimming should follow actual activity and the required lighting performance in each zone. Entrances, crossings, accommodation routes and quiet paths need separate schedules. A proposed percentage is a control setting, not proof that a location remains adequately lit.
Build the schedule around campus use
Review class timetables, residences, events, late transport, security patrols and emergency access. Record which areas remain active after normal hours. Define minimum acceptable maintained lighting and who can approve temporary changes.
The following example demonstrates energy accounting only. Its levels and times are not campus recommendations. Assume a particular luminaire has measured input of 40 W in an evening stage and 16 W in a reduced stage.
| Illustrative stage | Duration | Measured input | Energy |
|---|---|---|---|
| Evening activity | 5 h | 40 W | 200 Wh |
| Reduced activity | 7 h | 16 W | 112 Wh |
| Control electronics | 12 h | 1 W | 12 Wh |
| Total | 324 Wh |
A control command of 40% is not necessarily 40% of full input power or light output. Measure the proposed driver/LED combination at the scheduled settings. Include additional triggered operation and any daytime or continuous devices in the complete daily budget.
Separate the control layers
Identify the driver dimming interface, controller, local clock or sensor, network and management platform. NEMA or Zhaga connector arrangements are not the same kind of information as NB-IoT, LoRaWAN or cellular communications. Check compatibility for the actual devices and versions.
Specify where schedules are stored and what happens when the network is unavailable. A local fallback must maintain the agreed service. Test clock accuracy, time-zone settings, seasonal changes and restoration after power loss.
Check lighting and energy together
Run photometric checks for the required operating stages and inspect crossings, entrances and steps on site. Occupancy triggering should not cause abrupt or unsafe transitions. Set hold times and overlap between adjacent fixtures through a trial.
For solar poles, recalculate battery reserve and seasonal recharge using the complete schedule. Reduced demand may improve the energy margin, but it does not establish a universal battery-ageing effect. Use the pack’s actual operating conditions and documented data.
Commission and retain records
Verify stage power, schedules, manual override, event operation, network-loss fallback and fault alarms. Record baseline energy and use the same measurement boundary for later comparisons. Keep authorized settings and operator responsibilities with the handover documents.
Frequently asked questions
Does a 50% dimming command mean 50% electricity consumption?
Not necessarily. Measure the actual luminaire input at the command level and use that result in the energy calculation.
Can the same schedule be applied across the entire campus?
Only if the lighting and activity requirements support it. Different zones and events often need different schedules.
What should happen if the control network fails?
The lights should follow an agreed local fallback. Test schedule retention, recovery and the required lighting service before acceptance.
Related reading
- Smart vs Conventional Street Lights: Functions and Controls
- Remote Street Light Control and Dimming: How It Works
Prepare your project enquiry
Send the location, layout, required lighting schedule and documentation needs to sales@mclsolar.com. The proposed models, available evidence and commercial terms should be confirmed in the quotation.