JP2014164443A - Order terminal, terminal monitoring device and terminal monitoring program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable provision of a proper service according to operation state of an order terminal.SOLUTION: A terminal monitoring device detects an operation event which has occurred in an order terminal for receiving a menu order by an operation input from an operation device and acquires operation log information including this operation event and an occurrence time of the operation event. The terminal monitoring device monitors whether an operation event satisfying execution criteria of a processing event has occurred within a limit time by referring the acquired operation log information on the basis of a monitoring table storing the execution criteria and the time limit, and executes the processing event for the execution criteria when it has occurred.

Description

  Embodiments of the present invention relate to an order terminal of a restaurant, a monitoring device for the terminal, and a terminal monitoring program for causing a computer to function as the monitoring device.

  In recent years, self-order systems for restaurants have been developed and put into practical use. This system includes an order terminal, a kitchen terminal, a POS (Point Of Sales) terminal, and a server that controls each terminal. Each terminal is connected to a server via a wireless or wired communication means. The order terminal is installed in the passenger seat. The order terminal has an operation device and a display device. A menu screen is displayed on the display device. A customer who arrives at the passenger seat operates the operation device and orders a desired menu item from the menu screen.

JP-A-9-212749

  In a self-order system of a restaurant that handles many menu items, the menu screen has a hierarchical structure. For this reason, customers unfamiliar with the operation of the order terminal cannot order menu items smoothly.

  A problem to be solved by an embodiment is to provide a terminal monitoring apparatus that can provide an appropriate service according to an operation status of an order terminal.

  In one embodiment, the terminal monitoring apparatus includes an operation detection unit, an operation log collection unit, and a monitoring unit. The operation detection means detects an operation event that has occurred in an order terminal that accepts an order for a menu by an operation input from an operation device. The operation log collection unit collects operation log information including an operation event and the time when the operation event occurred. For example, the monitoring unit refers to the operation log information collected by the operation log collection unit based on the execution condition and the time limit of the processing event set in the monitoring table, and the operation event satisfying the execution condition is within the time limit. Monitor whether it occurred, and if it occurs, execute a processing event for that execution condition.

