Management device, management method, and management program

Abstract

To improve efficiency of management of a restaurant.SOLUTION: A management device 10 of an embodiment converts a format of order information being information regarding an order of a cuisine to a store of a restaurant according to an in-store system installed in the store. The management device 10 notifies the in-store system of the converted order information. The order information contains information specifying the providing mode of the cuisine such as delivery, eat-in, and take out.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a management device, a management method, and a management program. [Background technology]

[0002] There are a wide variety of IT systems used by restaurant chains and their headquarters, including POS (Point of Sales) registers, OES (Order Entry Systems), mobile ordering systems, tabletop ordering systems, delivery platform systems, takeout platform systems, seating management systems, reservation ledger systems, CRM (Customer Relationship Management) systems, marketing systems, and business management systems.

[0003] Furthermore, among these IT systems, systems related to in-store operations such as order taking, cooking, and accounting support the work of restaurant employees by connecting to hardware such as kitchen printers, kitchen displays, cash registers (drawers), cashless payment terminals, and handheld terminals. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-187112 Summary of the Invention [Problem to be solved by the invention]

[0005] However, conventional technology has the problem that it may not be possible to improve the efficiency of restaurant management.

[0006] For example, there are cases where external systems such as delivery and takeout platforms are not linked to in-store systems (POS registers, OES), and in such cases, restaurant staff must manually input orders sent from external systems into the in-store system.

[0007] In addition, there are cases where information is not integrated between systems for ordering outside the store, such as a takeout platform system and a delivery platform system, and systems for ordering inside the store, such as a mobile ordering system and a tabletop ordering system, and in such cases, the store must manage each type of information separately.

[0008] In addition, if orders on each food and beverage business's dedicated takeout site are not linked to the store's in-store system (POS register, OES), the food and beverage business will need to manage orders on its own takeout site separately from orders placed in the store. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems and achieve the objectives, the management device is characterized by having a conversion unit that converts the format of order information, which is information regarding ordering food at a restaurant, in accordance with an in-store system installed in the restaurant, and a notification unit that notifies the in-store system of the order information converted by the conversion unit. [Effects of the Invention]

[0010] According to the present invention, the management of restaurants can be made more efficient. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a management system. [Figure 2] FIG. 2 is a diagram showing an example of conversion of order information. [Figure 3] FIG. 3 is a diagram showing an example of an order management screen. [Figure 4] FIG. 4 illustrates an example of the configuration of the management device. [Figure 5] FIG. 5 is a diagram illustrating an example of a format conversion table. [Figure 6] FIG. 6 is a diagram illustrating an example of a store information table. [Figure 7] FIG. 7 is a diagram illustrating an example of a product information table. [Figure 8] FIG. 8 is a flowchart showing the flow of processing by the management device. [Figure 9] FIG. 9 illustrates an example of a computer that executes a management program. DETAILED DESCRIPTION OF THE INVENTION

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A management apparatus, a management method, and a management program according to the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the following embodiments.

[0013] [Configuration of the first embodiment] First, the configuration of a management system according to the first embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the configuration of a management system.

[0014] As shown in FIG. 1, the information processing system 1 includes a management device 10, a management system 20, an in-store system 30, an output device 40, an output device 50, and a terminal device 60.

[0015] The management device 10 is connected to the management system 20, the in-store system 30, the terminal device 60, and the terminal device 411 via a network (for example, the Internet).

[0016] Furthermore, the management device 10, the management system 20, and the in-store system 30 may be realized by a server on the cloud.

[0017] The management device 10 converts and notifies the order information. The order information is information about ordering food from a restaurant. The order information includes information for identifying the restaurant and information for identifying the product. In the embodiment, the product is, for example, a dish.

[0018] A product is a dish served at a store. The ways in which products are served at a store include eat-in, delivery, take-out, etc. Eat-in means that the user eats in the store. Delivery means that a delivery person delivers the product to the user. Take-out means that the user takes the product home from the store.

[0019] Here, the format of order information that can be processed may differ depending on the system, and the management device 10 functions as a gateway that converts the format of order information to suit each system.

[0020] The management device 10 converts the order information input from the management system 20 and notifies the converted order information to the in-store system 30. The order information may also be input to the management device 10 from a terminal device used by a user.

