IQMS / DELMIAworks Scheduling Gaps (And How EDGEBIC Fills Them)

DELMIAworks (formerly IQMS EnterpriseIQ) is a strong system of record for real-time MES, quality, and inventory, but many plants report that the fine-grained sequencing decision still happens in a spreadsheet, because the questions a planner answers each morning are finite capacity questions: which orders fit this week, how to order color and material changeovers, and when the constraint press actually runs out of hours. The fix is not replacing DELMIAworks. It is adding a finite capacity layer beside it that reads the data DELMIAworks already holds and hands executable dates back.

EDGEBIC by User Solutions is that layer. This post walks the gaps plants report, why they exist in any MES-first ERP, and how each one is filled with a specific mechanism rather than a brochure claim. For the data-flow mechanics, the companion post is the complete IQMS / DELMIAworks integration guide.

Why the gaps exist at all

An ERP's job is to be right about what happened and what it cost: production counts, quality records, inventory, and financials. A scheduler's job is to be right about what should happen next: what runs where, when, in what order, on which press, with which changeover. Those are different computational problems, and the second one grows hard fast. Sequencing hundreds of open orders across banks of presses and lines with shifts, color and material changeovers, and shared tooling is a constraint problem a real-time data model was never designed to solve.

So the gap is structural rather than a defect. Real-time monitoring is excellent at "now," but "next" is a planning decision, and it usually ends up in a spreadsheet the MES cannot see. The distinction between execution and detailed scheduling is standard in the operations management body of knowledge maintained by ASCM, and the general version of the story is in where ERP falls short on scheduling. Here is the DELMIAworks version, gap by gap.

Gap 1: dates that assume capacity exists

The first question, finite versus infinite capacity, decides whether a date means anything. Infinite-capacity logic stacks work into a week without asking whether the press hours exist. Finite-capacity logic refuses to plan 60 hours onto a press with 40 available and pushes the overflow to when capacity is real.

How EDGEBIC fills it: every schedule is finite capacity by construction. Work centers carry instance counts, shift calendars, efficiency, utilization caps, holidays, and downtime, and the engine resolves available hours day by day before it allocates anything. A run that does not fit this week lands where it fits, and the date it produces is one the floor can hit. When you want the just-in-time answer from the due date, backward scheduling is a per-job choice.

Gap 2: color and material changeovers with no sequencing logic

This is the gap that costs a molding plant the most, and the one an ERP cannot express. One setup time per operation cannot say that white to black costs four hours of purge while black to white costs one. Changeover cost depends on what ran immediately before, and no single column captures it.

How EDGEBIC fills it: a sequence-dependent setup matrix per work center, organized by setup families. You group parts by color and by material, set the changeover time between families once, and maintain dozens of entries rather than thousands of part-to-part pairs. The optimizer then sequences compatible runs together and orders families light to dark to cut total changeover, using mathematical optimization with a proven optimality gap plus a multi-run layer guaranteed never worse than the baseline. Recovered purge and scrap time is capacity you already own. The concept post is what a setup family is.

Gap 3: press banks flattened into one number

Most ERP data models describe a press bank as a capacity figure. Two identical presses become one resource with a bigger number, which is right in a weekly total and wrong every day, because it will plan one run that occupies the whole bank where two could run side by side.

How EDGEBIC fills it: machine instances are first-class. A bank holding two presses means two simultaneous runs, and the engine chooses between load balancing across instances and dedicating one press per job per day when a tooling change makes that the correct rule. Work center groups go further: a named pool of interchangeable presses that the engine re-shops on every reschedule, with a per-member efficiency factor so a slower press takes proportionally longer. The mechanics are in how EDGEBIC picks the best machine in a pool.

Gap 4: the constraint is invisible until it is late

Every plant has a constraint resource, whether it is a press size, a specific line, or a secondary cell. Without finite loading, its overload appears only as a wave of late orders weeks later, by which point the decision window has closed. Finding and protecting the constraint is the highest-return move in scheduling, and the method is in production bottleneck identification.

How EDGEBIC fills it: flag the work center as a bottleneck and the engine anchors schedules around it, scheduling backward into the constraint and forward out of it with protective buffers, which is the Theory of Constraints pattern applied to a real routing. Capacity views then show the constraint's load by day, so an overloaded Tuesday is visible while there is still time to move something.

Gap 5: reschedule churn nobody trusts

The complaint that quietly kills adoption is churn: a re-run that moves runs already set up, restarts work that is halfway done, or produces a plan the floor recognizes as fiction. Once that happens twice, supervisors stop reading it.

How EDGEBIC fills it: two guarantees, both structural. Completed work is never moved by a reschedule, because an operation with logged actual start and end is historical fact and no mode or setting will shift it. And every scheduled job runs from a frozen snapshot of the routing it was planned with, so a mid-stream change never silently rewires work in progress. On top of both, scheduling modes let you re-plan only new jobs and leave everything else untouched.

Gap 6: what-if answers that take an afternoon

Inserting one rush order displaces others, which displaces others. A person cannot recompute several hundred downstream operations, so the honest answer to "what slips?" is a guess, and the guess is usually optimistic.

How EDGEBIC fills it: rescheduling is a computed operation, and quote simulation lets you test a promise date before you make it. Insert the candidate order, run the scheduler, and read the displaced dates. The whole what-if loop is minutes, which changes who gets to ask the question: sales can ask it during the call rather than after it.

The integration question, answered honestly

The objection to any layer beside the ERP is the data bridge. This product line answered that decades ago, and the answer is deliberately unglamorous: reusable import masks that read the Excel, CSV, and database exports DELMIAworks already produces. You map columns once, and every later run is two clicks. Routings import in two passes so operation sequences wire themselves. Unit conversion (cycle seconds to hours at 0.000278, minutes to hours at 0.016667) lives inside the mask. Every row reports Created, Updated, Reused, or Failed with a per-run log.

There is no certified connector, no middleware server, and nothing installed inside DELMIAworks, which means there is nothing to re-certify at upgrade. The full architecture is on the ERP integration page, and the same method applied to other platforms is covered in the Plex and E2 Shoptech versions of this post.

This is not a new bet. User Solutions has integrated scheduling with ERPs this way since 1991, and the lineage includes a Fourth Shift integration at Plastilite Corporation, a plastics manufacturer, that ran Monday to Friday with the ERP vendor itself recommending the add-on, plus Cummins across 33 locations and BAE Systems.

Three checks that predict how fast this pays off

Each takes minutes and none requires buying anything.

Routing coverage. Pull routings for your ten highest-volume items. Do they carry an operation sequence, a work center, hours or cycle time per unit, and a setup time? If yes, you can schedule on day one. Missing setup times become visible in the results.

Press truth. Count real presses per bank and compare with what DELMIAworks records as a work center. Every bank where the counts disagree is capacity you are currently misrepresenting in both directions.

Changeover honesty. List your color and material families and the changeover time between the worst pairs. That table is the setup matrix you will build, and the purge hours it hides are the payback you can measure.

A 30-minute test

Export three files: work centers, routings for your five highest-volume items, and this week's open orders. Bring them to a demo. Mapping the columns live takes minutes, and the first finite capacity schedule from your own data, changeover families included, answers the only question that matters: do these dates look like your plant? The EDGEBIC product overview and the ERP scheduling add-on page cover the rest.