Schematic of the self-order system. The block diagram which shows the structure of an order terminal. The schematic diagram which shows the example of a transition of the general image displayed on a display. The block diagram which shows the terminal monitoring function which CPU of an order terminal has. The schematic diagram which shows the record format of the operation log information preserve | saved at an operation log file. The schematic diagram which shows the record format of the screen log information preserve | saved at a screen log file. The schematic diagram which shows the data structure of a monitoring table. The flowchart which shows the process sequence of CPU performed according to a terminal monitoring program.

  Hereinafter, an embodiment of a terminal monitoring apparatus will be described with reference to the drawings. In this embodiment, the order terminal used in the restaurant self-order system is monitored, and the order terminal is equipped with its own monitoring function.

  FIG. 1 is a schematic diagram of a self-order system 10. The self-order system 10 includes a plurality of order terminals 11, a kitchen terminal 12, a POS terminal 13, an order management server 14, a radio base station 15, and a display device 16. The order management server 14 connects the kitchen terminal 12, the POS terminal 13, the wireless base station 15, and the display device 16 via a LAN (Local Area Network) 17 in a wired manner. Further, the order management server 14 wirelessly connects the order terminals 11 via the wireless base station 15.

  Note that the connection between the order management server 14 and the kitchen terminal 12, the POS terminal 13, the wireless base station 15, or the display device 16 may be wireless instead of wired. Further, the connection between the order management server 14 and each order terminal 11 may be wired instead of wireless.

  The order terminal 11 is installed in each seat of the restaurant. The order terminal 11 has at least an operation device and a display device. At least a menu screen is displayed on the display device. A customer who arrives at the passenger seat operates the operation device and orders a desired menu item from the menu screen. The order terminal 11 has a built-in wireless circuit and wirelessly transmits data relating to the ordered menu item, so-called order data.

  The radio base station 15 is attached to, for example, a ceiling portion of a passenger seat so as to perform radio communication with each order terminal 11. The radio base station 15 receives the order data wirelessly transmitted from each order terminal 11 and transfers it to the order management server 14 via the LAN 17.

  The order management server 14 stores the order data received from each order terminal 11 for each customer. The order management server 14 specifies the menu item for which the order has been received from the order data, and transmits data for identifying the menu item to the kitchen terminal 12.

  The kitchen terminal 12 is installed in the kitchen. The kitchen terminal 12 outputs information on the menu item identified from the data from the order management server 14, that is, the menu item for which the order has been received. The output method may be any of display, printing, and sound. Alternatively, one or more output methods may be combined. The person in charge of cooking in the kitchen grasps the ordered menu item based on the information output from the kitchen terminal 12, and starts cooking.

  The POS terminal 13 is installed at an accounting place (register). The POS terminal 13 receives, for example, an input of a passenger seat number as data for specifying a customer. In response to the input of the seat number, the POS terminal 13 transmits the seat number to the order management server 14. The order management server 14 detects the order data of the customer who has arrived at the seat of the received seat number from the order data for each customer stored in the storage unit. The order management server 14 transmits the detected order data to the POS terminal 13 via the LAN 17. The POS terminal 13 calculates a food and beverage price based on the received order data, and processes the accounting for the food and beverage price.

  The display device 16 is installed at a predetermined location in the passenger seat in order to display various information to the customer service representative. The number of display devices 16 is not limited to one. Display devices 16 may be installed at a plurality of locations in the passenger seat. Similarly, the number of kitchen terminals 12, wireless base stations 15, and POS terminals 13 is not limited to one, and can be increased as appropriate according to the scale of the store.

  FIG. 2 is a block diagram showing the configuration of the order terminal 11. The order terminal 11 includes a central processing unit (CPU) 21, a read only memory (ROM) 22, a random access memory (RAM) 23, an auxiliary storage unit 24, a clock unit 25, a radio circuit 26, and a touch panel 27. A system bus 28 including an address bus and a data bus is connected to the CPU 21. Then, the ROM 22, the RAM 23, the auxiliary storage unit 24, and the clock unit 25 are connected to the system bus 28. The wireless circuit 26 and the touch panel 27 are connected to the system bus 28 via an input / output circuit (not shown).

  The CPU 21 corresponding to the central part of the computer executes arithmetic processing required as the order terminal 11 according to a predetermined program. A ROM 22 corresponding to a main storage portion of the computer stores fixed data such as the above-described program. Similarly, the RAM 23 corresponding to the main storage portion of the computer stores variable data such as order data. The auxiliary storage unit 24 corresponding to the auxiliary storage part of the computer stores programs, data files, and the like. The auxiliary storage unit 24 also functions as a data backup area when the power is turned off. An HDD (Hard Disk Drive), an SSD (Solid State Drive), an EEPROM (Electrically Erasable Programmable Read Only Memory), or the like is applied as the auxiliary storage unit. The clock unit 25 measures the current date and time. The wireless circuit 26 performs wireless data transmission / reception with the wireless base station 15.

  The touch panel 27 includes a panel-type display 27d that is a display device and a touch sensor 27t that is an operation device. The touch sensor 27t is arranged so as to overlap the screen of the display 27d, and detects the position on the screen where the touch operation is performed.

  FIG. 3 is a schematic diagram illustrating a transition example of a general image displayed on the display 27d. When the order terminal 11 is in the idle state, the standby image 51 is displayed on the screen of the display 27d. When the touch sensor 27 t detects that an arbitrary place on the screen on which the standby image 51 is displayed is touched, the screen is switched from the standby image 51 to the menu image 52.

  The menu image 52 has a hierarchical structure. The menu image 52-1 in the first layer displays a category selection button for classifying menu items such as salads, grilled foods, fried foods, and beverages. In the menu images 52-2, 52-3,... In the second and subsequent layers, menu item selection buttons belonging to the selected category are displayed.

  For example, when a beverage is selected in the menu image 52-1, a menu image on the second layer in which buttons for selecting a category belonging to a beverage such as beer, Japanese type, shochu, and soft drink are arranged. 52-2 is displayed. Further, when beer is selected in the menu image 52-2, a menu image 52-3 on the third layer in which buttons for selecting a brand of beer are arranged is displayed.

  In the menu image 52, images of a confirmation button and an accounting button are also displayed. When the touch sensor 27 t detects that the confirmation button has been touched, the screen is switched from the menu image 52 to the order status image 53. In the order status image 53, information related to the menu item ordered by the customer by operating the order terminal 11 is displayed. The information includes contents such as whether cooking is in progress or serving. For example, when the order status image 53 is displayed for a certain time, the order status image 53 is deleted, and the screen returns to the menu image 52.

  When the touch sensor 27 t detects that the accounting button has been touched, the screen is switched from the menu image 52 to the accounting image 54. The transaction image 54 displays the details of the menu items ordered by the customer by operating the order terminal 11 and the total amount. For example, the accounting image 54 is deleted when displayed for a certain period of time, and the screen returns to the standby image 51.

  Here, the order terminal 11 includes a receiving unit that displays a menu image 52 on the display 27d and receives a menu order based on information input via the touch sensor 27t.

  The CPU 21 includes a terminal monitoring function 30. The terminal monitoring function 30 is realized by a terminal monitoring program. The terminal monitoring program is stored in the ROM 22 or the auxiliary storage unit 24 that is a program storage unit.

  FIG. 4 is a block diagram showing the terminal monitoring function 30. The terminal monitoring function 30 includes an operation detection unit 31, an operation log detection unit 32, a screen detection unit 33, a display log detection unit 34, a monitoring table 35 and a monitoring unit 35.

  The operation detection unit 31 detects an operation event that has occurred in the order terminal 11 by an operation input from the touch sensor 27t that is an operation device. The operation log detection unit 32 collects operation log information including an operation event and the time when the operation event occurred. The collected operation log information is stored in the operation log file 41.

  The screen detection unit 33 detects a screen event displayed on the display 27d which is a display device. The display log detection unit 34 collects screen log information including a screen event and the occurrence time of the screen event. The collected screen log information is stored in the screen log file 42.

  The monitoring unit 35 refers to the operation log information collected in the operation log file 41 based on the monitoring table 43 that stores the execution conditions and time limit of the processing event. The monitoring unit 35 monitors whether an operation event satisfying the execution condition has occurred within the time limit, and when it occurs, causes the order terminal 11 to execute a processing event for the execution condition. The monitoring unit 35 refers to the screen log information collected in the screen log file 42 based on the monitoring table 43. The monitoring unit 35 monitors whether a screen event satisfying the execution condition has occurred within the time limit, and when it occurs, causes the order terminal 11 to execute a processing event corresponding to the execution condition.

