What happens in the plant
- Changeover time is estimated instead of measured by event
- Waiting time during setup is not separated from actual work time
- First-good-piece delays are not captured clearly
- Repeated setup issues are discussed without line, product, or tooling context
- Changeover actions are not assigned before the next similar run
Why it matters
Changeover loss often looks like normal schedule time until it is measured by step, delay reason, and first-good-piece outcome. Without that structure, teams cannot separate unavoidable setup time from waiting, missing tools, unclear approvals, quality release delays, or repeated adjustment problems.
What teams need to see
Teams need to see setup start, setup end, first-good-piece time, product change, tooling status, waiting reason, quality release status, owner, and recurring delay patterns.
Decisions this problem affects
- Which changeover step creates the most repeat delay?
- Which product or line change needs setup standardization?
- Which missing tool, material, or approval blocks first good piece?
- Which owner should correct the repeated setup issue?
- Which changeover should be reviewed before the next run?