foratvise
Get Started
Setup and adjustments

Changeover setup delay (baking)

Setup and adjustmentsAvailabilityBaking

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 1 of the 60 studies that could observe it (sparse evidence).

What happens

During a product or format changeover on the baking line, the crew must wait for instructions or materials, carry out verification inspections of oven settings and product parameters, and perform manual setup operations such as adjusting temperature profiles, belt speed or mould configuration. Each of these activities consumes time between the last good unit of the previous run and the first good unit of the next, extending the changeover beyond the ideal duration.

What is done about it

Apply structured changeover methods (SMED) to separate internal and external tasks, pre-stage tools, settings and inspection checklists before the line stops, and standardize the sequence of inspection and adjustment steps so they can run in parallel. Train operators on the standardized procedure and track changeover duration against a target to drive continuous reduction.

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
0.7% [0.1–2.1%]
Expected share of lost time
0.4% [0.1–1.2%]
Share of lost time when present
57% [45–67%]
Studies / units
60 / 73
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

Partially pooled estimates for each industry segment.
  • Dairy products
    0.8% [0.1–3.4%]5 studies
  • Soft drinks, bottled water and juices
    0.8% [0.1–3.4%]1 study
  • Brewing, wine and spirits
    0.8% [0.1–3.2%]0 studies
  • Bakery and pasta
    1.0% [0.1–3.3%]27 studies
  • Meat, poultry and seafood
    0.8% [0.1–3.3%]2 studies
  • Fruit and vegetable processing
    0.8% [0.1–3.1%]2 studies
  • Grain and oilseed milling
    0.8% [0.1–3.4%]0 studies
  • Sugar and confectionery
    0.8% [0.1–3.0%]8 studies
  • Snacks, coffee, tea and other foods
    0.8% [0.1–3.2%]4 studies
  • Animal feed and pet food
    0.8% [0.1–3.2%]4 studies
  • Food manufacturing (unspecified or mixed)
    0.8% [0.1–3.3%]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

During a product or format changeover on the baking line, the crew must wait for instructions or materials, carry out verification inspections of oven settings and product parameters, and perform manual setup operations such as adjusting temperature profiles, belt speed or mould configuration. Each of these activities consumes time between the last good unit of the previous run and the first good unit of the next, extending the changeover beyond the ideal duration.

How it looks in SCADA data

Engineering guidance

The line or oven state log shows an extended changeover/setup state with internal sub-states for waiting, inspection and adjustment, no good-unit counts being registered, and repeated operator acknowledgements or parameter entries. Oven temperature and belt-speed trends show a plateau or stabilization phase that lasts longer than the standard ramp-up window, with no product throughput recorded.

Countermeasure

Engineering guidance

Apply structured changeover methods (SMED) to separate internal and external tasks, pre-stage tools, settings and inspection checklists before the line stops, and standardize the sequence of inspection and adjustment steps so they can run in parallel. Train operators on the standardized procedure and track changeover duration against a target to drive continuous reduction.

4Sources

Every extracted datum with its study, value and verbatim quote.
  1. Number of events: 366 events · as reported: “Operations”
    Show verbatim quote
    Operaciones 366 518:05
  2. Lost time: 518 min:s · as reported: “Operations”
    Show verbatim quote
    Operaciones 366 518:05
  3. Number of events: 45.0 events · as reported: “Inspections”
    Show verbatim quote
    Inspecciones 45 77:10
  4. Lost time: 77.1 min:s · as reported: “Inspections”
    Show verbatim quote
    Inspecciones 45 77:10
  5. Number of events: 4.00 events · as reported: “Delays”
    Show verbatim quote
    Demoras 4 1295:15
  6. Lost time: 1,295 min:s · as reported: “Delays”
    Show verbatim quote
    Demoras 4 1295:15