T1–T2UD-MISEnergy & Utilities
Smart-charging load deconfliction
Schedule EV charging to avoid simultaneous local-transformer overload — temporal-geometric conflict graph.
Sector
Energy / grid edge
Likely buyer
DSOs; charge-point operators
Named precedent
EDF smart-charging work
Hardware gate
Orion; weighting → Vela
Taxonomy
throughput-limited × accelerating
Live demo — adiabatic sweep on 5 charges
Ω 9.4 · δ ±12.6 rad/µs · 4000 ns · R_b 9.1 µmCharging sessions on the same transformer conflict; find the largest simultaneously-safe set.
GTM talk track
'Same EDF relationship, pointed at transformer overload at the grid edge.'
OGSM — product operating frame
Objective
Extend the EDF energy motion into charge scheduling.
Goals
- One DSO runs a neighborhood scenario
Strategies
- Map transformer-locality conflicts to geometry
Measures
- Peak load avoided
- Charges served
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | DSO sees deconflicted charging on a feeder | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | DSO benchmarks a substation area | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | DSO integrates into DERMS | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
EDF-adjacent; conflicts are transformer-locality + time overlap.
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.