Manufacturing production scheduling software that plans to real capacity
Manufacturing production scheduling software decides which order runs on which machine, in what sequence, on which shift, so the plan matches what the factory can really do. It accounts for machine capacity, changeover times, materials on hand and on order, operator skills and maintenance windows, and it gives sales a delivery date the floor can keep. We build production scheduling software for manufacturing around your routings and your planner's rules, connect it to your ERP and your machines, host it in the EU and hand your company the source code.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Why the ERP plan is not a schedule
Most ERP systems plan production with infinite capacity. Material requirements planning works backwards from the due date and assumes every work centre can take whatever lands on it. On paper, that produces a plan where Tuesday on the press brake has 40 hours of work in an eight-hour shift. The planner then rebuilds the plan by hand, in a spreadsheet or on a whiteboard, and that hand-made plan is what the factory actually runs. When the planner is on holiday, the factory notices.
Production scheduling software does what the planner does by hand, with finite capacity: every machine and work centre has a calendar, every operation takes the time it really takes, and nothing is scheduled where there is no room. It respects the order of operations in each routing, waits for materials that have not arrived, and shows the knock-on effect of every change. The result is a schedule that can be released to the floor as it is.
The international standard for connecting business and plant systems, ISA-95, also published as IEC 62264, puts ERP at level 4, business planning and logistics, and manufacturing operations management at level 3, below it. Detailed scheduling lives at the line between the two: it takes orders and dates from the business side and turns them into work the floor can do. (ISA page read on 11 November 2026.)
What production scheduling software does
- Finite capacity on every resource. Machines, lines, cells, tools and qualified operators, each with its own shift calendar, holidays and planned maintenance.
- Routings and operations. Each order follows its routing step by step, with setup, run and wait times, minimum transfer quantities and operations that can overlap.
- Changeovers that depend on the sequence. The time to switch from one product, colour, alloy or tool to the next is in a table per machine, and the scheduler groups similar work to keep changeovers short.
- Materials before machines. An operation is not scheduled before its material is in stock or due in, so the plan never waits for steel that has not been ordered.
- Delivery dates you can promise. Sales asks when a new order could ship, and the answer comes from the real schedule, not from a standard lead time.
- A live planning board. A Gantt view per machine and per order, drag and drop for the planner, with conflicts and late orders shown in colour.
- Rescheduling in minutes. A machine stops, a rush order arrives or a supplier is late: the planner asks for a new draft, compares it with the current plan and accepts or adjusts it.
- Floor feedback. Operators report start, finish, quantities, scrap and stops at the machine, and the schedule updates from what really happened.
Advanced planning and scheduling, without the black box
Advanced planning and scheduling software, or APS, is the name for systems that plan materials and capacity together and search for a good sequence rather than accepting the first one that fits. Behind it are scheduling rules and optimisation methods: earliest due date first, shortest processing time, grouping by setup family, protecting the bottleneck machine, or a solver that weighs lateness against changeover time and overtime by weights you set.
We use these methods, but we keep them explainable. A planner can see why an order is where it is, which rule put it there and what would happen if it moved. The weights are business decisions, written down with your production manager: is one day late on a key customer worse than an extra changeover? Is overtime on Saturday acceptable to save a delivery? When the answers change, the weights change, and the next draft follows them.
Where scheduling pays back first
Scheduling projects that pay back usually start from one of a few symptoms. Delivery dates are promised from a standard lead time and missed. One machine is always the bottleneck, but nobody sees its queue until it is too long. Changeovers eat a large share of the shift because orders run in due date order with no grouping. Work in progress piles up between operations. Or the whole plan exists only in one planner's spreadsheet.
We measure the symptom before we build: on-time delivery, changeover hours per week, work in progress, the planner's hours spent on rescheduling. Those numbers are recorded at the start and compared after go-live, so you see what the scheduler changed rather than hearing that it should have.
Ready-made scheduler or custom software?
There are mature ready-made products, such as Siemens Opcenter APS, PlanetTogether, Asprova and DELMIA Ortems, and scheduling modules inside manufacturing ERPs such as Katana or MRPeasy. For a factory with standard routings and an ERP that one of them integrates with, a product is often the faster route, and we will say so.
| Situation | Ready-made scheduler | Custom software |
|---|---|---|
| Standard routings, an ERP the product supports | Usually the right choice | Rarely worth building |
| Rules that live in the planner's head | Configured where the product allows | Written down and built in as they are |
| Unusual constraints: curing, batching, shared tools | Partly, through workarounds | Modelled directly |
| Older or home-made ERP | Integration project of its own | Read through whatever it exposes |
| Floor reporting on tablets and machines | Often a separate MES | Part of the same system |
| Ownership of data and code | Licensed per seat or site | In your company's own account |
Connected to the ERP, the floor and the machines
The scheduler reads sales and production orders, routings, bills of materials, stock and purchase orders from your ERP, and writes back planned start and finish dates and actual quantities. On the floor, operators use a tablet at the machine or their phone to start and finish work and report stops, with no paperwork to retype. Where machines offer data through OPC UA, MQTT or a controller export, counts and stops come in automatically. If the ERP itself is the problem, see ERP for manufacturing; for the stock side, see inventory management software; for multi-warehouse replenishment, see distribution resource planning software; and for the material plan that feeds the schedule, see material resource planning software.
People are a constraint too. If a line needs two certified operators, the scheduler reads the shift plan and qualifications, and a gap in the shift plan shows as a gap in capacity. For the people side of the plan, see workforce management software. For planned machine stops agreed with maintenance, see preventive maintenance scheduling software. For the wider picture of AI on the shop floor, see manufacturing and artificial intelligence.
How we build it
- Planner workshop. We sit with your planner and production manager, go through a real week's plan and write down every rule, including the ones nobody has written before.
- Scope and fixed price in writing. Which resources, which rules, which integrations and what the first phase leaves out, signed before work starts.
- First version on your data. Your machines, routings and last month's orders, so the scheduler's draft can be compared with the plan the factory actually ran.
- Parallel planning. For a few weeks the planner plans the usual way and checks the scheduler's draft beside it. Rules are tuned until the planner trusts it.
- Release to the floor. The schedule goes out to tablets at the machines, floor reporting starts, and the numbers recorded at the start are measured again.
You own it
As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your company's name, running in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team. For the wider build, see custom software development; to decide between building and buying first, see software consulting. For the shift rosters of the people on the line, see employee scheduling software. For orders, purchasing and invoicing around the plan, see ERP systems for small business. See prices.
Questions we get
Do we need an ERP before we can have production scheduling?
No, but scheduling needs orders, routings and stock from somewhere. If you have an ERP, the scheduler reads them from it. If you do not, the first phase can hold orders and routings itself and grow into a light manufacturing ERP later.
Will the software decide the schedule on its own?
It drafts the schedule by your rules and shows why each order sits where it does. A planner reviews it, moves what needs moving and releases it to the floor. When a machine stops or a rush order comes in, the planner asks for a new draft and compares it with the current plan before accepting.
How do you handle changeover times that depend on the order sequence?
As a changeover table: the time to go from one product, colour, material or tool to another on each machine. The scheduler uses it to group similar work and avoid long changeovers, and the planner sees the total changeover time of each draft.
Can operators report progress from the floor?
Yes. Operators start and finish operations, report quantities, scrap and stops on a tablet at the machine or a phone, or the data comes from the machine itself where it has an interface. The schedule updates from those reports.
Our planner does this in Excel. Is that a problem?
It is where most of our scheduling projects start. The spreadsheet usually holds the real rules: which jobs can share a machine, which operator runs which line, what the customer will accept late. We write those rules down with the planner and they become the first version of the scheduler.
Who owns the software?
Your company. The source code is in a repository in your own account, and the database and hosting are in your company's name. You can keep us for maintenance, run it yourself or hand it to another team.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.