Skip to content

Manufacturing

A bad production schedule costs you three ways: overtime, wasted changeovers and missed delivery dates. One model plans every production line together and keeps every rule.

  • Free 30-minute call
  • No commitment
  • You own the code
Typical decisions
production scheduling
What you gain
A new schedule for every production line as soon as an order moves
First step
A free 30-minute call

Typical problems in manufacturing.

You juggle setups, shared tools, maintenance and due dates in a spreadsheet. Every rush order means rebuilding the week by hand.

Changeovers eat your day

The production line makes part A, then part B, then part A again. Every switch means retooling the line, and no parts come off it meanwhile.

Orders swing, your schedule does not

A key customer doubles an order on Tuesday. The schedule you made for a steady week no longer works the same afternoon.

Maintenance gets squeezed

Planned downtime is cheaper than a breakdown. Yet you keep moving the service date because production comes first. In the end, the service falls in the week of an important delivery.

One machine holds up the plant

Jobs queue at one bottleneck machine while two other production lines have no work. By hand, you rarely manage to spread the jobs evenly.

In short: A manufacturing scheduling optimisation sequences every job on every machine and production line with a mathematical model. It decides what runs where and when. It works around setups, shared tools and maintenance, so overtime, changeovers and late orders stay low.

What a hand-built production schedule costs

On Wednesday at 2 pm, a rush order lands. You open the spreadsheet and start moving jobs. One move has two effects: a changeover now falls into the night shift, and maintenance moves to next week. A changeover is the time you need to retool a production line from one part to the next. By Friday the production line runs overtime, and two delivery dates have slipped.

Many plants say a model won’t work for them, because of changeovers, changing demand and maintenance. We call them the reason to build one. Each of these comes with rules, and you can only keep a few rules in mind at once. You check the rest late or not at all. Then you pay in overtime, extra changeovers and missed delivery dates.

What changes on the shop floor

Today, you rebuild the week by hand whenever an order moves. Our model proposes a new schedule for every production line, with every rule built in. Fixing one bottleneck no longer creates the next, because the model plans all lines together.

You judge each schedule by figures you already track: overtime, changeover hours and on-time deliveries. Overall equipment effectiveness (OEE) shows how much planned machine time turns into good parts. You get a schedule the shop floor can run, and your customers get the dates you promised.

Job shop and flow shop scheduling for every production line

In a flow shop, every job visits the same machines in the same order. In a job shop, each job takes its own route through the plant. Our production scheduling covers both. It also covers three related tasks. Batch scheduling decides which orders you make together. Changeover minimisation finds an order of jobs with as little retooling as possible. Capacity planning shows how much you can make with your machines and shifts. The core is sequence-dependent setups: the retooling time depends on which part ran before. Switching from part A to the similar part B is quick. Switching to the very different part C takes much longer. So the order of jobs decides how many machine hours you lose to retooling.

The model keeps the makespan short. That’s the time until the last job is finished. It also limits tardiness: how many days orders finish after their due date. We often write it as a mixed-integer linear program (MILP), a standard maths form for yes-or-no choices.

Should the model also choose your shift pattern?

Most scheduling software takes the shift calendar as fixed. Yet a night shift or a third shift is a big step, and you have to prepare it months ahead. You have to find the people, win over the team and pay the night premiums. So the step has to pay off. We calculate weeks with two shifts and weeks with three shifts side by side. You see how many more orders the third shift lets you finish and what it costs, before you commit to it.

How a project runs.

Each of the three phases ends with something you can check before we go any further.

  1. Understand

    We start with your operation. What do you plan, where does it go wrong, and what would a better week look like? Then we tell you straight whether optimisation can help, and sometimes the answer is no.

    • A written assessment
    • A clear go or no-go
  2. Model

    We write your decisions, goals and rules into a mathematical model, which is just a precise description of how your operation works. Then we run it on your own data. You see side by side what each plan costs and what it delivers, and pick the one that fits your priorities.

    • A documented model
    • Results on your own data
  3. Implement

    We test with your data and go through the results with your team. Once they trust it, we connect the model to your systems, so it runs every day without anyone stepping in by hand.

    • Source code and documentation
    • Training for your team

Common questions.

Something else? Ask us directly.

Because Excel is flexible, and you already know it. The trouble starts when the sheet has to check setup times, shared tools and due dates for every move. It can store those rules, but it can’t weigh them against each other. A model can, and it can still export to the sheet you like.

A setup matrix lists the changeover time from every product to every other product. You need one as soon as the order of jobs changes how long you clean or retool. Most plants already have the numbers. Some are in shift reports, and some only in your head. Collecting them is often the first useful step.

Your ERP plans materials and usually assumes unlimited machine capacity. Advanced planning and scheduling (APS) tools sequence jobs against the hours your machines can run. If you lose money through a poor order of jobs and many changeovers, this extra planning pays off. If your rules are unusual, a model built for them fits better than standard software.

It depends on the problem, so we agree the timeline with you up front. Every project starts with a diagnostic, a short look at how you plan today. It shows which data, how much time and what budget a model for daily use needs. Only then do you decide.

No. We connect to your ERP, your warehouse management system or your planning spreadsheet. We build the model only for the planning that gives you trouble today. Your systems keep running as before.

Almost nobody’s data is clean. The diagnostic shows what the model needs and what’s missing. Then we build the model to cope with messy data.

Off-the-shelf tools are built for many companies at once, so they don’t know your special rules. We build a model that follows exactly your rules. Then we hand it over, and your team owns it.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go