The operation log file 41, the screen log file 42, and the monitoring table 43 are stored in the auxiliary storage unit 24.
FIG. 5 is a schematic diagram showing a record format of the operation log information 41 r stored in the operation log file 41. As shown in the figure, the operation log information 41r includes information (event name, event code, etc.) specifying the operation event Vi and time information (hour / minute / second) when the event occurred. The operation log file 41 stores the operation log information 41r, for example, in order from the latest occurrence time.

  FIG. 6 is a schematic diagram showing a record format of the screen log information 42 r stored in the screen log file 42. As shown in the figure, the screen log information 42r includes information (event name, event code, etc.) specifying the screen event Wi and time information (hour / minute / second) when the event occurred. The screen log file 42 stores the screen log information 42r, for example, in order from the latest occurrence time.

  FIG. 7 is a schematic diagram showing the data structure of the monitoring table 43. As shown in the figure, the monitoring table 43 is divided into an execution condition data area 43a, a time limit data area 43b, and a processing event data area 43c. In the data area 43a, data related to an operation event or a screen event that is an execution condition of the corresponding processing event is set. A time limit until the corresponding execution condition is satisfied is set in the data area 43b. In the data area 43c, information (event name, event code, etc.) for specifying a processing event to be executed when a corresponding establishment condition is established within the corresponding time limit is set.

  Incidentally, the first line of the monitoring table 43 shown in FIG. 7 stores data indicating that the processing event Y1 is executed when the operation event V1 occurs m times within the time limit T1. The second line stores data indicating that the processing event Y2 is executed when the screen event W1 occurs n times within the time limit T2. The third line stores data indicating that the processing event Y3 is executed when the screen event W3 occurs following the screen event W2 within the time limit T3.

  FIG. 8 is a flowchart showing the processing procedure of the CPU 21 executed in accordance with the terminal monitoring program. The CPU 21 waits for an operation event Vi to occur (Act 1). When it is detected that the screen is touched by a signal from the touch sensor 27t, the CPU 21 determines that an operation event Vi has occurred (YES in Act1: YES in the operation detection unit 21). Then, the CPU 21 recognizes the operation event Vi from the screen state and the touch position, and generates operation log information 41r from the information specifying the operation event Vi and the time information read from the clock unit 25 (Act2). The CPU 21 writes the operation log information 41r to the operation log file 41 (Act3: operation log collection means 32).

  The CPU 21 determines whether or not a screen event Wi has occurred in response to the operation event Vi (Act 4). When the screen event Wi has not occurred (NO in Act4), the CPU 21 returns to the processing of Act1 and waits for the next operation event Vi.

  When a screen event Wi occurs (YES in Act4: YES, screen detection means), the CPU 21 generates screen log information 42r from information specifying the screen event Wi and time information read from the clock unit 25 (Act5). . The CPU 21 writes the screen log information 42r into the screen log file 42 (Act 6: screen log collection means 34).

  The CPU 21 reads information on the execution condition, the time limit, and the processing event set in the data areas 43a, 43b, and 43c of the monitoring table 43 (Act7). Then, the CPU 21 searches the operation log information 41r and the screen log information 42r stored in the operation log file 41 and the screen log file 42, and determines whether or not an event that satisfies the execution condition occurs within the time limit. Confirm (Act8). If no event that satisfies the execution condition has occurred (NO in Act 8), the CPU 21 returns to the process of Act 1 and waits for the next operation event Vi.

  If at least one event that satisfies the execution condition has occurred (YES in Act 8), the CPU 21 recognizes the corresponding processing event Yi. Then, the CPU 21 executes this processing event Yi (Act 9: monitoring means 35). Thereafter, the CPU 21 returns to the process of Act1 and waits for the next operation event Vi.

  Hereinafter, specific examples of the execution condition, the time limit, and the processing event will be described.

