Meal management system

Abstract

To provide a technology for reducing a user's feeling of unfairness in a situation where a business time zone is divided into a plurality of segments.SOLUTION: A meal management system comprises: a database that stores a meal number and a division number, the meal number indicating a maximum number of meals provided in a business time zone, the business time zone being divided into a plurality of segments, the division number indicating the number of segments; a first calculation unit that calculates a specific provision number which is smaller than the meal number indicating the maximum number of meals to be able to provide to a user in a specific segment of the plurality of segments using the meal number and the division number stored in the database; a reception unit that receives a proposal of provision of a meal from the user; and a processing execution unit that executes stop processing for stopping meal provision in the specific segment when an accumulated number of meals provided following the proposal received from the user in the specific segment of the plurality of segments exceeds a specific provision number.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The technology disclosed in this specification relates to a meal management system for managing meals provided to users.

Background Art

[0002] Patent Document 1 discloses a number prediction device that predicts the number of meals provided to a user using past performance.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In consideration of recent social situations, the adoption of an operation that divides the business hours of a cafeteria into a plurality of sections is increasing. By dividing the business hours into a plurality of sections, it is possible to suppress the concentration of users at a specific time. However, if more users than expected use the cafeteria in the earlier section among the plurality of sections, there is a possibility that the number of meals that can be provided in the later section among the plurality of sections will be insufficient. Users who use the cafeteria in the later section may feel a sense of unfairness.

[0005] In this specification, in a situation where the business hours are divided into a plurality of sections, a technology for reducing the sense of unfairness of users is provided.

Means for Solving the Problems

[0006] The meal management system disclosed in this specification is a database that stores the number of meals and the number of divisions. The number of meals indicates the maximum number of meals provided during the business hours, and the business hours are divided into a plurality of sections. The number of divisions indicates the number of the plurality of sections. The database, a first calculation unit that calculates a specific number of offers smaller than the number of meals, which indicates the maximum number of meals that can be provided to the user in a specific one of the plurality of sections by using the number of meals and the number of divisions stored in the database, a reception unit that receives an application for meal provision from the user, and a processing execution unit that executes a stop process for stopping the provision of the meals in the specific section when the cumulative number of meals provided according to the application received from the user in a specific one of the plurality of sections exceeds the specific number of offers.

[0007] According to the above configuration, the maximum number of meals that can be provided to the user in a specific section is limited to a specific number of offers or less. Thereby, it is possible to suppress a shortage in the number of meals that can be provided to the user in the section next to the specific section. It is possible to reduce the sense of unfairness of the user.

[0008] The specific number of offers may be a value obtained by dividing the number of meals by the number of divisions.

[0009] The meal management system further includes a second calculation unit that subtracts the number of meals actually provided during the business hours from the number of meals to calculate the remaining number of meals that can be provided during the business hours. The first calculation unit may calculate the specific number of offers by dividing the remaining number by the number obtained by subtracting the number of one or more sections that ended before the specific section from the number of divisions before the business in the specific section starts.

[0010] According to the above configuration, it is possible to calculate the specific number of offers in consideration of the number of meals consumed in one or more sections that ended before the specific section.

[0011] The meal management system further includes a third calculation unit that calculates an estimated number of people who are expected to use the meal in the specific category by using the number of people arriving at the office and the number of divisions on the date including the business hours, and a fourth calculation unit that, when the number of people entering the place where the meal is provided after the business in the specific category starts exceeds the estimated number of people, multiplies the remainder by the number obtained by dividing the number of people entering by the number of people arriving at the office to calculate a new number of servings. The processing execution unit may execute the stop processing when the cumulative number exceeds the new number of servings when the new number of servings is calculated.

[0012] According to the above configuration, considering that the number of people entering exceeds the estimated number of people, the number of meals that can be provided to users in a specific category can be updated at any time.

[0013] The number of people arriving at the office may be the number of users authenticated by a first authentication device that authenticates users arriving at the office.

