- \n
- Waiting for material is an availability loss, like a breakdown.<\/li>\n
- Separate upstream waiting, downstream blocking, breakdowns and organisation.<\/li>\n
- Quantify lost hours, starting with the bottleneck machine.<\/li>\n
- Kanban, line side storage and rounds are targeted with measured stops.<\/li>\n<\/ul>\n<\/div>\n
A loss nobody owns<\/h2>\n
A machine waiting for material makes no noise. It is in good condition, the operator is there, the program is loaded. What is missing is a bin of components, a coil, a batch of blanks or an empty cart to clear finished parts. In many plants this time ends up in a catch all category (miscellaneous, organisation, other) or is not recorded at all, because everyone sees it as normal.<\/p>\n
Yet it is an availability loss in OEE terms, exactly like a breakdown. It weighs on line output, but it appears in no maintenance action plan, because maintenance cannot fix it, and rarely in logistics KPIs, which track service level or inventory, not machine waiting time. As long as it is neither named nor measured, it stays an orphan.<\/p>\n
Classifying the wait: upstream, downstream, and what it is not<\/h2>\n
The first step is to clearly separate four situations that operators often mix up when they log a stop.<\/p>\n
\n\n
\n \nSituation<\/th>\n What you observe<\/th>\n Who owns the action<\/th>\n<\/tr>\n<\/thead>\n \n Upstream wait (material shortage)<\/td>\n The machine is ready but has nothing to process: missing components, batch not delivered, material on quality hold<\/td>\n Internal logistics, supply, upstream station<\/td>\n<\/tr>\n \n Downstream wait (blocking)<\/td>\n The machine has produced but cannot evacuate: full bin, saturated conveyor, next station stopped, no storage location<\/td>\n Downstream station, material handling, flow management<\/td>\n<\/tr>\n \n Breakdown or technical stop<\/td>\n The machine cannot produce even with material available<\/td>\n Maintenance, setters<\/td>\n<\/tr>\n \n Organisational stop<\/td>\n No operator, meeting, uncovered break<\/td>\n Production supervision<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The upstream and downstream split matters: a material shortage is solved at the internal supplier, blocking is solved at the internal customer. Lumping both into a single waiting code asks two teams to fix a problem of which neither sees the full picture.<\/p>\n
You also need a rule for a common case: a machine that breaks down while material is missing. Code the cause that actually prevents restart. If material arrives and the machine does not restart, it is a breakdown. If the machine is repaired and still waits for its batch, the end of the stop is material waiting. Splitting one stop into two successive reasons is better than assigning it as a block.<\/p>\n
Telling a wait from a breakdown in the data<\/h3>\n
On a time stamped stop log, waits and breakdowns often show different signatures that help you check data quality.<\/p>\n
- \n
- Timing:<\/strong> material waits tend to cluster at specific moments (start of shift, after a changeover, just before a replenishment round), while breakdowns are more scattered.<\/li>\n
- Simultaneity:<\/strong> if several machines fed by the same flow stop within the same fifteen minutes, the cause is rarely technical.<\/li>\n
- Restart:<\/strong> after a wait, the machine usually resumes at normal speed straight away; after a breakdown you more often see a slow restart, scrap or micro stops.<\/li>\n
- Duration:<\/strong> waits often have regular durations, aligned with the logistics round cycle.<\/li>\n<\/ul>\n
These signatures do not replace the reason entered by the operator, but they quickly reveal misclassified stops and let you run the topic with facts.<\/p>\n
![\"Four](\"https:\/\/teeptrak.com\/wp-content\/uploads\/2026\/11\/teeptrak-solo-a5-en.png\")
<\/figure>\nQuantifying the losses: an illustrative example<\/h2>\n
For example, take a fictitious three station assembly line fed with components by a tugger train every two hours. The figures below are invented for illustration. Over a week of ten eight hour shifts, stop measurement shows 14 hours of downtime in total. After classification, the split is: 5 hours of breakdowns and adjustments, 6 hours of upstream waiting, 2 hours of downstream waiting and 1 hour of organisational stops.<\/p>\n
In this example, upstream waiting weighs more than breakdowns, while the line action plan only contained maintenance topics. Against 80 hours of planned time, it represents 7.5 % of available time. To express it in money, multiply those hours by the number of parts the line would have produced at nominal rate, then by unit margin or line hourly cost. The point is not to find someone to blame: it gives the loss an order of magnitude that management can weigh against other projects.<\/p>\n
Two precautions. First, use only measured stops, not estimates written at the end of the shift. Second, separate the bottleneck from the other machines: an hour of waiting on the bottleneck is an hour lost for the whole line, while an hour on an unconstrained station may be partly recovered.<\/p>\n
Opening the conversation between production and logistics<\/h2>\n
Material waiting sits on a boundary between departments. To move forward, you need a shared method rather than an exchange of complaints in the production meeting.<\/p>\n
- \n
- Measure before you discuss.<\/strong> Gather two to four weeks of time stamped stops, with upstream and downstream reasons kept separate.<\/li>\n
- Share the same view.<\/strong> Show logistics the same Pareto as production, by machine, by shift and by hour of the day.<\/li>\n
- Look for repetitions.<\/strong> A wait that comes back every day at the same time points to a round or sizing issue, not an incident.<\/li>\n
- Set a common target.<\/strong> For example, a cap on weekly upstream waiting hours on the bottleneck, tracked by both teams.<\/li>\n
- Review weekly.<\/strong> A short meeting, data on screen, to check that actions are bending the curve.<\/li>\n<\/ol>\n
Actions that really reduce waiting<\/h2>\n
Once waits are classified and quantified, the levers are well known. What changes is that you can target them and check their effect.<\/p>\n
- \n
- Kanban:<\/strong> replenishment triggered by actual consumption rather than a fixed schedule limits shortages at the station. Stop data helps size the number of cards on the part numbers that cause the most waiting.<\/li>\n
- Line side storage:<\/strong> review locations, quantities held at the station and bin presentation, so operators do not discover a shortage at the last moment.<\/li>\n
- Round frequency:<\/strong> if waits cluster just before the tugger train passes, the frequency or sequence of the round needs review.<\/li>\n
- Low level material call:<\/strong> trigger the request before the shortage, not when the station is already empty.<\/li>\n
- Downstream evacuation:<\/strong> for blocking, properly sized buffer locations and regular removal of full bins.<\/li>\n<\/ul>\n
What automatic measurement changes<\/h2>\n
TEEPTRAK measures stops and micro stops on every machine in real time with a module wired into the electrical cabinet and a line side sensor, with no PLC connection, about one hour of installation per machine and OEE available within 48 hours. Operators qualify the stop reason, including upstream or downstream waiting, and every stop is time stamped. Production and logistics work from the same data. Across more than 700 plants in over 30 countries, TEEPTRAK customers gain 10 to 15 OEE points on average.<\/p>\n
Further reading<\/h3>\n
- \n
- Downtime reason codes: the standard list and how to use them<\/a><\/li>\n
- Value stream mapping with measured machine data<\/a><\/li>\n
- Bottleneck analysis with OEE<\/a><\/li>\n<\/ul>\n
FAQ<\/h2>\n
Does material waiting lower OEE?<\/strong> Yes. If the machine was scheduled to produce, waiting for material is an availability loss, just like a breakdown. Excluding it flatters the indicator but hides the loss.<\/p>\n
Should all waits share one reason code?<\/strong> No. At a minimum, separate upstream waiting (material shortage) from downstream waiting (blocking), because actions and owners differ.<\/p>\n
How long should you measure before acting?<\/strong> Two to four weeks are usually enough to see repetitions by shift, hour and part number, and to build a first Pareto shared with logistics.<\/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 - Value stream mapping with measured machine data<\/a><\/li>\n
- Line side storage:<\/strong> review locations, quantities held at the station and bin presentation, so operators do not discover a shortage at the last moment.<\/li>\n
- Share the same view.<\/strong> Show logistics the same Pareto as production, by machine, by shift and by hour of the day.<\/li>\n
- Simultaneity:<\/strong> if several machines fed by the same flow stop within the same fifteen minutes, the cause is rarely technical.<\/li>\n
- Timing:<\/strong> material waits tend to cluster at specific moments (start of shift, after a changeover, just before a replenishment round), while breakdowns are more scattered.<\/li>\n