[Specific Example 1]
・ Execution condition: Operation event other than order 100 times ・ Time limit: 3 minutes ・ Processing event: Call of store clerk In the case of the above specific example 1, operation event other than the operation event that orders orders occurs 100 times in 3 minutes In this case, a clerk calling command is wirelessly transmitted from the order terminal 11 as a processing event. Incidentally, an operation event for instructing an order is generated when an order button is touched while a menu item is selected from the menu image 52-1.

  In the order terminal 11, the phenomenon that the operation event occurs 100 times in 3 minutes without the operation event for instructing the order is considered that the customer is at a loss in ordering the menu item. In such a case, in this embodiment, a salesclerk call command is wirelessly transmitted from the order terminal 11. The store clerk calling command is sent to the order management server 14 via the radio base station 15. The clerk call command includes information for identifying the order terminal 11 that is the command transmission source. In response to the clerk call command, the order management server 14 causes the display device 16 to display information on the seat where the order terminal 11 that is the command transmission source is installed. With this information, the person in charge of customer service can go to the corresponding passenger seat and give appropriate advice to the customer who is wondering about the operation.

[Specific Example 2]
-Execution condition: Order status image screen event 5 times-Time limit: 2 minutes-Processing event: Call of clerk In the case of the above specific example 2, the screen event for displaying the order status image 53 on the display 27d is 5 in 5 minutes If it occurs twice, a clerk call command is wirelessly transmitted from the order terminal 11 as a processing event. Incidentally, a screen event for displaying the order status image 53 occurs when a confirmation button is touched on the menu image 52.

  The event that the order status image 53 is displayed five times in five minutes on the order terminal 11 is considered that the arrangement of the ordered menu item is delayed. Even in such a case, in the present embodiment, a salesclerk call command is wirelessly transmitted from the order terminal 11. As a result, the information on the passenger seat where the command transmission source order terminal 11 is installed is displayed on the display device 16. With this information, the customer service representative can go to the corresponding passenger seat and confirm whether there is a menu item that is delayed in serving.

