MBW

Simulation

A working model of your operation, not a spreadsheet of it.

Building blocks ready to use, put together by the people who know the process, and then run as a real week, hour by hour.

Build your line on a canvas or as a file, start from a worked example, and run it until you see the range of weeks, not one lucky one.

A line placed, checked and run
01

A spreadsheet averages. Your floor does not.

A spreadsheet gives every hour the same load. A simulation runs like your floor: it shows the queue a breakdown leaves, and what it cost.

In the spreadsheet

Press

average load, every hour

Queue in front of the press

06:0008:0010:0012:0014:00

Every hour gets the average, so the morning looks calm.

In the model

Press

runningdown from 09:40

Queue in front of the press

06:0008:0010:0012:0014:00

The breakdown, and the queue it leaves behind for the next two hours.

An illustration of the idea, not a measurement: no axis here carries a figure.
02

Two views, one model

No programming: whoever knows the line builds the model, on a canvas or as a file. Both are one model, saved as an ordinary folder of files.

Change the drawing or the file and the other follows; every version is kept
03

Building blocks that already know how things behave

Each block already knows how its kind of thing behaves. You describe your plant instead of programming it: drag in, connect, fill in.

Shifts, breakdowns and changeovers, for engineers
Blocks that know their behaviour, joined into a line, one machine described in detail
04

Products that are more than a label

Variants inherit their product's data and set only what differs. Results come per product and variant, not as one average.

Variants inherit everything and set only what differs; results come out per variant
05

A model that tells you when you are wrong

A misspelt setting is refused with the word it probably meant, and an unpriced machine's cost reads unknown, never zero.

A typo is refused with the word it probably meant; a missing price is unknown, not zero
06

22 worked examples to start from

Each worked example asks one question and brings the runs that answer it. Open the closest: you work on a copy, the original stays.

A worked example picked by its question, copied into your project, made your own

Bring us your line.

The fastest way to know whether this models your operation properly is to describe it to us for 45 minutes and find out.

Book a discovery call(opens in a new tab)