Restaurant Enterprise Series

Conversational Ordering Mode

Information and
Configuration Guide

General Information

About This This document provides background information regarding the RES
Document Conversational Ordering Mode as well as steps to configure the featuer.

Who Should be This document is intended for the following audiences:

Reading This
Š MICROS Installers/Programmers
Document
Š MICROS Dealers

Š MICROS Customer Service

Š MICROS Training Personnel

Š MIS Personnel

MD0003-131
November 12, 2007
Page 1 of 64
General Information
What the Reader Should Already Know

What the This document assumes that you have the following knowledge or
Reader Should expertise:

Already Know Š Operational understanding of PCs

Š Understanding of basic network concepts

Š Experience with Windows 95/NT 4.0

Š Basic knowledge of relational database concepts

Š Understanding of POS terminology and concepts

Š Exposure to MICROS 3700 POS Systems and Restaurant Enterprise

Series products

MD0003-131
November 12, 2007
Page 2 of 64
 General Information
Declarations

Declarations Warranties
Although the best efforts are made to ensure that the information in this
document is complete and correct, MICROS Systems, Inc. makes no
warranty of any kind with regard to this material, including but not
limited to the implied warranties of marketability and fitness for a
particular purpose.

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form

or by any means, electronic or mechanical, including photocopying,
recording, or information recording and retrieval systems, for any
purpose other than for personal use, without the express written
permission of MICROS Systems, Inc.

MICROS Systems, Inc. shall not be liable for errors contained herein or
for incidental or consequential damages in connection with the
furnishing, performance, or use of this document.

Trademarks
FrameMaker is a registered trademark of Adobe Corporation.
Microsoft, Microsoft Excel, Win32, Windows, Windows®95, Windows 2000 (Win2K), and Windows NT are
either registered trademarks or trademarks of Microsoft Corporation in the U.S. and/or other countries.
Visio is a registered trademark of Visio Corporation.
All other trademarks are the property of their respective owners.

MD0003-131
November 12, 2007
Page 3 of 64
Introduction to Conversational Ordering
Traditional Operations Functionality Versus Conversational Ordering Mode

Introduction to Conversational Ordering

The Conversational Ordering Mode (COM) is an innovation in RES

Point-of-Sale functionality. COM delivers a streamlined ordering process
that improves operator efficiency. The COM feature is fully integrated
with POS Operations.

COM’s intuitive design requires a minimum amount of training to learn

and enables operators of all experience levels to easily interface with the
POS. This is achieved by minimizing the number of keystrokes needed to
ring an order, and by allowing the operator to ring items as they are
ordered by the customer.

COM offers a realistic model for the way that customers place an order.
For example, the customer orders a combo meal, and before they make
their drink and side item selection, they begin ordering another combo
meal.

With COM’s flexible ordering model, the operator can enter menu items
in any order they want without being prompted to complete the selections
for a particular menu item. In this way COM is able to diminish user
confusion while building confidence.

The COM feature can be turned on or off by Revenue Center, allowing a

site to incorporate legacy POS behavior, COM POS behavior, or both
simultaneously.

Traditional The traditional method of ringing an order in POS Operation is through a

Operations process called pre-checking. With this process the operator is stepped
through each menu item, collecting information piece-by-piece. In order
Functionality to proceed to the next menu item, the required data must be collected
Versus when the operator is prompted. For example, if the operator select a
Conversational Cheeseburger, they are forced to immediately select a cheese and any
other condiments before they can move onto the next item.
Ordering Mode

MD0003-131
November 12, 2007
Page 4 of 64
 Introduction to Conversational Ordering
Traditional Operations Functionality Versus Conversational Ordering Mode

This model provides a fluid way for operators to take an order in most
table service environments where the server takes the order from the
customer, and then walks up to a workstation to enter the order into the
system. This model, however, is more challenging for a quick service
environment where the operator enters menu items as the customer
speaks their order. In this environment, pre-checking can be a less
efficient process.

With quick service, the order that the operator is prompted will probably
not represent the actual order that the customer speaks their order. When
this occurs the customer may be asked to repeat their order, slowing
down the site’s speed of service.

Conversational ordering is a dynamic process that naturally mimics the

flow of the cashier-customer conversation. In order to achieve this, the
Conversational Ordering Mode introduces the following new features
and enhancements that make the ordering process more intuitive:

Š COM utilizes a special kind of touchscreen called a build screen.

Build screens provide a consistent layout across different screens,
giving the operator the impression that the touchscreen does not
change throughout the transaction.

Furthermore, the build screens include built-in functionality that

allows the operator to easily place an order. This functionality
includes the features listed below.

Š Smart keys that change based on the selections made by the operator,
or by the active revenue center. For example, a touchscreen key
located in the bottom-right hand corner may be different for the
Drive-thru and the Restaurant revenue centers. If this key is made
into a smart key, then the same build screen can be used in two
different revenue centers.

The implications of this feature is discussed in greater detail in the

Smart Keys section of the ReadMe First beginning on page 29.

MD0003-131
November 12, 2007
Page 5 of 64
Introduction to Conversational Ordering
Traditional Operations Functionality Versus Conversational Ordering Mode

Š SLU groups are a grouping of SLUs that generate based on user-

defined criteria, such as the lunch menu. For example, a build screen
can be programmed with a SLU Group called Lunch. When the
operator views that build screen, they will see all of the menu item
SLUs associated with the lunch menu in that SLU Group area.

Š Toggle menu items and condiments on and off the check by selecting
the same key multiple times. If a customer changes their mind, the
operator can easily go back and change the order instead of voiding
that menu item. This feature greatly reduces the amount of voids
incurred by the operator.

Š Keys that allow the operator to easily navigate through the ordering
process. All depressed keys will appear in a different color than the
un-depressed keys (if configured to do so). If a customer asks the
operator to determine which condiments have been ordered, the
operator can just look at the depressed keys rather than at the check
detail.

All default items will contain a mark in the

bottom-right hand corner of the key. The
appearance of this mark varies by theme. If a
customer wants to know which condiments come
with the menu item, the operator can just look at the keys and read off
the default condiments.

Š Fewer restrictions on when items should be ordered diminishes the

need for most error messages. Features such as combo meal
placeholders allow the operator to move on, if desired, from the
combo meal selection and come back later on during the transaction.

Š As a result of greater operator accuracy and fewer errors, it is easier

to detect theft at the site.

MD0003-131
November 12, 2007
Page 6 of 64
 Introduction to Conversational Ordering
Terminology

Feature Not all of the features outlined in this section are unique to the
Compatibility Conversation Ordering Module. The following can be incorporated in
traditional POS Operations. Since these items are not COM exclusive,
with Both
they are listed elsewhere in the ReadMe First. Please refer to the
Traditional POS appropriate sections for additional information on these features.
Operations and
New COM Š Smart Keys can be added to any touchscreen. For additional
functionality information refer to the Smart Keys section of the ReadMe First
beginning on page 29.

Š The Baby Blue, and Pastels themes that were created for
Conversational Ordering are also available in traditional POS
Operations.

For additional information see the New Themes Added section of the
ReadMe First beginning on page 232.

