Production scheduling software that plans inside real capacity.

The Scheduling Engine builds one ranked plan from open orders against your machines, shifts and changeovers. Rerun it when the day changes. That is APS without the spreadsheet.

Book a demo All solutions
  • Plan v41, Monday Line 1 Sequenced Line 2 Resequenced Line 3 Sequenced
  • Plan check Capacity clear Changeovers read from the matrix Shift calendar applied

Some of the people we've built with

  • Plan v41 committed 06:10Orders ranked against capacity, every change logged
  • Jobs at risk this week 2

The plan was fine on Friday. By Tuesday a machine is down and the real schedule is on a clipboard.

Plan every job against the hours you really have.

Old way

the schedule is a spreadsheet someone rebuilds by hand every Friday.

New way

open orders come in from your ERP, and the Scheduling Engine ranks them across your machines, shifts and changeovers.

  • You review it, commit it and rerun it when something changes. Work that has already started stays where it is.

The Modules that build the plan

How open orders become a plan you can commit

Each Module does one job, in this order.

1 It connects

  • ERP
  • Line PLC

2 What runs, and what it does

  1. Asset RegistryHolds the lines, cells and machines the plan is built on.
  2. Integration HubKeeps your ERP connected and logs every message. mode40 wires the connection with your team.
  3. Scheduling EngineRanks every open order against your machines, shifts and changeovers. Run it, review it, commit it.
  4. Demand PlannerHolds the forecast and projected inventory beside the schedule, so you can see what is coming.
  5. PlannerChecks every 30 minutes for jobs that will not finish on time and proposes the moves.
  6. Approval QueueMoves outside the Planner's authority wait here for a yes.

3 What you get

  • Plan v42 proposed Commit plan Discard

In customer plants, downtime fell 86% and shorts went from 50 a month to 12.

Real plants, real numbers, first in manufacturing.

  • less downtimeacross seven production facilities 86%
  • customer shorts a monthwithin six months 50 to 12
  • longer planning horizonin a customer deployment 50%
  • facilities on one installationrun by one customer 19
Where these numbers come from

These numbers come from customer deployments, first in manufacturing. We don’t name customers without asking them first. If you want to talk to a customer, ask us and we’ll ask them.

  • Planning issue: Weld Line 1 over capacity Thursday
  • Scenario SC-0207 Commit plan Discard

A plan built from your own constraints

The plan uses the lines, shifts and changeover times your plant really has. mode40 sets them up with you during implementation, and your own people change them after. mode40 was started by people who ran plants before they wrote any software.

  • Changeover time read from your own changeover matrix
  • Parallel-job capacity on each asset and percent of capacity on each shift
  • Shift calendar and planned downtime
  • Batch, continuous-flow and maintenance work ranked for the same hours
  • Sequencing rules and planning priorities you set
  • A what-if scenario runs on the same capacity math as the live plan

Related use cases and systems

FAQ

Bring Friday's schedule and Tuesday's reality.

30 minutes on one line's schedule and what changed by Tuesday. We'll show you the plan the Scheduling Engine would have built.

Book a demo See the Scheduling Engine