A setup matrix entry is one cell of the product-level changeover table: the setup time, in minutes, that a specific work center needs when it switches from one specific product to another. It is the sharpest setup rule available and it wins over every more general rule, which makes it the right tool for exceptions and the wrong tool for describing an entire product range. EDGEBIC by User Solutions resolves setup through a chain that checks these entries first, so a single problem changeover can be corrected without disturbing anything else.
How it works
Setup time on many machines is not a fixed number, it depends on what ran before. A paint booth changing from one shade of white to another may need five minutes. The same booth going from black back to white may need four hours of flushing and color matching. Modeling that with a single flat setup figure per step means either dramatically over-scheduling the easy changeovers or dramatically under-scheduling the hard ones. Sequence-dependent setup exists to solve this, and the matrix entry is its unit.
Each entry names four things: the work center, the from-product, the to-product, and the minutes. It is directional, which is the part most often missed. Black to white and white to black are two independent cells and will very often carry very different times, because the physics of the changeover is not symmetric.
Entries are also per work center, because two machines that make the same parts do not necessarily change over the same way. An older booth with a manual flush and a newer one with an automatic cycle deserve different numbers even for the identical product pair.
The trade-off is scale. Product-level cells are exact and they multiply badly: a hundred products means a theoretical table of thousands, and nobody maintains that. This is why the product level is not meant to stand alone. Products are grouped into setup families that share changeover behavior, and the family-level table carries the general rule in a compact form. The product-level entry then exists for the specific pairs where the family rule is genuinely wrong.
That layering is what the resolution order enforces. A product-level entry is checked first. If none matches, the family table applies. If neither applies, the step's own flat setup time is used, and failing that the work center's default. The first match wins outright, and the step records which tier produced the number so it can be traced later.
A concrete example
Picture the laminated changeover card taped up at the spray booth. Most of it is a small grid of color families: light to light is five minutes, light to dark is thirty, dark to light is ninety. That grid covers almost everything the booth does and fits on one card.
At the bottom of the card there is a short list of exceptions in different ink. "Black gloss to white matte: 240 minutes, full solvent flush and color match, do not use the family time." That short list is the product-level matrix. Four or five lines, each one a specific pair that the family grid gets badly wrong.
An operator setting up a job checks the exception list first, because it is the specific instruction. Nothing there? Use the family grid. Nothing there either? Use the booth's standard changeover. That is precisely the order the scheduling chain walks, and it is why the small exception list is worth maintaining while a full product-by-product grid would not be.
In numbers: a booth running white, then black, then white again has a real changeover cost of thirty minutes plus 240 minutes. Scheduled with a flat thirty-minute default, the plan is three and a half hours short of reality on a single shift, and the whole day drifts from there.
How EDGEBIC uses it
Product-level entries are maintained per work center in the setup matrix, alongside the family table they override. The grouping layer is the companion glossary term setup family, and the tier that actually produced a step's number is reported by setup source.
Building the table is covered in how to build a setup matrix, with the wider picture in the setup matrix explained. What sequence-dependent setup actually does to a plan, including the throughput it can free up, is walked through in how sequence-dependent setup shapes a schedule.
A setup matrix entry is a single honest number in the one place it is needed. Cells that can never apply, negatives, duplicates, self-pairs, and pointers at deleted products or families, are caught by the setup matrix hygiene check. For the wider vocabulary, see the manufacturing glossary, and to see changeovers resolved inside a live plan, explore EDGEBIC.
Expert Q&A: Deep Dive
Q: One changeover on our paint line takes four hours but the schedule only allows thirty minutes. What do I add?
A: That is exactly the case a setup matrix entry exists for. The family rule is presumably covering the general dark-to-light behavior with a modest number, and this one pair, say a specific black gloss to a specific white matte, is a genuine exception because of the solvent flush and color match involved. Add a product-level entry naming those two products on that work center with the real 240 minutes. It will win over the family rule for that pair only, and every other pair in the same two families keeps the family number. You have corrected one cell rather than distorting a rule that is right everywhere else.
Q: I added a product-level entry but the schedule still shows the old time. Where do I look?
A: Check the step's setup source first, because it names which tier actually produced the number. If it reads as a family or default source, your product-level entry is not being matched, and the usual reasons are that it was entered against a different work center than the one the step is routed to, or that the from-product and to-product are the wrong way round. Setup matrix entries are directional: black to white and white to black are two separate cells with two separate times. Also confirm the schedule has been rerun since you added it, because an already-completed step keeps its historical setup and is never recomputed.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.