Š Ability to Link 8 SLU keys to a single menu item on the Sales | Menu
Items | General tab. Additional information about this feature is
available in the Link 8 Slu Keys to a Single Menu Item on the Sales |
Menu Items | General tab section beginning on page 158.

Š SLU Groups can be used on any touchscreen to call a group of SLU

keys. Additional information about this feature is provided in the
SLU Groups section of the ReadMe First beginning on page 126.

Terminology The following terms are relevant to a discussion of the Conversational

Ordering Mode:

Š Active Menu Item. The menu item that is currently selected in POS
Operations. COM depends on active menu items to determine which
keys should appear and when. Therefore, once a check is started,
there is always an active menu item.

The active menu item will change when a new menu item is added or
when another item is selected from the guest check detail.

MD0003-131
November 12, 2007
Page 7 of 64
Introduction to Conversational Ordering
Architecture

Š Toggle Button. A key that when active, and pressed a second time,
will render the key inactive. Likewise, if the key is inactive, selecting
the key again will tender it active. For example, if the condiment
selection Tomatoes is available on a key, the user can add or remove
tomatoes from the active menu item by toggling the tomatoes key.

Architecture At the center of the Conversational Ordering Mode’s innovative design is

the concept of the build screen. The build screen is a style of touchscreen
template that produces automatically generated content in POS
Operations based on the configured settings in POS Configurator.

Central to build screen functionality is the concept of the active menu

item. Legacy POS Operations serves primarily to record the operator’s
keystrokes. COM, however, generates selections based on the menu item
currently active in the system. For this reason only a single item may be
selected at a time when COM is enabled.

Selecting a menu item will generate other choices relating to the

selection, including menu item defaults.

For example, selecting a Hamburger Combo Meal will generate

condiment choices for items that can go on that burger (e.g., Lettuce,
Tomato), the default drink size (e.g., Medium Coke), and the default side
item (e.g., Medium Fries). The automatically selected defaults can be
changed.

MD0003-131
November 12, 2007
Page 8 of 64
 Introduction to Conversational Ordering
Build Screens

The build screen will show the active menu item’s condiments and side
items as depressed keys, along with its active condiments and side items.

Here the
depressed (active)
condiments display in
green.

All configuration required for Conversational Ordering is built into the

existing POS Configurator. For additional information on Configuring
this feature see the Configuring Conversational Ordering Mode
beginning on page 43.

Build Screens Build Screens enable the operator to place an order quickly and to modify
the order easily. The idea is to allow the operator to ring items in any way
they choose. The screen provides a constant frame of reference for the
operator, allowing them to keep track of their place in the order, and to
easily answer questions about the menu items (e.g., Does that Hamburger
come with onions?).

MD0003-131
November 12, 2007
Page 9 of 64
Introduction to Conversational Ordering
Build Screens

The Build Screen will automatically select the default choices for the
active menu item If the customer requests a menu item configuration
other than the default, then the operator can add these items by
depressing the appropriate key. All condiments can be toggled on or off
by re-selecting the key.

Non-default
Condiments can
be selected by the
operator but will
not contain
a mark in the
bottom-right
corner of the key.

Default Condiments
automatically
depressed.

If no defaults are selected then no condiments will be depressed and no

marks will appear in the keys.

Example
The Mike Rose Cafe sells their Grilled Chicken Sandwich with Lettuce,
Tomato and Mayo.

A customer orders a Grilled Chicken Sandwich Combo with no Mayo.

The operator will select the Grilled Chicken Sandwich menu item. A
Mayo touchscreen key appears in the area with the rest of the
condiments. The Mayo key is already depressed.

MD0003-131
November 12, 2007
Page 10 of 64
 Introduction to Conversational Ordering
Build Screens

To make a change the operator has the following options:

Š They can select the Mayo key to deselect this condiment.

Š They can select the prefix No, then select Mayo.

Selections are simultaneously recorded

in the check detail

Depressed
keys give
a clear view
of currently
selected items.

Default items
are clearly
marked

Build Screen Build Screen templates were created to support Conversational Ordering
Features functionality. The graphic below illustrates where these features can be
found on a sample build screen.

MD0003-131
November 12, 2007
Page 11 of 64
Introduction to Conversational Ordering
Build Screens

Not all of the features listed below will appear on every build screen.
Refer to the Build Screen Templates section on page 14 for information
on the layout of each build screen.

Š 1. Touchscreen Area. This legacy feature allows the user to program

customized content on the build screen. Each build screen contains
up to 4 touchscreen areas. Each area is programmed separately in
Touchscreen Designer.

MD0003-131
November 12, 2007
Page 12 of 64
 Introduction to Conversational Ordering
Build Screens

Š 2. Touchscreen Area with a SLU Group Area. This is a

touchscreen area that is programmed with a SLU Group. A SLU
group is an automatically generated set of touchscreen buttons. When
a button is pressed the build screen will update with the appropriate
menu item SLU keys. The active SLU key will stay depressed until
another selection is made.

The scroll buttons will appear if there are more SLU groups than can
display at once on the screen. Use these to page through all available
SLUs.

Š 3. Quantity Area. This area represents a new way to order menu

item quantities. the number of keys displayed will vary depending
upon button size. At most, keys numbered 1 through 5 will appear as
well as an ellipses key (e.g., ....). Selecting the ellipses key will
generate the numeric keypad. Use they keypad to enter a value above
5.

Traditional numeric keypad functionality can still be programmed on

touchscreens. The layout of this section is configured on the Devices |
Touchscreens | Touchscreens | Display Options tab in POS
Configurator.

Š 4. Information Area. This area displays information about the order

including the active menu item, the current check total and the check
number. The display will change as items are added or removed from
the check. This area is a reference point that allows the operator to
see what is currently selected.

Š 5. Combo Group Area. This area will display the combo groups
programmed for the active combo meal (e.g., Sandwich, Side, Drink).
The display is in the form of tabs. Clicking on a tab allows the
operator to make a selection from that combo group. The content on
each tab is automatically generated. Arrows will display if the
available combo groups cannot display on the screen.

When a combo meal is selected, the build screen will automatically

transport the user to the main combo item.

MD0003-131
November 12, 2007
Page 13 of 64
Introduction to Conversational Ordering
Build Screens

Š 6. Prefix Area. This area displays modifier keys that are

automatically generated in the detail area. As in the past, a modifier
provides instructions regarding the preparation of the order (e.g., No
Onions).

Š 7. Condiment Area. This area automatically generates a list of all of

the possible menu items (e.g., condiments) that may be added to the
active menu item, or added as part of a combo meal. These keys will
be automatically generated based on the active menu item.

Š 8. Check Detail Area. This legacy area allows the user to see exactly
which items are rung on the check and their prices.

Š 9. Review Order Area. As in the past, this area is used to review

previous order information. The order type will now be displayed in
this area as well.

Build Screen Several new touchscreen templates have been added to support the build
Templates screen feature. This section describes the layout and the potential use for
each template type. Build screens are created and designed in POS
Configurator on the Devices | Touchscreen and Touchscreen Designer
forms.

Build screens are intended to provide a uniform feel to POS Operations.

Although the operator may be switching through different touchscreens,
it does not appear to them that they are.

