Mapping RMDB terms to EDGEBIC terms is mostly a matter of recognition, because EDGEBIC inherits RMDB's scheduling model and keeps the core vocabulary intact. In EDGEBIC by User Solutions, resources are work centers, a product's operation sequence is a routing, a job is a manufacturing order, working hours are shifts, and what-if analysis is quote simulation. Finite capacity means exactly what it always did. A short list of new terms appears for capabilities the previous generation did not have. This crosswalk lays out what stays the same and what is genuinely new.
Why most of the vocabulary carries over
EDGEBIC is the next generation of the same product line, built on RMDB's finite capacity foundation. That is why the language your team already speaks mostly transfers unchanged. An upgrade that renamed everything would be a different product wearing the same name; this is the opposite, the same model with a stronger engine on top. The continuity is documented in what carries forward from RMDB to EDGEBIC.
A short note before the tables: RMDB's exact on-screen labels can vary by version and configuration, so treat the left column as the concept you know rather than a guarantee of a specific menu string. The concepts, not the labels, are what carry forward, and they carry forward completely.
The core crosswalk: concepts that stay the same
These are the everyday terms. Each means in EDGEBIC what it meant in RMDB.
| The concept in RMDB | The term in EDGEBIC | What it means |
|---|---|---|
| Resource or machine | Work center | A machine, cell, or station with finite capacity |
| Operation sequence for a product | Routing | The ordered steps a product follows |
| A single step | Operation or routing step | One operation at one work center |
| Job or work order | Manufacturing order | A quantity of a product due by a date |
| Working hours and calendar | Shifts, holidays, downtime | When each work center is available |
| Finite capacity | Finite capacity | The engine never overloads a work center |
| What-if analysis | Quote simulation | A trial schedule to test a promise date |
| Run time and setup time | Run time and setup time | Per-piece and per-changeover durations |
| Due date | Due date | The date the order is promised |
If your team is fluent in the left column, they are already fluent in the right. The finite capacity concept in particular is identical, and it is the heart of both products.
The new crosswalk: terms EDGEBIC adds
The new terms exist because the new engine can do things the previous generation could not. You learn these as you adopt the capability, not all at once.
| New EDGEBIC term | What it is | Why it is new |
|---|---|---|
| Work center group | A pool of interchangeable machines the engine re-shops each run | The engine now picks the best available member per reschedule |
| Operator and skill | Labor as a real constraint, with certifications and rosters | A step can wait for a certified operator instead of assuming one |
| Setup matrix | Sequence-dependent changeover times, from one product to the next | Captures that white to black differs from black to white |
| Anchor scheduling | Theory of Constraints scheduling around the bottleneck | Plans the constraint first, then works outward |
| Backward scheduling | Working back from the due date to a start date | Just-in-time planning as an engine mode |
| Lot streaming | Overlapping operations by transferring partial batches | A downstream step starts before the upstream one finishes |
| Optimizer | A layer that proposes improved plans you accept or discard | Reports a proven optimality gap; never worse than your baseline |
| Kiosk | The shop-floor app for actuals | Operators start, count, and complete work |
Each of these is an addition beside the RMDB vocabulary, never a rename of it. Your planners keep saying work center and routing; they gain the option to say work center group and anchor when they use those features.
How to use this during the move
Keep a one-page crosswalk sheet taped up during the transition. It does two jobs. First, it reassures the team that the words they know still work, which removes most of the fear an upgrade creates. Second, it gives them the small set of new terms in one place, so when a trainer mentions a setup matrix or a work center group, the term already has a home.
When you update process documentation, do it additively. The routing you documented in RMDB terms is still accurate. Where you have adopted a new capability, add the new term next to the old process rather than rewriting it. Nothing in the old documentation becomes wrong; some of it gains a new option beside it. This mirrors the broader principle that the upgrade is continuity rather than replacement.
A worked example
Take a shop that runs a paint line. In RMDB, the planner talks about the paint booth as a resource, the product's steps as its routing, and the changeover as setup time. Every one of those terms is unchanged in EDGEBIC.
Now the planner adopts two new capabilities. They record that white-to-black takes longer than black-to-white in a setup matrix, a term that did not exist before because the previous engine treated setup as a single number. They flag the booth as the bottleneck so it becomes the anchor for the schedule, another new term. The daily vocabulary, booth, routing, setup, stays put. Two new words joined it, each tied to a capability the planner chose to use.
The takeaway
Mapping RMDB terms to EDGEBIC terms is mostly recognition, because EDGEBIC inherits RMDB's model and keeps its core vocabulary: work centers, routings, operations, shifts, finite capacity, and what-if analysis all carry forward unchanged. A short list of new terms, work center groups, operators and skills, setup matrices, anchor and backward scheduling, lot streaming, the optimizer, and the kiosk, appears for capabilities the previous generation lacked. Keep a one-page crosswalk during the move and update documentation additively. See the platform on the EDGEBIC overview, read the upgrade path on the RMDB to EDGEBIC guide, and hand your team the recognition tour in what carries forward from RMDB to EDGEBIC.
Expert Q&A: Deep Dive
Q: My planners are worried they will have to learn a whole new language. What actually changes in the words they use every day?
A: Almost nothing in their daily words changes. A planner who talks about work centers, routings, operations, run time, setup time, shifts, finite capacity, and what-if analysis uses every one of those terms unchanged in EDGEBIC, because the product inherits RMDB's model. The new words appear only when they reach for a new capability. If they group interchangeable machines, they will say work center group. If they schedule around a certified operator, they will say skill. If they plan backward from the bottleneck, they will say anchor. Those are a handful of additions learned as needed, not a vocabulary swap. The mental model that a decade of RMDB built transfers intact, which is the whole point of an upgrade rather than a replacement.
Q: We document our process using RMDB terms. Will that documentation still make sense after we move?
A: Yes, with a light pass. Your existing documentation describes work centers, routings, operations, and shifts, and those terms all carry forward, so the bulk of it stays accurate. The update you make is additive: where you have adopted a new EDGEBIC capability, you add the new term next to the old process. For example, a routing that now uses a pool of machines gains a note that it targets a work center group. Nothing in the old documentation becomes wrong; some of it gains a new option beside it. Keeping a short crosswalk sheet during the transition makes the update straightforward.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
Migrating to EDGEBIC: The Complete Guide
The full path from RMDB, EDGEBI, a spreadsheet, or a whiteboard to EDGEBIC: what carries forward, what is hand-built, the import order, and how to validate the first schedule.
Migrating Your Tools and Fixtures to EDGEBIC
Tools and fixtures are not one of the eight import masks, so you build the list by hand. Here is what to enter, the quantity rule that ruins schedules when it is wrong, and where tools belong in the migration sequence.
Rehearsing Your EDGEBIC Migration Load
The data load is a repeatable operation, not a one-shot event. Every entity type is safe to re-import, and a reset takes you back to an empty plant, so plan to load your data three times before go-live.