How to Export a Routing to Excel in EDGEBIC

To export a routing to Excel in EDGEBIC by User Solutions, open the routing, switch to data grid mode, and click Export on the routing toolbar. The workbook that lands is a faithful picture of the grid on screen: the same columns, the same sort, the same filter, plus a legend block at the top explaining the markers. It is built for reading and review, not for loading data back in.

Routings get reviewed by people who never open the scheduler. A process engineer wants to check hours per piece, a quality lead wants the step sequence, a customer wants evidence of a documented process. The export exists for those conversations. This page covers the task and the two traps that make a workbook say less than you meant it to.

Before You Start

• You know which product's routing you want. The export covers one routing at a time.
• The grid shows what you want the reader to see. Sorting, filtering, and column visibility all carry through to the file, so arrange the grid first.
• You have somewhere sensible to save it. The dialog suggests a name; you choose the location.
• You understand this is a snapshot. Nothing in the workbook stays linked to the routing. Change a step tomorrow and yesterday's file is simply out of date.

Step 1: Open the Routing

Open the BOR tab and select the product's routing in the selector at the top. If you are not sure how the routing was built in the first place, how to build a routing step by step in EDGEBIC walks the same grid from an empty list.

Step 2: Switch to Data Grid Mode

The toolbar carries a pair of view toggles: Data Grid and Designer. Click Data Grid.

The export snapshots the grid, so it needs the grid on screen. Click export while the diagram is showing and the application answers plainly: switch to the data grid view first, then export. That is a prompt, not an error, and nothing is lost by switching.

Step 3: Arrange the Grid the Way You Want It Read

This is the step people skip, and it is the one that decides what the reader gets.

The export writes the columns and rows exactly as shown, in the grid's current sort and filter order. So:

• Clear any filter unless you deliberately want a partial routing.
• Show the columns the reader needs. A hidden setup-time column produces a workbook with no setup times in it.
• Sort by sequence if the reader expects the routing in running order.

Count the rows on screen and remember the number. You will check it against the workbook in a moment.

Step 4: Click Export

Click Export (📤) on the routing toolbar. Its tooltip states the contract directly: the columns and rows exactly as shown, in the grid's current sort and filter order.

Step 5: Name and Save the File

The Export BOR to Excel dialog opens with a suggested file name built from the product and a timestamp, in the pattern BOR_<Product>_<timestamp>.xlsx. Accept it or type your own, then save.

Keep the product name in the file name. Routing exports pile up quickly, and a folder of files called export1.xlsx helps nobody three months later.

Step 6: Open the Workbook

An Export complete prompt appears offering to open the file now. Click Yes.

The workbook opens with a legend block above the data. That block is part of the export by design, because the grid uses visual shorthand that plain cells cannot carry: color swatches, glyph meanings, and an explanation of what the N/A cells mean. Below the legend sit the step rows, with child rows tinted the way they are on screen, and the star and parallel-child markers rebuilt as text so a spreadsheet reader can still see which step is which.

How to Check It Worked

1. Count the rows. The step count in the workbook should match the count you noted in step 3. If it is short, a filter was still applied.
2. Check the legend is there. It should sit above the first data row. It is what makes the markers readable to somebody who has never used the application.
3. Look at a material row. Material steps show N/A in the columns that only apply to machine steps. That is correct, and the legend says so.
4. Spot-check one step against the grid. Hours required, setup time, and the next-in-sequence value should match cell for cell.

Common Mistakes

Exporting from diagram mode and reading the message as a failure. It is an instruction. Switch to the data grid and click export again.

Treating the workbook as an import template. It is not one, and the legend rows alone would break a load. When the goal is to get routings into the system from a spreadsheet, use the import function and a mask instead. How to import a routing from Excel in EDGEBIC covers that path.

Exporting with a filter you forgot about. The file looks complete because nothing marks the missing rows. Always clear filters before an export that leaves the building.

Hiding columns for your own comfort, then exporting for someone else. Your working view is rarely the reviewing view. Restore the columns first.

Assuming the file updates. It never does. Re-export after every meaningful routing change, and date the file name so the newest one is obvious.

Next Steps

An export is a good habit before any irreversible routing action, especially resetting a job's own routing copy back to the standard, which cannot be undone. If you are heading in the other direction and want the diagram rather than the grid, how to build a routing as a flow chart in EDGEBIC shows what the same routing looks like as nodes and connectors. More task guides live on the EDGEBIC how-to hub, and the EDGEBIC product page shows where routings sit in the wider platform.