Energy seen branch by branch, costs that stop surprising you, waste that surfaces before the bill.
Energy Intelligence for bank-branch networks: three accumulative tiers (Essential / Managed / Optimized),
a Data Enabler that leads with connecting to the BMS / EMS metering your network already runs, product-specific add-ons,
platform-wide add-ons, and a Custom advisory layer. Built for retail banking where energy spend has no visibility branch
by branch, demand charges go unmanaged, and electrical problems only surface as a failure or a higher bill — replicated
across a large, uniform estate.
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 Energy Intelligence. HVAC Comfort & Optimization is the anchor product for the
segment and Lighting Control & Optimization follows the same model. Platform-wide add-ons and the Custom layer apply across every product.
HVAC · Draft
HVAC Comfort & Optimization
Asset class: RTUs / packaged & split units serving the branch — teller floor, back-of-house, and ATM vestibule.
Pain points: Customer and staff comfort, HVAC energy spend across the network, equipment life, comfort complaints.
Lighting · Draft
Lighting Control & Optimization
Asset class: Interior, exterior / signage, and ATM-vestibule lighting.
Pain points: Lighting energy spend, scheduling, 24/7 ATM-vestibule availability.
Pain points: Network-wide visibility and energy savings across a large, uniform network.
01 Energy Intelligence
Executive summary
Impact: Every branch's consumption, demand, and cost in one place; anomalies worked before they hit the invoice; demand and tariff actively managed with M&V; and the meter doubling as an early-warning system for failing equipment — 3–7% energy savings expected at the Optimized tier. Bank branches have no named Keedian energy deployment yet, so every figure is expected (pending validation) and framed conservatively — below HVAC, because the RTUs are the larger controllable load.
What it solves: Energy spend with no visibility branch by branch, demand charges nobody is managing, and electrical problems that only surface as a failure or a higher bill — replicated across a large, uniform network.
Main value drivers
Energy savingsSustainability
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 what every branch consumes, what it costs, and where energy is wasted — straight from the bill, whether that is the branch utility account, a landlord / common-area charge, or a PPA settlement."
"Keedian watches my energy alarms and works the anomalies — abnormal consumption, demand spikes, and circuits heading for trouble — across the network, so I do not have to."
"Keedian manages my demand and tariff exposure across the network, benchmarks every branch against the estate, and captures verified savings with M&V — and the meter doubles as an early-warning system for failing equipment."
Expected outcome
Bank branches have no validated Keedian benchmark — the named anchors (Chedraui, 7-Eleven) are retail, so every branch energy figure below is expected (pending validation). Energy savings at the meter level are intentionally conservative — below HVAC management — because the RTUs are the larger controllable load in a branch. Figures are savings on branch energy use, not the total operating bill.
Energy savings: Foundation — visibility (expected, pending validation)
Sustainability: Baseline established (expected, pending validation)
Energy savings: 2–4% (expected, pending validation)
Sustainability: Anomalies worked before they hit the invoice (expected, pending validation)
Energy savings: 3–7% (expected, pending validation)
Sustainability: Verified CO2e reduction across the network (expected, pending validation)
Data Enabler
Pick the model that matches what you already have
Model A — Keedian Direct
A revenue-grade energy meter at the branch main service, with current transformers (CTs) sized to the branch switchgear
One branch gateway streaming 15-minute interval data (kW, kWh) to the platform (shared with HVAC or Lighting if those products are also contracted)
You keep the model you chose (A, B, or C). The managed service is delivered the same way regardless of model.
Managed's Data Enabler, plus:
Sub-metering (CT clamps) on the big branch loads — HVAC RTUs, the ATM vestibule, signage — for consumption-by-load attribution and equipment-level health
Power-quality-capable metering (current, power factor, voltage) where the base meter does not expose it
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
Bill and cost captureCapture actual consumption and cost from the bill, whatever its source: the building invoice, the common-area charge, the utility statement, or a PPA
Conversational AI AssistantNatural-language questions on your data plus automated anomaly detection across the 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
Everything in Managed
Per-floor and per-tenant attribution with Measurement & VerificationBreak the building's consumption and cost down by floor and tenant, and verify savings against a baseline
Submetering and consumption-by-domain attributionBreak the bill into HVAC, lighting, refrigeration, and plug loads, and see each circuit on its own
Advanced and power-quality metricsCurrent, power factor, voltage, and abnormal-draw signals that turn the meter into an equipment-health tool
Demand and tariff analyticsPeak-shaving recommendations and time-of-use window analysis against your utility's rate model
IPMVP-compliant Measurement & VerificationRealized savings vs a contracted baseline, exportable for executive and ESG reporting
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 read the dashboards, capture the bill, and act on what you see.
24/7 energy 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 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
Energy remote resolution first — Every energy alarm — a demand-peak breach, an off-hours spike, a sustained over- or under-voltage, a circuit nearing its protection limit, or a site call about an outage — gets a remote diagnosis first: Keedian Ops works the meter data to pinpoint the cause, then guides the site to the fix or coordinates with the utility. The meter sees but does not command, so a truck roll is scheduled only when the fix is physical AI + Human
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
Cross-product demand and tariff optimization — The energy meter is read-only — so at Optimized, where the customer also runs Keedian on HVAC, Lighting, or Refrigeration, Keedian Ops turns the meter's demand and tariff insight into load actions through THOSE products: pre-cool-and-coast, staggered start-ups, and shifting flexible load into off-peak windows to cut demand charges and time-of-use cost AI + Human
Savings capture and verification — Keedian continuously identifies energy savings opportunities and tracks each measure from recommendation through to realized, verified savings against the baseline and the next billing cycle — utility-incentive and demand-response program enrollment is delivered as a dedicated add-on AI + Human
Extended energy FDD coverage — Analytics-driven fault detection on the submetered and power-quality signals — short-cycling, off-cycle draw, and voltage events — is fully worked by Keedian Ops, aligned with the advanced metrics in Platform Capabilities AI
Reporting
Portfolio energy reportConsumption, peak demand, and spend across the fleet for the period, with normalized benchmarks (per site, per square foot) and month-over-month trend per metric
Site energy reportPer-site consumption, peak demand, off-hours floor, and cost, each with a benchmark band and monthly trend, plus the site's evolution and the windows where savings are available
Meter-vs-bill reconciliationMetered consumption contrasted against the utility invoice, with any divergence (CT ratio, multiplier, or billing error) flagged for recovery
Energy alarm volume and top sourcesAnomalies raised across the fleet (off-hours waste, demand-peak approaches, consumption step-changes), ranked by the sites and circuits generating the most; where submetering is present, consumption is split by domain (HVAC, lighting, refrigeration, plug loads)
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 energy tickets received (site calls, CMMS, customer-initiated) categorized by type, with the cross-analysis of reactive vs proactive tickets including the % Keedian proactively initiated
Avoided truck rolls reportEnergy alarms diagnosed and resolved remotely without dispatch, with estimated cost savings
Managed-tier ROI reportEnergy spend recovered (off-hours waste corrected, anomalies and billing errors resolved) plus avoided truck rolls, monetized
Energy anomaly summaryBy site, by month: off-hours waste, demand-peak approaches, consumption step-changes, and power-quality events, with resolution time and root-cause distribution
Everything in Managed
Predictive alarm and ticket reportPower-quality and submeter faults caught proactively (short-cycling, voltage events), with prediction accuracy and lead time before operational impact
Optimized-tier ROI reportManaged ROI plus Demand and Tariff savings (executed through the customer's connected products) and Equipment Lifetime Extension from the meter's early-warning signals, adjusted by the site's utility billing model
IPMVP M&V quarterly reportFormal Measurement & Verification per IPMVP protocol vs the contracted baseline, backed by submetering where deployed; exportable for executive and ESG reporting
Outlier deep divesQuarterly analysis of bottom-quartile sites with root-cause analysis and recommended interventions
Monthly anomaly review SLA (delivered within 5 business days of month-end)
Quarterly review delivered within 10 business days of quarter-end
SLA from Managed
Quarterly captured savings target with shared accountability
Annual ESG report ready for board presentation
Pricing
Setup is one-time — hardware and installation (Model A) or integration (Model B). Subscription is recurring, per branch. Preliminary, subject to review.
Model A · Direct
Price per branch (Model A — Keedian revenue-grade meter — applies only to branches without a readable BMS / EMS meter)
Subscription: Price per branch per month (one meter per branch (sub-metering scoped per engagement))
Model B · Connect
No HW provision, no installation
Integration: Free or paid — depends on integration scope (open-protocol BMS / EMS metering is typically free via a reusable connector; vendor-locked metering is quoted at SOW)
Subscription: Price per branch per month (same as Model A)
Model C · Hybrid
Integration: Same as Model B — free or paid based on integration scope
Subscription: Price per branch per month (same as Model A)
Model A · Direct
Everything in Essential
Subscription: Price per branch per month
Model B · Connect
Subscription: Price per branch per month (same as Model A)
Model C · Hybrid
Subscription: Price per branch per month (same as Model A)
Model A · Direct
Everything in Managed
Subscription: Price per branch per month
Model B · Connect
Subscription: Price per branch per month (same as Model A)
Model C · Hybrid
Subscription: Price per branch 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.
Standard connectors — Green Button, EnergyStar Portfolio Manager, and major utility APIs — pull interval consumption and cost straight from the utility, with no on-site hardware. Normalizes each utility's billing format and reconciles the pulled data against meter telemetry.
Automated audit of utility bills against tariff schedules and meter data. Identifies billing errors, incorrect rate classes, and overcharges. Manages refund recovery.
Enrolls eligible sites and controllable loads in utility demand response programs at the portfolio level. Manages event response, post-event verification, and incentive collection. HVAC and other climate equipment are the primary curtailment lever.
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.
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 energy alarms in real time across the network, triage anomalies against expected consumption and demand, run fault detection on the meter signal (abnormal consumption, demand spikes, baseload drift, circuits heading for trouble), benchmark every branch against the estate, identify outlier branches, draft work orders with the suspected root cause, and verify closure with telemetry evidence. Because the meter diagnoses but does not command, the output is always a guided recommendation, never a remote control action. They work 24/7 against the thresholds you set.
Human operators handle the exceptions. When an anomaly needs a conversation with the branch manager, when a tariff or demand action needs customer approval before acting through another connected product, when a utility or vendor 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.
03 Data Enabler
We capture energy signal wherever it lives: your BMS meters, our meter, 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 metering across the whole network, so the default path is Model B — we connect to the BMS / EMS meters you already run and read their interval data. We don't charge you to integrate it; we use the investment the network already made. Where a branch has no usable metering — typically older or recently acquired branches with no remote read — Model A installs a revenue-grade meter. Where coverage is partial, Model C fills the gaps. The managed service, dashboards, SLA, and outcomes are identical across all three models.
Model B-Open · Connect
Open protocols · the branch-network default
When it applies
The common case for bank branches — the network already runs a BMS / EMS with metering that speaks an open protocol (BACnet, Modbus).
What's included
Integration with your existing BMS / EMS meters
No new on-site hardware where the branch already meters
Cost to you
No setup, no per-unit hardware
Recurring +$3/branch/month vs. Model A
3-year minimum contract
Model B-Proprietary · Connect
Proprietary protocols
When it applies
You have a BMS, but the metering is locked to a vendor cloud (Honeywell, Schneider, JCI, Siemens).
What's included
Vendor-gateway / API integration, scoped per system
Reads your existing BMS submeters into the platform
Cost to you
No setup, no per-unit hardware
Recurring +$5/branch/month vs. Model A
3-year minimum contract
Model A · Direct
Keedian Direct
When it applies
Older or recently acquired branches with no usable metering, or a meter that cannot be read remotely. The exception, not the rule, for a standardized branch network.
What's included
Branch main-service energy meter + CTs
Branch gateway, 15-minute interval data (shared with HVAC or Lighting if contracted)
Cost to you
Setup: Price per branch (install designed for fast multi-branch rollout)
Per meter: Price per meter (revenue-grade meter + CTs; Optimized adds sub-metering on the big branch loads)
Standard recurring
Model C · Hybrid
Partial coverage
When it applies
Some branches are already metered through the BMS and others (older or acquired) are not.
What's included
Keedian metering where the BMS has none, integration where it does
One combined data layer across new and existing meters
Cost to you
Scoped per branch based on coverage
Setup and per-unit charges only on the RTUs that need Keedian hardware
Intermediate recurring
Why Keedian can absorb the integration cost: integrations are reusable across customers running the same BMS platform.
The first build is the investment; every subsequent branch on the same network-standard system (Honeywell, Schneider, JCI, Siemens) runs at high margin. Because bank branches are BMS-dominant, the standard B-Open path covers the bulk of cases, and the connectors are already built.
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
No metering installed, or no remote read (older / acquired branches)
Existing meter data is incomplete or unreliable
You prefer Keedian to own the metering layer
Model B-Open · +$3 / branch / month
Open protocols
Existing revenue or sub-meters with an open protocol (Modbus, BACnet, pulse output)
Panel-level metering already installed on site
Energy management systems with documented APIs
Model B-Proprietary · +$5 / branch / month
Proprietary protocols
Closed or legacy EMS without an open API (e.g. Schneider Power Monitoring Expert legacy)
Proprietary submetering systems requiring vendor integration
Meters reachable only through a vendor cloud or gateway
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.
Asset class is the energy meter
Energy Intelligence is anchored to the branch's electrical metering, not one equipment type — the meter sees the whole branch, across the RTUs, the ATM vestibule, signage, and lighting load.
Priced per branch, not per point
A bank branch is metered whole-branch — one revenue-grade meter per site — so Energy Intelligence is priced per branch (the retail per-site model), the same choice branch HVAC and Lighting make. This is the deliberate difference from offices/energy.yml, which prices per BMS-equivalent point because an office building has many metered points.
Essential is bill-led, source-agnostic
Essential captures actual consumption and cost straight from the bill. The source does not matter — the branch utility account, a landlord / common-area charge, or a PPA settlement are all just "the bill". No physical metering is required to start.
Model B is the dominant path
Corporate real estate standardizes a BMS / EMS across the branch network (Honeywell, Schneider, JCI, Siemens) that already meters each branch, so the Data Enabler leads with Model B — connect to what is there. Model A metering is reserved for older or acquired branches with no usable read.
Demand, tariff, and cross-branch benchmarking are the Optimized differentiator
Essential runs on the bill and the data the branch already has; demand / tariff management, cross-branch benchmarking, and M&V (Optimized) are what turn the meter into a savings-verification tool across a large, uniform estate.
Savings stay below HVAC
In a branch the biggest controllable load is the HVAC RTUs, so Energy Intelligence savings claims are intentionally conservative versus HVAC management.
The meter diagnoses, it does not command
Because the meter sees but does not command, the Managed tier excludes reactive site requests (issue #230): remote resolution is energy-specific — diagnose and guide, never a remote command — and Optimized demand and tariff actions run through the branch's other connected products (HVAC, Lighting). Value drivers are energy and sustainability only (issue #229).
Utility / PPA integration is an add-on, not the enabler
Connecting to a utility API, Green Button, or a PPA portal is a software data integration (like CMMS integration) — offered as the Utility Data Integration add-on, separate from the physical Data Enabler that meters the branch.