EDGEBIC works with the ERP you already have
JobBOSS, Epicor, Fourth Shift, SAP, Oracle, Sage, Macola: if your ERP can export to Excel, CSV, or a database, EDGEBIC can schedule from it. Items, routings, and orders come in through reusable import masks; finite capacity schedules and realistic dates go back out. No custom API project. No middleware.
How the integration works
1. Export from your ERP
Use the exports your ERP already produces: item masters, work centers, routings, open orders. Excel, CSV, or a direct database source all work.
2. Map columns once
An import mask maps your columns to EDGEBIC fields, converts units where needed, and remembers the mapping. Routing imports wire up operation sequences automatically in a second pass.
3. Schedule and send dates back
EDGEBIC schedules against finite capacity and exports realistic dates, dispatch lists, and reports back to Excel for your ERP and your customers.
EDGEBIC + JobBOSS
JobBOSS runs the business side of thousands of job shops: quoting, order entry, purchasing, accounting. Its scheduling, though, is where many shops fall back to whiteboards and spreadsheets.
EDGEBIC takes the jobs, routings, and work centers JobBOSS already holds (exported to Excel/CSV), and schedules them against finite capacity: real shifts, machine instances, operator skills, and sequence-dependent setups. Updated promise dates go back to JobBOSS, so order entry quotes dates the shop can hit.
EDGEBIC + Epicor
Epicor Kinetic is a deep manufacturing ERP, and many plants still find its scheduling module produces plans the floor cannot follow, especially with multi-shift, multi-instance work centers and shared machine pools.
EDGEBIC models exactly those cases: work center groups behave like Epicor resource groups but re-shop the pool on every reschedule, and the optimizer sequences to cut changeovers. Epicor exports feed the import masks; finite capacity dates flow back.
EDGEBIC + Fourth Shift
Fourth Shift is the origin story of this integration approach: the Fourth Shift vendor itself recommended User Solutions scheduling as the add-on for its customers, and the documented Plastilite integration went from first export to a complete optimized schedule in 5 days.
EDGEBIC continues that lineage with the same import-mask architecture, now feeding a stronger engine: TOC anchor scheduling, lot streaming, and mathematically optimized sequences.
Running something else? SAP, Oracle, Sage, Macola, AS400-era systems, and home-grown databases have all fed this integration architecture across 35 years, including Cummins Engine scheduling across 33 locations from AS400 data. If it exports, EDGEBIC schedules it.