- \n
- Short stops are cleared in seconds and rarely reach the manual log.<\/li>\n
- A plan built on that log leans toward breakdowns by default.<\/li>\n
- A few weeks of automatic stop records size each loss in hours.<\/li>\n
- Size TPM, lean, training and technology first, then choose.<\/li>\n<\/ul>\n<\/div>\n
Why short stops rarely reach the manual log<\/h2>\n
A manual downtime log is filled in by people who are busy running the line. When a sensor faults, a part jams in a feeder or a label misfeeds, the operator clears it in under a minute and restarts. Nobody walks to the terminal or the paper sheet for that. The stop was real, the line did not produce, but the record says nothing happened.<\/p>\n
Several mechanisms push in the same direction:<\/p>\n
- \n
- Recording thresholds.<\/strong> Many plants only ask for a reason above a few minutes. Everything below the threshold disappears by design.<\/li>\n
- End of shift recall.<\/strong> When the log is completed at the end of the shift, people remember the breakdown that called maintenance, not the twenty restarts in between.<\/li>\n
- Rounding.<\/strong> Durations get rounded to 5, 10 or 15 minutes. Long stops are inflated, short ones vanish.<\/li>\n
- The “other” bucket.<\/strong> When the list of reasons does not match what happened, the stop goes into “other” or “misc”, and nobody can act on it.<\/li>\n<\/ul>\n
The result is a log that describes breakdowns and changeovers reasonably well and says very little about minor stops and idling. Yet those are the losses that repeat dozens of times a shift. A plan built on that log will naturally lean toward breakdown work, because breakdowns are what the data shows.<\/p>\n
Six strategies, one question first: Doug Hanawalt’s article<\/h2>\n
Doug Hanawalt, Lead Productivity Improvement Specialist at Purdue MEP, sets out six levers in Practical Strategies for Improving Manufacturing Productivity<\/a>: adopt lean, optimize processes and workflows, focus on workforce development, implement Total Productive Maintenance, implement technology, and measure. It is a clear, practical list, and the order of the last item is worth noticing.<\/p>\n
In his section on measurement, he asks: “How do you know if you are continuously improving if you don\u2019t measure first?”<\/p><\/blockquote>\n
Two other points in his article connect directly to short stops. In the TPM section, he lists “idling and minor stops” among the six big losses and makes the case for preventing breakdowns rather than reacting to them. He also notes that three minutes of downtime per hour adds up to 12.5 days lost per year. In the technology section, he points out that machine monitoring has become more affordable than in the past. His article does not discuss any specific product, and the approach described below is TEEPTRAK’s own reading of how to apply the “measure first” principle to stop data.<\/p>\n
![\"Four-step](\"https:\/\/teeptrak.com\/wp-content\/uploads\/2026\/11\/teeptrak-purdue-en.png\")
<\/figure>\nWhat a few weeks of automatic stop records show<\/h2>\n
Automatic stop records capture every stop from a machine signal, with a start time and an end time, whether it lasts eight seconds or two hours. Operators still add the reason, but they no longer decide whether a stop exists. Over a few weeks, that changes the picture in three ways.<\/p>\n
First, the count<\/strong> of stops goes up, often sharply, because short stops appear. Second, the distribution<\/strong> becomes visible: you can see how much time sits in stops under two minutes, between two and ten minutes, and above ten minutes. Third, patterns<\/strong> emerge by shift, product, hour of the day and machine, which a monthly log summary flattens out.<\/p>\n
Why a few weeks rather than a few days? Because you want to cover the normal product mix, all shifts, and at least a couple of changeovers per format. Three to four weeks is usually enough on a line that runs a stable mix. A line with long campaigns may need longer to see every product.<\/p>\n
From stop records to TPM and lean priorities<\/h2>\n
The point of the stop study is not a better chart. It is to size each candidate lever in hours before choosing one. The table below shows how typical patterns in the records map to the strategies in Doug Hanawalt’s list. The patterns are examples, not results from a specific plant.<\/p>\n
- End of shift recall.<\/strong> When the log is completed at the end of the shift, people remember the breakdown that called maintenance, not the twenty restarts in between.<\/li>\n
- Recording thresholds.<\/strong> Many plants only ask for a reason above a few minutes. Everything below the threshold disappears by design.<\/li>\n