Restaurant proposal device and method

Abstract

To propose use of a further appropriate restaurant in an area in which there are permanent restaurants and temporary restaurants.SOLUTION: A permanent restaurant proposal device 1 for proposing use of restaurants includes a storage unit 18 for storing permanent store information 182 about permanent restaurants which are the permanent restaurants that occupy a facility, a use history information collection unit 13 for collecting use history information 186 showing use states of temporary restaurants that open in an area affected by the facility, and a use proposal unit 17 for creating use proposal information 184 for proposing use of the permanent restaurants to a user of the temporary restaurants on the basis of the use history information 186 and the permanent store information 182.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing technology for supporting the use of permanent and temporary restaurants in an area where these restaurants exist (for example, an area affected by a facility). [Background technology]

[0002] Currently, facilities such as buildings that have permanent restaurants are sometimes inviting temporary restaurants such as food trucks to open during events. By opening such temporary restaurants within the facility's premises or other areas of influence, the convenience of facility users can be improved and new users can be attracted. As a result, the options for employees in the building will increase.

[0003] When there are options for restaurants, users need to select one. For example, Patent Document 1 discloses a technology that suggests a restaurant for the second party based on the menu items ordered and the amount spent at the restaurant used for the first party, taking into consideration overlapping menu items and the amount spent. Specifically, Patent Document 1 discloses that "the communication unit 19 of the server 10 receives order information corresponding to the menu items ordered by the customer at the first restaurant. The CPU 11 of the server 10 selects a second restaurant to be visited by the customer after leaving the first restaurant based on the order information, generates code information including at least information identifying the selected second restaurant and information identifying the first restaurant, and controls the communication unit 19 to transmit the code information to the first store terminal of the first restaurant that transmitted the order information." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2020-57310 Summary of the Invention [Problem to be solved by the invention]

[0005] As mentioned above, when permanent and non-permanent restaurants exist within the affected area of ​​a facility, such as within the premises of a building, the opening of a non-permanent restaurant will have an impact. This may result in a decline in sales at the permanent restaurant. Furthermore, when a non-permanent restaurant opens, the non-permanent restaurant may become more crowded than expected due to its novelty. From the perspective of facility operation and management, rather than increasing sales at only a specific restaurant, it is more important to ensure the coexistence and prosperity of the entire facility, that is, the permanent and non-permanent restaurants.

[0006] However, Patent Document 1 does not take into consideration the coexistence and co-prosperity of the entire facility or the impact of the opening of temporary restaurants. In other words, it does not take into consideration usage such as visits to stores and purchases at stores (including receiving services such as food and drink) within the affected area. Furthermore, Patent Document 1 only proposes a solution for limited situations such as after-parties, making it difficult to provide a general-purpose solution.

[0007] Therefore, the present invention aims to propose more appropriate use of restaurants in areas where permanent and temporary restaurants exist. [Means for solving the problem]

[0008] In order to solve the above problem, the present invention creates usage suggestion information that suggests the use of the restaurant to customers of the non-permanent restaurant, depending on the usage status of the restaurant.

[0009] More specifically, in a restaurant suggestion device that suggests the use of a restaurant, the restaurant is a permanent restaurant located in a facility, and the restaurant suggestion device has a memory unit that stores permanent store information about the permanent restaurant, a usage history information collection unit that collects usage history information that indicates the usage status of temporary restaurants that have opened in the affected area of ​​the facility, and a usage suggestion unit that creates usage suggestion information that suggests the use of the permanent restaurant to customers of the temporary restaurant based on the usage history information and the permanent store information.

[0010] The present invention also includes a restaurant recommendation method executed by the restaurant recommendation device, a program for causing the restaurant recommendation device to function as a computer, and a storage medium for storing the program. [Effects of the Invention]

[0011] According to the present invention, it is possible to propose more appropriate restaurant use in areas where permanent and temporary restaurants exist. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a functional block diagram of a permanent eating and drinking establishment suggestion device 1 according to an embodiment of the present invention. [Figure 2] 1 is a flowchart showing a processing flow according to an embodiment of the present invention. [Figure 3] 1 is a system configuration diagram of a permanent restaurant recommendation system including a permanent restaurant recommendation device 1 according to first and second embodiments. [Figure 4] 1 is a hardware configuration diagram of a permanent eating and drinking establishment suggestion device 1 in first and second embodiments. [Figure 5] FIG. 10 is a diagram showing building user information 181 used in the first and second embodiments. [Figure 6] FIG. 10 is a diagram showing permanent store information 182 used in the first and second embodiments. [Figure 7] FIG. 10 is a diagram showing temporary store information 183 used in the first and second embodiments. [Figure 8] FIG. 10 is a diagram showing usage history information 186 used in the first and second embodiments. [Figure 9] 1 is a flowchart showing a processing flow in the first embodiment. [Figure 10] 10 is a flowchart showing a processing flow in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] An embodiment of the present invention will be described below. First, the subject of this embodiment will be described. In this embodiment, a building is an example of a facility, and permanent restaurants and non-permanent restaurants are set up within the building premises, which is the area of ​​influence of the building. Here, it is assumed that multiple permanent restaurants are set up as tenants within the building, and non-permanent restaurants such as food trucks and stalls are set up in the open space of the building.

[0014] Furthermore, the opening of a temporary restaurant may affect the use of permanent restaurants, including visitor numbers. For example, the temporary restaurant may be new and attract customers from the permanent restaurant. This could result in a decrease in the number of customers of the permanent restaurant and a drop in sales.

[0015] Therefore, in this embodiment, usage suggestion information is created that suggests the use of permanent restaurants to users of temporary restaurants, including potential users, and users of permanent restaurants, depending on the usage status of the temporary restaurants. Note that the building may be any type, such as an office building, residential building, or commercial building, as long as it is occupied by tenants. Commercial buildings also include station buildings, department stores, and shopping malls. Furthermore, facilities also include amusement parks such as service areas, roadside stations, amusement parks, and zoos. Note that users of temporary restaurants in this embodiment include potential users as well as users who have actually used the temporary restaurants. Typical users are employees and residents of the building.

[0016] Next, the configuration of this embodiment will be described. Fig. 1 is a functional block diagram of a permanent restaurant recommendation device 1 in this embodiment. In Fig. 1, the permanent restaurant recommendation device 1 has an input unit 11, an output unit 12, a usage history information collection unit 13, a store information collection unit 14, a user presence status collection unit 15, a usage record information creation unit 16, a usage suggestion unit 17, and a memory unit 18.

[0017] First, the input unit 11 receives usage status information indicating the usage status of users at least at temporary restaurants. The usage history information may also include the usage status of permanent restaurants. For this purpose, the input unit 11 connects to the temporary store system 6 and user terminals 7-1 and 7-2 (hereinafter simply referred to as user terminals 7). More preferably, the input unit 11 also connects to the permanent store system 5. The input unit 11 then receives usage history information from these.

[0018] Here, for the permanent store system 5 and the temporary store system 6, usage history information based on sales data at the permanent store register 52 and the temporary store register 62 is used. For the user terminal 7, its location information and payment data can be used as usage history information.

