No items found.
It's 2 a.m. and the changeover that was supposed to take 45 minutes is pushing two hours. The next run is waiting, the schedule is slipping, and the overtime is already stacking up. Sound familiar?
If changeovers are eating your uptime, start by getting straight on what you're measuring. Changeover time is the elapsed time from the last good part of one production run to the first good part of the next. That's the real wall-clock number, not the one your lead operator remembers.
The proven method for cutting it is SMED (Single-Minute Exchange of Dies), and this playbook builds on it. We'll cover how to find your true changeover duration, separate internal from external work, standardize across shifts, and hold the gains, all without a big automation build. Modernize without the mess, prove value in weeks, and skip the disruptive overhaul.
Key takeaways before you dig in
- Changeover time runs from the last good part of one run to the first good part of the next, and SMED is the structured method for shrinking it.
- The four-step spine: baseline with real data, separate internal vs. external tasks, convert internal work to external, then standardize and sustain.
- The biggest gains come from process changes like pre-staging, parallel tasks, and parameter pre-loading, not capital equipment.
- One Guidewheel customer cut downtime across five machines from an average of 6.8 hours/day per machine to 3.4 hours/day after using real-time visibility to focus improvement work.
- Real-time data is what keeps a SMED program from sliding back after the first few changeovers.
What changeover time includes on the factory floor
Changeover time covers everything from the last good part of one run to the first good part of the next: the machine stop, the tooling or die swap, the material load, parameter entry, and first-piece verification. It's elapsed wall-clock time, including the small waits operators rarely log.
On a real line, that looks like a press die swap, a mold change, or a fixture swap, plus walking to staging, hunting for the right hex key, and waiting on a material handler. In a packaging operation, it's swapping a filler nozzle and recalibrating a labeler between SKUs. Those quiet gaps add up.
What's the difference between SMED and just reducing changeover time?
Reducing changeover time is the goal. SMED is the structured method to get there. It works by classifying every task as either internal (the machine must be stopped) or external (it can happen while the line is still running), then shifting as much work as possible off the critical path. You can chase a faster changeover by hustling harder, but SMED gives you a repeatable way to find where the minutes actually hide.
People also mix up changeover time and setup time. Here's the plain-language difference.
| Term | What it measures | Where it starts/ends | Why it matters |
|---|---|---|---|
| Changeover time | Total lost production time between runs | Last good part of run A to first good part of run B | Reflects true uptime impact on the schedule |
| Setup time | The hands-on work of preparing the machine | Tooling/die installation through machine ready | Useful for coaching specific tasks, but understates total loss |
The takeaway: setup is a piece of changeover, not the whole picture. If you only measure setup, you'll miss the waits that quietly drain capacity.
How to baseline changeover time before you start SMED
You can't shrink what you haven't honestly measured. Baselining means capturing real start and end timestamps across several consecutive changeovers of the same transition, across shifts, instead of trusting the number a lead operator quotes from memory.
What are the steps of a SMED changeover-reduction project?
A SMED project follows a clear sequence. These steps preview the rest of this playbook:
- Baseline with real data.
- Map and time every task.
- Separate internal vs. external work.
- Convert internal tasks to external.
- Streamline whatever's left.
- Standardize and monitor.
Pick 2 to 3 representative changeovers on a high-volume line and record 5 to 10 consecutive events. Not the easiest, not the hardest, the typical ones.
Now the honest part: when teams move from manual logs to real timestamps, changeovers almost always run longer than what was written down. That gap isn't a failure. It's your opportunity, and it's usually bigger than anyone expected.
This is where a FactoryOps platform like Guidewheel helps with the "how." It automatically tracks downtime, cycle time, and production metrics, giving you a real-time basis for the baseline without piling manual logging onto your operators.
How to separate internal vs. external setup tasks
The core move in SMED is classifying every changeover task as internal (only possible while the machine is stopped) or external (possible while the previous job is still running). The win is moving as much work as you can off the stopped-machine critical path.
The best way to see it is to walk the floor and watch a real changeover with your operators. The people closest to the work already know which "stopped" tasks were really just waiting. A quick classification looks like this (durations are illustrative, not measured):
| Task | Duration | Internal or external? | Opportunity |
|---|---|---|---|
| Notify material handler | 5 min | External | Stage before last part runs |
| Stop and clear machine | 3 min | Internal | Keep, but tighten |
| Remove old die | 8 min | Internal | Keep |
| Transport new die from staging | 10 min | External | Pre-stage at machine |
| Install new die | 12 min | Internal | Keep, standardize |
| Enter parameters | 6 min | Internal | Convert via recipe recall |
| First-piece inspection | 5 min | Internal | Keep |
Notice the goal here isn't to second-guess your team. It's to capture what your best operators already do well and make that the standard everyone runs.
How to convert internal steps into external work with SMED
Converting internal to external is where you unlock the biggest gains without spending a dollar of capital. The move is simple: anything that can be prepared, staged, or pre-loaded before the machine stops gets done while the previous run is still going.
Three no-capital tactics deliver most of the win:
- Pre-staging and kitting: tooling and materials sitting at the machine before the last part runs, not in a crib across the building.
- Parameter pre-loading: recipe recall by barcode or preset instead of manual entry, so the line doesn't wait on someone typing in settings.
- Parallel operator tasks: a second team member stages the next job while the line is still producing the current one.
These are process changes, not capital projects. This is the whole "modernize without the mess" idea: improve the work you already run, without a disruptive overhaul. SMED is the framework driving the conversion, and the framework costs you observation time, not a purchase order.
The math is easy to picture. If you recover 20 minutes per changeover and run six changeovers a day, that's two hours of production time back, every day, on one line. And there's a sustainability angle baked in: fewer wasted minutes means less energy burned idling and less material scrapped dialing in the first good part. Productivity and sustainability pull in the same direction here.
How to standardize tools, roles, and checklists for faster changeovers
Standardization is what makes a fast changeover repeatable on every shift. Once you've externalized the work, lock it in with documented step-by-step procedures, defined roles, 5S tool organization (sort, set in order, shine, standardize, sustain), and a visual changeover checklist right at the machine.
How do I reduce changeover losses without a big automation project?
You don't need a major automation build. Start with SMED process changes, standard work, and a lightweight real-time visibility layer that goes live in days. That low-lift path is exactly what one team described:
It was plug and play. We were live on Guidewheel a day or two after receiving the sensors. We set up alerts and the team started receiving emails and text messages about issues they needed to know about. That was the aha moment that really got the team bought-in.
Matt Yandura, Director of Manufacturing, Onduline.
A practical standardization checklist:
- Ask operators how to make setup easier. They run it every day.
- Standardize the process across similar machines.
- Use checklists so nothing slips.
- Stage tools and parts in defined, easy-to-find locations.
- Reduce the total number of changeovers where you can.
The standard should be built from your best operator's method, not imposed on the floor from a conference room.
How to use real-time production data to sustain changeover gains
SMED gains hold when teams can see them in real time. Without a clear view shift by shift, old habits can return. Live changeover data against a target lets a supervisor step in during the changeover instead of arguing about it in Monday's meeting.
How do I track changeover start and end times automatically?
Automatic tracking marks the last good part and first good part from machine signal, with no manual logs. Guidewheel's FactoryOps platform reads each machine's electrical "heartbeat" and automatically tracks downtime, cycle time, and production metrics, so changeover start and end land on the timeline without a single spreadsheet. And getting there is quick:
The setup was quick—about 40 minutes to get sensors installed and data flowing. That speed was impressive.
Jose Juan Gonzalez Sanchez, Director of Vehicles Assembly Plant, General Motors.
How does real-time monitoring expose hidden changeover variability?
Real-time monitoring shows the shift-to-shift and operator-to-operator spread that manual logs hide, then lets you confirm which changes actually improved uptime. UrthPact, for example, first used live data to understand downtime on equipment prone to many micro-stops, then quantified which changes genuinely improved uptime within the first week.
That's the real lesson: variability is often a bigger problem than raw duration. Standardize first, then chase speed. Recognizing that every facility has different equipment, products, and goals, these are reference points, not universal targets.
Be the champion on your floor this quarter
Here's the move. Pick one high-volume line. Run 10 observed changeovers. Map internal versus external. Push the obvious external work out, standardize what's left, and track it live. That's a real SMED program you can start this quarter, without disrupting the floor.
If you want live changeover data your team can act on, see how a FactoryOps platform reads your machines' heartbeat and turns it into clear next steps. Book a Demo and start unlocking the capacity already hiding in your changeovers.
Updated for 2026.
Frequently asked questions
Why does our SMED project stall after the first few changeovers?
SMED projects stall when the new standard isn't reinforced shift by shift, so old habits quietly creep back in within a few weeks. Real-time visibility keeps the gains alive by showing how each changeover runs and exactly where to focus coaching. As Cantex plant manager Mike Verren put it:
It's also a great training tool. If I have a new operator I can see how he's performing on time sensitive changeovers and focus the coaching to help him/her quickly improve.
Mike Verren, Plant Manager, Cantex.
Why does machine state flip between running and idle during changeovers?
During a changeover, a machine often jogs, runs test cycles, or pauses between steps, so its state naturally bounces between running and idle. Guidewheel automatically tracks downtime, cycle time, and production metrics, and adds downtime coding and root-cause tracking, which helps you label those flips correctly instead of mistaking them for true production.
How long does it take to install sensors for automatic changeover tracking?
It's fast, typically same-day. One General Motors leader reported sensors installed and data flowing in about 40 minutes, and Onduline said it was live a day or two after receiving the sensors. That means automatic changeover tracking can be up and running without a long deployment or IT project getting in the way.
Do operators need to log changeover times manually in a SMED program?
No, they don't. Guidewheel automatically tracks downtime, cycle time, and production metrics, so changeover start and end are captured from machine signal instead of manual spreadsheet entry. That gives your team real-time visibility into every transition without adding any manual tracking work on the floor.
Can I view changeover performance by line, product, or shift?
Yes. Guidewheel supports granular performance coaching by line, product, and shift, so you can compare the same changeover across different operating contexts. Cantex uses that visibility to coach time-sensitive changeovers and bring newer operators up to the standard faster.
About the author
Lauren Dunford is the CEO and Co-Founder of Guidewheel, a FactoryOps platform that empowers factories to reach a sustainable peak of performance. A graduate of Stanford, she is a JOURNEY Fellow and World Economic Forum Tech Pioneer. Watch her TED Talk—the future isn’t just coded, it’s built.
