The shop floor is a scheduling problem with sparks coming off it.

Which job on which machine, in what order, so the whole line finishes soonest? Job-shop scheduling is NP-hard the moment it matters. Our time-indexed formulation solves a real instance with QAOA and draws the answer as a Gantt chart your planner would recognise.

Every idle minute on the line was decided by a schedule.
Every idle minute on the line was decided by a schedule.
The problem, in your words

What actually hurts.

Sequencing is the bottleneck

Machines wait on jobs and jobs wait on machines; the makespan hides in the ordering. Our demonstration found the exact weighted-shortest-processing-time optimum — at 19.5× the guessing rate, our strongest QAOA result.

Changeovers compound

Setup times turn a schedule into a routing problem in disguise. Both live naturally in the same time-indexed QUBO.

Shifts meet the same wall

Crewing the line has the same shape as sequencing it — coverage, quals, fairness — and reuses the same machinery.

How an engagement runs

Three steps. One written verdict.

01

Formulate

One cell, one week of orders — we encode jobs, machines, and precedence into a time-indexed QUBO, with your planner checking that the constraints are the real ones.

02

Run and measure

QAOA training with every evaluation a real circuit run; results rendered as Gantt charts next to the optimum your current scheduler produces.

03

Verdict in writing

Instance sizes that work, the projected crossover, and what to instrument now so your data is formulation-ready — pursue, park, or drop.

Proof, not projection

What we've already measured.

These programs are published in our algorithm library. The numbers below come from recorded executions we can reproduce on demand.

job-shop-qaoa

Time-indexed job-shop scheduling trained with QAOA.

Measured: Best feasible sample was the exact weighted-shortest-processing-time optimum, at 19.5× the guessing rate.

shift-scheduling

Crew rostering with coverage and fairness penalties.

Measured: Best sampled roster satisfied every hard constraint.

Results are from the library items' own recorded runs on our simulator — the same one your browser uses.

Where we draw the line

What we will not claim.

A production MES schedules thousands of operations; today's quantum instances are tens. The value now is the formulation and the team that knows how to write it — not a swap-in scheduler.

  • Constraint-programming solvers still rule production scale; our programs say so in their output.
  • The 19.5× concentration is real, measured, and reproducible in your browser.
Talk to us

Bring us one week of one cell.

Jobs, machines, precedence — anonymised is fine. An engineer replies with the formulation sketch.

typically replies within a day — an engineer, not a script
Logistics All solutions Energy & Utilities