[0021] The management system 20 is a web service or SaaS system for restaurants. For example, the management system 20 is a SaaS system that centrally manages a food delivery system, a mobile ordering system, an owned takeout site, or other web services for restaurants (for example, a non-owned takeout site), a SaaS system, or the like.

[0022] Here, the management system 20 is assumed to be a SaaS system that centrally manages one or more food delivery systems. The management system 20 is a system that provides services related to product delivery (home delivery). The management system 20 notifies the in-store system 30 and the delivery person who delivers the product of the order information received from the user. The management system 20 can notify the in-store system 30 of the order information via the management device 10.

[0023] A user 210 uses a terminal device 211 to transmit order information to the management system 20. For example, the terminal device 211 is a smartphone. The terminal device 211 also transmits the order information via a website or a dedicated application.

[0024] The management system 20 receives the order information from the terminal device 211. Then, the management system 20 notifies the management device 10 and the terminal device 221 used by the delivery person 220 of some or all of the received order information.

[0025] As described above, the management device 10 converts the order information input from the management system 20 and notifies the in-store system 30 of the converted order information.

[0026] The in-store system 30 is a system for processing orders and provision of products in the store. The in-store system 30 includes various systems related to the management of a restaurant, such as a store operation system, a kitchen management system, an OES, and a POS system.

[0027] The store operation system registers and edits the menu of dishes (products) served at the store, accepts orders, changes the order status, cancels orders, and relays order information to the OES. The OES notifies the kitchen of accepted orders. The POS system also tallys up sales from orders.

[0028] The in-store system 30 is also connected to an output device 40 and an output device 50. The output device 40 and the output device 50 output order information. For example, the output device 40 is a tablet terminal equipped with a monitor. The output device 40 may be directly connected to the management system 20 without going through the management device 10 and the in-store system 30. For example, the output device 50 is a printer.

[0029] The terminal device 60 is provided on a table in the store and is used by a user 420 who is eating (eating in) in the store. For example, the terminal device 60 transmits order information to the management device 10 based on an operation by the user 420. The terminal device 60 may also transmit the order information to the in-store system 30.

[0030] The terminal device 411 is used by a user 410 who wants to take out or eat in a product. For example, the terminal device 411 transmits order information to the management device 10 based on an operation of the user 410. For example, the terminal device 411 is a smartphone. The terminal device 411 also transmits the order information via a website or a dedicated application.

[0031] The management device 10 converts the order information received from the terminal device 60 and the terminal device 411, and notifies the in-store system 30 of the converted order information.

[0032] As explained above, the in-store system 30 receives order information from the management system 20, the terminal device 60, and the terminal device 411. The order information corresponds to any one of delivery, eat-in, and take-out.

[0033] The store employee 310 provides the product based on the order information presented from the in-store system 30 via the output device 40 or the output device 50.

[0034] For example, the employee 310 delivers the product to the delivery person 220 in accordance with the order information transmitted from the management system 20.

[0035] For example, the employee 310 provides the product to the user 420 in accordance with the order information transmitted from the terminal device 60. In this case, the employee 310 may hand over the product to the user 420 or may serve the product.

[0036] For example, the employee 310 delivers the product to the user 410 in accordance with the order information transmitted from the terminal device 411 .

[0037] Furthermore, the order information transmitted by the user 420 using the terminal device 411 may correspond to eat-in rather than take-out. In this case, the employee 310 may deliver the food to the user 420.

[0038] 1, the management device 10 functions as a conversion program 10a. The management device 10 also has a mapping DB 10b. For example, the conversion program 10a receives input from another system via an API.

[0039] The conversion program 10a converts the contents of the order information. For example, the conversion program 10a converts the values ​​of variables included in the order information. The order information includes a variable for identifying a store and a variable for identifying a product.

[0040] The conversion program 10a also converts the format of the order information, for example, converting the data format of the order information and the names of variables included in the order information.

[0041] The mapping DB 10b is a DB including a table that associates data before and after conversion in the conversion by the conversion program 10a.

[0042] Conversion of order information will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of conversion of order information.

[0043] The order information 20a before conversion is input to the management device 10. Here, it is assumed that the order information 20a is sent from the management system 20.

[0044] The management device 10 then outputs the converted order information 30a, which is then sent to the in-store system 30.

