SMED: optimise changeover time
The main task of SMED is to convert internal changeover time (machine stopped) into external changeover time (done in parallel with the running process) – and then to minimise what remains using ECRS (Eliminate · Combine · Rearrange · Simplify). The coffee example from the video is built in 1:1 (32 s → 9 s → 8 s internal changeover time) and is fully editable.
At a glance
What matters is the internal changeover time – only it is machine downtime.
Record the changeover steps
All sub-steps with duration, classification (internal/external) and ECRS optimisation – freely editable.
The three stages
As in the video: everything internal → convert internal to external → minimise using ECRS.
ECRS analysis
Which step saves how much machine downtime – and through which ECRS lever?
Understanding SMED & ECRS (guided)
First the method in three steps, then the four ECRS levers – each with an example and best practice.
Video companion · Questions & answers
All the terms and calculations from the video – in plain language. Click a question to open the answer. Technical terms are underlined (hover over them).
Key terms explained +
SMED (Single-Minute Exchange of Die) is a method for optimising changeover time. Goal: the machine should be stopped for as short a time as possible. Here are the most important terms in plain language:
How saving works +
This HTML file is your document. Everything you enter is saved in this very file, just like a Word document. If you share the file, it includes all your analyses.
Save (green button or Ctrl+S) saves the current state without prompting. Until you create your own working file, the state is stored in the browser and is available the next time you open it.
Save as (under “Analyses”) creates a file on your drive. This is the only time you are asked where to save. After that, each Save writes silently to the same file.
The first time: Open the file, click “Analyses”, then Save as. From then on, just use the green button.
Autosave: Once an analysis has been saved, the tool automatically saves subsequent changes after a few seconds.
If something goes wrong: The tool continually stores a recovery copy in the browser. If the browser crashes or you accidentally close the window, your work is available the next time you open it.
Browser support: Chrome and Edge currently support writing directly to the file. In Firefox and Safari, everything stays saved in the browser, and the file itself remains unchanged.