[0019] Furthermore, the input unit 11 may be connected to the building management systems 2a and 2b and receive image information as usage history information from the cameras 23a and 23b. Furthermore, a camera 23c provided independently of the building management systems 2a and 2b may be used.

[0020] Furthermore, the output unit 12 outputs the processing results of the permanent restaurant suggestion device 1. For example, the output unit 12 outputs usage suggestion information for the user and usage record information of the permanent restaurant corresponding to the usage suggestion information. Furthermore, the output unit 12 may output usage status information. Therefore, the output unit 12 can be realized by a display device or a communication device.

[0021] Furthermore, the usage history information collection unit 13 collects usage history information via the input unit 11. The usage history information indicates the usage status. More preferably, the usage history information can specify the number of users per hour or the amount of usage, such as sales, and is created using or based on image information or sales data. Furthermore, the usage history information may also use the user's location and payment data from the user terminal 7, etc. In this embodiment, the stores used are restaurants, both permanent and temporary.

[0022] The store information collection unit 14 also collects permanent store information about permanent restaurants. In particular, the store information collection unit 14 collects usage volume, which is time-series data represented by the sales and number of customers of the permanent restaurants. Note that the store information collection unit 14 may also collect temporary store information about temporary restaurants.

[0023] The user presence status collection unit 15 also collects the presence status of users, particularly building users who are an example of facility users. This presence status indicates whether the user is present or absent in the building, and includes the user's schedule and working hours in the building. The usage suggestion unit 17, which will be described later, then calculates the proposal timing, which is the timing for outputting usage suggestion information, from the presence status. Here, it is desirable that the proposal timing be a time that is suitable for using a permanent restaurant. For example, the proposal timing can be the day the user arrives at work at the building (tenant) or the lunch break on that day. For this reason, in this embodiment, the presence status, such as whether the user is at work or not, is used.

[0024] In addition, the usage history information creation unit 16 creates usage history information indicating the user's usage history of the permanent eating and drinking establishments included in the usage suggestion information. For this purpose, the usage history information creation unit 16 uses, for example, usage history information and permanent eating and drinking establishment information.

[0025] Furthermore, the usage suggestion unit 17 executes a usage suggestion process for suggesting the use of a permanent restaurant. To this end, the usage suggestion unit 17 creates usage suggestion information that suggests the use of the permanent restaurant to users of the non-permanent restaurant, based on the collected usage history information and permanent store information about the permanent restaurant. Here, users of the non-permanent restaurant include potential users, and for example, the following examples are also included as relevant users. These include users at the time the usage history information was collected (current users), past users such as those from the previous day, and users who are planning to use the restaurant, such as those in a queue or those who have made a reservation. Furthermore, these also include people who are expected to use the restaurant based on their attributes (prospective users).

[0026] The storage unit 18 also stores building user information 181, permanent store information 182, temporary store information 183, usage suggestion information 184, usage record information 185, and usage history information 186. Details of each piece of information will be explained in each embodiment described later, so an overview of each piece of information will be given here.

[0027] First, building user information 181 is information about building users, who are an example of facility users who may become store users, and indicates user characteristics such as their attributes. Note that in this embodiment, information is handled about "building" users, but the present invention is not limited to this. For example, it may be information about members of each target store, previous users, or members of a store information service. It is also desirable that building user information 181 include information about the presence status and usage history of building users. Note that the presence status and usage history information may be handled as information separate from building user information 181.

[0028] Moreover, the permanent store information 182 and the temporary store information 183 are stores that are the subject of this embodiment, and are information about the permanent restaurants in the building described above and the temporary restaurants that will open within the affected area. More preferably, the permanent store information 182 includes the usage quantity, such as the sales and number of customers, of the permanent restaurant. Furthermore, the temporary store information 183 includes the opening date of the temporary restaurant. Note that the permanent store information 182 and the temporary store information 183 may be treated as one piece of store information. Furthermore, these are collected by the store information collection unit 14.

[0029] The usage suggestion information 184 is information that suggests the use of a permanent restaurant to a user of a non-permanent restaurant. The usage record information 185 is information that indicates the usage record of a user of the permanent restaurant included in the usage suggestion information 184, that is, the proposed permanent restaurant.

[0030] Furthermore, the usage history information 186 is information that indicates the usage status of at least the non-permanent eating and drinking establishments by the users, collected by the usage history information collecting unit 13. Therefore, by using the usage suggestion information 184, it is possible to identify users of the non-permanent eating and drinking establishments. In this way, it is possible to create usage suggestion information for the identified users.

[0031] The usage status of the non-permanent eating and drinking establishments also includes usage status of planned usage such as reservations, etc. The usage history information 186 may include the usage status of the user of at least the permanent eating and drinking establishments collected by the usage history information collecting unit 13.

[0032] This concludes the description of the permanent restaurant recommendation device 1 in this embodiment, but the permanent restaurant recommendation device 1 can be realized by various computers such as a server or a PC. Note that in this embodiment and in each of the following examples, the permanent restaurant recommendation device 1 is shown, but this is an example of a restaurant recommendation device for recommending restaurants of the present invention. In other words, in this invention, the restaurants to be recommended can include restaurants other than permanent restaurants. Furthermore, the permanent restaurant recommendation method executed by the permanent restaurant recommendation device 1 shown in this embodiment and in each of the following examples is also an example of a restaurant recommendation method executed by a restaurant recommendation device for recommending restaurants.

[0033] Next, the processing flow of this embodiment will be described. Fig. 2 is a flowchart showing the processing flow of this embodiment. First, in step S1, information such as usage history information and permanent store information is collected.

[0034] For this purpose, the usage history information collection unit 13 collects usage history information via the input unit 11 and stores it in the memory unit 18 as usage history information 186. In addition, the store information collection unit 14 collects permanent store information including the usage quantity via the input unit 11 and stores it in the memory unit 18 as permanent store information 182.

[0035] In addition, the store information collection unit 14 may collect temporary store information including the usage quantity via the input unit 11 and store this in the storage unit 18 as temporary store information 183. These operations are performed as appropriate on a daily basis.

[0036] In step S2, the usage suggestion unit 17 reads target permanent store information from the permanent store information 182. Here, the target permanent store information is permanent store information 182 for a predetermined period before the opening of the temporary restaurant and for a predetermined period after the opening, and for example, information for one day before and one day after the opening is read. In addition, if a temporary restaurant has not opened, processing from step S2 onwards may be omitted.

[0037] In step S3, the usage suggestion unit 17 determines whether there has been a change in the usage volume of the permanent restaurant information that has been read. Here, the change is determined by whether the amount of change in the usage volume before and after the opening of the non-permanent restaurant is equal to or greater than a predetermined value. Here, the usage volume before the opening can be a representative value such as an average value for one year. More preferably, the determination is made by whether the usage volume has decreased by equal to or greater than a predetermined value.