[0045] Here, the in-store system 30 handles order information in XML format. On the other hand, the data format of the order information 20a is JSON format. Therefore, the management device 10 converts the order information 20a in JSON format into XML format. Note that the in-store system 30 may handle order information in a data format other than XML format. Furthermore, the data format of the order information input to the management device 10 may be a format other than JSON format.

[0046] Furthermore, even if a variable means the same information, the variable name and value may differ between the management system 20 and the in-store system 30.

[0047] For example, in the management system 20, the variable for identifying a store is "store_no." On the other hand, in the in-store system 30, the variable for identifying a store is "store_id."

[0048] Furthermore, the store whose "store_no" in the management system 20 is "100101" is the same as the store whose "store_id" in the in-store system 30 is "A501".

[0049] At this time, the management device 10 changes "'store_no':'100101'" in the order information 20a to "<store_id> A501< / store_id> " is converted to

[0050] 3, the in-store system 30 displays an order management screen 40a on the output device 40 based on the order information 30a. Fig. 3 is a diagram showing an example of the order management screen.

[0051] The order management screen 40a displays the time when the order was placed, the form of delivery, the order number, the product ID, the product name, the quantity, the sender, and the sender's order number.

[0052] The example in FIG. 3 shows that an order was placed at time "13:31" for a delivery method of "Delivery," order number "1035," product ID "251," product name "Hamburger Set," and quantity of 1. It also shows that the order was sent from "Delivery Service A," and the order number at the sender is "1001011305." As shown in FIG. 3, one order may include multiple products (for example, order number "1038").

[0053] In this way, the management device 10 can notify the in-store system 30 of the order information including the delivery format. The employee 310 also provides the product by referring to the order management screen 40a.

[0054] Furthermore, for example, employee 310 can accurately deliver the product by matching the sender and sender order number displayed on the order management screen 40a with the sender and order number provided by delivery person 220 or user 410.

[0055] Furthermore, the order management screen 40a can display all order information in a unified manner, regardless of the system that sent the order information or the form of product provision.

[0056] Therefore, a store can process all orders from different systems and in different delivery formats with, for example, one output device 40, without having to prepare an output device for each system.

[0057] The configuration of the management device 10 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the configuration of the management device.

[0058] As shown in FIG. 4, the management device 10 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0059] The communication unit 11 is an interface for the management device 10 to send and receive data to and from other devices.

[0060] The storage unit 12 is a storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), an optical disk, etc. Note that the storage unit 12 may also be a data-rewritable semiconductor memory such as a RAM (Random Access Memory), a flash memory, or an NVSRAM (Non Volatile Static Random Access Memory). The storage unit 12 stores an OS (Operating System) and various programs executed by the management device 10.

[0061] The storage unit 12 stores a format conversion table 121, a store information table 122, and a product information table 123. The format conversion table 121, the store information table 122, and the product information table 123 correspond to the mapping DB 10b in FIG.

[0062] As shown in Fig. 5, the format conversion table 121 is a table showing the data format and variable names of the order information for each system. Fig. 5 is a diagram showing an example of the format conversion table.

[0063] Figure 5 shows that the data format of the order information for system "N011" is "JSON," the variable name corresponding to the time is "time," the variable name corresponding to the store ID is "store_id," the variable name corresponding to the delivery format is "form," the variable name corresponding to the order number is "order_no," and the variable name corresponding to the product ID is "product_id."

[0064] Figure 5 also shows that the data format of the order information for system "N012" is "XML," the variable name corresponding to the time is "order_time," the variable name corresponding to the store ID is "store_no," the variable name corresponding to the delivery format is "form_id," the variable name corresponding to the order number is "order_number," and the variable name corresponding to the product ID is "product_number."

[0065] For example, system "N011" is the management system 20, and system "N012" is the in-store system 30.

[0066] As shown in Fig. 6, the store information table 122 is a table that associates system IDs, store IDs, and store names before and after conversion. Fig. 6 is a diagram showing an example of the store information table.

[0067] Figure 6 shows that the store ID for a store named "ABC Burger Shinagawa Store" in the system "N011" before conversion is "100101," and the store ID in the system "N012" after conversion is "A501."

[0068] As shown in Fig. 7, the product information table 123 is a table that associates the system ID, product ID, and product name before and after conversion. Fig. 7 is a diagram showing an example of the product information table.