[Specific Example 3]
・ Execution condition: Transition from a screen event on the menu screen that accepts orders for menu items belonging to beer to a screen event on the menu screen that accepts orders for menu items that belong to fried foods ・ Time limit: 2 minutes ・ Processing event: Fried from 20% discount In the case of Example 3 above, a screen command for displaying a menu screen for accepting orders for menu items belonging to fried foods within 2 minutes from a screen command for displaying menu screens for accepting orders for menu items belonging to beers. Is generated, information on “20% off fried” is displayed on the display 27d as a processing event. In this state, when “fried” is selected from the menu items belonging to the deep-fried foods, 20% discount coupon information is added to the order data of this menu item “fried”. The coupon information is sent to the order management server 14 together with the order data of the menu item “karaage”. As a result, at the POS terminal 13, the sales amount of the menu item “karaage” is reduced by 20% during the accounting process.

  In other words, the service of issuing coupons for “20% discount from fried foods” to customers who have confirmed the menu item of fried foods within 2 minutes after confirming the menu item of beer is easy without the burden of the store clerk. Can be implemented.

[Specific Example 4]
・ Execution conditions: 3 menu screen events that accept orders for menu items belonging to salads ・ Time limit: 2 minutes ・ Processing event: Recommended salad 30 yen discount In the case of Example 4 above, menus belonging to salads When a screen event for displaying a menu screen for accepting an item order occurs three times within 2 minutes, information of “recommended salad 30 yen discount” is displayed on the display 27d as a processing event. In this state, when “recommended salad” is selected from the menu items belonging to salads, coupon information of 30 yen discount is added to the order data of this menu item “recommended salad”. This coupon information is sent to the order management server 14 together with order data for the menu item “recommended salad”. As a result, at the POS terminal 13, the sales amount of the menu item “recommended salad” is reduced by 30 yen during the accounting process.

  That is, a service for issuing a coupon of “recommended salad 30 yen discount” to customers who have confirmed the menu items of salads three times within 2 minutes can be easily performed without the burden of the store clerk.

  As described above, according to the present embodiment, an appropriate service can be provided from the store side to a customer who is an operator according to the operation status of the order terminal 11.

