You sequence tomorrow's runs by batch size and delivery order.
Whether that costs 3 hours or 9 hours in changeovers — you won't know until you're in it.
Changeover time matrix
Every product switch has a cost. Now you can see it before you commit.
Every line has fast switches and expensive ones. Most plants learn which is which after the clock starts — by instinct, batch size, or who's in the room. Cost shows up in OEE.
Three scheduling decisions made without the data
Same gap each time: no view of changeover cost before the commitment.
REF-31D to REF-55E starts. The line stops.
Three hours in, you realise this is the worst pair on the line. The schedule can't move.
You learn which pairs are expensive over months of runs.
Nobody records it. The same sequence gets scheduled again next week.
A bad sequence costs real time. You just can't see it until you've committed.
Every product pair, ranked before you run any of them.
ProChangeover computes planned changeover time for every product pair from your task structure. One view. Colour-coded green (cheapest) to red (most expensive). Products grouped by category.
Not entered by hand. Add a task, change a duration, restructure a changeover — it recalculates. Open from the line screen. No separate planning tool. No version drift.
The data was always in your task structure. Now it's usable before you commit.
Three things the matrix tells you at a glance
You don't need every cell. Three observations are enough to sequence better.
01
Pick the cheapest landing spot before the schedule locks
Greenest column = product your line reaches cheapest from anywhere. End a long run there — or start the day with it.
02
Know which pairs to avoid before they're committed
Reddest row = product your line leaves most expensively. Spot it before the schedule locks — move it to the end or avoid back-to-back.
03
Always have a cheaper next move ready
For any product running, the row shows every option and its cost. Batch finishes early? Matrix picks the cheapest next run.
4 hours 48 minutes saved. Same products. Different order.
Same five products. Only the order changes — batch size vs. changeover time matrix.
Before — by batch size
REF-12A
145 min
145
REF-55E
160 min
160
REF-16C
110 min
110
REF-31D
85 min
85
REF-14B
Total changeover time
8 h 20 min
After — matrix-guided
REF-12A
22 min
22
REF-14B
30 min
30
REF-16C
110 min
110
REF-31D
50 min
50
REF-55E
Total changeover time
3 h 32 min
Who uses the changeover time matrix
Production planner
See which sequence costs least before locking the day. Adjust run order in 30 seconds if a cheaper path exists.
Process engineer
Spot expensive pairs and focus standardisation there. A 20-minute cut on a red cell pays back every time that pair runs.
Shift supervisor
Check the day's run order against the matrix before the first changeover. Catch a bad sequence while you can still change it.
Common questions
Related
Changeover configuration & standards
Task structure that drives the matrix — sequences, durations, roles per product pair.
Post-run analytics & changeover performance
After the sequence: did the matrix prediction hold, and where did time go?
OEE changeover: why availability is the easiest win to close
How changeover overruns hit OEE availability — and what sequencing has to do with it.
After your first run
Stop choosing the next product by instinct.
Matrix computed from your task structure. Line config changes — matrix updates with it.
-
Timestamped sign-off
Audit-ready from run one
-
Gantt of every task
See where time was lost
-
A repeatable standard
Not tied to who showed up
7-day free trial · Self-serve · No IT project