[0069] FIG. 7 shows that the product ID of a product with the product name "Hamburger Set" in the system "N011" before conversion is "1002051", and the product ID in the system "N012" after conversion is "251".

[0070] Note that order information may be input from multiple systems with different product ID systems to the management device 10. Therefore, multiple pre-conversion product IDs may be associated with one post-conversion product ID.

[0071] In the example of FIG. 7, the product IDs before conversion, "1002051" and "2002064", are associated with the product ID after conversion, "251".

[0072] That is, regardless of whether the product ID indicated in the order information input to the management device 10 is "1002051" or "2002064," the in-store system 30 will accept an order for the "hamburger set."

[0073] The control unit 13 controls the entire management device 10. The control unit 13 is, for example, an electronic circuit such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a GPU, or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The control unit 13 also includes a GPU for executing image recognition processing.

[0074] The control unit 13 has an internal memory for storing programs that define various processing procedures and control data, and executes each process using the internal memory. The control unit 13 also functions as various processing units by running various programs. For example, the control unit 13 has a conversion unit 131 and a notification unit 132.

[0075] The conversion unit 131 converts the format of order information, which is information about ordering food from a restaurant, in accordance with the in-store system.

[0076] The conversion unit 131 can refer to the format conversion table 121 and convert the data format of the order information and the variable names and variable values ​​included in the order information in accordance with the in-store system.

[0077] The conversion unit 131 converts the first store information included in the order information into second store information and converts the first product information included in the order information into second product information by referring to the store information table 122 and the product information table 123.

[0078] In the example of Figure 2, "'store_no':'100101'" corresponds to the first store information, and<store_id> A501< / store_id> " corresponds to the second store information. In the example of FIG. 2, "'product_number':'1002051'" corresponds to the first product information, and "<product_id> 251< / product_id> " corresponds to the second product information.

[0079] The notification unit 132 notifies the in-store system of the order information converted by the conversion unit 131. The notification unit 132 notifies the store identified by the second store information that the dish (product) identified by the second product information has been ordered.

[0080] For example, in the example of FIG. 2, the notification unit 132 refers to the store information table 122 and the product information table 123 and<store_id> A501< / store_id> " is identified by the store "ABC Burger Shinagawa store,"<product_id> 251< / product_id> " has been ordered.

[0081] The notification unit 132 further notifies the customer of information indicating the type of food to be served, which is included in the order information. For example, the notification unit 132 notifies the customer of whether the type of food to be served is delivery, eat-in, or take-out.

[0082] In this way, the notification unit 132 notifies the in-store system of the product provision format, allowing the store to prepare the product in accordance with the provision format, thereby improving the efficiency of operations in the store.

[0083] [Processing of the first embodiment] The flow of processing by the management device 10 will be described with reference to Fig. 8. Fig. 8 is a flowchart showing the flow of processing by the management device.

[0084] 8, the management device 10 receives the order information (step S101). The management device 10 receives the order information from the management system 20, the terminal device 60, or the terminal device 411.

[0085] Next, the management device 10 refers to the mapping DB 10b (the store information table 122 and the product information table 123) to identify the store and product indicated in the order information (step S102). Furthermore, the management device 10 refers to the format conversion table 121 to convert the format of the order information (step S103).

[0086] Then, the management device 10 notifies the in-store system installed in the identified store of the order information (step S104). At this time, the management device 10 notifies the in-store system of the converted order information.

[0087] [Effects of the first embodiment] As explained above, the conversion unit 131 of the management device 10 converts the format of order information, which is information about ordering food from a restaurant, in accordance with the in-store system installed in the restaurant. The notification unit 132 notifies the in-store system of the order information converted by the conversion unit 131.

[0088] In this way, the management device 10 provides order information in a format suited to the restaurant. Therefore, the management device 10 can link various systems used in the restaurant. As a result, according to the embodiment, the management device 10 can improve the efficiency of the restaurant's management.

[0089] For example, large POS registers known as terminal-type POS systems often do not support APIs, and the protocols and data formats they use are proprietary. As a result, terminal-type POS systems have traditionally been unable to integrate with various restaurant web services and SaaS services, requiring manual data entry and separate management. In contrast, according to the present embodiment, terminal-type POS systems can be integrated with web services and SaaS services.

