A workable overnight schedule for a car dealership parking lot separates the site into zones, holds each zone at a lower, project-defined standby output during quiet hours, and commands a higher-output state when a qualifying vehicle or person enters. The standby level, timeout, and override behavior are requirements you define for your site, not fixed settings that apply everywhere. Getting this structure right matters more than picking a specific dimming percentage, because the zone and trigger logic determines whether the system responds the way you actually need it to.
A single sitewide timer that just dims everything at midnight is not the same as bi-level control. It cannot tell the difference between an empty service lot and a customer walking through the display area, so it either wastes light or leaves zones under-lit exactly when someone needs visibility.
Key Takeaways
- Bi-level dimming pairs a scheduled standby state with an event-driven higher-output state; both states should be written as project requirements, not assumed defaults.
- Dealership zones such as sales/display, service, delivery, employee, and perimeter areas often need different schedules and triggers rather than one sitewide profile.
- Standalone scheduled, sensor-linked, and networked control architectures each fit different combinations of zoning, activity, and monitoring needs.
- A documented 0-10V dimming input on a fixture does not by itself prove the sensor, controller, driver, and load will work together as a bi-level system.
- Commissioning should confirm each zone's actual behavior against the written requirement before the schedule is accepted.
How a Dealership Overnight Bi-Level Schedule Works
Bi-level dimming means a fixture or zone holds a lower scheduled output during defined quiet hours and switches to a higher output when a specific event occurs. The actual light levels, response timing, and energy profiles depend on your facility and equipment, and should be set through project-specific design.
Define the Two Lighting States
The standby state is the lower output level a zone holds during a scheduled quiet period, such as after closing and before the first morning activity. The active state is the higher output level commanded when a qualifying event, like a person or vehicle entering the zone, is detected. Both states, along with the transition speed and how long the active state holds before returning to standby, need to be defined for your fixtures and confirmed with your control equipment. Nothing about the two-state concept guarantees a specific energy reduction or security result; it only describes the mechanism.
Write the Schedule as a Control Requirement
Before selecting hardware, write down each zone's operating period, its standby behavior, the trigger that should raise output, the resulting active behavior, the timeout back to standby, and any manual override the owner needs. This document is a planning requirement, not a fixture specification sheet. Once it exists, you can test whether a proposed sensor, driver, and controller combination can actually deliver that sequence, instead of discovering gaps after installation.
Map Dealership Zones and Operating Periods
Different dealership areas usually need different overnight treatments because their activity patterns and visibility needs are not identical. Mapping zones before picking hardware prevents a single schedule from being both too dim where people still walk and unnecessarily bright where nothing moves.
We cover a fuller version of this zoning process, including mounting context and glare considerations, in our guide to map exterior lighting zones.
Separate Customer-Facing and Operational Zones
Sales and display rows often stay visually important after closing, since inventory remains on view to passing traffic and late browsers. Service, delivery, and employee areas may go quiet earlier and have narrower, more predictable access windows. Recording when each area is actually used, rather than assuming the whole lot behaves the same way overnight, is the first input into a workable schedule.
Account for Human, Vehicle, and Nuisance Movement
Each zone needs a defined answer to a simple question: what kind of activity should raise its output? A display row may need to respond to a person walking the lot, while a drive lane may need to respond primarily to vehicle entry. Review approaches, blind spots, and mounting context with whoever is designing the sensor layout, because a sensor tuned for human-scale movement will not necessarily register a vehicle the same way, and nuisance sources like street traffic or blowing debris can trigger unwanted activations if coverage is not reviewed for the specific zone.
Choose Operating Periods Deliberately
Business hours, the closing transition, the quiet overnight stretch, and any scheduled late-access window (for example, a driver returning a loaner vehicle) can each be a distinct planning state rather than one long "after hours" block. Document any owner override, such as a manual full-brightness command during a security walk-through, before you select a controller, since not every architecture supports manual overrides the same way.
Choose the Control Architecture for the Site
The right control architecture depends on how many zones you have, how each one should respond to activity, and whether you need centralized monitoring, not on one system being universally best. The table below compares the three common planning paths.
| Approach | Best fit | Purchasing/design implication | Limitation |
|---|---|---|---|
| Standalone scheduled | Simple sites with limited event-response needs | Lower upfront complexity; less commissioning | May not raise output for entry events unless paired with a sensor |
| Sensor-linked | Zones where local activity should raise output | Requires coverage, trigger, and timeout verification per zone | Detection quality depends on mounting and geometry, not just sensor rating |
| Networked | Multi-zone sites needing monitoring, alerts, or coordinated overrides | Adds platform, commissioning, and documentation requirements | More points of failure and setup effort than a standalone zone |
Compare the Three Planning Paths
A scheduled-only approach can hold a standby level reliably but will not add a higher-output response unless it is paired with a sensor input, so it usually falls short of a full bi-level requirement on its own. A sensor-linked zone adds that response but needs its detection coverage, trigger behavior, and timeout verified for the specific area, not just the sensor's rated range. A networked system lets you adjust schedules, monitor energy use, and receive alerts across zones from one place, which is useful once a site has enough zones or reporting needs to justify the added setup.
Let the Site Condition Choose the Path
New construction can coordinate the fixture, driver, sensor, and network design from the start, which usually simplifies architecture selection. A retrofit with mixed or undocumented existing equipment is a different situation: an inventory of what is already installed, or a limited pilot zone, often makes more sense than committing the whole site to one architecture immediately. A commercial parking-area controls case study documents how dedicated zones, adjustable schedules, sensor inputs, timeouts, and overrides were coordinated on one site; it illustrates the components involved but does not establish what settings or savings a dealership lot would see. For zone-level detection design specifically, our follow-me lighting design guide covers how perimeter sensors are laid out for that kind of response.
Verify Fixture, Sensor, and Control Compatibility Before Buying
Before ordering fixtures or retrofitting controls, verify the complete chain from fixture through driver, sensor, controller, and load, because a single specification field cannot confirm the whole sequence will work. Stop the purchase or control change until a qualified electrician, lighting designer, or other responsible project professional confirms this interface, the total connected load, manufacturer instructions, and any applicable local requirements.
Pre-Buy Verification Checklist
- Fixture and driver: exact model, input voltage, wattage, connected load, dimming input type, and the manufacturer's control instructions for that model.
- Sensor and controller: sensor type and rating, detection coverage, mounting context, trigger and timeout behavior, grouping and override options, and the controller's communication protocol.
- System and project: 0-10V compatibility where applicable, total connected load across the circuit, expected behavior with mixed fixture types, available documentation, photometric requirements, and any owner or local review standards.
Interpret Product Specifications Narrowly
A fixture documented with a 0-10V dimming input or a motion-sensing feature confirms that starting fact for that specific model and configuration, and nothing beyond it. It does not by itself prove that a particular sensor, controller, or scheduling platform will produce the bi-level sequence you designed, or that the same behavior applies to a different model in the same product line. Confirming the full chain against current manufacturer documentation, and having the responsible project professional review it, is what actually establishes compatibility.
Commission the Overnight Sequence and Review Exceptions
Before accepting the schedule, walk each zone through its written requirement and confirm the system actually does what was planned. This step tests behavior against the requirement you wrote earlier; it does not replace the compatibility checks already covered above.
Review the Intended Sequence by Zone
Confirm that the scheduled standby state begins and ends at the intended transition time for each zone, and that the defined trigger, whether a person, a vehicle, or a gate approach, produces the intended active-state behavior. Where relevant, walk through late delivery, employee access, and any owner override to confirm each behaves as written.
Document Exceptions Before Acceptance
Record any missed activations, nuisance triggers, unexpected timeouts, or inconsistent behavior between fixtures in the same zone, and assign each one an owner for correction. If a layout involves mixed or older fixtures and the specification sheets alone do not make the expected result clear, our photometric planning support page is one option for working through a layout before final acceptance. Unresolved electrical, photometric, or local-requirement questions belong with the responsible project professional rather than being guessed at during commissioning. If sensors are triggering inconsistently once installed, our motion-control diagnostic flow walks through checking placement, coverage, and timing.
Once every operational exception is resolved and logged, submit the finalized sequence of operations to the facility manager and servicing contractor to establish the official baseline for future maintenance.
FAQs
Can an existing dealership lot be retrofitted for bi-level dimming if the current fixtures have no documented sensor or dimming interface?
Feasibility cannot be assumed from the fixture's age or wattage alone. Start by inventorying the exact existing fixtures and drivers and obtaining current manufacturer documentation for each model before choosing a control architecture, since undocumented equipment may need replacement, a limited pilot zone, or a professional compatibility review before a sitewide retrofit makes sense.
Does a fixture labeled 0-10V automatically work with motion-triggered bi-level control?
No. A 0-10V label confirms the fixture accepts that dimming input, but it does not confirm that a specific sensor, controller, and scheduling platform will produce the sequence you need, or how the driver actually responds under load. Verify the complete fixture-driver-sensor-controller chain, including wiring architecture, through a qualified professional before relying on that label as proof of system compatibility.
Who confirms whether an overnight dimming schedule meets local code, owner, or insurance requirements?
That determination belongs to the responsible lighting designer, qualified electrician, dealership owner or facility representative, insurer, and local authority for your specific project. No planning guide can confirm code compliance or insurance approval in advance; those requirements vary by jurisdiction and by the insurer's own standards, so they need direct confirmation before the schedule is finalized.
