[go: up one dir, main page]

WO2002017058A1 - Systeme et procede de gestion d'interface d'utilisateur - Google Patents

Systeme et procede de gestion d'interface d'utilisateur Download PDF

Info

Publication number
WO2002017058A1
WO2002017058A1 PCT/AU2001/001070 AU0101070W WO0217058A1 WO 2002017058 A1 WO2002017058 A1 WO 2002017058A1 AU 0101070 W AU0101070 W AU 0101070W WO 0217058 A1 WO0217058 A1 WO 0217058A1
Authority
WO
WIPO (PCT)
Prior art keywords
user interface
screen
button
xos
operator
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/AU2001/001070
Other languages
English (en)
Inventor
David Swift
Patrick Bettels-Blume
Elissa Doyle
David Johnson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XERTS INTERNATIONAL Ltd
Original Assignee
XERTS INTERNATIONAL Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from AUPQ9641A external-priority patent/AUPQ964100A0/en
Priority claimed from AUPQ9642A external-priority patent/AUPQ964200A0/en
Priority claimed from AUPQ9643A external-priority patent/AUPQ964300A0/en
Application filed by XERTS INTERNATIONAL Ltd filed Critical XERTS INTERNATIONAL Ltd
Priority to AU2001285572A priority Critical patent/AU2001285572A1/en
Publication of WO2002017058A1 publication Critical patent/WO2002017058A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G06F3/0485—Scrolling or panning
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/38—Creation or generation of source code for implementing user interfaces

