foratvise
Get Started
not classifiable

Screw press downtime of mixed/unrecorded cause

In short

It appears in about 2 of every 100 lines studied.

When it appears, it takes on average about 57 % of the line's lost time. Reported by 2 of the 37 studies that could observe it (limited evidence).

What happens

The primary study logs stop time on the screw press under generic labels such as set up, breakdown, downtime, planned downtime or dirty without separating the underlying physical or organisational mechanism, so the same bucket mixes changeovers, mechanical failures, scheduled maintenance and hygiene-related stops. Because the reason code is not disaggregated at source, the cluster cannot be tied to a single failure mode or adjustment task.

What is done about it

Implement a structured, mutually exclusive downtime reason-code taxonomy at the press HMI that forces the operator to separate changeover, mechanical failure, scheduled maintenance and hygiene stops at the moment they occur, and audit the coding periodically for consistency. This reclassification enables the loss to be routed to the correct six-big-losses category for targeted root-cause analysis.

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.5% [0.3–4.2%]
Expected share of lost time
0.9% [0.2–2.4%]
Share of lost time when present
57% [45–68%]
Studies / units
37 / 44
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.7% [0.2–6.5%]5 studies
  • Soft drinks, bottled water and juices
    1.8% [0.2–6.6%]1 study
  • Brewing, wine and spirits
    1.8% [0.2–6.6%]1 study
  • Bakery and pasta
    1.8% [0.2–7.2%]0 studies
  • Meat, poultry and seafood
    1.7% [0.2–6.7%]2 studies
  • Fruit and vegetable processing
    1.7% [0.2–6.6%]3 studies
  • Grain and oilseed milling
    3.6% [0.4–12.6%]6 studies
  • Sugar and confectionery
    1.7% [0.2–6.5%]3 studies
  • Snacks, coffee, tea and other foods
    1.6% [0.2–5.8%]4 studies
  • Animal feed and pet food
    1.6% [0.2–5.5%]5 studies
  • Food manufacturing (unspecified or mixed)
    1.7% [0.2–6.1%]7 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

The primary study logs stop time on the screw press under generic labels such as set up, breakdown, downtime, planned downtime or dirty without separating the underlying physical or organisational mechanism, so the same bucket mixes changeovers, mechanical failures, scheduled maintenance and hygiene-related stops. Because the reason code is not disaggregated at source, the cluster cannot be tied to a single failure mode or adjustment task.

How it looks in SCADA data

Engineering guidance

Downtime counters or state logs for the press show a single aggregated stop-time tag covering several reason codes, with no consistent correlation to a specific alarm, sensor pattern or maintenance work order; equivalent stop durations appear under different labels across shifts or batches. The lack of a dedicated digital reason code makes it impossible to isolate a repeatable SCADA signature.

Countermeasure

Engineering guidance

Implement a structured, mutually exclusive downtime reason-code taxonomy at the press HMI that forces the operator to separate changeover, mechanical failure, scheduled maintenance and hygiene stops at the moment they occur, and audit the coding periodically for consistency. This reclassification enables the loss to be routed to the correct six-big-losses category for targeted root-cause analysis.

4Sources

Every extracted datum with its study, value and verbatim quote.
  1. Lost time: 420 menit · as reported: “Breakdown”
    Show verbatim quote
    1–6 Maret 8640 420 360 480 1166,01 0 1166,01
  2. Lost time: 360 menit · as reported: “Planned downtime”
    Show verbatim quote
    1–6 Maret 8640 420 360 480 1166,01 0 1166,01
  3. Lost time: 480 menit · as reported: “Set up”
    Show verbatim quote
    1–6 Maret 8640 420 360 480 1166,01 0 1166,01
  4. Lost time: 390 menit · as reported: “Breakdown”
    Show verbatim quote
    8–13 Maret 7200 390 300 420 961,76 0 961,76
  5. Lost time: 300 menit · as reported: “Planned downtime”
    Show verbatim quote
    8–13 Maret 7200 390 300 420 961,76 0 961,76
  6. Lost time: 420 menit · as reported: “Set up”
    Show verbatim quote
    8–13 Maret 7200 390 300 420 961,76 0 961,76
  7. Lost time: 450 menit · as reported: “Breakdown”
    Show verbatim quote
    15–20 Maret 8640 450 360 540 1043,31 0 1043,31
  8. Lost time: 540 menit · as reported: “Set up”
    Show verbatim quote
    15–20 Maret 8640 450 360 540 1043,31 0 1043,31
  9. Lost time: 390 menit · as reported: “Set up”
    Show verbatim quote
    22–27 Maret 7200 390 300 390 1154,16 0 1154,16
  10. Lost time: 240 menit · as reported: “Breakdown”
    Show verbatim quote
    29–3 April 5760 240 240 330 782,6 0 782,6
  11. Lost time: 240 menit · as reported: “Planned downtime”
    Show verbatim quote
    29–3 April 5760 240 240 330 782,6 0 782,6
  12. Lost time: 330 menit · as reported: “Set up”
    Show verbatim quote
    29–3 April 5760 240 240 330 782,6 0 782,6
  13. Lost time: 300 menit · as reported: “Breakdown”
    Show verbatim quote
    5–10 April 7200 300 300 450 601,64 0 601,64
  14. Lost time: 450 menit · as reported: “Set up”
    Show verbatim quote
    5–10 April 7200 300 300 450 601,64 0 601,64
  15. Lost time: 360 menit · as reported: “Breakdown”
    Show verbatim quote
    12–17 April 7200 360 240 510 867,39 0 867,39
  16. Lost time: 510 menit · as reported: “Set up”
    Show verbatim quote
    12–17 April 7200 360 240 510 867,39 0 867,39
  17. Lost time: 270 menit · as reported: “Set up”
    Show verbatim quote
    19–24 April 5760 240 240 270 805,98 0 805,98
  18. Lost time: 480 menit · as reported: “Breakdown”
    Show verbatim quote
    26–30 April 5760 480 240 360 744,24 0 744,24
  19. Lost time: 360 menit · as reported: “Set up”
    Show verbatim quote
    26–30 April 5760 480 240 360 744,24 0 744,24
  20. Defect rate: 0.0140 % · as reported: “Dirty”
    Show verbatim quote
    Desember 43.500.000 0,07 34.140 89,19% 0,014 6.090 99,98%
  21. Lost time: 720 menit · as reported: “Downtime”
    Show verbatim quote
    November 25 36.000 3.000 33.000 720 32.280 97,81
  22. Lost time: 4,260 menit · as reported: “Downtime”
    Show verbatim quote
    Desember 28 40.320 1.920 38.400 4.260 34.140 88,90
  23. Lost time: 3,000 menit · as reported: “Planned Downtime”
    Show verbatim quote
    November 25 36.000 3.000 33.000 720 32.280 97,81
  24. Lost time: 1,920 menit · as reported: “Planned Downtime”
    Show verbatim quote
    Desember 28 40.320 1.920 38.400 4.260 34.140 88,90