Blog
Insights on production scheduling, lean manufacturing, and manufacturing software from 35+ years of industry experience.
Everything we have published.
Deciding Which ERP Work Orders to Import
How to filter an ERP work order export for scheduling: which statuses belong in the plan, why MRP planned orders usually do not, and why a status filter beats a date window.
Handling ERP Part Number Revisions on Import
Whether a revision should create a new product in EDGEBIC or update the existing one, how identifier matching decides it, and how to stop revisions creating duplicate part records.
Importing Customer Due Dates vs Internal Need Dates
Your ERP holds several dates per work order. Learn which one to map as the EDGEBIC due date, which to map as the job start, and why importing an MRP need date double-buffers the plan.
Importing Your ERP's Operation Sequence Numbers Into EDGEBIC
How EDGEBIC uses ERP operation sequence numbers to wire a routing chain on import, and how to handle duplicates, alphanumeric codes, sub-operations, and renumbered steps.
Should You Import Your ERP's Manufacturing Calendar?
What an ERP calendar actually gives a scheduler, why shift patterns have to be authored rather than imported, and how to harvest the holiday closure list your ERP already maintains.
Mapping ERP Order Priority Into Your Schedule
How to translate an ERP's priority codes, customer classes, and rank numbers into EDGEBIC job priority, and why priority ranks the queue rather than overriding finite capacity.
Reconciling ERP Work Order Quantities After Partial Completion
How to import work order quantities from an ERP once a job is partly finished: original versus remaining quantity, avoiding double subtraction, and closing jobs that leave the export.
Scheduling a Shop That Runs Two ERPs
One shop floor, two systems of record: how to feed both into a single finite capacity model, namespace colliding part numbers, and avoid double-counting the same demand.
What Changes in EDGEBIC When You Replace Your ERP
Swapping ERPs while keeping your scheduler: what survives untouched, which masks get rebuilt, why identifier continuity is the whole risk, and how to keep scheduling through cutover.
When Your ERP Exports Setup as Its Own Operation Row
How to import an ERP routing that models setup as a separate operation line: merge it into the run step's setup field, or keep it as a real step when setup runs off the machine.
A Go-Live Cutover Plan for Your ERP and EDGEBIC
A staged cutover plan for running EDGEBIC alongside your ERP: parallel run, the trust checks that end it, who owns which data, and the first week the schedule is official.
An ERP Import Reconciliation Checklist for EDGEBIC
The checks to run after every ERP import into EDGEBIC: row counts, Created versus Reused, orphan work centers, routing chain gaps, and hours that do not reconcile.