1. Help Center
  2. Kitchen display (KDS)
  3. Using KDS

Demo: Two KDS devices with Pass and Info

This article demonstrates an advanced scenario of two Kitchen Display System (KDS) devices working in sync. 

Info

In this scenario, there are two Stations with their own screens in the kitchen:

  • Grill section with Grill screen.
  • Dessert/Salad station with Salad screen that is also in charge of Pass, meaning completing and sending orders.

Restaurant uses three Courses:

  • Appetizers
  • Main courses
  • Desserts

This scenario uses the following advanced functionality:

  • Summary: Enables the users to have an overview of all products in all active PrepTickets.
  • Pass: Enables information to be synced across several KDS screens. 
  • Transit: A view where tickets are placed between courses. Tickets are moved to Transit automatically when a single course on a PrepTicket is complete. 
  • Info: Enables the users to be aware of which orders are served together with other stations.
  • Courses: Enables the tickets to appear when certain courses are requested, otherwise they are out of the view (for more info, check out Working with Courses).

This represents, for example, a small pub restaurant. 

KDS PrepTicket (with courses)

For description of basic info on a PrepTicket, check out Demo: Single Kitchen Display Screen (KDS) device.

  • PrepTicket in this scenario looks like this:
  • Following info is displayed:
    • Orange Preparing button (changes order status to Preparing)
    • Green Prepared button (changes order status to Prepared)
    • Red Transit button (moves PrepTicket to Transit)
    • Current Course active
    • Product Course info
    • Course groups
    • Info property (representing the fact that this product is served by a different station)
       

KDS Views

This advanced scenario uses the following views:

Active

Displays all PrepTickets that are not in Transit or in History. 

Active view is represented by a gray background:

MyActive

Displays only PrepTickets that require an action from the station. MyActive is represented by a beige background:

Observe that table 3 is not visible in MyActive as opposed to Active above, since its active course is Appetizer and there is nothing Grill Screen needs to do with it. 

To switch between Active and MyActive select the "ACTIVE" word at the bottom of the screen.

Transit

Displays PrepTickets whose last course is completed, that are waiting for next course to be requested. Transit is represented by a green background. 

To switch to Transit view, select the "TRANSIT" word at the bottom of the screen.

History

Displays completed PrepTickets, together with Activated and Closed time. 

To switch to History view, select the "HISTORY" word at the bottom of the screen.

Workflow

  • The following is ordered in Domino on POS device:
    • Appetizer: 1 Caprese Salad (Salad) and 1 Grilled Asparagus (Grill)
    • Main Course: 1 Fish & Chips (Grill) and 1 Mushroom Carpaccio (Salad)
    • Dessert: 2 Lava cakes (Dessert)

  • Let us assume Grill is using MyActive and Salad is using Active view. Both screens display the new order and each screen sees what the other screen needs to do on the same course (as info):
Salad Screen Grill Screen
  • Users select the red Transit button to move the ticket to Transit until Appetizer course is requested:
  • Transit count is updated to 1:
  • Waiting staff requests next course in Domino on POS device and tickets reappear on the Salad screen. Nothing is displayed on Grill screen since only Salad station has products in this course:
Salad Screen Grill Screen
  • Users select the "Next course AP" (Appetizer) notification to have it disappear. 
  • Passage of time is represented by a time counter and a color bar that slowly changes color to red as time goes by (color duration can be configured individually):

  • Salad chef selects the Preparing button to set the status to Preparing.

  • The change is reflected on the ticket:
Salad Screen Grill Screen
  • When the Appetizers are complete, Salad chef selects the green Prepared button:

  • Ticket is moved to Transit automatically:

  • Next course is requested by waiters (Main course) and "Next course MC" message is displayed on Grill and Salad devices: 
Salad Screen Grill Screen
  • After tapping away the "Next course MC" message, Grill screen sees its orders. 
Salad Screen Grill Screen
  • Grill chef selects the Preparing button to set the status to Preparing.
  • The change is reflected on the Salad Screen:
Salad Screen Grill Screen
  • When the Main courses are complete, Grill chef selects the green Prepared button:
  • Ticket is moved to Transit automatically. 
  • Next course is requested by waiters (Dessert) and "Next course DC" message is displayed on Salad display since there is nothing in this course for Grill station: 
Salad Screen Grill Screen
  • After tapping away the "Next course DC" message, Salad screen sees its orders. 
Salad Screen Grill Screen
  • Salad chef selects the Preparing button to set the status to Preparing.
  • The change is reflected on the Salad Screen:
Salad Screen Grill Screen
  • When the Main courses are complete, Grill chef selects the green Prepared button:
  • The PrepTicket is moves to History view automatically:

Summary

If at some point users would like to get an overview of all orders in their different states, they can use the Summary function. To open the Summary window, select the Summary button in the lower right corner of the screen:

Summary displays all products relevant for the station according to their PrepStatus:

 

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request