EDGEBIC + Fourth Shift: The Complete Scheduling Integration Guide

Integrating Fourth Shift with EDGEBIC means exporting items, work centers, routings, and open orders from your ERP, mapping those columns once with reusable import masks, scheduling the work against true finite capacity, and sending realistic dates back to Excel for Fourth Shift. This pairing carries unusual weight in scheduling history: Fourth Shift is the ERP whose vendor recommended the User Solutions scheduler to its own customers, and whose documented integration benchmark (5 days at Plastilite Corporation, Monday to Friday) still defines what fast ERP integration looks like.

EDGEBIC by User Solutions is the direct successor to that lineage. The company has built ERP-adjacent scheduling since 1991; across 35+ years the approach has served the US Navy, GE, BAE Systems, and Cummins. This guide covers the Fourth Shift case specifically: the heritage, the data flows, the mask mechanics, and a realistic first-week plan.

The heritage: when the ERP vendor recommends the add-on

The strongest endorsement a scheduling add-on can get is the ERP vendor pointing its own customers at it. That happened with Fourth Shift (from Softbrands, Inc.). Plastilite Corporation of Omaha, Nebraska, chose Fourth Shift for accounting and inventory, but its scheduling module could not handle Plastilite's injection molding complexity: many machines with different tool configurations holding different combinations of molds. Fourth Shift recommended Resource Manager DB (RMDB) from User Solutions as the scheduling layer.

The integration ran in one working week. Monday to Friday, the team broke down the scheduling data, entered routings with alternate work centers, managed the variable chest and tool sizes, imported open orders from Fourth Shift, generated an optimized finite capacity schedule, and synchronized dates back to the ERP. The full account is in the Plastilite case study, and the method behind the week gets its own telling in the 5-day integration story.

That proof belongs to the RMDB generation, and it is claimed as exactly that: heritage. What EDGEBIC inherits is the architecture that made it possible, now feeding a stronger engine.

Why file-based integration suits a legacy ERP

Fourth Shift installs tend to be long-lived. Shops running it have often run it for a decade or more, and the last thing a stable legacy system needs is a fragile API dependency bolted to its side. The EDGEBIC integration architecture fits that reality on purpose:

• The interface is a file. Anything Fourth Shift can put into Excel or CSV (item lists, work center data, routings, open orders) feeds EDGEBIC directly. Database sources work too, but nothing requires them.
• No connector to certify or maintain. There is deliberately no "native Fourth Shift connector" to version-match. The masks read whatever the export produces; when the export gains a column, you map it or ignore it.
• The ERP is never touched. Fourth Shift stays the system of record for financials, purchasing, and inventory. EDGEBIC reads exports and hands Excel back. Risk to the incumbent system is structurally zero.

The data flows

An import mask is a saved column mapping: which entity you are importing, the file format (Excel workbook or comma, semicolon, tab, or space delimited text), whether the first row is headings, and how each source column maps to an EDGEBIC field. Build it once by dragging your file's headings onto the target fields; after that the weekly run is two clicks. Every row lands as exactly one of Created, Updated, Reused, or Failed, with counts in the result dialog and every row recorded in a per-run log file.

Mask behaviors that matter most against a legacy export:

1. Unit conversion. A conversion factor of 0.016667 turns minutes into hours during import (a 30 lands as 0.5). Set once on the mask, applied every run.
2. Blank cells preserve values on update. A partial refresh file (say, item costs only) updates what it carries and touches nothing else.
3. Safe by default. Existing records come back Reused unless you enable updates, and one bad row fails alone instead of aborting the run.
4. Positional mapping. Older exports without heading rows map by column number instead of column name.

The routing import: two passes, wired sequences

Routing data is where legacy integrations usually stall, because operations reference each other and a row-by-row load cannot wire the links. EDGEBIC's routing import runs two passes: pass one validates rows, auto-creates any work centers or products the file names that do not yet exist, and buffers the steps; pass two sorts each product's steps by sequence number, saves them, and wires step 10 to 20, 20 to 30, and the final step to the finished product. The routing arrives as one connected flow in the graphical routing designer, alternates and parallel steps included.

Three conventions keep re-imports boring (which is the goal):

• Sequence numbers in gaps of 10, so inserting a step later needs no renumbering.
• All of one product's steps in one file. A re-import wipes and recreates that product's steps within the run; splitting a routing across two runs loses the first run's steps.
• Scheduled jobs are immune. Every scheduled job carries a frozen snapshot of its planned routing, so routing maintenance never rewires work in progress, and completed operations are never moved by any reschedule.

What the modern engine adds to the heritage

Plastilite's 2000s-era schedule was built on alternate work centers and finite capacity. EDGEBIC keeps those and adds the current generation: work center groups that re-shop a machine pool on every reschedule, a sequence-dependent setup matrix, operator skills and certifications, lot streaming with transfer batches, backward (just-in-time) scheduling per job (see forward versus backward scheduling), Theory of Constraints anchoring around bottlenecks, and mathematical optimization with a proven optimality gap (with a multi-run layer guaranteed never worse than the baseline). The full map is on the EDGEBIC product overview and in the complete EDGEBIC guide.

One rule spans everything: imports change data, never the plan. Imported orders wait as unscheduled demand until you run the scheduler, which confirms the new and existing job counts in scope before planning, so fresh work slots around existing commitments.

Closing the loop with shop-floor actuals

A schedule built from ERP data drifts the moment the floor deviates from plan, so the return loop matters as much as the initial load. EDGEBIC offers two paths, and legacy shops typically use both.

The first is live capture: operators record hours and piece counts at a shop-floor kiosk as work happens. The second is bulk import: whatever your shop already collects (a Fourth Shift labor export, a data-collection extract, a supervisor's spreadsheet) flows in through the Actuals import mask, one row per job, work center, and day.

The actuals import is engineered for re-running, because corrected timesheets are a fact of life. The dates a file carries are always overwritten with the file's values, so importing the same file twice never double-counts and importing a corrected file fixes the earlier numbers. Days the file does not mention are preserved by default. A row carrying only pieces gets its hours derived from the operation's rate automatically, and a truthy value in a Complete column marks the operation finished.

The payoff comes at the next reschedule: remaining work replans from where the shop actually stands, while completed operations stay exactly where reality put them. Plan and floor reconverge weekly instead of drifting until quarter-end.

The first week, Plastilite-style

The original benchmark maps cleanly onto the mask workflow:

Starting EDGEBIC from an empty database? The green-field setup walkthrough sequences the entire build, and the ERP scheduling add-on guide frames the category if you are still comparing approaches.

Put the lineage to the test

The Fourth Shift story is the origin of this integration method; your export is the next chapter. Pull this week's open orders and your routing file from Fourth Shift and bring them to a demo. The columns map in minutes, and the first schedule from your own data tells you more than any page of claims.