Global Shop Scheduling Gaps (And How EDGEBIC Fills Them)

Global Shop Solutions is a strong system of record for quoting, materials, cost, and commitments, but many job shops report that the day-to-day sequencing decision still happens on a whiteboard or in a spreadsheet, because the questions a planner answers each morning are finite capacity questions: which jobs fit this week, what a hot order displaces, and when the constraint work center actually runs out of hours. The fix is not replacing Global Shop. It is adding a finite capacity layer beside it that reads the data the ERP already holds and hands executable dates back.

EDGEBIC by User Solutions is that layer. This post walks the gaps job shops report, why they exist in any business-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 Global Shop integration guide.

Why the gaps exist at all

An ERP's job is to be right about money and material: what was quoted, what was committed, what it cost. A scheduler's job is to be right about time: what runs where, when, in what order, on which machine, with which operator. Those are different computational problems, and the second one grows hard fast. Sequencing 300 open jobs across 45 work centers with shifts, changeovers, shared machines, outside processing, and skill constraints is a constraint problem that a transactional data model was never designed to solve.

So the gap is structural rather than a defect, and it is sharpest in high-mix make-to-order work where every job has its own routing. The discipline distinction between planning material and scheduling capacity 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. The job-shop version of the underlying problem is in job shop scheduling challenges. Here is the Global Shop 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 hours exist. Finite-capacity logic refuses to plan 60 hours onto a machine 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 job 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 instead of the safe one, backward scheduling from the due date is a per-job choice.

Gap 2: work center capacity flattened into one number

Most ERP data models describe a work center as a capacity figure. A cell of three identical mills becomes one resource with a bigger number, which is right in a weekly total and wrong every day, because it will plan one job that occupies the whole cell where three could run side by side.

How EDGEBIC fills it: machine instances are first-class. A work center holding three mills means three simultaneous jobs, and the engine chooses between load balancing across instances and dedicating one machine per job per day when long changeovers make that the correct rule. Work center groups go further: a named pool of interchangeable machines that the engine re-shops on every reschedule, with a per-member efficiency factor so an older, slower machine takes proportionally longer. That matters in job shops where the pool is genuinely mixed: a 20-year-old mill and last year's mill do the same work at different rates. The mechanics are in how EDGEBIC picks the best machine in a pool.

Gap 3: no sequence-dependent setup logic

One setup time per operation cannot express the reality that changeover cost depends on what ran immediately before. Shops running coatings, colors, alloys, or tooling families lose whole shifts to sequencing nobody can see, and no single column in any export can capture it.

How EDGEBIC fills it: a sequence-dependent setup matrix per work center, organized by setup families so you maintain dozens of entries rather than thousands of part-to-part pairs. That distinction matters more in a job shop than anywhere else, because a shop with 4,000 part numbers has an unmaintainable part-to-part matrix and a very maintainable family matrix. The optimizer then sequences compatible work together and orders families to reduce total changeover, using mathematical optimization with a proven optimality gap plus a multi-run layer guaranteed never worse than the baseline schedule. The concept post is what a setup family is.

Gap 4: the constraint is invisible until it is late

Every shop has a constraint resource, and in job shops it moves: this month it is the big mill, next month it is heat treat. Without finite loading, an overload appears only as a wave of late jobs weeks later, by which point the decision window has closed. The method for finding it 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, and when the constraint moves you re-flag it rather than rebuilding a model.

Gap 5: outside processing that disappears from the plan

Job shops send work out constantly: plating, heat treat, anodize, special grinding. In most plans the vendor week is either invisible or hidden inside a padded operation, so the schedule shows a gap nobody can explain and the expeditor calls the vendor to find out where the parts are.

How EDGEBIC fills it: outside processing maps as an operation on a work center representing the vendor, with the turnaround expressed as transit days on the routing step. The vendor week then appears on the Gantt as its own block with its own dates, which means it can be planned around, measured against actuals, and improved. A vendor that consistently runs three days longer than the routing says becomes a visible number rather than a recurring surprise.

Gap 6: reschedule churn nobody trusts

The complaint that quietly kills adoption is not a missing feature, it is churn: a re-run that moves jobs already set up, restarts work that is halfway done, or produces a plan the floor recognizes as fiction. Once that happens twice, supervisors go back to the whiteboard.

How EDGEBIC fills it: two guarantees, both structural. Completed work is never moved by a reschedule, because an operation with recorded 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 engineering 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 7: quoting from a lead time rather than from capacity

In a make-to-order shop the promise date is the product. Quoting from a standard lead time plus padding works until the shop is busy, which is exactly when quoting matters most, and the padding grows every time a job goes late.

How EDGEBIC fills it: quote simulation tests a promise date before you make it. Insert the candidate order, run the scheduler, and read both the completion date and which existing jobs it displaces. The whole what-if loop is minutes, which changes who gets to ask the question: the estimator 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 Global Shop 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 (minutes to hours at 0.016667, hours per 100 pieces at 0.01) 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 the ERP, which means nothing to re-certify at upgrade and no standing project for an IT team of one or two. The full architecture is on the ERP integration page, and the same method applied to other platforms is covered in the Infor and Microsoft Dynamics versions of this post.

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

Three checks that predict how fast this pays off

Each takes minutes and none requires buying anything.

Routing coverage. Pull routings for your ten most frequently run parts. Do they carry an operation sequence, a work center, hours per unit, and a setup time? If yes, you can schedule on day one. Missing setup times are survivable: a zero-setup step simply contributes no changeover time, and the gap becomes visible in the results.

Machine truth. Count real machines per work center and compare with what the ERP records. Every center where the counts disagree is capacity you are currently misrepresenting in both directions.

Date honesty. Sample 20 recently shipped jobs and compare promised dates with actual ship dates. That spread is your current scheduling error and becomes the baseline you measure against. Shops that skip this step cannot prove the improvement they can feel.

A 30-minute test

Export three files: work centers, routings for your five most frequently run parts, and this week's open jobs. Bring them to a demo. Mapping the columns live takes minutes, and the first finite capacity schedule from your own data answers the only question that matters: do these dates look like your shop? The EDGEBIC product overview and the ERP scheduling add-on page cover the rest, and the field-level detail is in the Global Shop to EDGEBIC data mapping reference.