[0014] The number of people entering may be the number of users authenticated by a second authentication device that authenticates users entering the place.

[0015] The meal management system further includes a second calculation unit that subtracts the number of meals actually provided during the business hours from the number of meals to calculate the remaining number of meals that can be provided during the business hours. The first calculation unit calculates the number of servings by using the number of meals and the number of divisions when the specific category is not the last category among the plurality of categories, and may determine the remaining number as the specific number of servings when the specific category is the last category.

[0016] According to the above configuration, the maximum number of meals that can be provided to users can be determined as the remaining number. As a result, it is expected that all the meals corresponding to the remaining number will be consumed.

[0017] The stop processing may be processing for stopping the acceptance of the application.

[0018] The reception unit is a terminal device installed at the place where the meal is provided, and the stop process may be a process of changing the display mode of the display unit of the terminal device from a mode capable of receiving the application to a mode incapable of receiving the application.

[0019] According to the above configuration, it is possible to notify the user that an application for providing a meal is not permitted in a specific category.

Brief Description of the Drawings

[0020]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0021] (Configuration of the meal management system 2; FIG. 1) The meal management system 2 is a system for managing meals provided to employees in the company cafeteria. The meal management system 2 includes an entry / exit management server 10, a meal management server 100, a self-checkout 200, an entry / exit authentication device 300, and a cafeteria authentication device 400. Each device 10, 100, 200, 300, 400 is connected to a network 4 and can communicate with each other via the network 4. The network 4 is, for example, a Local Area Network (LAN), a Wide Area Network (WAN), a combination of LAN and WAN, etc. Note that WAN is a concept that also includes the Internet.

[0022] The entry / exit management server 10 manages information related to the entry and exit of employees. The meal management server 100 manages information related to meals provided to employees in the cafeteria. The self-checkout 200 is a terminal device installed in the cafeteria. The entry / exit authentication device 300 is used for authenticating employees who enter the company and employees who leave the company. The cafeteria authentication device 400 is used for authenticating employees who enter the cafeteria. The company provides each employee with an employee ID card 500 for identifying each employee.

[0023] The employee ID card 500 includes an IC chip that stores an employee ID (for example, "e01") for identifying each employee. Each authentication device 300 and 400 includes a reader for reading the employee ID from the IC chip. When the authentication of the employee ID read by the reader is successful, entry into the company or the cafeteria is permitted. In a modified example, the employee ID card 500 may display an information code for recording the employee ID. In this case, each authentication device 300 and 400 may include a reader for reading information from the information code.

[0024] The entry / exit authentication device 300 is connected to, for example, an electronic lock, a gate, an automatic door, etc. installed at the entrance of the company. When the authentication of an employee using the entry / exit authentication device 300 is successful, the above-mentioned electronic lock, etc. operates, and the employee can enter the company. The cafeteria authentication device 400 is connected to an electronic lock, etc. installed at the entrance of the cafeteria.

[0025] (Configuration of the self-checkout 200; Figure 2) The self-checkout 200 is a device that accepts applications for meal provision from users in the cafeteria. The self-checkout 200 includes a display unit 212, an operation unit 214, a communication interface 216, a reader 218, and a control unit 230. The display unit 212 is a device that displays various information, for example, a liquid crystal display or an organic EL display. The operation unit 214 includes a plurality of buttons. The user can input various instructions to the self-checkout 200 by operating the operation unit 14. The operation unit 14 includes, for example, a touch screen or a mechanical switch. The communication interface 216 is an interface for executing communication via the network 4 and is connected to the network 4. The reader 218 is a reader that reads the employee ID from the employee card 500. Hereinafter, the interface will be referred to as "I / F".

[0026] The control unit 230 controls each of the units 212, 214, 216, and 218. The control unit 230 includes a CPU 232 and a memory 234. The memory 234 is, for example, a volatile memory or a non-volatile memory. The CPU 232 executes various processes according to the program 240 stored in the memory 234.

