How to choose manufacturing scheduling software

Draw the category boundaries first, then shortlist. What counts as production scheduling software, what "free" really covers, and how to prove value on your own job list before you commit any budget.

Orkyo · Published

Search for manufacturing scheduling software and you get ranked lists of fifteen vendors, most of which mix MES platforms, ERP modules, APS optimisers and staff rota tools into a single pile. That is why people keep re-searching the same phrase: the lists never answer the question, because the entries are not comparable.

This is the version that draws the category boundaries first. It names no vendors, because category fit decides the outcome long before brand does. We build one of these tools, and there is a section near the end saying where it fits and where it does not — read it with that in mind.

What production scheduling software actually does

The core job is narrow: put jobs onto the machines, people, and tools that run them, in one plan everybody reads.

Four neighbouring categories share the vocabulary and solve genuinely different problems.

  • MES / shop-floor control tracks execution. It collects signals from machines and reports progress operation by operation. It does not decide next week’s plan.
  • ERP / MRP plans materials, orders and money. Its scheduling module generally assumes you already run the rest of the suite.
  • APS / fine scheduling sequences operations to the minute and optimises the order. It needs accurate run times to earn its keep, and most shops do not have them.
  • CMMS plans maintenance work orders against assets. It schedules repairs, not production.

Two more turn up in these searches and fit no shop at all. Shift and rota tools plan people rather than jobs, and know nothing about machines or setups. Generic scheduling software built for appointments and field service has no concept of a double-booked machine.

There is a quick test that resolves most of it. If the tool cannot show a machine and the operator qualified to run it in the same plan, it is not production scheduling software, and no amount of configuration will make it one.

Why there is no agreed “best”

Because the market splits three ways, and each part is genuinely best for a different shop:

  • ERP add-on modules, for shops already committed to the suite.
  • Heavyweight APS and MES suites, for repetitive line production at volume.
  • Standalone schedulers, for shops sitting between the spreadsheet and the ERP.

Two questions settle which part you are shopping in.

What is your mix? High-mix, low-volume work routes every job differently, and the plan is rebuilt constantly. Repetitive line production runs the same path every time, and the interesting problem is sequence. These are not the same tool.

What granularity do you actually need? Day-level planning answers what runs where this week. Minute-level optimisation sequences a line. Buy minute-level optimisation only when sequence is genuinely your constraint — and be honest about that, because it is the most common expensive mistake in this category. Plenty of shops buy an optimiser when the real problem is that nobody knows which machine is booked twice on Thursday. Optimisation cannot fix a plan nobody can see.

Once you know the part of the market, compare on the things that actually differentiate:

  • Resource types beyond machines — benches, fixtures, forklifts, and the people who hold the qualifications.
  • Conflict detection at the moment of booking, rather than on a report the next morning.
  • Utilisation per resource, so the bottleneck is measured instead of argued about.
  • Multi-site, if you run more than one.
  • Setup and changeover time, if it is a real share of your day.

The free question, answered directly

Roughly half the searches in this category ask for a free option, and most vendor content skates straight past that to a demo request. It deserves a straight answer.

Free takes four forms, and they are not equivalent:

  1. Spreadsheet templates. Genuinely free, flexible, immediately usable. Ours are here: capacity planning and the job-shop version.
  2. Free tiers of paid tools, usually capped by users or by resources.
  3. Free tiers of general project tools. These schedule tasks, not machines, and fail the test above.
  4. Open-source APS projects. Free to licence, expensive to run. Budget engineering time, not licence cost.

The spreadsheet deserves more credit than vendors give it. It costs nothing, everyone can read one, and it encodes the planner’s judgement without a configuration project. If it is working, keep it.

It fails in four fairly specific ways, and they are worth recognising early:

  • One person owns the file, and the shop works from a printout that is already stale.
  • Conflicts stay invisible, because two jobs on one machine are just two adjacent cells.
  • A rush job means rebuilding everything behind it by hand.
  • There is no utilisation data, so the bottleneck stays a matter of opinion.

Before calling it free, count the planner’s hours each week, the scrapped setup from a double-booked machine, and the risk carried by a single file on one laptop.

The switch point is recognisable. Watch for three signals: more than one person needs to change the plan, more than one site needs to see it, or the schedule gets rebuilt by hand more than once a week. When two of the three are true, the spreadsheet has stopped being the cheap option. We wrote that moment up in full in Outgrowing the machine-shop Excel schedule, including the case for staying put.

Prove it before you pay

Run a one-week test on real data. Take last month’s job list, load it into a trial, and count the conflicts the tool catches that your spreadsheet missed. That number is the business case, and it costs nothing to produce.

Worth asking before a demo:

  • Can I model my own resource types, including fixtures and benches?
  • Can I see one plan across two sites?
  • What happens when two jobs claim the same machine?
  • What does the operator on the floor see, and does that seat cost extra?
  • How long does a shop my size take to get its jobs, machines and qualifications in?

Four things are reasonable red flags: an implementation project measured in months, per-user pricing that punishes giving the shop floor read access, a mandatory ERP integration before anything works at all, and no trial on your own data.

Where Orkyo fits, and where it does not

Orkyo is a standalone scheduler in the sense above, aimed at shops of roughly 10 to 250 people planning at day granularity. It books machines, qualified people and tooling in one plan, and reports a conflict when any one of them is already taken.

It is deliberately not an MES, an ERP module, an APS optimiser, or a CMMS. If you need minute-level sequencing on a line, or execution tracking from the machines themselves, one of those categories is the right answer and we are not it. The boundary is written out in full on what Orkyo is not.