[0038] The usage suggestion unit 17 may also use the usage volume of non-permanent restaurants. In this case, if there is a correlation between the usage volumes, such as an increase in the usage volume of non-permanent restaurants and a decrease in the usage volume of permanent restaurants, the usage suggestion unit 17 can determine that there is a change. Note that at least one of sales and the number of users can be used as the usage volume. Furthermore, other numerical values ​​may also be used.

[0039] As a result of the above, if it is determined in step S3 that there is a change, in step S4, the usage suggestion unit 17 creates usage suggestion information that suggests the use of a permanent restaurant to the user of the non-permanent restaurant. This usage suggestion information includes the proposed permanent restaurant, which is the proposed store. It is desirable that the usage suggestion unit 17 selects users to whom the suggestion will be made. This user selection includes (1) determining user characteristics according to the proposed permanent restaurant and searching for users using the determination results, and (2) extracting users who have used the non-permanent restaurant.

[0040] Furthermore, if it is determined in step S3 that there is no change, in step S5, the use suggestion unit 17 omits creating use suggestion information and ends this process. Note that in step S5, the use suggestion unit 17 may output a message that creating use suggestion information is not necessary via the output unit 12. This concludes the description of this embodiment, and below, specific examples will be described. [Example]

[0041] Example 1 is a specific example of presenting suggested usage information to all building users. Here, all building users refer to building users who meet certain conditions, regardless of whether they use temporary restaurants. In Example 1, user characteristics are determined according to the proposed permanent restaurants, and users are searched for using the determination results. Details are explained below.

[0042] 3 is a system configuration diagram of a permanent restaurant recommendation system including a permanent restaurant recommendation device 1 in Example 1. In the permanent restaurant recommendation system, the permanent restaurant recommendation device 1, building management systems 2a and 2b, a building management database 3, a temporary store database 4, a permanent store system 5, a temporary store system 6, and a user terminal 7 are connected to one another via a network 8.

[0043] First, the permanent restaurant recommendation device 1 is a device that executes the main processing of Example 1. The permanent restaurant recommendation device 1 includes an input unit 11 to a storage unit 18, similar to those in Fig. 1. The following will mainly explain the differences from Fig. 1.

[0044] The input unit 11 and the output unit 12 are connected to the network 8. The input unit 11 receives usage history information indicating the usage status of the permanent restaurant and the temporary restaurant from the permanent store system 5 and the temporary store system 6. The usage status includes usage quantities such as sales and the number of customers. The usage history information of the permanent restaurant preferably includes an ID that identifies the customer who used the permanent restaurant. The usage history information of the temporary restaurant may also include an ID that identifies the customer who used the temporary restaurant. The input unit 11 may also use purchase information from the permanent store register 52 or the temporary store register 62 or image information captured by the cameras 23a to 23c as usage history information.

[0045] Furthermore, output unit 12 outputs the processing results of permanent restaurant recommendation device 1 to various terminals via network 8. Therefore, input unit 11 and output unit 12 can be realized by a communication device having a communication function via network 8. However, output unit 12 may also be realized as a display device that displays the processing results.

[0046] 1, the usage history information collection unit 13 collects usage history information via the input unit 11. Furthermore, the usage history information collection unit 13 requests usage history information of the permanent restaurant of the user to whom the usage suggestion information is proposed. The usage history information collection unit 13 stores the collected usage history information in the storage unit 18 as usage history information 186.

[0047] The store information collection unit 14 also collects permanent store information about permanent eating and drinking establishments, and stores this information in the storage unit 18 as permanent store information 182. The store information collection unit 14 also collects temporary store information about temporary eating and drinking establishments, and stores this information in the storage unit 18 as temporary store information 183.

[0048] The user presence status collection unit 15 also collects the presence status of users, particularly building users who are an example of facility users, and stores this information in building user information 181 in the storage unit 18. The usage history information creation unit 16 creates usage history information indicating the user's usage history for the permanent restaurant included in the usage suggestion information. The user presence status collection unit 15 then notifies the permanent restaurant system 5, particularly the permanent restaurant terminal 51, via the output unit 12. As a result, the manager and employees of the permanent restaurant can understand the effectiveness of the usage suggestion information. The usage history information creation unit 16 also stores the created usage history information in the storage unit 18 as usage history information 185. The output unit 12 may also notify the building manager of the usage history information. This allows the building manager to understand the effectiveness of the usage suggestion information and to explain the effectiveness of the usage suggestion information to the manager and employees of the permanent restaurant.

[0049] In addition, the usage suggestion unit 17 executes a usage suggestion process for suggesting the use of a permanent restaurant. In the first embodiment, in order to execute the usage suggestion process, the usage suggestion unit 17 includes a fluctuation determination unit 171, a permanent restaurant identification unit 172, a user selection unit 173, a suggestion timing calculation unit 174, and a usage suggestion information creation unit 175.

[0050] First, the fluctuation determination unit 171 determines whether the usage quantity at the permanent eating and drinking establishment is fluctuating in step S2 of Fig. 2. Furthermore, the permanent eating and drinking establishment identification unit 172 identifies the permanent eating and drinking establishment that is proposed for use based on the determination result of the fluctuation determination unit 171. In other words, the permanent eating and drinking establishment included in the usage suggestion information is identified. Note that the number of identified permanent eating and drinking establishments needs to be one or more, and multiple permanent eating and drinking establishments can be included in the usage suggestion information.

[0051] Furthermore, the user selection unit 173 selects a user to whom the usage suggestion information is to be proposed. To this end, in the first embodiment, the user characteristics are determined according to the permanent eating and drinking establishment identified by the permanent eating and drinking establishment identification unit 172, and the building user information 181 is searched using these user characteristics to select a user. Furthermore, the proposal timing calculation unit 174 calculates the proposal timing, which is the timing for outputting the usage suggestion information, based on the seating status. Furthermore, the usage suggestion information creation unit 175 creates usage suggestion information that proposes the permanent eating and drinking establishment identified by the permanent eating and drinking establishment identification unit 172.

[0052] 1, the storage unit 18 stores building user information 181, permanent store information 182, temporary store information 183, usage suggestion information 184, usage record information 185, and usage history information 186. Details of each of these pieces of information will be explained later.

[0053] Next, the building management systems 2a and 2b are used to manage buildings and are utilized by the owners and managers of the buildings. In the first embodiment, the permanent restaurant recommendation device 1 is realized in a so-called cloud environment used to manage stores in multiple buildings, and therefore multiple building management systems are illustrated. However, this may be a single system, or the functions of the permanent restaurant recommendation device 1 may be provided in the building management system.

[0054] First, the building management system 2a can be realized by a computer system used to manage building A. The building management system 2a is composed of a building management terminal 21a, a building management server 22a, and a camera 23a. The building management terminal 21a notifies the permanent restaurant recommendation device 1 of a request to create usage suggestion information, and displays usage history information, which is the processing result of the permanent restaurant recommendation device 1. The building management system 2a may be used to manage multiple buildings. The camera 23a is an example of a device that acquires usage history information, and captures predetermined areas of permanent restaurants and temporary restaurants in building A. Although FIG. 3 shows one building management terminal 21a and one camera 23a, multiple devices may be provided. In particular, the camera 23a may be provided for each establishment, such as a permanent restaurant and a temporary restaurant.

