T1UD-MISAerospace & Space
Constellation scheduling & downlink deconfliction
Allocate ground-station contact windows across a constellation without conflicts — geometric contact/visibility conflicts map to MIS.
Sector
Space operations
Likely buyer
Constellation operators; ground-segment providers
Named precedent
Adjacent to Thales satellite-MIS work
Hardware gate
Orion; scale → weighted (Vela)
Taxonomy
throughput-limited × accelerating
Live demo — adiabatic sweep on 5 contacts
Ω 9.4 · δ ±12.6 rad/µs · 4000 ns · R_b 9.1 µmGround-station contact windows conflict when they overlap; maximize non-conflicting downlinks.
GTM talk track
'The same tasking engine, pointed at your ground-station bottleneck.'
OGSM — product operating frame
Objective
Attach downlink deconfliction to the satellite tasking motion.
Goals
- One operator runs a contact-window schedule
Strategies
- Reuse the tasking MIS kernel
Measures
- Contacts scheduled
- Data-return throughput
OBR — outcome-based roadmap
| Horizon | Outcome we create | Buyer behavior change | Result we measure |
|---|---|---|---|
| Now | Operator schedules sample contacts | Prospect runs the emulated demo on their own instance data | Booked QPU-time evaluation or paid pilot |
| Next | Operator benchmarks a full constellation | Prospect co-designs a scoped benchmark against their incumbent solver | Documented crossover curve; expansion to production instances |
| Later | Operator standardizes ground-segment scheduling | Prospect standardizes on the workflow or buys an on-prem system | Recurring QPU consumption / system sale; reference case |
Fit notes (honesty gate)
Same tasking-MIS kernel; downlink contention instead of imaging.
Ready to run this on real hardware?
Emulation-verified today — the same program runs on a Pasqal QPU unchanged.