Lighting that stays on schedule, vestibules that stay lit, energy that stops drifting across the network.

Bank branches offering: products anchored to each asset class.

Each product has its own Essential / Managed / Optimized structure, its own Data Enabler, and its own set of add-ons. This document covers Lighting Control & Optimization. HVAC Comfort & Optimization is the anchor product for the segment and Energy Intelligence follows the same model. Platform-wide add-ons and the Custom layer apply across every product.

Executive summary

Impact: Interior and exterior lighting held on schedule across every branch, ATM vestibules kept lit when they must be, occupancy-driven dimming on the customer floor, and lamp life planned from cumulative burn hours — with reductions in off-schedule run-hours already at Managed. Bank branches have no named Keedian lighting deployment yet, so every figure is expected (pending validation) and framed against the lighting load, not the total branch bill.

What it solves: Interior and exterior lighting left on outside branch hours, ATM vestibules that must stay lit for safety and security, lights-left-on and lamp-out tickets on branch and facilities staff, and lighting energy replicated across a large, uniform network — all of it landing on the ESG report.

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.

Three accumulative tiers.

Each tier adds capabilities on top of the previous one. You never lose functionality by upgrading, and you can start at any tier.

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.

Platform-wide

Transversal add-ons that apply across any product you contract, charged once per branch.

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.

Pricing: project-based · scoped per engagement

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 alarms in real time across the network, triage common lighting false positives like a scheduled dark zone read as a fault, detect off-schedule zones and driver / ballast faults, revert off-schedule interior and exterior zones to their scheduled state, generate occupancy-driven dimming and schedule recommendations, identify outlier branches, draft work orders with the suspected root cause, and verify closure with telemetry evidence. They work 24/7 against the schedules and ATM-vestibule availability rules you set.

Human operators handle the exceptions. When a lamp-out or dark-vestibule ticket requires conversation with the branch manager, when a schedule change needs customer approval before acting, when an electrical-contractor escalation needs a human voice on the phone — that's the human side of the team. Operators also manage the customer relationship, refine the operating rules over time, and own the outcome 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.

We capture lighting signal wherever it lives: your lighting control, our node, or both.

The Data Enabler is how the operational signal enters Keedian. Bank branches are different from a single small-retail store: corporate real estate standardizes controls across the whole network, so the default path is Model B — we connect to the BMS / networked lighting control you already run and read its per-zone points. We don't charge you to integrate it; we use the investment the network already made. Where a branch has no networked control — typically older or recently acquired branches on manual switches and time clocks, or a standalone ATM vestibule — Model A installs the Keedian lighting control + metering node. Where coverage is partial, Model C fills the gaps. The managed service, dashboards, SLA, and outcomes are identical across all three models.

Why the structure is built this way.

About this document.