Moving Your RMDB Routings Into EDGEBIC

You move your Resource Manager DB routings into EDGEBIC by exporting them to Excel or CSV and importing them through a routing import mask, which maps your columns once and wires the step sequences automatically. In EDGEBIC by User Solutions, there is no hand-rebuilding of routings you already have. The import mask remembers your column mapping, and the two-pass routing import reads every row before connecting steps, so operations come in correctly sequenced. RMDB stays untouched and fully supported throughout, so the move is additive, not a cutover.

The routing is your most valuable data, so treat it that way

Routings are the accumulated knowledge of how your shop actually makes things: which operations, on which work centers, in what order, at what setup and run times. In RMDB you built that up over years. The last thing a migration should ask is that you type it all again.

EDGEBIC does not. It inherits the same import-export approach the User Solutions product line has always used, so your routings move across as data, not as a rebuild project. RMDB, the proven classic of the line, keeps running as your system of record while EDGEBIC picks up the imported routings, which is why the move can be gradual rather than a risky all-at-once switch. The full upgrade path is laid out on the RMDB to EDGEBIC guide.

The mechanism: export, map once, import

The migration has three moves.

Export from RMDB. Send your routings out to Excel or CSV in whatever layout you already use. There is no required format; the mask adapts to your columns, not the other way around.

Map the columns once. In EDGEBIC, build a routing import mask that maps your source columns to the target fields: product, operation sequence number, work center, setup time, run time per unit, and any queue or move times you track. This mapping is the real work, and you do it a single time. The mask is saved, so re-running it later is one click. The general mechanics of building and saving a mask are covered in EDGEBIC import masks explained.

Import. Run the mask. The rows come in as EDGEBIC routings, connected and ready to schedule.

Why the import runs in two passes

Routing import is not a simple row-by-row load, because a step's successor may sit anywhere in the file. Step 30 might appear before step 20; a sub-assembly's operations might be listed after the parent references them. A naive single-pass import would try to link a step to a successor it has not read yet and fail.

EDGEBIC solves this with a two-pass import. The first pass reads every routing row and creates the steps. The second pass walks the steps and wires each one to its next-in-sequence using the sequence data you mapped. Because everything is in memory before any linking happens, row order in the source file is irrelevant. Your routings come in correctly connected, not out of order. The mechanism is described in detail in how EDGEBIC imports routings in two passes.

A worked example

A shop has 300 routings in RMDB. The steps are stored with a product code, an operation sequence, a work-center name, a setup time, and a run time per piece.

1. Export. The planner exports all 300 routings to one Excel file, routings.xlsx, 4,100 rows across the 300 products.
2. Map once. In EDGEBIC, they build a routing import mask: Item maps to product, OpSeq to sequence, WC to work center, SetupHrs to setup time, RunPerPc to run time per unit. They save the mask as "RMDB Routings."
3. Import. They run the mask. Pass one reads all 4,100 rows and creates the steps. Pass two links each step to its successor by OpSeq within each product. All 300 routings arrive connected.
4. Spot-check. They open a handful of routings in the graphical designer to confirm the sequences look right, then run a scheduling pass on one product family.

The 300 routings became one export, one mapping, and one import. The saved mask means the next export, after a data cleanup, re-imports in a click.

Sub-assemblies come across too

If a product's routing references a sub-assembly, import the sub-assembly products and their routings as well. EDGEBIC treats a step whose product resolves to its own routing as a sub-assembly, and rolls that sub-assembly's hours, labor, and material up when it schedules and quotes the parent. Bring the whole tree across and the rollup works the way you expect; leave a sub-assembly out and its parent will under-report work.

After the import: the routing is now visual

Once imported, a routing is a first-class EDGEBIC routing, which means you can open it in the drag-and-drop graphical designer. Every operation is a node and every dependency is an arrow, so you can lay out, annotate, and later reschedule the routing as a flow chart. Nothing forces you to redesign an imported routing, but the option is there the moment it lands, which is one of the things EDGEBI users gain in EDGEBIC.

Common pitfalls

A few things to watch on a routing import:

• Blank cells can overwrite values. A blank in a mapped column may clear the target field rather than leave it alone, depending on the mask setup. Check the mask's handling of empty cells before a large import.
• Work-center names must match. Steps link to work centers by name, so import your work centers first and keep the names consistent between the two files.
• Sub-assembly products need their own routings. A referenced sub-assembly with no routing contributes only material, not work hours. Import the sub-assembly routings too.
• Verify capacity after import. Set shifts, holidays, and per-work-center calendars, then check the capacity numbers against what RMDB showed before you trust a schedule.

The takeaway

Moving RMDB routings into EDGEBIC is an export, a one-time column mapping, and an import, not a rebuild. The two-pass routing import wires step sequences automatically regardless of row order, sub-assemblies roll up when you bring the whole tree, and every imported routing is instantly available in the graphical designer. RMDB stays untouched and supported, so you migrate on your own timeline. Start with the RMDB to EDGEBIC upgrade guide for the full path, or see the platform in full on the EDGEBIC overview. When you are ready, the next step is often to run RMDB and EDGEBIC side by side on one cell.