[0027] (Configuration of authentication devices 300 and 400; FIG. 3) The entry / exit authentication device 300 includes a communication I / F 316, a reader 318, and a control unit 330. The communication I / F 316 is connected to the network 4. The control unit 330 controls each of the units 316 and 318. The control unit 330 includes a CPU 332 and a memory 334. The CPU 332 executes various processes according to the program 340 stored in the memory 334. The cafeteria authentication device 400 has the same configuration as the entry / exit authentication device 300.

[0028] (Configuration of entry / exit management server 10; FIG. 4) The entry / exit management server 10 includes a communication I / F 16 and a control unit 30. The communication I / F 16 is connected to the network 4. The control unit 30 controls the communication I / F 16. The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to a program 40 stored in the memory 34.

[0029] The memory 34 further stores an ID table 42, an entrance table 44, a permission table 46, and an entry / exit log 48. The ID table 42 stores, for each of a plurality of employees, the name of the employee and the employee ID that identifies the employee in association with each other. The entrance table 44 stores, for each of a plurality of entrances of the company, the name of the entrance (for example, the name of the company entrance "Main", the name of the cafeteria entrance "Cafeteria") and the entrance number that identifies the entrance (for example, "01", "02") in association with each other.

[0030] The permission table 46 stores, for each of a plurality of employees, the employee ID of the employee and the permission entrance information indicating the entrances where the employee is permitted to enter in association with each other. The permission entrance information is a list of entrance numbers. For example, for an employee with the employee ID "e01", entry from the entrances indicated by each of the entrance numbers "01", "02", and "03" is permitted. On the other hand, for an employee with the employee ID "e01", entry from the entrances indicated by each of the entrance numbers "01" and "02" is permitted, while entry from the entrance indicated by the entrance number "03" is not permitted.

[0031] The entry / exit log 48 is a log that manages the entry date and time when an employee enters and the exit date and time when the employee exits. For example, when an employee with the employee ID "e01" enters from the company entrance, the entry / exit log 48 stores, in association with the employee ID "e01", the entrance number "01" of the company entrance and the entry date and time when the employee with the employee ID "e01" enters from the company entrance.

[0032] (Configuration of the meal management server 100; Fig. 5) The meal management server 100 includes a communication I / F 116 and a control unit 130. The communication I / F 116 is connected to the network 4. The control unit 130 includes a CPU 132 and a memory 134. The CPU 132 executes various processes according to the program 140 stored in the memory 134.

[0033] The memory 134 further stores a menu table 142, a meal table 144, a time table 146, and a performance log 148. The menu table 142 stores, for each of a plurality of types of menus provided in the cafeteria, the menu name of the menu, the menu ID for identifying the menu, the provision period indicating the period during which the menu is provided, and the business hours during which the menu is provided. The business hours are, for example, lunch, dinner, etc.

[0034] The meal table 144 stores information regarding the meals provided on each business day. The meal table 144 stores by associating the business day, the business hours, the number of meals, the remaining number, and the number of employees present. Here, the number of meals indicates the maximum number of meals to be provided during a specific business hour period (e.g., lunch, dinner) on a specific business day (e.g., 2023 / 12 / 1). The remaining number is the value obtained by subtracting the number of meals actually provided from the number of meals in a specific business hour period. The number of employees present indicates the total number of employees who came to work on a specific business day. The number of employees present is, for example, the total number of employees authenticated using the entry / exit authentication device 300. Here, the number of meals may be the total sum obtained by adding up the maximum numbers of all menus provided during a specific business hour period, or may be the individual maximum number for each menu.