[0055] Here, the predetermined area refers to the location where the user is located in each store, and may be, for example, an area including seats within the store.

[0056] Furthermore, building management system 2b is used to manage building B, and is shown as an example configured with building management terminal 21b and camera 23b. Building management terminal 21b is also used to manage the building, and has the same functions as building management terminal 21b. Camera 23b is also an example of a device that acquires usage history information as image information, and takes pictures of a predetermined area of ​​permanent and temporary restaurants in building B. Building management system 2b can also be used to manage multiple buildings. The camera may be installed independently of building management system 2a and building management system 2b. FIG. 3 shows camera 23c as an example of this.

[0057] Here, cameras 23a to 23c will be described. These cameras are installed so as to capture images of a predetermined area of ​​the store. For this reason, cameras 23a to 23c are installed according to the location conditions of the store. In other words, cameras 23a to 23c are installed at positions and orientations according to the location conditions of the store so that the angle of view of cameras 23a to 23c covers the predetermined area.

[0058] Furthermore, the building management database 3 is a database that stores building A resident user information 31, building A resident permanent store information 32-1, and building B resident permanent store information 32-2. The building A resident user information 31 is the same information as the building user information 181. Therefore, either one of these may be omitted. The building A resident permanent store information 32-1 and the building B resident permanent store information 32-2 are each the same information as the permanent store information 182. Note that at least a portion of this information may be stored in the permanent restaurant suggestion device 1 or the building management system 2a or 2b. Conversely, at least a portion of the usage suggestion information 184 to the usage history information 186 may be stored in the building management database 3.

[0059] The temporary store database 4 is a database that stores temporary store information 41 related to temporary eating and drinking establishments. The temporary store information 41 is the same information as the temporary store information 183. Therefore, either one of them may be omitted. The temporary store information 41 may be stored in the permanent eating and drinking establishment suggestion device 1, the building management systems 2a and 2b, or the building management database 3. Conversely, at least a portion of the usage suggestion information 184 to the usage history information 186 may be stored in the temporary store database 4.

[0060] The permanent store system 5 is composed of a permanent store terminal 51 and a permanent store register 52. The permanent store terminal 51 is a device used by those involved and managers of the permanent store, and can be realized by a computer. The permanent store terminal 51 accepts and displays the usage history created by the permanent restaurant recommendation device 1. The permanent store register 52 has a payment function for purchases (eating and drinking) at the permanent restaurant, and can be realized by a so-called POS register. Sales data created based on the payment function of the permanent store register 52 can be used as usage history information.

[0061] The temporary store system 6 is composed of a temporary store terminal 61 and a temporary store register 62. The temporary store terminal 61 is a device used by those involved and the manager of the temporary restaurant, and can be realized by a computer. The temporary store terminal 61 receives and displays policy information related to the temporary restaurant. The temporary store register 62 has a payment function for purchases at permanent restaurants, and can be realized by a so-called POS register. Sales data created based on the payment function of the temporary store register 62 can be used as usage history information.

[0062] The permanent store system 5 and the temporary store system 6 and the devices that make them up can be omitted. Furthermore, the permanent store register 52 and the temporary store register 62 may be devices independent of the permanent store system 5 and the temporary store system 6.

[0063] The user terminal 7 is an information terminal held by the user, and receives and displays the usage suggestion information created by the permanent restaurant suggestion device 1. As a result, the usage suggestion information motivates the user, increasing the likelihood that the user will dine at the suggested permanent restaurant. The user terminal 7 can be implemented using various computers, such as smartphones, tablets, and wearable devices like smartwatches. The user terminal 7 has a location detection function using GPS or the like, and notifies the permanent restaurant suggestion device 1 of location information indicating the detected location. The user terminal 7 may also have a payment function implemented using a two-dimensional code or electronic money. This payment function may also be implemented using an IC card separate from the user terminal 7. Since this location information and payment data indicate usage status, they can be used as usage history information.

[0064] Furthermore, network 8 can be realized by a wide area network such as the Internet, and connects the above-mentioned devices together. Note that the above-mentioned building management terminal 21a, building management terminal 21b, permanent store terminal 51, and temporary store terminal 61 can be realized by a PC, smartphone, tablet, or the like. This concludes the explanation of Figure 3. Next, we will explain an implementation example of permanent restaurant recommendation device 1 that performs the main processing of Example 1.

[0065] 4 is a hardware configuration diagram of the permanent restaurant recommendation device 1 in Example 1. In Example 1, the permanent restaurant recommendation device 1 can be realized by a server, which is an example of a computer, particularly a cloud. As shown in FIG. 4, the permanent restaurant recommendation device 1 has a processing device 101, a communication device 102, a memory 103, and a secondary storage device 104, which are connected to each other via a communication path.

[0066] First, the processing device 101 can be realized by a processor such as a CPU, and executes calculations in accordance with a permanent restaurant recommendation program 105 stored in a secondary storage device 104, which will be described later. The permanent restaurant recommendation program 105 will be described later. The communication device 102 corresponds to the input unit 11 and output unit 12 in FIG. 3, and is connected to the network 8 to communicate with other devices. Note that, as components equivalent to the input unit 11 and output unit 12, an input device such as a keyboard or mouse that is operated by a system user to input data, or a display device such as a display monitor, may be provided in the permanent restaurant recommendation device 1. Note that the permanent restaurant recommendation program 105 shown in Examples 1 and 2 is an example of a restaurant recommendation program that suggests the use of restaurants of the present invention.

[0067] 3. The memory 103 and the secondary storage device 104 store the permanent restaurant recommendation program 105 and information used for processing by the processing device 101. The secondary storage device 104 can be implemented as a so-called storage device. The secondary storage device 104 stores the permanent restaurant recommendation program 105, building user information 181, permanent store information 182, temporary store information 183, usage recommendation information 184, usage record information 185, and usage history information 186. These will be described later. The secondary storage device 104 may be implemented as various storage media such as an external HDD (Hard Disk Drive), SSD (Solid State Drive), or memory card, or may be implemented as a device separate from the permanent restaurant recommendation device 1, such as a database system or file server.

[0068] Here, the permanent restaurant suggestion program 105 is composed of a usage history information collection module 106, a store information collection module 107, a user presence status collection module 108, a usage record information creation module 109, a fluctuation determination module 110, a permanent restaurant identification module 111, a user selection module 112, a suggestion timing calculation module 113, and a usage suggestion information creation module 114. Note that each of these modules may be realized as an individual program or a partial combination.

