Every floor on schedule, lighting matched to occupancy across the portfolio.
Lighting Control & Optimization for offices: three accumulative tiers (Essential / Managed / Optimized),
a Data Enabler with three models that lead with the BMS you already run, product-specific add-ons,
platform-wide add-ons, and a Custom advisory layer. Built for corporate portfolios where buildings already run a BMS,
floors are emptier and more variable on a hybrid-work baseline, and lighting that no longer matches how a building is used
quietly wastes energy — and lands on the ESG report.
ProductLighting Control & Optimization (1 of 3)
SegmentOffices — corporate portfolios and REITs with BMS-run buildings
StatusDraft for internal review
Versionv1 · June 2026
00 Products
Pick a product.
Each Keedian product targets a specific asset class in the building. Click a card to open its product page — the one marked This document is the page you're on.
Drop docs/shared/offices-building.png to see the illustration
Impact: There is no office lighting anchor customer — Chedraui and 7-Eleven are retail — so every figure is expected (pending validation), not a benchmarked result. Expected schedule discipline at Managed by reverting off-schedule zones — floor lighting left on overnight, lobby and cafeteria lights running when the space is empty; Optimized adds occupancy-driven dimming, common-area scheduling, and burn-hour-driven lamp-life planning on top, matching light to how the building is actually used. Per-tier ranges in the Expected outcome row below.
What it solves: Floor lighting left on overnight, lobby and cafeteria lights running when the space is empty, lights-left-on and lamp-out tickets on facilities staff, lighting energy that no longer matches a hybrid-work occupancy pattern, and off-schedule run-hours no central facilities team can manually police across a portfolio.
Main value drivers
Energy savingsAsset lifespanSustainability
01b Optimization Metrics
The metrics you'll want to optimize.
These are the operational metrics the product monitors. What changes across tiers is who acts on them — you (Essential), Keedian's Agentic Operations (Managed), or Keedian plus continuous tuning (Optimized) — and, where the data layer adds instrumentation, which signals become available.
The core metrics are summarized below. Full methodology, thresholds, diagnosis steps, and escalation criteria are in the Metrics Catalog.
Each metric includes definition, detection logic, diagnosis steps, recommended actions, escalation criteria, and prevention controls. Thresholds are reference values to be calibrated per client.
Each tier adds capabilities on top of the previous one. You never lose functionality by upgrading, and you can start at any tier.
Component
EssentialVisibility
ManagedAgentic Operations 24/7
OptimizedAgentic Operations + intelligence
Customer promise
"I can see and operate lighting across every floor and common area in my portfolio from one place — every zone on schedule, consistent standards, across every building."
"Keedian actively monitors my lighting 24/7, reverts off-schedule zones automatically, and dispatches only when remote action isn't enough. My floors and common areas stay lit to standard, my schedules are enforced, and I don't have to chase issues."
"Keedian keeps my lighting matched to how my buildings are actually used — occupancy-driven dimming on the floors, scheduled common areas, lamp life planned, and energy waste caught before it lands on the ESG report."
Expected outcome
Illustrative, expected (pending validation) — there is no office lighting reference customer (Chedraui and 7-Eleven are retail). Actual results depend on your current BMS / controls, the lighting share of the building's energy bill, occupancy patterns on a hybrid-work baseline, and lamp inventory. Energy figures are savings on lighting energy use, not the total utility bill.
Energy savings: Visibility / foundation
Asset lifespan: Foundation
Sustainability: Off-schedule run-hours made measurable
Energy savings: Reduced off-schedule run-hours (expected, pending validation)
Asset lifespan: Foundation
Sustainability: Eliminated off-schedule run-hours, evidenced for ESG
Energy savings: Further reduction via occupancy-driven dimming (expected, pending validation)
Sustainability: Sustained, evidenced reductions for carbon and ESG reporting
Data Enabler
Pick the model that matches what you already have
Model A — Keedian Direct
Per building: a lighting control + metering node at the panel — a smart relay/contactor with per-zone current sensing (CT) and scheduling, covering the floor and common-area zones (lobby, cafeteria)
One connectivity gateway per building (covers all monitored zones; shared with HVAC or Energy if those products are also contracted)
You keep the model you chose. The managed service is delivered the same way regardless of model.
Managed's Data Enabler, plus:
Model A:
Per-zone submetering / power-quality sensing on zones that need equipment-health depth — real power and current per zone for lamp-driver and ballast health
Additional optional sensors evaluated per building profile — occupancy sensing per floor and common area for occupancy-driven dimming, daylight / photocell sensing on perimeter zones, dedicated CT per zone for rigorous burn-hour and rebate validation
Site and portfolio dashboardsReal-time and historical visibility into the assets and metrics included in scope, with live alarms where applicable
Cross-site benchmarking with outlier detectionSee which locations drift from the fleet
Ticket workspaceAlarms auto-filter into a managed queue that you and your team work yourselves: triage, resolve remotely, or dispatch on each ticket
Conversational AI AssistantNatural-language questions on your data plus automated anomaly detection across the fleet
Lighting Remote CommandSwitch circuits on or off and push lighting schedules to one site or the whole fleet
And moreRole-based access, alarm history, data export, web and mobile parity
Everything in Essential
SLA tracking and service performanceLive SLA compliance against contractual targets per priority level
Standard CMMS integrationOut-of-the-box connectors for Fexa, Corrigo, ServiceNow and others; custom field maps or workflow adjustments may apply depending on your configuration
And moreClosure evidence on every ticket, weekly ops digest, post-incident reviews
And moreCross-site benchmarking with savings ranking, custom optimization rules, executive briefing reports
Managed service scope
Identical regardless of Data Enabler model (A, B, or C)
No managed service.
You and your team manage alarms, tickets, and remote reverts yourselves from the dashboards
24/7 lighting operations:
Real-time alarm and ticket monitoring — Alarms and tickets generated from the assets and metrics included in scope are monitored, triaged, and worked by Keedian agents in real time, in accordance with the agreed operating procedures and escalation paths AI
Reactive site requests — Sites can reach Keedian on any channel; our AI evaluates each request and opens a ticket when one is warranted — a fault, a setpoint-change request, or a question — feeding it into the same triage-and-resolve workflow AI + Human
Reactive CMMS intake — Tickets triggered by the customer's CMMS are ingested and routed into the same triage-and-resolve workflow, with our AI evaluating and enriching each one AI + Human
Remote resolution first — Every ticket gets a remote-resolution attempt by Keedian Ops before a truck roll is scheduled, with the avoided truck rolls counted toward the Managed-tier ROI report AI
Field dispatch when needed — Keedian Ops creates the work order, hands off to the customer's CMMS, and tracks resolution against SLA Human
Root cause analysis on close — Every closed ticket includes a documented root cause and the corrective action taken, feeding into recurring-failure detection AI
Recurring-failure detection — Sites or units with repeat tickets are flagged for replacement or vendor escalation, with the recurrence pattern surfaced in the monthly executive report AI
Operations + intelligence:
Everything in Managed, plus
Predictive ticket origination (roadmap — coming later) — AI and multi-variable FDD logic use the assets, metrics, baselines, and predictive signals included in scope to open and work tickets for emerging fault patterns before a conventional alarm or customer report AI
Additional Lighting FDD coverage — Analytics-driven fault detection on Schedule Compliance, Utilization, and Burn Hours is fully worked by Keedian Ops, aligned with the advanced and predictive lighting metrics dashboards in Platform Capabilities AI
Reporting
Portfolio lighting compliance report% of sites in compliance for each lighting optimization metric (Schedule Compliance, Utilization, Burn Hours) for the period, with monthly trend per metric
Site lighting reportPer-site schedule compliance, utilization by space, and burn hours with compliance flags, all with monthly trends
Lighting alarm and ticket volumeMonthly off-schedule, utilization-out-of-band, and lamp-life alarms, tickets generated, and alarm-to-ticket conversion across the fleet
Top alarm and ticket sourcesRanked list of sites and circuits generating the most lighting alarms and tickets
Everything in Essential
SLA & MTTR performanceSLA compliance against contracted targets per priority level, with Mean Time to Resolution by priority for fleet and per-site, and monthly compliance and resolution-time trends
Reactive ticket activityReactive lighting tickets received (site calls, CMMS, customer-initiated) categorized by type, with the reactive vs proactive cross-analysis including the % Keedian proactively initiated
Auto-revert and remote-resolution reportOff-schedule circuits returned to schedule automatically and tickets resolved remotely without a dispatch
Managed-tier ROI reportLighting energy recovered through schedule discipline plus avoided lamp-out dispatches, monetized
Off-schedule and lamp-out summaryBy site, by space: off-schedule circuits, utilization outliers, and lamp/ballast failures, with resolution time and root-cause distribution
Everything in Managed
Predictive alarm and ticket reportLighting faults caught proactively by predictive models (driver/ballast degradation, lamp end-of-life, control faults), with prediction accuracy and lead time before operational impact
Optimized-tier ROI reportManaged ROI plus lamp-life extension from burn-hour-based group relamp planning and the energy from tighter schedule discipline
Outlier deep divesQuarterly analysis of bottom-quartile sites with root-cause analysis and recommended interventions
Quarterly energy savings target with shared accountability
Pricing
Setup is one-time — integration per technology + commissioning per point. Subscription is recurring, per point. Preliminary, subject to review.
Model A · Direct
Consultative — scoped per project (Model A — direct sensors — applies only to buildings without a BMS)
Subscription: Price per point per month (minimum points per building apply)
Model B · Connect
No HW provision, no installation
Integration: Per technology (lighting control system) — one-time. Free when a reusable connector exists (open-protocol lighting control); quoted at SOW when proprietary systems need custom work.
Commissioning: Per point — one-time. Mapping and normalizing each point to the reporting model (flat standard rate; abnormally complex normalization quoted at SOW).
Subscription: Price per point per month (same as Model A)
Model C · Hybrid
Integration: Same as Model B — per technology, one-time (free or quoted by integration scope).
Commissioning: Per point — one-time, same as Model B; only on the points Keedian normalizes.
Subscription: Price per point per month (same as Model A)
Model A · Direct
Everything in Essential
Subscription: Price per point per month
Model B · Connect
Subscription: Price per point per month (same as Model A)
Model C · Hybrid
Subscription: Price per point per month (same as Model A)
Model A · Direct
Everything in Managed
Subscription: Price per point per month
Model B · Connect
Subscription: Price per point per month (same as Model A)
Model C · Hybrid
Subscription: Price per point per month (same as Model A)
02a Add-ons
Adjacent capabilities, on top of any tier.
Add-ons activate on top of any tier and any Data Enabler model. Each is either Domain-specific (within a product domain) or Transversal (across any contracted product). Open an add-on for its hardware, value levers, and pricing — or browse the full add-ons catalog.
Domain-specific
Adjacent capabilities within the product domain. Hardware and pricing live on each add-on's page.
Add-on
What it solves
Platform-wide
Transversal add-ons that apply across any product you contract, charged once per building.
Temperature and operating-status monitoring for office cafeteria, pantry, and vending refrigeration — alarms on warm cases and outages so food-safety risk is caught before stock is lost.
Monitoring of the electrical-continuity chain — UPS and standby generators, with the ATS and main switchboard as supporting signals — so a backup that is not ready surfaces before the outage it was meant to cover, not during it, and the site stays online: an office building's tenants and critical rooms, or a bank branch's ATMs, teller and core-banking systems, security, and comms. Monitors readiness ("will the backup take the load, and for how long?"), not just "broken now." Continuity links to the other monitoring add-ons for the layers they already cover — Chiller Plant Monitoring (critical-environment cooling), Fire Detection & Suppression Monitoring, and Vertical Transport Monitoring — which read alongside continuity but stay separate add-ons.
Monitoring of elevators and escalators — operating status, fault codes, and out-of-service events — so a stoppage is detected and routed to the maintenance provider the moment it happens.
Monitoring of fire detection and suppression systems — panel status, supervisory and trouble signals, and test/inspection records — so a supervisory fault or a missed inspection is caught and routed to the life-safety provider.
02b Advisory
An advisory layer, not a tier.
Tailored work for needs outside the standard packaging — scoped and priced per engagement, on top of any product and any tier. Keedian owns the connectivity and data layer; the physical asset stays with you and your vendors. Browse the full advisory catalog.
On-site work on the connectivity layer — sensor calibration, gateway and smart-thermostat installation, integration validation — plus coordination of your HVAC vendor for asset repairs.
Bespoke integrations with proprietary systems or clouds for which Keedian has no standard connector.
Transversal
All products
Pricing: project-based · scoped per engagement
02c How Agentic Operations works
A hybrid of AI agents and human operators, working as one service.
The Managed and Optimized tiers are delivered through Agentic Operations — AI agents and human operators working together against the same operational rules and the same SLA.
AI agents handle the routine, high-volume work. They monitor schedule compliance and zone utilization in real time across every building, triage common lighting events like a floor reading on outside its scheduled window, auto-revert off-schedule zones to their scheduled state where the BMS or controls allow, track cumulative burn hours to flag lamps approaching end of life, detect lamp, ballast, and driver degradation before a zone goes dark, identify outlier buildings across the portfolio, draft work orders with the suspected root cause, and verify closure with telemetry evidence. They work 24/7 against the schedules and occupancy rules you set.
Human operators handle the exceptions. When a control fault needs a conversation with the building engineer, when a schedule or dimming change needs customer approval before acting, when a relamp visit needs to be coordinated with your electrical contractor — that's the human side of the team. Operators also manage the customer relationship, refine the operating rules over time, and own the outcome and ESG reporting.
One service, one SLA, one accountability. The split between AI and human is invisible to you — you call Keedian, you read Keedian's reports, you measure Keedian against the contract. The internal mechanism evolves as the agentic stack matures; your contract does not change with it.
03 Data Enabler
We capture lighting signal wherever it lives: your BMS first, our control node where there's none.
The Data Enabler is how the operational signal enters Keedian. Offices are Model B dominant — almost every building already runs a BMS or networked lighting control,
so the default path is to connect to it: no Keedian lighting hardware, no installation. For older Class B / C buildings with no networked control, we install the control node.
Where a portfolio mixes the two, we cover the gap. The managed service, dashboards, SLA, and outcomes are identical across all three models.
Model A · Direct
Keedian Direct
When it applies
The fallback for older Class B / C buildings. There is no networked lighting control — or what is there produces no usable per-zone data. Floors and common areas run on manual switches, local time clocks, or standalone photocells.
What's included
Per building: a lighting control + metering node at the panel — a smart relay/contactor with per-zone current sensing (CT) and scheduling, covering the floor and common-area zones
One connectivity gateway per building (shared with HVAC or Energy if those products are also contracted)
In Optimized tier, per-zone submetering / power-quality sensing is added on zones that need equipment-health depth. Additional optional sensors available per building profile (occupancy per floor and common area for occupancy-driven dimming, daylight / photocell on perimeter zones, dedicated CT for burn-hour and rebate validation)
Installation included in the setup
Cost to you
Setup: Consultative — scoped per project (older buildings only; install designed for fast multi-building rollout)
Per zone: Scoped per project (control + metering node; submetering added in Optimized)
Standard recurring
Model B-Open · Connect
Open protocols
When it applies
The default for offices — most buildings already run a BMS or networked lighting control that exposes data over open protocols: BACnet, DALI, 0-10V, documented REST APIs. Honeywell, Schneider EcoStruxure, JCI Metasys, Siemens Desigo, Acuity nLight, Lutron Vive / Athena, Tridium.
What's included
Integration through Keedian's standard connectors (already built and reusable across customers on the same BMS)
No Keedian hardware (or minimal if specific floors or common areas are unmetered)
Integration cost absorbed by Keedian
Cost to you
No setup, no per-unit hardware
Recurring +$3/site/month vs. Model A
3-year minimum contract
Model B-Proprietary · Connect
Proprietary protocols
When it applies
Your BMS or lighting control is a legacy or closed system without modern APIs and needs a vendor gateway to reach: legacy Lutron Quantum, WattStopper / Hubbell, Encelium, closed building-controller variants.
What's included
Custom integration built by Keedian (initial vendor-gateway work, then reusable across customers with the same system)
No Keedian hardware (or minimal if specific zones are unmetered)
Integration cost absorbed by Keedian
Cost to you
No setup, no per-unit hardware
Recurring +$5/site/month vs. Model A
3-year minimum contract
Model C · Hybrid
Partial coverage
When it applies
You have partial coverage: networked control across most of the portfolio but a few older buildings on manual switches, recent acquisitions on a different system, or common areas on a separate system from the floor lighting.
What's included
A blend of Models B and A
Uses existing BMS / lighting-control data where it exists
Adds the Keedian control + metering node where coverage is missing
Cost to you
Scoped per building based on coverage
Setup and per-unit charges only on zones that need Keedian hardware
Intermediate recurring
Why Keedian can absorb the integration cost: integrations are reusable across customers running the same BMS or lighting control platform.
The first build is the investment; every subsequent customer on the same system runs at high margin. Because offices are BMS dominant — Honeywell, Schneider, JCI, Siemens recur across the market — the standard B-Open connectors cover the bulk of a portfolio, and B-Proprietary work stays selective and amortizes across customers on the same closed system.
System classification
Maintained by Product + Engineering. Lets Sales quote on the spot without engineering scoping.
Classification is pre-assigned per system; any system not on this list requires Engineering review before quoting.
Model A · Direct
No BMS classification needed
The building has no networked lighting control or BMS lighting integration
What is installed (manual switches, local time clocks, standalone photocells) produces no usable per-zone data
You prefer the Keedian control + metering node end-to-end on an older building
Model B-Open · +$3 / site / month
Open protocols
BACnet-enabled lighting control
DALI networks with documented gateway
0-10V dimming via documented controller
Acuity nLight (modern, API-enabled)
Lutron Vive / Athena (modern API)
Tridium / Niagara lighting modules
Model B-Proprietary · +$5 / site / month
Proprietary protocols
Legacy Lutron Quantum (older versions)
WattStopper / Hubbell legacy
Cloud-only platforms without documented API
Encelium (legacy versions)
Custom-built panel control stacks
Exception → Custom: If an integration takes more than ~300 hours of engineering, isn't reusable across customers,
or requires one-off development for a system without precedent, it falls outside Model B and is sold as Advisory work (section 02b).
05 Design notes
Why the structure is built this way.
Same template as HVAC
Lighting follows the exact same Essential / Managed / Optimized structure as the office HVAC and Energy products. This consistency makes the offering easy for Sales to explain and for facilities and ESG buyers to understand across products on the same portfolio.
Model B is the default for offices
Almost every office building already runs a BMS or networked lighting control — Honeywell, Schneider, JCI, Siemens. So the Data Enabler leads with Model B: we connect to the system you already operate, with no Keedian lighting hardware and no installation. Model A is the fallback for older Class B / C buildings with no networked control, and Model C covers a portfolio that mixes the two.
Per zone, not per circuit
Office lighting variable pricing is per lighting zone because zone count is what scales effort and value — a zone is a floor or a common area (lobby, cafeteria). A typical office building runs about 6 controllable zones; larger or multi-floor footprints run more. Pricing is pending, so the page shows the structure only.
Lighting is commandable, like HVAC
Lighting zones are controllable, not just observable — an off-schedule zone auto-reverts to its scheduled state where the BMS or controls allow, rather than waiting for a site visit. Essential includes Lighting Remote Command for exactly this reason: the revert is the primary remediation, not the dispatch.
Optimized is occupancy-driven dimming, not real-time optimization
The lighting Optimized tier has no real-time optimization agent and no IPMVP measurement-and-verification — those belong to HVAC and Energy. The lighting differentiator is occupancy-driven dimming and common-area scheduling on a hybrid-work baseline, plus the predictive-metrics dashboard and burn-hour-driven lamp-life planning. Occupancy here is a control INPUT to dimming, not a separate product.
Offices have no lighting anchor — every outcome is expected
There is no office lighting reference customer. Chedraui and 7-Eleven are the only real benchmarks and both are retail, so none of them anchor office lighting. Every outcome on this page is expected (pending validation) and framed conservatively. The page claims no benchmarked office lighting result.
Shared gateway across products
If a building contracts Lighting alongside HVAC or Energy under Model A, the connectivity gateway is shared (one per building). The setup fee is not duplicated — only added once.