In short
It appears in fewer than 1 of every 100 lines studied.
When it appears, it takes on average about 57 % of the line's lost time. Reported by 0 of the 120 studies that could observe it (sparse evidence).
What happens
The line is stopped because operators and support staff are gathered for scheduled talks, shift briefings, safety meetings or training sessions that are organized independently of equipment condition or product changeover needs. Production simply pauses while the workforce is engaged in a non-production activity away from the machines.
What is done about it
Schedule talks and meetings during already planned breaks, shift handovers or changeovers so they do not add independent downtime, and stagger attendance or use relief operators so minimal line coverage is maintained. Standardize short, structured huddles outside production windows and track their duration separately from technical stop causes.
Practical guidance written from engineering knowledge; it is not a statistical estimate.
1Probability and evidence
- Probability of presence
- 0.4% [0.1–1.1%]
- Expected share of lost time
- 0.2% [0.0–0.6%]
- Share of lost time when present
- 57% [45–68%]
- Studies / units
- 120 / 162
- Evidence grade
- D
Grade D: 0 or 1 study; the estimate is driven by partial pooling and priors, and the wide interval is the result.
2Probability by segment
- Dairy products0.4% [0.0–1.6%]18 studies
- Soft drinks, bottled water and juices0.4% [0.0–1.3%]44 studies
- Brewing, wine and spirits0.4% [0.0–1.6%]16 studies
- Bakery and pasta0.5% [0.0–1.9%]0 studies
- Meat, poultry and seafood0.4% [0.0–1.7%]6 studies
- Fruit and vegetable processing0.4% [0.0–1.7%]4 studies
- Grain and oilseed milling0.4% [0.0–1.8%]6 studies
- Sugar and confectionery0.5% [0.0–1.7%]3 studies
- Snacks, coffee, tea and other foods0.4% [0.0–1.7%]6 studies
- Animal feed and pet food0.5% [0.0–1.7%]4 studies
- Food manufacturing (unspecified or mixed)0.4% [0.0–1.6%]13 studies
3Mechanism, SCADA signature and countermeasure
Mechanism
Engineering guidanceThe line is stopped because operators and support staff are gathered for scheduled talks, shift briefings, safety meetings or training sessions that are organized independently of equipment condition or product changeover needs. Production simply pauses while the workforce is engaged in a non-production activity away from the machines.
How it looks in SCADA data
Engineering guidanceSCADA/MES logs show the line entering an idle or stopped state with no equipment fault, alarm or interlock trip associated with the event; the stop is typically tagged as a manual or organizational downtime reason code and tends to cluster around shift-start times or fixed times of day, with no abnormal signal patterns on upstream or downstream stations.
Countermeasure
Engineering guidanceSchedule talks and meetings during already planned breaks, shift handovers or changeovers so they do not add independent downtime, and stagger attendance or use relief operators so minimal line coverage is maintained. Standardize short, structured huddles outside production windows and track their duration separately from technical stop causes.
4Sources
- Proposal for improvement to increase the overall equipment effectiveness (OEE) of a dairy products company through a Preventive Maintenance Plan, Standardized Work, and SMED (2025)Open sourceShare of planned time: 1.50 % · as reported: “Charlas/Reuniones”
Show verbatim quote
Charlas /Reuniones Velocidad reducida Defectuosos 1,50% 2,10% 0,05%
- Proposal for improvement to increase the overall equipment effectiveness (OEE) of a dairy products company through a Preventive Maintenance Plan, Standardized Work, and SMED (2025)Open sourceShare of planned time: 1.50 % · as reported: “Charlas/Reuniones”
Show verbatim quote
Charlas /Reuniones Velocidad reducida Defectuosos 1,50% 1,00% 0,05%