[0069] The configuration shown in FIG. 3, which performs the same functions as each module, is as follows: Usage history information collection module 106: Usage history information collection unit 13 Store information collection module 107: Store information collection unit 14 User presence status collection module 108: User presence status collection unit 15 Usage history information creation module 109: Usage history information creation unit 16 Fluctuation determination module 110: Fluctuation determination unit 171 Permanent restaurant identification module 111: Permanent restaurant identification section 172 User selection module 112: User selection unit 173 Proposal timing calculation module 113: Proposal timing calculation unit 174 Usage suggestion information creation module 114: Usage suggestion information creation unit 175 Therefore, the processing device 101 executes the processing of the usage history information collection unit 13, the store information collection unit 14, the user presence status collection unit 15, the usage record information creation unit 16, and the usage suggestion unit 17 (the fluctuation determination unit 171, the permanent restaurant identification unit 172, the user selection unit 173, the suggestion timing calculation unit 174, and the usage suggestion information creation unit 175) in accordance with the permanent restaurant suggestion program 105. Note that each of these modules may be configured as an individual program. This concludes the description of the configuration of the first embodiment, and next, the information used in the first embodiment will be described.

[0070] Next, the information used in the first embodiment will be described. First, FIG. 5 is a diagram showing building user information 181 used in the first embodiment. The building user information 181 is information about building users, such as employees of a building related to the permanent restaurant or non-permanent restaurant that is the subject of analysis, and indicates user characteristics such as their attributes. The building user information 181 also includes the presence status of the user. Furthermore, the building user information 181 includes notifications of usage suggestion information and subsequent usage records of the permanent restaurant.

[0071] Here, a building user is a user who can be proposed a permanent restaurant. The building user information 181 includes the following items for each building user: ID, working tenant, working hours (lunch break, finishing time), schedule, restaurant usage history, proposal record / usage record, and attributes.

[0072] First, the ID is an item for identifying the building user. The employment tenant is an item that indicates the tenant where the building user in question works. The employment tenant may be any tenant, location, etc. related to the building user in question. Also, Furthermore, working hours is an item indicating the working hours of the building user in question, and in the example of FIG. 5, includes lunch break time and finishing time. In Example 1, since the target store is a restaurant, lunch break time and finishing time are used. That is, since Example 1 targets a restaurant, lunch break time and finishing time (or later) when there is a high possibility of use are used. For this reason, break time other than lunch break time may be used, or in the case of other types of stores, other times may be used depending on the possibility of use.

[0073] The schedule is an item that indicates the plans of the building user. In particular, it is desirable for this information to be able to determine whether the user is present in Building A. The working hours and schedule are examples of presence information that indicates the presence status of the building user.

[0074] The restaurant usage history is an item that shows the history of the building user's use of restaurants within the affected area, and records the restaurants used and the time of use. The proposal record / usage record shows the number of times the use of a permanent restaurant was proposed to the building user and the response to this. This item indicates the number of times of use. In the example of Fig. 5, the proposal record / usage record is shown by the number of times, but it may also be shown by the presence or absence of record or frequency.

[0075] The attributes indicate the attributes of the building user in question. In the example of Figure 5, address, gender, age, and preferences are used. Here, the attributes, especially preferences, are related to the target restaurant. Therefore, when targeting stores other than restaurants, it is desirable that the attributes, especially preferences, correspond to the type of business of the target store. The preferences represent the preferences of the user in question.

[0076] The working tenant, attributes, working hours, and schedule in the building user information 181 are examples of user characteristics.

[0077] 6 is a diagram showing permanent establishment information 182 used in the first embodiment. The permanent establishment information 182 is information about permanent restaurants. Therefore, the permanent establishment information 182 includes the following items: establishment name, genre, date and time, sales, number of customers, number of people that can be accommodated, offered menu 1, offered menu 2, and location conditions.

[0078] First, the store name indicates the name of the permanent store, but any item that can identify the permanent store will suffice. The genre is an item that indicates the genre of the target permanent store. The sales indicates the sales of the relevant permanent store. Note that a profit margin item may be added to the sales.

[0079] The date and time is an item indicating the period for obtaining usage quantities such as sales and number of users, and is used in Example 1 to grasp fluctuations. The number of users indicates the number of users at the relevant permanent store at the date and time. Note that for users, an item for user information (e.g., membership information) regarding each user may be provided. The number of customers that can be accommodated indicates the number of customers that can be accommodated at the relevant permanent store. Representative values ​​such as the average or median for each unit period can be used for sales and number of users. Furthermore, the number of customers that can be accommodated may be determined based on the number of seats at the relevant permanent store. In Example 1, the location of the permanent store can be obtained from the permanent store information 32-1 in Building A. Note that the number of customers that can be accommodated may be determined for each date and time.

[0080] The offered menu 1 and offered menu 2 are items that indicate menus that are examples of products and services provided at the permanent store. In addition to these, the permanent store information 32-1 in building A may also include a representative menu.

[0081] The location conditions indicate the location conditions of the permanent store in question, and in the example of FIG. 6, the location, size (area), and orientation (entrance) are used. The location conditions can be used to select users in steps S17 and S18 described below. For example, users can be selected based on their location relative to the business tenant (such as on the same floor or nearby). Next, FIG. 7 is a diagram showing temporary store information 183 used in Example 1. The temporary store information 183 is information about temporary restaurants. Therefore, the temporary store information 183 has the following items: store name, genre, date and time, sales, number of users, menu items 1 and 2, opening period, and location conditions.

[0082] First, the store name indicates the name of a temporary store that has already opened or is a potential store candidate, but any item that can identify the temporary store will suffice. Also, the items from genre to menu offering 2 are the same as the permanent store information 182 for the corresponding temporary store.

[0083] The opening period indicates the period during which the temporary store will be open in Building A. The location conditions can be used to select users, just like the permanent store information 182. However, when the temporary store information 183 is used, users can be selected based on the relationship with the location of the permanent restaurant they used (such as proximity).

[0084] 8 is a diagram showing the usage history information 186 used in the first embodiment. The usage history information 186 is information indicating the usage status of permanent and temporary restaurants. Therefore, the usage history information 186 has items such as restaurant name, user, usage status, and date and time.

[0085] First, the store name is an item that identifies the target store, such as a permanent restaurant or a temporary restaurant. The user is an item that identifies the user of the store. The usage status is an item that indicates how the user uses the store, and includes plans such as reservations. The date and time indicates the date and time of the usage status. If the usage status is "completed," that is, if the store was actually used, it indicates the date and time of the usage, and if it is "reserved," it indicates the date and time of the reservation to be used.

[0086] The usage history information 186 only needs to include the usage status of at least the non-permanent eating and drinking establishments, and the usage status of the permanent eating and drinking establishments may be omitted.

[0087] In addition, in the first embodiment, in addition to the building user information 181 to the usage history information 186 shown in FIGS. 6 to 8, usage suggestion information 184 and usage record information 185 are used. These will be briefly described below. The usage suggestion information 184 is information that suggests permanent restaurants to the user. Therefore, the usage suggestion information 184 includes one or more suggested permanent restaurants. Furthermore, the usage suggestion information 184 can include not only the name of the permanent restaurant, but also the restaurant location and menu identified based on the permanent restaurant information 182. The restaurant location can be identified from location conditions. Furthermore, the usage suggestion information can include preferential service information such as coupons and points that can be used at the suggested permanent restaurant. Furthermore, the usage suggestion information can include available hours, such as the business hours of the permanent restaurant and recommended visiting times.