[0035] The time table 146 stores information regarding business hours. The time table 146 stores a business day, business hours, classification information, start time, and end time. In this embodiment, the lunch business hours are divided into three classifications. By dividing the business hours into three classifications, it is possible to suppress the concentration of users at a specific time. For example, in the time table 146, associated with the business day "2023 / 12 / 1", the business hours "lunch" and classification information "1 / 3", start time "12:00", and end time "12:30" are stored. The classification information "1 / 3" indicates the first classification among the three classifications into which the business hours "lunch" are divided. The start time "12:00" indicates the start time of the first classification, and the end time "12:30" indicates the end time of the first classification. In the time table 146, similar to the information regarding the first classification, information regarding the second classification (for example, information stored in association with the classification information "2 / 3") and information regarding the last classification (for example, information stored in association with the classification information "3 / 3") are stored. Note that in this embodiment, the business hours "evening" are not divided into multiple classifications. In this case, the classification information "1 / 1" is stored in the time table 146 in association with the business hours "evening". Note that the notations such as the classification information "1 / 3" are merely examples. Also, the number of divisions of the business hours is not limited to three, and may be two, four or more. Also, the evening business hours may be divided.

[0036] The performance log 148 is a log for managing the menus actually provided to employees. For example, when a menu with menu ID "m01" is provided to an employee with employee ID "e01" during the business hours "lunch" on the business day "2023 / 12 / 1", the performance log 148 stores the business day "2023 / 12 / 1", the business hours "lunch", the employee ID "e01", and the menu ID "m01" in association with each other.

[0037] (Processing of the entry / exit management server 10; FIG. 6) With reference to FIG. 6, the processing executed by the CPU 32 of the entry / exit management server 10 according to the program 40 will be described. The processing in FIG. 6 is started, for example, triggered by turning on the power of the entry / exit management server 10.

[0038] In S10, the CPU 32 monitors whether the employee ID card 500 is detected in the authentication device (e.g., 300). Specifically, when the reader of the authentication device (e.g., 318) reads the employee ID from the employee ID card 500, the authentication device transmits the employee ID read from the employee ID card 500 to the access control server 10. When the CPU 32 receives the employee ID from the authentication device, it determines that the employee ID card 500 has been detected in the authentication device. If the authentication device detects the employee ID card 500 (YES in S10), the process proceeds to S12.

[0039] In S12, the CPU 32 determines whether the employee ID received from the authentication device in S10 is stored in the ID table 42. If the CPU 32 determines that the employee ID is stored in the ID table 42 (YES in S12), the process proceeds to S14.

[0040] In S14, the CPU 32 identifies the entrance number of the entrance where the authentication device that is the transmission source of the employee ID in S10 is installed. For example, the entrance number is associated with the IP address of the authentication device. The CPU 32 identifies the entrance number from the IP address of the transmission source in the communication of S10. Further, the CPU 32 determines whether the identified entrance number is stored in the permission table 46 in association with the employee ID received in S10. If the CPU 32 determines that the identified entrance number is stored in the permission table 46 in association with the employee ID (YES in S14), the process proceeds to S16.

[0041] In S16, the CPU 32 executes a permission process to permit entry or exit from the entrance corresponding to the authentication device that is the transmission source of the communication in S10. For example, the CPU 32 transmits a signal instructing the unlocking of the electronic lock to the authentication device that is the transmission source. The authentication device that is the transmission source unlocks the electronic lock according to the signal from the access control server 10.

[0042] In subsequent S20, the CPU 32 stores the log of the entry date and time or the exit date and time in the entry / exit log 48. In S22, the CPU 32 determines whether the permission process in S16 is a permission for coming to work or leaving work (i.e., a permission using the entry / exit authentication device 300). When the CPU 32 determines that the permission process in S16 is a permission for coming to work or leaving work (YES in S22), it proceeds to S24.

[0043] In S24, the CPU 32 sends a count instruction to the meal management server 100 to instruct the counting of the number of people coming to work on the current day. The meal management server 100 updates the number of people coming to work in the meal table 144 according to the count instruction from the entry / exit management server 10. Specifically, when the permission process in S16 is a permission for coming to work, the meal management server 100 increments the number of people coming to work, and when the permission process in S16 is a permission for leaving work, the meal management server 100 decrements the number of people coming to work.