The present invention is not limited to the above embodiment.
For example, in the embodiment, the pattern in which the terminal monitoring function 30 is built in the order terminal 11 has been described. The terminal monitoring function 30 is not necessarily built in the order terminal 11. An information processing apparatus specialized for the terminal monitoring function 30, a so-called terminal monitoring apparatus, may be configured, and the terminal monitoring apparatus may monitor the order terminal 11 by being connected to the order terminal 11 by communication means. In this case, one terminal monitoring apparatus can simultaneously monitor a plurality of order terminals.

  In the embodiment, the operation device of the order terminal 11 is the touch sensor 24 t and the display device 24 d is the display of the touch panel 24. The display device 24d may be a single display device. In this case, a keyboard or a mouse is used as the operation device.

  Furthermore, in the said embodiment, the order terminal 11 was demonstrated as a stationary type installed in a passenger seat. The order terminal 11 is not necessarily limited to a stationary type. The present embodiment can also be applied to a portable order terminal called a handy terminal or the like.

  In the embodiment, the terminal monitoring program for realizing the functions of the invention is recorded in advance in the ROM 22 or the auxiliary storage unit 24 which is a program storage unit in the apparatus. However, the present invention is not limited to this, and a similar program may be downloaded from the network to the apparatus. Alternatively, a similar program recorded on the recording medium may be installed in the apparatus. The recording medium may be in any form as long as it can store a program such as a CD-ROM or a memory card and can be read by the apparatus. Further, the function obtained by installing or downloading the program may be realized in cooperation with an OS (operating system) in the apparatus.

  In addition, although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 10 ... Order entry system, 11 ... Order terminal, 21 ... CPU, 27 ... Touch panel, 30 ... Auxiliary storage function, 31 ... Operation detection means, 32 ... Operation log collection means, 33 ... Screen detection means, 34 ... Screen log collection means 35 ... monitoring means, 41 ... operation log file, 42 ... screen log file, 43 ... monitoring table.

Claims (6)

An operation detection means for detecting an operation event that has occurred in an order terminal that accepts an order for a menu by an operation input from an operation device;
Operation log collection means for collecting operation log information including the operation event and the time of occurrence of the operation event;
Based on the execution condition and time limit of the set processing event, the operation log information collected by the operation log collecting means is referred to monitor whether an operation event that satisfies the execution condition has occurred within the time limit. Monitoring means for executing a processing event for the execution condition when it occurs,
A terminal monitoring apparatus comprising: Screen detecting means for detecting a screen event that has occurred in an order terminal that displays a screen related to ordering a menu on a display device in response to an operation input from the operation device;
Screen log collection means for collecting screen log information including the screen event and the occurrence time of the screen event;
Based on the execution condition and time limit of the set processing event, the screen log information collected by the screen log collection unit is referred to and a screen event that satisfies the execution condition is monitored within the time limit. Monitoring means for executing a processing event for the execution condition when it occurs,
A terminal monitoring apparatus comprising: An operating device;
Accepting means for accepting an order for the menu according to information input via the operation device;
Operation detecting means for detecting an operation event generated by an operation input of the operation device;
Operation log collection means for collecting operation log information including the operation event and the time of occurrence of the operation event;
Based on the execution condition and the time limit of the set processing event, the operation log information collected by the operation log collection means is referred to monitor whether an operation event satisfying the execution condition has occurred within the time limit. Monitoring means for executing a processing event for the execution condition when it occurs,
An order terminal characterized by comprising: An operating device;
A display device for displaying a screen related to menu order in response to an operation input from the operation device;
Accepting means for accepting an order for the menu according to information input via the operation device;
Screen detection means for detecting a screen event that causes the display device to display a screen related to the menu order;
Screen log collection means for collecting screen log information including the screen event and the occurrence time of the screen event;
Based on the execution condition and time limit of the set processing event, the screen log information collected by the screen log collection unit is referred to and a screen event that satisfies the execution condition is monitored within the time limit. Monitoring means for executing a processing event for the execution condition when it occurs,
An order terminal characterized by comprising: On the computer,
A function for detecting an operation event that occurs in an order terminal that accepts an order for a menu by an operation input from an operation device;
A function of collecting operation log information including the operation event and the occurrence time of the operation event;
Based on the execution condition and time limit of the set processing event, referring to the collected operation log information and monitoring whether or not an operation event that satisfies the execution condition has occurred within the time limit. A function to execute a processing event for the execution condition,
Terminal monitoring program to realize On the computer,
A function for detecting a screen event that has occurred in an order terminal that displays a screen related to menu order on a display device in response to an operation input from the operation device;
A function of collecting screen log information including the screen event and the occurrence time of the screen event;
Based on the execution condition and time limit of the set processing event, referring to the collected screen log information and monitoring whether or not a screen event satisfying the execution condition has occurred within the time limit. A function to execute a processing event for the execution condition,
Terminal monitoring program to realize

Images