[0088] Furthermore, the usage history information 185 is information indicating the usage history of the users who are the notification recipients of the permanent eating and drinking establishments included in the usage suggestion information 184. This usage history information 185 can use a proposal history indicating the number of notifications and a usage history indicating the number of users who are the notification recipients or the number of uses. Furthermore, the proposal history and usage history can include the number of notifications, the number of users, or the number of uses for each notification recipient and each specified permanent eating and drinking establishment. Furthermore, the usage history information 185 is notified to the permanent eating and drinking establishment system 5. As a result, the permanent eating and drinking establishment can confirm the effectiveness of the notification of the usage suggestion information 184 to the user terminal 7.

[0089] This concludes the explanation of the information used in the first embodiment, and next, the processing flow of the first embodiment will be explained. Fig. 9 is a flowchart showing the processing flow in the first embodiment. The following explanation will be given along this flowchart, but the processing will mainly use the configuration in Fig. 3. In addition, the following explanation will be given using an example of opening a temporary restaurant in building A.

[0090] First, in step S11, the usage history information collection unit 13 collects usage history information of the temporary restaurant from the temporary store system 6 via the input unit 11 and stores it in the memory unit 18 as usage history information 186. The usage history information collection unit 13 may also collect temporary store information 41 from the temporary store database 4.

[0091] In addition, the usage history information collection unit 13 may collect usage history information of permanent restaurants from the permanent store system 5 via the input unit 11 and store this in the usage history information 186. Furthermore, the usage history information collection unit 13 may collect information 32-1 of permanent stores located in building A and information 32-2 of permanent stores located in building B from the building management database 3.

[0092] In step S11, the usage history information collection unit 13 stores the collected usage history information of the permanent eating and drinking establishments and the non-permanent eating and drinking establishments in the building user information 181.

[0093] Furthermore, in step S12, the store information collection unit 14 collects permanent store information from the permanent store system 5 and stores it in the memory unit 18 as permanent store information 182. Specifically, the usage quantity, which is time-series data, is recorded in the date and time, sales, and number of users of the permanent store information 182. Similarly, the store information collection unit 14 can collect temporary store information from the temporary store system 6 and store it in the memory unit 18 as temporary store information 183.

[0094] The above steps S11 and S12 are executed as appropriate on a daily basis (performed at all times). Therefore, the processing order of steps S11 and S12 may vary, and they may be executed in parallel. Then, the processing from step S13 onwards is executed periodically. That is, in step S13, the fluctuation determination unit 171 of the use suggestion unit 17 determines whether it is time to create use suggestion information. As a result, if it is time to create it (Y), the process proceeds to step S14, and use suggestion processing is executed. On the other hand, if it is not time to create it (N), the process returns to step S11, and collection of each piece of information is executed. Note that it is desirable that these steps S11 and S12 are executed continuously even when executing steps S13 and onwards.

[0095] Furthermore, in step S14, the fluctuation determination unit 171 determines whether the usage quantity of the relevant permanent eating and drinking establishment has fluctuated based on the permanent establishment information 182. To this end, the fluctuation determination unit 171 reads permanent establishment information for a predetermined period before and a predetermined period after the target non-permanent eating and drinking establishment opened from the permanent establishment information 182. As the predetermined period, for example, the period corresponding to the creation cycle of usage suggestion information, such as the day before and the day before that, can be used.

[0096] Furthermore, the fluctuation determination unit 171 uses the read permanent establishment information to compare the usage volume before the establishment opened with the usage volume after the establishment opened for each permanent eating and drinking establishment in building A. As a result, if the difference is equal to or greater than a predetermined value, it is determined that there has been a fluctuation (Y), and the process proceeds to step S16. On the other hand, if the difference is less than the predetermined value, it is determined that there has not been a fluctuation (N), and the process proceeds to step S15. As a result, the fluctuation determination unit 171 determines the need to create usage suggestion information.

[0097] The fluctuation determination unit 171 may use a predicted value other than the usage quantity, which is an actual value. For example, the fluctuation determination unit 171 detects a time-series trend in the usage quantity in the permanent store information 182. Then, if the fluctuation determination unit 171 predicts that a future fluctuation will occur, it determines that a fluctuation has occurred (Y). Conversely, the fluctuation determination unit 171 may determine a fluctuation in a non-permanent restaurant. The fluctuation in a non-permanent restaurant is determined to have occurred (Y) if the usage quantity exceeds the prediction, as compared with a previously predicted usage quantity. In this case, the predicted value of the usage quantity of the non-permanent restaurant may also be used. Furthermore, the fluctuation determination unit 171 may determine whether at least one of the sales and the number of users has fallen below a predetermined threshold. In this case, if the usage quantity falls below the predetermined threshold (Y), the process proceeds to step S16, and if the usage quantity does not fall below the predetermined threshold (N), the process proceeds to step S15.

[0098] Furthermore, in step S15, the fluctuation determination unit 171 outputs via the output unit 12 that it is not necessary to create usage suggestion information. This is notified to, for example, the building management system 2a, and the system user of the building management terminal 21a can confirm that usage suggestion information will not be created. At this time, the fluctuation determination unit 171 may output via the output unit 12 the results of a comparison between the usage volume before the store opening and the usage volume after the store opening. In this case, the system user can understand that the impact of the temporary restaurant on the permanent restaurant is small.

[0099] Furthermore, in step S16, the permanent restaurant identification unit 172 identifies a permanent restaurant to be proposed in the usage suggestion information using the result of step S14. That is, the permanent restaurant determined to have changed in step S14 is identified as the permanent restaurant to be proposed. Therefore, in step S16, one or more permanent restaurants are identified. Furthermore, in step S16, the permanent restaurant identification unit 172 may identify a permanent restaurant using the location conditions of the permanent restaurant. For example, the permanent restaurant identification unit 172 may identify, from among the changed permanent restaurants, permanent restaurants within a predetermined range (e.g., on the same floor) from the location of the temporary transplant store.

[0100] Furthermore, the permanent restaurant identification unit 172 may identify a permanent restaurant based on the number of notifications (output count) of the usage suggestion information in step S21, which will be described later. For this purpose, the usage history information creation unit 16 counts the number of notifications of usage suggestion information it itself makes. This count includes the number of notifications for each user to whom the notification was made and for each identified permanent restaurant. The permanent restaurant identification unit 172 then stores this number of notifications in the usage suggestion information 184. In this way, when identifying a permanent restaurant based on the number of notifications, priority may be given to permanent restaurants with fewer notifications, or permanent restaurants with fewer notifications per user to whom the notification was made. Conversely, priority may be given to permanent restaurants with more notifications, or permanent restaurants with more notifications per user to whom the notification was made.