[0044] Also, when the permission process in S16 is a permission for entering the cafeteria (i.e., a permission using the cafeteria authentication device 400) (NO in S22), the CPU 32 proceeds to S26. In S26, the CPU 32 sends a count instruction to the meal management server 100 to instruct the counting of the number of people entering the cafeteria in the target business segment. In this embodiment, during the daytime business hours, the target business segment indicates any one of the three divided segments, and during the nighttime business hours, the target business segment indicates the time from the start time to the end time of the nighttime business hours. The meal management server 100 increments the number of people entering according to the count instruction from the entry / exit management server 10.

[0045] Also, when the CPU 32 determines that the employee ID received from the authentication device at S10 is not stored in the ID table 42 (NO at S12), and when it determines that the identified entrance number is not stored in the permission table 46 associated with the employee ID (NO at S14), the process proceeds to S30. At S30, the CPU 32 executes NG processing. The NG processing is, for example, a process of transmitting a signal indicating that entry or exit is not permitted to the authentication device that is the source of S10. When any of S24, S26, and S30 ends, the CPU 32 ends the process of FIG. 6.

[0046] (Processing of the meal management server 100; FIGS. 7 and 8) With reference to FIGS. 7 and 8, the processing executed by the CPU 132 of the meal management server 100 according to the program 140 will be described. The processing of FIG. 7 is a process executed a predetermined time (for example, 10 minutes) before the start time of the target business category. The processing of FIG. 8 is a process repeatedly executed during the business hours of the target business category.

[0047] (Processing before business start; FIG. 7) At S50, the CPU 132 determines whether the target business category is a divided category (for example, any one of the three categories during the lunch business hours). When the CPU 32 determines that the target business category is a divided category (YES at S50), the process proceeds to S52.

[0048] At S52, the CPU 132 determines whether the target business category is the last category (for example, the last of the three categories during the lunch business hours). When the CPU 132 determines that the target business category is not the last category (NO at S52), the process proceeds to S54.

[0049] In S54, the CPU 132 calculates the assumed number of users who will use the cafeteria in the target business segment. The assumed number is, for example, the value obtained by dividing the current number of employees present by the number of divisions. For example, when the lunch business hours are divided into 3 segments, the number of divisions indicates "3". Note that the method for calculating the assumed number is not limited to the above method of equal division. For example, the assumed number may be a value obtained by multiplying the value obtained by dividing the current number of employees present by the number of divisions by a predetermined coefficient. By adjusting the predetermined coefficient for each segment, the assumed number calculated for each segment may be changed.

[0050] In S56, the CPU 132 calculates the planned number of offerings, which indicates the maximum number of meals that can be provided to users in the target business segment. The planned number of offerings is, for example, the value obtained by dividing the current remaining quantity by the remaining number of divisions. The remaining number of divisions is the number obtained by subtracting the number of one or more segments that ended before the target business segment from the number of divisions. Note that when the target business segment is the first of the 3 segments, the current remaining quantity is equal to the number of meals. Here, the planned number of offerings may be the total obtained by summing up the maximum numbers of all menus provided in the target business segment, or may be the individual maximum number for each menu. Note that the method for calculating the planned number of offerings is not limited to the above method of equal division. For example, the planned number of offerings may be a value obtained by multiplying the value obtained by dividing the current remaining quantity by the remaining number of divisions by a predetermined coefficient. By adjusting the predetermined coefficient for each segment, the planned number of offerings calculated for each segment may be changed. The predetermined coefficient may be adjusted, for example, using the information in the performance log 148. By using the information in the performance log 148, the planned number of offerings can be calculated in consideration of the popular menus and user preferences in the target business segment. Also, in other variations, the predetermined coefficient may be adjusted using the weather, temperature, etc. on the day. Machine learning may be used for adjusting the predetermined coefficient.

[0051] In S58, the CPU 132 transmits the information used in the target business category to the self-checkout 200. The said information includes the information of the menu provided in the target business category (i.e., menu name and menu ID) in the menu table 142, the assumed number of people calculated in S54, and the planned number of servings calculated in S56. When S58 ends, the CPU 132 ends the process of FIG. 7.