MD0003-131
November 12, 2007
Page 14 of 64
 Introduction to Conversational Ordering
Build Screens

Build screen configuration is similar to that of a traditional touchscreen.

As with traditional touchscreens, the user can generate their own content
using touchscreen areas. Touchscreen areas numbered 1 through 4. These
correspond to the Area field at the top of the screen in Touchscreen
Designer.

Each section must be created separately and will correspond to the area
designated on the touchscreen templates listed below. The touchscreen
area of the build screen is the only configurable area of the build screen.
All other areas use automatically generated content.

When configuring touchscreen areas on a template, the user will only be

able to see the area being configured, not the entire template. Please use
the template layouts below for reference during configuration.

The following build screen templates are available:

MD0003-131
November 12, 2007
Page 15 of 64
Introduction to Conversational Ordering
Build Screens

Š 850 Single Build 1. This template is used for building menu items,
such as a Hamburger.

Š 851 Single Build 2. This template is used for building menu items,
such as Fries that can be ordered in different Menu Levels (small,
medium and large). This template includes Menu Level Area.

MD0003-131
November 12, 2007
Page 16 of 64
 Introduction to Conversational Ordering
Build Screens

Š 852 Single Build 3. This template is used for building menu items,
such as a drinks. This template includes a built-in SLU Item Area.

Š 860 Combo Build 1. This template is used for building a main

combo meal item (e.g. the Hamburger in the Hamburger Combo
Meal).

MD0003-131
November 12, 2007
Page 17 of 64
Introduction to Conversational Ordering
Build Screens

Š 861 Combo Build 2. Used for build combo meal side items (e.g., the
fries in the Hamburger Combo Meal).

Š 862 Combo Build 3. An alternate template for building a combo

meal side item. This template includes a built-in menu level area.

MD0003-131
November 12, 2007
Page 18 of 64
 Introduction to Conversational Ordering
Build Screens

Š 870 Main Build. Use to generate a function screen or a SLU screen.

Š 871 SLU Build. Use to generate a function screen or a SLU screen.

This template includes a quantity area.

MD0003-131
November 12, 2007
Page 19 of 64
Introduction to Conversational Ordering
Build Screens

Š 872 Pay Build 1. Used to build a payment screen. This template

includes a keyboard area for displaying numeric entries.

Š 873 Pay Build 2. Used to build a payment screen. This template

includes a keyboard area for displaying numeric entries and a prompt.

MD0003-131
November 12, 2007
Page 20 of 64
 Introduction to Conversational Ordering
Build Screens

Š 874 SLU Build 2. Used to build SLU screens. This template includes
a quantity area and an active menu item information area.

Š 880 HHT Single Build 1. This handheld build screen template is

used for building a single menu item.

MD0003-131
November 12, 2007
Page 21 of 64
Introduction to Conversational Ordering
Build Screens

Š 881 HHT Single Build 2. This handheld build screen template is

used for building a single menu item. This template also includes a
built-in menu level area.

Š 882 HHT Single Build 3. This handheld screen template is used for
building a single menu item. This template also includes a built-in
SLU Item Area.

MD0003-131
November 12, 2007
Page 22 of 64
 Introduction to Conversational Ordering
Build Screens

Š 890 HHT Combo Build 1. This handheld build screen template is

used for building the Main Combo Meal Menu Item (e.g., the
Hamburger in a Hamburger Combo).

Š 891 HHT Combo Build 2. This handheld build screen template is

used for making a combo meal side item selection (e.g., the fries in a
hamburger combo meal).

MD0003-131
November 12, 2007
Page 23 of 64
Introduction to Conversational Ordering
Build Screens

Š 892 HHT Combo Build 3. This handheld build screen template is

used for making a combo meal side item selection. This template
includes a built-in menu level area.

Š 900 HHT Main Build. A generic template for a handheld device that
can be used for several functions (e.g., sign-in screen).

MD0003-131
November 12, 2007
Page 24 of 64
 Introduction to Conversational Ordering
Build Screens

Š 901 HHT SLU Build. A handheld template that can be used to

browse menu item slus and order menu items.

Š 902 HHT Pay Build 1. A handheld template that can be used as a

payment screen or to change menu item quantity.

MD0003-131
November 12, 2007
Page 25 of 64
Introduction to Conversational Ordering
Build Screen Functionality

Š 903 HHT Pay Build 2. A handheld template that can be used as a

payment screen. This template includes a built-in keyboard and a
prompt to handle credit card payments.

Build Screen Each Build Screen contains the following features that facilitates the
Functionality ordering process:

Š SLU Groups

Š Smart Keys

Š Enhanced Prefixes

Š Condiment Groups

Š Combo Meals

Š Sizes

MD0003-131
November 12, 2007
Page 26 of 64
 Introduction to Conversational Ordering
SLU Groups

Š Menu Item Substitution

Note Menu item availability is not supported with

Conversational Ordering and if enabled will be
ignored.
Re-ordering is not supported with Conversational
Ordering.

SLU Groups An efficient method of saving space on a touchscreen is to add a Screen

Lookup (SLU) key in lieu of a hard coded menu item key. A SLU is a
pre-defined categorization of items that display together when the SLU
key is selected. The SLU content is generated dynamically by looking up
the appropriate keys at runtime to determine which keys should display
for that SLU record. A single SLU key can provide access to hundreds of
menu items. Likewise, a SLU Group is a categorization of several
dynamically generated SLU keys, providing even greater efficiency.

With a traditional touchscreen, each SLU key must be programmed using

hard coded function keys. This method limits the versatility of each
touchscreen, especially if the number of SLU keys needed exceeds the
allotted space on the touchscreen. As a result, several similar
touchscreens may have to be programmed.

With SLU groups, the same touchscreen area can be programmed on

several different touchscreens, corresponding to a specific SLU Group. If
the user needs to make a change to the SLUs available in this SLU
Group, then they only need to make it in one place. All of the
touchscreens will be changed automatically, and no configuration is
required in Touchscreen Designer.

For example, the Mike Rose Cafe has decided to sell dessert during lunch
and dinner. The Cafe has programmed the Lunch/Dinner SLU Group
onto multiple touchscreens. The Mike Rose Cafe must update their
dessert menu and created the new SLU. Rather than add the dessert SLU
or new menu item keys on every touchscreen, they only need to add one
new SLU group key linked to the dessert SLU Group on the SLU Groups
form.

MD0003-131
November 12, 2007
Page 27 of 64
Introduction to Conversational Ordering
SLU Groups

SLU Groups also allow the user to determine what the active SLU is at
all times. When a SLU is active, it will stay depressed until another
selection is made. That way the operator will always know their place in
the transaction.

Programmed as a SLU Group Area

in Touchscreen Designer.

Automatically
generated SLUs
appear

Selected SLU Group remains depressed until another

selection is made

When a SLU button is pressed it becomes an Active SLU button. Based

on the active SLU, keys will automatically generate on the screen. The
operator can selected from one of these items to place an order.

MD0003-131
November 12, 2007
Page 28 of 64
 Introduction to Conversational Ordering
Smart Keys