[0101] Furthermore, the usage history information creation unit 16 counts the total number of notifications for each permanent restaurant in building A and stores the count in the usage suggestion information. The permanent restaurant identification unit 172 may then identify the permanent restaurant using the total number of notifications and the ratio of the number of notifications to each permanent restaurant. In this case, priority may be given to permanent restaurants with a lower ratio, or conversely, priority may be given to permanent restaurants with a higher ratio.

[0102] Furthermore, in steps S17 and S18, the user selection unit 173 selects a user to whom the usage suggestion information will be notified. To this end, first, in step S17, the user selection unit 173 determines user characteristics according to the permanent eating and drinking establishment identified in step S16. Then, in step S18, the user selection unit 173 searches the building user information 181 using the determined user characteristics and selects a user.

[0103] For example, the user selection unit 173 determines attributes such as preferences and age according to the menu offered by the identified permanent restaurant. In addition, a tenant according to the location conditions of the identified permanent restaurant may be determined as the user characteristics of the user. This determination can be realized using predetermined determination rules, natural language processing, or the like. Then, the user selection unit 173 searches the building user information 181 using the determined user characteristics. As a result, the user selection unit 173 selects a user to be notified according to the permanent restaurant.

[0104] Furthermore, in step S19, the proposal timing calculation unit 174 calculates the proposal timing, which is the timing to output the usage proposal information, based on the seating status of the selected user. This seating status can be identified using the building user information 181. Here, the proposal timing calculation unit 174 may also calculate the proposal timing using the proposal timing history and the usage record information 185. The proposal timing calculation unit 174 includes the proposal timing of the usage proposal information in the usage record information 185, and calculates the correlation between the usage status of the notification destination user, such as the number of uses, and the proposal timing. Then, based on the correlation, the proposal timing calculation unit 174 calculates the proposal timing at which the user is more likely to use the permanent restaurant.

[0105] In step S20, the usage suggestion information creation unit 175 creates usage suggestion information that proposes the permanent restaurant identified by the permanent restaurant identification unit 172. As described above, the usage suggestion information can include the name of the identified permanent restaurant, as well as the restaurant's location, menu, preferential service information, and available hours. Here, when the usage suggestion information creation unit 175 includes a menu in the usage suggestion information, it is desirable to recommend a menu according to the available hours. For example, if the suggested timing is lunchtime, the available hours are set to the dinner time, and the recommended menu is a dinner menu. Furthermore, the menu eaten may be stored in the usage history information 186, and the usage suggestion information creation unit 175 may recommend a menu other than the menu at the non-permanent restaurant. Furthermore, the usage suggestion information creation unit 175 may set the available hours as outside the business hours of the non-permanent restaurant (especially after closing). In this case, the business hours are stored in the non-permanent restaurant information 183.

[0106] Furthermore, the use suggestion information creating unit 175 stores the created use suggestion information in the storage unit 18 as use suggestion information 184. The above steps S14 to S15 are preferably performed at a fixed time such as 7:00 every day, but may be performed periodically such as once a day.

[0107] Then, in step S21, when the usage suggestion information creation unit 175 detects the suggestion timing, it notifies the created usage suggestion information to the user terminal 7 of the user selected in step S18 via the output unit 12. The user terminal 7 of the selected user can be identified by storing the email address of the user terminal 7 held by the user in the building user information 181. In addition, a permanent restaurant suggestion app may be installed in the user terminal 7, and the usage suggestion information may be notified to the app.

[0108] In addition, in the first embodiment, the processes from step S22 onward are executed to confirm the effectiveness of the usage suggestion information. However, these processes may be omitted. First, in step S22, the usage history information creation unit 16 notifies the permanent establishment system 5 of the permanent restaurant proposed in the usage suggestion information of a request for usage history information via the output unit 12. Here, the request for usage history information includes the user to whom the usage suggestion information is proposed. Furthermore, the usage history information creation unit 16 may execute step S22 on the condition that the timing of creation of the usage history information is detected. The creation timing is a timing estimated to be after the opening hours of the permanent restaurant corresponding to the usage suggestion information. Therefore, the creation timing can be the opening hours of the usage suggestion information or after the closing hours of the permanent restaurant.

[0109] Furthermore, in step S23, the usage history information creation unit 16 receives the usage history in response to the request via the input unit 11, and uses this to create usage history information indicating whether the relevant user has used the permanent restaurant. The usage history information creation unit 16 then reflects this result in the proposal history / usage history of the building user information 181. It is desirable that the usage history information include the proposal timing. Furthermore, the usage history information creation unit 16 stores the proposal timing and the visit status (presence or absence) at that time in association with each other in the building user information 181.

[0110] Then, in step S23, the usage history information creation unit 16 notifies the corresponding permanent establishment system 5 of the usage history information via the output unit 12. At this time, the usage history information creation unit 16 may notify the accumulated proposal history / usage history as usage history information, or may notify usage history information limited to the notification of the usage suggestion information in step S21. As a result, the manager and employees of the permanent establishment can grasp the effect of the usage suggestion information.

[0111] The process from step S22 onwards is created after the opening hours of the permanent restaurant, but the creation timing is not limited to this. The creation may be performed periodically, such as at a fixed time. This concludes the explanation of the first embodiment. In the first embodiment, it is possible to encourage the use of the permanent restaurant affected by the opening of the temporary restaurant. [Example]

[0112] In the second embodiment, the selection of users to whom the usage suggestion information is to be notified is performed using a non-permanent restaurant. However, the configuration and information used in the second embodiment are the same as those in the first embodiment shown in Figures 3 to 8. Therefore, the common explanations will be omitted and the differences will be mainly explained.

[0113] The second embodiment differs from the first embodiment in the usage suggestion unit 17. However, the fluctuation determination unit 171, the permanent restaurant identification unit 172, the proposal timing calculation unit 174, and the usage suggestion information creation unit 175 of the usage suggestion unit 17 execute the same processes as those in the first embodiment. However, the user selection unit 173 identifies the user to be notified based on the usage history information of the non-permanent restaurants. The following describes the processing flow of the second embodiment. Fig. 10 is a flowchart showing the processing flow in the second embodiment.

[0114] Steps S11 to S15 are the same processes as in the first embodiment, and therefore their explanation will be omitted. First, in step S25, the user selection unit 173 reads usage history information indicating usage of the non-permanent eating and drinking establishment within a predetermined period from the usage history information 186. This predetermined period indicates a predetermined period since the non-permanent eating and drinking establishment opened, as in the first embodiment. Note that in step S25, the user selection unit 173 may use the eating and drinking establishment usage history in the building user information 181.

[0115] Furthermore, in step S26, the user selection unit 173 extracts a user corresponding to the read usage history information from the usage history information 186. Furthermore, in step S26, the user selection unit 173 may identify a user (ID) corresponding to the restaurant usage history. In this manner, the notification destination user is selected in steps S25 and S26. Note that in the second embodiment as in the first embodiment, the user terminal 7 to which the usage suggestion information is notified from the identified user is identified.

