Skip to content

Planning

Conflict detection: see at once what no longer fits

When one work step moves, the dependent dates move with it — in every plan. Whatever no longer fits, the conflict engine reports immediately from the Pro plan, with a suggested fix.

No credit card · trial ends automatically · servers in Frankfurt

Gantway Conflict Engine — Gantt with red markings for conflicts

How you work with it

The cutting takes two days longer — in Gantway, edge banding, assembly, and delivery move along on their own, because every task knows its dependencies. You immediately see what the lost day means at the end of the chain, instead of tracking it by hand — that is included in every plan, Business too. From the Pro plan, the conflict engine also checks six conflict types after every change — from double booking through material shortages to vacation in the middle of an order — and recalculates only the affected section, not the entire plan. The result appears practically instantly in the conflict list: classified by urgency (P0 to P2), with a plain-text description and a concrete suggested solution — for example, which employee would be free instead. And whatever you deliberately accept, you acknowledge with a reason: it reappears only when the situation changes.

Dependent dates follow automatically — in every plan

Every task knows its predecessors. When a work step is delayed, Gantway moves the dependent steps along with their team and machine — the whole chain up to the delivery date recalculates in one go. You correct one date, not twelve. This is included in every plan, Business too; you set the dependencies on the item in the order.

  • Every task knows its predecessors
  • Team and machines move with the date
  • The whole chain up to the delivery date recalculates in one go
  • Included in every plan, Business too

Dependent dates follow automatically — in every plan

Visibly marked in every view

Conflicts are shown in the Gantt as red dashed lines, in the board as red badges on the tasks, and in the conflict list as a sortable table.

  • Red dashed lines in the Gantt
  • Red badges on tasks in the board
  • Sortable conflict list

Visibly marked in every view

Also included

Spot double bookings, overload and shortages

From the Pro plan, the engine reports six conflict types — desk overbooking, station overload, employee double booking, employee on vacation or absent, violation of task dependencies, and material shortage. For each type, the planner immediately sees exactly what collides.

  • Overbooking, station overload, double-booked employees
  • Vacation or absence in the middle of an order
  • Broken dependencies and missing material
  • From the Pro plan

Sorted by urgency

P0 (within 2 working days) — immediate action required. P1 (within 14 days) — plan this week. P2 (later than 14 days) — monitor. Color-coded in the conflict list and on the affected tasks.

  • Act now: conflict within two working days
  • Plan this week: within 14 days
  • Keep an eye on it: anything later

Results instantly, even with hundreds of tasks

After every change, the engine does not recalculate the entire plan, only the section the user is currently working on — for example, the single order. The result appears practically instantly, even in workshops with hundreds of tasks.

  • Only the section you are working on is recalculated
  • Result appears almost instantly, even with hundreds of tasks

A suggested fix for every conflict

Every conflict contains a detailed description and a concrete suggested solution — for example, which other employee is free, or which other slot would have capacity.

  • Plain-language description for every conflict
  • Suggestion of which employee or slot would be free

Accept a conflict knowingly, with a reason

If you want to deliberately accept a conflict, you acknowledge it with a short reason. It is hidden, but reappears automatically as soon as the plan for the affected order is changed. So clicking it away is not a permanent way of ignoring it.

  • Acknowledge with a short reason
  • Reappears automatically as soon as planning on that order changes

Warning when a qualification is missing

In addition to the conflict engine, the system checks when a task is assigned whether the selected employee has the required qualification. If it is missing, a warning appears. The planner deliberately decides whether to accept it — no hard block.

  • Checked when a task is assigned
  • A warning, not a hard block — the planner decides

Typical situations

  • The cutting is delayed by two days: You enter the delay on a task. Edge banding, assembly, and delivery move along automatically — including the assigned people and machines, in every plan. You immediately see whether the delivery date still holds, and you call the customer before they call you.
  • Prevent double booking: You drag a task to a slot that is already occupied. The engine warns immediately and suggests free slots.
  • Spot a material shortage early: An order needs 50 m of edge banding, only 30 m are in inventory, and no order is on its way. A P1 conflict appears, and the purchase order is triggered before the job starts.
  • Secure vacation planning: An employee requests vacation for next week. The engine checks which tasks are planned for them during that time and reports them as a conflict — before the vacation is approved.

See conflicts before the workshop does

With your own orders, no credit card. Or bring a current order to a 30-minute call.