Off-peak
Hours 20–11, the charge window
The edge controller running one full day at a building on a time-of-use price. It charges the battery when power is cheap and discharges at the peak, holding site import under the meter's demand cap. This is a simulator run. Nothing here has touched a real building, and every command below cleared the safety kernel.
Off-peak
Hours 20–11, the charge window
Peak
Hours 12–19, 4.7× off-peak
Peak discharge
Battery, eight hours out
Cap held
Import pinned to the cap (D6)
Commands
All safety-gated
Power in kW. Bars are the battery: below the line it charges, above it discharges.
The same day through meter.main.kw. The loop pins import to the cap while charging, then drops it to the floor at the peak.
Import held to
Charging takes every kW of headroom under the cap and never crosses it. That's D6.
Peak-hour import
Discharge plus HVAC shed cut it 81% at the $0.42 peak.
Correlation
Every clamp and discharge above shows up here as a bounded import curve.
Cloud sets intent, the edge disposes. The controller binds a twin of the building and its DER nodes, reads each one, and actuates only what the kernel clears.
The meter is the demand-cap input. No live meter, no charge (D6).
Straight from edge.optimizer forecast. ←req is the kernel trimming a request to what the cap allows.
| hr | load | pv | net | meter | $/kWh | dispatch |
|---|
What a good operator does, run every cycle without one.
Overnight at $0.09 the battery charges and the EV pulls 11 kW. Cheapest power of the day.
A 50 kW charge trims to headroom (→14, →10) so metered import holds at the 51 kW cap.
Hours 12–19 at $0.42: battery out 50 kW, HVAC sheds 20 kW, the peak drops.
A dr_shed signal lands at 17–18h, fleet already leaning out.
2 of 52 commands relinquished to the building rather than hold stale intent. The dead-man default.
The optimizer proposes, the kernel disposes. Nothing actuates it hasn't cleared.
Backed by NVIDIA Inception. The loop works in simulation. Next is real hardware, real buildings, a live twin.
Run forecast and dispatch on DGX-class hardware in the building, not a cloud VM.
Today: simulator, cloudTie the controller to the robotic-payload capture so the twin is the building.
Today: registry + adaptersScale from one controller to a portfolio under one tenant-scoped gateway.
Today: one building