[0090] Furthermore, according to the embodiment, by linking various systems, it is possible to integrate various data collected in restaurants (order data, menu data, sales data, customer data, etc.), and to support the analysis or utilization of effective data that contributes to management.

[0091] The order information input to the management device 10 is not limited to that described in the embodiment. For example, the order information may be input to the management device 10 from a website (owned site) operated by each restaurant.

[0092] Furthermore, the management device 10 may collect and store the converted order information as a log. At this time, the management device 10 can analyze the stored order information. For example, the management device 10 can identify popular products for each delivery format through the analysis.

[0093] [System configuration, etc.] Furthermore, the components of each device shown in the figure are functional concepts and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown, and all or part of the devices can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc. Furthermore, all or any part of the processing functions performed by each device can be realized by a CPU (Central Processing Unit) and a program analyzed and executed by the CPU, or can be realized as hardware using wired logic. Note that the program may be executed not only by the CPU but also by other processors such as a GPU.

[0094] Furthermore, among the processes described in this embodiment, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.In addition, the information including the processing procedures, control procedures, specific names, various data and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified.

[0095] [program] In one embodiment, the management device 10 can be implemented by installing a management program (a program for causing a computer to function as the management device 10 (including the conversion program 10a)) that executes the above management processing as package software or online software on a desired computer. For example, by causing an information processing device to execute the above management program, the information processing device can be made to function as the management device 10. The information processing device referred to here includes desktop and notebook personal computers. In addition, the information processing device also includes mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone Systems), as well as slate terminals such as PDAs (Personal Digital Assistants).

[0096] 9 is a diagram showing an example of a computer that executes a management program. The computer 1000 includes, for example, a memory 1010 and a CPU 1020. The computer 1000 also includes a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.

[0097] The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM (Random Access Memory) 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to a hard disk drive 1090. The disk drive interface 1040 is connected to a disk drive 1100. A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example. The video adapter 1060 is connected to a display 1130, for example.

[0098] The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the program that defines each process of the management device 10 is implemented as a program module 1093 in which computer-executable code is written. The program module 1093 is stored, for example, in the hard disk drive 1090. For example, a program module 1093 for executing processes similar to those of the functional configuration of the management device 10 is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD (Solid State Drive).

[0099] Furthermore, setting data used in the processing of the above-described embodiment is stored as program data 1094, for example, in the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 or the program data 1094 stored in the memory 1010 or the hard disk drive 1090 into the RAM 1012 as necessary, and executes the processing of the above-described embodiment.

[0100] The program module 1093 and program data 1094 are not limited to being stored in the hard disk drive 1090, but may also be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and program data 1094 may be stored in another computer connected via a network (such as a LAN or a WAN (Wide Area Network)). The program module 1093 and program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070. [Explanation of symbols]

[0101] 1. Information Processing Systems 10 Management device 10a Conversion Program 10b Mapping DB 11 Communications Department 12 Storage section 13 Control Unit 20 Management System 20a, 30a ordering information 30 In-store systems 40, 50 output device 40a Order Management Screen 60, 211, 221, 411 terminal equipment 121 Format Conversion Table 122 Store Information Table 123 Product Information Table 131 Conversion Unit 132 Notification Department 210, 410, 420 users 220 Delivery Person 310 employees

Claims

1. a conversion unit that converts the data format of order information, which is information about ordering food at a restaurant, and the variable names and variable values ​​included in the order information, in accordance with an in-store system installed in the restaurant; a notification unit that notifies the in-store system of the order information converted by the conversion unit; A management device comprising:

2. the conversion unit converts first store information included in the order information into second store information and converts first product information included in the order information into second product information; The notification unit notifies an in-store system installed in the store identified by the second store information that the dish identified by the second product information has been ordered. The management device according to claim 1 .

3. 3. The management device according to claim 1, wherein the notification unit further notifies the customer of information indicating a serving style of the food contained in the order information.

4. The management device according to claim 3 , wherein the notification unit notifies whether the provision method is delivery, eat-in, or take-out.

5. A management method executed by a management device, comprising: a conversion step of converting the data format of order information, which is information regarding an order for food to a restaurant, and the variable names and variable values ​​included in the order information, in accordance with an in-store system installed in the restaurant; a notification step of notifying the in-store system of the order information converted by the conversion step; A management method comprising:

6. A management program for causing a computer to function as the management device according to any one of claims 1 to 4.

Images