Capacity

Which work centre is holding the plan up, how much time it would take to fix, and which orders that would move.

The Capacity page answers three questions in order: which work centre your late orders are queueing for, how much more time it would take to clear them, and which orders that time would actually move. The second and third answers come from running the scheduler again, not from a formula.

The work centre table

  • Load — working hours used against hours available, over the period you choose.
  • Used h and Free h — the same thing in hours, because “how much room is left” is a number of hours, and a percentage cannot answer it for a work centre standing idle.
  • Queued h — work assigned here that has not started, anywhere in the plan.
  • Waiting caused — hours late orders spent waiting for this work centre while it was busy with something else.
  • Late orders — late orders with at least one step here.

Load, used and free follow the period selector. Queued, waiting and late orders cover the whole plan: an order that misses its date in four months is still waiting for the same work centre.

Waiting is not the same as blame. It is counted in the work centre's own working hours — nights and weekends are not its doing — and only for the part of the wait when it was occupied. An order held up by a missing component is not the fault of the machine standing idle waiting for it. Even so, waiting measures a queue, not lateness; the trial run below is what tells you whether relieving that queue changes any dates.

How much would it take

Pick a work centre. You set how the extra time is added — weekend shifts or longer days — and for how many weeks, because a plant runs Saturdays until October, not forever. The dates the arrangement covers are shown, and the hours exist only inside them.

Work out how much then runs the plan at rising amounts of added time and stops when two steps in a row buy nothing. Each row reports how many orders are still late, the on-time percentage, and what the whole arrangement costs in hours. You can also type a number in yourself and run just that.

The answer comes back in one of two forms, and the second is the more useful one:

  • +18 h a week for 6 weeks — late orders 214 → 152.
  • More hours here do not clear anything. They are waiting for Edge Banding Machine.

The second saves you buying a shift that changes nothing. It happens because clearing one queue moves the constraint to whatever is next — which is also why a row that barely moves is a real answer rather than a failure.

Somewhere else for the work

Alongside more hours you can let some of the work go elsewhere: a second machine of the same kind, or a work centre APS proposes because your own routings already run the same operations on both. The proposal is read off your history, not guessed — but the same operation name is not proof of interchangeability, and only the shop knows whether “Cut” on one machine is the same cut as on another.

Both are what-ifs. Nothing here is written to Odoo. To keep an arrangement, add the shift to the work centre's calendar in Odoo, or set the other work centre as an alternative on it, and sync.

Which orders it moves

Pick a row in the results to see the orders behind the number: order and sale order, the date it finishes before and after, and how many days it moved. Orders that stop being late are marked, and so are the ones the reshuffle sets back — hiding those would make every trial look like a free win.

Days are counted between the dates shown, not between timestamps, because a job that moves from Tuesday afternoon to Sunday night has moved two days in the only sense a planner reads.

APS 4 Manufacturing

Built by Avalah

Odoo Gold Partner

APS 4 Manufacturing

Built by Avalah

Odoo Gold Partner