Manufacturing and production
Production scheduling: the classical solver proves the answer
Job-shop scheduling is the canonical factory problem. Each job visits machines in its own order, each machine handles one job at a time, and the goal is the shortest makespan. It is NP-hard, it is genuinely difficult, and it is one of the applications most often named as a quantum computing target.
The encoding, first
As on the logistics page, the quantum benchmark does not exist here, and the reason is the result. Putting job-shop scheduling on a quantum computer requires a time-indexed QUBO: a binary variable for every combination of job, machine and discrete time slot. The variable count is the product of all three, and it grows brutally.
A 15 by 15 shop needs 268,425 binary variables, so 268,425 logical qubits before error correction. The largest processor we can run is 108 physical qubits, the largest built anywhere is around 1,600, and the most logical qubits anyone has demonstrated is 96. The published 2029 roadmaps target hundreds of logical qubits. Every one of those numbers is three orders of magnitude short of this single instance.
What the classical solver does with the same instances
| Shop | Qubits needed | Makespan | CP-SAT time | Result |
|---|---|---|---|---|
| 3 x 3 | 531 | 28 | 0.01 s | proven optimal |
| 5 x 5 | 3,675 | 47 | 0.01 s | proven optimal |
| 10 x 10 | 57,000 | 94 | 0.17 s | proven optimal |
| 15 x 15 | 268,425 | 126 | 2.45 s | proven optimal |
OR-Tools CP-SAT, seed 20260902, measured 2 September 2026 on an ordinary laptop CPU. The makespans are proven optimal and therefore reproduce exactly; solve times vary with machine load, and the accompanying notebook took 5.6 s on the 15 by 15 shop against the 2.45 s shown here.
The word doing the work is "proven"
CP-SAT did not find a good schedule for the 15 by 15 shop. It found the best possible schedule and proved that nothing shorter exists, in 2.45 seconds.
That distinction matters more in a factory than in most places. A plant manager asking whether the line can run faster is asking a question with a definite answer, and a heuristic that returns a good schedule without a bound cannot give it. Every quantum approach to this problem is a heuristic. QAOA returns a sample, not a proof, so even at unlimited scale it would answer a weaker question than the classical solver already answers in seconds.
Where quantum could still matter here
Two honest caveats, because the picture above is not the whole industry.
Real shops are larger and messier. Hundreds of jobs, sequence-dependent setup times, maintenance windows, shift patterns and stochastic durations. CP-SAT does not always prove optimality there, and past a certain size it returns a good schedule with a gap rather than a guarantee. That is the regime where a better heuristic has value.
But the encoding gets worse, not better, in that regime. A larger, more constrained problem needs more time slots and more variables, so the qubit requirement rises faster than the classical difficulty does. Quantum approaches become relatively less applicable exactly as the problem becomes commercially interesting, which is the opposite of the usual pitch.
The question to ask a vendor
If a supplier proposes quantum scheduling, ask what makespan they achieve on a 15 by 15 shop and how long it takes. Then compare it against 126 in 2.45 seconds, proven optimal, on a laptop. The comparison is not unfair. It is the alternative you already have.
Ask the same question at whatever size your plant actually runs. If CP-SAT proves optimality there, no heuristic of any kind, quantum or classical, has anything to offer.
For context: where the hardware actually is
Gaps on this page are quoted against the devices ZKSF can run, which are Amazon Braket’s public processors. That is not the frontier. Quantinuum, IBM, QuEra and Atom Computing are not resellable through us, and their machines are considerably further along. As of September 2026:
Physical qubits built
| Infleqtion Sqale | 1,600 | Neutral atom |
| Atom Computing | 1,180 | Neutral atom, 1,225 sites |
| IBM Condor | 1,121 | Superconducting, 2023 |
| IBM Heron R2 | 156 | Superconducting, ~99.5% two-qubit fidelity |
| Rigetti Cepheus | 108 | The largest available through ZKSF |
Two-qubit gate fidelity
The number that actually governs what a circuit can do.
| IonQ | 99.99% | Trapped ion, first past four nines |
| Silicon Quantum Computing | 99.99% | Silicon spin |
| Quantinuum | 99.97% | Trapped ion, all-to-all |
| IQM | 99.91% | Superconducting, available through ZKSF |
Logical qubits demonstrated
Published results, not roadmap targets.
| QuEra | 96 logical / 448 physical | Neutral atom |
| Quantinuum | 48 logical / 98 physical | Trapped ion, iceberg code |
| Atom Computing | 24 logical | On the 1,180-qubit system |
| 1 logical / 105 physical | Surface code, below threshold |
Announced roadmap
Targets. Roadmaps slip, and these are not results.
| Quantinuum Sol, 2027 | 192 physical, ~100 logical | Iceberg code, distance 2. Error detection with postselection, not correction |
| IBM Starling, 2029 | ~200 logical | Bivariate bicycle qLDPC, 100 million gates |
| Quantinuum Apollo, 2029 | hundreds of logical | Thousands of physical, logical error 1e-6 or better |
Where the encoding does work.
Not every operations problem encodes this badly. Satellite tasking needs one qubit per decision rather than one per job, machine and time slot, and there we have a real head-to-head result.