Production scheduling software decides what gets made next, on which machine, in what order and by when, using the capacity, materials and people you actually have. CodeFish builds it for the operations, planning and leadership teams at Australian manufacturers whose real schedule still lives on a whiteboard or in one person's head. Unlike a plan, it takes feedback from the floor and resequences what is left when a job runs long or a machine goes down. Sales quotes dates the plant can hold, and the week stops being rebuilt every morning.
Production Scheduling Software
Production scheduling software means the promise date is a calculation, not a guess someone makes on the phone.
Types of production scheduling software
Most plants already run two or three of these. The schedule breaks in the gaps between them.
ERP and MRP planning
Pronto, MYOB Advanced, SAP Business One and Business Central plan what to make and buy, usually with infinite capacity. You get the demand, not a sequence the floor can run. See [ERP integration](/enterprise-integration/erp-integration).
Advanced planning and scheduling (APS)
Finite capacity schedulers like Siemens Opcenter APS (formerly Preactor), PlanetTogether and Asprova. Strong when routings are accurate and your rules fit their model.
Manufacturing execution (MES)
Records what actually happened on the floor, job by job. It gives the schedule the feedback it needs to stay true. See [MES](/enterprise-integration/mes-manufacturing-execution-system).
Shop-floor job tracking
Start, finish, quantity and downtime captured at the machine in a scan or two taps. The smallest piece that turns a plan into a live schedule.
Capacity and S&OP planning
Months ahead rather than hours: whether the plant can make what sales expects to sell. See [sales and operations planning](/enterprise-integration/sales-and-operations-planning).
Spreadsheets and whiteboards
Where the real rules usually live. Writing them down is the first step, whatever you buy or build, so the schedule survives the scheduler's leave.
What production scheduling software has to do
Six jobs. A scheduler that does the first three and not the last three produces a plan the floor ignores.
Schedule against real capacity
Machines, tooling, skilled operators and shifts — the constraints that actually limit output. Infinite-capacity planning is why an ERP schedule and the floor disagree, and why the whiteboard survives alongside it.
Sequence for changeovers
Grouping jobs by colour, material, tooling or temperature to avoid a setup is often the largest available gain on the floor, and it is the reason an experienced scheduler beats the system they were given.
Check materials before promising
A job scheduled without the stock or the incoming delivery behind it moves the problem to the floor and turns the schedule into fiction. Availability has to be part of the decision, not a check done afterwards.
Give a promise date
Sales needs a date at the time of the quote, calculated from what is already committed. This is the feature that changes how the business sells, and it is usually the one that justifies the project.
Take feedback from the floor
Job start, job finish, quantity good, quantity scrapped, downtime reason — captured at the machine. Without it the schedule drifts from reality within a shift and everyone goes back to asking.
Reschedule without starting over
Breakdowns and hot jobs are normal. The test of a scheduler is what happens at 6am when a machine is down: it should resequence what is left and show what moves, not require a person to rebuild the week.
How is production scheduling different from ERP and MES?
ERP decides what to make and buy. MES records what happened on the floor. Scheduling sits between them and decides the order things run in.
Most ERP planning modules assume unlimited capacity, which is why the spreadsheet survives next to them. The fix is rarely a new ERP. It is a scheduling layer between the two that knows your constraints.
Should we buy scheduling software or build it?
Buy when your constraints are ordinary: discrete jobs, set machines and clean routings, where an APS tool configured to your plant gets there faster and cheaper. Build when the sequencing rules are how the plant makes money, like shared tooling, curing times or one constraint that governs everything, and the tool would have to be fought. Often the first step is neither: fix the routing data, prove the rules in a small tool, then decide. You spend on the scheduler once you know it will beat the whiteboard.
How much does production scheduling software cost?
Data quality drives the cost more than the scheduling logic.
Start with a $9,000 workshop
A fixed $9,000 + GST Rapid Insight Workshop on your floor. We write down the sequencing rules nobody has documented and say what to build, buy or fix first.
Data drives the price
How accurate your routings and run times are, and whether the floor can report progress today, matter more than the scheduling logic.
Fixed-price builds
A defined build is quoted fixed-price as an Amplify project before it starts.
Apex when the plant keeps changing
Where the product mix keeps shifting, an Apex partnership keeps the rules matching the work.
How a scheduling project runs
Write down the rules
We sit with whoever builds the schedule now and record every rule they apply without thinking about it — what can share a setup, what cannot run overnight, which customer never waits. This is the asset the project is really built on.
Close the feedback loop first
Job progress capture at the machine goes in before any scheduling logic, because a schedule with no feedback is a plan. It is deliberately small: start, finish, quantity, reason for a stop.
Schedule one cell, then extend
The rules run against one work centre or one cell alongside the current whiteboard, and the two are compared for a few weeks. The schedule takes over when it is beating the whiteboard, not on a go-live date.
How we deliver manufacturing software
Web App Development
Web application development services for internal tools, customer portals and SaaS products. Built in Adelaide to a fixed price, with a one-year warranty.
CTO as a Service
A fractional CTO — a senior technology leader part-time, owning your roadmap, managing your developers, and making the calls that cost real money when they go wrong.
Rapid Insight Workshop
We map how your business really runs — systems, costs, friction — and return a prioritised roadmap with a business case. $9,000 + GST, fixed.
Systems Integration
For operations businesses running five or more systems. We connect your ERP, CRM, warehouse and field systems so nobody retypes data, and keep them connected as a long-term partner.
Production scheduling questions we get asked
They usually are, and it is the most common reason a scheduling project fails. A scheduler is only as good as the run times behind it, and in most plants those were entered once, years ago, and have never been corrected. The fix is not a better algorithm — it is measuring the real times on the jobs that matter most and accepting a rough schedule that improves as the data does.
They become the person the system learns from, and the project fails without them. A scheduler who is treated as the thing being replaced will withhold the rules that make their schedule work, and those rules are the whole asset. The measure of success is that the schedule survives them taking annual leave, not that they leave.
Only if it takes seconds. Capture at the machine has to be a scan or two taps — start, finish, quantity, a reason code for a stop — and it has to be on a screen that survives a factory floor. Ask for more than that and the data arrives at the end of the shift, entered from memory, which is worse than no data at all.
Not necessarily, and not first. MES records what happened on the floor in detail; scheduling decides what happens next. Scheduling needs only a thin slice of that record — job start, finish, quantity and downtime — which can be captured directly. Buy the full MES when the questions you cannot answer are about quality and machine performance rather than sequence.
Three to eight weeks to have feedback capture and one work centre scheduled, once the rules are written down and system access is available. Running the whole plant on it takes longer, and should — each cell added is a new set of rules to prove against the whiteboard before it is trusted.
Yes, and for most manufacturers that is the change worth paying for. A promise date calculated from what is already committed lets sales quote with confidence and stops the plant absorbing dates it never agreed to. It only works when the floor is reporting progress, which is why the feedback loop is built before the promising.
Four things: they spend time on the floor before quoting; they write down your sequencing rules rather than importing someone else's; they tell you when your data has to be fixed first; and they build the feedback capture before the clever scheduling. A partner who demonstrates an optimiser before asking how you sequence a changeover is selling, not scoping.