The Millwright demo, explained. Read how it was built.

Machine Down. Floor keeps running.

Work reroutes on the next 200 ms tick.

Free browser MES simulator. All data simulated.

Millwright / shop floor
8 stations / 18 operations / 200 ms
Fault: station M5, MILL-03
Work moved to M2 MILL-02, M6 MILL-04, M8 MILL-05
A tower of an industrial plant with pipes, stairs and platforms, seen from the side.
Photo: Jakub Zerdzicki, Pexels

A stopped machine bills you by the minute. Only you know the rate.

What a failover saves depends on two numbers. Both are yours.

Put your own numbers in
50,000/hr
30 min
Replanning by hand
30 MIN 25,000 lost
Millwright auto-response
8 MIN 6,667 lost
Saved per incident, with the starting numbers (change them above)
18,333

Your figures: 50,000 lost per hour down, 30 min by hand. Millwright: 8 min (the next 200 ms tick, plus the demo's flat 5 min transport and 3 min setup), 22 min sooner. At 10 incidents a month: 2,200,000 a year.

Replanning by hand compared with Millwright
StepBy handMillwright
StartsSomeone noticesNext 200 ms tick
Who picks the machineA personThe one that finishes soonest
Time lostYour estimate (above)8 min: tick, transport, setup
Millwright production view during a machine failure: FAULT state on one machine, work rerouted to the rest of the floor
Failover / M5 fault, 3 jobs rerouted

Every machine, every queue, live.

8 Machines / 18 Operations / 200 MS Tick
Machine fleet: identifier, machine, type, and operations
ID Machine Type Operations Failover run
M1MILL-01CNC3 CNC operationsRunning
M2MILL-02CNC3 CNC operationsTakes over
M5MILL-03CNC3 CNC operationsFault
M6MILL-04CNC3 CNC operationsTakes over
M8MILL-05CNC3 CNC operationsTakes over
M3ASM-AAssembly7 assembly and welding, 2 sharedRunning
M7ASM-BAssembly7 assembly and welding, 2 sharedRunning
M4TEST-BTest6 test and calibration, 2 sharedAlert
Operations / all 18 types

Variator housing AL7075 / Controller housing IP67 / Brake caliper / Battery pack 48V / Shock absorber housing, welded / Main harness 16-pin / Inverter 5 kW / BLDC motor 2.5 kW / Support frame, TIG / Control board PCB / Full EOL protocol / Basic inspection / Sensor array calibration / Vibration analysis / Power load cycle / EMC compliance scan / Assembly kit packaging / QC rework

  1. Fault M5 A machine stops.
  2. Detect 200 ms Next tick. Also: a parameter out of range.
  3. Rank 3 levels Critical, then rush, then standard.
  4. Pick soonest Queue and measured speed decide.
  5. Move 5 + 3 min Transport, plus setup on a changeover.
  6. Run M2 M6 M8 Jobs start. No schedule by hand.
Millwright dashboard tracking 8 machines in real time
Floor view / 8 machines, live status

Three charts, one event log, CSV out.

3 Charts / 1 Event log / CSV export

Time-filtered reports on live charts.

Charts
3Floor load, throughput, utilization. Live.
Alert tags
4Technicians, supervisors, managers, QC. Labels only: nothing is sent.
CSV export
CSVFull event log. The demo keeps nothing: this file is the only copy.
Millwright analytics view with hall load, task volume, and machine utilization charts
Analytics / Load, throughput, utilization
Event log / simulated failover
Event log from one simulated failover: twelve entries, one per 200 ms tick
Time Machine Event Tagged for
14:22:07.400M5FAULT_DETECTEDTechnicians
14:22:07.600M5JOB_SUSPENDEDSupervisors
14:22:07.800SCHRESCHEDULE_STARTEDManagers
14:22:08.000M2JOB_ASSIGNEDSupervisors
14:22:08.200M6JOB_ASSIGNEDSupervisors
14:22:08.400M8JOB_ASSIGNEDSupervisors
14:22:08.600SCHRESCHEDULE_DONEManagers
14:22:08.800M2JOB_STARTEDSupervisors
14:22:09.000M6JOB_STARTEDSupervisors
14:22:09.200M4PARAM_OUT_OF_RANGEQC team
14:22:09.400M1JOB_COMPLETEDManagers
14:22:09.600M3QC_CHECK_PASSEDQC team

It reschedules the same whether one machine fails or three.

Failure simulation

Trigger a failure, watch its jobs move to the rest of the floor.

Fastest-finish scheduling

Re-plans the fastest finish for every job on every 200 ms tick, counting machine speed, transport and setup.

Runs local

Runs in your browser. Nothing goes to a server. Every operation lands in an event log with CSV export.

Questions before you open it.

How fast does Millwright react when a machine goes down?
Affected tasks reroute on the next 200 ms tick after a failure. No manager builds a new schedule by hand.
What machines and processes does it track?
5x CNC, 2x Assembly, and 1x Test station across 18 operation types, with live status and utilization data for every machine.
Do I have to change how my floor runs today?
Nothing changes. Millwright is a simulator that shows a rescheduling layer on top of a running floor: jobs flow as normal, and MCT-S steps in only when a machine fails or the schedule needs rebalancing.
How is the savings estimate calculated?
From your two numbers, in your currency: the cost of an hour of lost output, and the minutes to replan by hand. Millwright's side is the demo's own arithmetic: the next 200 ms tick, plus a flat 5 min transport and 3 min setup. Every number comes from you or from the demo's own settings.
Is our production data secure?
No real production data: everything on screen is simulated. The demo runs in your browser and sends nothing to a server. Its event log exports to CSV.
How large a floor does the demo run?
A fixed floor of 8 machines and 18 operation types. At that size the scheduler re-runs on every 200 ms tick.

The demo runs in your browser. Nothing to install.

Free / No signup / All data simulated