[0052] Also, when the CPU 132 determines that the target business category is not a divided category (NO in S50), or when it determines that the target business category is the last category (YES in S52), it proceeds to S60. In S60, the CPU 132 sets the current remaining quantity as the planned number of servings. When S60 ends, the CPU 132 proceeds to S58.

[0053] (During business operation; FIG. 8) In S100, the CPU 132 determines whether the target business category is a divided category. When the CPU 132 determines that the target business category is a divided category (YES in S100), it executes the processes after S102. When it determines that the target business category is not a divided category (NO in S100), it skips the processes from S102 to S106 and proceeds to S108.

[0054] In S102, the CPU 132 determines whether the current number of people entering the room exceeds the assumed number of people. When the CPU 132 determines that the current number of people entering the room exceeds the assumed number of people (YES in S102), it proceeds to S104.

[0055] In S104, the CPU 132 calculates a new planned number of servings to replace the planned number of servings calculated in S56 of FIG. 7. The CPU 132 calculates the value obtained by dividing the number of people entering the room by the number of people coming to work and multiplying by the remaining quantity as the new planned number of servings. According to such a configuration, considering that the number of people entering the room exceeds the assumed number of people, the number of meals that can be provided to users in the target business category can be updated at any time.

[0056] In S106, the CPU 132 transmits the newly calculated number of planned offerings to the self-checkout 200. When S106 ends, the CPU 132 proceeds to S108.

[0057] In S108, the CPU 132 monitors whether the employee ID card 500 is detected at the self-checkout 200. The self-checkout 200 displays a screen for selecting one or more menus from a plurality of menus using the information received from the meal management server 100. When one or more menus are selected on the screen and the employee ID read by the reader 218 is stored in the ID table 42, the self-checkout 200 executes a process (such as settlement) for providing one or more menus to the user. Also, when one or more menus are provided to the user, the self-checkout 200 transmits the one or more menu IDs and the employee ID to the meal management server 100. The CPU 132 determines that the employee ID card 500 has been detected at the self-checkout 200 when the one or more menu IDs and the employee ID are received from the self-checkout 200. When the CPU 132 determines that the employee ID card 500 has been detected at the self-checkout 200 (YES in S108), it proceeds to S110.

[0058] In S110, the CPU 132 increments the actual number of offerings indicating the cumulative number of meals actually provided in the target business category using the number of one or more menus selected by the user at the self-checkout 200. In S112, the CPU 132 stores the one or more menu IDs and the employee ID received from the self-checkout 200 in the performance log 148 in association with the current date and business hour range. In S114, the CPU 132 decrements the remaining quantity in the meal table 144 using the number of one or more menus selected by the user at the self-checkout 200.

[0059] In S120, the CPU 132 determines whether the actual number of offerings exceeds the planned number of offerings. When the CPU 132 determines that the actual number of offerings exceeds the planned number of offerings (YES in S120), it proceeds to S122. When it determines that the actual number of offerings has not reached the planned number of offerings (NO in S120), it skips the processing of S122 and returns to S100.

[0060] In S122, the CPU 132 instructs the self-checkout 200 not to permit menu selection. When the self-checkout 200 receives an instruction not to permit menu selection from the meal management server 100, it changes the display mode of the display unit 212 from a permission mode that can receive menu selection to a non-permission mode that cannot receive menu selection. The non-permission mode is, for example, a mode in which an icon for selecting a menu is displayed, but the icon is in a non-active state. Also, in a modification, the non-permission mode may be a mode in which an icon for selecting a menu is not displayed. Also, in another modification, the non-permission mode may be a mode in which an icon for selecting a menu is active, but even if the icon is selected, the menu cannot be settled. Also, the non-permission mode may be a mode in which selection of some menus for which the actual number of offerings exceeds the planned number of offerings among all the menus cannot be received, or a mode in which selection of all the menus cannot be received. Due to the non-permission mode, in the target business category, the offering of meals for which the actual number of offerings exceeds the planned number of offerings is stopped. The non-permission mode can inform the user that applications for meal offerings are not permitted in the target business category. When the processing of S122 is completed, the CPU 132 returns to the processing of S100.

