- \n
- Warm-up, adjustments, ramp-up and scrap get scattered across OEE.<\/li>\n
- Monday mornings and restarts after planned shutdowns cost more than a normal shift.<\/li>\n
- A defined restart window lets you measure these losses separately.<\/li>\n
- A restart standard mainly reduces variability from one restart to the next.<\/li>\n<\/ul>\n<\/div>\n
A loss nobody measures separately<\/h2>\n
In most plants, the restart does not exist as a category. Warm-up is logged as downtime, or not at all. Adjustments get mixed up with breakdowns. Ramp-up shows up as diffuse slow running. Start-up parts go to scrap without anyone linking them to the restart. The result: the loss is there in Monday’s OEE, but it is scattered across three components and never becomes a topic.<\/p>\n
That is a problem, because restart losses are among the easiest to standardise. They repeat at every restart, under the same conditions, and depend largely on preparation. You just have to see them.<\/p>\n
Where restart losses come from<\/h2>\n
A restart combines several losses of different kinds, each hitting one OEE component.<\/p>\n
\n\n
\n \nSource of loss<\/th>\n OEE component affected<\/th>\n Sign on the shop floor<\/th>\n<\/tr>\n<\/thead>\n \n Warm-up, bringing to temperature or pressure<\/td>\n Availability<\/td>\n Machine powered but not yet producing<\/td>\n<\/tr>\n \n Restart adjustments and settings<\/td>\n Availability<\/td>\n Repeated short stops in the first hour<\/td>\n<\/tr>\n \n Ramp-up<\/td>\n Performance<\/td>\n Speed deliberately reduced or unstable<\/td>\n<\/tr>\n \n Start-up scrap<\/td>\n Quality<\/td>\n First parts scrapped or reworked<\/td>\n<\/tr>\n \n Waiting at start-up (material, people, sign-off)<\/td>\n Availability<\/td>\n Line ready, but nothing arrives<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Taken one by one, these losses look normal: you have to warm up, you have to adjust. It is their sum, and above all their variability from one restart to the next, that deserves attention.<\/p>\n
![\"Four-step](\"https:\/\/teeptrak.com\/wp-content\/uploads\/2026\/11\/teeptrak-solo-a4-en.png\")
<\/figure>\nMonday morning: the weekend effect<\/h2>\n
Monday stacks several factors. Machines are cold, some fluids have settled, tools may have been removed for cleaning. The morning shift is not always the one that stopped the line on Friday, and information on the machine’s condition got lost in between. Material is not always at the line on time. And settings that worked on Friday evening on a hot machine no longer work on a cold one.<\/p>\n
In many shops, this shows up as a Monday OEE that is structurally lower than on other days, something everyone knows and nobody quantifies. Comparing Monday’s first shift with the average first shift of the other days is an excellent starting point.<\/p>\n
After a planned shutdown: maintenance, holidays, stocktaking<\/h2>\n
Restarting after a planned shutdown adds its own risks. After maintenance work, the machine may have been dismantled, parts replaced, settings changed. After summer or year end holidays, the shutdown is long enough for routines to be lost and latent defects to appear. These restarts are rarer, so less practised, and they often cost far more than an ordinary Monday.<\/p>\n
The classic mistake is to treat the planned shutdown as over when the work is finished. In reality, it ends when the line is back at nominal speed with good parts. In between lies a grey period nobody owns: maintenance considers the machine handed back, production considers it not yet received.<\/p>\n
How to measure restart losses separately<\/h2>\n
Measuring the restart separately requires a clear definition, applied the same way everywhere.<\/p>\n
- \n
- Define the restart event.<\/strong> For example: any restart after a stop of more than eight hours, plus any restart after planned maintenance. The rule matters less than its consistency.<\/li>\n
- Define the start and end of the window.<\/strong> Start: the planned restart time, not the actual time of the first part. End: the moment nominal speed is reached and held for a set duration, with conforming parts.<\/li>\n
- Create a dedicated category.<\/strong> Stops and slow running inside the window go to a restart family, with sub-reasons (warm-up, adjustment, waiting for material, waiting for sign-off).<\/li>\n
- Count start-up scrap separately<\/strong>, with a dedicated bin or code, so it is not mixed with defects from normal running.<\/li>\n
- Compare.<\/strong> Window duration, losses by component, scrap: by line, by day of the week, by shift and by restart type. Variability often says more than the average.<\/li>\n<\/ol>\n
A word of caution: starting the window at the actual time of the first part erases exactly the losses you are looking for, especially waiting and warm-up.<\/p>\n
Worked example: an extrusion line on Monday<\/h2>\n
For example, an extrusion line shut down every weekend (fictitious figures, for illustration only). The restart is planned for 6 am. After four weeks of separate measurement, the team sees that the restart window lasts 2 h 10 on average, but varies from 1 h 20 to 3 h 30 depending on the week. Warm-up accounts for 50 minutes and is stable. The variation comes from die adjustments and from waiting for material when the morning forklift driver does not have the picking list. Automatic heating before the team arrives and a picking list left on Friday shorten the window and, above all, narrow its spread.<\/p>\n
The lesson is general: warm-up is rarely the priority target, because it is known and stable. Variable losses are the expensive ones, and they only show up when every restart is measured.<\/p>\n
Building a restart standard<\/h2>\n
Once losses are visible, the restart standard addresses them one by one. It fits on one page per line and contains at least:<\/p>\n
- \n
- Preparation the day before<\/strong>: material, tooling, documents, handover notes from the shift that stops to the shift that restarts.<\/li>\n
- The start-up sequence<\/strong>, with planned warm-up times and what can be launched before the team arrives.<\/li>\n
- Cold reference settings<\/strong>, distinct from production settings, and when to switch from one to the other.<\/li>\n
- The first good part criterion<\/strong> and who signs it off, with a response time.<\/li>\n
- The ramp-up profile<\/strong>: steps and durations, rather than an improvised climb.<\/li>\n
- The target window duration<\/strong>, tracked at every restart and discussed at the production meeting when exceeded.<\/li>\n<\/ul>\n
For restarts after maintenance, the standard adds an explicit handover between maintenance and production, with the end of the planned shutdown defined by production recovered, not by work completed.<\/p>\n
What TEEPTRAK brings to restart measurement<\/h2>\n
TEEPTRAK automatically measures each machine’s activity, stops, micro-stops and speed, with precise timestamps. A module wired into the electrical cabinet and a sensor at the line are all it takes, with no PLC connection, about one hour of installation per machine and OEE available within 48 hours. The restart window becomes visible: restart time, short adjustment stops, ramp-up profile. Operators qualify reasons, so a restart family can be tracked week after week. Equipped plants see on average a 10 to 15 point OEE gain and 30% fewer unplanned stops.<\/p>\n
Further reading<\/h3>\n
- \n
- Changeover time: how to really measure it, ramp-up included<\/a><\/li>\n
- The 6 big losses: what your manual log doesn’t see<\/a><\/li>\n
- Quality Rate OEE: How to Calculate, Measure and Improve This Critical Manufacturing Metric<\/a><\/li>\n<\/ul>\n
FAQ<\/h2>\n
Are restart losses planned downtime?<\/strong> Warm-up defined in the standard can be treated as planned time, provided its duration is fixed. Anything beyond the standard is a loss and must show up in OEE.<\/p>\n
Should restarts be separated from changeovers?<\/strong> Yes. Both include ramp-up, but their causes differ: a cold machine and a returning team on one side, a product and tooling change on the other. Mixing them blurs both analyses.<\/p>\n
How do you set the end of the restart window?<\/strong> Use a measurable criterion: nominal speed reached and held for a set duration, with conforming parts. The exact duration depends on the process; what matters is that it is the same for every restart compared.<\/p>\n
\nYour real OEE within days<\/div>\nModule wired in the electrical cabinet, sensor at the edge of the line, about one hour of installation per machine, no MES project and no production stop.<\/div>\n - The 6 big losses: what your manual log doesn’t see<\/a><\/li>\n
- The start-up sequence<\/strong>, with planned warm-up times and what can be launched before the team arrives.<\/li>\n
- Define the start and end of the window.<\/strong> Start: the planned restart time, not the actual time of the first part. End: the moment nominal speed is reached and held for a set duration, with conforming parts.<\/li>\n
- Define the restart event.<\/strong> For example: any restart after a stop of more than eight hours, plus any restart after planned maintenance. The rule matters less than its consistency.<\/li>\n