How to Add a Product-Level Setup Override in EDGEBIC

A product-level setup override in EDGEBIC by User Solutions is a setup matrix cell for one specific from-product to to-product pair on a work center, used when that pair breaks its family rule, and it always wins over the family cell. It is how you handle the odd changeover that costs more than its family suggests, without complicating the family matrix that handles everything else. Add it when one pair genuinely needs its own number.

Overrides sit on top of the family matrix, so if you have not built that yet, start with how to set up sequence-dependent setup times. This page is the exception mechanism, one of many tasks mapped on the EDGEBIC how-to hub.

Before You Start

• The work center is saved and its Setup-Matrix editor opens. The matrix is keyed to a saved machine.
• Both products in the pair exist. An override references two real products by name.
• You know the true minutes for this direction. An override is directional, so measure the pair you are actually capturing.

Step 1: Open the Product Overrides Tab

Open the Workcenter tab, and on the machine's row click the gear button in the Actions column to open the Setup-Matrix editor. You can also open the work center for edit and use the Setup Matrix tab, then Open Setup-Matrix Editor.

The dialog is headed Setup Matrix followed by the work center name. Select the Product Overrides tab. It is a flat list of product-to-product cells, separate from the family matrix, with a per-row Remove.

Step 2: Add the Override Cell

1. Click Add cell.
2. Pick the From product and the To product. The order matters, because the override is directional: Red to Black is a different cell from Black to Red.
3. Enter the changeover in Setup (min), in minutes. A 90-minute solvent flush goes in as 90.
4. Type an explanatory Notes value, such as extra flush for red residue, so the next planner understands why the pair is special.
5. Click Save.

Zero is a valid value for a pair that truly needs no changeover. Negatives are rejected.

Step 3: Understand the Resolution Order

When the scheduler places an operation, it looks at what the machine ran last and resolves the setup down a ladder, first match wins:

A product override at priority 1 always beats the family cell at priority 2 for exactly that pair. The family matrix is never consulted when a product cell matches, which is what lets one exception change one changeover while everything else follows the family rule.

What Changes When You Save

Saving the override changes no schedule by itself. The next Drive Schedule run, and every quote simulation, resolves setups through the new cell, while existing bars keep the times they were planned with until then. Completed operations never change: on a reschedule, finished steps keep their historical setup, and only remaining work is re-resolved against the product that actually ran last.

Because a product override is the most specific rule, it is also the easiest to forget. Note why each one exists, and revisit them when a solvent, tooling, or process change makes the exception no longer true.

How to Check It Worked

Run Drive Schedule, then open Job View and show the Setup Reason column. The pair you overrode reads Matrix (product). A different pair in the same families still reads Matrix (family), which proves the override is scoped to exactly the one pair and not leaking into its neighbors. If the overrode pair still reads Matrix (family), the cell did not match, so check the machine and the direction.

Common Mistakes

• Reversing the direction. Overrides are directional. From Red to Black is not the same cell as Black to Red.
• Editing the wrong machine. The dialog header names the work center; the override only applies there.
• Overusing overrides. Many overrides mean the families are wrong. Regroup the products instead of piling on exceptions.
• Mixing minutes and hours. The matrix is minutes; the flat routing and work center fields are hours.

Next Steps

For the flat, non-sequenced setup on a routing step, see how to add setup time to a routing step. See how sequence-aware setup fits the wider engine on the EDGEBIC product page.