Process Model

The Process starts as soon as the order is confirmed in Dialogflow (via REST API). The order has to be timely displayed in the kitchen so the preparation of the order can start, to ensure that it is finished as soon as the customer arrives.

Start: Guest confirms his order in Dialogflow

Task: Display order in the kitchen

The order has to be displayed in the kitchen. This will eventually be done with a large display in the kitchen listing the orders and the time they have to be ready to serve.

Intermediate Event:

The customers scans the QR code generated for his order in the restaurant signaling his arrival.

Task: Serve drinks

Drinks usually get served first, so they will be sent out immediately

Task: Serve food

After a short period of time, the food will get served, so the guest has a minimum amount of waiting time, giving him enough time to arrive and settle down with a sip of his ordered drink.

Intermediate Event: Customer finished the meal

When the customer has finished his meal and leaves (eventually this will use GPS; as soon as the customer is further than 200m away from the restaurant (preventing minor GPS drifts to be noticed)) the seat is available for the next booking.

Deployment

The task got started after a confirmation for an order has been done. Deployment in Heroku