Water and beverages · WB-02 · Line speed after marking

The code was added to the line. Speed was never measured.

Producers report that line speed and efficiency fell after marking was introduced. This loss usually does not appear separately in the shift report: the stoppage is recorded, but its cause is not.

Platform: Plant Pulse, Goods Flow

20%+

Drop in line efficiency and speed after marking was introduced, according to one producer.1

10%+

Losses due to stoppages, according to another producer.1

60,000

High-speed line output cited by a representative of a large producer, bottles/hour.2

Until the speed loss is measured, it can neither be recovered nor claimed from the equipment supplier.

Who it is for

Production director
Gap between nominal and actual speed; causes of stoppages.
Chief mechanic
Printer and camera settings; spare parts.
Shift supervisor
Recording stoppages and their causes.
Plant owner
Lost production in monetary terms.

Where the problem lies

  • Printer and camera do not match line speed

    If code application or reading is slower than the line, the entire line runs at the speed of that stage.

  • Stoppage cause is not recorded

    The operator restarts the line, but whether the stoppage was caused by marking or by something else is not recorded.

  • Setup depends on an external specialist

    During format changes or faults, the line waits for a specialist and does not run in the meantime.

  • Not compared with nominal speed

    The shift report shows units produced, but not how much was lost relative to line capacity.

How the loss is calculated

Speed loss(nominal − actual) units/hour × operating hours × margin per unit
Stoppagestoppage minutes × line rate (units/minute) × margin per unit
Rejectsrejected units × unit cost
Waitinghours spent waiting for a specialist × line value per hour

Calculate with your data

Line Speed Loss from Serialisation Calculator

This calculator estimates how much code application and inspection reduce line speed while the line is running.

Use spaces for thousands and a dot or comma for decimals. Use the same currency throughout.

Values stay in this page and are not sent to the server.

Scenario estimate

0 / 6 values entered

Enter your operating figures to see the estimate.

Measure actual speed over running time only, excluding stoppages. Otherwise stoppage losses will be double counted. The result is contribution margin at risk, not lost revenue. The scenario speed is set by the user, and achieving it is not promised. The calculator does not provide the cost of a solution or an implementation timeline; these require an audit. Changes to line software may only be made with the equipment supplier's approval. The result does not account for regulatory requirements or deadlines.

Formulas and assumptions

This calculator estimates how much code application and inspection reduce line speed while the line is running. It calculates the monthly output not produced and the contribution margin at risk on that volume. The margin is counted only for the share of extra output that could actually be sold. You can compare the current situation with a speed scenario you define yourself. Enter all values from your own line counter and accounting data. The calculation period is one month. Stoppages, rejects, specialist waiting time and investment costs are excluded. Results are estimates, not guarantees.

Units not produced due to speed loss
(Nominal speed − actual speed, units/hour; taken as 0 if negative) × monthly running hours = units not produced per month.
Current situation: contribution margin at risk
Units not produced (units/month) × contribution margin per unit × sellable share (% / 100). This is monthly contribution margin at risk, not revenue.
Scenario: contribution margin at risk
(Nominal speed − scenario speed, units/hour; 0 if negative) × monthly running hours × contribution margin per unit × sellable share (% / 100). Reaching the scenario speed is not guaranteed.
Difference between current situation and scenario
Current contribution margin at risk minus scenario margin at risk (currency/month). A negative result is shown as 0. This is an estimated difference, not guaranteed savings or income.

Facts and global practice

  • Producer of carbonated soft drinks and water

    After marking was introduced, line efficiency and speed fell "in practice by more than 20%"; costs and unit cost rose.1

  • Juice and beverage producer, over 30 million litres per year

    Losses due to stoppages are "at least 10%".1

  • Representative of a large producer

    A high-speed line produces 60,000 bottles per hour; a minor code-reading fault or an internet outage stops the line immediately.2

  • Representative of a large producer

    If a bottle is not counted or ends up in the wrong bundle, it has to be searched for along the entire line.2

  • Plant manager at a large producer

    The country lacks specialists to set up the equipment.2

  • UzBev association

    In trials, no supplier was able to offer a complete technical solution that does not reduce high-speed line output.1

The percentages above relate to two different companies and must not be added together. They are not industry averages. Losses must be measured separately at each plant.

Measuring and recovering speed

Losses are first measured stage by stage, then the largest constraint is removed. Existing equipment is not replaced; monitoring is added on top of it.

  1. 01Line
    • Printer speed
    • Camera reading speed
    • Rejecting faulty units
  2. 02Recording
    • Stoppage time
    • Cause code
    • Operator panel
  3. 03Analysis
    • Availability
    • Performance
    • Quality (OEE)
  4. 04Service
    • Setup manual
    • Spare parts list
    • Local engineer

Modules

The current maturity level is shown next to each module.

Camera inspection on the lineReading every code at line speed and rejecting faulty unitsEngineering capability
Recording stoppage causesOperator panel, cause codes, shift reportEngineering capability
Line efficiency (OEE)Calculation by availability, performance and qualityEngineering capability
Asl belgisi integrationTracking of applied and rejected codesCommercially available
Setup and serviceInspection and re-adjustment of existing equipmentCommercially available

How we start

  1. 01

    Speed audit

    The speed and stoppages of each stage are measured over several shifts.

    Outcome: the constraining stage is identified.

  2. 02

    Setting up recording

    An operator panel and cause codes are introduced.

    Outcome: stoppages are visible with their causes.

  3. 03

    Removing the constraint

    Measures related to setup, camera or printer.

    Outcome: speed is measured again.

  4. 04

    Scaling up

    Rolled out to other lines and formats.

    Outcome: monthly metrics.

What is measured

Actual / nominal speedUnits produced / line capacity, per shiftLine counter
Stoppages caused by markingMinutes, by cause codeOperator panel
Rejected unitsRejected / total, per shiftCamera
Recovery timeAverage time from stoppage to restartOperator panel
OEEAvailability × performance × qualityOEE module

What is needed to start

  • Person responsible for the line
  • Nominal line speed and list of formats
  • Shift schedule
  • Access to the line for measurement

What we do not promise

  • Exact timeline and price without an audit
  • Government decisions and deadlines
  • Changes to line software without the equipment supplier's permission
  • Unmeasured results or savings

Self-check

  1. Is the nominal speed of each line documented?
  2. Is actual speed compared with nominal speed at the end of each shift?
  3. Is stoppage time recorded automatically?
  4. Is the cause of each stoppage recorded?
  5. Are stoppages caused by marking shown separately?
  6. Is the number of units rejected by the camera known?
  7. Is format changeover time measured?
  8. Are printer and camera settings documented?
  9. Can a local engineer arrive within one day in case of a fault?
  10. Are key spare parts kept in stock?

Line speed audit

We measure the speed and stoppages of the marking stages on your line and identify the largest constraint.

  • Speed map by stage
  • List of stoppage causes
  • Action plan and budget

Sources

  1. Statements by producers and UzBev. gazeta.uz, 15.04.2026.
  2. Statements by producers and UzBev. gazeta.uz, 30.03.2026.