See what a change does before you accept it.
The schedule is built per line, team and machine, together with the orders that are waiting. When you move something or a stoppage appears, its effect on the schedule is immediately visible, so the decision is made with the consequence in view.
What it solves
A schedule per line, team and machine
Real capacity is visible, not assumed. You can see where another order fits and where it does not.
The effect of a change, before the decision
You move an order and see what shifts behind it. The choice stays with the planner; the system shows the consequence, it does not decide instead.
Planned stoppages share the same calendar
Scheduled maintenance takes machine time, like an order does. The overlap is not discovered on the morning of the intervention.
Waiting orders, with the reason for waiting
You see what is waiting on material, what on capacity and what on a customer decision. Prioritisation starts from the reason, not from the order’s age.
The current week, per line, with a planned stoppage.
| Interval | Line | Load | |
|---|---|---|---|
| Mon – Tue | Line 1 · cutting | C-240, C-241 | Full |
| Wednesday | Line 2 · painting | Maintenance U-07 | Planned stoppage |
| Thu – Fri | Line 2 · painting | R-302 | Scheduled |
| — | Waiting | P-118 | Waiting for material |
Wednesday’s stoppage comes from the maintenance plan; it was not entered separately.
demo dataRelated apps
Want to see the app on your own flow?
We arrange a demo on your company’s actual case. The app above comes preselected in the form.