Fleet Programs

Aggregators and VPP operators need one integration surface to enroll devices, ingest telemetry, and dispatch across manufacturers without maintaining N OEM connectors.

Book a Demo

Fleet Control

One integration surface, from first connection to verified outcome.

Step 1: Enroll devices

Link an OEM account and kWh discovers every eligible device, assigns a canonical ID, and records what each one can do.

iOne connector for every OEM, not one per manufacturer.
Enroll devices
OEM cloudOAuth linked
BESS · Inverter · EV charger
Devices discovered1,284
Batteries 812EVSE 341Tstats 131
canonical device_idcapability: control

Step 2: See the whole fleet

Telemetry from every OEM lands in one schema, so a mixed fleet reads like a single system in real time.

iOne canonical data model across the entire fleet.
Fleet telemetry
Fleet state of charge63%
Online
1,271 / 1,284
Dispatchable
4.9 MW
Live telemetryupdated 2s ago

Step 3: Dispatch in canonical form

Send one command against a canonical device. kWh converts it into each manufacturer's format and tracks execution state.

ikWh translates one command into each OEM's native API.
Dispatch
POST /devices/dev_8f2c1a/commands
{
  "command_type": "set_charge_mode",
  "parameters": { "mode": "backup_reserve" }
}
Battery APIacknowledged
Inverter APIacknowledged
EVSE APIpending

Step 4: Verify and settle

Every dispatch is measured against target and logged, so program performance and settlement are provable.

iLogged response for settlements and program M&V.
Event performance
Event · Peak shave Verified
4.62 MWdelivered vs 4.5 target
Devices responded1,240
Settlement$18,420
Enroll devices
OEM cloudOAuth linked
BESS · Inverter · EV charger
Devices discovered1,284
Batteries 812EVSE 341Tstats 131
canonical device_idcapability: control
Fleet telemetry
Fleet state of charge63%
Online
1,271 / 1,284
Dispatchable
4.9 MW
Live telemetryupdated 2s ago
Dispatch
POST /devices/dev_8f2c1a/commands
{
  "command_type": "set_charge_mode",
  "parameters": { "mode": "backup_reserve" }
}
Battery APIacknowledged
Inverter APIacknowledged
EVSE APIpending
Event performance
Event · Peak shave Verified
4.62 MWdelivered vs 4.5 target
Devices responded1,240
Settlement$18,420

Why Teams Choose kWh

One API

Connect batteries, thermostats, EV chargers, and more through a canonical data model.

Faster Enrollment

OAuth-based device linking and normalized enrollment state across OEMs.

Dispatch

Issue control commands in canonical form; kWh translates to OEM-specific calls.

Verify

Logged response data for program performance and settlements.

OEM Platform

Cloud APIs for multi-OEM connectivity and normalization.

Explore OEM Platform →

Talk to the kWh team

Request a demo tailored to your use case and buyer segment.

Book a Demo