[0116] In steps S25 and S26, a user who previously used a permanent restaurant and switched to using the permanent restaurant following the restaurant's opening may be selected. Here, "past" refers to a predetermined period before the restaurant opened, and more preferably, a predetermined period immediately before the restaurant opened. To this end, in step S25, the user selection unit 173 reads, from the usage history information 186, usage history information indicating use of the restaurant within a predetermined period before and after the restaurant opened. In this case, the user selection unit 173 reads first usage history information indicating use of the permanent restaurant within a predetermined period before the restaurant opened. Furthermore, the user selection unit 173 reads second usage history information indicating use of the restaurant within a predetermined period after the restaurant opened.

[0117] Then, in step S226, the user selection unit 173 compares the first usage history information with the second usage history information and extracts users to be notified from the comparison result. To this end, the user selection unit 173 compares the first usage history information with the second usage history information and extracts users who have changed from permanent eating and drinking establishments to non-permanent eating and drinking establishments.

[0118] In this case, in step S16, a permanent restaurant may be identified as follows: The permanent restaurant identification unit 172 may identify a permanent restaurant included in the first usage history information, or may identify a permanent restaurant included in the first usage history information that has changed in step S14. As a result, it is possible to encourage users who have switched to a non-permanent restaurant to use a permanent restaurant. This concludes the description of the user selection process in steps S25 and S26.

[0119] Then, the processes of steps S16 to S23 are executed in the same manner as in embodiment 1. Note that the order of the processes of steps S25, S26 and S16 is not limited, and they may be executed in parallel.

[0120] This concludes the explanation of Example 2. In Example 2, users of non-permanent restaurants can be extracted and encouraged to use permanent restaurants. Furthermore, the present invention is not limited to each Example. For example, Examples 1 and 2 may be combined. In this case, users may be selected by combining the user characteristics of Example 1 with the usage history of non-permanent restaurants. In other words, the user selection unit 173 selects users who match the user characteristics determined in Example 1 and have used non-permanent restaurants. Furthermore, the restaurants proposed in the present invention may be non-permanent restaurants, or may be proposed when a new permanent restaurant opens. Furthermore, the target stores are not limited to restaurants. [Explanation of symbols]

[0121] 1... Permanent restaurant suggestion device, 11... Input unit, 12... Output unit, 13... Usage history information collection unit, 14... Store information collection unit, 15... User presence status collection unit, 16... Usage record information creation unit, 17... Usage suggestion unit, 171... Fluctuation determination unit, 172... Permanent restaurant identification unit, 173... User selection unit, 174... Proposal timing calculation unit, 175... Usage suggestion information creation unit, 18... Memory unit, 181... Building user information, 182... Permanent store information, 183... Non- Permanent store information, 184...usage proposal information, 185...usage record information, 186...usage history information, 2a...building management system, 21a...building management terminal, 22a...building management server, 23a...camera, 2b...building management system, 21b...building management terminal, 23b...camera, 23c...camera, 3...building management database, 4...temporary store database, 5...permanent store system, 6...temporary store system, 7...user terminal, 8...network

Claims

1. In a restaurant suggestion device that suggests the use of restaurants, The restaurant is a permanent restaurant located in the facility, A storage unit that stores permanent establishment information regarding the permanent eating and drinking establishment; A usage history information collection unit that collects usage history information indicating the usage status of temporary restaurants opened in the affected area of ​​the facility; A restaurant suggestion device having a usage suggestion unit that creates usage suggestion information that suggests use of the permanent restaurant to users of the non-permanent restaurant based on the usage history information and the permanent restaurant information.

2. The restaurant recommendation device according to claim 1, The permanent establishment information includes at least one of sales and the number of customers of the permanent establishment, the use suggestion unit identifies the permanent eating and drinking establishment based on the permanent establishment information, and creates the use suggestion information including permanent establishment information related to the identified permanent eating and drinking establishment; A restaurant suggestion device having an output unit that outputs the utilization suggestion information.

3. The restaurant recommendation device according to claim 2, The use suggestion unit is a restaurant suggestion device that creates the use suggestion information using the amount of change in at least one of the sales and the number of customers in the permanent store information before and after the opening of the temporary restaurant.

4. The restaurant recommendation device according to claim 2, The user is a facility user who uses the facility, The output unit is a restaurant suggestion device that outputs the usage suggestion information to a user terminal used by the facility user.

5. The restaurant recommendation device according to claim 4, the storage unit stores facility user information relating to the facility user; the use suggestion unit calculates a suggestion timing, which is an output timing for outputting the permanent eating and drinking establishment and the use suggestion information, based on the facility user information, and creates the use suggestion information including the permanent eating and drinking establishment; The output unit outputs the use suggestion information at the suggestion timing.

6. The restaurant recommendation device according to claim 5, The facility user information includes the user's schedule, The restaurant suggestion device, wherein the usage suggestion unit calculates the suggestion timing based on the schedule.

7. The restaurant recommendation device according to claim 4, There are multiple facility users, the storage unit stores facility user information relating to the facility user; the usage suggestion unit selects a user to whom the usage suggestion information is to be proposed based on the facility user information; The output unit is a restaurant suggestion device that outputs the usage suggestion information to a user terminal of the selected user.

8. The restaurant recommendation device according to claim 4, moreover, a usage history information creation unit that creates usage history information indicating the user's usage history for the permanent eating and drinking establishments included in the usage suggestion information from the usage history information collected by the usage history information collection unit; The output unit is a restaurant suggestion device that outputs the usage history information to a permanent restaurant system of the permanent restaurant included in the usage suggestion information.

9. The restaurant recommendation device according to claim 2, The use suggestion unit is a restaurant suggestion device that creates the use suggestion information when the sales or number of users of the permanent restaurant falls below a predetermined threshold.

10. The restaurant recommendation device according to claim 1, The use of the temporary restaurant is a permanent restaurant suggestion device including potential users.

11. The restaurant recommendation device according to claim 1, Several permanent restaurants are located in the facility. The restaurant suggestion device, wherein the usage suggestion unit creates the usage suggestion information including a permanent restaurant selected from the plurality of permanent restaurants.

12. The restaurant recommendation device according to claim 11, further comprising an output unit for outputting the use suggestion information, The usage suggestion unit is a restaurant suggestion device that identifies a permanent restaurant from the plurality of permanent restaurants depending on the number of times the usage suggestion information is notified by the output unit, and creates the usage suggestion information including the identified permanent restaurant.

13. The restaurant recommendation device according to claim 1, The use suggestion unit is a restaurant suggestion device that creates the use suggestion information including a plurality of permanent restaurants.

14. A restaurant suggestion method executed by a restaurant suggestion device that has a storage unit, a usage history information collection unit, and a usage suggestion unit and that suggests the use of restaurants, The restaurant is a permanent restaurant located in the facility, The storage unit stores permanent establishment information regarding the permanent eating and drinking establishment, The usage history information collection unit collects usage history information indicating the usage status of temporary restaurants set up in the affected area of ​​the facility, A restaurant suggestion method in which the usage suggestion unit creates usage suggestion information that suggests use of the permanent restaurant to customers of the non-permanent restaurant based on the usage history information and the permanent restaurant information.

Images