Skip to main content
Log2MapLog2Map

Process Mining

Where orders wait

Find the slowest frequent edge. On this file it is Preparation → Order handoff — a candidate to inspect, not a proven kitchen fault.

Waiting time needs a timestamp. This file has one on every row, so Performance and Bottlenecks can run.

Open Performance and find the slowest transition. Right-click that edge for Cases, Transitions, and waiting time.

Check your result. The edge Preparation → Order handoff should stand out. Median in the file is 46 minutes (range 24–71). The longest case is PIZZA-025 (71 minutes on that edge, 112 minutes end to end). PIZZA-001 is 70 minutes on that edge, 102 minutes total.

That gap is timestamp(handoff) minus timestamp(preparation). There is no Event End, so the number includes cooking as well as any wait to leave the counter. Treat it as a place to look, not as proof that the kitchen is idle.

Early app steps are short. Handoff → Order received is courier travel or the pickup desk — real, but shorter than the kitchen edge on the slow orders. Process quality will not show payment loops; payment completed once.

Find the kitchen edge

Open Performance or Bottlenecks and select Preparation → Order handoff. Compare one delivery case with one pickup case. Which wait is larger, and what else besides a queue could explain it?

Reference in Docs