[0061] (Effect of this embodiment) The meal management server 100 calculates the planned number of servings in a target business segment, which is one of the three divided business hours (S56 in FIG. 7). When the actual number of servings exceeds the planned number of servings, the meal management server 100 causes the display mode of the self-checkout 200 to be changed from the permitted mode to the non-permitted mode (S122 in FIG. 8). That is, in a target business segment, which is one of the three divided business hours, the maximum number of meals available to the user is limited to be less than or equal to the planned number of servings. This can prevent the number of meals available to the user from being insufficient in the next segment of the target business segment. The sense of unfairness of the user can be reduced.

[0062] Also, in this embodiment, the planned number of servings in the target business segment is a value obtained by dividing the current remaining quantity by the remaining number of divisions (S56 in FIG. 7). For example, a comparative example is assumed in which the planned number of servings is set to a value obtained by dividing the number of meals by the number of divisions. In this comparative example, the planned number of servings is the same for each of the divided segments, and the number of meals consumed in one or more segments that ended before the target business segment is not considered. In contrast, in this embodiment, by calculating the planned number of servings using the current remaining quantity, the planned number of servings can be calculated considering the number of meals consumed in one or more segments that have already ended. In a modification, the configuration of the above comparative example may be adopted.

[0063] Also, in this embodiment, when the target business segment is the last segment (NO in S52 in FIG. 7), the meal management server 100 sets the current remaining quantity as the planned number of servings (S60). Thus, it is expected that all the remaining meals will be consumed in the last segment.

[0064] (Corresponding relationship) The meal management system 2 is an example of a "meal management system". The memory 134 of the meal management server 100 is an example of a "database". The self-checkout 200 is an example of a "reception unit (and terminal device)". The entry / exit authentication device 300 and the cafeteria authentication device 400 are examples of a "first authentication device" and a "second authentication device", respectively.

[0065] S56 in FIG. 7 and S122 in FIG. 8 are examples of processes realized by the "first calculation unit" and the "processing execution unit", respectively. S114 in FIG. 8, S54 in FIG. 7, and S104 in FIG. 8 are examples of processes realized by the "second calculation unit", the "third calculation unit", and the "fourth calculation unit", respectively.

[0066] As described above, specific examples of the technology disclosed in this specification have been explained, but these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. For example, the following modification examples may be adopted.

[0067] (Modification Example 1) The technology disclosed in this specification can also be adopted for the purpose of providing meals at locations other than the company cafeteria. For example, it can also be used for providing meals in a cafeteria without entry and exit management. In this modification example, the meal management system 2 may not include the entry and exit management server 10, the entry and exit authentication device 300, and the cafeteria authentication device 400.

[0068] (Modification Example 2) The authentication devices 300 and 400 may perform authentication using the biometric information of employees instead of the employee ID card 500.

[0069] (Modification Example 3) The self-checkout 200 may execute the processes in FIGS. 7 and 8 and the like executed by the meal management server 100. In this modification example, each of the tables 142 to 146 and the performance log 148 may be stored in the self-checkout 200. In this modification example, the memory 234 of the self-checkout 200 and the control unit 230 of the self-checkout 200 are examples of the "database" and the "first calculation unit", respectively.

[0070] (Modification Example 4) The "reception unit" may be not limited to the self-checkout 200 installed in the cafeteria, but may also be a mobile terminal (for example, a smartphone or a tablet terminal) owned by the user.

[0071] (Modification Example 5) The processes of S102 to S106 in FIG. 8 may not be executed. In this modification example, the "third calculation unit" and the "fourth calculation unit" can be omitted.