Definitions

  • a user interface management system and method A user interface management system and method.
  • the present invention generally relates to a system and method of user interface management and more particularly, to the provision of a user interface development environment for an interactive system that allows an operator to define the user interface presented to customers for the purpose of ordering goods and services.
  • Computerised ordering systems that allow customers to order goods and/or services have been proposed but typically, these systems are operated by service staff who accept the order from the customer and operate the ordering system to place the order for the desired goods and/or services. Usually, service staff undergo training in order for them to obtain the necessary skills to effectively and efficiently operate such an ordering system.
  • Computerised ordering systems comprise many advantages for customers seeking to order goods and or services.
  • the primary advantage in these types of systems is obviating the requirement for a customer to relay their order through a human operator, this process possibly involving delays whilst waiting for available staff to record the order and is subject to human error.
  • the high cost of computerised systems for collecting and processing orders generally results in the system being considered economically unjustifiable in many environments.
  • the two major cost components are the initial capital investment in the system and the ongoing cost for technical support.
  • the cost of technical support to regularly • update the system to reflect new offerings becomes significant. For example, in a restaurant where items on the menu may change on a weekly basis, the cost of technical support for highly skilled operators to adjust the menu of available food items may incur substantial cost.
  • the present application is one of a five co-pending applications describing an interactive ordering system and the development and management thereof, the system having application in environments such as a restaurants, hotels, casinos and so on.
  • the reader is referred to these five co-pending applications by the same applicant that relate to different aspects of the system:
  • a video and video management system for navigation through a user interface system This aspect of the system enables the user to navigate through a hierarchical menu structure used in providing the user with selectable indicia.
  • a user interactive system and method comprising profiles. This aspect of the system provides users with a choice of indicia that may be in a form of graphical images relating to their language and/or customs, whilst remaining transparent to the rest of the operating system.
  • a user interface development system and method This aspect of the system relates to the development of the user interface by subsequent use by users seeking to submit orders and requests. In particular, this aspect provides the ability for relatively low skilled operators to develop and/or modify the visual aspect of a user interface.
  • a user interface management system and method This aspect of the system relates to the management of the user interface development system thus providing relatively high skilled administrators with the ability to provide low skilled operators with the facilities to develop and/or modify the visual aspect of a user interface.
  • the present invention provides a user interface management system for use by a system administrator including a means to create available items for display in a user interface development system and subsequent inclusion by an operator in the visual aspect of a user interface, the creation of available items including generation of an object to represent the item, the object comprising attributes that are selected by the system administrator and associated with the object.
  • items may be formed from an aggregation of objects, each object including any one or more of the following attributes, or any combination of one or more of the following attributes:
  • the attributes being selected by a system administrator at the time of creating an item.
  • a system administrator is provided with the facility to determine the availability of items for inclusion by an operator in the visual aspect of a user interface.
  • the system administrator may construct blank templates of the visual aspect of a user interface for subsequent completion by an operator, the system administrator associating items with templates thus determining the availability of items for use by an operator.
  • the user interface management system may also include a means to define a placeholder designating a specific region of the visual aspect of the user interface into which an available item may be located.
  • the system administrator may be provided with a list of pre-defined placeholders.
  • the system administrator may also classify placeholders according to the types of available items that may be located in the placeholder.
  • a system administrator may associate a first placeholder with at least one additional placeholder and may prevent additional placeholders being displayed to an operator until an appropriate item requiring additional placeholders is located in the first placeholder.
  • placeholders may be defined within a template.
  • a system administrator may select at least one graphical image to be displayed to an operator upon location of an available item in a placeholder to provide an indication to the operator of the success or otherwise of the location of the item in the placeholder.
  • the system administrator is provided with a list of available tests that may be applied upon location of an item into a placeholder, selection of an available test causing that test to be applied upon location of an item into a placeholder and display of the appropriate image indicating the success or otherwise of the applied test.
  • the system administrator may also select when tests will be applied. Such tests may include checking the accessibility of object attributes.
  • system administrator may create functions for display to an operator for selection and association with an item located in a placeholder.
  • system administrator may also determine a list of available sounds that may be used by an operator to associate with items located in a visual user interface.
  • Figure 1 is a schematic diagram of a database used in a preferred embodiment of the present invention illustrating the database tables
  • Figure 2 illustrates the "advertising" tables of the database
  • FIG. 3 illustrates the "category" tables of the database
  • Figure 4 illustrates the "image and sound" tables of the database
  • FIG. 5 illustrates the "profile" tables of the database
  • Figure 6 illustrates the "ordering items" tables of the database
  • Figure 7 illustrates the "maintenance" tables of the database
  • Figure 8 illustrates the "restaurant table” tables of the database
  • Figure 9 illustrates the "system information" table of the database
  • Figure 10 illustrates the "sound theme” tables of the database
  • Figure 11 illustrates the "screens and buttons" tables of the database
  • Figure 12 illustrates the profile tab of the User Interface Utility screen
  • Figure 13 illustrates the visual and audio maintenance tab of the User Interface Utility screen
  • Figure 14 illustrates the system maintenance tab of the User Interface Utility screen
  • Figure 15 illustrates the File option menu of the User Interface Utility screen
  • Figure 16 illustrates the system configuration window of the User Interface Utility screen
  • Figure 17 illustrates the User Interface Utility screen when being edited
  • Figure 18 illustrates the Category Image Assignment window of the profile maintenance of the User Interface Utility
  • Figure 19 illustrate the list of category images available under the Edit Category selection of the profile maintenance of the User Interface Utility
  • Figure 20 illustrates the time period maintenance screen of the profile maintenance of the User Interface Utility
  • Figure 21 illustrates the screen editor of the profile maintenance section of the User Interface Utility
  • Figure 22 illustrates the screen editor in relation to a transmit screen
  • Figure 23 illustrates the buttons for a navigation screen
  • Figure 24 illustrates creating a new button for the navigation screen
  • Figure 25 illustrates the Item Type Maintenance form of the Visual and Audio Maintenance of the User Interface Utility
  • Figure 26 illustrates the item Sub Types form of the Item Maintenance form
  • Figure 27 illustrates the Image Maintenance form of the Visual and Audio Maintenance of the User Interface Utility
  • Figure 28 illustrates the Image maintenance form for a product background
  • Figure 29 illustrates the Sound Theme form of the Visual and Audio Maintenance of the User Interface Utility
  • Figure 30 illustrates the File Import form of the Visual and Audio Maintenance of the User Interface Utility
  • Figure 31 illustrates the Remove files form of the Visual and Audio Maintenance of the User Interface Utility
  • Figure 32 illustrates the XOS Category Editor form of the System Maintenance of the User Interface Utility
  • Figure 33 illustrates the XOS/Micros Category Assignment form of the System Maintenance of the User Interface Utility
  • Figure 34 illustrates the Table Maintenance form of the System Maintenance of the User Interface Utility
  • Figure 35 illustrates the Table Colour Maintenance form of the System Maintenance of the User Interface Utility
  • FIG. 36 illustrates the colour selection of the Table Colour Maintenance form
  • Figure 37 illustrates the Product Maintenance form of the System Maintenance of the User Interface Utility
  • Figure 38 illustrates the Screen Type Editor form of the System Maintenance of the User Interface Utility
  • Figure 39 illustrates the Button Types form of the System Maintenance of the
  • Figure 40 illustrates the selection of the sound type of the Button Type form
  • Figure 41 illustrates the System Information form of the System Maintenance of the User Interface Utility
  • the present invention is well suited to the management of a user interface of an interactive ordering system for a restaurant or cafe environment where customers place orders for food and/or beverages.
  • the invention is also suited to other environments such as hotels, supermarkets, airport terminals and the like where customers place orders for goods and/or services.
  • customers can usually order a range of services including room service, entertainment (such as in-house movies) and information services relating to events or places of interest in the vicinity of the hotel.
  • customers are provided with an ordering system which includes a visual display and a selection means enabling customers to select items from the visual display.
  • Visual displays incorporating a touch sensitive selection means such that customers may touch the display in a region corresponding to a displayed item in order to select that item have been found to be particularly intuitive and relatively easy for customers to understand and use.
  • This type of arrangement is also preferred by those with physical disabilities who may otherwise experience difficulty operating other type of selection means such as a mouse device as used with most personal computers.
  • a system according to the present invention is likely to be operated by a highly skilled practitioner, however, it enables the highly skilled practitioner to create a user interface development system that may be operated by a low skilled operator for the purpose of creating and/or editing a user interface presented to a customer thus enabling the operator to perform those tasks without the requirement of referring to a relatively high skilled practitioner.
  • FIG. 1 Detailed in Figure 1 is a schematic of the typical tables used in the database of the present example. Each of the necessary tables will be discussed in more details in the following section, where they are divided into logical sections.
  • the database is used to run the XOS (Xerts Ordering System), the host podium and the transfer of information to and from existing kitGhen databases such as Micros.
  • XOS Xerts Ordering System
  • kitGhen databases such as Micros.
  • FIG. 2 details the advertising tables used in the database. Before we describe the advertising tables it is important to understand how the advertising works. Advertising is in the form of messages that appear on the screen to the user, usually in a select area of the screen, the content of which can change depending on the screen that the user is accessing at the time.
  • Advertising is divided into profiles. Each advertising profile may be assigned to a XOS profile. Therefore, one may have an advertising profile for Japanese which links to a XOS Japanese profile. One may also have an advertising profile in English which links to an English XOS profile. There can also be children's advertising in a children's profile and so on.
  • an advertising profile the operator of the User Interface Management system may specify when and where a particular set of advertisements are played.
  • a set of advertisements is called an advertising group. This is made up of several individual advertising images.
  • a particular advertising group may be made up of five images. If these images all relate to a product such as beer, then there is a beer-advertising group. The operator may then specify when and where in the database, in the XOS, the particular beer group appears. For example, the operator may select that the beer group may only be viewed at dinnertime and only when the user selects a beverage screen. The operator may also select the beer group to be shown all day but only in the beers and sodas screen. This level of flexibility does make the table structure somewhat complicated.
  • advertising uses the following five tables; advProfile 10 (advertising profile), advGroup 12 (advertising group), main_advGroup 14 (maintenance of advertising group), advlmages 16 (advertising images) and advTimePeriod 18 (advertising time period).
  • advProfile 10 an advertising profile is made up of all the different advertising groups for this particular set. For example, there may be an advertising profile for children or one for another language.
  • advGroup 12 advertising group
  • main_advGroup 14 maintenance of advertising group
  • advlmages 16 advertising images
  • advTimePeriod 18 advertising time period
  • the advertising time period table 18 allows one to select when a particular advertising group is displayed. For example, the operator may want the beer advertisements to be displayed at lunchtime. These particular time periods are calculated in the advertising time period table 18. It is important to note that for the preferred embodiment, the total of all the time periods must cover a twenty-four hour period of time but must never overlap. In the table there is a time period ID 24 that is the primary ID followed by a description 26. The description is simply used in the User Interface Utility to allow the operator to distinguish between time periods. There is then a start time 28 and an end time 30. As an example, lunch may be the description, with a start time of 11:30 and an end time of 14:00 hours.
  • a profile is made up of several advertising groups.
  • Each advertising group for example beer, is made up of several advertising images.
  • the advertising images table 16 has several entries that are all primary keys.
  • the advertising group ID 32 may link this particular image to the beer.
  • the image ID 34 is a foreign key link to the image catalogue and gives the ID of the particular advertisement that the operator may wish to show. For example this may be a Brand X beer.
  • the play order 36 allows the operator to choose where in the group they wish this particular Brand X advertisement to play. If it is to be played first the operator enters 1 (one). To play it fifth, the operator enters a five (5). It is important to note that for the preferred embodiment, the number must run in order with no gaps. This rule is maintained in the User Interface Development System. Using these three values as the primary key, the operator can have the same image appear many times in the particular group. For example the Brand X beer may appear as advertisement one and as advertisement five in this particular group.
  • the groups are given a particular name in the main advertisement table 14. Like other maintenance tables described in the maintenance system the group is given a group ID 38 and a description 40. This description is simply used in the content management system to allow the operator to distinguish between groups. In the beer example the operator would enter the unique primary key followed by beer. All the advertising images would then have the same group ID as beer but they would have separate ID's and group order until the group is filled. The size of the group is not fixed.
  • the advertising group table 12 has four values for the primary key, the primary key being signified by the key symbol (42). This allows the flexibility of allowing a group to be in a profile, for a specific time and for specific positioning in the XOS.
  • the group ID 44 Considering the beer example, this would be the foreign key link to the beer group in the maintenance advertising table 14.
  • the profile ID 46 for the advertisement group As mentioned previously an advertisement profile is made up of several advertisement groups therefore each group must be given a particular profile ID. A group may however belong to several profiles.
  • the operator can select for a product, which may be associated with a particular profile ID such as adults, the time period ID 48, namely when they want the beer to be displayed. Once again the operator selects from the foreign key in the advertisement time period table 18.
  • beer may appear in several different time periods; one therefore simply creates a new record for each time period in which the beer group appears.
  • the final part of the link is the category JD 50.
  • Each screen is given a particular category that may already be used in existing systems, such as the well known Micros. If the Micros category of a screen matches the category of this record in the category ID 50, the operator knows to display this particular group of advertisements if the time period and profile also match. This then allows the operator to say that beer in the adult's profile when available at lunchtime will be shown in the screen that has beers and sodas, Beers and sodas having its own category ID. As with time periods, one may show in different category ID's the same group. For example if one wanted to show beer in an all drinks screen at lunchtime one needs to create a new advertising group record for each drink category ID, leaving the group, profile and time period the same. Different category ID's apply to wine, soft drinks, cocktails, etc.
  • the operator For a particular group in a particular profile at a particular time and a particular category, in our example for beer, in our adult profile at lunchtime, on beers and sodas, the operator must select a ratio 52.
  • the ratio is very important in the preferred embodiment as not every screen in the XOS will relate to a Micros category ID.
  • the Home screen is not related to the Micros category ID and neither is the transmit screen. Therefore whenever a category ID is not available for a screen one shows the system category.
  • the system category has a category ID of negative one (-1).
  • the system advertisements in the system category will display whenever there is either
  • the operator may display the system advertisements.
  • the ratio allows arrangement for a particular beer profile, for a beer in the adult profile at lunchtime for beers and sodas menu the operator wants to show either all beer advertisements or 50% beer and 50% system. If 50/50 is selected a user will first see a beer advertisement followed by a system advertisement, followed by the next beer advertisement with each advertisement displayed for approximately the same period of time.
  • the field “isRandom” (54) provides the order in which advertising images within an advertising group are to be displayed. If “isRandom” is true when the records are first returned to the XOS they will be randomised. They are only randomised once per XOS session. This ensures fair play for all advertisements. If it is not random then they are simply played in the play order specified in the advertising images.
  • Categories use the following tables; Category 100, XOSCategory 102, XOS CategoryMicros 104 and XOSCategorylmage 106.
  • the category table 100 is a list of all categories 108 stored within existing restaurant or kitchen operating systems such as that referred to as Micros.
  • the category name 110 details are imported directly from a system such as Micros and may not be edited by the operator.
  • the XOS categories 102 When a user orders items in the XOS they are grouped by category. These categories are usually drinks, mains, desserts and so on. They can be rather large groups but are seen in the bottom left hand side shopping cart of the order screen and is also how items are grouped in the transmit screen.
  • a description 114 For a XOS category there is a primary key 112, a description 114, this description being solely for use in the XOS User Interface Development System and is never seen in the XOS, and also a display order 116.
  • the operator sets the display order for all XOS categories. This tells the XOS which order to display the items both in the shopping cart in the bottom left hand corner of the order manu and also in the main transmit page.
  • the XOSCategories 106 are linked to Micros Categories using the XOSCategoryMicros table 104. This is a link with just the category ID 118 and the Micros category ID 120 forming the primary key.
  • a XOS Category there is a XOS Category Image.
  • the XOS Category Image is actually an image set made up of two images. The first is the image that displays in the bottom left hand shopping cart area, and the second one is the one that displays in the transmit screen.
  • an image set 126 which is an image set of the two previously mentioned category ID's.
  • the CatalogEntryType stores the information of a set of images or sounds, that is, an image name or a sound name.
  • a primary key 208 is followed by the number required 210 which gives the total number of images or sounds within a current set.
  • a set may be images or sounds, but it may never be both in the preferred embodiment.
  • a media type 216 which is where we find out whether it is a sound or an image. So for a set one basically stores how many images or sounds are within the set, a basic description of the set and also whether the set contains images or sounds.
  • the media type will be an I or an S indicating an image or sound respectively.
  • the CatalogEntrySubType table 202 contains information about each individual image or individual sound within an image or sound set. There is a foreign key link 218 to the CatalogEntryType. There is a sequence ID 220, for example, type A may have sequence ID 1,2,-3 which is because the "num. required" field tells us we only need three records. There is also a description of this particular image type 222 and the file extensions 224 that this image type extension may use, for example, an image of this sub-type must be either a JPEG or an MPEG or if it is a sound it must be a WAV file. A location 226 of this particular subtype may also be stored. This will be an X for a server or a C for a client.
  • a quick example may be as follows. In the XOS one shows products on the menu screens. The product button is actually made up of four individual images, therefore the number required is set at 4, the description would be a product and buttons and the media type would be an I because it is an Image. There is a catalog entry sub type for each button within this particular products button. The first button within a products button is the deselected image. That is what the button looks like before a user selects it. So for type ID product button there will be a first image with a description of de-selected and in the example, it must be a JPEG. The location will be on the client.
  • most images and sounds are stored on the client as it is considered to be more stable and has more computing power as compared with the server.
  • the second image which will be the type ID of the product button, type sequence ID of 2, is the selected image, that is, it is the graphical image when the user has selected that product. So the description will be "selection”.
  • this can only be a JPEG and one enters JPEG on the extension and enters a location of Client since it will be stored on the Client.
  • the type ID is once again the same as the product button
  • the type sequence ID is 3
  • the third image is the large image so one types large image into the description. This is the image that is displayed in the centre of the XOS ordering screen whenever the user selects a product button.
  • the file name extension In the case of the large image this may either be a JPEG or it may be an MPEG, so these can be entered in a semicolon-delimited list. Once again the operator enters the location. It is important to note for the preferred embodiment that even though there are two different file types they must always come from the one location.
  • the type ID is once again the product button, the type sequence ID will be number 4 and the description will be "selection screen image". This image is the one that will appear on the selection screen when a user selects the transmit button.
  • the file extension would be JPEG and once again the location will be on the Client.
  • the system then uses the ImageCatalog 206 or the SoundCatalog 204, which is dependant on whether the CatalogEntryType is an I for an image or an S for a sound. If working with an image, the operator first enters an image ID 228 which is simply a unique number followed by the image sequence ID 230, in the case of a product described earlier one would have the same image ID four times with the image sequence ID being 1,2, 3, 4 each time. It is this image ID and sequence ID that make up the primary key. One then links to the type of image 232. This type of image is the type of set as described in the CatalogEntryType defined by the type ID. Then there are the physical file names 234 which are simply the file names from which one can access the file and the system category 236.
  • the system category may not need to be used but if it is, the system category ensures that any amendment or changes made by the system administrator or by the programmers can be tracked. That is, it is a category that tells you whether the particular row of the database that was amended was entered by an operator or by a developer.
  • the sound ID 238 For sounds this is very similar to the images.
  • a sound sequence ID 240 for example the sound ID 4 may be used three times for sound sequence ID 1,2 and 3. This makes up the primary key.
  • the type ID 242 which is the CatalogEntryType, the physical file name 244 and system category 246.
  • Each session of the XOS runs in a particular XOS profile. That is every screen that appears in the XOS and every button within every screen is related to that particular profile. This allows the operator to have different versions of the XOS for different customers, for example, a children's version, an adult's version, an English version and a Japanese version. There is no limit to the number of profiles that may be created. To change languages, an operator may simply enter a new profile and select images from that profile where the image includes a graphical representation of text in that countries' language. For example, there may be a Japanese version of all the buttons. To work with profiles, the database includes the Profile table 250, Profile_TimePeriod table 252 and TimePeriod table 254. We consider each of these in turn, first considering the Profile table and referring to Figure 5.
  • the Profile has a unique identifier 256 followed by its description 258.
  • This description of the profile may be displayed in the User Interface Management System. It may also be displayed in the User Interface Development System when an operator selects which profile they wish to edit, and it may also be displayed in the Host Podium system. When a waiter assigns a table to customers they must select the profile that the XOS will be running. It is the descriptions in this table that will be displayed thus detailing a list of available profiles.
  • the start-up screen 262 is the screen LD to a screen that appears when the XOS first starts up.
  • the sound theme ID 264 and which will be discussed further below. However, the sound theme ID that is selected here will apply to all buttons in the XOS.
  • the Valid 266 field As there are so many things that may be changed in a profile it is easy for a profile to become invalid. For example, missing screens or missing images. Therefore in the User Interface Development System whenever an operator makes a change in the example of the preferred embodiment, they must re-validate the profile. If they have not re-validated the profile or have re-validated it but it failed that particular profile will not be available in the list in the Host Podium system.
  • the XOS may never run with an invalid profile.
  • the advertising profile ID 268 is a foreign key link to the advertising profile table. This indicates to the operator which sets of advertisements will be running for this particular profile of the XOS. For example if there was a children's profile, different sets of advertisements could be displayed as compared with an adults profile. In this particular instance, a children's profile will not include advertisements for alcohol.
  • the Profile_TimePeriod table 252 provides a list of all the profiles and the time periods for which each profile is valid. Before describing this further we first need to consider the TimePeriod table 254.
  • the TimePeriod table is a list of all time periods 270 for which the restaurant is open, divided into segments. There is a start time 272, an end time 274 and a description 276. The description is solely used for the Management system. Common time periods may be breakfast, lunch and dinner.
  • the ProfileTimePeriod table has a profile LD 278 and a time period ID 280, therefore one can say that this particular profile is valid during lunchtime only.
  • Time periods are used as a recommendation only and may not be enforced when accepting orders from a user.
  • this table has the primary key of the transaction ID 306, which is a unique identifier.
  • the XOS stores a number of parameters. These include the table ID 308, that is the table that ordered the product, the product ID 310, that is the product that has been ordered, and the Condiment LD's 312, that is a string containing any condiment ID's that have been ordered for the product. For example, if a user ordered a Caesar's Salad as the product ID they may have condiment ID's for bacon, chicken and anchovies.
  • the item status field 314 is used when the customer views the transmit screen and where they may change the status of a product selected from “cleared” to "not cleared", that is, they may delete previously selected items they no longer wish to consider. When they delete any item the item status is changed in the table.
  • the system also stores the date and time 316 that the customer ordered the item.
  • the transmit button When the customer selects the transmit button, items are transferred from the XOS into the Order Manager (the POS_Order_Items and POS_Batch tables being used). All the items that are sent when the customer presses the transmit button are collated into a batch.
  • the XOS stores a primary key batch ID 318 that is simply a unique identifier, the table LD 320 that identifies the table from which the batch originated, and also the batch time and date 322 that the batch was sent.
  • This table also stores a value for batch transferred 324 that indicates if this batch has been sent through to the Micros system.
  • the XOS For each batch the XOS stores the information for each particular product that has been ordered. Many of these fields are simply duplicated from the XOS_Order_Items table.
  • the transaction ID 328 is the same transaction ID as in the XOS_Order_Items table as are the product LD 330 and condiment ID's 332.
  • the waiter uses the Order Manager System, they must clear items before they can be transferred into Micros. If an item has been cleared and is ready for transfer it is stored as the item cleared field 334.
  • Whether or not this particular product has been transferred yet is stored in the "isltem transferred" field 336, which provides information as to whether this particular product has been moved from the XOS to the Micros system. If the item has been transferred then the system stores the date and time that this item has been transferred in the "Transfer Date/Time” field 338. Once the particular XOS session has finished the information in the POS_Order_Items and POS_Batch is archived.
  • POS_Order_Items when a customer orders an item on the XOS, it is sent to the XOS_Order_Items table. When they actually transmit the particular orders to the kitchen the POS_Order_Items and the POS_Batch tables are used. Once the XOS session has finished, that is, the table is vacant, the POS_Order_Items and POS_Batch tables are then archived for later reporting.
  • the maintenance tables in the database are used by both the Content Management utility and the User Interface Development System.
  • the Maint_ScreenName table 350 enables the operator to give each screen a particular name
  • the Maint_SoundName table 352 allows one to give each sound set a particular name
  • the Maint_ImageName 354 table allows the operator to give each image set a particular name whilst the Maint_ProductImage 356 is slightly different in that it allows one to4ink products to image sets.
  • the MaintjScreenName table is only used by the XOS Content Management Utility. It has a foreign key link 358 back to the Screens table and also a screen name field 360 and notes 362. These fields are provided so that the operator may easily distinguish between screens when working in the Content Management Utility and this is their sole purpose.
  • the Main_SoundName table is similar to the Main ScreenName table in that it has a foreign key link 364, name 366 and notes 368 that allows the operator to identify a particular name and any notes about each sound set that is in the database. Once again this is used in the Content Management Utility to allow the operator to easily distinguish between the groups of sounds. This information is also used in the Interface Development system. In the User Interface Development System, the operator is able to drag and drop sounds onto buttons. It is the sound name that the operator uses to distinguish between each sound set. There is also a language ID field 370, which does not need to be used but can distinguish between different languages. MaintJmageName 354 works in a similar manner as Maint_SoundName.
  • image ID 372 is a foreign key link back to the Image catalog.
  • image name 374 and notes 376 are stored in the Content Management System to allow the operator to easily distinguish between the images.
  • image names are also used in the User Interface Development System.
  • the User Interface Development System allows the user to drag and drop image sets therefore creating buttons on a particular menu. It is this image name that distinguishes what the image set represents.
  • the Main_ProductImage table 356 links an image set 382 to a product 384. For example it could link an image set that could be a product type in which it represents chocolate cake. The operator then links the chocolate cake image set to the chocolate cake product JD. This allows the system to determine which product the customer has ordered when they press a particular button on the XOS menu.
  • the restaurant tables shown in Figure 8 hold all the information for all the restaurant tables in the Xerts database.
  • Information about all of the tables in the Xerts restaurant are stored in the following three tables, namely, RestaurantTables 400, TableConfig 402, and Colours 404.
  • the information in these tables is used by both the Content Management system for maintenance of the tables and by the Host Podium system, which includes the Order Management and the System Administration mode of the Host Podium system.
  • the TableConfig table includes a unique identifier being the table ID 406 and a profile ID 408 that determines the profile that the XOS is currently running for that particular table.
  • table 2 may be running a profile for children
  • table 10 a profile for Japanese tourists
  • table 8 may be running the standard XOS profile.
  • the child lock enabled field 410 indicates whether child lock is enabled. If it is enabled then whenever the customer using the XOS tries to send information to the kitchen, that is:
  • the child lock code ID 412 is currently a spare field.
  • the food ordered field 414 indicates whether the particular table has ordered any food from the XOS. This may be important in the case where certain areas of the XOS are only available after food has been ordered. For example, the operator may not wish the customer to enter the "fun" menu until they have ordered a meal.
  • the table status field 416 presents the current status of a table and can indicate whether if allocated, vacant, being cleaned, out of service or reserved, etc.
  • the "num. seated" field 418 stores information on the number of customers seated at a particular table at the current time.
  • the screen Pos X 420 and the screen Pos Y fields 422 are used by the Host Podium system.
  • the Host Podium there is provided a layout of the restaurant with the tables superimposed on that layout. The position of these tables is stored by their X and Y co-ordinates.
  • the optional guest Name field 424 which may be filled at the Host Podium or the Order Manager, provides a store for the guest name.
  • the comments field 426 enables comments about the particular guests seated at that table or the table to be entered by the Host Podium or the Order Manager as required. An example where this may be used is where a member of the party has a birthday. Another example is where the table may be out of service due to an XOS equipment failure.
  • the comments field enables that reason to be stored in relation to the table so that the information is generally available.
  • the start time 428 is the time at which a particular table was allocated to the current guests. From this start time the system can calculate how long the guests have been seated at this particular table.
  • the tc time stamp field 430 is used by the Host Podium and the Order
  • req help field 432 Whenever the customer requests help from the XOS, the required field for the reqHelp field will be set. This will then be shown in the Host Podium and Order Manager system. This also occurs when requesting a bill, which is the "req Bill" field 434. Whenever the customer using XOS requests a bill by pressing the request bill button this flag will be set. Once this flag is set the information will be shown in the host Podium and the Order Manager systems.
  • the card ID 436 stores the cards swiped for this particular table.
  • the previous Status field 438 and the previous profile field (not shown) provide the status and the profile respectively that the XOS was in the previous times that it was running.
  • the RestaurantTable 400 has a foreign key link 440 back to the Table_Config table.
  • the table name 442 is the name of the table and in most cases this will be a numeric number between 1 and 30 for XOS tables and then up to whatever is required for conventional tables. For example we could have table 2, table 10 etc. Although numbers is a guide one may enter any value that they want into the table name field.
  • the field table capacity 444 is the maximum number of guests can be seated at any one table. If a table has a XOS, in the preferred embodiment, one needs to be able to link this table to a table in Micros to allow us to transfer the orders from the XOS into the Micros point of sale system. This is set by the micros table ID 446.
  • the colour LD 448 represents the waiter responsible for the particular table.
  • the operator needs to know the network name of the computer. Usually the computer name will be equal to the table name. However, this does not need to be strictly enforced. Since a restaurant may use both XOS and conventional tables the "has XOS" flag 452 tells the operator whether the table is in fact a XOS or a conventional table. Finally the time stamp fielcf454 is the same as for the TableConfig table and its function is to stop one from over-writing other table information.
  • the RestaurantTable table 400 stores all of the static information for a particular table, while the TableConfig table 402 stores all of the information that will change whenever a new customer is seated at the table or whenever the table's status changes. Therefore, this is variable information whilst the RestaurantTable is static information.
  • colours table 404 In order to allocate waiters to tables the operator allocates each waiter a particular colour. A list of all these colours is shown in this table.
  • the colour ID field 456 is simply the primary key followed by a description 458, which is the name of the colour, for example red, green, blue. Then one has the colour value 460 that is the RGB colour value for the particular colour.
  • the operator assigns each restaurant table a particular colour using its colour ID 456. Therefore each table is assigned a colour and each waiter is assigned a colour. For example, all pink tables may be serviced by a waiter who has been allocated the pink colour whilst all green tables may be serviced by a waiter who has been allocated green. It is to be understood that the table allocation may be distinguished by other visual indicia such as a pattern or shading.
  • the system information table 500 illustrated in Figure 9 is used by the XOS Content Management system and also by the User Interface Development System to locate the position of all files required by the XOS.
  • the first four fields of this one record since this table will only ever hold one single record, provides the root to all the paths required by both the User Interface Development system and the Content Management system The file root
  • the 502 is the root of the files from the perspective of the clients - all these files being stored on a server. From this root one gets the html file path 510 which is the file path to all of the html and cold fusion pages, the ess file path 518 which is the path to all the style sheet files, the client image file path 526 which is the path to all the images stored on the clients, the server image file path 534 which is the path to all the images stored on the server, the client sound file path 540 which is the path to all client sounds, and the server sound file path 548 which is the path to all of the sounds stored on the server.
  • the html file path 510 which is the file path to all of the html and cold fusion pages
  • the ess file path 518 which is the path to all the style sheet files
  • the client image file path 526 which is the path to all the images stored on the clients
  • the server image file path 534 which is the path to all the images stored on the server
  • the client sound file path 540 which is the
  • the physical root field 504 is the root for the path of the files stored on the server from the perspective of the server.
  • the html physical path field 514 takes one--to all the html physical paths on the server, whilst the physical path to all of the style sheets is by field ess physical path 522.
  • the field for all the images stored on the clients is by field client image physical path 530, all of the images stored on the server by field server image physical path 536, all the sounds stored on the clients, by client sound physical path 544 and all the sounds stored on the server by server sound physical path 552.
  • the web root address 506 allows one to access files over the web.
  • html web path 510 one has a path to all the html and cold fusion pages, ess web path 524 being the path to all the style sheets, to the client images being client image web path 532, to the server images server image web path 538, to the client sounds client sound web path 546, and to the server sounds server sound web path 546.
  • “Web” is access to the files over the Internet.
  • One extra path which is the "Relative” path, is the path to the files when running the XOS. Firstly there is a relative path to get to the html directory, the html relative path 512, then a relative path to get to the ess relative path 520 storing the style sheets, the client image relative path 528 that will be the actual position of the files on the client hard drive and the server image relative path 535 that gives the relative path to access the images stored on the server.
  • the client sound relative path 542 provides hard drive location on the client where the sound files are stored and the server sound relative path 550 indicates the relative path to all the sound files on the server.
  • the System table includes several additional fields.
  • the maintenance web path 556 indicates the address from which the XOS can go to the User Interface Development system. This is because the User Interface Development system uses the XOS for navigation.
  • the XOS web path 558 is used by the User Interface Development system to load the XOS into the original.
  • SoundTheme which simply has a sound theme ID 604 and a description 606.
  • the description is solely for use by the operator in the Content Management system so that they can easily distinguish between the sound themes.
  • This sound theme description is also displayed for a menu in the Screen Builder utility.
  • the sys category 608 tracks the originator of any amendments (as mentioned above).
  • buttons 612 and 614 For each sound theme 610 one then identifies which button type 612 and which sound 614, therefore there is a link back to the SoundTheme and also to our Buttons table. For example, in a particular sound theme the operator may select the button type 612 product to have the sound set of 10. An operator may then select a condiment which has a particular type ID to have a sound ID 614 of 20. Therefore any screens which apply this sound theme will have all products buttons using the sound set which belongs to sound ID 10 and all condiments on this screen with a sound set which has the sound ID 20. An operator can enter any button types into the sound LD, but must have a sound ID for each particular button type. Sound Themes are set both in the Content Management utility and the User Interface Development system.
  • the Sound Theme may be set for a screen and also for a profile.
  • Each screen in the XOS is stored separately in the Xerts database.
  • a screen may be a separate html page or it may be a segment of video used to navigate through the menu screens.
  • Each screen contains buttons. These buttons may be used for navigation purposes in the navigation video or to order products on a menu.
  • the system uses the VideoTime table 620, the Screens table 622, the Button table 624, the ScreenType table 626 and the ButtonType table 628.
  • the primary table in this respect is the Screen table. For every single screen in the XOS there is an entry in this table. First there is a unique identifier for that table, the screen ID 630, and then if appropriate an image ID 632 for the screen. This contains the background image ID for the screen and is a foreign link to the ImageCatalog table.
  • the image ID may be, for example, a background or it may actually contain a set of images that make up the screen.
  • an image ED that contains all of the buttons that appear on that screen such as scrolling up and down, the transmit button, the apply changes button and so on. In the preferred embodiment, there are fifteen buttons that appear on that particular screen. However these are grouped into a single image set.
  • Each image set has the one image ID.
  • the sound JJD 634 is the same as the image ID. It may be a background sound that plays when a particular page is open or may be a group of sounds that are played when certain buttons in the XOS are selected. For example, when a user returns to the transmit screen LD and selects the apply changes button a sound will be played, however when the user selects the scroll up or scroll down button different sounds may play.
  • the source file 636 is the html file that is referenced whenever this screen is requested. For example it may be the file act-menu if one is looking at a menu page or act-navigator if one is looking at a navigation page. Below that is the style sheet file 638. If this particular screen uses an individual style sheet for example on a menu screen, mains and grills will use a different style sheet to those in build-a-burger. The operator may provide a name for the style sheet here.
  • the category ID 640 is used in the XOS when working with advertisements. When one loads a new page in the XOS the category ID of that page is set to advertisements. If one has a particular advertising group that matches that category ID one displays the advertisements in that group. Otherwise the system advertisements will be played.
  • Field 642 is the profile ID and all screens belong to a profile.
  • the child lock enable 644 screen enables the child lock facility. This file does not need to be used.
  • the screen type ID 646 defines which particular screen a user is viewing and will be described further when considering the ScreenType table.
  • Field 648 is the sound theme ID for this screen, which may be set either into the User Interface Development system or the Content Management utility. This is a sound theme that will apply a certain sound to all buttons on a menu screen.
  • the incidental ID 652 which relates to the LD of another screen, will be called after a random number of user selections if the incidental ID is available for that screen.
  • a screen may include either an individual html page or video sequence.
  • VideoTime table 620 there is a foreign key link 654 to our screen and the table has a number of video times. If the screen, be it a video or a normal html file, has a video that must play as a user enters the screen there needs to be a video start and end time. These times are provided by the intro start field 656 and intro end field 658. This segment will usually be around two seconds and it is played whenever the user enters or leaves the screen. If this particular screen is actually part of the video, an operator is required to enter the times for when the screen starts and ends, namely, the main start field 660 and main end field 662.
  • an exit start field 664 and an exit end time field 666 whenever a video is to be played and a user indicates that they wish to exit the screen. For example, an operator may arrange a particular video sequence to be played when a user exits this screen.
  • Every screen has a particular type field 668 and these are stored in the Screen Type table 626. For a particular type there is a description 670. This is solely for viewing in the User Interface Management system. A list of what is required for that screen is provided. Depending on whether these are set to one or zero, being true or false, the User Interface Management system will allow an operator to enter values into these fields. For example, if we have reqBGImage 674, reqCSS 676 or require video exit 678, then those fields will be available for any entry in the User Interface Management system. It will be recognised that not all fields are relevant for all screens.
  • buttons allow users to navigate to further screens in the XOS, and also allow users to order items through the XOS.
  • the button table 624 there is a screen ID 670, which is a foreign link to the screen on which the button is placed.
  • the image ED 672 indicates what image to display for that particular button, remembering that a single image ED is actually a set of images.
  • an image ID which is made up of a set of four images; an image to be displayed when the image has been de-selected, an image for when the image has been selected, a large image for display at the centre of the menu and finally, an image to display when a product is ordered we need button to display on the transmit screen.
  • the position of the button on the screen is recorded in the pos X 676 and pos Y 678 (coordinates) fields and the height 680 and width fields 682.
  • the link ID field 684 indicates to the XOS which screen to call when a product image is selected by a user. For example, if a user orders a music video they select the music video button for an artist and then select the add button. The link ID indicates to the XOS which screen should be referenced that contains the ordered music video.
  • the parent ED 686 is used in the case of condiments. Condiments are linked to a particular food image and therefore the XOS needs to know which food images particular condiments are related to so that it only appears in the correct position in the XOS. For example, if a user selects a salad, only the available condiments for that particular salad should be displayed.
  • the product ED 688 indicates to the XOS which product to order when the customer selects a particular image. This is only used for product images. This product ED is used when transferring information to and from the Micros system.
  • the sound ID 690 is the sound set thatis to be played whenever a particular button or image is selected. The sound set may have different sounds for the different states of the button. For example, for a product image there may be one sound when the product image is deselected, and another when the product image is selected.
  • no order button 692 may be set to true or false. A user may press this button only if they have ordered an item. For example, to get to "fun" menu there is a navigational button. However, the XOS can be programmed to prevent users from accessing the "fun" menu where they can play games and watch videos etc, until they have ordered an item such as food or a drink.
  • buttonsType table 628 There is the button type ED 694 which is a foreign key link back to the button type ED 674 in the Button table.
  • the description 696 is used solely in the User Interface Development system to allow the operator to recognise which button type they are referencing. The system advises the operator in the User Interface Development system what image set and sound set is applicable to an image of functional button. For example, for an image type product button there are four images within the set; a de-selected, selected, enlarged and a selection screen. For a condiment button only these images are required; namely, deselected, selected and a selection screen image. Therefore we want to ensure that whenever a system operator creates a button type product they are only dragging a product button onto the screen.
  • the User Interface Utility generally referred to as the XOS Content Management Utility for the preferred embodiment, comprises a main screen 700 illustrated in Figure 12. This screen is divided into three aspects represented by the three tabs 702, 704 and 706.
  • the first tab 702 relates to the profile maintenance and allows one to edit any details required with respect to each individual profile, Figure 12 illustrating the functions available under the profile tab.
  • the audiovisual maintenance tab 704 allows one to edit the images and the sounds used by the XOS. As can be seen in Figure 13, there are a total of six choices including Item Type Maintenance 708, Image Maintenance 710, Sound Maintenance 712, Sound Theme Maintenance 714, Import Files 716 and Remove Files 718.
  • the system maintenance tab 706 allows you to edit any system details and as shown in Figure 14 includes choices such as XOS/Micros category assignment 720, Edit XOS Categories 722, System Directories 724, Edit Table Details 726, Table Colour Maintenance 728, Screen Types 730, Button Types 732, Product Maintenance 734, Advertisement Profiles 736 and Advertisement Groups 738.
  • the menu and the tool bar allow for other different functions.
  • Under File (this illustrated in Figure 15) there is a close option 744 that will return one to the main menu.
  • the Edit button the edit area allows one to edit a new record or delete a record. However this may also be achieved by the plus and minus button in the toolbar.
  • a search function is also provided that allows one to move forward and backward though the records. There is also a find choice for locating records and Help simply provides help through the system.
  • the four arrows 746 on the tool bar enable one to scroll through the records on the grid.
  • the plus symbol 748 allows one to enter a new record enabling the tick 750 or the undo function 752 on the tool bar.
  • the tick as one would have thought, allows one to save changes whilst the undo cancels changes. If one selects the tick any error messages will appear at the bottom of the menu.
  • the edit menu also allows one to save and undo.
  • the minus button 754 will delete any record whilst the filter button 756 will allow the operator to search through the records for a specific entry.
  • the Profile tab in the Content management Utility provides a number of options for the operator. It enables the operator to edit all the details for each profile in the XOS. Referring now to Figure 12 a list of all the current profiles is listed in the Description grid 758 at the left hand side of the window, whilst the details for that profile window are shown to the right.
  • identifier 760 which as an arbitrary number. Besides that is a message 762 whether or not the current profile is valid, that is, whether or not it may be used in the XOS. Thus one can see that the April 2000 profile is valid.
  • To validate a profile one presses the validate profile button 764. Then there is the description 766 which is the name of the profile that will be seen in the Host Podium and Order Manager systems. Below that is the time period 768, which is the default time period for that particular profile.
  • Edit screens 772 allows one to edit any screens used in the profile, that is all the screens that make up a XOS.
  • Edit category images 774 allows one to edit the category images for a profile, that is, the images that are shown for each category in the XOS. For example the bottom left hand side of the XOS in the shopping cart and also the selection screen.
  • Validate Profile 764 allows one to validate a profile.
  • the visual and audio maintenance tab allows one to edit the images and sounds using the XOS.
  • the first button being the Item Type Maintenance 708 allows one to edit the type of images and sounds, the second 710 the images and the third 712 allows one to edit the sounds.
  • the sound theme maintenance button 714 allows one to edit the sound themes on the menu screen of the XOS.
  • the import files button 716 is used to import files into the XOS whilst the remove button 718 is used remove the files that are no longer required, generally the old files.
  • This tab allows one to edit all of the system related details for the XOS.
  • the first two buttons 720 and 722 allows us to edit the XOS categories and assign them to Micros categories.
  • This tab also enables editing of the advertising creating groups and profiles.
  • the following section relates to the video graphical functions of the XOS system and describes adding an image name to the database where one of the graphics within the image name is actually a movie that will run from the net-show streaming server.
  • one begins by adding the image name in the normal process.
  • the first of these is the description such as a product, which has a music video and has the name training.
  • the operator selects an item type - in this case the Music video type.
  • the system provides the operator with a dropdown box for each of the images associated with the image name.
  • the music video would have a stream next to it, meaning that this particular image may come from net-show theatre server.
  • a known streaming Video Selector Window is then provided where the operator defines it with a filename and tests the video. If the video plays fine the operator confirms the selection and the video file name will then appear in the correct drop-down box. The other images are selected as per usual and confirmed.
  • the profile maintenance tab to enure that the profiles are on the front, select the profile to be validated and then press the validate button. This process may generally take some time.
  • the profile validation window is displayed. On the left hand side it will show you the status of each of the individual system of the profile that it checked. At the bottom it will tell you whether or not the profile validation has been successful.
  • Edit Category images button 774 for the relevant profile in the XOS Management utility, after selecting a profile.
  • a new window 786 will appear showing a list of all XOS categories used in the XOS. These categories appear in the bottom left hand side of the XOS shopping cart and also in the selection screen. Each of these images is actually made up of two. The first image is the one that appears in the shopping cart, the second is the one that appears on the selection screen.
  • a style sheet 824 if appropriate a background image 826 and a background sound 828 , also if there is a sound theme we need to select a sound theme 830. If it is a menu it will need to have a XOS category 832. This XOS category is used so that whenever any food is ordered form the menu is added to the shopping cart and also the selection screen.
  • An Incidental screen appears when the type of screen is menu and is a video that will play after the user clicks the screen a random number of times whilst in the current screen, generally between 5 and 15.
  • Different main types of screens include the menu, the navigation screen including home, here one can see and also the use of the background image, which is the navigation video.
  • Another common type of screen is the transmit screen, the screen editor shown in Figure 22.
  • the background images are made up of all images required to be shown on the selection screen. On can flick through this images using the button 838 at the bottom of the Xerts image display catalogue.
  • the following section discusses the video times required in the Screen editor in the XOS Management utility.
  • introduction, menu or exit times for a particular screen. These times refer to particular segments of the navigation video that you one may wish to play.
  • times refer to particular segments of the navigation video that you one may wish to play.
  • the screen itself is part of the navigation video such as the home, eat, fun, XertsTV and shopping screen, the times that the Video will play when showing that screen will need to be entered. For example, in the eat screen one can see that the particular screen runs from 50 to 70 seconds of the particular navigation video.
  • the exit time is the section of the navigation video you wish to display when one is exiting a particular screen. Much like the introduction this will usually be two seconds long.
  • a typical navigation screen 840 is shown in Figure 23, together with its buttons. To edit the buttons for a navigation screen within a profile one first selects the screen from the grid on the left hand side of the screen editor menu, in this case we want to edit home, then select the Edit Buttons button.
  • Each of the boxes 844 represents a virtual button on the navigation video.
  • the highlighted box 846 is the one currently selected over in the navigation button editor.
  • the navigation button editor 848 we can select the screen 850 that this button links to, that is the screen that the XOS will navigate to once this button has been pressed, the X, Y, height and width 852 which are determined by dragging and dropping a new box size, and also the sound 854 that is played when the button is pressed. There is also disabling if no order option 856.
  • buttons may select the buttons by simply pressing on them and therefore see the details on the left hand side.
  • To create a button on a navigation screen first select the part of the video, as this is the screen that we wish to add the button to. If, for example we select home we then need to select the Edit Buttons button. Here we can see all of the buttons currently enabled on the video. They are shown by square, with the highlighted or green colour square the one currently selected.
  • To add a new button press the plus button and then simply click and drag to insert your button, the new button 858 shown in Figure 24 with its details shown in the navigation button editor screen on the right hand side
  • a button Once a button has been created one needs to link it to a screen, such as a training screen. We may also apply any sounds to this button and also decide whether or not this button will be disabled if there is no order. Currently Fun, XertsTV and Shop are disabled unless the customer orders food or drink. Once you are happy with the new button press the green tick and then close the window whereby we are returned to the screen editor window.
  • buttons you wish to edit To edit a button in the navigation screen, select the button you wish to edit. The button will be highlighted and any details in the navigation editor can be changed, such as disable if no order. Simply dragging and dropping a new box over the top can change the size of the box. The changes can then be confirmed and saved by pressing the green-tick.
  • An item type is the type of image and sound set used by the XOS.
  • the edit these types press the Item Type Maintenance button 708 that will bring up the Item Type Maintenance Form 860 shown in Figure 25.
  • On the left hand side we have a list 862 of all the different item types used by the XOS.
  • a condiment button image requires three items that are an image, the first item must be a selected button image, the second item must be a de-selected button image and the third item a selection screen image, all three having to be JPEG files.
  • the condiment button sound type requires two items, it is S for a sound type, and that the first item is a de-selected sound and the second item a selected sound, both of which must be WAV files.
  • To add an item type presses the plus button in the Item Type Maintenance Form, enters the type description and whether or not this type will be an image or a sound. Once selected the choice is confirmed by the tick. To delete an item type first select it and then press the minus button. Then confirm the delete when prompted.
  • Image Maintenance button 710 To edit images select the Image Maintenance button 710.
  • the data window or the Image Maintenance form 874 will then be loaded.
  • On the left hand side there is a list 876 of all current items, in this case image names.
  • On the right hand side there are the details for each of these images names.
  • the image names 884 is made up of a selected button, a de-selected button and a selection screen. In the catalog display in the lower right hand corner you lay see all of the three images, being the selected, de-selected and selection screen images.
  • the first image is a selected image
  • the second is the de-selected image
  • the third is the large image
  • the fourth is the video related to this product.
  • the image name is actually made up of several individual images collated as a group. Using this form we can therefore add, edit or delete any image names.
  • the image name is first selected. The details relating to that image are then shown on the right hand side. We can edit the fields by simply typing within them, such as the description. The item type cannot be edited, only the images within that item type. To change the item type the image name must be deleted and re-created. Once all the desired fields are changed we validate it by selecting the tick that will save the changes to the database. Editing Sound Themes
  • a sound theme is used on the XOS menu screens and applies particular sounds to each type of button depending on what is set in this form. For example any XOS menus using the-first sound theme, all product buttons will have PRD - set one as their sound whilst all help buttons will use the HLP - set one sounds. This ensures that all buttons of the same type on the screen are using the same sounds. From this screen one may edit, add or delete sound themes as is necessary.
  • a sound theme To edit a sound theme first select the sound theme 890 on the grid on the left-hand side. The fields may then be edited by either typing in the files, such as the description 892, or selecting a new option form the different drop-down boxes. Once all the changes have been made we press the tick, which results in the changes being made and the sound them being updated,
  • the Import Files button 816 To import files one selects the Import Files button 816.
  • the File Import Window 894 as shown in Figure 30 will appear.
  • the type of file to import has to be selected, such as sounds 896, images and movies 898.
  • We then select the drive from which the images are to be imported Then we browse as is normal in an explorer window until we find the directory where the files are stored. Then a list of all files matching the extension listed in the select file type area of the screen.
  • To then import all of the images you simply click on the Import button 900. We then click and drag until all of them are highlighted and press the Import button. At the bottom left hand corner a message Copy Complete! will pop up to tell us that the copy has been completed.
  • Removal Files button 718 which will load the remove files from 902 illustrated in Figure 31.
  • the form allows us to delete any files that are no longer required.
  • a list of the relevant files is then listed.
  • a XOS category is the category that one sees in the XOS, both in the order pad at the bottom left side of the XOS and also the selection screen.
  • We may edit these categories by selecting the Edit XOS category button 722 that will open the XOS Category Editor form 906 illustrates in Figure 32. To the left is a list 908 of all the current categories and on the right is the description 910 for each of these categories. Selecting a category and moving it up and down using the arrows may change the display order of the categories.
  • the colour of the table represents the waiter responsible for the table.
  • Table Colour Maintenance button 728 brings up the form 934 illustrated in Figure 35. From here, there is a list 936 of all current table colours. On the right we see a description 938 of the colour plus the colour 940 itself. We can select the particular colours and even define our own custom colours.
  • To add a new table colour we press the plus button, enter a description and then choose the particular colour by pressing the button 942 to the right hand side of the colour box. This brings up the Colour form 944 as illustrated in Figure 36.
  • To create a custom colour we press the define custom colours button 946. Thus, for example to select a light green we select that colour and press the add to custom colours button. If you are happy with the colour press the tick.
  • the first area 950 has two columns.
  • the first is a list 952 of all the products, which have been imported directly in from Micros, the second 954 the XOS category names.
  • the middle area 956 has a set of images that are not used on this product. Only product and condiment images are shown in this list.
  • the third area 958 or column has any product or condiment images that have been correlated with the particular product highlighted on the left hand side.
  • the Screen Types button 730 which will load its form 966 illustrated in Figure 38.
  • On the left hand side is a list 968 of all the different types of screens ' available for use in XOS. Most of these will probably not need to be changed unless redevelopment within the XOS occurs.
  • the first type of screen is the Border Screen 970 that provides the border of the XOS.
  • the second is the Child Lock Verification Screen 972 , which is the screen that is shown whenever a customer is asked to use their smart card.
  • the Disabled Button Screen 974 is the screen shown whenever the customer is prevented from entering other parts of the XOS until they have ordered either food and/or drink.
  • the End Point From Menu 976 is a screen that appears once an item on a menu has been ordered, for example if the customer order a music video, it will play in a second screen which will be cold an end point from a menu.
  • the End Point Form Navigation 978 is as above but coming from navigation rather than a cold fusion menu page.
  • the Help 980 is the screen in which the help video is played.
  • the Home Screen 1082 is the initial screen of the XOS, the screen from which the five menu items are available, eat, drink, fun, XertsTV and shopping. Only one home screen may be available per profile of the XOS.
  • the Incidental Screen 984 is a screen that appears after a random number of clicks on a menu screen.
  • the Media Player Error Screen 986 is a screen that shows when a media player error occurs, such as problems with the theatre server.
  • the Menu 988 is the menu from which the customer orders products.
  • the Navigation 990 screens use the navigation video, such as that for the home screen and the sub screens from there, i.e. the drink, eat, fun, XertsTV and shopping.
  • the No Buttons Screen 992 is used when a particular menu screen has no products on it, such as a profile with no alcohol so that the food and beverage manager would remove all alcohol buttons from that menu. When that menu is opened it will count the number of product buttons and if it is zero will open the No Buttons screen.
  • the Options screen 994 is the one appears when the customer presses the options, such as to call a waiter or request a bill.
  • the Order Submitted Screen 996 is the screen that appears once a customer has submitted their order to the kitchen.
  • the Selection 998 is a screen that is shown to the customer when they have pressed the transmit button listing all food and drink items ordered but not yet sent to he kitchen.
  • the Shutdown Screen 1000 is a screen showing a final video when the XOS is shut down.
  • the Welcome Screen 1002 is the initial open up screen that the XOS opens up to.
  • the video intro is whether or not we want to play a sequence of videos whenever the customer enters this particular screen. We then need to decide whether or not the screen itself will be part of the video. If we want to play a sequence of videos whenever a customer exits the screen we tick the video exit option. If the sound theme is enabled, the user will be able to select a sound theme that applies to all buttons on a menu in the XOS.
  • the category is whether or not this particular screen leads to a particular XOS category. Thus, for example if we are looking at drinks, whenever anything new on a screen is ordered, the number of drinks in the order pad will increase by one and also in the transmit screen the items that is ordered will appear below the drinks. We finally need to decide whether this particular screen is allowed an incidental video. This has been discussed previously. Once all the details are entered we press the tick to save the new screen. To delete a screen type first select the screen on the left hand side grid and then press the minus button. The deletion will now have to be confirmed and after that will be deleted.
  • buttons type button 732 To edit a button type select the Button Type button 732. We will then see the button type form 1004 as illustrated in Figure 39. On the left hand side form there is a list 1006 of all the buttons available and to the right there is a list 1008 of all the details.
  • the current button types are the Add button. The types of images and sounds that are selected in this screen are applied in different areas of the system.
  • a condiment button uses a condiment type of image and sound, and relates to ordering a condiment.
  • a DCR condiment has an image but no sounds, such as the thermometer where an animation occurs whenever a user selects a new condiment.
  • the dummy condiment has no image or sound types and are used with the DCR condiment since the DCR condiment does not have all three condiments that a normal button does, so we need to create dummy condiments.
  • the Help button shown at the bottom of each screen has an image but no sound. There is also the help video and the navigation button that are virtual hotspots on a video that when clicked will either move to a new spot on the video or an html page or an end mode.
  • the product button uses images and sounds and is each of the large products available on a menu for selection.
  • the selection screen button use a transmit image and a transmit sound.
  • buttons type press the plus button and then enter a description of the type.
  • type of images that may be applied to this button, such as a background image.
  • type of sounds such as any sound. The choices shown the drop-down box
  • System Directory button 824 that will load the system information form 1012 illustrated in Figure 41.
  • the directories listed above the black line 1014 are the root paths to which all other directories are related.
  • the directories below relate to the paths in relation to other files of the XOS. These will not be described in detail. They can all be changed by typing in the boxes and validated by selecting the tick.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • User Interface Of Digital Computer (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Cash Registers Or Receiving Machines (AREA)

Abstract

L'invention concerne un système de gestion d'interface d'utilisateur pouvant être mis en application par un administrateur de système et permettant à des administrateurs relativement compétents de donner la possibilité à des opérateurs moins compétents de développer et/ou de modifier l'aspect visuel d'une interface d'utilisateur. Ce système comprend des moyens servant à créer des articles disponibles afin de les afficher dans un système de développement d'interface d'utilisateur et de permettre à un opérateur de les intégrer par la suite dans l'aspect visuel d'une interface d'utilisateur, la création d'articles disponibles consistant à générer un objet afin de représenter cet article, l'objet comprenant des attributs sélectionnés par l'administrateur de système et associés à cet objet.
PCT/AU2001/001070 2000-08-25 2001-08-27 Systeme et procede de gestion d'interface d'utilisateur Ceased WO2002017058A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001285572A AU2001285572A1 (en) 2000-08-25 2001-08-27 A user interface management system and method

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
AUPQ9641A AUPQ964100A0 (en) 2000-08-25 2000-08-25 A content management system and database for an interactive system and method for food and/or entertainment used in venue such as a restaurant
AUPQ9642A AUPQ964200A0 (en) 2000-08-25 2000-08-25 A screen or menu builder of an interactive systemand method for food and /or entertainment used in a venue, such as a restaurant
AUPQ9643A AUPQ964300A0 (en) 2000-08-25 2000-08-25 Interactive system and method for food and/or entertainment used in a venue such as a restaurant
AUPQ9643 2000-08-25
AUPQ9641 2000-08-25
AUPQ9642 2000-08-25

Publications (1)

Publication Number Publication Date
WO2002017058A1 true WO2002017058A1 (fr) 2002-02-28

Family

ID=27158240

Family Applications (5)

Application Number Title Priority Date Filing Date
PCT/AU2001/001071 Ceased WO2002017059A1 (fr) 2000-08-25 2001-08-27 Procede et systeme de developpement d'une interface utilisateur
PCT/AU2001/001072 Ceased WO2002017060A1 (fr) 2000-08-25 2001-08-27 Systeme video et de gestion de video, destine a la navigation dans un systeme interactif
PCT/AU2001/001069 Ceased WO2002017156A1 (fr) 2000-08-25 2001-08-27 Systeme et procede interactifs de commande et de gestion
PCT/AU2001/001068 Ceased WO2002017155A1 (fr) 2000-08-25 2001-08-27 Systeme utilisateur interactif et procede faisant appel a des profils
PCT/AU2001/001070 Ceased WO2002017058A1 (fr) 2000-08-25 2001-08-27 Systeme et procede de gestion d'interface d'utilisateur

Family Applications Before (4)

Application Number Title Priority Date Filing Date
PCT/AU2001/001071 Ceased WO2002017059A1 (fr) 2000-08-25 2001-08-27 Procede et systeme de developpement d'une interface utilisateur
PCT/AU2001/001072 Ceased WO2002017060A1 (fr) 2000-08-25 2001-08-27 Systeme video et de gestion de video, destine a la navigation dans un systeme interactif
PCT/AU2001/001069 Ceased WO2002017156A1 (fr) 2000-08-25 2001-08-27 Systeme et procede interactifs de commande et de gestion
PCT/AU2001/001068 Ceased WO2002017155A1 (fr) 2000-08-25 2001-08-27 Systeme utilisateur interactif et procede faisant appel a des profils

Country Status (1)

Country Link
WO (5) WO2002017059A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2429106B (en) * 2004-03-01 2009-02-25 Ordatronics Pty Ltd Interactive terminal with advertising screen

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2006252191B2 (en) 2006-12-21 2009-03-26 Canon Kabushiki Kaisha Scrolling Interface
AU2006252194B2 (en) 2006-12-21 2010-02-11 Canon Kabushiki Kaisha Scrolling Interface
AU2006252196B2 (en) * 2006-12-21 2009-05-14 Canon Kabushiki Kaisha Scrolling Interface
US20160078571A1 (en) * 2014-09-12 2016-03-17 DoDine, Inc. Hotel Room Restaurant Delivery System
JP2018010517A (ja) * 2016-07-14 2018-01-18 東芝テック株式会社 情報入力装置およびプログラム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0449438A2 (fr) * 1990-03-30 1991-10-02 International Business Machines Corporation Système et méthode de gestion d'interface utilisateur graphique
US5297250A (en) * 1989-05-22 1994-03-22 Bull, S.A. Method of generating interfaces for use applications that are displayable on the screen of a data processing system, and apparatus for performing the method
WO1998037483A1 (fr) * 1997-02-19 1998-08-27 Gallium Software Inc. Interface-utilisateur et methode visant a la maximisation de l'information s'affichant sur ecran
US6016146A (en) * 1994-07-27 2000-01-18 International Business Machines Corproation Method and apparatus for enhancing template creation and manipulation in a graphical user interface

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5235509A (en) * 1989-06-28 1993-08-10 Management Information Support, Inc. Customer self-ordering system using information displayed on a screen
US5128862A (en) * 1989-06-28 1992-07-07 Management Information Support, Inc. Customer operable system for a retail store or fast-food restaurant having plural ordering stations
EP0618526A3 (fr) * 1993-03-31 1995-09-27 Us West Advanced Tech Inc Procédé et appareil pour un environnement vidéo multi-niveau et dirigeable.
US5762571A (en) * 1993-08-05 1998-06-09 Degaris; Kenneth Godfrey Ultra thin racquet frame
JP3014286B2 (ja) * 1994-12-16 2000-02-28 インターナショナル・ビジネス・マシーンズ・コーポレイション 直接操作のための補助装置及び方法
US5845263A (en) * 1995-06-16 1998-12-01 High Technology Solutions, Inc. Interactive visual ordering system
US5912668A (en) * 1997-05-30 1999-06-15 Sony Corporation Controlling a screen display of a group of images represented by a graphical object
US6087927A (en) * 1998-01-30 2000-07-11 Techknow, Inc. Order communication system for restaurant
WO2000033571A1 (fr) * 1998-11-30 2000-06-08 Sony Corporation Procede et dispositif de delivrance d'information
JP2001128115A (ja) * 1999-08-16 2001-05-11 Univ Of Washington 対話型ビデオ処理環境を実施するシステムと、その記憶媒体および処理方法
WO2001024518A1 (fr) * 1999-09-25 2001-04-05 Koninklijke Philips Electronics N.V. Generation d'interface utilisateur
SG99294A1 (en) * 1999-11-19 2003-10-27 Apex Pal Internat Pte Ltd Interactive menu system for restaurants
MXPA02007020A (es) * 2000-01-21 2004-01-30 Oneida Indian Nation Sistema operante de reclasificacion interactiva.

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5297250A (en) * 1989-05-22 1994-03-22 Bull, S.A. Method of generating interfaces for use applications that are displayable on the screen of a data processing system, and apparatus for performing the method
EP0449438A2 (fr) * 1990-03-30 1991-10-02 International Business Machines Corporation Système et méthode de gestion d'interface utilisateur graphique
US5509116A (en) * 1990-03-30 1996-04-16 International Business Machines Corporation Graphical user interface management system
US6016146A (en) * 1994-07-27 2000-01-18 International Business Machines Corproation Method and apparatus for enhancing template creation and manipulation in a graphical user interface
WO1998037483A1 (fr) * 1997-02-19 1998-08-27 Gallium Software Inc. Interface-utilisateur et methode visant a la maximisation de l'information s'affichant sur ecran

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2429106B (en) * 2004-03-01 2009-02-25 Ordatronics Pty Ltd Interactive terminal with advertising screen

Also Published As

Publication number Publication date
WO2002017060A1 (fr) 2002-02-28
WO2002017155A1 (fr) 2002-02-28
WO2002017156A1 (fr) 2002-02-28
WO2002017059A1 (fr) 2002-02-28

Similar Documents

Publication Publication Date Title
USRE46731E1 (en) Computer-based ordering system
US6769010B1 (en) Apparatus for distributing information over a network-based environment, method of distributing information to users, and method for associating content objects with a database wherein the content objects are accessible over a network communication medium by a user
US7673044B2 (en) Information processing system, apparatus and method for processing information, and program
US20050021417A1 (en) E-commerce shopping cart
US20020154157A1 (en) Website system and process for selection and delivery of electronic information on a network
US20130339180A1 (en) Collection creator and organizer for social media
US20020026386A1 (en) Personalized storage folder & associated site-within-a-site web site
US20030043144A1 (en) Organizing and interactively accessing information
WO2001078304A1 (fr) Systeme de site web et procede de selection et de distribution d'informations electroniques sur un reseau
US20110283173A1 (en) Methods and systems for designing photo books
US7092935B2 (en) Customizable filter interface
JPH01295363A (ja) 商品情報伝送・検索方法およびその装置
US20060068919A1 (en) Method and apparatus for playing video and casino games with a television remote control
WO2002017058A1 (fr) Systeme et procede de gestion d'interface d'utilisateur
KR100720565B1 (ko) 쇼핑몰 서비스 시스템의 시스템 운영 방법 및 이 시스템의구축을 위한 운영 방법
JP7309845B2 (ja) 会員登録システム、会員登録方法、及びプログラム
JP2003217030A (ja) Ｐｏｓシステム
JPH09146756A (ja) 注文管理システム
JP7659298B2 (ja) 飲食店を単位としたリサイクルウエブサイトシステム
JP5730171B2 (ja) 営業支援システム
JPH09146755A (ja) 端末装置
EP4361850A1 (fr) Système de liaison de disques
KR200260241Y1 (ko) 정보통신망을 통한 디브이디 방의 운영서비스 접속장치
JP2022121294A (ja) 小売店舗運用システム及び小売店舗運用方法
JPH1166162A (ja) 映像ビデオ商品の取引支援装置

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 69(1) EPC, F1205A DATED 21.08.03

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP