How to Remove a Setup Matrix Entry in EDGEBIC

To remove a setup matrix entry in EDGEBIC by User Solutions, open the setup matrix editor for the work center, use the remove control on the cell's row, and click save. The removal is staged in the grid until the save goes through, so you can undo a mistake by closing without saving. What matters more than the click is knowing what the scheduler charges once the cell is gone.

A changeover matrix is only useful while it matches the floor, so removing entries is part of keeping it honest. This page covers the task and the fallback behavior that makes a careless removal expensive.

Before You Start

• Know which cell is wrong and why. A wrong number should usually be edited, not removed. Removal is for cells that should not exist at all.
• Know which work center. The matrix belongs to the machine. The dialog has no work center selector inside it, because a paint booth's changeover physics say nothing about a welder.
• Know the fallback. With no matrix cell for a pair, the setup time comes from the routing step, then the work center default.
• Save your other edits first if you have unsaved changes in the editor, so a removal you are unsure about can be abandoned cleanly.

Step 1: Open the Setup Matrix Editor

On the Workcenter tab, click the ⚙ button in the actions column of the work center's row, tooltip Sequence-dependent setup matrix (A1). The Sequence-Dependent Setup Matrix dialog opens, headed with the work center's name.

The dialog carries four tabs: Family Matrix, Product Overrides, Families, and Product Families, with Export CSV, Save, and Close in the footer.

Step 2: Find the Cell

Changeover cells live on two tabs, and which one you want depends on how the cell was created.

Both are flat lists of from and to rows rather than a pivot grid, so scanning down the from column finds the row quickly.

Step 3: Decide Between Editing and Removing

Stop for a second before you remove anything, because the two actions do very different things:

• The number is wrong. Edit the Setup (min) value in place. The pair keeps a pair-specific answer.
• The pair does not exist on this machine. Remove the row. Nothing is lost, because the pair never runs.
• The changeover genuinely costs nothing. Enter 0. Zero is valid and it means what it says. Removing the row instead makes the pair fall back to a flat default, which is a different and usually worse answer.
• The override is no longer an exception. Remove the product override so the pair returns to its family rule, which is where it should have been all along.

Step 4: Remove the Row

Use the per-row Remove control on the cell you want gone. The row disappears from the grid, but the change is staged: nothing has been written yet.

Remove any other cells in the same pass. Working through a whole tab in one session is safer than repeated open, remove, save cycles.

Step 5: Save

Click Save in the footer.

If you close the dialog with edits still pending, you are prompted first: unsaved setup matrix changes, close without saving. Answering yes discards the removals, which is the escape hatch when you change your mind halfway.

How to Check It Worked

1. The row is gone from the tab after reopening the editor. Reopening is the real proof, because it reads the saved state rather than the staged grid.
2. The remaining rows still cover the pairs you run. Walk the from and to combinations that happen on the floor and confirm each still has an answer.
3. Export the matrix and read it. The export writes type, from, to, minutes, and notes, which is the fastest way to review a matrix as a whole.
4. Run a schedule across the boundary. Sequence two jobs that cross the affected pair and confirm the setup hours booked on that machine match what you expect.

Common Mistakes

Removing a cell to "reset" a wrong number. There is no reset. The pair drops to a flat default that is almost never the number you wanted.

Removing zero-minute cells for tidiness. A zero cell is doing real work: it tells the scheduler this swap is free, which is exactly what lets it group compatible jobs together. Deleting it invents a changeover cost that does not exist.

Removing a product override without checking the family underneath. If the products involved have no family assigned, there is nothing underneath to catch them, and the pair falls all the way to a flat step or work center setup time.

Assuming a removal on one machine applies everywhere. Cells belong to the work center you opened the editor from. The same product pair may need its own answer on each machine that runs it.

Forgetting the notes. A cell with 240 minutes and no note gets questioned every quarter. A cell with 240 minutes and a note reading full solvent flush and color match gets left alone.

Next Steps

If the whole grouping is being retired rather than one cell, how to delete a setup family in EDGEBIC covers the wider job, including the products that have to move first. To rebuild a matrix from scratch on a new machine, how to build a setup matrix in EDGEBIC walks the full sequence. More task guides live on the EDGEBIC how-to hub, and the EDGEBIC product page shows where changeover modeling fits the scheduling engine.