EDGEBIC + ProShop: The Complete Scheduling Integration Guide

Integrating ProShop with EDGEBIC means exporting the parts, work centers, routings, and open orders ProShop already holds to Excel or CSV, mapping those columns once with a reusable import mask, and letting EDGEBIC schedule the work against finite capacity: real shift hours, real machine counts, and sequence-dependent setups. Executable dates then export back for ProShop and your customers. There is no middleware server, no interface object inside the ERP, and no certified connector to maintain through an update.

EDGEBIC by User Solutions is the newest generation of a scheduling line that has integrated with manufacturing ERPs this way since 1991. Across 35+ years the same approach has fed schedules for the US Navy, GE, BAE Systems, and Cummins, and it carried the Nimitz-class program past 26,000 tasks. This guide covers the ProShop case: what to export, how the masks work, what the engine does with the result, and what a realistic first two weeks looks like in a quality-driven shop.

Where ProShop stops and detailed scheduling starts

ProShop is very good at the paperless quality system: digital travelers, work instructions, purchasing, and the compliance records an AS9100 or ISO shop lives on. That belongs there and should stay there. The gap most ProShop shops report is one layer over, in the questions a planner answers every morning:

• Which of these open orders actually fits on the constraint machine this week?
• If the AOG job jumps the queue, which committed dates slip and by how much?
• Is the shared grinder loaded to 80 percent or 150 percent next Tuesday?

Those are finite capacity questions. Answering them means modeling shifts, machine counts, changeover sequences, and operator certifications against every open order at once, which is a different computational problem from running a quality system. That is why a dedicated scheduling layer beside the ERP is the standard pattern rather than an admission of weakness. The general argument is in finite versus infinite capacity scheduling, and the gap-by-gap version for this ERP is the companion post on ProShop scheduling gaps and how EDGEBIC fills them. The wider category view is on where ERP falls short on scheduling.

The integration in one table

The EDGEBIC ERP integration architecture is identical for every ERP, ProShop included:

An import mask is a saved recipe. It remembers which kind of data you are importing, what format it arrives in (an Excel workbook, or comma, semicolon, tab, or space delimited text), whether the first row carries headings, and how each column of your file maps onto an EDGEBIC field. You build it once by dragging your file's column headings onto EDGEBIC's target fields. Every run after that is two clicks: pick the mask, press Do It.

Every row in your file produces exactly one outcome: Created, Updated, Reused (found and deliberately left alone), or Failed (rejected, with the reason recorded). A result dialog shows the counts and a per-run log file records every row. Nothing half-imports silently, which is exactly the audit posture a quality shop wants.

Step 1: the four exports

You do not need everything ProShop knows. Four exports carry a complete scheduling model.

1. Parts. The part number, description, unit of measure, and any cost or lead-time columns you want visible. The identifier is the natural key and matching is case-insensitive, so WING-RIB-4 in the file finds Wing-Rib-4 in the database.
2. Work centers. The work center identifier, how many identical machines it holds, default setup hours, efficiency, and an hourly rate if you want cost rollups. Bottleneck and shift assignment flags can ride along in the same file.
3. Routings. One row per operation: end part, work center, sequence number, hours per unit, setup time, queue time.
4. Open orders. Part, quantity, order reference, and dates.

Any report, list, or query in your ProShop environment that saves to Excel or CSV is a valid source. You are not writing code, not touching the database directly, and not asking for a custom interface. The file is the interface, which is exactly why nothing here enters your ERP's upgrade path.

Step 2: map the columns once

Build one mask per file. Name it after the routine rather than the file: Weekly ProShop Orders outlives orders-week29.xlsx. Mandatory fields are flagged in the mask editor, and the run refuses to start until they are mapped, so a half-built mask fails before it reads a single row rather than half-way through.

Two mask features carry most of the weight in a ProShop integration:

Unit conversion. ERPs and schedulers disagree about units constantly. Set a conversion factor on any numeric column and the multiplication happens before the value is stored. Minutes to hours is 0.016667. Seconds to hours is 0.000278. A standard time quoted per lot of 100 pieces becomes per piece with 0.01. Different columns in one file can carry different factors, so a routing export mixing per-lot run times with per-changeover setup minutes lands correctly in one run.

Blank-cell preservation. On an update run, a blank cell keeps the existing value instead of wiping it. A file carrying only part number and price refreshes prices and touches nothing else. Note the rule: a zero is a value, not a blank, so leave a column out rather than filling it with zeros you do not mean.

Step 3: the routing import, and why it takes two passes

Routings are the hardest data to move between systems because operations reference each other: op 10 feeds op 20 feeds op 30. A naive row-by-row import cannot wire those links, because op 20 does not exist yet when op 10 is written.

EDGEBIC's routing import therefore runs in two passes. Pass one reads and validates every row, auto-creates any work center or part the file names that does not exist yet, and buffers the steps. Pass two groups the buffered rows by end part, sorts them by sequence number, writes them, and then wires the chain: 10 to 20, 20 to 30, and the terminal step to the finished part so the routing renders as one connected flow in the graphical routing designer.

Three conventions save time later:

• Number sequences in gaps of 10. When engineering inserts an inspection op next quarter it becomes 25 and nothing renumbers.
• Keep all of one part's steps in one file. A routing import wipes and recreates that part's steps once per run, which is what makes re-imports idempotent. Splitting one part across two runs means the second run's wipe deletes the first run's steps.
• Re-importing is safe for running orders. Every scheduled job carries a frozen snapshot of the routing it was planned with, so a routing change applies to future jobs and leaves work in progress untouched. In a controlled-process shop that guarantee matters as much as the schedule itself.

Step 4: orders in, then run the scheduler

The order import maps part, quantity, reference, and dates. When your export carries an order reference, rows sharing that reference group under one order and their jobs auto-number as {Ref}-{line}, which keeps a multi-line release together instead of scattering it.

One rule matters more than any other: imports never schedule anything. After the run, imported orders sit as unscheduled demand. You then run the scheduler, which states its scope before it plans (how many jobs are new and how many existing jobs are being rescheduled), and the new work slots around everything already committed on the floor. Data movement and planning stay separate on purpose, so an import can never silently rearrange the plant.

Once the data is in, the whole engine applies to your ProShop work: finite capacity across multiple shifts and machine instances, work center groups that re-shop the machine pool on every reschedule, a sequence-dependent setup matrix, lot streaming with transfer batches, operator skills and certifications, and mathematical optimization with a proven optimality gap. Operator certifications map naturally onto an aerospace shop, where a special-process step can only run when a qualified operator is available. The EDGEBIC product overview maps the engine.

Step 5: sending executable dates back

The return trip is Excel. The Job View grid exports the job schedule as a workbook with colored cells and a legend sheet. The work center schedule exports the same way, and every report dialog exports to Excel or PDF using the column layout you saved, which turns a dispatch list into a saved report rather than a document someone rebuilds each morning.

From there, revised dates go back into ProShop through the order-maintenance path your team already uses. There is no automated write-back, which is deliberate: your ERP data stays under your team's control and inside your existing approval process. The category framing for this split is on the ERP scheduling add-on page.

A realistic first two weeks

The method behind this guide has a documented benchmark in the User Solutions lineage: at Plastilite Corporation the ERP vendor itself recommended User Solutions scheduling, and the team went from first export to a complete optimized schedule with ERP integration in 5 days. A shop with heavier routing and quality data usually wants a little more runway for review rather than for the technical work.

If you are starting from an empty database, the green-field setup walkthrough covers the sequence in detail, and the ProShop to EDGEBIC data mapping reference is the field-level lookup you keep open while building masks.

Prove it with your own export

The fastest evaluation is not a feature list, it is your own file. Export this week's open orders and a routing 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. Shops comparing several ERPs at once can also read the E2 Shoptech, Plex, and Statii versions of this guide: the method is identical, which is the point.