In the example above, selecting the Desserts SLU key yields a complete
list of available Desserts in the SLU Area of the touchscreen. When
configuring a touchscreen with a SLU Group key, make sure that part of
screen is free to display the Menu Item keys associated with that group.

All of the defined SLU groups will appear on the touchscreen within the
designated SLU group key. If because of space limitations, not all of the
SLU keys can appear on the screen, then the operator may use the paging
buttons to scroll through all of the available SLU keys. The paging
buttons will appear automatically unless the SLU group area is too small
to display a single SLU button and the paging buttons.

SLU Group keys will be listed in order by object number in POS

Operations. Configure a SLU key first if you would like for it to appear
as the first SLU Group button.

A SLU group can be defined by discount, service charge, tender/media,

or menu item.

Smart Keys Smart keys will allow the user to program a space on the touchscreen to
perform a different function based on either revenue center, order type,
serving period, workstation, or employee class.

A major advantage to the smart key feature is that they allow a site to
minimize the number of touchscreens in use. In the past the user had to
configure additional touchscreens to accommodate slight touchscreen
differences based on factors such as revenue center, or order type.

Now, with the smart key feature, the key will adapt to account for these
changes. The appropriate smart key will activate based on the selected
criteria.

Smart keys are highly customizable. A user can program the size,
position and appearance of these keys.

Smart keys are programmed on the Devices | Smart Keys form and are
added to the touchscreen in Touchscreen Designer.

MD0003-131
November 12, 2007
Page 29 of 64
Introduction to Conversational Ordering
Smart Keys

Enhanced RES prefixes serve as descriptors for condiments to help communicate

Prefixes how the menu item should be prepared. Some examples of prefixes
include Add, No, Extra and Double.

In the past, when a condiment was ordered, it was appended by the

appropriate prefix (e.g., No Cheese, Add Pickles), if applicable. The
condiment’s prefix, however, does not always make sense in all usage
situations.

For example, the Mike Rose Cafe sells their Mike’s Special Sandwich
with Prosciutto ham, olive loaf, and Pepperoni. Customer A ordered the
sandwich with Pepperoni. The server is uncertain about the ingredients of
Mike’s Special Sandwich and puts in the order as follows:

Mike’s Special Sandwich

+Add Pepperoni

The Add condiment prefix makes no sense in this case because this menu
item comes with Pepperoni already. In this situation, the kitchen could
become confused and would need to confirm the ingredients, slowing
down the site’s speed of service.

Enhanced prefixes is aware of the active menu item, and is aware of its
default condiments. COM does not register nonsensical prefix
configurations. For example, the prefix Add will never appear in front of
a default condiment.

Prefixes may also be used to override the menu item’s price level. For
example, ordering Double Cheese on a Hamburger could override the
price of a single slice of cheese.

Prefixes have been enhanced to include this functionality and to be more

intuitive for the operator. The following prefixes have been enhanced to
operate with Conversational Ordering Mode:

Note Similar condiment modifier functionality was

incorporated for the Ordering Module feature with the
release of RES Version 4.1.

MD0003-131
November 12, 2007
Page 30 of 64
 Introduction to Conversational Ordering
Smart Keys

Š Add. Indicates the addition of a non-default condiment. The prefix

Add will never append a default condiment. If No is initially selected
for a default condiment, and then Add is selected, then the default
will go back to its original state. Selecting any other condiment prefix
state (e.g., Extra) and then selecting Add will also revert the
condiment back to its original state.

Add can be selected in two ways. The legacy way involves manually
pressing the Add key, and then making a non-default condiment
selection. The second method will insert the Add prefix automatically
when a non-default condiment choice is made.

Š No. Indicates the removal of a default condiment. Pressing the No

prefix followed by a condiment while that condiment is on the check
will remove the condiment. A condiment can also be removed by
selecting an already depressed condiment. When this occurs, No will
be recorded next to the condiment name in the check detail (if this is a
default condiment).

Pressing No and then selecting a non-default condiment that is not on

the check will have no effect on that condiment.

Selecting the No prefix while any other prefix is selected for a non-
default condiment will null that prefix and remove that condiment
from the check.

Š Plain. Indicates that all condiments are removed from the menu item.
Selecting the Plain key and then adding condiments (even default
condiments) will cause the check to record these items as being added
to the check.

Cheeseburger
Plain
+ Ketchup

Once selected, the menu item will remain in a plain state until the key
is unselected. Toggling the Plain key to off is the same as selecting
the Everything prefix.

MD0003-131
November 12, 2007
Page 31 of 64
Introduction to Conversational Ordering
Smart Keys

Multiple prefixes can be programmed as “Plain” (e.g., Only, Plain),

however, multiple of this type of prefix cannot be applied to the same
item. For example, if you add a Cheeseburger and then select the
Only prefix, the Cheeseburger will be put into a Plain state. Selecting
the Plain prefix will now toggle that menu item, putting it into an
Everything state.

Š Everything. Resets the menu item to its original ordered state with
no non-default condiments selected, and all of the default condiments
selected.

Š Substitute. This prefix is applied when the default condiment is

being substituted with another condiment from the same condiment
group. For example, it would make sense to substitute Cheddar for
American cheese on a Cheeseburger, however, it would not make
sense to substitute a Pickle for American cheese.

Selecting the Substitute key and then selecting a non-default

condiment will add the item to the check and record the prefix as Sub.

Condiments must be identified in POS Configurator as members of

the same condiment group. For more information see the Menu Item
Substitution section on page 35.

Š Default. Indicates that the prefix adheres to legacy condiment prefix

behavior. These prefixes are added before the condiment, but contain
no additional embedded functionality. Some examples include light,
double, extra.

Any of the above mentioned prefixes can be given the name of your
choice, however, they will be governed by the behavior described above.

MD0003-131
November 12, 2007
Page 32 of 64
 Introduction to Conversational Ordering
Smart Keys

Prefixes not mentioned above are not governed by COM-specific rules

and can be programmed as desired. If a prefix is already selected and a
second prefix is selected for the same item, then that will replace the first
prefix on the guest check.

Notes The Do Not Deplete From Inventory option (POS Configurator |

Menu Items | Options) should only be enabled for a No prefix. Do
not enable this option for any other prefix types.

Printing The order used to print prefixes is configurable. Prefixes can either print
Prefixes together (e.g., all Add modifier together), or in the order that the
condiments are added to the check.

The following options determine the layout of prefixes and the

condiment they modify on an order device. They can be found on the
Devices | Order Devices | Options | Sorting/Formatting tab in POS
Configurator.

Š Print Default Condiments. The default condiment will be set to the

order device according to the item’s print class. When this option is
disabled, the default condiment will only print if it is modified by a
prefix.

Š Print on Condiment’s Line. Determines if the prefix will print on

the same line as the condiment that it modifies. When enabled, the
prefix will print on a separate line above the condiment. This option
is enabled by default.

Š Use Condiment’s Print Group. When enabled, the prefix will print
according to the print group associated with the condiment that it
modifies. This option is enabled by default.

Please note that line-by-line remote printing is not supported in

Conversational Ordering Mode.

When using KDS in DOM Mode, all KDS priorities must be set to the No
Sort option (Devices | Order Devices | DOM | Priorities) in order to
support the COM feature.

