Blog
Insights on production scheduling, lean manufacturing, and manufacturing software from 35+ years of industry experience.
Everything we have published.
Cleaning Your Data Before Importing to EDGEBIC
Clean your data before importing to EDGEBIC and the migration goes smoothly: fix name drift, fill required fields, and reconcile capacity, because the import surfaces every gap as a broken link or a wrong date.
Completing the Cutover to EDGEBIC
Complete the cutover to EDGEBIC on the trust signal, not a deadline: let short jobs drain on RMDB, import new work clean, and make EDGEBIC the system of record when it has earned it.
Exporting Your RMDB or EDGEBI Data to Excel for EDGEBIC
Exporting RMDB data to Excel is the whole first step of an EDGEBIC migration. Send each entity out, map the columns once in an import mask, and re-run the saved mask in one click.
Migrating Open Jobs and Their Actuals to EDGEBIC
The cleanest way to migrate open jobs to EDGEBIC is to let in-flight work finish on RMDB and start new jobs on EDGEBIC. When you must carry WIP across, actuals import and completed work is preserved.
Migrating Your Work Center and Shift Definitions to EDGEBIC
Migrate work centers, shifts, and plant holidays to EDGEBIC through import masks, attach per-work-center calendars, and verify capacity against RMDB before you trust a schedule.
Migrating Your Item and Customer Master to EDGEBIC
Migrate your item and customer master to EDGEBIC first, through saved import masks, because routings and orders link to them by name. Get the foundation right and the rest resolves cleanly.
Preparing Your EDGEBIC Install Before Migrating
Before migrating, prepare your EDGEBIC install: choose SQLite for a single planner or SQL Server for a team, let the setup wizard handle the connection, and confirm the data source before you import.
The Order to Import Your Data Into EDGEBIC
Import your data into EDGEBIC in dependency order: products and work centers first, then routings, then orders. References link by name, so the thing pointed at must exist before the pointer.
Validating a Migrated Schedule Against RMDB
Validate a migrated schedule by comparing EDGEBIC's dates against RMDB job by job. Verify capacity first, then treat every difference as a modeling detail to reconcile, not a failure.
What You Do Not Need to Migrate to EDGEBIC
Half of a smooth EDGEBIC migration is knowing what to leave behind: schedules regenerate, dormant items stay put, and closed history stays in RMDB. Migrate the master data and open demand only.
From Excel and RMX to EDGEBIC: The Growth Path
Outgrown scheduling in Excel or Resource Manager for Excel? EDGEBIC imports the spreadsheets you already keep, so the move up is your data mapped once, not a rebuild.
Moving Your RMDB Routings Into EDGEBIC
Move your Resource Manager DB routings into EDGEBIC through import masks. Export to Excel, map columns once, and let the two-pass routing import wire step sequences for you.