KhaqanWhat is machine scheduling in an ERP?
Machine scheduling in an ERP is the planning of manufacturing work orders onto specific machines or work centres over time, respecting each machine's capacity and availability, so that the schedule is realistic and no two orders claim the same machine at once.
A manufacturing ERP models the factory as work centres (machines, lines or teams), each with a capacity in hours per day and a calendar of working time. A manufacturing order is broken into work orders, one per operation, and each work order is planned onto a work centre for a duration. Scheduling is the act of placing those work orders in time. Infinite-capacity scheduling ignores whether the machine is already busy; finite-capacity scheduling pushes a job later when the machine is taken.
It matters because the schedule is the promise the factory makes to the sales team. A schedule that allows overlaps produces delivery dates that cannot be met, and the shop floor reverts to a whiteboard that the ERP knows nothing about. Once that happens, every downstream figure (planned completion, capacity utilisation, on-time delivery) is fiction.
Many ERPs, Odoo included, will happily plan two work orders on the same work centre in the same slot unless the business adds a rule. In practice I treat this as one of the first customisations worth making in a manufacturing deployment: a constraint that checks, when a work order is planned or its dates are moved, whether the work centre already has a confirmed work order in that window, and refuses the overlap with a message that names the clashing order. A small module with that constraint and a test is enough.
The common mistake is solving it with people rather than with a rule, by asking a planner to check the Gantt view before confirming. That works until the day the planner is on leave. The second mistake is setting every work centre's capacity to a round number that nobody has measured, which makes the schedule look full while the machine is idle.
Related terms
- Odoo: Odoo is a modular, open-source ERP and business application suite from Belgium, written in Python on PostgreSQL, that covers accounting, inventory, manufacturing, sales, CRM, HR, websites and more, available as a free Community edition and a paid Enterprise edition.
- ERP (enterprise resource planning): Enterprise resource planning (ERP) software runs a company's core operations, such as finance, purchasing, inventory, sales, manufacturing and HR, from one shared database, so a transaction entered once in one department is visible and correct everywhere else.
- ERP customisation risk (upgrade-safe customisation): ERP customisation risk is the danger that changes made to fit an ERP to a business (custom code, edited core files, database tweaks, undocumented workflows) will break, block or inflate the cost of the next upgrade; upgrade-safe customisation is the discipline of avoiding that.