A manufacturing changeover process can quietly take capacity away from your schedule. Each switch from one product, batch, or SKU to the next uses time that cannot produce saleable goods. When those minutes add up across a week or month, you may see delayed orders, overtime, and a production plan that looks achievable on paper but falls behind on the floor.
At Kodershop, we help manufacturers connect the information behind these production gaps. The question is simple: how much time do you lose between runs, and can your team see the difference between planned changeover time and what happened?
Every Minute Between Runs Affects Capacity
The changeover process includes all activities needed to move a work centre, line, machine, or team from one production run to another. It the current run is cleared and ends when the next run is producing stable, acceptable output.
This matters as Canadian manufacturers prepare for autumn demand, customer commitments, and budget discussions. Demand can shift quickly. Customer-specific work, supply delays, limited labour, and shorter runs can all mean more product changes during a shift.
A line may look busy all day, yet still produce fewer units than scheduled because time is being spent between runs. When changeover time is treated as a fixed and unavoidable cost, its effect on capacity can remain hidden until delivery dates start to slip.
Where Hidden Changeover Losses Build Up
A changeover often includes more work than the schedule shows. Before stable production can resume, teams may need to complete several steps:
- Clear materials, finished goods, and packaging from the previous run
- Clean equipment and prepare the work area
- Change tools, fixtures, settings, components, or labels
- Complete first-piece inspections and quality checks
- Wait for materials, maintenance support, labour, instructions, or approval
Any one of these activities may be expected. The problem begins when the real time needed is longer than the planned time, or when waiting time is not recorded at all.
For example, setup may be complete, but production can still be delayed by a missing component or a supervisor approval. A machine may restart, but adjustments and first-piece checks can postpone stable output. These losses are easy to dismiss as isolated events when they are only captured in shift notes or verbal handoffs.
Over time, longer changeovers reduce throughput and constrain work-centre capacity. Planners may respond by adding larger schedule buffers, while production teams may rely on overtime or rushed recovery work. Not every changeover can or should be eliminated. Our goal should be to separate expected work from recurring loss, while protecting quality, safety, and traceability.
Why Fragmented Records Hide Actual Time
Many manufacturers already have planned setup or operation times somewhere in their business. They may exist in routings, scheduling boards, spreadsheets, paper logs, or the knowledge held by experienced operators. The difficulty is that actual time is often recorded somewhere else, if it is recorded consistently at all.
An operator might log when production resumed but not when cleanup started. A maintenance interruption may be noted separately from the affected work order. Different shifts may use different meanings for setup, downtime, adjustment, and waiting. That makes a reliable comparison difficult.
A measurable changeover process needs shared definitions and connected production records, not simply more manual reporting. Without that connection, recurring delays can look like one-off problems. Scheduling teams keep using old assumptions, while operations leaders lack clear evidence about whether the cause is product complexity, material readiness, staffing, equipment performance, or a work-centre constraint.
Connect Odoo Manufacturing Data to Planned and Actual Time
Odoo manufacturing can provide a connected view of the records that surround a changeover. It is not an automatic fix for poor processes, but it gives your team a stronger basis for finding and discussing the gap between plan and reality.
Planned operation duration in Odoo routings provides a working benchmark. You can define expected operation times based on production requirements, work-centre capacity, and efficiency. Once a work order is executed, your team can compare the planned duration with actual logged Work Order time and Real Duration. A repeated gap can show that a changeover-related operation is taking longer than the routing assumes.
Odoo’s official documentation describes the Work Orders tablet view and Shop Floor app as tools for following assigned work and recording progress in the context of specific work orders. That context matters. Rather than leaving timing details in a disconnected note, the record can be associated with the order, operation, and work centre involved.
The Work Center form also includes an OEE Smart button. According to Odoo documentation, it gives teams a way to review overall equipment effectiveness information. Used with planned and actual work-order duration, this view can help your team ask a better question: is lost time linked to extended changeovers, or is it part of a broader availability, performance, or quality issue at the work centre?
Measure Losses Before Autumn Demand Arrives
Before fall production pressure builds, we recommend reviewing the metrics that turn changeover concerns into operational priorities. Start with a clear facility-wide definition of changeover time, such as the period from the end of one stable production run to the start of the next stable run.
The most useful measures usually include:
- Changeover time, tracked by product, work centre, shift, or sequence
- Lost production time, or the productive minutes and units missed when a restart runs late
- Work-centre utilization, showing whether constrained equipment sits unavailable between runs
- OEE, placing changeover loss within the wider picture of availability, performance, and quality
- Duration variance, comparing planned operation duration with actual Work Order time or Real Duration
Lost production time creates a direct link between a shop-floor delay and its business effect. It helps your team see when a late restart may lead to missed capacity, overtime, reduced margin, or a late order. Duration variance is equally useful because it can reveal repeatable gaps that may otherwise be absorbed into the normal pace of production.
Use Visibility to Build Better Schedules
SMED, or Single-Minute Exchange of Die, is a widely used approach for reducing changeover time. Its central idea is practical: separate work that can happen while equipment is still running from work that requires the equipment to stop, then simplify and standardize the remaining stopped-time activities.
ERP visibility supports that improvement work. With connected routing, work-order, work-centre, and OEE information, your team can identify the products, shifts, work centres, and production sequences with the biggest planned-versus-actual gaps. This is especially important when you have frequent product changes, many SKUs, short runs, make-to-order work, volatile demand, limited labour, or highly utilized equipment.
A reliable view of actual changeover performance gives planners better assumptions to work with. By investigating the largest recurring variances and updating schedules based on operational evidence, you can protect capacity before lost time becomes a delivery problem.
Turn Changeover Data Into Confident Production Decisions
Kodershop helps manufacturers connect shop-floor performance with planning through Odoo manufacturing solutions built around operational visibility. We can help your team identify where changeover information is fragmented and create a clearer basis for capacity decisions. To discuss your manufacturing requirements, contact us and speak with our team.