EDGEBIC + Fulcrum: The Complete Scheduling Integration Guide

Integrating Fulcrum with EDGEBIC means exporting the items, work centers, routings, and open work orders Fulcrum already holds to CSV or Excel, 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 go back as Excel. There is no API project, nothing installed inside Fulcrum, and no certified connector to version-match when either side updates.

EDGEBIC by User Solutions is the newest generation of a scheduling line that has integrated with ERPs this way since 1991. Across 35+ years the same file-based approach has fed schedules for the US Navy, GE, BAE Systems, and Cummins. This guide covers the Fulcrum case: what to export, how the masks work, and what the engine does with the result.

Why a modern cloud platform still needs a floor scheduler

Fulcrum runs the manufacturing business record well: items, work orders, purchasing, inventory, and the shop data that hangs off them. What most Fulcrum manufacturers report is that the daily sequencing decision still happens somewhere else, because the morning questions are finite capacity questions:

• Which of these open work orders fit on the two machining cells this week?
• If this rush order jumps the queue, which promise dates move and by how much?
• Is the finishing line loaded to 80 percent or 160 percent next Thursday?

Those require modeling shifts, machine instances, changeover sequences, and operator availability against every open order at once. It is a different computational problem from recording transactions, which is why a dedicated finite capacity layer beside the ERP is the standard pattern. The general case is in finite versus infinite capacity scheduling, and the reason the same layer serves every platform is in why EDGEBIC connects to every ERP the same way.

The integration in one table

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

An import mask is a saved recipe that remembers the data type, the file format, whether the first row is headings, whether text values are quoted, and how each column maps onto an EDGEBIC field. You build it once by dragging column headings onto target fields, and every run after that is two clicks. Each row returns Created, Updated, Reused, or Failed, with a per-run log recording every one.

The file is the interface, and that is the advantage

Cloud platforms change on the vendor's schedule, not yours. A file-based interface has a small failure mode: the only thing that can break is a column heading, and the fix is re-mapping one row in a mask. Nothing is installed in your account, no integration credential is created, and scheduling keeps working offline because the plan is computed locally.

Step 1: the four exports

Any Fulcrum list or report that saves to CSV is a valid source.

1. Items. Identifier, description, unit of measure, and any cost or lead-time columns worth keeping visible. The identifier is the natural key, matched case-insensitively.
2. Work centers. Identifier, machine count, default setup hours, efficiency, and an hourly rate. A bottleneck flag rides along.
3. Routings. One row per operation: end item, work center, sequence number, hours per unit, setup time, queue time.
4. Open work orders. Item, quantity, order reference, and dates.

Step 2: map the columns once

Name each mask after the routine, so Weekly Fulcrum Work Orders outlives wo-week29.csv. Mandatory fields are flagged and the run refuses to start until they are mapped. Unit conversion applies a factor to a numeric column before storage, so minutes become hours with 0.016667 and a per-100-piece time becomes per piece with 0.01. Blank-cell preservation keeps an existing value when a cell is blank on an update run, with a zero counting as a value rather than a blank.

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

Routings reference each other, so a row-by-row import cannot wire the links because step 20 does not exist when step 10 is written. EDGEBIC's routing import runs in two passes: pass one validates and buffers every row and auto-creates any missing work center or item, and pass two groups the rows by end item, sorts by sequence, writes them, and wires the chain so the routing renders as one connected flow in the graphical routing designer. Number sequences in gaps of 10, and keep all of one item's steps in one file so re-imports stay idempotent.

Step 4: work orders in, then run the scheduler

The order import maps item, quantity, reference, and dates. Imports never schedule anything: imported orders sit as unscheduled demand until you run the scheduler, which states how many jobs are new and how many are being rescheduled before it plans. Once the data is in, the full engine applies: finite capacity across multiple shifts and machine instances, work center groups, a sequence-dependent setup matrix, lot streaming, operator skills, and mathematical optimization with a proven optimality gap. The EDGEBIC product overview maps the engine.

Step 5: sending dates back

The return trip is Excel. The Job View grid exports the schedule as a workbook with colored cells and a legend, the work center schedule exports the same way, and every report exports to Excel or PDF using your saved layout. Revised dates go back into Fulcrum through your normal work order maintenance path. There is no automated write-back, which keeps your ERP data under your team's control.

Test it with your own export

Export this week's open work orders and a routing file, then bring them to a demo. Mapping them live takes minutes. If you are comparing systems, the Katana and MRPeasy versions follow the same method, which is the point of a universal import layer.