T1UD-MISEnergy & Utilities
Offshore wind farm micro-siting
Place turbines to maximize output while avoiding wake interference — wake exclusion is a distance/direction conflict.
Sector
Renewables
Likely buyer
Wind developers; energy majors
Hardware gate
Orion; weighting → Vela
Taxonomy
throughput-limited × accelerating
Live demo — adiabatic sweep on 5 turbines
Ω 9.4 · δ ±12.6 rad/µs · 4000 ns · R_b 9.1 µmTurbines within a wake radius interfere; maximize the non-interfering set.
GTM talk track
'Turbine wakes are exclusion zones. Maximize energy capture by packing the most non-interfering turbines.'
OGSM — product operating frame
Objective
Demonstrate wake-aware turbine packing.
Goals
- One developer runs a lease-area layout
Strategies
- Map wake exclusion to blockade geometry
Measures
- Energy capture
- Turbines sited per area
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | Developer sees a layout on a lease area | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | Developer benchmarks against their siting tool | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | Developer adopts for project design | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
Wake exclusion = geometric conflict; expanded-domain native fit.
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.