In short
It appears in about 1 of every 100 lines studied.
When it appears, it takes on average about 57 % of the line's lost time. Reported by 3 of the 120 studies that could observe it (sparse evidence).
What happens
The filler is deliberately stopped as part of the production schedule, for reasons such as scheduled maintenance, breaks, shift changes or lack of demand, rather than due to any equipment malfunction or product issue. No output is expected during this interval because the line is intentionally taken out of operation.
What is done about it
Confirm the stop against the production and maintenance schedule so it is correctly excluded from availability losses, and ensure the operator logs the planned reason code consistently. Optimize the schedule itself (maintenance windows, break timing, shift handover) to minimize unnecessary idle time without affecting the OEE loss accounting.
Practical guidance written from engineering knowledge; it is not a statistical estimate.
1Probability and evidence
- Probability of presence
- 0.6% [0.1–1.6%]
- Expected share of lost time
- 0.3% [0.1–0.9%]
- 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.7% [0.1–2.3%]18 studies
- Soft drinks, bottled water and juices0.5% [0.1–1.7%]44 studies
- Brewing, wine and spirits0.6% [0.1–2.2%]16 studies
- Bakery and pasta0.7% [0.1–2.6%]0 studies
- Meat, poultry and seafood0.7% [0.1–2.4%]6 studies
- Fruit and vegetable processing0.7% [0.1–2.7%]4 studies
- Grain and oilseed milling0.7% [0.1–2.5%]6 studies
- Sugar and confectionery0.7% [0.1–2.7%]3 studies
- Snacks, coffee, tea and other foods0.7% [0.1–2.5%]6 studies
- Animal feed and pet food0.7% [0.1–2.7%]4 studies
- Food manufacturing (unspecified or mixed)1.0% [0.1–3.6%]13 studies
3Mechanism, SCADA signature and countermeasure
Mechanism
Engineering guidanceThe filler is deliberately stopped as part of the production schedule, for reasons such as scheduled maintenance, breaks, shift changes or lack of demand, rather than due to any equipment malfunction or product issue. No output is expected during this interval because the line is intentionally taken out of operation.
How it looks in SCADA data
Engineering guidanceSCADA/MES shows the filler state transitioning to a dedicated planned-stop or standby code aligned with the shift calendar, with no associated fault or alarm codes. The stop duration matches scheduled maintenance or break windows and upstream/downstream equipment typically shows the same planned-state pattern simultaneously.
Countermeasure
Engineering guidanceConfirm the stop against the production and maintenance schedule so it is correctly excluded from availability losses, and ensure the operator logs the planned reason code consistently. Optimize the schedule itself (maintenance windows, break timing, shift handover) to minimize unnecessary idle time without affecting the OEE loss accounting.
4Sources
- Lost time: 0 mnt · as reported: “Planned Down Time”
Show verbatim quote
B Planned Dow n Time mnt 0 0 39
- Lost time: 0 mnt · as reported: “Planned Down Time”
Show verbatim quote
B Planned Dow n Time mnt 0 0 39
- Lost time: 39.0 mnt · as reported: “Planned Down Time”
Show verbatim quote
B Planned Dow n Time mnt 0 0 39

