EDGEBIC + SYSPRO Integration FAQ: The Questions Planners Ask First

These are the questions SYSPRO manufacturers ask in the first conversation, answered without hedging: there is no connector, the interface is your existing exports or a database view, nothing is installed in SYSPRO, and nothing you import can disturb a job already running. Each answer stands on its own, so skip to whichever one you came for.

EDGEBIC by User Solutions is a finite capacity scheduling platform that sits beside your ERP. The full walkthrough is the complete SYSPRO integration guide, and the field-level detail is in the SYSPRO to EDGEBIC mapping reference.

Does EDGEBIC connect through a SYSPRO service?

No, and that is deliberate. EDGEBIC integrates through reusable import masks that read Excel, CSV, delimited text, or a database source. You map your export's columns onto EDGEBIC's fields once and save the mask; every later run is two clicks. Because there is no service integration, there is no add-on in SYSPRO, no integration credential, no schema change to carry through an upgrade, and nothing to version-match when either side updates. A connector is a dependency. A file or a view is not.

Does EDGEBIC replace SYSPRO?

No. SYSPRO stays the system of record for orders, inventory, purchasing, WIP, and financials. EDGEBIC reads exports, builds a finite capacity schedule against real shift hours and real machine counts, and hands back dates and dispatch lists as Excel files. Nothing about how your team uses SYSPRO changes. The general case for the split is in why ERP needs a scheduling add-on.

What exactly has to come out of SYSPRO?

Four exports carry a complete scheduling model, and a fifth is optional. Stock codes (a code is the only mandatory column). Work centers (an identifier, plus capacity detail). BOM operations (end product, step name, an operation flag, and hours per unit). Open WIP jobs (item, quantity, and a date). Optionally, labor (job number, work center, date, and hours or pieces). Any report that saves to Excel or CSV is a valid source, and a database view works equally well.

We run multiple SYSPRO sites. Can one schedule cover them?

Yes. A single scheduling database can hold work centers from more than one site, each assigned to its own shift and holiday calendar, so the plan respects each site's real hours rather than an average. Export per site or add a site column you filter within EDGEBIC, and carry inter-site transport as transit days on the routing so a step that ships between plants shows the calendar delay explicitly. You would only split into separate scheduling databases if the sites never share a plan.

Our times come out in minutes. Do we convert them by hand?

No. Set a conversion factor of 0.016667 on the setup or run column in the operations mask and a 30-minute cell lands as 0.5 hours. Seconds use 0.000278, and a time quoted per 100 pieces uses 0.01. The factor is stored on the mask, so every future import converts identically without anyone remembering to do it, and the per-run log records every row if you want to audit the math.

How long until the first real schedule?

Most shops see a first finite capacity schedule from their own data in the first working session, and a tuned one within the week. The documented benchmark in the User Solutions lineage is the Plastilite integration on Fourth Shift: 5 days, Monday to Friday, from first export to a complete optimized schedule with dates synchronized back to the ERP. That figure belongs to that case rather than being a promise, but the method is what repeats: export, map, import, schedule, tune.

Do we have to clean our BOMs first?

No, and the attempt usually costs a month. Import what SYSPRO holds today, schedule it, and compare the dates with what your planner believes. The disagreements are your defect list and they arrive specific: a wrong hours-per-unit shows up as a job finishing implausibly early, a missing setup time shows up as a machine that changes over for free. Because a routing re-import wipes and recreates that item's steps, each corrected file replaces the last cleanly.

Do imported WIP jobs schedule themselves?

No, and the separation is deliberate. An import changes data; the scheduler changes the plan. Imported jobs appear as unscheduled demand until you run the scheduler, and before the run starts a confirmation states the scope in plain numbers: how many jobs are new and how many existing jobs are being rescheduled. You always know the blast radius before anything moves.

Can an import disturb jobs already running?

No, for two independent reasons. Every scheduled job carries a frozen snapshot of the routing it was planned with, so a routing re-import affects future jobs and leaves work in progress alone. And recorded work is never moved by any run: an operation with an actual start and an actual end is historical fact, and no reschedule, mode, or setting will shift it.

We have several identical machines in one work center. How does EDGEBIC know that?

Through the machine-count column on the work center file, which most ERP exports leave out because a work center is usually modeled as one resource with a capacity figure. Fill the instance count deliberately for every multi-machine center: a cell of four machines imported as one produces a plan roughly four times too long, and it fails quietly, since nothing errors and the dates are simply wrong. The arithmetic is in how EDGEBIC calculates work center capacity.

Can we automate the export and the import?

Partly, and it is worth being precise about which half. The export side automates well: a scheduled report or a database view that presents stable columns removes the only manual step that ever gets forgotten. The import side stays a deliberate act, because the result dialog exists to be read. A run that reports 40 unexpected Failed rows is information a person needs to see before the schedule is built on top of it. Most shops settle on automated exports plus a two-minute human import.

What can import never bring across?

The settings that most change what a schedule looks like, because no ERP export has a column for them. Work center groups (machine pools re-shopped on every reschedule, with per-member efficiency factors). The sequence-dependent setup matrix that lets the optimizer sequence work to cut changeover. Operator skills and rosters. Bottleneck anchoring. Lot streaming with transfer batches. Each is configured once inside EDGEBIC and then applies to every imported job afterwards. The EDGEBIC product overview maps them and the ERP integration hub explains where the import boundary sits.

Who runs this day to day?

The planner, in about twenty minutes each morning, without IT. Involve IT exactly once, to make the four exports saved reports or database views with stable columns. After that the routine is export, run the saved masks, run the scheduler, publish the dispatch lists. The same questions for other platforms are answered in the Acumatica and MIE Trak Pro FAQs, and the wider category framing is on the ERP integration hub.

Still deciding?

The fastest way to settle any of this is your own export. Pull this week's open WIP jobs and a BOM/operations file, then bring them to a demo: mapping them live takes minutes, and you leave having watched your own shop scheduled against its own capacity.