Training Your RMDB Team on the EDGEBIC Engine

Training an experienced RMDB team on EDGEBIC is fast because the scheduling model carries over: you teach the new interface and the few new capabilities, not scheduling itself. EDGEBIC by User Solutions is the next-generation successor to RMDB, EDGEBI, and RMX, so your schedulers' hard-won judgment about finite capacity, routings, and due-date scheduling transfers directly. The training job is narrow and mostly about vocabulary and location, with a short list of genuinely new features to add on top. Do it during a pilot, on real jobs, and it sticks.

Start from what they already know

The temptation is to run RMDB veterans through a full scheduling course. Do not. They already understand finite capacity scheduling, routings, work centers, and forward and backward passes. Retraining that insults their expertise and wastes their time. EDGEBIC uses the same model, so their mental picture of a good schedule is already correct.

The right opening move is to have the team list the RMDB features they use every day. Then walk each item to its EDGEBIC equivalent using the feature-parity map. This does two things at once: it shows the team their knowledge carrying forward, and it gives you the exact list of screens to train on. You are training on their actual workflow, not a generic curriculum.

The three things that actually changed

For an RMDB team, the entire training scope fits in three buckets.

Where things live. The interface is new, so a feature the team knows may sit in a different place. This is location training, not concept training. A short walkthrough of the main screens (master data, the schedule board, the job view) covers most of it.

What things are called. A few terms changed. A scheduler who cannot find a feature is usually looking for the old word. Keep the terminology crosswalk open during training so "I cannot find X" gets answered in seconds. Vocabulary is the single biggest source of early friction, and it is trivial to remove.

What is new. This is the only genuinely new learning: the optimizer, work center groups, operator skills, and the shop-floor kiosk with actuals. Teach these last, after the team is comfortable that their familiar workflow survived. Introduced too early, they feel like the system is unfamiliar; introduced after parity is proven, they feel like a bonus.

Train on the pilot, not in a classroom

The most effective training is not a slide deck. It is scheduling one real cell in EDGEBIC and reconciling the result against RMDB. This one-cell pilot doubles as hands-on training because the team learns the interface while proving the migration on jobs they recognize.

The reconciliation step is where the learning locks in. When a scheduler explains why a date differs, they are exercising the interface and confirming they understand the engine at the same time. A difference is nearly always a data gap, a missing setup time or a skipped routing step, which teaches the team exactly what clean data means for the engine. Classroom training on a demo dataset cannot do this, because the numbers mean nothing to the trainee.

A practical training sequence

A workable order for a team of a few schedulers:

1. Parity walkthrough (half a day). Team lists daily RMDB features; you map each to EDGEBIC. Output is the screen list to train on and confidence that nothing was lost.
2. Interface tour on the pilot cell (half a day). Master data, schedule board, job view, using the pilot's real work centers and routings.
3. Schedule and reconcile the pilot cell (one to two days). The team drives; you coach. Every difference against RMDB gets explained.
4. New capabilities (half a day, later). Optimizer, work center groups, operator skills, kiosk actuals, introduced only after parity is proven.
5. Expand and repeat (ongoing). Each new cell reinforces the interface with less coaching.

This is deliberately front-loaded on proving parity and back-loaded on new features, which matches how a skeptical veteran team builds trust.

Mind the mixed team

Veterans and junior planners train differently. A veteran unlearns RMDB screen locations; a junior planner has no old habits and learns EDGEBIC fresh. Pair them during the pilot: the veteran judges whether a schedule is right, the junior drives the new interface. By cutover you have two people who know the system for different reasons, which is more resilient than depending on one expert. For the junior, teach concepts first using the production scheduling primer; for veterans, teach only the deltas.

What not to over-train

Do not drill the team on every new capability before cutover. Work center groups, operator skills, and the optimizer are real, shipped features, but a shop does not need all of them on day one. Get the familiar workflow running first, cut over, then adopt the new capabilities one at a time as each earns its place. Training everything at once buries the simple truth that most of their RMDB knowledge already works.

The takeaway

To train an RMDB team on EDGEBIC, start from what they already know, teach only the three deltas (where features live, what changed names, and what is new), and do it hands-on during a one-cell pilot that reconciles against RMDB. Introduce the optimizer, work center groups, and operator skills after parity is proven, not before. See the platform on the EDGEBIC overview, read the upgrade path on the RMDB to EDGEBIC guide, and pair training with planning an EDGEBIC pilot on one cell.