ProShop Scheduling Gaps (And How EDGEBIC Fills Them)

ProShop is a strong system of record for the quality system, digital travelers, and compliance, but many shops report that the day-to-day sequencing decision still happens by hand off a load view, because the questions a planner answers each morning are finite capacity questions: which orders fit this week, what an expedite displaces, and when the constraint machine actually runs out of hours. The fix is not replacing ProShop. It is adding a finite capacity layer beside it that reads the data ProShop already holds and hands executable dates back.

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

Why the gaps exist at all

An ERP's job is to be right about records: what was planned, what was inspected, what was shipped, and the documentation trail behind all of it. A scheduler's job is to be right about time: what runs where, when, in what order, on which machine, with which certified operator. Those are different computational problems, and the second one grows hard fast. Sequencing a few hundred open orders across a couple dozen work centers with shifts, changeovers, and certification constraints is a constraint problem a records-first data model was never designed to solve.

So the gap is structural rather than a defect. A load view is genuinely useful, but it stops at "how much," and the planner still has to decide "in what order." The distinction between capacity planning 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 ProShop-shop version, gap by gap.

Gap 1: a load view is not a sequence

A load view sums the hours queued at a work center and compares them with capacity. That answers whether a week is heavy, not the order the jobs should run in, which job finishes late, or what the expedite pushes out. The deeper question is finite versus infinite capacity: does a date reflect real available hours or just an offset?

How EDGEBIC fills it: every schedule is finite capacity by construction and it produces a real sequence, not just a load bar. Work centers carry instance counts, shift calendars, efficiency, utilization caps, holidays, and downtime, and the engine resolves available hours day by day, then orders the work and hands back a finish date per job. When you want the just-in-time answer from the due date instead of the earliest one, backward scheduling 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. Two identical grinders become 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 two could run side by side.

How EDGEBIC fills it: machine instances are first-class. A work center holding two machines means two 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 a slower machine takes proportionally longer. 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. Aerospace shops running material families, fixtures, or tooling groups 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. 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 schedule ignores who is certified

In a controlled-process shop, a machine being free does not mean the work can run. A special process needs a qualified operator on shift, and a schedule that assumes any body will do produces a date the floor cannot hit.

How EDGEBIC fills it: operator skills and certifications are part of the engine. A step that requires a certified operator is scheduled only into a shift where one is available, so the plan respects the person as well as the machine. That single constraint closes one of the most common sources of "the schedule said today but we could not run it."

Gap 5: the constraint is invisible until it is late

Every shop has a constraint resource. 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 6: reschedule churn, and the audit trail

The complaint that quietly kills adoption is churn: a re-run that moves jobs already set up or restarts work that is halfway done. In a quality shop there is a second worry: whether a reschedule leaves a defensible record of what changed.

How EDGEBIC fills it: two structural guarantees plus a log. Completed work is never moved by a reschedule, because an operation with a recorded actual start and end is historical fact and no mode or setting will shift it. Every scheduled job runs from a frozen snapshot of the routing it was planned with, so a mid-stream engineering change applies to future work and leaves work in progress untouched. And every import run writes a per-run log with one line per row, so you can show exactly what a load changed. Scheduling modes let you re-plan only new jobs and leave everything else in place.

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 ProShop 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 ProShop, which means there is nothing to re-certify at update. The full architecture is on the ERP integration page, and the same method applied to other platforms is covered in the E2 Shoptech and Plex versions of this post.

This is not a new bet. User Solutions has integrated scheduling with ERPs this way since 1991, including work for BAE Systems and the US Navy, where the method scheduled a Nimitz-class program past 26,000 tasks, plus a Fourth Shift integration at Plastilite Corporation that the ERP vendor itself recommended.

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 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 and become visible in the results.

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

Date honesty. Sample 20 recently shipped orders and compare committed dates with actual ship dates. That spread is your current scheduling error and becomes the baseline you measure against.

A 30-minute test

Export three files: work centers, routings for your five highest-volume parts, 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 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.