Packaging Changeover Codes: A Practical Loss Dictionary

Use the working record

Download the editable worksheet. Record the actual evidence and responsible reviewer against each relevant row. The empty results are inputs for your project, not completed tests. Add the equipment identity, operating period and reference method before assigning an outcome. Retain unsuccessful checks and the evidence from any repeat after correction.

Define the start and finish on the line

Agree the physical events that open and close a changeover. A useful specification might start at the last accepted pack of the previous product and end at a defined accepted production condition for the next. The actual definition belongs to the production and quality team. Record whether cleaning, clearance, trials and release sit inside that interval.

A first pack and a stable production condition are different milestones. Capture both if the improvement question requires them. Do not quietly shorten the recorded changeover by ending it at the first machine movement when packs still await quality release. Conversely, keep planned nonproduction time visible rather than presenting it as a changeover delay.

Use three separate fields

The activity field describes what the crew is doing: cleaning, changing tooling, loading packaging material or setting the machine. The delay field describes why an activity cannot proceed: material unavailable, maintenance support requested or release pending. The asset field identifies where the condition occurs.

These fields answer different questions. A single code such as machine problem often combines the station, symptom and presumed cause. Keep observed facts separate from later investigation. Operators should be able to select a defensible reason during the shift without diagnosing a failure that requires specialist review.

Make each code observable

Write a short inclusion rule, an exclusion rule and the evidence expected for every code. Waiting for packaging material should mean the required item is unavailable at the agreed point of use. If the material is present but its identity is disputed, use the quality or identification review category chosen by the site.

Give the code an owner and effective date. The owner resolves ambiguous examples and controls revisions. Keep a free-text observation field for unusual conditions, but review recurring entries and decide whether they justify a new code. An expanding list of near synonyms makes selection slower and destroys comparison.

Record parallel work without double-counting time

Cleaning, tooling and material preparation may proceed together. Their labour durations can add to more than the elapsed changeover. Store activity intervals independently, then identify the work that actually held back the production restart. Adding every activity duration as lost line time creates a misleading result.

Use an agreed rule for overlapping delays. The line timeline needs one consistent classification for each reporting interval, while the investigation can retain several contributing observations. Document the precedence rule and test it on a real sequence with the shift team before using it in a comparison between crews.

Keep machine signals and human explanations linked

A stop signal can establish that a machine was inactive under the accepted mapping. It cannot normally explain that a label roll was missing or that a supervisor was checking clearance. Link the signal interval to the operator explanation using the line identity and timestamp, preserving both records.

Where an explanation arrives later, retain the original unclassified interval and the amendment time. An unanswered reason should remain visibly unclassified. Automatically assigning every unexplained interval to operator delay creates apparent certainty and encourages the team to distrust the reporting process.

Test the dictionary against difficult events

Walk through a change that crosses a shift boundary, a cancelled order and a trial that returns to setup. Include a change where the downstream station holds the line while upstream equipment is ready. These examples expose whether the dictionary describes the actual operating sequence.

Ask two trained reviewers to code the same recorded event independently. Discuss disagreements and improve the definitions. The objective is a repeatable interpretation, not a large catalogue. Retain the disputed examples as training material with the approved resolution and the version that introduced it.

Build comparisons from comparable changes

Keep previous product, next product, packaging format, crew and relevant machine configuration with the change record. A label-only change and a washdown plus format change have different work content. Compare matched families before interpreting a longer duration as weaker execution.

Separate preparation completed while the line was producing from work performed during the stopped interval. An improvement that moves preparation outside the stop can reduce elapsed loss even when total labour stays similar. The record should reveal that mechanism rather than implying that the necessary work disappeared.

Use the review to assign a practical action

Rank repeat delays using their verified elapsed contribution and frequency. Inspect a few underlying events before choosing an action. A frequent stores code may reflect an incorrect picking list, a late order change or an unclear delivery location; each requires a different owner and correction.

After the change, repeat the same measurement boundary and product grouping. Preserve dictionary versions so a coding change is not mistaken for a production improvement. Close the action with observed evidence, remaining uncertainty and the next review date. This turns the dictionary into a maintained operating tool rather than a dashboard label exercise.

Connect the decision to the project

Use Packaging lines, Shop floor data collection to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.

Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.

Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.

Sources and method

Vorne’s OEE calculation guidance supplies production-time context. This dictionary is an engineering method and contains no customer performance results.

Frequently asked questions