MD0003-131
November 12, 2007
Page 33 of 64
Introduction to Conversational Ordering
Smart Keys

Condiments Although condiments themselves have not been enhanced, the way that
POS Operations handles condiments has changed with COM.

In the past, if the operator entered a menu item that required a condiment
entry, then they would be prompted by POS Operations to make a
condiment selection. With Build Screens, condiments are no longer part
of required groups, and the operator will no longer be prompted for an
entry.

Builds screens consider every condiment entry as optional. Menu items

can be configured with default condiments, that will be automatically
ordered when that item is rung. The user can alter this selection, if
desired.

Default condiments will always appear with a mark in the bottom right-
hand corner of the key. The appearance of this mark will vary by theme.
The mark will appear, even if the default condiment is unselected. The
operator can use this mark to identify the default condiment(s).

Condiments that modify a menu item usually fall into different

categories, called condiment sets. For example, the condiments sets for a
Cheeseburger could include Cheese, Doneness, and Toppings.

The Condiment Area of a Build

Screen can be composed of
different condiment selections,
or groups of condiment
selections (e.g. Condiment
Groups), each represented by
its own key. An ellipse (e.g., ...)
will appear after the name of a
Condiment Group, if that group contains multiple condiments. Selecting
a key with an ellipse will generate a list of the condiments contained in
that group.

MD0003-131
November 12, 2007
Page 34 of 64
 Introduction to Conversational Ordering
Smart Keys

For example, selecting the

Cheese key in the example
above will generate a list of
available cheeses.

When finished modifying

cheese condiments, selecting
[Close] will return the operator to the previous screen.

To enable the ellipses function, the user must enable the Roll up
Condiments option on the Devices | Touchscreens | Conversational
Ordering tab. This option must be enabled for all applicable
touchscreens.

Selected condiments, like other depressed keys in COM, can be

configured to display in a different color than a non-selected key. This
allows the operator to quickly determine which condiments were rung
with the menu item. When recalling an order to a customer, the operator
can see the selected buttons in addition to the text in the guest check.

Default condiments are not used with Fixed Price Meals or the Ordering
Module.

Please keep in mind that the Use Min/Max (Sales | Condiments |

Condiment Selection) option is not supported with Conversational
Ordering.

Menu Item The goal of conversational ordering is to provide an intuitive interface

Substitution that minimizes the amount of operator keystrokes. One important method
used to accomplish this goal is menu item substitution. Because the
nature of a menu item can change based on the condiment selections, or
the lack of condiment selections.

MD0003-131
November 12, 2007
Page 35 of 64
Introduction to Conversational Ordering
Smart Keys

Menu Item Substitution determines the appropriate menu item based on

the operator’s condiment input for the active menu item. The feature can
change menu items if the condiment change results in the creation of a
completely different menu item. In the example above, ordering a
Cheeseburger without Cheese will substitute a Hamburger menu item.
Adding cheese again will re-convert the menu item back to a
Cheeseburger.

Substitution mapping allows the user to configure how the exclusion/

inclusion of a condiment set from a menu item will change that menu
item.

MD0003-131
November 12, 2007
Page 36 of 64
 Introduction to Conversational Ordering
Smart Keys

Example 1

The Mike Rose Cafe makes the following Burgers with all additional
toppings selling for an additional $0.50.:

Included
Burger Price
Condiments
Hamburger Lettuce, Tomato, $2.99
Onion
Cheeseburger Choice of Cheese, $3.50
Lettuce, Tomato,
Onion
Bacon Cheeseburger Bacon, Choice of $3.99
Cheese, Lettuce,
Tomato, Onion
Barbecue Burger Barbecue Sauce, $3.99
Choice of Cheese,
Lettuce, Tomato,
Onion

Customer A places an order with the cashier for a Hamburger with no

Lettuce or Onions. The operator enters the Hamburger and un-selects the
default Lettuce and Onion default condiments.

Customer A then decides that they would like Cheese on their

Hamburger. The operator highlights the Hamburger menu item in the
guest check and adds Cheese.

In this situation, the Cheeseburger comes with Cheese where the

Hamburger does not. Since the addition of cheese fundamentally changes
the nature of this menu item, the Hamburger automatically becomes a
Cheeseburger on the guest check without additional input from the
operator.

MD0003-131
November 12, 2007
Page 37 of 64
Introduction to Conversational Ordering
Smart Keys

In the scenario described above, the menu item change involves a one-to-
one mapping of menu items to condiment. Substitution mapping also
allows for combinations of condiments to produce several possible
mappings from a single menu item. For example, a Hamburger can
become a Barbecue Burger with the addition of Cheese and Barbecue
sauce.

The following example builds on the example described above.

Notes If the original menu item contains condiments not allowed on the
substituted menu item, then those condiments will be ignored. For
example, suppose that the original menu item is a Hot Sauce
Burger. The burger is substituted for a Cheeseburger that does not
allow Hot Sauce as a condiment. In this situation, the
Cheeseburger will be automatically rung without Hot Sauce.
Keep in mind that menu item substitution will change the original
menu item’s condiment status if it was ordered plain. When menu
item substitution occurs, the plain item is replaced with the default
condiments for the substituted menu item.
For example, suppose that both a Hamburger and a Cheeseburger
come with Tomatoes, Lettuce, and Onions. A customer orders a
plain Hamburger with American Cheese. When the system
automatically converts the Hamburger to a Cheeseburger, the
Tomatoes, Lettuce and Onion default condiments are included.

MD0003-131
November 12, 2007
Page 38 of 64
 Introduction to Conversational Ordering
Smart Keys

Example 2

After ordering a Hamburger at the Mike Rose Cafe Customer A decides

to Add Bacon and Cheese. The cashier will select the Hamburger in the
guest check area and will add the Bacon and the Cheese. The guest check
will automatically change to show a Bacon Cheeseburger instead of the
Hamburger.

Not all condiments change the nature of the original menu item. For
example, the menu at the Mike Rose Cafe offers a Hamburger and a
Bacon Cheeseburger, but not a Hamburger with Bacon. If the Hamburger
Menu Item was selected, but only the bacon condiment was added, then
the menu item would appear as follows on the guest check:

Hamburger $2.99
+ Add Bacon $0.50

The appearance and behavior of the menu item substitution feature

depends entirely on the configuration at the site.

Menu Item Substitution Mapping is programmed on the Sales | Menu

Items | Substitution Mapping tab. For additional information see the
Configuring Conversational Ordering Mode section beginning on page
43.

SWAP Keys A SWAP key is used by the operator to replace the active menu item with
a different menu item. There are two types of SWAP keys:

Š SLU Swap. With this key, the active menu item is replaced with a
different menu item from the same SLU group. Unlike with
automatic substitution, this operation must be performed manually.

A configured SLU SWAP key should be programmed into the

touchscreen. Once a menu item has been selected, the operator can
select this key to display the item’s SLU group. For example, if the
active menu item is a Hamburger, selecting the SLU SWAP key
would bring up all of the other burgers in that SLU group (e.g.,
Cheeseburger, Bacon Cheeseburger, Garden Burger).