[0072] (Modification Example 6) The process of S52 in FIG. 7 may not be executed. In this modification example, "determining the remaining number to the specific provision number" can be omitted.

[0073] The technical elements described in this specification or the drawings exhibit technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Also, the technologies exemplified in this specification or the drawings achieve multiple purposes simultaneously, and achieving one of those purposes itself has technical utility.

Description of Reference Numerals

[0074] 2: Meal Management System 4: Network 10: Entrance / Exit Management Server 14: Operation Unit 16: Communication I / F 30: Control Unit 32: CPU 34: Memory 40: Program 42: ID Table 44: Entrance Table 46: Permission Table 48: Entrance / Exit Log 100: Meal Management Server 116: Communication I / F 130: Control Unit 132: CPU 134: Memory 140: Program 142: Menu Table 144: Meal Table 146: Time Table 148: Performance Log 200: Self-checkout 212: Display Unit 214: Operation Unit 216: Communication I / F 218: Reader 230: Control Unit 232: CPU 234: Memory 240: Program 300: Entry / Exit Authentication Device 316: Communication I / F 318: Reader 330: Control Unit 332: CPU 334: Memory 340: Program 400: Canteen Authentication Device 500: Employee ID Card

Claims

1. A database that stores the number of meals and the number of divisions, where the number of meals indicates the maximum number of meals provided during business hours, the business hours are divided into a plurality of sections, and the number of divisions indicates the number of the plurality of sections, the database, and A first calculation unit that calculates a specific number of offers smaller than the number of meals, which indicates the maximum number of meals that can be provided to the user in a specific section among the plurality of sections, using the number of meals and the number of divisions stored in the database; A reception unit that receives an application for meal provision from a user; A processing execution unit that executes a stop process for stopping the provision of meals in the specific section when the cumulative number of meals provided according to the application received from the user in the specific section among the plurality of sections exceeds the specific number of offers; A meal management system comprising the above.

2. The meal management system according to claim 1, wherein the specific number of offers is a value obtained by dividing the number of meals by the number of divisions.

3. The meal management system further comprises A second calculation unit that subtracts the number of meals actually provided during the business hours from the number of meals to calculate the remaining number of meals that can be provided during the business hours, and The first calculation unit calculates the specific number of offers by dividing the remaining number by the number obtained by subtracting the number of one or more sections that ended before the specific section from the number of divisions before the business in the specific section starts. The meal management system according to claim 1.

4. The meal management system further comprises A third calculation unit that calculates the assumed number of people who will use the meal in the specific section using the number of people who come to work on the date including the business hours and the number of divisions, and A fourth calculation unit that calculates a new number of offers by multiplying the remaining number by the number obtained by dividing the number of people who entered the place where the meal is provided after the business in the specific section starts by the number of people who come to work when the number of people who entered exceeds the assumed number of people, and Comprises When the new number of offers is calculated, the processing execution unit executes the stop process when the cumulative number exceeds the new number of offers. The meal management system according to claim 3.

5. The meal management system according to claim 4, wherein the number of people who come to work is the number of users authenticated by a first authentication device that authenticates users who come to work.

6. The meal management system according to claim 4, wherein the number of people entering is the number of users authenticated by a second authentication device that authenticates users entering the location.

7. The meal management system further includes a second calculation unit that subtracts the number of meals actually provided during the business hours from the number of meals to calculate the remaining number of meals available for provision during the business hours, The first calculation unit calculates the provision number using the number of meals and the division number when the specific category is not the last category among the plurality of categories, The meal management system according to claim 1, wherein when the specific category is the last category, the remaining number is determined as the specific provision number.

8. The stop process is a process for stopping the acceptance of the application, and is the meal management system according to any one of claims 1 to 7.

9. The reception unit is a terminal device installed at a location where the meal is provided, The stop process is a process for changing the display mode of the display unit of the terminal device from a mode capable of accepting the application to a mode incapable of accepting the application, and is the meal management system according to any one of claims 1 to 7.

Images