## Why changeover time needs one agreed definition
In a hatchery, a SKU change can involve chick size, tray format, vaccination recipe, labeling, pack configuration, or customer-specific handling rules. Teams often report different changeover numbers because they start and stop the clock at different points. One operator measures only the time spent changing tooling. Another includes cleaning, line clearance, software recipe loading, and the first quality check. Both figures may be accurate for their local definition, but neither is useful for planning until the boundaries are explicit.
For a comparable hatchery automation changeover time measurement, define the event as:
> From the last accepted unit of the previous SKU to the first accepted unit of the next SKU produced at the agreed settings.
This definition captures the operational delay that affects schedule reliability. It also prevents a line from appearing fast simply because unfinished checks were moved outside the stopwatch window.
Break the changeover into measurable stages
Use the same stage names on every shift. A simple sequence is:
1. Stop and identify: finish the previous order, isolate remaining trays or crates, and record the last-good timestamp.
2. Line clearance: remove product, labels, packaging, vaccine containers, and disposable items that belong to the previous SKU.
3. Clean and inspect: complete the approved cleaning step, inspect contact surfaces, and document any hold points.
4. Mechanical setup: change guides, pockets, grippers, nozzles, belts, sensors, or other format parts that are SKU-specific.
5. Recipe and parameter setup: load the approved program, verify speed limits, and confirm that the displayed values match the work order.
6. Dry run and verification: run empty or with test material to check alignment, sensor response, reject paths, and label position.
7. First-piece release: process a controlled sample, complete the quality checks, and record the first accepted unit.
Recording each stage exposes the true constraint. If mechanical setup takes 12 minutes but first-piece release takes 25 minutes, buying faster tooling will not solve the schedule problem.
Use last-good and first-good timestamps
The changeover clock should use events that can be verified from production records. Recommended fields include:
| Field | What to record |
| --- | --- |
| Previous SKU | Work order or product code that is ending |
| Next SKU | Work order or product code that is starting |
| Last-good time | Timestamp of the last accepted previous-SKU unit |
| Setup start | Time the line is released for changeover |
| First-test time | Time the first test unit enters inspection |
| First-good time | Timestamp of the first accepted next-SKU unit |
| Hold reason | Missing material, cleaning hold, fault, or quality decision |
The primary metric is first-good time - last-good time. Stage durations are supporting metrics. Keep planned waiting separate from avoidable waiting so a scheduled sanitation hold is not confused with an unplanned delay.
Create a SKU changeover matrix
Not every SKU pair requires the same work. Build a matrix with the previous SKU on one axis and the next SKU on the other. Mark each transition as:
- Like-for-like: same tray, guide, and recipe family; only labels or minor settings change.
- Format change: guides, pockets, grippers, or tray handling parts must be changed.
- Process change: vaccination, treatment, inspection, or dosing parameters change.
- Full sanitation change: the line must be cleaned and released before the next product.
Use the matrix to sequence compatible work orders together. A production schedule that reduces unnecessary format changes can often recover more capacity than a faster individual setup.
Design a changeover checklist that can be audited
A checklist should be short enough to use at the machine and specific enough to prove completion. Include:
- Previous SKU material removed and reconciled.
- New SKU work order and approved recipe identified.
- Format parts installed and checked against the parts list.
- Guards, sensors, reject devices, and emergency stops tested.
- Product-contact surfaces cleaned according to the site procedure.
- Labels, cartons, trays, or crates match the new order.
- Trial units inspected against the release criteria.
- Operator and quality sign-off recorded.
Do not use a single signature to represent every step if different people own different checks. A digital record can capture the person, time, and exception reason without adding a long narrative.
Reduce changeover time without weakening control
The safest improvements remove searching and waiting rather than removing verification. Pre-stage approved parts on a labeled cart. Use keyed or color-coded connections where appropriate. Store recipe versions under controlled names. Prepare cleaning tools before the previous order ends, while keeping product segregation intact. Assign a clear owner for the first-piece decision so the line does not wait for an undefined approver.
Review the slowest 20% of changeovers separately. Ask whether the delay came from missing parts, a recurring alarm, an unclear work instruction, a quality hold, or a genuine format limitation. Each cause needs a different countermeasure.
What should be included in an acceptance test?
When commissioning a new line, agree on the changeover test before the site trial. Define the SKU pair, staffing level, material availability, cleaning boundary, number of test cycles, and quality release criteria. Report the median and worst completed cycle, not only the fastest attempt. A useful acceptance record shows the stage times, exceptions, rework, and whether the line returned to stable production after the first-good unit.
FAQ
### What is a reasonable hatchery automation changeover time?
There is no universal number. The target depends on format complexity, sanitation requirements, automation scope, and the release procedure. Use a baseline from your own SKU matrix and improve the largest repeatable losses.
### Should cleaning be included in changeover time?
Include cleaning when it is required between the two SKUs and affects when the next accepted unit can be produced. Report the cleaning stage separately so teams can distinguish sanitation work from mechanical setup.
### How many changeovers should be measured?
Measure enough completed cycles to cover normal operators, shifts, and the main SKU pairs. A single best-case run is not a reliable planning standard.
### Does recipe loading count as changeover work?
Yes, when the line cannot produce the next SKU until the approved recipe is loaded and verified. Record recipe loading and parameter verification as separate stages if they create different delays.
Closing
Consistent definitions turn changeover from a vague complaint into a manageable production metric. By measuring last-good to first-good, separating the stages, and linking each delay to an owner, a hatchery can improve schedule accuracy while preserving line clearance and quality control.