MD0003-131
November 12, 2007
Page 39 of 64
Introduction to Conversational Ordering
Smart Keys

The operator can make a selection from the displayed SLU group, or
they can select [Close] to dismiss the displayed SLU and return to the
menu item. If a new menu item is selected, then all of the condiments
selected for the previously active menu item will be transferred onto
the new menu item. However, if the previous item was ordered as
Plain, then the new menu item SLU will be ordered with its default
condiments.

Š Menu Item Swap. With this key, the active menu item is replaced
with any other menu item. This SWAP is not limited by SLU Group
and can include any available menu item.

A configured Menu Item SWAP key should be programmed into the

touchscreen. Once a menu item has been selected, the operator can
select this key and then replace the menu item with any other
available item. For example, if the active menu item is a Hamburger,
the operator could use with Menu Item SWAP key to replace it with a
Salad.

Depending upon the current screen template assigned to the active

screen template, a swap mode indicator may be displayed on the
screen while navigating to the new menu item.

This functionality will only work when Conversational Ordering is

enabled for that revenue center. If COM is not enabled the user will
receive the following error message:

As with Menu Item Substitution, if the original menu item contains

condiments not allowed on the substituted menu item, then those
condiments will be ignored. For example, suppose that the original menu
item is a Hot Sauce Burger. The burger is swapped for a Cheeseburger
that does not allow Hot Sauce as a condiment. In this situation, the
Cheeseburger will be automatically rung without Hot Sauce.

MD0003-131
November 12, 2007
Page 40 of 64
 Introduction to Conversational Ordering
Smart Keys

Combo Meals Traditionally, when a combo meal is rung, the operator will enter the
items in the following order:

1. Select the appropriate combo meal (e.g., Sandwich Combo Meal).

2. The system will prompt the operator to select a parent menu item, if
appropriate (e.g., the Sandwich selection for the Sandwich Combo
Meal).

3. The system will prompt for all required side items.

This scenario poses the same issues regarding speed of service and
operator efficiency. The operator cannot enter items in the order that the
customer speaks them, and going back to change a combo meal can
require several keystrokes.

Conversational Ordering improves on the methodology used to place

combo meal orders by allowing the operator to return to the combo meal
to make changes at any time. When a customer places an order for a
combo meal and they fail to provide all of the required side items, the
operator can go back to the order.

The user can configure combo meals in the following ways:

Š Automatically ring default items when a combo meal is added to the

check. In this case, if a side item selection is not made, then default
items will be selected automatically when the check is service
totalled. If no default item is configured then POS Operations will
select an item automatically. This will be the menu item with the
highest object number. At no point will the operator be prompted to
satisfy the combo meal order.

Š Use placeholders instead of automatically ringing defaults. In this

situation, a placeholder is inserted instead of a default item. When the
user attempts to send the order, they will be prompted to make a
selection for each of the remaining placeholders.

Programming will differ depending on the ringing option selected.

Additional information is provided in the Configuration section
beginning on page 43.

MD0003-131
November 12, 2007
Page 41 of 64
Introduction to Conversational Ordering
Smart Keys

If a side item is changed during the order, the KDS system will be
updated to reflect the change. Printed items will not be reprinted after a
change occurs.

This behavior only describes side item selection when Conversational

Ordering is enabled. When it is disabled, and a combo meal is selected,
the system will prompt for side items as in the past.

Placeholder To facilitate ordering with combo meal placeholders, COM introduces

Scan Function the Placeholder Scan function. Selecting this key will scan the check for
any outstanding placeholder menu items. If the system discovers a
Key
placeholder then the operator will be notified with a prompt stating:

At least one meal selection is still required.

The system will then go to the appropriate combo meal selection. If

multiple placeholders are located, then the operator will be moved to the
second outstanding placeholder after they have completed entry on the
first.

This key can be added in Touchscreen Designer by selecting the

Category: Function: Transaction and the Function Placeholder Scan.

This functionality can also be linked to a tender. Enable the Check for
Placeholder option on the Sales | Tender/Media | Tender tab to scan for
placeholders when the tender is selected.

Sizes COM utilizes Menu Level functionality to facilitate the way that the
operator can select and change a menu item’s size.

Previously, POS Operations used Menu Levels to control menu item

pricing, and to manage the available size selections for each menu item.
This approach to pricing serves to limit the operator’s choices. They must
make choices in a predetermined order. This model presents the same
issues as discussed earlier including reduced efficiency, and does not
necessarily represent the order that the customer will place their order.

MD0003-131
November 12, 2007
Page 42 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

To simplify ordering, COM introduces the notion of the Menu Item

Group. The SLU Item Area on the build screen templates will be
automatically populated with the menu item choices based on the active
Menu Level.

This model treats the relationship between menu item and size in a
similar fashion as that of combo meal to combo meal side item. Menu
Item Groups are a collection of linked items that can be substituted for
one another when they appear on the build screen. For example, a small
Coke can be substituted for a small Sprite.

Menu Items that are not available in certain sizes can be omitted from
that Menu Item Group. When the user selects that menu item, the
unavailable size will not appear as a choice.

Example

The operator rings a small coke from the SLU screen. The Coke build
screen appears with the small coke selected in the detail area.

At this point the operator can substitute the Coke for any other menu item
displayed in the Menu Item SLU Group.

Configuring the Configuring this feature requires setup on several different forms.
Conversation Although there are multiple ways to configure this feature, MICROS
recommends that programming occur in the order indicated below. Only
Ordering the options required to configure this feature are included. Additional
Module options may be configured as desired.

Š Turning on Conversational Ordering Mode

Š Creating Build Screens

Š Designing Build Screens

Š Creating Condiment Sets

Š Configure Smart Keys

MD0003-131
November 12, 2007
Page 43 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š SLUs

Š Creating Combo Meal Placeholders (Optional)

Turning on The Conversational Ordering Mode can be enable by revenue center. For
Conversational example, at a single site the Restaurant revenue center can have COM
Ordering Mode enabled, while the Bar revenue center does not.
To enable the Conversational Ordering Mode go to the Revenue Centers |
RVC Transactions | General tab and enable the Conversational
Ordering Mode option for the appropriate revenue center.

Creating Build A build screen is a touchscreen with built-in characteristics that

Screens automatically generate content based on the active menu item. A list of
the available build screens can be found in the Build Screen Templates
section beginning on page 14.

MD0003-131
November 12, 2007
Page 44 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Prior to beginning configuration, create a list of all of the build screens

that will be required and identify which Build Screen Template would be
the most appropriate for each. An example of this list is provided below:

Function Template Comments

Order 870 Main Build Main screen for placing orders.

Pay 872 Pay Build 1 Screen to submit payment.
Manager 870 Main Build Main manager screen.
Menu Item SLU 871 SLU Build 1 Generates SLU items for menu
items.
Menu Item Build 860 Combo Build 1 Another screen used for
ordering menu items.
Combo Meal 874 SLU Build 2 Main screen for ordering
combo meals.
Combo SLU 861 Combo Build 2 Generates SLU items for
combo meals.

Once the list is complete, you can begin creating build screens. Build
screen creation is accomplished in the same way as the creation of a
regular touchscreen. Follow these steps to create a build screen. These
steps should be repeated for every build screen noted in your list:

1. Go to Devices | Touchscreens and select the Blue Plus Arrow icon to

add a new touchscreen record. If non-COM touchscreens exist in the
database, you should use an identifying marker to note that this is a
COM build screen.

MD0003-131
November 12, 2007
Page 45 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

In the example below the “>” character is used to designate a build

screen. This is ideal if the site is using both COM and non-COM
touchscreens.

2. Configure the following options on the Touchscreens | General tab:

Š Touchscreen template. From the drop-down, select the

appropriate template associated with this touchscreen. Refer to
the list of build screen templates for additional information on the
layout and characteristics of COM build screens.

Š Once a template is selected, the # of TS Areas field will be

configured automatically. This number cannot be changed.

Š Screen Type. Identify whether a hand-held device or a

workstation will be displaying this touchscreen.

MD0003-131
November 12, 2007
Page 46 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š Configure the Display Options tab as desired.

Use the Quantity section of this form to configure the appearance

of the Quantity Area of a build screen.

MD0003-131
November 12, 2007
Page 47 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

3. Go to the Conversational Ordering tab to configure display options

for each touchscreen style. The following options should be
configured for the Condiments, Combo Menu Items, Modifiers, and
Menu Levels display:

Š Font. Use the drop-down to select the font that will appear on the
touchscreen key associated with this build screen area.

Š Color. Use the drop-down to select the color of the touchscreen

key associated with this build screen area.

Š Arrangement. Identify the arrangement (e.g., horizontal or

vertical) of the touchscreen keys for this build screen area.

Š Icon Placement. Identify where (if applicable) the icon will

display on the touchscreen key. This option is not available for
the Menu Level build screen area.

Š Type. Use the drop-down to select the type of menu level

associated with this build screen area (e.g., Main Level). This
option is only available for the Menu Level build screen area.

MD0003-131
November 12, 2007
Page 48 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š Height. If desired, enter a value that will determine the height of

the keys associated with this build screen area. The default value
is 2.

Š Width. If desired, enter a value that will determine the width of

the keys associated with this build screen area. The default value
is 2.

Š Save all changes.

4. Repeat step 3 for all applicable touchscreen styles.

Designing Now that you have created all of the build screens, you can begin
Build Screens designing the content for each. Prior to beginning this step, identify the
requirements for each build screen. For example, determine which SLU
Groups (if any) will be included on your Menu Item Build Screen.

The user will configure build screens by touchscreen area, and will not be
able to view the completely designed build screen until starting POS
Operations. MICROS recommends that you keep a copy of the build
screen templates for reference while designing the layout of each screen.

MD0003-131
November 12, 2007
Page 49 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

As with other touchscreens, build screens are configured on the Devices |

Touchscreen Designer form in POS Configurator. Use the Area field in
the top right corner of the screen to indicate which touchscreen area you
would like to configure.

Enter a value
corresponding to the
touchscreen value you
would like to configure.
Values begin with 0.

New Build This section describes the newly created keys that may be added to the
Screen touchscreen area of a build screen. These keys are optional., however,
they are very useful when using Conversational Ordering.
Function Keys
Most legacy touchscreen functionality may be configured into a COM
build screen. The exception is the change condiment feature which does
not work because the user is unable to select a single condiment in the
check detail with Conversational Ordering. The Insert Condiment
function is also not compatible with build screens.

Additionally, the following list includes new available functionality:

MD0003-131
November 12, 2007
Page 50 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š SLU Group Areas. The user can configure part of the touchscreen
area to contain an SLU Group. The SLU Group Area will generate
content automatically depending on the programmed SLUs. Add the
appropriate SLU group areas to the build screen, however, the linking
will be configured later.

Š Select Function: SLU Key from the Category drop-down.

Š Go to the SLU Key drop-down and select the appropriate SLU

group linked to this key. SLU groups will be discussed later in the
SLU Keys section beginning on page 61.

These SLU Groups Areas

will automatically generate
the linked SLU keys when
this build screen or
touchscreen is opened
in POS Operations.

MD0003-131
November 12, 2007
Page 51 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š Smart Keys. Smart keys will allow the user to program a space on
the touchscreen to perform a different function based on either
revenue center, order type, serving period, workstation, or employee
class.

Smart Key functionality will be programmed later on the Devices |

Smart Keys form beginning on page 58.

To add a smart key make the following selections:

Š From the Category drop-down select Function: Smart Key.

Š From the Smart Key drop-down select how the smart key
definition that will be used to determine the touchscreen key’s
functionality. This cannot be selected until after smart keys have
been defined on the Smart Key form.

Š Do not assign a label to the smart key in the Legend as the

functionality of this key will change.

Š SLU Swap Key. Selecting a SLU Swap Key will display the SLU
Group associated with the active menu item, allowing the user to
make an alternate selection. The operator can then make a selection
or hit [Close] to return to the build screen.

To add a SLU Swap Key make the following selections:

Š From the Category drop-down select Function: Transaction.

MD0003-131
November 12, 2007
Page 52 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š From the Function drop-down SLU Swap Screen.

Š Enter a friendly descriptor for this key in the Legend field (e.g.,
Swap).

Š Menu Item Swap Key. Selecting a Menu Item Swap Key will put the
system into Swap mode. The user can then swap the active menu item
with another other item (regardless of SLU Group association).
Selecting a non-valid menu item will take the system out of swap
mode. For example, selecting a condiment will take the system out of
swap mode.

To add a Menu Item Swap key make the following selections:

Š From the Category drop-down select Function: Transaction.

Š From the Function drop-down Menu Item Swap Mode.

Š Enter a friendly descriptor for this key in the Legend field (e.g.,
MI Swap).

Š Placeholder Scan. Selecting this key will scan the check for any
outstanding placeholders that have not been fulfilled. The user can
then go back to the placeholder and make a selection.

To add the Placeholder Scan key make the following selections:

Š From the Category drop-down select Function: Transaction.

Š From the Function drop-down Placeholder Scan.

Creating A condiment set is a grouping of condiments that can either be used to

Condiment Sets define a menu item’s default condiments, and/or for substitution
mapping.

Since the available condiments will vary based on the active menu item,
COM will populate the touchscreen automatically with the condiments
associated that menu item. Once configured, condiments will
automatically appear in the Condiment Area of the build screen template.

MD0003-131
November 12, 2007
Page 53 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Configuring Follow these steps to configure condiment sets:

Default
1. To create a condiment set go to the Sales | Condiment Sets form in
Condiments
POS Configurator.

2. Select the Blue Plus Sign toolbar icon to add a new record. Use the
Name column to assign a friendly descriptor to this condiment set
(e.g., Burger Toppings). Save all changes.

A separate condiment set should be created for each grouping of

condiments.

3. Go to the condiment linking table and select the Blue Plus Sign to add
a new condiment to this condiment set.

4. Use the Linked Condiment drop-down to select the appropriate

condiment menu item. Menu Items are added on the Sales | Menu
Items form.

5. Repeat steps 2-4 for each linked condiment associated with this
Condiment Set.

MD0003-131
November 12, 2007
Page 54 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

6. Go to the Revenue Center | RVC Display Design form and configure

