Keystone Feature
Production planning and finite scheduling
Capacity is limited by the machine and by whoever is rostered to run it. The schedule accounts for both.
The problem it solves
The schedule says a job will finish on Thursday. It assumes the machine runs three shifts and nobody is on holiday.
Subcontract operations sit in the routing and inflate the loaded figure on the capacity board.
When the board says a machine is at 0% and the planner knows it has a hundred hours against it, the board stops being used.
What you get
- 01
Plan against real capacity — Schedule to work-centre calendars rather than assuming every machine runs every hour.
- 02
Account for who is on shift — Capacity narrows to the hours somebody is rostered to the machine, with unattended running counted separately.
- 03
Spot the machine nobody is on — See lost hours and double-booked operators before the week starts.
- 04
Keep subcontract off your board — Outsourced operations do not inflate your own loaded hours.
Detail
Plan against the shift you actually run
Where a rota has been imported from your planning system, that is what narrows the calendar. The board says which rota it used.
A board the planner will trust
The loaded figure on the board and the hours against the job agree. Where they disagree, the board reports which source it used.
Build a plan before it takes capacity
Works orders can sit as drafts before machine allocation, so a plan can be built and looked at before it takes capacity.
Next step
Show us how your factory runs
A walkthrough starts with your orders, your production flow and your material problems. We follow one of your jobs through the system rather than presenting a feature list.