AleoBlue in the Field: Real-World Results With Luminaire-Level Controls

When contractors hear “networked lighting controls,” they often picture extra devices, extra wiring, and a commissioning day that turns into a callback. Luminaire-level lighting controls change that equation by moving sensing and control closer to the fixture, then using a wireless network to coordinate behavior across a space.

This article shows what luminaire-level lighting control looks like in practice using published AleoBlue case studies, along with a contractor-focused checklist you can apply to your next bid. It builds on our earlier discussion in Lighting Controls in 2026: What Contractors Need to Know and the technical breakdown in Inside AleoBlue: How Wireless Lighting Control Simplifies Commercial Projects.

Case Study 1: Medical Clinic With Fast Commissioning

A new medical clinic project needed a full-featured controls package with zoning, occupancy sensing, scheduling, high-end trim, and manual dimming. The contractor also wanted a system that would meet the design intent without turning controls into a labor sink.

In Aleo’s Northern Valley Indian Health case study, Aleo reports a deployment that included 350 luminaires with sensors, plus wireless dimmers and ceiling sensors. Aleo also reports that interior commissioning was completed in 4 total man-hours after a 20-minute training call, with an average provisioning time of roughly 30 seconds per device. The case study also includes an “over 80%” labor cost savings claim for controls implementation. These results are manufacturer-reported.

Why this matters to contractors

When the workflow is built around provisioning and grouping rather than landing control wiring, commissioning can be scoped more clearly and executed more consistently. It also helps when scheduling is expected across multiple areas, which is common in clinics and other owner-operated facilities.

Case Study 2: Government Office Building With High Reported Savings

On larger facilities, the concern is usually scalability. The question is not only whether the network can cover the building, but whether zoning, daylight strategies, and overrides can be implemented without ambiguity.

In Aleo’s Los Angeles County building case study, Aleo reports energy savings of over 75% after deploying AleoBlue with strategies that include occupancy sensing, daylight harvesting, and zone linking. These results are manufacturer-reported.

What to take from this case

On multi-floor projects, the largest risks are often scope-related: unclear zone definitions, missing sequence details, and undefined expectations for scheduling and overrides. If the sequence of operations is implied but not written, commissioning time and callback risk tend to increase.

Case Study 3: Retrofit Troffer Kits and the Role of Controls

Retrofits are where contractors most often consider luminaire-level controls as a value alternative, since adding control wiring can be disruptive and costly in existing spaces.

In Aleo’s Roy Miller Freight Lines case study, Aleo reports 74% savings from the LED retrofit portion without controls, then presents an estimated “control factor” energy savings of 50% based on projections and similar applications. The case study notes that measurement and verification had not been conducted at the time of writing, and includes customer feedback that the sensors were an added benefit and expected to increase savings.

Contractor takeaway

In intermittently used spaces, occupancy-based control helps prevent “always on” behavior that erodes LED payback. When savings are estimated, it is best to present them as estimates and lead with functionality, installation impact, and compliance first.

What Contractors Should Look for on Plans

If you are trying to identify whether a luminaire-level approach is already specified, or could be proposed as a value-engineered option, scan for:

• Fixture schedules that call out integral sensors, control nodes, or wireless control compatibility
• Control sequences that imply per-fixture dimming, daylight zones, or granular occupancy response
• Notes referencing networked lighting controls (NLC) or luminaire-level lighting controls (LLLC)
• Daylight harvesting language without a clear wired control diagram

If these show up, you may already be in luminaire-level territory in practice, even if the drawings do not use that exact term.

Reducing Bid Risk: Scope Items to Clarify Early

These questions prevent rework and startup surprises:

1. Who owns commissioning and programming, and what is the acceptance criteria?
2. Are owners expecting centralized scheduling, dashboards, or BMS integration?
3. Is the control network required to connect to the customer's IT network?
4. What is the override requirement (local wall control, app-based control, or both)?
5. What documentation is required at turnover (as-builts, zone lists, sequences)?

Get Help Reviewing Controls and Options

If you are bidding a project with networked controls, or you want to propose a luminaire-level approach as a value alternative, we can help you evaluate the drawings and build a clean, defensible scope.

• Send us your reflected ceiling plan, fixture schedule, and controls narrative
• Tell us the project type, jurisdiction, and timeline
• We will help you identify scope gaps and determine whether an AleoBlue approach is a fit

Contact us to review your project and explore practical control-ready options that are straightforward to install and straightforward to commission.