the following options for the appropriate revenue center:

Š Display default condiments. Enable this option to display menu

items designated as default condiments when in conversational
ordering mode.

Š Display prefix on condiment’s line. Enable this option to

display the condiment prefix on the same line as the condiment
when in conversational ordering mode.

7. Save all changes.

Substitution Substituting mapping is an optional component of Conversational

Mapping Ordering that changes the active menu item based on the inclusion or
exclusion of certain menu items.

Prior to beginning configuration, create a list of parent menu items that

should change in the system if a specific condiment is not ordered. For
example, Hamburger ordered with Cheese becomes a Cheeseburger.

MD0003-131
November 12, 2007
Page 55 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

This section begins after all of the applicable condiment sets are defined.

1. Go to the Sales | Condiment Sets form. Enable the No (used for MI

Sub) column. This column determines menu item behavior when a
condiment is added or omitted (e.g., a Cheeseburger with no cheese
will become a Hamburger).

When this condiment set is selected, but the highlighted condiment is

not added or omitted, a different parent menu item will be substituted.
Additional mapping for this feature is performed on the Sales | Menu
Items | Substitution Mapping tab.

2. Go to the Sales | Menu Items | Definition | Substitution Mapping tab

and highlight the appropriate parent menu item that can be replaced
with another menu item if a specific condiment is added or omitted.

MD0003-131
November 12, 2007
Page 56 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

The example below dictates substitution mapping for the

Cheeseburger menu item. When Bacon is ordered, the Cheeseburger
becomes a Bacon Cheese Burger. When No American Cheese is
present on the Cheeseburger then the menu item becomes a
Hamburger.

Repeat this step for all parent menu items that can be substituted with
another item.

3. Use the Condiment Set drop-down to identify the condiment set

associated with this menu item substitution change. This is the
condiment set, that when a particular condiment is omitted from the
parent menu item, will be automatically changed to a different parent
menu item.

MD0003-131
November 12, 2007
Page 57 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

4. Use the Substitute Menu Item drop-down to identify the menu item
that will be substituted when the specified condiment as part of the
selected condiment set is not ordered.

5. Save all changes.

Configure Smart keys are dynamic areas on a build screen that change based on
Smart Keys predefined criteria. This criteria is defined on the Devices | Smart Keys
form.

Follow these steps to configure smart keys:

1. Select the Blue Plus Sign toolbar icon to add a new Smart Key
record. Use the Name column to assign a unique descriptor for this
record. This is the record that will appear in the Smart Keys drop-
down in Touchscreen Designer.

MD0003-131
November 12, 2007
Page 58 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

A separate record should be created for each grouping of smart keys.

2. Use the Rule Type drop-down to select the type of smart key this will
apply to this smart key group. This is the rule that will determine the
active status (e.g., when the appropriate key will be active). Select
from the following options:

Š Revenue Center

Š Order Type

Š Serving Period

Š Workstation

Š Employee Class

MD0003-131
November 12, 2007
Page 59 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

3. Use the Operator fields to determine when the smart key group will
be active. Select one of the following options:

Š Equal. Indicates that the smart key is active when the smart key
group type identified below is selected.

Š Not Equal. Indicates that the smart key is not active when the
smart key group type below is selected.

4. Select the Blue Plus Sign to add a new smart key record associated
with this smart key group. Use the Name column to identify a unique
descriptor associated with this record (e.g., Store Order).

5. Configure the following fields for this record:

Š Type. Use the drop-down box to select the smart key group type
of item associated with the selected smart key. The name of this
field will change to match that of the selected Rule Type. For
example, if the Revenue Center Rule Type is selected, this field
will be populated with the names of all Revenue Centers.

Š Legend. Enter the name that will display on the smart key.

Š Next. Use the drop-down to select the next touchscreen that will
display when this smart key is selected.

Š Category. Select the category of the smart key being created.

Depending on the selection made, a related field may display
below.

To look up a category, type the first letter to automatically display

it. If there is more than one item that begins with the same letter,
the list will display alphabetically. If needed, click the drop-down
arrow to select from the rest of the list.

Š Function. Select the actual function that this smart key will
perform. This field will change depending on the Category
selected.

MD0003-131
November 12, 2007
Page 60 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Š Icon Pos. If desired, select the position where the icon should
display on the smart key. Use the Icon box to select the
appropriate icon.

Š Font. Select the font used to display the key legend.

Š Next. If desired, select the next touchscreen that will display

when this smart key is selected.

Š Color. Identify the color used to display the legend and the smart
key. For example, selecting black on green indicates that the
legend is black and the smart key is green.

Š If desired select the Bitmap that will display on the smart key.
The user can also determine if the bitmap will be stretched to fit
the size of the key, and/or if the bitmap is transparent.

Š If desired, select the media file that will play when this key is
selected. Enable the Full Screen option is the media file should
expand to the size of the full screen when playing.

6. Save all changes.

7. Repeat steps 4-6 for all smart keys associated with this smart key
group.

SLUs Linking Menu Item SLUs will determine which menu items appear when
the appropriate SLU key is selected. Remember that with build screens,
individual menu items are not configured on the touchscreen, their
associated SLU keys are.

MD0003-131
November 12, 2007
Page 61 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Go to the Menu Items | Definition | General form and link the menu items
to the appropriate Menu Item SLUs. The user can now configure up to 8
Menu Item SLUs per menu item.

Menu Item SLUs are created and defined on the Sales | Descriptors |
Menu Item SLU tab.

A grouping of menu item SLUs can be categorized together in a SLU

Key. In this case the SLU Key would be programmed onto the
touchscreen, and the linked Menu Item SLUs will appear when that
group is selected.

For example, programming a SLU Group called Lunch/Dinner would

generate keys linked to the menu items available during lunch and dinner.

MD0003-131
November 12, 2007
Page 62 of 64
 Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

Creating Combo meals can either be configured to ring with defaults (as with
Combo Meal regular menu items), or they can be configured to use placeholders. For
additional information on placeholder functionality see the Combo Meals
Placeholders
section on page 41.
(Optional)
Follow these steps to configure combo meal placeholders:

1. Placeholders are defined by Menu Item Class. Go to the Sales | Menu

Item Classes form and highlight the menu item class that will be
defined as a placeholder (e.g., Placeholder Beverage).

2. Go to the General Options tab and enable the Placeholder option.

3. Save all changes.

4. Repeat steps 1-3 for all applicable menu item classes.

5. Go to the Sales | Menu Items tab and add a placeholder menu item
(e.g., Placeholder Beverage).

MD0003-131
November 12, 2007
Page 63 of 64
Introduction to Conversational Ordering
Configuring the Conversation Ordering Module

6. Go to the Sales | Combo Meals | Combo Groups tab and select the
combo group that will contain a placeholder. Select a placeholder
menu item and enable the Default when no order type declared.

7. Save all changes.

8. Repeat step 6 and 7 for all combo groups that will contain a
placeholder.

9. Go to the Sales | Tender/Media tab and enable the Check for

Placeholders option. This option will check for outstanding
placeholders before tendering the check. This is only available with
COM.

10. Save all changes.

MD0003-131
November 12, 2007
Page 64 of 64