Blog
Insights on production scheduling, lean manufacturing, and manufacturing software from 35+ years of industry experience.
How the platform actually works: scheduling, optimization, the shop floor and ERP data.
Featured Guides
Connecting EDGEBIC to Your ERP Database With a SQL Source
How to point a scheduled EDGEBIC integration at a read-only ERP query instead of a file: testing the connection, previewing columns, checking the mask fits, and the stored-password rule that catches most teams out.
Closing ERP Work Orders That EDGEBIC Still Thinks Are Open
Your ERP closing a work order is invisible to EDGEBIC. There is no status column on the order mask, and a job whose every step is done is not closed automatically. Here is the closing pass that keeps your numbers honest.
ERPNext to EDGEBIC: The Data Mapping Reference
ERPNext data export scheduling doctype by doctype: map Items, Workstations, BOM operations and Work Orders into EDGEBIC import masks, with conversions and upsert rules.
Reading the Import Log After a Nightly ERP Run
An unattended import writes one log file per run recording every row's outcome. Here is the ninety-second review that catches a broken export before the plant works to a wrong plan.
The Direction Decision Your ERP Export Cannot Make
Forward or backward is stamped on a job at creation from a site-wide default, and no import mask carries it. Settle the policy before the first order file, because direction locks once actuals land.
What to Do When the ERP Export Is Late or Missing
The nightly file did not arrive. Here is why yesterday's plan is still safe to work to, what not to do while you wait, and how to catch up cleanly when the file lands.
When Your ERP Labor File Starts Mid-Routing
An actuals row can only land on an operation that is already scheduled. When your ERP's labor history begins at step 30, you have three responses and only one of them keeps the record honest.
Who Should See Your ERP Export Files
Your nightly export is a spreadsheet holding customer names, prices, due dates and labor rates. Here is who needs it, where it should live, and what the application does and does not control.
Deciding ERP Import Frequency by Data Type
Set a refresh cadence per data type instead of one global schedule: why work orders come daily, routings come on change, and why re-importing everything nightly costs more than it gives.
Handling an ERP Export That Changed Column Order
When an ERP export adds, moves, or renames columns, here is how an EDGEBIC import mask reacts, which changes are safe, and the ten-minute repair that keeps the schedule honest.
How Many Import Masks Your Shop Actually Needs
Five masks cover most shops, and the reasons to add a sixth are specific. How to decide when a second mask on the same data type helps and when it just doubles maintenance.
Keeping a Change Log of Import Mask Edits
An import mask edit overwrites the old mapping with no history. Here is the one-line-per-change log that explains a shifted hour total six months later, and what belongs in it.