foratvise
Get Started

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 5 of the 112 studies that could observe it (limited evidence).

What happens

These labels record a generic time loss on the packaging line without identifying the specific component, failure mode, jam type or startup activity responsible; authors report only the aggregated loss bucket (a short stop or a startup-related loss) rather than its underlying physical or organisational cause. The loss may stem from any of several unreported events clearing automatically or by brief operator intervention, or from product/line behaviour during the ramp-up period.

What is done about it

Improve loss-reason granularity by configuring the line's downtime tracking system to require specific fault codes for every short stop and startup event, and train operators to log the actual cause at the moment of clearance. Periodically review the catch-all or default reason codes to reclassify recurring events into specific, actionable categories.

Practical guidance written from engineering knowledge; it is not a statistical estimate.

1Probability and evidence

Pooled over all segments. A wide interval is a result: it states how much the evidence allows us to know.
Probability of presence
1.4% [0.4–3.2%]
Expected share of lost time
0.8% [0.2–1.8%]
Share of lost time when present
57% [46–67%]
Studies / units
112 / 155
Evidence grade
C

Grade C: 2 to 4 studies, or an interval wider than 0.35.

2Probability by segment

Partially pooled estimates for each industry segment.
  • Dairy products
    1.4% [0.2–4.6%]14 studies
  • Soft drinks, bottled water and juices
    1.5% [0.3–4.1%]33 studies
  • Brewing, wine and spirits
    1.9% [0.3–5.5%]14 studies
  • Bakery and pasta
    2.2% [0.3–7.3%]6 studies
  • Meat, poultry and seafood
    1.5% [0.2–5.0%]6 studies
  • Fruit and vegetable processing
    1.6% [0.2–5.3%]4 studies
  • Grain and oilseed milling
    1.5% [0.2–5.0%]4 studies
  • Sugar and confectionery
    1.6% [0.2–5.1%]4 studies
  • Snacks, coffee, tea and other foods
    2.0% [0.3–6.1%]8 studies
  • Animal feed and pet food
    1.6% [0.2–5.2%]5 studies
  • Food manufacturing (unspecified or mixed)
    1.4% [0.2–4.5%]14 studies

3Mechanism, SCADA signature and countermeasure

Engineering guidance that helps recognise and address the cause; it is not part of the statistical estimate.

Mechanism

Engineering guidance

These labels record a generic time loss on the packaging line without identifying the specific component, failure mode, jam type or startup activity responsible; authors report only the aggregated loss bucket (a short stop or a startup-related loss) rather than its underlying physical or organisational cause. The loss may stem from any of several unreported events clearing automatically or by brief operator intervention, or from product/line behaviour during the ramp-up period.

How it looks in SCADA data

Engineering guidance

In SCADA/MES data this appears as short machine-state transitions to stopped or reduced-output states with generic or default fault codes, or as a startup-phase flag with below-target output and rejects before stabilisation; no specific alarm tag, sensor fault or component identifier is logged. Event duration and counters are captured but the associated reason code remains blank, defaulted, or mapped to a catch-all category.

Countermeasure

Engineering guidance

Improve loss-reason granularity by configuring the line's downtime tracking system to require specific fault codes for every short stop and startup event, and train operators to log the actual cause at the moment of clearance. Periodically review the catch-all or default reason codes to reclassify recurring events into specific, actionable categories.

4Sources

Every extracted datum with its study, value and verbatim quote.
  1. Share of planned time: 20.6 % · as reported: “overall plant down time”
    Show verbatim quote
    One year's data was gathered and it showed an average down time of 20.625 %; therefore, the plant's actual production was down by 20.625 % of its maximum capacity.
  2. Share of lost time: 0.350 % · as reported: “Breakdown Losses”
    Show verbatim quote
    Breakdown Losses 1,38% 0,35% 100%
  3. Share of lost time: 3.81 % · as reported: “Scrap Losses”
    Show verbatim quote
    Scrap Losses 14,86% 3,81% 99,6%
  4. Share of lost time: 24.9 % · as reported: “Speed Losses”
    Show verbatim quote
    Speed Losses 96,94% 24,87% 88,4%
  5. Share of lost time: 46.9 % · as reported: “process stoppages due to machinery”
    Show verbatim quote
    Lastly, process stoppages due to machinery were the most significant factor, with an impact of 46.85%, stemming from extended equipment setup times, which represented 19.84%, suggesting the implementation of the SMED methodology to reduce these delays.
  6. Lost time: 41.7 min · as reported: “Planned downtime”
    Show verbatim quote
    Rata-rata 41.68 401.25 10.12 97.07% 11.68 96.73%
  7. Lost time: 10.1 min · as reported: “Unplanned downtime (trouble mesin)”
    Show verbatim quote
    Rata-rata 41.68 401.25 10.12 97.07% 11.68 96.73%
  8. Lost time: 41.7 min · as reported: “Planned downtime”
    Show verbatim quote
    Rata-rata 41.68 401.25 10.12 97.07% 11.68 96.73%
  9. Lost time: 11.7 min · as reported: “Unplanned downtime (trouble mesin)”
    Show verbatim quote
    Rata-rata 41.68 401.25 10.12 97.07% 11.68 96.73%
  10. Share of lost time: 0 % · as reported: “Startup loss”
    Show verbatim quote
    Startup loss 0
  11. Share of lost time: 20.0 % · as reported: “Small stop loss”
    Show verbatim quote
    Small stop loss 20
  12. Lost time: 3.48 min · as reported: “Travel time”
    Show verbatim quote
    Travel time 3.48 min 2.03 min -1.45 min
  13. Lost time: 2.03 min · as reported: “Travel time”
    Show verbatim quote
    Travel time 3.48 min 2.03 min -1.45 min