01 · DECISION WORKFLOW

Replan the future. Keep the work already done.

A machine outage becomes a proposed schedule, a fair comparison and an explicit operator decision. The solver and simulation carry the numbers; the workflow carries the state.

Open the recorded replayRead the evidence
  1. Observesnapshot + outage
  2. Compareoriginal / candidate
  3. Confirmexplicit choice
  4. Continuenew snapshot
2/4 → 4/4First-outage comparison · synthetic units completed
2 eventsConfirmed transitions in the recorded exercise
0 model callsHiGHS and SimPy compute this example

The problem

At hour 2, a machine fails while a job is partly fabricated. Replacing the entire schedule would erase completed work and move an operation that has already started. A useful planner must preserve both commitments before improving the remaining horizon.

Implementation decisions

01

One state, two futures

SimPy resumes the original schedule and the HiGHS candidate from the same snapshot. Completed operations stay frozen; work in progress keeps its machine and remaining duration.

02

A proposal is not a dispatch

Compare completion, unfinished units, overtime and the timeline before confirming. Advancing consumes the selected proposal, then a second outage starts a new comparison from the resulting state.

03

Failure keeps an explainable path

The solver runs in an isolated process. A failed or timed-out solve publishes no proposal and does not advance execution. Infeasible or worse candidates keep the original recommendation; stale confirmations cannot apply a proposal to a different snapshot.

Inspect it yourself

The public page replays a recorded, authored scenario. To edit an outage and run the actual solver, start the local demo after installing the repository requirements:

python -m mpa.demo --port 8840
  1. Compare the default M1 outage from hour 2 to 6.
  2. Inspect the frozen prefix and remaining work; confirm a choice and advance to hour 3.5.
  3. Compare the second M2 outage, advance again and download the transition trace.

Open the recorded replay →

Scope and limits

This is a four-unit synthetic exercise on a bounded time grid. It establishes the state transition and comparison contract, not factory throughput gains or LLM planning quality. There is no connection to shop-floor equipment.

Sources and verification

Source and CI links let you inspect the implementation and reproducibility. Passing checks do not establish deployment success or business gains.