How do I choose schedules vs motion-based dimming?
Start with schedules when operating hours and traffic patterns are predictable (campus gates, parking peaks, fixed shifts). Use motion-based dimming only where activity is irregular and detection is reliable. A practical approach is schedule as the baseline, and motion as an “override” for specific zones.
What areas should never be dimmed?
Define “never-dim” zones before rollout: crosswalks, gates/entrances, critical routes, and any area where visibility is safety-critical or tied to security operations. If exceptions are needed, state them explicitly (no silent defaults).
How do you prevent flicker and complaint-prone transitions?
Use ramp transitions (smooth step changes), set a sensible hold time for motion triggers, and avoid frequent up/down adjustments. Complaints usually come from rapid changes near walkways and entrances—treat those as higher-baseline zones with fewer transitions.
What is the safest fallback when sensors/comms fail?
Default to safe predictable light: either stay-on at a defined baseline or enter a safe mode that protects critical zones. The fallback rule should be written as a pass/fail requirement so a “dark event” cannot be treated as acceptable behavior.
How do you define acceptance checks for dimming behavior?
Acceptance should include: schedule execution (correct zones and times), motion trigger + hold behavior (if used), transition smoothness (no flicker), and fallback behavior under simulated faults. Also confirm “never-dim” zones remain compliant under all modes.
What inputs speed up a dimming strategy recommendation?
Provide: operating hours, zone priorities (crossings/gates/walkways/CCTV), preferred dimming stages, and any “never-dim” constraints. If motion is required, include sensor scope (trigger distance/hold/override). A simple site sketch with zone labels helps reduce clarification rounds.
