Business support device and program

Abstract

To provide a business support device and a program that can support management of a plurality of facilities.SOLUTION: A business support device comprises: display means that displays, on a display, images representing facilities in a store; and execution means that receives an operation for one of the displayed images, and executes processing for switching the state of a facility corresponding to the image according to the details of the received operation. The display means displays the images in a form with which the current state of the facilities can be identified.SELECTED DRAWING: Figure 48

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a business support device and a program. [Background technology]

[0002] Conventionally, there are stores that accept customers upon entry and then charge them according to the time they have used the store or facility upon exit. For example, in leisure facilities such as karaoke booths, darts bars, and manga cafes, or sports facilities such as gyms, golf courses, and bowling alleys, customers are accepted upon entry to the store or facility, and then the charges for facility usage fees, food and drink, etc. are charged upon exit. For example, a space service provision system has been proposed that provides users with exclusive space that they can use exclusively.

[0003] The above-mentioned facilities transition through multiple states, such as when the facility is in use by users, when the facility is vacant, when the facility is being cleaned, when the facility is out of order, and so on. However, the actual period during which the facility is available, i.e., the operating period, is affected by the cleaning or out-of-order state. Therefore, by understanding the operating status of each facility, a store can improve the efficiency and take measures to improve the operation of the facility. However, in a store with a large number of facilities, such as karaoke booths, it is not easy to understand the operating status of the facilities. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a business support device and program capable of supporting the operation of a plurality of facilities. [Means for solving the problem]

[0005] The business support device of the embodiment includes a recording means for associating each facility owned by a store with an identifiable facility identifier and recording the state of the facility and the period for which the state continued as operation history, a generating means for generating information representing the operation status of the facility based on the operation history recorded by the recording means, and an output means for outputting the information generated by the generating means. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a facility management system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a base server according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a data configuration of a room information DB according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a data configuration of the state management DB according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a data configuration of a user management DB according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of the data configuration of the reservation management DB 337 according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a data configuration of the operation record DB according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of a hardware configuration of the reception terminal according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of the sales terminal according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the functional configuration of the base server, the sales terminal, and the reception terminal according to the embodiment. [Figure 11] FIG. 11 is a state transition diagram showing an example of state transition rules for the karaoke booth according to the embodiment. [Figure 12] FIG. 12 is a sequence diagram illustrating an example of a collaboration start process performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of an operation screen displayed on the reception terminal according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of a room list screen displayed on the reception terminal according to the embodiment. [Figure 15] FIG. 15 is a diagram showing an example of how room buttons are displayed according to the embodiment. [Figure 16] FIG. 16 is a diagram showing an example of how room buttons are displayed according to the embodiment. [Figure 17] FIG. 17 is a diagram showing an example of how room buttons are displayed according to the embodiment. [Figure 18] FIG. 18 is a diagram showing an example of how room buttons are displayed according to the embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of a vacant room selection screen displayed on the reception terminal according to the embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of a user information input screen displayed on the reception terminal according to the embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of a user information input screen displayed on the reception terminal according to the embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of a usage information input screen displayed on the reception terminal according to the embodiment. [Figure 23] FIG. 23 is a sequence diagram illustrating an example of check-in processing performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of a fault setting screen displayed on the reception terminal according to the embodiment. [Figure 25] FIG. 25 is a sequence diagram illustrating an example of a process related to failure setting performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 26] FIG. 26 is a diagram illustrating an example of a currently present selection screen displayed on the reception terminal according to the embodiment. [Figure 27] FIG. 27 is a diagram illustrating an example of a product menu screen displayed on the reception terminal according to the embodiment. [Figure 28]FIG. 28 is a sequence diagram illustrating an example of a process related to a product order performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 29] FIG. 29 is a diagram illustrating an example of a room details screen displayed on the reception terminal according to the embodiment. [Figure 30] FIG. 30 is a sequence diagram illustrating an example of a change process performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 31] FIG. 31 is a diagram illustrating an example of an intermediate exit screen displayed on the reception terminal according to the embodiment. [Figure 32] FIG. 32 is a sequence diagram illustrating an example of a process related to mid-session leaving performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 33] FIG. 33 is a sequence diagram illustrating an example of processing related to cancellation of entry performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 34] FIG. 34 is a diagram illustrating an example of a number-of-persons addition screen displayed on the reception terminal according to the embodiment. [Figure 35] FIG. 35 is a sequence diagram illustrating an example of a process related to mid-session entry performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 36] FIG. 36 is a diagram illustrating an example of a service time setting screen displayed on the reception terminal according to the embodiment. [Figure 37] FIG. 37 is a sequence diagram illustrating an example of a process related to granting service time performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 38] FIG. 38 is a diagram illustrating an example of a complaint registration screen displayed on the reception terminal of the embodiment. [Figure 39] FIG. 39 is a sequence diagram illustrating an example of a process related to complaint registration performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 40] FIG. 40 is a diagram illustrating an example of a complaint reception screen displayed on the store clerk terminal according to the embodiment. [Figure 41] FIG. 41 is a diagram illustrating an example of a destination selection screen displayed on the reception terminal according to the embodiment. [Figure 42] FIG. 42 is a sequence diagram illustrating an example of processing related to room transfer in a karaoke booth, which is performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 43] FIG. 43 is a diagram illustrating an example of a checkout screen displayed on the reception terminal according to the embodiment. [Figure 44] FIG. 44 is a sequence diagram illustrating an example of a checkout process performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 45] FIG. 45 is a diagram illustrating an example of a cleaning start screen displayed on the reception terminal according to the embodiment. [Figure 46] FIG. 46 is a diagram illustrating an example of a cleaning completion screen displayed on the reception terminal according to the embodiment. [Figure 47] FIG. 47 is a sequence diagram illustrating an example of a process related to cleaning management performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 48] FIG. 48 is a diagram illustrating an example of an operation status screen displayed on the reception terminal according to the embodiment. [Figure 49] FIG. 49 is a diagram illustrating another example of the operation status screen displayed on the reception terminal according to the embodiment. [Figure 50] FIG. 50 is a diagram illustrating an example of a room-by-room report screen displayed on the reception terminal of the embodiment. [Figure 51] FIG. 51 is a diagram illustrating an example of a cleaning report screen by person displayed on the reception terminal of the embodiment. [Figure 52] FIG. 52 is a sequence diagram illustrating an example of a process related to display of an operational status performed between the infrastructure server and the reception terminal according to the embodiment. [Figure 53] FIG. 53 is a diagram illustrating an example of a room reservation screen displayed on the sales terminal of the embodiment. [Figure 54] FIG. 54 is a sequence diagram showing an example of processing related to room reservation for a karaoke booth, which is performed between the infrastructure server and the sales terminal according to the embodiment. [Figure 55] FIG. 55 is a sequence diagram illustrating an example of a notification process performed by a notification processing unit of the infrastructure server according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0007] The following describes a business support device and a program according to an embodiment with reference to the drawings. In the following embodiment, an example in which the device is applied to a karaoke booth (hereinafter simply referred to as a store) will be described, but the present invention is not limited to this embodiment.

[0008] In this embodiment, a karaoke booth store is a facility for enjoying karaoke, a store equipped with one or more so-called karaoke booths. Each karaoke booth is assigned a unique room ID. The room ID is an example of a facility identifier, and is a series of room numbers or the like assigned to individually identify each karaoke booth.

[0009] [Explanation of facility management system] 1 is a diagram showing an example of the configuration of a facility management system 100. The facility management system 100 has multiple store systems 1, a mobile server 2, a base server 3, a user terminal 4, and a sales terminal 5.

[0010] The store system 1 is a common system provided in each chain store, and includes a reception terminal 11, an order terminal 12, a kitchen terminal 13, a store clerk terminal 14, and the like.

[0011] The reception terminal 11, the order terminal 12, the kitchen terminal 13, and the staff terminal 14 are communicatively connected via a first network Na. The first network Na is, for example, a network such as a LAN (Local Area Network) provided within the store. The LAN may be a wired LAN or a wireless LAN. The first network Na is also communicatively connected to a second network Nb (described later) via a communication device such as a router (not shown).

[0012] [Reception terminal] The reception terminal 11 is installed at the reception desk of the store. The reception desk of the store is the place where customers stop by before entering the karaoke booth or when leaving the karaoke booth. The reception desk is also called the front desk.

[0013] The reception terminal 11 accepts entry into a karaoke booth, or so-called check-in. Specifically, the reception terminal 11 accepts input of check-in information required when a user uses a karaoke booth. The check-in information includes, for example, information about the user using the karaoke booth, such as the room ID of the karaoke booth to be used, a member ID, the date and time of entry, the planned time of use, the room course, and optional courses (hereinafter simply referred to as options).

[0014] The room ID is unique identification information assigned to each karaoke booth in order to individually identify the multiple karaoke booths provided by the store. The member ID is unique identification information assigned to users who have signed a membership contract with the store, known as members. Users register as members by installing store-specific application software, known as a store app, on their own user terminal 4, such as a smartphone or tablet. By registering as a member, the user becomes a member and is assigned a unique member ID. The member ID is displayed on the screen of the user terminal 4 in the form of a machine-readable code symbol, such as a barcode or two-dimensional code, by launching the store app.

[0015] The entry date and time is the date and time when the use of the karaoke box began by checking in. The planned use time indicates the planned time for using the karaoke box. The room course is a course menu related to the use of the karaoke box, such as a fee plan in which the room fee for the karaoke box is a fixed amount for a specified period of time. The options are course menus related to food and drink, such as a drink bar or one drink option. The room course may also include options.

[0016] The reception terminal 11 also accepts leaving the karaoke booth, or so-called check-out. Specifically, the reception terminal 11 accepts input of check-out information required when a user leaves the karaoke booth. The check-out information includes, for example, information that can identify the room ID of the karaoke booth used. The reception terminal 11 executes accounting for the fee associated with using the karaoke booth. The reception terminal 11 is assumed to accept various payment methods such as cash, credit card, electronic money, and code payment, but may also accept only one type of payment method.

[0017] The reception terminal 11 cooperates with the infrastructure server 3 to execute the above-mentioned check-in and check-out processes.

[0018] In this embodiment, a case where the reception terminal 11 is operated by a store employee will be described, but the present invention is not limited to this. For example, the reception terminal 11 may be a face-to-face terminal that can be operated by both the store employee and the customer, or a self-service terminal that can be operated by the customer themselves.

[0019] Alternatively, the reception terminal 11 may be configured to exclusively handle check-in processing, and a separate reception device (hereinafter also referred to as an accounting terminal) may be provided to exclusively handle check-out processing. In this case, the reception terminal 11 exclusively handles check-in processing can be referred to as a registration terminal, a POS (Point Of Sales), etc. The accounting terminal can also be referred to as a payment terminal, a POS terminal, etc.

[0020] [Ordering terminal] The order terminal 12 is a terminal device used by users when ordering products in a karaoke booth. The order terminal 12 is, for example, a terminal device such as a tablet PC installed in each karaoke booth. The user selects the product they wish to order from a list of product menus displayed on the touch panel of the order terminal 12 and inputs the quantity. The user's order data is then sent to the infrastructure server 3 together with the store ID of the store, the karaoke booth room ID, etc., and is notified to the kitchen terminal 13 of the same store via the infrastructure server 3.

[0021] Ordering terminal 12 may be a handheld terminal carried by an employee and equipped with a function for inputting product orders received from customers. Alternatively, customers can install store-specific application software on their own user terminal 4 and use the user terminal 4 as an ordering terminal by inputting the application software ID, such as a membership code, into the user terminal 4 upon entering the store.

[0022] [Kitchen terminal] Kitchen terminal 13 is a device for outputting information about products (food and drink menu items) ordered by karaoke box patrons. Kitchen terminal 13 is available in two types: one that outputs information about food and drink menu items by displaying it on a display device, and one that outputs information about food and drink menu items by printing it on recording paper using a printer. Kitchen terminal 13 is generally installed in the store's kitchen where the food and drink menu items are prepared. Kitchen staff use the information output from kitchen terminal 13 to determine the food and drink menu items ordered by karaoke box patrons, prepare them, and serve them to the patrons.

[0023] [Store clerk terminal] The clerk terminal 14 is a terminal device operated by a store employee. The clerk terminal 14 is realized by a mobile terminal such as a smartphone or tablet terminal, and is carried by the employee. The store employee can check the status of the karaoke booth and various notifications sent from the infrastructure server 3 via the clerk terminal 14.

[0024] The facility management system 100 also connects each of the above-mentioned store systems 1, the mobile server 2, and the infrastructure server 3 via a second network Nb. The second network Nb is, for example, a wide area network such as the Internet or an intranet, or a mobile communication network.

[0025] [Mobile Server] The mobile server 2 provides a two-way data communication service with the user terminal 4 and the sales terminal 5. The mobile server 2 provides the data communication service using a short-range wireless communication network such as WiFi (registered trademark) or a mobile communication network.

[0026] [Infrastructure Server] The infrastructure server 3 is an example of a business support device. The infrastructure server 3 is a server device that supports the operation of each store in which the store system 1 is installed. The infrastructure server 3 manages the status of the karaoke booths installed in the store and provides support related to the use and operation of the karaoke booths. The infrastructure server 3 may provide services in an on-premise environment or in a cloud computing environment.

[0027] [User terminal] The user terminal 4 is a terminal device carried by a user who uses a karaoke booth. The user terminal 4 is realized by a mobile terminal such as a smartphone or a tablet terminal, and is carried by the user. By operating the user terminal 4, the user can make a reservation at a desired store, order products at the store they enter, etc.

[0028] [External sales terminal] The sales terminal 5 is a terminal device operated by an employee (hereinafter also referred to as an "outside salesperson") who goes outside the store and invites pedestrians and the like to use the store. Generally, when a store has many vacant karaoke booths, the store's employees or the person in charge of the store's area will head to nearby entertainment districts and the like to conduct sales activities to invite pedestrians and the like to use the store. The sales terminal 5 is intended to be used during such sales activities.

[0029] The sales terminal 5 is realized by a mobile terminal such as a smartphone or tablet terminal, and is carried by the sales representative. By linking with the infrastructure server 3, the sales terminal 5 can display the reservation status of karaoke booths and make karaoke booth reservations for solicited users. In the following, karaoke booth reservations made by the sales representative are also referred to as "room reservations."

[0030] The configuration of the main devices included in the facility management system 100 described above will be described below.

[0031] [Main components of infrastructure server 3] Fig. 2 is a diagram illustrating an example of the hardware configuration of the infrastructure server 3. As shown in Fig. 2, the infrastructure server 3 includes a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, a communication interface 35, and the like.

[0032] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the infrastructure server 3 in accordance with an operating system or application programs. The processor 31 is, for example, a CPU (Central Processing Unit). The processor 31 is preferably a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

[0033] The main memory 32 corresponds to the main storage portion of the computer. The main memory 32 includes a nonvolatile memory area and a volatile memory area. The main memory 32 stores an operating system or application programs in the nonvolatile memory area. The main memory 32 may store data required for the processor 31 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is rewritten by the processor 31 as appropriate. The nonvolatile memory area is, for example, ROM (Read Only Memory). The volatile memory area is, for example, RAM (Random Access Memory).

[0034] The auxiliary storage device 33 corresponds to the auxiliary storage portion of a computer. For example, an EEPROM, a hard disk drive (HDD), or a solid state drive (SSD) can be the auxiliary storage device 33. The auxiliary storage device 33 stores various application programs executable by the processor 31, setting information related to the execution of the application programs, etc. The auxiliary storage device 33 also stores data used by the processor 31 in performing various processes, various databases (DBs) described below, data generated by the processes of the processor 31, etc.

[0035] The clock 34 keeps track of the date and time. The processor 31 processes the date and time kept by the clock 34 as the current date and time.

[0036] The communication interface 35 is a communication device that can be connected to the second network Nb, and performs data communication with external devices via the second network Nb.

[0037] The processor 31 is connected to each component via a system transmission line. The system transmission line includes an address bus, a data bus, a control signal line, etc. The infrastructure server 3 constitutes a computer by connecting the processor 31 with a main memory 32, an auxiliary storage device 33, a clock 34, and a communication interface 35 via the system transmission line.

[0038] In addition, the infrastructure server 3 of this embodiment stores an employee management DB 331, a member management DB 332, a product management DB 333, a basic information DB 334, a status management DB 335, a check-in management DB 336, a reservation management DB 337, and an operation record DB 338 in the auxiliary storage device 33.

[0039] [Employee Management DB] The employee management DB 331 is a database for managing employees involved in the operation of each store. The employee management DB 331 stores employee information such as password, name, store affiliation, authority, and terminal address in association with the employee ID of each employee.

[0040] The employee ID is an example of an employee identifier that can identify each employee. The password is information used for verification when authenticating an employee. In the affiliated store, a store ID or the like that can identify the store to which the employee belongs is registered. Note that the number of stores that can be registered as affiliated stores is not limited to one; multiple stores may be registered. For example, if the person in charge is in an area where multiple stores exist, the store IDs of multiple stores are registered.

[0041] The name field contains information indicating the name of the employee corresponding to the employee ID. The authority field contains information indicating the scope of actions that an employee can perform. For example, the authority field contains the scope of data that can be referenced in the store system 1 and the scope of processes that can be executed. If authority is defined for each employee attribute, such as job title or affiliation, the employee attribute may be registered in the authority field. The terminal address field contains the address of the clerk terminal 14 or the external sales terminal 5 carried by the employee corresponding to the employee ID. The address here is an identifier used for communication, and may be, for example, a host name, an IP address, or an MMS (multimedia messaging service) account. If application software for linking with the infrastructure server 3 is installed on the clerk terminal 14 or the external sales terminal 5, and the ID of the application software, such as an employee ID, is entered when starting operation, the employee ID can also be used as the address.

[0042] [Membership Management DB] The member management DB 332 is a database for managing information about users who have registered as store members, i.e., members. The member management DB 332 stores member information such as name, age, contact information, rank, and coupon information in association with each member's member ID, for example.

[0043] The member ID is an example of identification information assigned to each member. The name and age are information indicating the name and age of the member corresponding to the member ID. A user who becomes a member is issued a member card on which a member code is recorded, for example. Alternatively, the member code is displayed on the display device of the smartphone in the form of a machine-readable code symbol, such as a barcode or two-dimensional code, by dedicated application software installed on the user's smartphone, etc.

[0044] The contact information includes the telephone number of the user terminal 4 owned by the member. The rank is information indicating the relative position of the member among other members. The rank is preferably determined according to the member's contribution to the store, such as the number of times or frequency of use of the karaoke box store. The store can provide the member with services (discounts, discounts, etc.) according to the rank, for example.

[0045] Coupon information is service information that is distributed to users in advance and allows them to receive services such as discounts. By applying coupon information at the time of payment, discount services according to the content of the coupon information are applied.

[0046] [Product management DB] The product management DB 333 is a database that stores data related to products that can be provided to users of the karaoke booths. The product management DB 333 stores data related to products, such as the name, price, product image, category, and restrictions, in association with the product ID of each product.

[0047] The product ID is an example of identification information assigned to each product. Products include food, beverages, cooking supplies, tobacco, etc. Rental items such as lighting equipment, musical instruments, and audio equipment, which are charged for, also belong to the product category. For example, room courses and options may also be stored as products in the product management DB 333.

[0048] The name is information indicating the name of the product. The price is information indicating the price of the product. The product image is image data such as an image or illustration that represents the product. The classification registers classification information indicating each classification according to the product category, etc. For example, products are classified into recommended products, lunch, salad, dessert, drink, others, etc.

[0049] Restrictions specify restrictions on the provision of products. For example, products such as tobacco and alcoholic beverages are subject to restrictions that prohibit them from being provided to minors. In addition, if the product is a room course or option and includes the provision of alcoholic beverages, restrictions are also attached that prohibit them from being provided to minors.

[0050] The information stored in the product management DB 333 is not limited to the above example. For example, the amount of a discount or reduction, and the conditions for discounting or reduction (e.g., whether or not the customer is a member) may be stored in association with the product ID. Also, the product management DB 333 may be provided for each store ID. This allows the product menu to be different for each store.

[0051] [Basic information DB] The basic information DB 334 is a database that stores basic information about the karaoke booths provided in each store. Fig. 3 is a diagram showing an example of the data configuration of the basic information DB 334. As shown in Fig. 3, the basic information DB 334 stores store IDs, room IDs, and basic information in association with each other.

[0052] The store ID is identification information that can identify each store. The room ID is identification information that can identify each karaoke booth installed in the store corresponding to the store ID. The basic information includes information such as the specifications of the karaoke booth corresponding to the room ID. For example, the basic information includes the karaoke booth room name, maximum and minimum capacity, karaoke machine model, terminal address, etc.

[0053] The maximum capacity is information indicating the upper limit of the number of people that can be accommodated in the karaoke booth. The minimum capacity is information indicating the lower limit of the number of people that can be accommodated in the karaoke booth. The karaoke model is information indicating the model name and brand name of the karaoke device installed in the karaoke booth. The terminal address is the address of the ordering terminal 12 installed in the karaoke booth.

[0054] The data configuration of the basic information is not limited to the example in Fig. 3. For example, the basic information may include settings such as the usage fee per unit time and whether or not the usage time can be extended.

[0055] [Status Management DB] The status management DB 335 is a database for managing the current status of the karaoke booths installed in each store. Fig. 4 is a diagram showing an example of the data configuration of the status management DB 335. As shown in Fig. 4, the status management DB 335 stores a store ID, a room ID, a room status, a status start date and time, and additional information in association with each other.

[0056] The room status indicates the current status of the karaoke booth corresponding to the room ID. Examples of the status of a karaoke booth include "vacant," "occupied," "waiting for cleaning," "cleaning in progress," and "out of order."

[0057] "Vacant" indicates that the karaoke box is available for use. "In the room" indicates that the karaoke box is being used by a customer. "Waiting for cleaning" indicates that the karaoke box has been used but is not yet being cleaned. "Cleaning in progress" indicates that the karaoke box is being cleaned. "Out of order" indicates that the karaoke box cannot be used due to a malfunction of the karaoke equipment, etc.

[0058] The status start date and time is the date and time when the status was changed. Additional information is registered as additional information related to the room status. For example, additional information for the "out of order" status may include the reason for the outage and any comments entered by employees.

[0059] [Check-in management DB] The check-in management DB 336 is a database that stores information about karaoke booths that are in use and users who are using the karaoke booths. Fig. 5 is a diagram showing an example of the data configuration of the check-in management DB 336. As shown in Fig. 5, the check-in management DB 336 stores, in association with each other, a store ID, a room ID, a slip number, entry date and time, scheduled use time, scheduled exit date and time, exit date and time, user information, the number of users, representative information, order information, complaint information, additional information, and the like.

[0060] The slip number is a number issued when a user starts using the karaoke box (checks in). The slip number is an example of a management number that can uniquely identify a transaction related to the use of the karaoke box. The entry date and time is information indicating the date and time when the user started using the karaoke box. The planned usage time is information indicating the number of hours the user plans to use the karaoke box. The planned departure date and time is the date and time obtained by adding the planned usage time to the entry date and time. The departure date and time is information indicating the date and time when the user actually left, i.e., the date and time when the user finished using the karaoke box.

[0061] The user information contains information about each user who uses the karaoke booth corresponding to the room ID. For example, the user information contains a user identifier, options, age, entry / exit status, entry date / time, exit date / time, member ID, payment completion flag, additional user information, etc.

[0062] The user identifier is identification information that can identify each user who enters the same karaoke booth. The user identifier is an identifier such as a serial number that can identify a user. The option is information that indicates the type of option selected by the user. The age is information that indicates the date of birth or age category of the user corresponding to the user identifier.

[0063] The entry / exit status is information indicating the entry / exit status of a user. Examples of entry / exit status include "entering," "entered midway," "left midway," and "entry canceled." "Entering" indicates a state in which the user is currently in the karaoke booth, meaning that the user entered at the entry date and time described above. "Entered midway" indicates a state in which the user entered the karaoke booth midway, meaning that the user entered after the entry date and time described above. "Left midway" indicates a state in which the user left the karaoke booth midway, and is a status assigned when a leave operation is performed while a user who is "entering" is still in the karaoke booth.

[0064] "Entry Cancelled" indicates that the user has been cancelled, and is the status given when entry is cancelled due to, for example, selecting the wrong number of people. A user in the "Entry Cancelled" status is treated as never having entered the room in the first place, and is excluded from the usage fee.

[0065] The mid-entry date and time is information indicating the date and time when a user entered a karaoke booth mid-entry. Mid-entry means that an additional user enters the karaoke booth while a user is already in the karaoke booth. The mid-entry date and time is information indicating the date and time when a user leaves the karaoke booth mid-entry. Mid-entry means that a user leaves the karaoke booth while a user is already in the karaoke booth.

[0066] If the user is a member, the member ID is registered. The paid flag is flag information that indicates whether the user corresponding to the user identifier has paid or not. A user whose paid flag is set to paid is considered to have paid the usage fee. The initial state of the paid flag is set to the unpaid state.

[0067] Additional information about each user is registered in the additional user information. For example, if identification is checked to verify the user's age at check-in, information indicating the type of identification used for verification (driver's license, student ID, etc.) is registered in the additional user information. For example, if the user is a non-member, the user's contact information (phone number, etc.) is registered in the additional user information.

[0068] The number of users is information indicating the number of users registered in the user information, i.e., the number of user identifiers. The number of users is the number of user identifiers remaining after excluding user identifiers whose entry / exit status is "entry canceled" from the user identifiers registered in the user information. The number of users of a karaoke booth may also be the number of user identifiers remaining after excluding user identifiers whose entry / exit status is "entry canceled" and "left midway." Note that even if the entry / exit status is "left midway," user identifiers whose payment completion flag is "not yet paid" may be included in the number of users.

[0069] The representative information is registered as information on the representative user among the users included in the user information. For example, if the representative user is a member, the user identifier or member ID of that user is registered in the representative information. Also, for example, if the representative user is a non-member, the user identifier of that user is registered in the representative information.

[0070] The order information includes information that can identify the product ordered by the user. For example, the order information includes information that indicates the type of room course. For example, the order information includes information that can identify the product, such as food or drink, ordered by the karaoke booth user.

[0071] The complaint information includes opinions, requests, complaints, etc. received from users of the karaoke booth. For example, the complaint information includes the content of the complaint, comments from employees, and the date and time of registration.

[0072] The additional information stores additional information related to the use of the karaoke booth. For example, if the store offers a free extension of the usage time, the additional information stores a service time indicating the extended usage time.

[0073] [Reservation management DB] The reservation management DB 337 is a database for managing reservations for using karaoke booths. Fig. 6 is a diagram showing an example of the data configuration of the reservation management DB 337. As shown in Fig. 6, the reservation management DB 337 stores a store ID, a room ID, reservation information, and additional information in association with each other.

[0074] Reservation information includes, for example, reservation date and time, planned usage time, number of people making the reservation, representative information, etc. The reservation date and time is information indicating the planned date and time to use the karaoke box. The planned usage time is information indicating the planned number of hours to use the karaoke box. The number of people making the reservation is information indicating the number of people planning to use the karaoke box. The representative information is information indicating the representative user, such as the member ID or name of the user who made the reservation.

[0075] The additional information includes additional information related to the reservation of a karaoke booth. For example, the additional information includes information indicating the date and time when the reservation was made (hereinafter also referred to as the reservation acceptance date and time). In addition, if the reservation was made by an outside sales representative (hereinafter also referred to as a "room reservation"), the additional information includes information that can identify the reservation as made by an outside sales representative, such as the employee ID of the outside sales representative who made the room reservation. In addition, the additional information includes information related to the amount of the reservation exchanged between the outside sales representative and the customer, and any messages from the outside sales representative to store employees.

[0076] [Operational performance DB] The operation record DB 338 is a database for managing the operation records of karaoke booths. Fig. 7 is a diagram showing an example of the data configuration of the operation record DB 338. As shown in Fig. 7, the operation record DB 338 stores store IDs, room IDs, room states, durations of states, reasons for states, person in charge information, additional information, and the like, in association with each other.

[0077] The room status is information indicating the status of the karaoke booth corresponding to the room ID. The status duration is information indicating the period during which the status of the karaoke booth has continued. For example, the status duration may include the start date and time, end date and time of the status, and the duration of the status.

[0078] The reason for the karaoke booth's status is registered in the status reason field. For example, for a karaoke booth in a "broken" state, the name of the broken device and the reason the karaoke booth is unavailable are registered.

[0079] The person in charge information includes information that can identify the operator who instructed the change to the state indicated by the room status and the employee who was in charge of the work associated with that status. For example, if a karaoke booth is "cleaning," the name and employee ID of the employee in charge of cleaning are registered in the person in charge information.

[0080] The additional information includes additional information related to the room status. For example, for a karaoke booth in a status such as "out of order," information such as contact information for other employees is registered. Also, for example, if the status is changed from "vacant" to "in cleaning," the reason for changing the status back to "in cleaning" is registered.

[0081] The DB held by the infrastructure server 3 is not limited to the above example. For example, the infrastructure server 3 may hold a store management DB that stores the store chain name, address, and addresses of each terminal installed in the store, in association with the store ID of each store. For example, the infrastructure server 3 may hold a fee DB that specifies the usage fees for karaoke booths in the auxiliary storage device 113. This fee DB stores, for example, the usage fee per unit time of the karaoke booth corresponding to the room ID, in association with the store ID and room ID. The fee DB also stores the usage fees and discount amounts when the user is a member / non-member, the discount amount according to the member rank, and the usage fees and discount amounts when the user is a student / non-student.

[0082] [Hardware configuration of reception terminal] 8 is a diagram showing an example of the hardware configuration of the reception terminal 11. The reception terminal 11 includes a processor 111, a main memory 112, an auxiliary storage device 113, a clock 114, a communication interface 115, a display unit 116, an operation unit 117, a reading unit 118, a printing unit 119, and the like.

[0083] The processor 111 corresponds to the central part of the computer. The processor 111 controls each part to realize various functions of the reception terminal 11 in accordance with an operating system or an application program. The processor 111 is, for example, a CPU. The processor 111 is preferably a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

[0084] The main memory 112 corresponds to the main storage portion of the computer. The main memory 112 includes a nonvolatile memory area and a volatile memory area. The main memory 112 stores an operating system or application programs in the nonvolatile memory area. The main memory 112 may store data required for the processor 111 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 112 uses the volatile memory area as a work area where data is rewritten by the processor 111 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0085] The auxiliary storage device 113 corresponds to the auxiliary storage portion of a computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 113. The auxiliary storage device 113 stores various application programs executable by the processor 111, setting information related to the execution of the application programs, etc. The auxiliary storage device 113 stores data used by the processor 111 when performing various processes, data generated by the processes in the processor 111, etc.

[0086] The clock 114 keeps track of the date and time. The processor 111 processes the date and time kept by the clock 114 as the current date and time.

[0087] The communication interface 115 is a communication device that can be connected to the first network Na. The communication interface 115 performs data communication with external devices via the first network Na.

[0088] The display unit 116 is a display device such as an LCD (Liquid Crystal Display). The display unit 116 displays various types of information under the control of the processor 111. The operation unit 117 is an input device such as a keyboard or a pointing device. The operation unit 117 outputs operation details input via the input device to the processor 111. The operation unit 117 may be a touch panel provided on the display unit 116.

[0089] The reading unit 118 is a reading device that reads information from an information-holding medium. For example, the reading unit 118 is a code scanner or a digital camera that reads information from code symbols such as barcodes or two-dimensional codes. Also, for example, the reading unit 118 is a magnetic card reader that reads information from a card medium such as a magnetic card. The printing unit 119 is a printing device such as a thermal printer.

[0090] The processor 111 is connected to each unit via a system transmission line. The system transmission line includes an address bus, a data bus, a control signal line, etc. The reception terminal 11 constitutes a computer by connecting the processor 111 with the main memory 112, the auxiliary storage device 113, the clock 114, the communication interface 115, etc. via the system transmission line.

[0091] [Hardware configuration of external sales terminal] 9 is a diagram showing an example of the hardware configuration of the sales terminal 5. The sales terminal 5 includes a processor 51, a main memory 52, an auxiliary storage device 53, a clock 54, a communication interface 55, a display unit 56, an operation unit 57, and the like.

[0092] The processor 51 corresponds to the central part of the computer. The processor 51 controls each part to realize various functions of the sales terminal 5 in accordance with an operating system or application programs. The processor 51 is, for example, a CPU. The processor 51 is preferably a multi-core processor that includes multiple processor cores and can execute multiple processes in parallel.

[0093] The main memory 52 corresponds to the main storage portion of the computer. The main memory 52 includes a nonvolatile memory area and a volatile memory area. The main memory 52 stores an operating system or application programs in the nonvolatile memory area. The main memory 52 may store data required for the processor 51 to execute processes for controlling each part in either the nonvolatile or volatile memory area. The main memory 52 uses the volatile memory area as a work area where data is rewritten by the processor 51 as appropriate. The nonvolatile memory area is, for example, ROM. The volatile memory area is, for example, RAM.

[0094] The auxiliary storage device 53 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM, a HDD, or an SSD can be the auxiliary storage device 53. The auxiliary storage device 53 stores various application programs executable by the processor 51, setting information related to the execution of the application programs, etc. The auxiliary storage device 53 stores data used by the processor 51 when performing various processes, data generated by the processes in the processor 51, etc.

[0095] The clock 54 keeps track of the date and time. The processor 51 processes the date and time kept by the clock 54 as the current date and time.

[0096] The communication interface 55 is a communication device that can be connected to the second network Nb (or the first network Na). The communication interface 55 performs data communication with an external device via the second network Nb.

[0097] The display unit 56 is a display device such as an LCD (Liquid Crystal Display). The display unit 56 displays various information under the control of the processor 51. The operation unit 57 is an input device such as a keyboard or a pointing device. The operation unit 57 outputs operation details input via the input device to the processor 51. The operation unit 57 may be a touch panel provided on the display unit 56.

[0098] The processor 51 is connected to each unit via a system transmission line. The system transmission line includes an address bus, a data bus, a control signal line, etc. The sales terminal 5 constitutes a computer by connecting the processor 51 with the main memory 52, the auxiliary storage device 53, the clock 54, the communication interface 55, etc. via the system transmission line.

[0099] The sales clerk terminal 14 has the same hardware configuration as, for example, the sales terminal 5. The sales terminal 5 and the sales clerk terminal 14 may be realized by the same device.

[0100] [Function Configuration] Next, the functional configuration of the above-mentioned infrastructure server 3, sales terminal 5, and reception terminal 11 will be described with reference to Fig. 10. Fig. 10 is a diagram showing an example of the functional configuration of the infrastructure server 3, sales terminal 5, and reception terminal 11.

[0101] [Store server functional configuration] First, we will explain the functional configuration of the infrastructure server 3. As shown in Fig. 10, the infrastructure server 3 has, as its functional configuration, a status management unit 311, a reservation management unit 312, a check-in processing unit 313, an order reception unit 314, a complaint processing unit 315, a check-out processing unit 316, an information provision unit 317, a notification processing unit 318, etc.

[0102] The functional configuration of the infrastructure server 3 may be a software configuration realized by cooperation between the processor 31 of the infrastructure server 3 and various programs stored in a non-volatile memory area. Also, the functional configuration of the infrastructure server 3 may be a hardware configuration realized by a dedicated circuit or the like mounted on the infrastructure server 3.

[0103] [Status Management Section] The state management unit 311 is an example of a recording means and an execution means. The state management unit 311 manages the state of the karaoke booths. For example, the state management unit 311 manages the state of each karaoke booth based on predetermined karaoke booth state transition rules. Fig. 11 is a state transition diagram showing an example of the state transition rules for the karaoke booths.

[0104] In the state transition diagram of FIG. 11, the "vacant" state is the starting point. When a check-in process is performed on a karaoke booth that is in the "vacant" state, the state management unit 311 switches the state of that karaoke booth to "occupied." Specifically, when the state management unit 311 detects that a new data entry has been registered in the check-in management DB 336 by working in cooperation with the check-in processing unit 313 (described later), the state management unit 311 switches the room state in the state management DB 335 corresponding to the combination of the store ID and room ID included in the data entry from "vacant" to "occupied." In addition, the state management unit 311 records the operation history of the karaoke booth whose state has been switched in the operation history DB 338, in association with the store ID and room ID of the karaoke booth.

[0105] Here, the state management unit 311 executes the following process in recording (registering) the operation history. First, the state management unit 311 searches the data entries in the operation history DB 338 related to the combination of the store ID and room ID for which the room status has been switched for a data entry in which the room status is the status before the switch and the end date and time of the status is blank. The state management unit 311 registers the current date and time as the end date and time of the searched data entry. Furthermore, the state management unit 311 registers in the operation history DB 338 the combination of the store ID and room ID for which the status has been switched, the room status indicating the status after the switch, and a data entry in which the current date and time is set as the start date and time.

[0106] Furthermore, when a checkout process is performed on a karaoke booth that is in the "occupied" state, the status management unit 311 switches the state of that karaoke booth to "waiting for cleaning." Specifically, when the status management unit 311 detects that a data entry has been removed from the check-in management DB 336, in cooperation with the check-out processing unit 316 (described later), the status management unit 311 switches the room status in the status management DB 335 corresponding to the combination of the store ID and room ID included in the data entry from "occupied" to "waiting for cleaning." Furthermore, the status management unit 311 registers the operation history of the karaoke booth whose state has been switched in the operation history DB 338, in association with the store ID and room ID of the karaoke booth.

[0107] Furthermore, when the status management unit 311 receives an instruction to start cleaning for a karaoke booth that is in the "waiting for cleaning" state, it switches the state of that karaoke booth to "cleaning in progress." Specifically, when the status management unit 311 receives a cleaning start notification from the store system 1 (the reception terminal 11 or the store staff terminal 14) instructing the store to start cleaning the karaoke booth, it identifies a data entry corresponding to the store ID and room ID specified in the cleaning start notification from the status management DB 335. Next, the status management unit 311 switches the room state of the identified data entry from "waiting for cleaning" to "cleaning in progress." Furthermore, the status management unit 311 associates the store ID and room ID of the karaoke booth whose state has been switched with the operation record of that karaoke booth in the operation record DB 338.

[0108] If the cleaning start notification includes the employee ID of the employee in charge of cleaning, the status management unit 311 registers the employee ID and the name of the employee corresponding to the employee ID in the person in charge information column of the operation history DB 338.

[0109] Furthermore, when the status management unit 311 receives an instruction to complete cleaning for a karaoke booth that is in the "cleaning in progress" state, it switches the state of that karaoke booth to "vacant." Specifically, when the status management unit 311 receives a cleaning completion notice from the store system 1 (the reception terminal 11 or the staff terminal 14) instructing that cleaning of the karaoke booth be completed, it identifies a data entry corresponding to the store ID and room ID specified in the cleaning completion notice from the status management DB 335. Next, the status management unit 311 switches the room state of the identified data entry from "cleaning in progress" to "vacant." Furthermore, the status management unit 311 registers the operation history of the karaoke booth whose state has been switched in the operation history DB 338, in association with the store ID and room ID of the karaoke booth.

[0110] If the cleaning completion notification includes the employee ID of the employee in charge of cleaning, the status management unit 311 registers the employee ID and the name of the employee corresponding to the employee ID in the person in charge information column of the operation history DB 338.

[0111] Furthermore, when the status management unit 311 receives an instruction to return a karaoke booth that is currently in the "vacant" state to "in cleaning," it switches the state of that karaoke booth to "in cleaning." Specifically, when the status management unit 311 receives an instruction to return a karaoke booth to the "in cleaning" state from the store system 1 (the reception terminal 11 or the store staff terminal 14), it identifies a data entry corresponding to the store ID and room ID specified in the instruction to return a karaoke booth to the "in cleaning" state from the status management DB 335. Next, the status management unit 311 switches the room state of the identified data entry from "vacant" to "in cleaning." Furthermore, the status management unit 311 associates the store ID and room ID of the karaoke booth whose state has been switched with the operation record of that karaoke booth in the operation record DB 338.

[0112] If the instruction to return to the cleaning state includes a reason for returning to the cleaning state, the status management unit 311 registers the reason in the status reason field or additional information field of the operation record DB 338.

[0113] Furthermore, when the status management unit 311 receives a notification of a malfunction for a karaoke booth that is in the "vacant" state, it switches the state of that karaoke booth to "out of order." Specifically, when the status management unit 311 receives a malfunction notification from the store system 1 (the reception terminal 11 or the store clerk terminal 14) indicating that a malfunction has occurred in a karaoke booth, it identifies a data entry corresponding to the store ID and room ID indicated in the malfunction notification from the status management DB 335. Next, the status management unit 311 switches the room state of the identified data entry from "vacant" to "out of order." Furthermore, the status management unit 311 registers the operation history of the karaoke booth whose state has been switched in the operation history DB 338, in association with the store ID and room ID of the karaoke booth.

[0114] If the failure occurrence notification includes a reason for the failure, a comment, etc., the status management unit 311 registers the reason for the failure and the comment in the status reason column and additional information column of the operation record DB 338.

[0115] Furthermore, when the status management unit 311 receives a repair completion instruction for a karaoke booth that is in the "out of order" state, it switches the state of that karaoke booth to "vacant." Specifically, when the status management unit 311 receives a repair completion instruction from the store system 1 (the reception terminal 11 or the store clerk terminal 14) indicating that repairs to the karaoke booth have been completed, it identifies a data entry corresponding to the store ID and room ID specified in the repair completion instruction from the status management DB 335. Next, the status management unit 311 switches the room state of the identified data entry from "out of order" to "vacant." Furthermore, the status management unit 311 registers the operation history of the karaoke booth whose state has been switched in the operation history DB 338, in association with the store ID and room ID of the karaoke booth.

[0116] In this way, the state management unit 311 switches the room state in the state management DB 335 depending on the current state of the karaoke booth. In addition, when the state of the karaoke booth is switched, the state management unit 311 registers the operation history of the karaoke booth in the operation history DB 338. As a result, the current state of the karaoke booth is stored in the state management DB 335. In addition, the operation history DB 338 records the time-series state transitions of the karaoke booth as operation history.

[0117] [Reservation Management Department] 10, the reservation management unit 312 manages reservations for karaoke booths. Specifically, when the reservation management unit 312 receives a reservation instruction including a set of the store ID and room ID to be reserved and the reservation date and time from the store system 1, the user terminal 4, the external sales terminal 5, etc., the reservation management unit 312 registers the reservation information such as the reservation date and time in the reservation management DB 337 in association with the set of the specified store ID and room ID.

[0118] The reservation management unit 312 also manages reservation information registered in the reservation management DB 337. Specifically, the reservation management unit 312 deletes from the reservation management DB 337 data entries related to reservation information for which a predetermined time (e.g., 15 minutes) has elapsed since the reservation date and time.

[0119] [Check-in processing section] The check-in processing unit 313 is an example of an execution unit. The check-in processing unit 313 executes processing related to a user's check-in (hereinafter also referred to as check-in processing) in cooperation with the reception terminal 11. Specifically, when the check-in processing unit 313 receives check-in information specifying a set of a store ID and a room ID from the reception terminal 11, the check-in processing unit 313 issues a unique slip number and transmits the issued slip number to the reception terminal 11. The check-in processing unit 313 also associates the specified set of store ID and room ID with the issued slip number and various information included in the check-in information, and registers them in the check-in management DB 336.

[0120] The check-in information includes data elements based on the data configuration of the check-in management DB 336. For example, the check-in information includes the entry date and time, the scheduled time of use, user information, and representative information. When registering user information in the check-in management DB 336, the check-in processing unit 313 sets the entry / exit status of each user to "entering the room" and registers the entry date and time in the entry date and time column for each user.

[0121] The check-in processing unit 313 may determine whether or not a karaoke booth is available for use based on the maximum and minimum occupancies of each karaoke booth registered in the basic information DB 334 and the number of users checking in. For example, the check-in processing unit 313 determines that the karaoke booth is unavailable if the number of users exceeds the maximum occupancy or is less than the minimum occupancy specified in the check-in information. In this case, the check-in processing unit 313 may notify the operator of the reception terminal 11 that the karaoke booth is unavailable for use in cooperation with the information providing unit 317, which will be described later.

[0122] Furthermore, when the check-in processing unit 313 receives an instruction to read reservation information from the reception terminal 11, it reads the reservation information specified by the read instruction from the reservation management DB 337 and executes check-in processing based on the read reservation information. Specifically, the check-in processing unit 313 executes check-in processing for the karaoke booth corresponding to the store ID and room ID associated with the reservation information, based on the contents registered in the reservation information. Furthermore, in conjunction with executing check-in processing based on the reservation information, the check-in processing unit 313 deletes the data entry related to the reservation information from the reservation management DB 337.

[0123] The check-in processing unit 313 may narrow down the reservation information to be read from the reservation management DB 337 based on the date and time when the reservation information read instruction was received. For example, when the check-in processing unit 313 receives a read instruction specifying a store ID and a room ID, the check-in processing unit 313 may be configured to read from the reservation management DB 337, reservation information that meets the conditions and has a reservation date and time set within a predetermined time (for example, 15 minutes) before or after the date and time when the read instruction was received. This allows the check-in processing unit 313 to perform check-in processing using reservation information that is appropriate for the current date and time, even if there is a plurality of reservation information that meets the conditions specified in the read instruction.

[0124] Furthermore, the check-in processing unit 313 changes the registered contents of the data entry registered in the check-in management DB 336 in response to a change instruction sent from the reception terminal 11. Specifically, when the check-in processing unit 313 receives a change instruction specifying a set of a store ID and a room ID, it identifies a data entry that meets the specified conditions from the check-in management DB 336. Next, the check-in processing unit 313 executes a process to change the contents of the data entry based on the contents specified in the change instruction.

[0125] For example, when the check-in processing unit 313 receives a change instruction to change a room ID, it changes the room ID included in the corresponding data entry to the room ID specified in the change instruction. For example, when the check-in processing unit 313 receives a change instruction to change a room course, it changes the room course included in the corresponding data entry to the room course specified in the change instruction.

[0126] Furthermore, when the check-in processing unit 313 receives a change instruction to instruct a user to enter midway (hereinafter also referred to as a midway entry instruction), it adds information about the user specified in the midway entry instruction to the user information in the check-in management DB 336. Then, the check-in processing unit 313 sets the entry / exit status of the added user to "entered midway" and registers the date and time specified in the midway entry instruction as the midway entry date and time.

[0127] In addition, when the check-in processing unit 313 receives a change instruction (hereinafter also referred to as an entry cancellation instruction) to cancel a user's entry, it changes the entry / exit status of the user instructed in the entry cancellation instruction to "entry canceled" in the user information in the check-in management DB 336.

[0128] [Order Reception Department] The order receiving unit 314 receives product orders from users who are using a karaoke booth and notifies the kitchen terminal 13 or the like of the store where the karaoke booth is located of the received order details. Specifically, when the order receiving unit 314 receives an order instruction specifying the product to be ordered from a user who has entered the karaoke booth via the order terminal 12 or the like, the order receiving unit 314 notifies the kitchen terminal 13 of the store where the karaoke booth is located of the order details. In addition, the order receiving unit 314 identifies a data entry related to the karaoke booth of the user who placed the order from the check-in management DB 336, and registers the order details in the order information field included in the data entry.

[0129] The order receiving unit 314 may determine whether or not an order can be placed based on the restrictions on each product registered in the product management DB 333, the age category of the users using the karaoke booth, etc. For example, if the age category of all users using the karaoke booth is underage, the order receiving unit 314 may determine that products such as alcoholic beverages and tobacco cannot be ordered. In this case, the order receiving unit 314 may cooperate with the information providing unit 317 (described later) to provide the user with a product menu that extracts orderable products, or may notify the user that an order cannot be placed if a non-orderable product is ordered.

[0130] Furthermore, the order receiving unit 314 may switch the notification destination of the order details depending on the type of product to be ordered. For example, if the product to be ordered is a beverage or a cooked food, the order receiving unit 314 may notify the kitchen terminal 13, and if the product to be ordered is a lighting fixture, a musical instrument, or the like, the order receiving unit 314 may notify the staff terminal 14.

[0131] In addition, for items included in the room course or options ordered at check-in, the order receiving unit 314 may be configured to notify the kitchen terminal 13, etc., in cooperation with the check-in processing unit 313.

[0132] The complaint processing unit 315 registers complaints received from karaoke booth users and notifies employees. Specifically, when the complaint processing unit 315 receives a complaint registration instruction from the reception terminal 11 to register the details of the complaint, the complaint processing unit 315 identifies a data record related to the karaoke booth to which the complaint registration instruction is directed from the check-in management DB 336. The complaint processing unit 315 then registers the details of the complaint specified in the complaint registration instruction in the complaint information field of the identified data record.

[0133] Furthermore, when the complaint processing unit 315 receives a complaint registration instruction, it notifies the store clerk terminal 14 of the store that sent the instruction of the complaint, including the details of the complaint as instructed in the complaint registration instruction.

[0134] In this embodiment, the complaint registration instruction is transmitted from the reception terminal 11, but this is not limiting, and the complaint registration instruction may be transmitted from the order terminal 12 or the user terminal 4.

[0135] [Checkout processing section] The check-out processing unit 316 is an example of an execution unit. The check-out processing unit 316 executes processing related to the check-out of users (hereinafter referred to as check-out processing) in cooperation with the reception terminal 11. Specifically, when the check-in processing unit 313 receives check-out information specifying a slip number from the reception terminal 11, it executes check-out processing for users of the karaoke booth who meet the specified conditions.

[0136] During the check-out process, the check-out processing unit 316 identifies a data entry from the check-in management DB 336 that meets the conditions specified in the check-out information, and calculates the usage fee for the karaoke box based on the various information contained in the identified data entry.

[0137] For example, when the check-out processing unit 316 registers the date and time when the check-out information is received in the exit date and time field of the identified data entry, it calculates the length of time from the entry date and time to the exit date and time (hereinafter also referred to as usage time). If free time is set, the check-out processing unit 316 makes the free time free of charge, and therefore deducts the free time from the remaining time and sets it as usage time, but reserves the time specified in the room course, etc. without deducting it.

[0138] Next, the checkout processing unit 316 calculates the usage fee for the karaoke box based on the usage time calculated for each user (user identifier), the type of room course, the type of option, the price of the product registered in the order information, various discount conditions for members, etc. The checkout processing unit 316 also calculates the usage fee for each user by dividing the karaoke box usage fee by the number of users. However, user identifiers whose payment completion flag is "payment completed" and user identifiers whose entry / exit status is "entry canceled" are excluded from the calculation of the usage fee.

[0139] The method of calculating the usage fee for each user is not limited to the above, and the fee may be calculated in more detail for each user. For example, the usage fee for each user may be calculated based on options associated with each user identifier or discounts according to the user's attributes (discounts according to whether the user is a member, age group, student, etc.). Furthermore, for a user identifier whose entry / exit status is "entered midway," the usage fee may be calculated based on the usage time from the entry / exit date and time to the exit date and time.

[0140] Next, the checkout processing unit 316 transmits transaction data including the usage amount for the karaoke booth and the usage amount for each user to the reception terminal 11 that transmitted the checkout information. Note that the checkout processing unit 316 may transmit the transaction data including some or all of the slip number and the data entry identified from the check-in management DB 336.

[0141] When the checkout processing unit 316 receives a transaction completion instruction from the reception terminal 11 that transmitted the transaction data, the checkout processing unit 316 sets the transaction completion flag for each user included in the data entry in the check-in management DB 336 related to the transaction data to "transaction completed." The checkout processing unit 316 then removes the data entry for which the transaction has been completed from the check-in management DB 336 by, for example, moving it to another DB.

[0142] Furthermore, when the checkout processing unit 316 receives from the reception terminal 11 an instruction to leave the karaoke booth of a user who is leaving midway, it changes the entry / exit status of the user specified in the instruction to "left midway." Specifically, when the instruction to leave midway specifies the store ID, room ID, and user identifier of the user who is leaving midway, the checkout processing unit 316 identifies a data entry that meets the specified conditions from the check-in management DB 336. The checkout processing unit 316 then changes the entry / exit status included in the identified data entry to "left midway," and registers the date and time specified in the instruction to the date and time of leaving midway.

[0143] If an instruction to pay for a user who leaves the room early is issued when an early exit instruction is issued, the checkout processing unit 316 may calculate the usage fee for that user individually. In this case, the checkout processing unit 316 calculates the usage time from the entry date and time (or the entry / exit date and time) to the early exit date and time for the user identifier whose entry / exit status is set to "left the room early," and calculates the usage fee based on that usage time. The usage fee can be calculated based on the usage fee and the user's attributes, as in the calculation method described above.

[0144] Next, the checkout processing unit 316 sends transaction data including the calculated usage amount to the reception terminal 11 that sent the early exit instruction. The checkout processing unit 316 may also send the transaction data including the slip number and other data related to the karaoke booth from which the user is leaving. Then, when the checkout processing unit 316 receives a transaction completion notice from the reception terminal 11 that sent the transaction data notifying that the transaction is complete, the checkout processing unit 316 sets the transaction completion flag associated with the user identifier of the user who is leaving to "accounted."

[0145] This allows the facility management system 100 to individually process the accounts of users who leave the karaoke booth midway through their stay, thereby improving the convenience of users when using the karaoke booth.

[0146] [Information Department] The information providing unit 317 is an example of a generating means, an output means, and a providing means. The information providing unit 317 cooperates with the various DBs and functional configurations described above to provide support information for supporting the use and operation of the karaoke booth to external devices such as the reception terminal 11 and the external sales terminal 5.

[0147] Specifically, when the information providing unit 317 receives a login request including a set of the operator's employee ID and password from an external device such as the reception terminal 11 or the sales terminal 5, the information providing unit 317 executes an authentication process to check the set of employee ID and password against the set of employee ID and password registered in the employee management DB 331. If the authentication is successful, the information providing unit 317 provides the external device that sent the login request with support information for supporting the use and operation of the karaoke booths installed in the store corresponding to the store ID, based on the store ID and attributes associated with the employee ID.

[0148] For example, the information providing unit 317 provides support information for supporting operations related to check-in and check-out processes. Also, for example, the information providing unit 317 provides support information indicating the operating status of a karaoke booth. Also, for example, the information providing unit 317 provides support information for supporting operations related to reserving a karaoke booth.

[0149] The support information is a concept that includes not only data stored in various DBs, but also results derived from the data, screens such as GUIs (Graphical User Interfaces), control information for displaying the screens on external devices, etc. Examples of various screens displayed based on the support information will be described later.

[0150] [Notification processing section] The notification processor 318 issues various notifications regarding the use or operation of the karaoke booth. For example, when the notification processor 318 detects that the current date and time is a predetermined time (e.g., 10 minutes) before the scheduled date and time of leaving the karaoke booth, it notifies the user of the scheduled date and time of leaving the karaoke booth.

[0151] Specifically, the notification processor 318 detects a data entry that has reached a predetermined time (e.g., 10 minutes) before the scheduled date and time of leaving the room by comparing the current date and time with the scheduled date and time of leaving included in each data entry in the check-in management DB 336. Then, based on the set of the store ID and room ID included in the detected data entry, the notification processor 318 transmits notification information including the scheduled date and time of leaving the room to the ordering terminal 12 installed in the karaoke booth of the corresponding store.

[0152] This allows the facility management system 100 to notify users who are currently using a karaoke booth that the scheduled time to leave is approaching. Therefore, the facility management system 100 can improve the convenience of using a karaoke booth.

[0153] The destination of the notification information is not limited to the ordering terminal 12, and if the user terminal 4 of the user can be identified based on the member ID or the like, the notification information may be sent to the user terminal 4 of the user currently using the karaoke booth. In this case, the notification processing unit 318 may send the notification to the user terminal 4 of the representative user, or to the user terminal 4 of each user whose entry / exit status is "entering" or "entered midway." Furthermore, the timing of the notification of the scheduled departure date and time is not limited to a predetermined time before the scheduled departure date and time, but may also be when the scheduled departure date and time arrives or when a predetermined time has passed since the scheduled departure date and time.

[0154] [Functional configuration of reception terminal 11] Next, a description will be given of the functional configuration of the reception terminal 11. As shown in Fig. 10, the reception terminal 11 includes a first display control unit 1101, a first operation reception unit 1102, and a first cooperation processing unit 1103 as functional components.

[0155] The functional configuration of the receiving terminal 11 may be a software configuration realized by cooperation between the processor 111 of the receiving terminal 11 and various programs stored in a non-volatile memory area. Also, the functional configuration of the receiving terminal 11 may be a hardware configuration realized by a dedicated circuit or the like installed in the receiving terminal 11.

[0156] The first display control unit 1101 controls the display unit 116 of the reception terminal 11 and displays various screens on the display unit 116. For example, the first display control unit 1101 cooperates with the first cooperation processing unit 1103 to display various screens for supporting the use and operation of the karaoke booth.

[0157] The first operation receiving unit 1102 receives an operation from an operator via the operation unit 117 of the reception terminal 11. For example, the first operation receiving unit 1102 receives an operation for various screens displayed by the first display control unit 1101.

[0158] The first cooperation processing unit 1103 cooperates with the infrastructure server 3 to support processes related to the use and operation of the karaoke booth using the reception terminal 11. Specifically, the first cooperation processing unit 1103 displays a screen for supporting the use and operation of the karaoke booth on the display unit 116 based on various support information provided by the infrastructure server 3.

[0159] When starting collaboration with the infrastructure server 3, the first collaboration processing unit 1103 authenticates the operator by sending a login request including the employee ID and password of the employee who will be the operator to the infrastructure server 3. Then, based on support information provided by the infrastructure server 3 upon successful authentication, the first collaboration processing unit 1103 displays a screen on the display unit 116 to support the use and operation of the karaoke booth.

[0160] [Functional configuration of store clerk terminal] Next, we will explain the functional configuration of the sales terminal 5. As shown in Fig. 10, the sales terminal 5 includes a second display control unit 511, a second operation receiving unit 512, and a second link processing unit 513 as functional components.

[0161] The functional configuration of the sales terminal 5 may be a software configuration realized by cooperation between the processor 51 of the sales terminal 5 and various programs stored in a non-volatile memory area. Also, the functional configuration of the sales terminal 5 may be a hardware configuration realized by a dedicated circuit or the like installed in the sales terminal 5.

[0162] The second display control unit 511 controls the display unit 56 of the sales terminal 5 and displays various screens on the display unit 56. For example, the second display control unit 511 cooperates with the second link processing unit 513 to display various screens for supporting the use and operation of the karaoke booth.

[0163] The second operation receiving unit 512 receives operations from the operator via the operation unit 57 of the sales terminal 5. For example, the second operation receiving unit 512 receives operations for various screens displayed by the second display control unit 511.

[0164] The second cooperation processing unit 513 cooperates with the infrastructure server 3 to support the processing related to the use and operation of the karaoke booth using the sales terminal 5. Specifically, the second cooperation processing unit 513 displays a screen on the display unit 56 to support the use and operation of the karaoke booth based on various support information provided by the infrastructure server 3.

[0165] When starting collaboration with the infrastructure server 3, the second collaboration processing unit 513 authenticates the operator by sending a login request including the employee ID and password of the employee who will be the operator to the infrastructure server 3. Then, based on support information provided by the infrastructure server 3 following successful authentication, the second collaboration processing unit 513 displays a screen on the display unit 56 to support the use and operation of the karaoke booth.

[0166] [Example of facility management system operation] An example of the operation of the above-mentioned infrastructure server 3, sales terminal 5, and reception terminal 11 will be described below.

[0167] [Linkage between infrastructure server and external sales terminal] First, a description will be given of an example of the operation performed between the infrastructure server 3 and the reception terminal 11. Fig. 12 is a sequence diagram showing an example of the cooperation start processing performed between the infrastructure server 3 and the reception terminal 11.

[0168] First, when an employee starts operating the reception terminal 11, the employee inputs his / her own employee ID and password into the reception terminal 11. When the first collaboration processing unit 1103 of the reception terminal 11 receives the input of the employee ID and password (ACT11), it transmits a login request including the store ID of the employee's store and the input combination of employee ID and password to the infrastructure server 3 (ACT12).

[0169] When the information providing unit 317 of the infrastructure server 3 receives the login request, it performs an authentication process to compare the employee ID and password pair included in the login request with each employee ID and password pair registered in the employee management DB 331 (ACT13).

[0170] If a combination of employee ID and password that matches the combination included in the login request is stored in the employee management DB 331, the information providing unit 317 determines that the authentication is successful. In this case, the information providing unit 317 references various DBs and extracts data related to the store ID specified in the login request, thereby generating support information related to the store with that store ID (ACT14). Then, the information providing unit 317 provides the generated support information to the reception terminal 11 (ACT15).

[0171] The first cooperation processing unit 1103 of the reception terminal 11 displays a screen for supporting the use and operation of the karaoke booth on the display unit 116 based on the support information provided by the infrastructure server 3 (ACT16). In response to various operations performed on the reception terminal 11, the information providing unit 317 of the infrastructure server 3 provides the reception terminal 11 with support information corresponding to the operation content.

[0172] Furthermore, if the employee management DB 331 does not store a set of employee ID and password that matches the set of employee ID and password included in the login request, the information providing unit 317 determines that the authentication has failed. In this case, the information providing unit 317 transmits response information notifying the reception terminal 11 of the authentication failure (ACT17). In this case, the first collaboration processing unit 1103 of the reception terminal 11 displays a screen notifying the authentication failure on the display unit 116 based on the response information provided from the infrastructure server 3 (ACT18).

[0173] For example, the first cooperation processing unit 1103 of the reception terminal 11 displays on the display unit 116 an operation screen for supporting the use and operation of the karaoke booth, based on support information provided by the infrastructure server 3 following successful authentication.

[0174] Fig. 13 is a diagram showing an example of an operation screen displayed on the reception terminal 11. As shown in Fig. 13, the operation screen A has an information display field Aa, a tab display field Ab, a display area Ac, and the like.

[0175] The information display field Aa displays various information such as the current date and time, a terminal ID that can identify the reception terminal 11, and the name of the operator who has been successfully authenticated. The tab display field Ab displays, for example, tabs Aba and Abb. The tabs Aba and Abb are controls for switching functions, and a screen corresponding to the selected function is displayed in the display area Ac.

[0176] The tab Aaa is an operator for selecting a list of karaoke booths installed in the store. When the first collaboration processor 1103 accepts the operation of the tab Aaa, it transmits a room list request including the store ID of the store to the infrastructure server 3.

[0177] When the information providing unit 317 of the infrastructure server 3 receives a room list request, it provides support information to the reception terminal 11 indicating the status of each karaoke box owned by the store with the store ID specified in the room list request, based on the data entries of various DBs related to the store ID specified in the room list request.

[0178] The first cooperation processing unit 1103 displays a room list screen showing a list of each karaoke booth on the display unit 116 (display area Ac) based on the support information provided from the infrastructure server 3. Note that the tab Aba may be configured to be automatically selected in the initial state when the operation screen A is displayed.

[0179] Fig. 14 is a diagram showing an example of a room list screen displayed on the reception terminal 11. As shown in Fig. 14, the room list screen B has an operator field Ba and a list area Bb.

[0180] Room buttons Bc representing each karaoke booth are arranged and displayed in the list area Bb. The room buttons Bc are an example of an image. Each room button Bc is, for example, a rectangular display area, and is associated with the room ID of the corresponding karaoke booth. The room buttons Bc are provided in the same number as the number of karaoke booth rooms, and are arranged, for example, in the order of the room ID.

[0181] The operator field Ba displays various operators related to display control of the room buttons Bc. For example, the operator field Ba is provided with a first operator Baa and a second operator Bab for specifying the arrangement order (display order) of the room buttons Bc to be displayed in the list area Bb, a third operator Bac for narrowing down the room buttons Bc to be displayed, a fourth operator Bad and a fifth operator Bae for changing the number of room buttons Bc to be displayed on one screen, etc.

[0182] With the first operator Baa and the second operator Bab, the order of the room buttons Bc to be displayed can be changed by combining, for example, the order of the room ID (room number), the order of the scheduled time of leaving the room, the karaoke machine model, the order of the maximum number of people (or the minimum number of people), etc. Also, with the first operator Baa and the second operator Bab, the order of the room buttons Bc to be displayed can be changed depending on the status of the object to be displayed, such as "entering the room," "cleaning," or "out of order." Note that Fig. 14 shows an example in which the room buttons Bc are displayed in the order of the room numbers set in the first operator Baa.

[0183] The third operator Bac is an operator for enabling selection of only the room buttons Bc of karaoke booths awaiting cleaning or in the process of cleaning. When the first cooperation processing unit 1103 receives an operation of the third operator Bac, it disables selection of room buttons Bc in other states by graying out the room buttons Bc other than the room buttons Bc of karaoke booths awaiting cleaning or in the process of cleaning. In other words, only the room buttons Bc of karaoke booths awaiting cleaning or in the process of cleaning are enabled and can be selected.

[0184] When the first cooperation processor 1103 receives an operation to select one or more room buttons Bc from the enabled room buttons Bc, it switches the name displayed on the third operator Bac from "Batch Cleaning" to "Change." After switching to "Change," the third operator Bac (hereinafter also referred to as the "Change button") is an operator for switching the state of the selected room buttons Bc all at once. Note that the first cooperation processor 1103 may perform exclusive control to only accept the selection operation of the room button Bc for one of the states, in order to prevent the "Waiting for Cleaning" and "Cleaning" room buttons Bc from being selected together.

[0185] When the first collaboration processor 1103 accepts the operation of the change button described above, it performs processing to switch the status of the karaoke booth corresponding to each selected room button Bc to the next status. For example, when the first collaboration processor 1103 accepts the operation of the change button while the "waiting for cleaning" room button Bc is selected, it sends a cleaning start notification to the infrastructure server 3, including the store ID of its own store and the room ID of each selected room button Bc, thereby switching the status of the corresponding karaoke booth to "cleaning in progress." For example, when the first collaboration processor 1103 accepts the operation of the change button while the "cleaning in progress" room button Bc is selected, it sends a cleaning completion notification to the infrastructure server 3, including the store ID of its own store and the room ID of each selected room button Bc, thereby switching the status of the corresponding karaoke booth to "vacant."

[0186] In addition, the first collaboration processing unit 1103 may hide room buttons Bc other than those of karaoke booths in the ``waiting for cleaning'' and ``cleaning in progress'' states, provided that the room button Bc is operated, thereby narrowing down the room buttons Bc displayed to those in the ``waiting for cleaning'' and ``cleaning in progress'' states.

[0187] The fourth operator Bad and the fifth operator Bae can each instruct to display a different number of room buttons Bc. For example, the fourth operator Bad is used to instruct to display 6 x 8 room buttons Bc on one screen. The fifth operator Bae is used to instruct to display 6 x 4 room buttons Bc on one screen. In response to the operation of the fourth operator Bad or the fifth operator Bae, the first cooperation processor 1103 changes the number of room buttons Bc to be displayed on one screen, as well as the size of the room buttons Bc and the amount of information to be displayed on the room buttons Bc. Note that FIG. 14 shows an example in which the fifth operator Bae is selected.

[0188] Each room button Bc displays basic information about the corresponding karaoke booth and information according to its status.

[0189] 15 to 18 are diagrams showing examples of the display of a room button Bc. Here, FIG. 15 shows a room button Bc of a karaoke booth that is in an "vacant" state. As shown in FIG. 15, the room button Bc of a karaoke booth that is in an "vacant" state displays basic information such as the room name Bca, maximum capacity Bcb, minimum capacity Bcc, karaoke machine type Bcd, etc. Note that even if a karaoke booth is in an "vacant" state, if reservation information for that karaoke booth is registered in the reservation management DB 337, the room button Bc displays the most recent reservation date and time Bce.

[0190] Fig. 16 shows the room button Bc of a karaoke booth in the "Entering the Room" state. As shown in Fig. 16, the room button Bc of a karaoke booth in the "Entering the Room" state displays basic information such as the room name Bca, maximum capacity Bcb, minimum capacity Bcc, and karaoke machine Bcd, as well as information about the user currently using the karaoke booth.

[0191] For example, the room button Bc of a karaoke booth in the "entering" state displays information such as the start date and time Bcf, the number of users Bcg, the scheduled time of leaving Bch, the remaining time Bci, an information icon Bcj, and the sales amount Bck. Here, the start date and time Bcf, the number of users Bcg, and the scheduled time of leaving Bch correspond to the entry date and time, the number of users, and the scheduled time of leaving contained in the data record of the corresponding karaoke booth stored in the check-in management DB 336. The remaining time Bci is information indicating the time from the current date and time to the scheduled time of leaving.

[0192] The information icon Bcj displays an icon representing information related to the use of the karaoke booth. For example, the information icon Bcj displays an icon representing a room course, etc., based on the data record of the corresponding karaoke booth stored in the check-in management DB 336. Furthermore, based on the data record of the corresponding karaoke booth stored in the reservation management DB 337, if reservation information in which the reservation date and time is set within a predetermined time from the scheduled departure date and time is registered in the reservation management DB 337, an icon image indicating that extension is not possible is displayed on the information icon Bcj.

[0193] The sales amount Bck represents the current amount spent at the karaoke booth and is calculated, for example, in cooperation with the checkout processing unit 316.

[0194] Fig. 17 shows the room buttons Bc of karaoke booths in the "waiting for cleaning" and "cleaning in progress" states. As shown in Fig. 17, the room buttons Bc of karaoke booths in the "waiting for cleaning" and "cleaning in progress" states display basic information such as the room name Bca, maximum capacity Bcb, karaoke machine type Bcd, etc. In addition, if reservation information has been registered for the karaoke booth of the room button Bc, the most recent reservation date and time Bce is displayed.

[0195] Additionally, the room buttons Bc of karaoke booths in the "waiting for cleaning" and "cleaning" states display information icons Bcl, elapsed time Bcm, priority order Bcn, etc.

[0196] The information icon Bcl displays an icon representing information related to cleaning of the karaoke booth. For example, if the time from the current date and time to the nearest reservation date and time is less than a predetermined time based on the data record of the corresponding karaoke booth stored in the reservation management DB 337, an icon image representing urgency is displayed on the information icon Bcl.

[0197] The elapsed time Bcm indicates the time that has elapsed since the status was switched to "waiting for cleaning" (or "cleaning in progress"). The elapsed time Bcm corresponds to the time from the status start date and time of the corresponding karaoke booth stored in the status management DB 335 to the current date and time.

[0198] The priority Bcn indicates the priority of cleaning. There is no particular restriction on the method of deriving the priority, and various methods can be used. For example, the priority Bcn may be determined by sorting the elapsed time Bcm in descending order. The priority Bcn may also be determined based on whether a reservation has been made for the corresponding karaoke booth, the time between the current date and time and the reservation date and time, etc.

[0199] Figure 18 shows the room button Bc of a karaoke booth that is in an "out of order" state. As shown in Figure 18, the room button Bc of a karaoke booth that is in an "out of order" state displays basic information such as the room name Bca, maximum capacity Bcb, karaoke machine model Bcd, etc. In addition, the room button Bc of a karaoke booth that is in an "out of order" state displays the date and time of the outage Bco, the reason for the outage Bcp, etc.

[0200] The failure date and time Bco indicates the date and time when the status changed to "out of order". The failure date and time Bco corresponds to the start date and time of the status of the corresponding karaoke booth stored in the status management DB 335, for example. The failure reason Bcp indicates the reason why the karaoke booth became "out of order". The failure reason Bcp corresponds to the failure reason of the corresponding karaoke booth stored in the status management DB 335, for example.

[0201] The room buttons Bc in each of the above states are displayed in a manner that allows each state to be visually distinguished. For example, the room buttons Bc are displayed in different colors according to the state of "vacant," "occupied," "waiting for cleaning," "cleaning in progress," and "out of order," so that each state can be distinguished.

[0202] This allows the operator to easily check the status of each karaoke booth installed in his / her own store by looking at the room list screen B. Therefore, the facility management system 100 can improve the convenience of using and operating the karaoke booths.

[0203] Furthermore, the room buttons Bc in the "vacant" state may be displayed in a manner that makes it possible to distinguish whether or not the corresponding karaoke booth has a reservation. For example, the room buttons Bc may be displayed in different colors depending on whether or not a reservation has been made. Furthermore, the remaining time until the reservation date and time may be displayed in a manner that makes it possible to distinguish whether or not a reservation has been made by changing the display color of the room buttons Bc or by changing the shade of the display color depending on the number of hours from the current date and time to the nearest reservation date and time.

[0204] This allows the operator to easily check whether or not a reservation exists for a karaoke booth that is "vacant" by looking at the room list screen B. Also, by looking at the room list screen B, the operator can intuitively grasp the remaining time until the reservation for a karaoke booth that is "vacant." Therefore, the facility management system 100 can improve the convenience of using and operating karaoke booths.

[0205] Furthermore, the room button Bc in the "Enter" state may be displayed in a different color depending on the remaining time. For example, the remaining time may be divided into multiple time intervals, such as 11 minutes or more until the scheduled room leaving date and time, 0 to 10 minutes until the scheduled room leaving date and time, 1 to 15 minutes after the scheduled room leaving date and time, and 16 minutes or more after the scheduled room leaving date and time, and the display color may be changed for each interval or the shade of the display color may be changed to clearly display the relationship between the scheduled room leaving date and time and the remaining time.

[0206] This allows the operator to easily check the usage status of karaoke booths that are in the "entered" state by looking at the room list screen B. Also, the operator can easily check karaoke booths that have passed their scheduled exit date and time by looking at the room list screen B. Therefore, the facility management system 100 can improve the convenience of using and operating karaoke booths.

[0207] Each room button Bc also functions as an operator for accepting various operations for the corresponding karaoke booth. Specifically, when the first collaboration processor 1103 accepts an operation for a room button Bc, it notifies the infrastructure server 3 of an operation request including the store ID of its own store and the room ID corresponding to the karaoke booth of the operated room button Bc.

[0208] When the information providing unit 317 of the infrastructure server 3 receives an operation request, it provides support information for supporting an operation according to the current state of the karaoke booth corresponding to the combination of the store ID and room ID specified in the operation request to the reception terminal 11 that transmitted the operation request. The first collaboration processing unit 1103 of the reception terminal 11 displays various screens on the display unit 116 based on the support information provided from the infrastructure server 3.

[0209] For example, when the first collaboration processing unit 1103 receives an operation on the room button Bc in the "vacant" state, it causes the display unit 116 to display a vacant selection screen having operators for performing operations such as check-in, malfunction setting, and return to cleaning.

[0210] 19 is a diagram showing an example of a vacant room selection screen displayed on the reception terminal 11. Here, the vacant room selection screen C is an example of a screen that is displayed when the "vacant" room button Bc is operated, and has operators such as an enter room button Ca, a malfunction setting button Cb, and a return to cleaning button Cc.

[0211] The enter button Ca is an operator for checking a user in. When the first cooperation processing unit 1103 receives an operation of the enter button Ca, it displays a user information input screen for inputting user information of the user who is checking in.

[0212] 20 and 21 are diagrams showing an example of a user information input screen displayed on the reception terminal 11. As shown in Fig. 20 and 21, the user information input screen D has a member button Da, a non-member button Db, a user information field Dc, and an operator field Dd.

[0213] The member button Da and non-member button Db are controls for switching input items depending on whether the user is a member or not. When the first collaboration processor 1103 receives an operation of the member button Da, it displays input items for members in the user information field Dc.

[0214] 20 shows the state when the member button Da is selected, and the user information field Dc displays a scan button Dca, a member ID display field Dcb, a date of birth input field Dcc, etc. Here, the scan button Dca is an operator for instructing the reading of the member ID.

[0215] When the first collaboration processing unit 1103 accepts operation of the scan button Dca, it works in cooperation with the reading unit 118 and the like to read the member ID from a medium held by the user. When the first collaboration processing unit 1103 acquires the member ID via the reading unit 118 and the like, it displays the acquired member ID in the member ID display field Dcb. In addition, the first collaboration processing unit 1103 sends a member lookup request including the acquired member ID to the infrastructure server 3. When the information providing unit 317 of the infrastructure server 3 accepts the member lookup request, it reads out the member information corresponding to the member ID specified in the member lookup request from the member management DB and provides it to the reception terminal 11 that made the request.

[0216] When the first collaboration processing unit 1103 acquires member information from the infrastructure server 3 in response to the member reference request, it displays the date of birth included in the member information in the date of birth input field Dcc. Note that when the member button Da is selected, information other than the date of birth included in the member information may be displayed in the user information field Dc.

[0217] On the other hand, when the non-member button Db is selected, the first collaboration processing unit 1103 displays input items for non-members in the user information field Dc. Fig. 21 shows a state in which the non-member button Db is selected, and a name input field Dcd, a date of birth input field Dce, a contact information input field Dcf, an identification card selection button Dcg, etc. are displayed in the user information field Dc.

[0218] The name input field Dcd is an input field for inputting the user's name. The birth date input field Dce is an input field for inputting the user's birth date. The contact information input field Dcf is an input field for inputting the user's contact information.

[0219] The operator of the reception terminal 11, for example, enters the user's name and date of birth written on their identification card into the name input field Dcd and date of birth input field Dce. The operator of the reception terminal 11 also enters, for example, the telephone number of the user terminal 4 held by the user into the contact information input field Dcf. Note that the user may be configured to enter information into the name input field Dcd, date of birth input field Dce, and contact information input field Dcf themselves.

[0220] The ID selection button Dcg is an operator that can select various types of ID, such as a driver's license or student ID. In stores, if the user is not a member, an employee may check the user's ID to confirm the user's age, etc. The ID selection button Dcg is operated by the employee when checking the user's ID, and allows the employee to select the type of ID that has been checked. The selected type of ID is used as an indicator when applying services such as student discounts. Note that the configuration may also be such that input into other input fields is disabled until one of the types is selected.

[0221] 20 and 21, various types of operators are provided in the operator field Dd. For example, the operator field Dd is provided with a back button Dda, a reset button Ddb, an add button Ddc, an OK button Ddd, etc. The back button Dda is an operator that instructs returning to the source screen. When the back button Dda is operated, the first cooperation processor 1103 displays the source screen.

[0222] The reset button Ddb is an operator that instructs to reset the information entered in the user information field Dc. When the reset button Ddb is operated, the first cooperation processor 1103 clears the various pieces of information entered in the user information field Dc.

[0223] The Add button Ddc is an operator that instructs the addition of a user. When the Add button Ddc is operated, the first collaboration processor 1103 stores the various pieces of information entered in the user information field Dc in RAM or the like as user information for one user. The first collaboration processor 1103 also clears the user information field Dc to prepare for input of user information for the next user. The first collaboration processor 1103 may also be configured to assign a user identifier when storing user information for one user.

[0224] The OK button Ddd is an operator that instructs the user to confirm their identity. When the OK button Ddd is operated, the first collaboration processor 1103 displays the usage information input screen shown in Fig. 22 on the display unit 116. Furthermore, if information has been entered in the user information field Dc at the time the OK button Ddd is operated, the first collaboration processor 1103 stores the various pieces of input information in RAM or the like as user information for one user, and then displays the basic information input screen on the display unit 116.

[0225] In this embodiment, user information is entered on the user information entry screen D for each user using the karaoke booth, but this is not limiting, and for example, only the user information of a representative user may be entered. Also, the information that can be entered on the user information entry screen D is not limited to the above example.

[0226] Fig. 22 is a diagram showing an example of a usage information input screen displayed on the reception terminal 11. As shown in Fig. 22, the usage information input screen E has a number of people input field Ea, a course input field Eb, an option input field Ec, a scheduled usage time input field Ed, and an operator field Ee.

[0227] The number of people input field Ea allows the number of people using the karaoke booth and their age group to be entered. The number of people input field Ea is provided with a + button Eaa, a - button Eab, and a number of people display field Eac, which allow the number of people to be specified for each age group, for example. The + button Eaa is an operator for instructing the user to add one to the number of people. The - button Eab is an operator for instructing the user to subtract one from the number of people.

[0228] The first collaboration processing unit 1103 adds 1 to the number of people in the corresponding age category each time it receives a press of the + button Eaa, and displays the added number in the number of people display field Eac for that age category. The first collaboration processing unit 1103 also subtracts 1 from the number of people in the corresponding age category each time it receives a press of the - button Eab, and displays the subtracted number in the number of people display field Eac for that age category. The - button Eab is enabled when the number of people displayed in the number of people display field Eac is 1 or greater. Setting the number of people is not limited to operations via the + button Eaa and - button Eab; a numerical value may also be entered directly into the number of people display field Eac.

[0229] The first collaboration processor 1103 may determine the age category based on the birth date of each user entered on the user information input screen D, and display the number of people in each determined age category in the number display field Eac for the corresponding age category. In this case, the + button Eaa and the - button Eab can be used to adjust the number of people.

[0230] The number-of-people input field Ea is provided with a total number-of-people display field Ead. The first collaboration processing unit 1103 adds up the numbers of people displayed in the number-of-people display fields Eac for each age group, and displays the total number of people in the total number-of-people display field Ead.

[0231] The course input field Eb allows the user to specify the room course to be used. For example, the course input field Eb may be provided with an operator such as a pull-down menu that allows the user to select one room course from a plurality of preset room courses. When the operator selects one room course from the plurality of room courses, the selected room course is entered into the course input field Eb.

[0232] The option input field Ec allows the user to specify the option to be used. For example, the option input field Ec may be provided with an operator such as a pull-down menu that allows the user to select one option from a plurality of preset options. When the operator selects one option from the plurality of options, the selected option is entered into the option input field Ec.

[0233] In FIG. 22, multiple option input fields Ec are provided to allow multiple types of options to be selected, but the number of option input fields Ec may be one. Also, options may be selectable for each user. For example, by providing option input fields Ec on the user information input screen D, options can be selected for each user.

[0234] Furthermore, it is preferable that the options displayed as choices in the option input field Ec are selectable based on conditions such as the user's age category and room course. For example, if the user is a minor, it is preferable to exclude options that include the provision of alcoholic beverages from the choices. It is also preferable to exclude options that cannot be combined with the room course selected in the course input field Eb from the choices. The extraction of selectable options may be performed by the information providing unit 317 of the infrastructure server 3 or by the first collaboration processing unit 1103.

[0235] The scheduled use time input field Ed is an input field for inputting the scheduled use time. The operator inputs the time the user plans to use the karaoke booth in the scheduled use time input field Ed. If the time input in the scheduled use time input field Ed interferes with the reservation date and time set for the same karaoke booth, the first collaboration processing unit 1103 may display a notification screen informing the user that the time interferes with the reservation date and time or prompting the user to change the scheduled use time or the karaoke booth. Here, "interfering with the reservation date and time" means that the time overlaps with the reservation date and time, or that the time taken into account for cleaning the karaoke booth after use overlaps with the reservation date and time. The determination of whether the time interferes with the reservation date and time may be made by the information providing unit 317 of the infrastructure server 3 or by the first collaboration processing unit 1103.

[0236] The operator field Ee is provided with various operators. For example, the operator field Ee is provided with a back button Eea, an OK button Eeb, etc. The back button Eea is an operator that instructs returning to the source screen. When the back button Eea is operated, the first cooperation processing unit 1103 displays the source screen.

[0237] The OK button Eeb is an operator that instructs the confirmation of the information entered on the usage information input screen E. When the OK button Eeb is operated, the first collaboration processing unit 1103 transmits check-in information to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth that is the target of the operation, and various information entered on the user information input screen D and the usage information input screen E. Specifically, the first collaboration processing unit 1103 transmits to the infrastructure server 3 a check-in instruction that includes the user information held on the user information input screen D and the various information entered on the usage information input screen E.

[0238] When the OK button Eeb is operated, the maximum and minimum occupancies of the karaoke booth that is the target of the operation may be compared with the total number of users to determine whether the karaoke booth is available for use, and the result of the determination may be notified. Specifically, if the total number of users exceeds the maximum occupancy or is less than the minimum occupancy, a message notifying the user may be displayed on the display unit 116. In this case, the determination of whether the karaoke booth is available for use may be made by the information providing unit 317 of the infrastructure server 3 or by the first cooperation processing unit 1103.

[0239] The check-in processing unit 313 of the infrastructure server 3 starts check-in processing when it receives a check-in instruction from the reception terminal 11. Specifically, when the check-in processing unit 313 receives the check-in instruction, it issues a slip number. The check-in processing unit 313 also associates the issued slip number with the store ID, room ID, user information, etc. included in the check-in instruction and registers them in the check-in management DB 336.

[0240] When registering the user information included in the check-in instruction in the check-in management DB 336, the check-in processing unit 313 sets the entry / exit status of each user to "entering" and the payment completion flag to "unpaid." The check-in processing unit 313 also selects a representative from the users whose user information is included in the check-in instruction and registers the user identifier in the representative information field of the check-in management DB 336. The representative may be specified in the check-in instruction, or may be selected automatically by the check-in processing unit 313. When selecting automatically, the check-in processing unit 313 may select the first user entered based on the user identifier as the representative. The check-in processing unit 313 also registers elements other than the items in the check-in management DB 336 in the additional information field or the user additional information field.

[0241] Then, when the check-in processing unit 313 of the infrastructure server 3 completes the registration in the check-in management DB 336, it sends the issued slip number to the reception terminal 11 that sent the check-in instruction. As a result, in the infrastructure server 3, the status management unit 311 switches the status of the karaoke booth corresponding to the store ID and room ID for which the check-in process was performed from "vacant" to "occupied."

[0242] After sending a check-in instruction, the first linking processing unit 1103 of the reception terminal 11 receives a slip number from the infrastructure server 3, and controls the printing unit 119 to print a slip that includes at least the slip number. For example, the first linking processing unit 1103 prints a slip that includes the slip number, room ID, entry date and time, expected exit date and time, number of occupants, etc. The slip number may also be printed in a coded form, such as a barcode or two-dimensional code. This slip number is entered into the reception terminal 11, for example, at the time of checkout.

[0243] An example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the above-mentioned check-in process will now be described with reference to Fig. 23. Fig. 23 is a sequence diagram showing an example of the check-in process carried out between the infrastructure server 3 and the reception terminal 11. Note that this process is premised on the assumption that the karaoke booth to be operated is in a "vacant" state.

[0244] First, the first collaboration processing unit 1103 of the reception terminal 11 displays a user information input screen D on the display unit 116 (ACT21), and waits until user information of the user using the karaoke booth is input. When the first collaboration processing unit 1103 receives the input of the user information (ACT22), it displays a usage information input screen E on the display unit 116 (ACT23), and waits until usage information such as a room course is input. When the first collaboration processing unit 1103 receives the input of the usage information (ACT24), it sends a check-in request including the store ID of its own store, the karaoke booth room ID, the user information, the usage information, etc. to the infrastructure server 3 (ACT25).

[0245] When the check-in processing unit 313 of the infrastructure server 3 accepts the check-in request, it issues a slip number (ACT26). Next, the check-in processing unit 313 associates the issued slip number with the store ID, room ID, user information, and usage information included in the check-in request, and registers them in the check-in management DB 336 (ACT27). Next, the check-in processing unit 313 notifies the infrastructure server 3 of the issued slip number (ACT28).

[0246] Furthermore, in accordance with the processing of ACT27, the status management unit 311 of the infrastructure server 3 switches the status of the status management DB 335 corresponding to the room ID specified in the check-in request from "vacant" to "occupied" (ACT29). Furthermore, the status management unit 311 registers the operation history of the karaoke booth whose status has been switched in the operation history DB 338 (ACT30).

[0247] When the first cooperation processing unit 1103 of the reception terminal 11 receives the slip number from the infrastructure server 3 as a response to the check-in request, it prints a slip including the slip number (ACT31). When the slip is printed, the operator of the reception terminal 11 hands the slip to the user and urges them to proceed to the karaoke booth.

[0248] This completes the check-in process for the user at the store, and the user is now able to use the karaoke booth.

[0249] The above explains how users who have not made a reservation for a karaoke booth can enter (check in), but users who have made a reservation can check in, for example, using the following method.

[0250] First, the operator of the reception terminal 11 requests the infrastructure server 3 to read out reservation information based on key information that can identify the reservation information. Here, the key information can be any information that can be used as a search key, such as the user's membership ID, the reservation date and time, the reserved room ID, etc. The check-in processing unit 313 (or the information providing unit 317) of the infrastructure server 3 reads out the reservation information corresponding to the key information from the reservation management DB 337 and transmits the reservation information to the reception terminal 11.

[0251] The first collaboration processor 1103 displays a user information input screen D and a usage information input screen E based on the reservation information provided by the infrastructure server 3. For example, the first collaboration processor 1103 displays the user information input screen D and the usage information input screen E that reflect the user information (member ID), number of users, planned usage time, etc. included in the reservation information. Then, the first collaboration processor 1103 sends a check-in request including the information entered on the user information input screen D and the usage information input screen E to the infrastructure server 3, in the same manner as described above.

[0252] This allows the reception terminal 11 to perform check-in processing based on the reservation information. Note that the infrastructure server 3 deletes the reservation information from the reservation management DB 337 upon completion of transmission of the reservation information to the reception terminal 11 or registration in the check-in management DB 336.

[0253] 19, the malfunction setting button Cb on the vacant room selection screen C is an operator to be operated when a malfunction or the like occurs in the karaoke booth. When the first cooperation processing unit 1103 receives an operation of the malfunction setting button Cb, it displays a malfunction setting screen for inputting the reason for the malfunction or the like.

[0254] Fig. 24 is a diagram showing an example of a fault setting screen displayed on the reception terminal 11. As shown in Fig. 24, the fault setting screen F has a fault reason input field Fa, a comment field Fb, and an operator field Fc.

[0255] The malfunction reason input field Fa is provided with option buttons Faa that indicate the names of various pieces of equipment provided in the karaoke booth and the reasons for the malfunction. By selecting the appropriate option button Faa, the operator inputs the name of that option button Faa as the malfunction reason. Note that the number of selectable option buttons Faa is not limited to one, and multiple buttons can be selected.

[0256] Any character string can be entered in the comment field Fb. For example, the operator enters a comment in the comment field Fb, such as additional information about the reason for the malfunction or a message to other employees.

[0257] The operator field Fc is provided with various operators. For example, the operator field Fc is provided with a back button Fca, an OK button Fcb, etc. The back button Fca is an operator that instructs returning to the source screen. When the back button Fca is operated, the first cooperation processor 1103 displays the source screen.

[0258] The OK button Fcb is an operator that instructs the confirmation of the information entered on the fault setting screen F. When the OK button Fcb is operated, the first collaboration processing unit 1103 transmits a fault occurrence notification to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, the fault reason entered on the fault setting screen F, comments, etc. Note that the first collaboration processing unit 1103 may also include the employee ID of the operator, etc., in the fault occurrence notification before transmitting it.

[0259] When the status management unit 311 of the infrastructure server 3 receives the failure occurrence notification, it identifies the data entry corresponding to the store ID and room ID specified in the failure occurrence notification from the status management DB 335. Next, the status management unit 311 changes the room status of the identified data entry from "vacant" to "out of order." Accordingly, the reception terminal 11 updates the display of the corresponding room button Bc in response to the change in the status of the karaoke booth.

[0260] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the above-mentioned fault setting will be described with reference to Fig. 25. Fig. 25 is a sequence diagram showing an example of the processing relating to the fault setting performed between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this processing, it is assumed that the karaoke booth to be operated is in a "vacant" state.

[0261] First, the first collaboration processing unit 1103 of the reception terminal 11 displays the fault setting screen F on the display unit 116 (ACT41), and waits until the reason for the fault, etc. is input. When the first collaboration processing unit 1103 receives the input of the reason for the fault, etc. (ACT42), it transmits a fault occurrence notification including the store ID of its own store, the room ID of the karaoke booth, the input reason for the fault, etc. to the infrastructure server 3 (ACT43).

[0262] When the status management unit 311 of the infrastructure server 3 receives the failure occurrence notification, it changes the status of the status management DB 335 corresponding to the room ID specified in the failure occurrence notification from "vacant" to "out of order" (ACT 44). In addition, the status management unit 311 registers the operation record of the karaoke booth whose status has been changed in the operation record DB 338 (ACT 45).

[0263] As a result, the karaoke booth in which the malfunction has occurred is clearly displayed on the reception terminal 11. Therefore, the operator of the reception terminal 11 can easily check the karaoke booths that are currently unavailable from the room list screen, etc.

[0264] 19, the Cleaning Return button Cc on the Vacant selection screen C is an operator that is operated to return a karaoke booth in an "Vacant" state to an "In Cleaning" state. When the first cooperation processing unit 1103 receives an operation of the Cleaning Return button Cc, it displays a Cleaning Return screen (not shown) having an operator that instructs to return to the cleaning state.

[0265] When the first collaboration processing unit 1103 receives an instruction to return to cleaning from the return to cleaning screen, it transmits an instruction to return to cleaning including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, etc. to the infrastructure server 3. The first collaboration processing unit 1103 may also transmit the employee ID of the operator to the infrastructure server 3 in the instruction to return to cleaning.

[0266] When the status management unit 311 of the infrastructure server 3 receives the instruction to return to the cleaning status, it identifies a data entry corresponding to the store ID and room ID specified in the instruction from the status management DB 335. Next, the status management unit 311 switches the room status of the identified data entry from "vacant" to "cleaning in progress." Accordingly, the reception terminal 11 updates the display of the corresponding room button Bc in response to the change in the status of the karaoke booth.

[0267] Next, an example of a screen displayed when the room button Bc in the "entering the room" state is operated will be described. When the first cooperation processing unit 1103 receives an operation on the room button Bc in the "entering the room" state, it causes the display unit 116 to display a "entering the room" selection screen having operators for performing operations such as accepting product orders, entering the room midway, leaving the room midway, registering a complaint, changing rooms, and checking out.

[0268] Fig. 26 is a diagram showing an example of a room entry selection screen displayed on the reception terminal 11. As shown in Fig. 26, the room entry selection screen G has operators such as an order button Ga, a room details button Gb, a complaint registration button Gc, a room change button Gd, and an accounting button Ge.

[0269] The order button Ga is an operator for placing an order for a product received from a karaoke booth user. When the first collaboration processing unit 1103 receives an operation of the order button Ga, it transmits a product menu request to the infrastructure server 3, specifying the store ID of its own store and the room ID of the karaoke booth that is the target of the operation.

[0270] When the information providing unit 317 of the infrastructure server 3 receives a product menu request from the reception terminal 11, it provides support information including product information of orderable products based on the product management DB 333 to the reception terminal 11 that sent the product menu request.

[0271] For example, when the information providing unit 317 of the infrastructure server 3 identifies a data entry corresponding to the combination of store ID and room ID instructed by the reception terminal 11 from the check-in management DB 336, it extracts orderable products from the product management DB 333 based on the age category of each user included in the data entry, etc.

[0272] As an example, if the users include minors, the information providing unit 317 provides support information to the reception terminal 11 to assist with product ordering operations, based on product information for the remaining products excluding products that cannot be provided to minors based on the restrictions set for each product. Furthermore, when information that can identify the user who placed the order is specified, the information providing unit 317 of the infrastructure server 3 may extract product information based on the age category of the corresponding user.

[0273] When the first cooperation processing unit 1103 receives support information from the infrastructure server 3 as a response to the product menu request, it causes the display unit 116 to display a product menu screen on which products can be ordered based on the support information.

[0274] Fig. 27 is a diagram showing an example of a product menu screen displayed on the reception terminal 11. As shown in Fig. 27, the product menu screen H has a category selection field Ha, a product menu field Hb, a price field Hc, a list button Hd, an operator field He, etc.

[0275] In the category selection field Ha, tab operators Haa categorized according to product categories, etc. are displayed. When a tab operator Haa is selected, the products belonging to the category of the operated tab operator are displayed in the product menu field Hb. Note that FIG. 25 shows an example in which tab operators are provided for each category: recommended products, lunch, salad, dessert, drink, and others (rental items, etc.). Also, FIG. 27 shows an example in which the lunch tab operator Haa is selected.

[0276] The product menu field Hb displays product buttons Hba representing each product. The product buttons Hba are associated with the product ID of the corresponding product, and product information such as the product name, price, and product image of the product corresponding to the product ID is displayed. The product buttons Hba also function as an operator for selecting the product to be ordered.

[0277] When the first cooperation processing unit 1103 receives a selection operation of a product button Hba, it associates the product ID of the selected product button Hba with the number of times it has been selected (number of points) and stores them in RAM, etc. Hereinafter, the process of storing the product ID and number of points related to the selected product is also referred to as "sales registration."

[0278] The price column Hc displays the total number of items and the total price of the items selected from the product menu column Hb. The first linkage processing unit 1103 displays the total number of items and the total price of the items selected from the product menu column Hb in the price column Hc based on the product ID and number of items of the registered sales items, the price of the item corresponding to the product ID, etc. If a discount or discount is applied, the amount may be displayed in the price column Hc.

[0279] A list button Hd is provided. The list button Hd is an operator for instructing the display of a list of registered sales items. When an operation of the list button Hd is received, the first linkage processing unit 1103 displays a list screen (not shown) that displays a list of the product names, prices, and quantities of registered sales items for each item. On the list screen, registered sales items can be confirmed, and items can be added or deleted, or items can be cancelled. The first linkage processing unit 1103 changes the quantity of registered sales items or cancels items in response to a change or cancellation of the quantity.

[0280] The operator field He displays various operators related to ordering products. For example, the operator field He may include a back button Hea, an order button Heb, etc. The back button Hea is an operator that instructs the user to return to the screen from which the user transitioned. The order button Heb is an operator that instructs the user to confirm the order.

[0281] When the back button Hea is operated, the first collaboration processor 1103 displays the original screen by collaborating with the infrastructure server 3. When the order button Heb is operated, the first collaboration processor 1103 transmits to the infrastructure server 3 order information including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, and the product ID and number of the product that has been registered for sale.

[0282] When the order receiving unit 314 of the infrastructure server 3 receives order information from the reception terminal 11, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the order information from the check-in management DB 336. Then, the order receiving unit 314 registers the order details included in the order information, i.e., the product ID and quantity of the ordered product, in the order information field of the identified data entry. The order receiving unit 314 of the infrastructure server 3 also notifies the kitchen terminal 13 or staff terminal 14 of the store ID specified in the order information that the user has ordered a product by sending the room ID and order details to the kitchen terminal 13 or staff terminal 14.

[0283] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 related to the above-mentioned product ordering will be described with reference to Fig. 28. Fig. 28 is a sequence diagram showing an example of the processing related to the product ordering carried out between the infrastructure server 3 and the reception terminal 11. Note that this processing is premised on the assumption that the karaoke booth to be operated is in the "entering the room" state.

[0284] First, in response to the operation of the order button Ga, etc., the first collaboration processing unit 1103 of the reception terminal 11 sends a product menu request to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth being used by the user placing the order, etc. (ACT51).

[0285] When the information providing unit 317 of the infrastructure server 3 receives the product menu request, it identifies the age category of the user based on the data entry in the check-in management DB 336 that corresponds to the combination of the store ID and room ID specified in the product menu request (ACT52). Next, the information providing unit 317 extracts product information from the product management DB 333 about products that are provided at the store with the store ID specified in the product menu request and that can be provided to the user, based on restrictions and the like set for each product in the product management DB 333 (ACT53). Next, the information providing unit 317 generates support information for supporting the product ordering operation, such as the product menu, based on the extracted product information (ACT54), and provides the generated support information to the reception terminal 11 (ACT55).

[0286] When the first collaboration processing unit 1103 of the reception terminal 11 receives support information as a response to the product menu request, it displays the product menu screen H on the display unit 116 based on the support information (ACT56). When the first collaboration processing unit 1103 receives a product selection operation via the product menu screen H (ACT57), it registers the sales of the product (ACT58). Then, when the first collaboration processing unit 1103 receives an order confirmation operation using the order button Heb or the like (ACT59), it transmits order information including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, and the product ID and number of the product that has been registered for sales to the infrastructure server 3 (ACT60).

[0287] When the order receiving unit 314 of the infrastructure server 3 receives the order information, it registers the order details included in the order information in a data entry of the check-in management DB 336 corresponding to the combination of the store ID and room ID specified in the order information (ACT61). Next, the order receiving unit 314 transmits the specified room ID and order details to the kitchen terminal 13 of the store ID specified in the order information (ACT62).

[0288] The kitchen terminal 13 outputs the room ID and the order details transmitted from the base server 3 (ACT63), thereby notifying the kitchen worker that the user has ordered a product.

[0289] Through the above process, the order details of the customer who is using the karaoke booth and the room ID of the karaoke booth are notified to the kitchen staff, etc. The ordered items are then delivered to the karaoke booth that the customer is using.

[0290] In this embodiment, an example of ordering a product using the reception terminal 11 has been described, but this is not limiting, and the same method can be used when ordering using the user terminal 4, the ordering terminal 12, etc. Specifically, the user terminal 4 and the ordering terminal 12, by linking with the infrastructure server 3, display a screen on which products can be ordered, such as the above-mentioned product menu screen H, and send order information to the infrastructure server 3 in response to an operation by the operator.

[0291] 26, the room details button Gb on the currently entered room selection screen G is an operator that displays detailed information about the karaoke booth that is the target of the operation. When the first collaboration processor 1103 accepts the operation of the room details button Gb, it transmits a room details request including the store ID of its own store and the room ID of the karaoke booth that is the target of the operation to the infrastructure server 3.

[0292] When the information providing unit 317 of the infrastructure server 3 receives a room detail request from the reception terminal 11, it identifies a data entry that meets the conditions of the combination of the store ID and room ID specified in the room detail request from the check-in management DB 336. Next, the information providing unit 317 provides support information indicating details of the karaoke booth in use to the reception terminal 11 that sent the room detail request, based on the identified data entry.

[0293] When the first cooperation processing unit 1103 transmits the room detail request to the infrastructure server 3, it causes the display unit 116 to display a room detail screen showing details of the karaoke booth currently in use, based on the support information provided by the infrastructure server 3.

[0294] Fig. 29 is a diagram showing an example of a room details screen displayed on the reception terminal 11. As shown in Fig. 29, the room details screen I has a detailed information field Ia, a user information field Ib, and an operator field Ic.

[0295] The detailed information field Ia displays the room name of the karaoke booth that was the target of the operation, "Room 5," as well as information about the user currently using the karaoke booth. Specifically, the detailed information field Ia displays the entry time (entry date and time), scheduled exit time (scheduled exit date and time), course (room course), number of users, membership category, membership fee, representative member (representative information), etc. Here, the membership category and membership fee are information that is displayed when the users include a member.

[0296] Furthermore, in the detailed information field Ia, a date and time change button Iaa is displayed in association with the scheduled date and time of leaving the room. The date and time change button Iaa is an operator for instructing a change of the scheduled date and time of leaving the room. When the first collaboration processing unit 1103 receives an operation of the date and time change button Iaa, it displays a time change screen (not shown) that allows the user to extend or shorten the scheduled date and time of leaving the room. The time change screen allows the user to specify the amount of time to be added or subtracted. For example, the time change screen is provided with an operator that allows the user to specify the amount of time to be added or subtracted in 30-minute increments.

[0297] When the time to be added or deleted is specified, the first collaboration processing unit 1103 sends a change instruction to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth that is the target of the operation, the time to be added or deleted, etc.

[0298] In response to the change instruction, the check-in processing unit 313 of the infrastructure server 3 identifies a data entry that meets the conditions of the specified store ID and room ID from the check-in management DB 336. Then, the check-in processing unit 313 adds or subtracts the time specified in the change instruction to the scheduled use time and scheduled use date and time included in the identified data entry. Accordingly, the scheduled room leaving time in the detailed information field Ia is updated to the changed scheduled room leaving time.

[0299] It is preferable that the check-in processing unit 313 adds time after checking the reservation status of the store ID and room ID specified in the change instruction by referring to the reservation management DB 337. Specifically, the check-in processing unit 313 may add time if it determines that the changed scheduled date and time of use will not interfere with the reservation date and time set for the same karaoke booth.

[0300] Furthermore, when adding (adding) time, the check-in processing unit 313 may be configured to refer to the basic information DB 334 and confirm that extension is not permitted before adding time. If the check-in processing unit 313 confirms that the time will interfere with the reservation date and time or that extension is not permitted, it sends response information to the reception terminal 11 that sent the change instruction, informing that extension is not permitted.

[0301] Furthermore, in the detailed information field Ia, a course change button Iab is displayed in association with the room course. The course change button Iab is an operator for instructing a change of the room course. When the first collaboration processing unit 1103 receives an operation of the course change button Iab, it displays a course change screen (not shown) on which the room course can be changed. On the course change screen, it is possible to specify the room course after the change. For example, the course change screen is provided with an operator such as a pull-down type operator that allows the user to select the room course after the change. Furthermore, the course change screen may include an operator that allows the user to specify the application date and time when the changed room course will be applied.

[0302] When the changed room course is specified, the first collaboration processing unit 1103 sends a change instruction to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, the changed room course, etc.

[0303] In response to the change instruction, the check-in processing unit 313 of the infrastructure server 3 identifies a data entry that meets the specified store ID and room ID conditions from the check-in management DB 336. Then, the check-in processing unit 313 changes the room course included in the identified data entry to the room course specified in the change instruction. Accordingly, the room course in the detailed information column Ia is updated to the changed room course.

[0304] Furthermore, if the change instruction specifies a date and time for applying the changed room course, the check-in processing unit 313 changes the room course to the specified date and time, but it is preferable to store information related to the room course before the change in additional information, etc. For example, the check-in processing unit 313 associates the room course before the change with the date and time when application of the room course before the change began (e.g., the date and time of entry into the room), and the date and time when application of the room course before the change ended (e.g., the date and time when the changed room course was applied) in the additional information column. The usage fees for the room courses before and after the change are calculated respectively according to their duration.

[0305] Even when a date and time for applying the room course is instructed, if the duration of the room course before the change does not reach a predetermined number of hours (for example, 30 minutes), the check-in processing unit 313 may return response information to the reception terminal 11 that sent the change instruction, notifying that the change is not possible. Furthermore, if the date and time for applying the changed room course is earlier than the date and time when the application of the room course before the change began, the check-in processing unit 313 may return response information notifying that the application times overlap, or may shorten the room course before the change and change it to the changed option. In the latter case, it is preferable that the check-in processing unit 313 change to the changed room course when a change instruction is received from the reception terminal 11.

[0306] Furthermore, if the options of the currently using user cannot be used in the changed room course, the check-in processing unit 313 may return response information to the reception terminal 11 that sent the change instruction, informing the user that the room course cannot be changed or urging the user to change the options. Note that the correspondence between each room course and the options available for each room course is assumed to be specified in advance in the form of setting information or the like.

[0307] Furthermore, the user information field Ib of the room details screen I displays content based on the user information in the check-in management DB 336. Specifically, the user information field Ib displays, for each user identifier (No.), information such as options, age category, status (entering / exiting status), entry time (entering date and time), mid-entry (mid-entering date and time), mid-exit (mid-entering date and time), and scheduled exit time (scheduled exit date and time) in association with the user identifier (No.).

[0308] Here, for users whose entry / exit status is "entered midway," the date and time of entry is displayed for those who entered midway. For users whose entry / exit status is "left midway," the date and time of exit is displayed for those who left midway. In addition, for users other than those whose entry / exit status is "left midway," the scheduled exit time is displayed as the scheduled exit date and time in the detailed information column Ia.

[0309] Furthermore, in the user information field Ib, an option change button Iba is displayed in association with the option. The option change button Iba is an operator for instructing a change of option. When the first collaboration processing unit 1103 receives an operation of the option change button Iba, it displays an option change screen (not shown) on which the option can be changed. On the option change screen, it is possible to specify the option after the change. For example, the option change screen is provided with an operator such as a pull-down type that allows the user to select the option after the change.

[0310] It is preferable that the option change screen displays a selection of selectable option types based on the user's age category and room course. The option change screen may also include an operator that allows the user to specify the application date and time when the changed option will be applied.

[0311] When the changed option is specified, the first collaboration processing unit 1103 sends a change instruction to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, the user identifier that was the target of the operation, the changed option, etc.

[0312] In response to the change instruction, the check-in processing unit 313 of the infrastructure server 3 identifies user information that meets the conditions of the specified store ID, room ID, and user identifier from the check-in management DB 336. Then, the check-in processing unit 313 changes the options included in the identified user information to the options specified in the change instruction. Accordingly, the options for the user identifier that was the target of the operation in the user information column Ib are updated to the changed options.

[0313] If the change instruction specifies a date and time for applying the changed option, the check-in processing unit 313 changes the option to the specified date and time, but it is preferable to store information related to the option before the change in the user's additional information, etc. In this case, for example, the check-in processing unit 313 associates the option before the change with the date and time when application of the option before the change began (e.g., the date and time of entry) and the date and time when application of the option before the change ended (e.g., the date and time when the changed option was applied) and stores them in the additional information column. Note that the usage fees for the options before and after the change are calculated according to their duration.

[0314] Note that even when an application date and time is instructed, if the duration of the option before the change does not reach a predetermined number of hours (for example, 30 minutes), the check-in processing unit 313 may return response information notifying that the change is not possible to the reception terminal 11 that sent the change instruction. Furthermore, if the application date and time of the changed option is earlier than the date and time when application of the option before the change began, the check-in processing unit 313 may return response information notifying that the application times overlap, or may shorten the option before the change and change it to the changed option. In the latter case, it is preferable that the check-in processing unit 313 change to the changed option when a change instruction is received from the reception terminal 11.

[0315] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the various change processes described above will be described with reference to Fig. 30. Fig. 30 is a sequence diagram showing an example of change processes carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise for this process, it is assumed that the room details screen I is displayed on the display unit 116 of the reception terminal 11.

[0316] When the first collaboration processing unit 1103 of the reception terminal 11 receives an operation via the room details screen I to instruct a change to the scheduled departure date and time, room course, options, etc. (ACT71), it sends a change instruction including the store ID of its own store, the room ID of the karaoke box to be operated on, and the change contents, etc. to the infrastructure server 3 (ACT72).

[0317] When the check-in processing unit 313 of the infrastructure server 3 receives the change instruction, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the change instruction from the check-in management DB 336 (ACT73). Next, the check-in processing unit 313 determines whether or not the change specified in the change instruction is possible based on the reservation information in the reservation management DB 337 associated with the same room ID, the age category of the user included in the data entry, etc. (ACT74).

[0318] If the check-in processing unit 313 of the infrastructure server 3 determines that the change is possible, it changes the registered content in the identified data entry based on the instructed change content (ACT 75). Next, the check-in processing unit 313 cooperates with the notification processing unit 318 to send support information that reflects the change content to the reception terminal 11 (ACT 76). If the change instruction specifies a date and time at which the change should be applied, the check-in processing unit 313 changes the registered content at the specified date and time.

[0319] The first cooperation processing unit 1103 of the reception terminal 11 updates the screen to reflect the changes by displaying the room details screen I or the like based on the support information provided from the infrastructure server 3 (ACT77).

[0320] Furthermore, if the check-in processing unit 313 of the infrastructure server 3 determines that the change is not permitted, it cooperates with the notification processing unit 318 to send response information including the reason why the change is not permitted to the reception terminal 11 (ACT78). In this case, the first cooperation processing unit 1103 of the reception terminal 11 displays the reason why the change is not permitted based on the response information provided from the infrastructure server 3 (ACT79). This allows the operator of the reception terminal 11 to easily review the content of the change based on the displayed reason why the change is not permitted.

[0321] 29, the leave midway button Ibb for instructing a user to leave midway is displayed in the leave midway column of the user information column Ib. The leave midway button Ibb is an operator for instructing a user to leave midway. When the first collaboration processor 1103 receives an operation of the leave midway button Ibb, it displays an leave midway screen on which the user can specify the time (date and time) to leave the room.

[0322] Fig. 31 is a diagram showing an example of an interim leaving screen displayed on the reception terminal 11. As shown in Fig. 31, the interim leaving screen J has a time input field Ja and an operator field Jb. The time input field Ja includes, for example, a current time button Jaa that can specify the current time, a time specification button Jab that can specify an arbitrary time, and a time display field Jac.

[0323] When the first collaboration processor 1103 of the reception terminal 11 accepts operation of the current time button Jaa, it displays the current time in the time display field Jac. When the first collaboration processor 1103 accepts operation of the time specification button Jab, it accepts the time input into the time display field Jac via the operation unit 117. Note that the time that can be input is within the range from the current time to the scheduled date and time of use.

[0324] The operator field Jb displays a back button Jba and an OK button Jbb. The back button Jba is an operator that instructs the user to return to the original screen. When the back button Jba is operated, the first collaboration processor 1103 collaborates with the infrastructure server 3 to display the original screen.

[0325] The OK button Jbb is an operator for specifying the time to leave the room. When the OK button Jbb is operated, the first collaboration processor 1103 transmits an instruction to leave the room to the infrastructure server 3, including the store ID of the store, the room ID of the karaoke booth that was the target of the operation, the user identifier of the user that was the target of the operation, and the time (date and time) displayed in the time display field Jac.

[0326] In response to the midway leaving instruction, the checkout processing unit 316 of the infrastructure server 3 identifies user information that meets the conditions of the store ID, room ID, and user identifier specified in the midway leaving instruction from the check-in management DB 336. Then, the checkout processing unit 316 changes the entry / exit status included in the identified user information to "midway leaving completed," and registers the time specified in the midway leaving instruction as the midway leaving date and time.

[0327] The operators provided in the operator field Jb are not limited to the above examples. For example, an operator (hereinafter also referred to as an "interim billing button") for instructing a user who leaves the room to pay during the session may be provided. An example of the operation when an "interim billing button" is provided will be described later.

[0328] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the above-mentioned midway leaving of a user will be described with reference to Fig. 32. Fig. 32 is a sequence diagram showing an example of the processing relating to midway leaving carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this processing, it is assumed that the room details screen I is displayed on the display unit 116 of the reception terminal 11.

[0329] When the first collaboration processing unit 1103 of the reception terminal 11 receives an instruction to a specific user identifier to leave early by operating the leave early button Ibb or the like displayed on the room details screen I (ACT81), it displays the above-mentioned leave early screen J (ACT82). Next, when the first collaboration processing unit 1103 receives a specification of the time to leave early via the leave early screen J (ACT83), it transmits an instruction to leave early to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth being operated, the user identifier of the user leaving early, the specified time to leave early, etc. (ACT84).

[0330] When the check-in processing unit 313 of the infrastructure server 3 receives the midway leaving instruction, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the change instruction from the check-in management DB 336 (ACT85). Next, the check-in processing unit 313 sets the entry / exit status of the user identifier specified in the midway leaving instruction, among the user identifiers included in the user information of the identified data entry, to "midway leaving completed" (ACT86), and registers the time specified in the midway leaving instruction in the midway leaving date and time field (ACT87). Next, the check-in processing unit 313, in cooperation with the notification processing unit 318, transmits support information reflecting the registered content to the reception terminal 11 (ACT88).

[0331] The first cooperation processing unit 1103 of the reception terminal 11 updates the screen to reflect the registered contents by displaying the room details screen I or the like based on the support information provided from the infrastructure server 3 (ACT89).

[0332] This allows the facility management system 100 to individually record users who leave the karaoke booth. Therefore, the facility management system 100 can individually manage users who use the karaoke booth.

[0333] Returning to Fig. 29, the user information column Ib displays a cancel entry button Ibc associated with each user identifier for instructing the user to cancel entry. The cancel entry button Ibc is an operator for instructing the user to cancel entry. Note that the cancel entry button Ibc is disabled for user identifiers for which the mid-exit date and time has been registered and for user identifiers whose entry / exit status is "entry canceled."

[0334] When the first collaboration processing unit 1103 receives an operation of the entry cancellation button Ibc, it sends an entry cancellation instruction to the infrastructure server 3, including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, the user identifier that was the target of the operation, etc.

[0335] In response to the entry cancellation instruction, the check-in processing unit 313 of the infrastructure server 3 identifies user information that meets the conditions of the specified store ID, room ID, and user identifier from the check-in management DB 336. Then, the check-in processing unit 313 changes the entry / exit status included in the identified user information to "entry canceled." Accordingly, in the user information field Ib of the reception terminal 11, the status of the user identifier that is the subject of entry cancellation is updated to "entry canceled."

[0336] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the cancellation of the user's entry will be described with reference to Fig. 33. Fig. 33 is a sequence diagram showing an example of the process relating to the cancellation of entry carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise for this process, it is assumed that the room details screen I is displayed on the display unit 116 of the reception terminal 11.

[0337] When the first collaboration processing unit 1103 of the reception terminal 11 receives an operation to instruct a specific user identifier to cancel entry by operating the entry cancellation button Ibc displayed on the room details screen I (ACT91), it sends an entry cancellation instruction to the infrastructure server 3 including the store ID of its own store, the room ID of the karaoke box being operated on, the user identifier for whom entry is to be canceled, etc. (ACT92).

[0338] When the check-in processing unit 313 of the infrastructure server 3 receives the entry cancellation instruction, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the entry cancellation instruction from the check-in management DB 336 (ACT93). Next, the check-in processing unit 313 sets the entry / exit status of the user identifier specified in the entry cancellation instruction, among the user identifiers included in the user information of the identified data entry, to "entry canceled" (ACT94). Next, the check-in processing unit 313 cooperates with the notification processing unit 318 to send support information reflecting the registered content to the reception terminal 11 (ACT95).

[0339] The first cooperation processing unit 1103 of the reception terminal 11 updates the screen to reflect the registered contents by displaying the room details screen I or the like based on the support information provided from the infrastructure server 3 (ACT96).

[0340] This allows the facility management system 100 to easily cancel entry if, for example, the operator of the reception terminal 11 has registered a user by mistake. The entry cancellation operation may be configured to be enabled / disabled depending on the operator's authority (employee authority), etc.

[0341] 29, various operators are displayed in the operator field Ic of the room details screen I. For example, the operator field Ic includes a back button Ica, a mid-room entry button Icb, a complimentary time button Icc, a slip print button Icd, an OK button Ice, etc.

[0342] The back button Ica is an operator for instructing to return to the original screen. When the back button Ica is operated, the first cooperation processor 1103 cooperates with the infrastructure server 3 to display the original screen.

[0343] The mid-session join button Icb is an operator that instructs adding a user who is a target of mid-session join. When the first collaboration processing unit 1103 receives an operation of the mid-session join button Icb, it displays an add users screen that allows an instruction to add a target user.

[0344] Fig. 34 is a diagram showing an example of a number of people addition screen displayed on the reception terminal 11. As shown in Fig. 34, the number of people addition screen K has a time input field Ka, a number of people input field Kb, an option input field Kc, and an operator field Kd.

[0345] The time input field Ka allows the user to input the time of entry midway. For example, the time input field Ka is provided with a From the beginning button Kaa for specifying the entry date and time, a time specification button Kab for specifying any time, a current time button Kac for specifying the current time, and a time display field Kad.

[0346] When the first collaboration processor 1103 of the reception terminal 11 initially accepts operation of the button Kaa, it displays the time set as the entry date and time in the time display field Kad based on the user information, etc., that was the target of the operation. Furthermore, when the first collaboration processor 1103 accepts operation of the time specification button Kab, it displays the time input via the operation unit 117 in the time display field Kad. Note that the time that can be input is within the range from the entry date and time to the scheduled use date and time. Furthermore, when the first collaboration processor 1103 of the reception terminal 11 accepts operation of the current time button Kac, it displays the current time in the time display field Kad.

[0347] The number of users input field Kb allows the number and attributes of users to be added to be entered. For example, the number of users input field Kb is provided with a + button Kba, a - button Kbb, and a number of users display field Kbc, which allow the number of users to be specified for each age group. The number of users input field Kb is also provided with a total number of users display field Kbd. The number of users input field Kb is the same as the number of users input field Ea described above.

[0348] In the option input field Kc, it is possible to specify options to be used by the user to be added. The option input field Kc is the same as the option input field Ec described above.

[0349] The operator field Kd displays various operators, such as a back button Kda, a reset button Kdb, and an OK button Kdc.

[0350] The back button Kda is an operator that instructs returning to the original screen. When the back button Kda is operated, the first cooperation processing unit 1103 cooperates with the infrastructure server 3 to display the original screen.

[0351] The reset button Kdb is an operator that instructs to reset the information input on the number of people addition screen. When the reset button Kdb is operated, the first collaboration processor 1103 clears the various information input on the number of people addition screen K.

[0352] The OK button Kdc is an operator that instructs to confirm the information entered on the number of people addition screen K. When the OK button Kdc is operated, the first collaboration processor 1103 transmits to the infrastructure server 3 an instruction to enter the room midway, including the store ID of its own store, the room ID of the karaoke booth that is the target of the operation, and various information entered on the number of people addition screen K.

[0353] The first collaboration processor 1103 may display an input screen (for example, user information input screen D) for inputting user information of users to be added prior to the number-of-people addition screen K. In this case, the first collaboration processor 1103 includes the user information of each user to be added in the mid-entry instruction and transmits it to the infrastructure server 3.

[0354] In response to the mid-entry instruction, the check-in processing unit 313 of the infrastructure server 3 identifies a data record that meets the specified store ID and room ID conditions from the check-in management DB 336. The check-in processing unit 313 then adds information about the user specified in the mid-entry instruction to the user information included in the identified data record. Here, the check-in processing unit 313 registers "mid-entered and exited" in the entry / exit status of the added user identifier, and registers the time specified in the mid-entry instruction as the mid-entry date and time. Accordingly, the information about the added user is reflected on various screens at the reception terminal 11.

[0355] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the mid-way entry of a user described above will be described with reference to Fig. 35. Fig. 35 is a sequence diagram showing an example of the processing relating to mid-way entry carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this processing, it is assumed that the room details screen I is displayed on the display unit 116 of the reception terminal 11. Also, in this processing, an example of the operation when the user information input screen D is displayed prior to the number of people addition screen K will be described.

[0356] When the first collaboration processing unit 1103 of the reception terminal 11 receives an operation to instruct a user to enter the room midway by operating the midway entry button Icb displayed on the room details screen I (ACT101), it displays the user information input screen D on the display unit 116 (ACT102).

[0357] When the first collaboration processing unit 1103 of the reception terminal 11 accepts input of user information of a user who will enter midway through the meeting via the user information input screen D (ACT103), the first collaboration processing unit 1103 displays the number of people addition screen K on the display unit 116 (ACT104).

[0358] The first collaboration processing unit 1103 accepts the specification of the time for mid-entry on the number of people addition screen K (ACT105). The first collaboration processing unit 1103 also accepts the input of additional information such as options on the number of people addition screen K (ACT106). Then, when an instruction is given via the OK button Kdc or the like to confirm the information related to the user who will enter the room mid-enter, the first collaboration processing unit 1103 transmits a mid-entry instruction to the infrastructure server 3 including the store ID of its own store, the room ID of the karaoke booth, user information, additional information, and the like (ACT107).

[0359] When the check-in processing unit 313 of the infrastructure server 3 receives the mid-entry instruction, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the mid-entry instruction from the check-in management DB 336 (ACT108). Next, the check-in processing unit 313 additionally registers the user information and additional information specified in the mid-entry instruction in the user information field of the identified data entry (ACT109).

[0360] Furthermore, the check-in processing unit 313 of the infrastructure server 3 sets the entry / exit status of the added user information to "entered midway" (ACT110), and registers the time specified in the midway entry instruction in the midway entry date and time field (ACT111). Next, the check-in processing unit 313 cooperates with the notification processing unit 318 to transmit support information reflecting the registered content to the reception terminal 11 (ACT112).

[0361] The first cooperation processing unit 1103 of the reception terminal 11 updates the room details screen I etc. based on the support information provided from the infrastructure server 3, thereby displaying a screen that reflects the registered contents (ACT113).

[0362] This allows the facility management system 100 to individually record users who enter the karaoke booth midway through a performance. Therefore, the facility management system 100 can individually manage users who use the karaoke booth.

[0363] Returning to FIG. 29, the complimentary time button Icc in the operator column Ic of the room details screen I is an operator for instructing the provision of complimentary time. Complimentary time is a free extension of time provided by the establishment when the establishment has caused inconvenience to the customer due to some reason, such as a store error. For example, complimentary time is provided when a customer complains.

[0364] When the first cooperation processing unit 1103 receives an operation of the free time button Icc, it displays a free time setting screen on which the free time can be set.

[0365] Fig. 36 is a diagram showing an example of a service time setting screen displayed on the reception terminal 11. As shown in Fig. 36, the service time setting screen L has an already-granted display field La, a time selection field Lb, a back button Lc, and an OK button Ld.

[0366] The granted service time display field La displays the granted service time. The time selection field Lb displays time buttons Lba. The time buttons Lba are controls that indicate the number of hours of service time. Multiple time buttons Lba are provided at intervals of a predetermined number of hours (5 minutes). The operator selects the amount of service time to be newly granted by operating any one of the time buttons Lba displayed in the time selection field Lb.

[0367] The back button Lc is an operator that instructs returning to the original screen. When the back button Lc is operated, the first cooperation processor 1103 cooperates with the infrastructure server 3 to display the original screen.

[0368] The OK button Ld is an operator that instructs to confirm the time selected in the time selection field Lb. When the OK button Ld is operated, the first collaboration processor 1103 transmits to the infrastructure server 3 a service time grant instruction that includes the store ID of its own store, the room ID of the karaoke booth that is the target of the operation, the time selected in the time selection field Lb, etc.

[0369] In response to the discount time granting instruction, the check-in processing unit 313 of the infrastructure server 3 identifies a data record that meets the specified store ID and room ID conditions from the check-in management DB 336. Then, the check-in processing unit 313 registers the time specified in the discount time granting instruction in the discount time field included in the identified data record. The check-in processing unit 313 also adds the time registered in the discount time field to the planned room departure date and time included in the identified data record. Accordingly, the reception terminal 11 displays the planned room departure date and time, etc., to which discount time has been granted, on various screens.

[0370] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the granting of the above-mentioned service time will be described with reference to Fig. 37. Fig. 37 is a sequence diagram showing an example of the process relating to the granting of service time carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this process, it is assumed that the room details screen I is displayed on the display unit 116 of the reception terminal 11.

[0371] When the first cooperation processing unit 1103 of the reception terminal 11 receives an instruction to grant a service time by operating the service time button Icc or the like (ACT 121), the first cooperation processing unit 1103 displays the service time setting screen L on the display unit 116 (ACT 122).

[0372] The first collaboration processing unit 1103 receives a selection of the service time to be granted on the service time setting screen L (ACT123). Then, when an instruction to confirm the service time is given via the OK button Ld or the like, the first collaboration processing unit 1103 transmits a service time granting instruction including the store ID of its own store, the room ID of the karaoke booth, the service time to be granted, etc. to the infrastructure server 3 (ACT124).

[0373] When the check-in processing unit 313 of the infrastructure server 3 receives the service time granting instruction, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the service time granting instruction from the check-in management DB 336 (ACT 125). Next, the check-in processing unit 313 determines whether the reservation can be extended to the time specified in the service time granting instruction based on the reservation information and the like in the reservation management DB 337 associated with the same room ID (ACT 126).

[0374] Specifically, the check-in processing unit 313 determines whether the scheduled departure date and time plus the service time conflicts with the reservation date and time of the most recent reservation information associated with the same karaoke booth. If there is no conflict, the check-in processing unit 313 determines that the extension is possible, and if there is conflict, the check-in processing unit 313 determines that the extension is not possible.

[0375] If it is determined that the extension is possible, the check-in processing unit 313 of the infrastructure server 3 registers the time specified in the service time grant instruction in the service time field included in the identified data record (ACT 127). The check-in processing unit 313 also updates the planned leaving date and time included in the identified data record by adding the time registered in the service time field to the planned leaving date and time (ACT 128). Next, the check-in processing unit 313 cooperates with the notification processing unit 318 to transmit support information reflecting the registered content to the reception terminal 11 (ACT 129).

[0376] The first cooperation processing unit 1103 of the reception terminal 11 updates the room details screen I etc. based on the support information provided from the infrastructure server 3, thereby displaying a screen that reflects the registered contents (ACT130).

[0377] Furthermore, when the check-in processing unit 313 of the infrastructure server 3 determines that the extension is not possible, it cooperates with the notification processing unit 318 to send response information including the reason why the extension is not possible to the reception terminal 11 (ACT131). In this case, the first cooperation processing unit 1103 of the reception terminal 11 displays the reason why the extension is not possible based on the response information provided from the infrastructure server 3 (ACT132). This allows the operator of the reception terminal 11 to easily review the service time to be granted based on the displayed reason why the extension is not possible.

[0378] In this process, the determination of whether or not the service time can be extended is made after an operation to confirm the service time is performed on the reception terminal 11, but the timing of the determination of whether or not the service time can be extended is not limited to this. For example, the determination of whether or not the service time can be extended may be made when an operation to specify (select) the service time is performed on the service time setting screen L. Also, by providing a time button Lba within the range of the extendable time, the service time that can be specified on the service time setting screen L may be limited to the range of the extendable time. In this process, the determination of whether or not the service time can be extended is made by the check-in processing unit 313 of the infrastructure server 3, but it may also be configured so that the first cooperation processing unit 1103 of the reception terminal 11 makes the determination.

[0379] 29, the slip print button Icd in the operator field Ic is an operator that instructs printing of a slip. When the first cooperation processing unit 1103 accepts operation of the slip print button Icd, it cooperates with the infrastructure server 3 to cause the printing unit 119 to print a slip related to the use of the room ID of the karaoke booth that was the target of the operation. Specifically, when the first cooperation processing unit 1103 accepts operation of the slip print button Icd, it sends to the infrastructure server 3 a slip number request that includes the store ID of its own store and the room ID of the karaoke booth that was the target of the operation.

[0380] In response to the slip number request, the check-in processing unit 313 of the infrastructure server 3 identifies a data record that meets the store ID and room ID conditions specified in the slip number request from the check-in management DB 336. Then, the check-in processing unit 313 sends the slip number included in the identified data record to the reception terminal 11 that sent the slip number request.

[0381] When the first linking processing unit 1103 of the reception terminal 11 receives the slip number from the infrastructure server 3 as a response to the slip number request, it controls the printing unit 119 to print a slip including the slip number. As mentioned above, since the slip is printed at check-in, operating the slip print button Icd means that the slip is to be reissued.

[0382] The OK button Ice in the operator column Ic is an operator for confirming various operations. For example, the OK button Ice is operated when confirming various operations performed on the room details screen I.

[0383] It is also possible to configure the configuration so that operations are not confirmed on sub-screens such as the mid-room exit screen J and the service time setting screen L that are displayed as derivatives of the room details screen I, but rather the operations performed on the sub-screens are confirmed by pressing the OK button Ice on the room details screen I. In this case, it is preferable that when the OK button on each sub-screen is pressed, the room details screen I is displayed, clearly indicating the changes made on that sub-screen, and the changes are confirmed by pressing the OK button Ice on the room details screen I.

[0384] 26, the complaint registration button Gc on the in-room selection screen G is an operator for instructing the user to register a complaint such as an opinion or request received from a user of the karaoke booth. When the first cooperation processing unit 1103 receives an operation of the complaint registration button Gc, it causes the display unit 116 to display a complaint registration screen on which the user can register the content of the complaint.

[0385] Fig. 38 is a diagram showing an example of a complaint registration screen displayed on the reception terminal 11. As shown in Fig. 38, the complaint registration screen M has a complaint content field Ma, a comment field Mb, a back button Mc, and an OK button Md.

[0386] The complaint content field Ma allows the user to input the content of the complaint received from the user. For example, the complaint content field Ma may be provided with an operator such as a pull-down menu that allows the user to select one complaint content from a plurality of pre-set types of complaint content. When the operator selects one complaint content from the plurality of types of complaint content, the selected complaint content is entered into the complaint content field Ma.

[0387] Any character string can be entered into the comment field Mb. For example, the operator enters comments such as details of a complaint received from a user or information to be communicated to other employees into the comment field Mb.

[0388] The back button Mc is an operator that instructs returning to the original screen. When the back button Mc is operated, the first cooperation processor 1103 cooperates with the infrastructure server 3 to display the original screen.

[0389] The OK button Md is an operator that instructs the confirmation of the information entered on the complaint registration screen M. When the OK button Md is operated, the first collaboration processing unit 1103 transmits to the infrastructure server 3 a complaint registration instruction that includes the store ID of the store itself, the room ID of the karaoke booth that is the target of the operation, the complaint content and comments entered on the complaint registration screen M, etc. Note that the first collaboration processing unit 1103 may also include the employee ID of the operator in the complaint registration instruction and transmit it to the infrastructure server 3.

[0390] In response to the complaint registration instruction, the complaint processing unit 315 of the infrastructure server 3 identifies a data record that meets the store ID and room ID conditions specified in the complaint registration instruction from the check-in management DB 336. Then, the complaint processing unit 315 stores the complaint details and comments specified in the complaint registration instruction, the date and time when the complaint registration instruction was received, and other information in association with each other in the complaint information field included in the identified data record.

[0391] Furthermore, the complaint processing unit 315 of the infrastructure server 3 sends a complaint acceptance notification including the room ID, complaint details, comments, etc. specified in the complaint registration instruction to the clerk terminal 14 associated with the store having the store ID specified in the complaint registration instruction. As a result, the content of the complaint accepted from the user is notified to the store employee in real time.

[0392] It should be noted that the information displayed on the complaint registration screen M is not limited to the example screen shown in FIG. 38. For example, when existing complaint details are registered in the complaint information, the first collaboration processing unit 1103 may collaborate with the infrastructure server 3 to display the complaint details, the registration date and time, comment details, etc. together. In this case, a configuration may be adopted in which new comments such as "the complaint has been handled" can be added to the existing complaint details, and the new comments may be displayed together with the employee ID of the added employee. This allows the user to easily check the existing complaint details and the handling status, thereby improving convenience.

[0393] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the above-mentioned complaint registration will be described with reference to Fig. 39. Fig. 39 is a sequence diagram showing an example of the processing relating to the complaint registration carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this processing, it is assumed that the in-room selection screen G is displayed on the display unit 116 of the reception terminal 11.

[0394] When the first collaboration processing unit 1103 of the reception terminal 11 receives an instruction to register a complaint by operating the complaint registration button Gc or the like (ACT141), it displays the complaint registration screen M on the display unit 116, where the complaint details can be entered (ACT142).

[0395] The first collaboration processing unit 1103 accepts input of the complaint content and comments on the complaint registration screen M (ACT143). Then, when an instruction to confirm the complaint content is given via the OK button Md or the like, the first collaboration processing unit 1103 transmits a complaint registration instruction including the store ID of its own store, the room ID of the karaoke booth, the input complaint content, etc. to the infrastructure server 3 (ACT144).

[0396] When the complaint processing unit 315 of the infrastructure server 3 receives the complaint registration instruction, it identifies a data entry corresponding to the combination of the store ID and room ID specified in the complaint registration instruction from the check-in management DB 336 (ACT145). Next, the complaint processing unit 315 registers the complaint content, etc. specified in the complaint registration instruction in the complaint information field of the identified data entry (ACT146).

[0397] In addition, the complaint processing unit 315 of the infrastructure server 3 sends a complaint acceptance notification including the room ID and complaint content specified in the complaint registration instruction to the clerk terminal 14 belonging to the store ID specified in the complaint registration instruction (ACT147).

[0398] Meanwhile, when the processor of the clerk terminal 14 receives a complaint acceptance notification from the base server 3, it displays a screen showing the room ID and the complaint details (hereinafter also referred to as the complaint acceptance screen) on the display unit based on the information contained in the complaint acceptance notification (ACT148).

[0399] Fig. 40 is a diagram showing an example of a complaint reception screen displayed on the staff terminal 14. As shown in Fig. 40, the complaint reception screen N displays a message informing that a complaint has been registered, as well as the room ID "Room No. X" in which the complaint has been registered and the content of the complaint "Delay in serving food."

[0400] This allows the employee carrying the clerk terminal 14 to easily check the karaoke booth where the complaint has been registered and the registered complaint details by looking at the complaint reception screen, allowing the employee to quickly respond to the complaint.

[0401] The destination of the complaint receipt notification is not limited to the staff terminal 14. The complaint processing unit 315 may also switch the destination device depending on the content of the complaint. For example, if the content of the complaint is about a delay in providing the ordered product (food or drink), the complaint processing unit 315 may send the complaint receipt notification to the kitchen terminal 13. For example, if the content of the complaint is about a malfunction of karaoke equipment or the like, the complaint processing unit 315 may send the complaint receipt notification to the staff terminal 14.

[0402] In this way, by switching the device to which the message is sent depending on the content of the complaint, employees can smoothly respond to the complaint, thereby making the operation of the karaoke booth more efficient.

[0403] 26, the room transfer button Gd on the currently-entered room selection screen G is an operator that is operated when transferring a user currently using a karaoke booth to another karaoke booth. When the first collaboration processing unit 1103 receives an operation of the room transfer button Gd, it causes the display unit 116 to display a destination selection screen that allows the user to specify the destination karaoke booth. For example, the first collaboration processing unit 1103 causes the display unit 116 to display the destination selection screen shown in FIG. 41.

[0404] Fig. 41 is a diagram showing an example of a destination selection screen displayed on the reception terminal 11. As shown in Fig. 41, the destination selection screen O has the same screen configuration as the room list screen B. Also, on the destination selection screen O, the room button Bc of the karaoke booth in the "vacant" state is enabled so that it can be selected.

[0405] On the destination selection screen O, the operator selects a destination room button Bc from the selectable room buttons Bc displayed. When the first collaboration processor 1103 accepts the selection of the destination room button Bc, it transmits a room transfer instruction to the infrastructure server 3, including the store ID of the store itself, the room ID of the karaoke booth from which the user is to move, and the room ID of the karaoke booth to which the user is to move.

[0406] In response to the room transfer instruction, the check-in processing unit 313 of the infrastructure server 3 identifies a data record that meets the conditions of the specified store ID and source room ID from the check-in management DB 336. Then, the check-in processing unit 313 changes the room ID included in the identified data record to the destination room ID specified in the room transfer instruction. As a result, the karaoke booth is moved, and the room list screen B after the move is displayed on the display unit 116 of the reception terminal 11.

[0407] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the above-mentioned karaoke booth room change will be described with reference to Fig. 42. Fig. 42 is a sequence diagram showing an example of the process relating to the karaoke booth room change carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this process, it is assumed that the currently-entered room selection screen G is displayed on the display unit 116 of the reception terminal 11.

[0408] When the first collaboration processing unit 1103 of the reception terminal 11 receives an operation to instruct a karaoke booth room change by operating the room change button Gd or the like (ACT151), it displays a destination selection screen O on the display unit 116, which allows the user to select the karaoke booth to which the user is to move (ACT152).

[0409] When the first collaboration processing unit 1103 receives the selection of the destination karaoke box on the destination selection screen O (ACT153), it sends a room transfer instruction to the infrastructure server 3 including the store ID of its own store, the room ID of the karaoke box from which the user is being moved, and the room ID of the karaoke box to which the user is being moved (ACT154).

[0410] When the check-in processing unit 313 of the infrastructure server 3 receives the room transfer instruction, it identifies a data entry corresponding to the combination of the store ID and the room ID of the transfer source specified in the room transfer instruction from the check-in management DB 336 (ACT155). Next, the check-in processing unit 313 determines whether or not the transfer to the room ID of the transfer destination is possible based on the basic information in the basic information DB 334 associated with the room ID of the transfer destination, the reservation information in the reservation management DB 337 associated with the room ID of the transfer destination, etc. (ACT156).

[0411] For example, the check-in processing unit 313 determines whether or not the transfer is possible by comparing the number of users of the source karaoke box with the minimum and maximum occupancies of the destination karaoke box. Here, the check-in processing unit 313 determines that the transfer is possible if the number of users of the source karaoke box is equal to or greater than the minimum occupancy but less than the maximum occupancy of the destination karaoke box. Also, the check-in processing unit 313 determines that the transfer is not possible if the number of users of the source karaoke box is less than the minimum occupancy or exceeds the maximum occupancy of the destination karaoke box.

[0412] For example, the check-in processing unit 313 determines whether or not the user is allowed to move by comparing the scheduled departure date and time of the user using the karaoke booth from which the user is moving with the most recent reservation date and time set for the karaoke booth at the destination. Here, the check-in processing unit 313 determines that the user is allowed to move if the scheduled departure date and time of the user does not conflict with the reservation date and time of the karaoke booth at the destination, and determines that the user is not allowed to move if they conflict.

[0413] The check-in processing unit 313 determines whether or not the move is possible based on either or both of the number of users and the scheduled date and time of departure, and if it determines that the move is possible, changes the room ID included in the data entry identified from the check-in management DB 336 to the room ID of the move destination (ACT 157). Next, the check-in processing unit 313 cooperates with the notification processing unit 318 to transmit support information reflecting the changed content to the reception terminal 11 (ACT 158).

[0414] The first cooperation processing unit 1103 of the reception terminal 11 updates the room details screen I etc. based on the support information provided from the infrastructure server 3, and displays a screen reflecting the changes (ACT 159).

[0415] Furthermore, when the check-in processing unit 313 of the infrastructure server 3 determines that the movement is not possible, it cooperates with the information providing unit 317 to transmit response information including the reason why the movement is not possible to the reception terminal 11 (ACT160).

[0416] In this case, the first cooperation processing unit 1103 of the reception terminal 11 displays the reason for the impossibility of the move, etc., based on the response information provided from the infrastructure server 3 (ACT161). This allows the operator of the reception terminal 11 to easily review the karaoke booth to be the destination, etc., based on the displayed reason for the impossibility of the move.

[0417] In this process, the determination as to whether or not the move is possible is made after the karaoke booth to which the user is to move is specified in the infrastructure server 3, but the timing of the determination as to whether or not the move is possible is not limited to this. For example, the determination as to whether or not the move is possible may be made when an operation to specify (select) the karaoke booth to which the user is to move is performed on the destination selection screen O.

[0418] Additionally, on the destination selection screen O, the room buttons Bc of karaoke booths that can be moved to may be enabled to be selectable. In this case, in addition to the "vacant" condition, for example, room buttons Bc of karaoke booths that have no reservations, or even if there are reservations, the reservation date and time does not interfere with the scheduled departure time of the karaoke booth from which the user is moved, may be enabled. Also, in addition to the "vacant" condition, room buttons Bc of karaoke booths that can accommodate the number of users of the karaoke booth from which the user is moved may be enabled.

[0419] In addition, in this process, the determination of whether or not the movement is permitted is made by the check-in processing unit 313 of the infrastructure server 3, but it may be configured such that the first cooperation processing unit 1103 of the reception terminal 11 makes this determination.

[0420] Returning to FIG. 26, the checkout button Ge on the in-room selection screen G is an operator that is operated when a user who has used the karaoke booth checks out, that is, when checking out. For example, the checkout button Ge is operated when checking out. Note that if the reception terminal 11 and the checkout terminal are provided separately, the checkout button Ge may be disabled on the reception terminal 11 by not displaying it, and the checkout button Ge may be operated on the checkout terminal.

[0421] When the first linkage processing unit 1103 of the reception terminal 11 accepts operation of the checkout button Ge, it activates the reading unit 118 and waits until the slip number is read by the reading unit 118. The operator of the reception terminal 11 causes the reading unit 118 to read, for example, a code symbol printed on the slip of the user checking out. When the first linkage processing unit 1103 obtains the slip number via the reading unit 118, it sends a checkout request including this slip number to the infrastructure server 3.

[0422] When the checkout processing unit 316 of the infrastructure server 3 receives a checkout request, it identifies the data record corresponding to the slip number specified in the checkout request from the user management DB. Next, the checkout processing unit 316 registers the current date and time as the exit date and time included in the identified data entry, and calculates the usage time from the entry date and time to the exit date and time.

[0423] Next, the checkout processing unit 316 of the infrastructure server 3 calculates the usage fee for the karaoke box based on the calculated usage time, the room course and number of users included in the identified data record, the attributes of each user (age category, presence or absence of membership ID, etc.), options, order information, service time, etc. Note that the checkout processing unit 316 excludes users whose entry / exit status is "Entry canceled" and whose payment completion flag is "Payment completed" from the calculation of the usage fee.

[0424] Then, the checkout processing unit 316 of the infrastructure server 3 works in cooperation with the information providing unit 317 to send detail data including the amount used and details related to the calculation of the amount used to the reception terminal 11 that sent the checkout request.

[0425] When the first cooperation processing unit 1103 of the reception terminal 11 receives the detailed data from the infrastructure server 3, it causes the display unit 116 to display an accounting screen for accounting the amount of the transaction based on the detailed data.

[0426] Figure 43 is a diagram showing an example of a checkout screen displayed on the reception terminal 11. As shown in Figure 43, the checkout screen P has a details display field Pa, a subtotal display field Pb, a discount amount display field Pc, a total display field Pd, a payment method selection field Pe, and an operator field Pf.

[0427] The details display field Pa displays details related to the calculation of the usage amount. The subtotal display field Pb displays the usage amount before the discount as the subtotal amount. The discount amount display field Pc displays details related to the discount amount. The total display field Pd displays the amount remaining after subtracting the discount amount from the subtotal amount as the total amount. The total display field Pd also displays the usage amount for each user. For example, the total display field Pd displays the amount obtained by dividing the total amount by the number of users as the usage amount per person.

[0428] The payment method selection field Pe displays payment method buttons Pea representing various payment methods. For example, payment methods such as cash, credit, electronic money, code payment, and gift certificates are displayed as payment method buttons Pea. The operator selects the payment method notified by the user via the payment method button Pea.

[0429] The operator field Pf is provided with various operators, such as a back button Pfa, a coupon button Pfb, and an order details button Pfc.

[0430] The back button Pfa is an operator for instructing to return to the transition source screen. When the back button Pfa is operated, the first cooperation processor 1103 displays the transition source screen.

[0431] The coupon button Pfb is an operator for inputting coupon information for a coupon held by the user. A coupon is a ticket distributed to a user in advance for receiving a discount (or discount) service. For example, a coupon holds coupon information in the form of a code symbol or the like that can identify the discount amount. Coupons may be distributed electronically or on paper. In the former case, the coupon information is registered in the member management DB 332, for example, in association with a member ID.

[0432] When the coupon button Pfb is operated, the first cooperation processing unit 1103 of the reception terminal 11 executes a process for accepting input of coupon information for a coupon held by the user. When the first cooperation processing unit 1103 accepts input of a coupon number, it reflects the amount of discount provided by the coupon information in the discount amount display field Pc and updates the total display field Pd.

[0433] For example, if coupon information is distributed electronically, the first collaboration processing unit 1103 acquires coupon information associated with the user's member ID from the member management DB by collaborating with the information provider 317 of the infrastructure server 3. Then, the first collaboration processing unit 1103 displays a screen (not shown) that displays a list of the acquired coupon information, and accepts input of coupon information selected from the screen.

[0434] The first link processing unit 1103 may acquire coupon information associated with the member ID of one member such as a representative member, or may acquire coupon information associated with the member IDs of all members included in the user. Also, when accounting is performed for each user and the user is a member, the first link processing unit 1103 may acquire coupon information associated with the member ID of that member.

[0435] Furthermore, for example, when coupon information is distributed in the form of a paper medium, the first cooperation processing unit 1103 enables the reading unit 118 and receives input of the coupon information via the reading unit 118.

[0436] The Order Details button Pfc is an operator operated when a user wants to display and edit the details of the items ordered. When the Order Details button Pfc is operated, the first collaboration processor 1103 of the reception terminal 11 collaborates with the information provider 317 of the infrastructure server 3 to obtain order information associated with the slip number from the user management DB. The first collaboration processor 1103 then displays a screen (not shown) showing the details of the obtained order information. For example, the first collaboration processor 1103 displays an area showing the details of the order information and an area showing the product menu on the same screen, thereby displaying a screen on which the order details can be displayed and additional products can be registered. When editing operations such as changing the quantity of ordered items, adding or deleting products are performed on this screen, the first collaboration processor 1103 updates the subtotal display field Pb and the total display field Pd according to the content of the editing operation.

[0437] On the above-mentioned accounting screen P, when the first linkage processing unit 1103 of the reception terminal 11 accepts the selection of one payment method button Pea from the payment method selection field Pe, it performs accounting for the usage fee using the payment method selected from the payment method button Pea. Specifically, the first linkage processing unit 1103 of the reception terminal 11 performs accounting to pay the total amount displayed in the total display field Pd using the payment method selected from the payment method button Pea. Then, when the accounting is complete, the first linkage processing unit 1103 sends an accounting completion notice to the infrastructure server 3, including the slip number of the transaction that was the subject of the processing.

[0438] The first cooperation processing unit 1103 may perform accounting processing for each user. For example, the first cooperation processing unit 1103 may be configured to accept a payment method selection operation for each user and perform individual accounting processing using the selected payment method.

[0439] When the checkout processing unit 316 of the infrastructure server 3 receives the transaction completion notice, it identifies the data entry corresponding to the slip number indicated in the transaction completion notice from the check-in management DB 336 and sets the transaction completion flag for each user included in that data entry to transaction completion.The checkout processing unit 316 then removes the identified data entry from the check-in management DB 336 by, for example, moving it to another DB.

[0440] Here, an example of the operation of the infrastructure server 3 and reception terminal 11 relating to the above-mentioned checkout process will be described with reference to Fig. 44. Fig. 44 is a sequence diagram showing an example of the checkout process carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this process, it is assumed that the entry selection screen G is displayed on the display unit 116 of the reception terminal 11.

[0441] When the first cooperation processing unit 1103 of the reception terminal 11 receives an instruction to check out by operating the checkout button Ge or the like (ACT171), it reads the slip number via the reading unit 118 (ACT172). Next, the first cooperation processing unit 1103 sends a checkout request including the read slip number to the infrastructure server 3 (ACT173).

[0442] When the check-out processing unit 316 of the infrastructure server 3 receives the check-out request, it identifies the data record corresponding to the slip number specified in the check-out request from the user management DB (ACT 174). Next, the check-out processing unit 316 calculates the usage time from the entry date and time included in the identified data entry to the current date and time (exit date and time) (ACT 175).

[0443] Next, the checkout processing unit 316 of the infrastructure server 3 calculates the usage fee for the karaoke booth based on various information included in the identified data entry, the calculated usage time, etc. (ACT176). Next, the checkout processing unit 316 transmits detailed data including the usage fee, etc. to the reception terminal 11 (ACT177).

[0444] When the first linkage processing unit 1103 of the reception terminal 11 receives the statement data from the infrastructure server 3 in response to the checkout request, it displays the accounting screen P on the display unit 116 based on the statement data (ACT178). Next, when the first linkage processing unit 1103 accepts the selection of a payment method for the usage amount on the accounting screen P (ACT179), it executes accounting processing for the usage amount using the selected payment method (ACT180). Then, when the accounting processing is completed, it sends an accounting completion notification including the slip number read earlier to the infrastructure server 3 (ACT181).

[0445] When the checkout processing unit 316 of the infrastructure server 3 receives the transaction completion notice, it identifies the data entry corresponding to the slip number indicated in the transaction completion notice from the check-in management DB 336 (ACT182). Next, the checkout processing unit 316 sets the transaction completion flag for each user included in the identified data entry to transaction completion, and then removes the data entry from the check-in management DB 336 (ACT183).

[0446] In response to ACT173, the status management unit 311 of the infrastructure server 3 changes the status of the status management DB 335 corresponding to the room ID of the data entry removed from the check-in management DB 336 from "occupied" to "waiting for cleaning" (ACT184). In addition, the status management unit 311 registers the operation history of the karaoke booth whose status has been changed in the operation history DB 338 (ACT185).

[0447] As a result, karaoke booths that have transitioned to a waiting state for cleaning are identifiable and displayed on the reception terminal 11. Therefore, the operator of the reception terminal 11 can easily check the karaoke booths that are waiting for cleaning from the room list screen or the like.

[0448] In the above-described checkout process, the accounting process is performed when all users leave the karaoke booth, but this is not limited to this. When some users leave the booth midway, the accounting process may be performed individually for those users. In this case, for example, by providing an "account midway" button or the like in the operator field Jb of the above-described "leave midway" screen J, the accounting may be performed at the user's request when they leave midway.

[0449] When a mid-transit payment button is provided, the first cooperation processing unit 1103 of the reception terminal 11 performs the following process, for example, to individually process payments for users who leave mid-transit.

[0450] First, when the first collaboration processing unit 1103 receives an operation of the mid-checkout button on the mid-checkout screen J, it sends a mid-checkout instruction including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, the user identifier of the user who is leaving the room, etc. to the infrastructure server 3. Note that if the user who is leaving the room presents a receipt, the first collaboration processing unit 1103 may also send a mid-checkout instruction to the infrastructure server 3 including the receipt number obtained from the receipt and the user identifier of the user who is leaving the room, etc.

[0451] When the checkout processing unit 316 of the infrastructure server 3 receives the mid-checkout instruction, it identifies a data record in the user management DB that corresponds to the conditions specified in the mid-checkout instruction. Next, the check-in processing unit 313 calculates the usage fee for the user who will be leaving the room early, based on various information such as the room course included in the identified data entry, the usage time of the user identifier specified in the mid-checkout instruction, attributes (age category, presence or absence of membership ID, etc.), and options. Then, in cooperation with the information providing unit 317, the checkout processing unit 316 sends detailed data including the usage fee for the user who will be leaving the room early to the reception terminal 11 that sent the mid-checkout instruction.

[0452] When the first collaboration processing unit 1103 of the reception terminal 11 receives the transaction data, it displays the accounting screen P similar to that shown in Figure 43 on the display unit 116 based on the transaction data and executes the accounting process. Then, when the first collaboration processing unit 1103 of the reception terminal 11 completes the accounting process for the user who is leaving midway, it sends an interim accounting completion notice to the infrastructure server 3, which includes the store ID of its own store and the room ID (or slip number) of the karaoke booth being operated, the user identifier of the user who is leaving midway, etc.

[0453] When the checkout processing unit 316 of the infrastructure server 3 receives the interim transaction completion notification from the reception terminal 11, it identifies the data entry corresponding to the conditions specified in the interim transaction completion notification from the check-in management DB 336. The checkout processing unit 316 then sets the transaction completion flag for the user identifier specified in the interim transaction completion notification to transaction completion.

[0454] This allows the establishment to process the bill for each user who leaves the karaoke booth separately. Therefore, the facility management system 100 can improve the convenience of using and managing karaoke booths.

[0455] 14, the description of the room list screen B will continue. When the first collaboration processor 1103 receives an operation on a room button Bc in the “Waiting for cleaning” state on the room list screen B, it displays a cleaning start screen that allows an instruction to start cleaning.

[0456] Fig. 45 is a diagram showing an example of a cleaning start screen displayed on the reception terminal 11. As shown in Fig. 45, the cleaning start screen Q has a back button Qa and a cleaning start button Qb that instructs the user to start cleaning. The back button Qa is an operator that instructs the user to return to the screen from which the user transitioned. When the back button Qa is operated, the first cooperation processor 1103 displays the screen from which the user transitioned.

[0457] The cleaning start button Qb is an operator that instructs the start of cleaning. When the first collaboration processing unit 1103 receives an operation of the cleaning start button Qb, it transmits a cleaning start notification including the store ID of the store itself, the room ID of the karaoke booth that was the target of the operation, etc. to the infrastructure server 3. The first collaboration processing unit 1103 may also include the employee ID of the operator in the cleaning start notification and transmit it to the infrastructure server 3.

[0458] When the status management unit 311 of the infrastructure server 3 receives the cleaning start notification, it identifies a data entry corresponding to the store ID and room ID specified in the cleaning start notification from the status management DB 335. Next, the status management unit 311 switches the room status of the identified data entry from "waiting for cleaning" to "cleaning in progress." In addition, the status management unit 311 registers the operation history of the karaoke booth whose status has been switched in the operation history DB 338.

[0459] Furthermore, on the room list screen B of FIG. 12, when the first cooperation processor 1103 receives an operation on the room button Bc in the "cleaning" state, it displays, for example, a cleaning completion screen having an operator for instructing completion of cleaning.

[0460] Fig. 46 is a diagram showing an example of a cleaning completion screen displayed on the reception terminal 11. As shown in Fig. 46, the cleaning completion screen R has a back button Ra and a cleaning completion button Rb that instructs completion of cleaning. The back button Ra is an operator that instructs returning to the original screen. When the back button Ra is operated, the first cooperation processor 1103 displays the original screen.

[0461] The cleaning completion button Rb is an operator that instructs the completion of cleaning. When the first collaboration processor 1103 receives an operation of the cleaning completion button Rb, it transmits a cleaning completion notification to the infrastructure server 3, including the store ID of the store itself and the room ID of the karaoke booth that was the target of the operation. The first collaboration processor 1103 may also include the employee ID of the operator in the cleaning completion notification and transmit it to the infrastructure server 3.

[0462] When the status management unit 311 of the infrastructure server 3 receives the cleaning completion notification, it identifies a data entry corresponding to the store ID and room ID specified in the cleaning completion notification from the status management DB 335. Next, the status management unit 311 changes the room status of the identified data entry from "cleaning in progress" to "vacant." In addition, the status management unit 311 registers the operation history of the karaoke booth whose status has been changed in the operation history DB 338.

[0463] Here, an example of the operation of the infrastructure server 3 and reception terminal 11 relating to cleaning management of karaoke booths will be described with reference to Fig. 47. Fig. 47 is a sequence diagram showing an example of processing relating to cleaning management carried out between the infrastructure server 3 and reception terminal 11. Note that, as a premise for this processing, it is assumed that the room list screen B is displayed on the display unit 116 of the reception terminal 11.

[0464] When the first collaboration processing unit 1103 of the reception terminal 11 accepts operation of the room button Bc in the "waiting for cleaning" state (ACT191), it displays the cleaning start screen Q on the display unit 116 (ACT192). When the first collaboration processing unit 1103 accepts an instruction to start cleaning by operation of the cleaning start button Qb or the like (ACT193), it transmits a cleaning start notification including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, etc. to the infrastructure server 3 (ACT194).

[0465] When the status management unit 311 of the infrastructure server 3 receives the cleaning start notification, it switches the status of the status management DB 335 corresponding to the room ID instructed in the cleaning start notification from "waiting for cleaning" to "cleaning in progress" (ACT 195). In addition, the status management unit 311 registers the operation record of the karaoke booth whose status has been switched in the operation record DB 338 (ACT 196).

[0466] As a result, the karaoke booths that have transitioned to the cleaning in progress state are identifiable and displayed on the reception terminal 11. Therefore, the operator of the reception terminal 11 can easily check the karaoke booths that are in the cleaning in progress state from the room list screen B, etc.

[0467] Furthermore, when the first cooperation processing unit 1103 of the reception terminal 11 accepts operation of the room button Bc in the "cleaning" state (ACT197), it displays the cleaning completion screen R on the display unit 116 (ACT198). When the first cooperation processing unit 1103 accepts an instruction to complete cleaning by operating the cleaning completion button Rb or the like (ACT199), it sends a cleaning completion notification including the store ID of its own store, the room ID of the karaoke booth that was the target of the operation, etc. to the infrastructure server 3 (ACT200).

[0468] When the status management unit 311 of the infrastructure server 3 receives the cleaning completion notification, it changes the status of the status management DB 335 corresponding to the room ID specified in the cleaning completion notification from "cleaning" to "vacant" (ACT201). In addition, the status management unit 311 registers the operation record of the karaoke booth whose status has been changed in the operation record DB 338 (ACT202).

[0469] As a result, karaoke booths that have become vacant are identifiable and displayed on the reception terminal 11. Therefore, the operator of the reception terminal 11 can easily check vacant karaoke booths from the room list screen B, etc.

[0470] Returning to FIG. 13, the operation when another tab operator is operated from operation screen A will be described.

[0471] Tab Abb on operation screen A is an operator operated to check the operating status of each karaoke booth installed in the store. When the first cooperation processing unit 1103 of the reception terminal 11 accepts the operation of tab Abb, it transmits an operating status request including the store ID of the store to the infrastructure server 3.

[0472] When the information provider 317 of the infrastructure server 3 receives an operation status request from the reception terminal 11, it reads data entries related to the store ID specified in the operation status request from the status management DB 335, the operation record management DB, etc. The information provider 317 generates support information representing the operation status of each room ID based on the read data entries. For example, the information provider 317 generates support information representing the state transitions of the karaoke booths in chronological order based on records related to the current and past state transitions of the karaoke booths stored in the status management DB 335 and the operation record management DB. The information provider 317 then provides the generated support information to the reception terminal 11 that sent the operation status request.

[0473] When the first collaboration processing unit 1103 of the reception terminal 11 receives support information from the infrastructure server 3 in response to the operation status request, it displays an operation status screen showing the operation status of each karaoke booth installed in its own store on the display unit 116 (display area Ac) based on the support information.

[0474] Fig. 48 is a diagram showing an example of an operation status screen displayed on the reception terminal 11. As shown in Fig. 48, the operation status screen S has an operator field Sa and an operation status field Sb.

[0475] The operator field Sa displays various operators related to display control of the operating status. For example, the operator field Sa is provided with a first operator Saa for specifying the order (display order) of the karaoke booths to be displayed in the operating status field Sb, a second operator Sab for specifying the conditions for narrowing down the karaoke booths to be displayed in the operating status field Sb, etc.

[0476] The first operator Saa and the second operator Sab can change the order of room IDs to be displayed by combining, for example, the order of room IDs (room numbers), the order of expected exit times, the order of maximum occupancy (or minimum occupancy), etc. Furthermore, the first operator Saa and the second operator Sab can change the order of room IDs to be displayed depending on the status of the displayed object, such as "entering the room" or "cleaning in progress." Furthermore, via the first operator Saa and the second operator Sab, etc., it may be possible to narrow down the display to specific statuses, such as the statuses in which the karaoke booth is unavailable ("waiting for cleaning," "cleaning in progress," and "out of order").

[0477] The operation status column Sb displays information indicating the operation status of the karaoke booth. For example, the operation status column Sb displays the time-series status transition status of the corresponding room ID in a graph format such as a Gantt chart, in association with the room ID and the model name of the karaoke equipment installed in that room ID. Here, the number in parentheses displayed in association with the room ID indicates the maximum capacity of the karaoke booth corresponding to that room ID. The model name and maximum capacity of the karaoke equipment can be obtained from the basic information DB 334.

[0478] The operation status field Sb in Figure 48 shows an example of a display when "room number" is set with the first operator Saa and "occupied" is set with the second operator Sab. In this case, the operation status field Sb displays, for example, the current and past usage times of each room ID that is currently in the "occupied" state on a time axis using a period bar Sba that represents that period. The time displayed in association with the period bar Sba indicates the time from the start date and time to the end date and time, or from the start date and time to the scheduled date and time of use.

[0479] This allows the operator of the reception terminal 11 to easily check the operating status of each karaoke booth installed in his / her store, that is, the actual usage time of each karaoke booth and its usage status, by looking at the operating status screen S.

[0480] The time axis range displayed in the operation status field Sb is set based on the current date and time, but it is preferable to make it changeable in response to an operation by the operator. The operation status field Sb is not limited to displaying both the current and past operation statuses, and may display either the current or past operation statuses. Furthermore, by using the reservation management DB 337, the status of the reservation dates and times registered in each karaoke booth may be displayed individually or together.

[0481] Moreover, Fig. 49 is a diagram showing another example of the operation status screen displayed on the reception terminal 11. The operation status screen S in Fig. 49 shows a display example when "room number" is set with the first operator Saa, and "out of order" and "cleaning" are set with the second operator Sab.

[0482] In this case, the operating status column Sb highlights the room ID and graph in the "out of order" state, such as by graying out, so that the "out of order" state can be easily identified. Note that the character string such as "air conditioner" displayed in the graph indicates the reason for the outage that is stored in association with the room ID.

[0483] For room IDs that are in the "cleaning" state, a time bar Sba indicating the period during which cleaning was performed is displayed on the time axis. The time and name displayed in association with the time bar Sba indicate the period from the start date and time of cleaning to the date and time of completion, and the name of the employee in charge of cleaning.

[0484] This allows the operator of the reception terminal 11 to easily check the operating status of each karaoke booth installed in his / her store, i.e., which karaoke booths are out of order, the time required for cleaning and the person in charge, by looking at the operating status screen S.

[0485] Furthermore, the information representing the operating status of the karaoke booths is not limited to the forms shown in Figures 48 and 49. For example, the information provider 317 of the infrastructure server 3 may derive information for each karaoke booth, such as the exclusive time for each state during a predetermined period or the ratio obtained by dividing the exclusive time for each state by the predetermined time, and provide information for displaying the derived results to the reception terminal 11 as support information. In this case, the first collaboration processor 1103 of the reception terminal 11 may display, for example, a screen shown in Figure 50 (hereinafter also referred to as a room-by-room report screen) as the operating status.

[0486] FIG. 50 is a diagram showing an example of a room-by-room report screen displayed on the reception terminal 11. Note that there is no particular restriction on the method for displaying the room-by-room report screen. For example, the room-by-room report screen may be displayed by transitioning from the operation status screen S by performing a predetermined operation on the operation status screen S. Also, for example, a dedicated tab operator for displaying the room-by-room report screen may be provided on the operation screen A in FIG. 13.

[0487] As shown in Fig. 50, the room-by-room report screen T has an information display field Ta and an operation status field Tb. The information display field Ta displays items such as the store name, period, room number (room ID), etc. The store name displays the name of the store.

[0488] The period for which the operating status is to be derived is displayed in the period. The period and room number items can be edited via the operation unit 117. FIG. 50 shows an example in which April 1, 2023, in the past, is set as the period.

[0489] The room number displays the room ID of the karaoke booth for which the operating status is to be derived. The room number item can be edited via the operation unit 117. FIG. 50 shows an example in which karaoke booths with room IDs "1" and "2" are set as room numbers.

[0490] The operation status column Tb displays the exclusive time and percentage of each state during the predetermined period set in the period of the information display column Ta for each karaoke booth with the room ID set in the room number of the information display column Ta. Fig. 50 shows an example in which the exclusive time (operating time) and percentage (operating rate) of the "occupied" state and the exclusive time and percentage (outage rate) of the "out of order" state during the predetermined period set in the period Tab are displayed in association with the room ID and the name of the karaoke booth corresponding to that room ID.

[0491] The operating status field Tb also includes a total field that displays the total operating time, average operating rate, average failure rate, etc. for the room ID set in the room number in the information display field Ta.

[0492] As a result, by viewing the room-by-room report screen T, the operator of the reception terminal 11 can easily check the operating hours, operating rate, and failure rate of the karaoke booths for a predetermined period, and can grasp the operating status of the karaoke booths from multiple angles. For example, the operator of the reception terminal 11 can identify karaoke booths with high (or low) operating rates, or karaoke booths that frequently malfunction. Therefore, the facility management system 100 can efficiently support the operation of the karaoke booths.

[0493] The number of hours displayed in the operation status column Tb is not limited to the "occupied" state, but may also display the exclusive time for other states. Also, the percentage displayed in the operation status column Tb is not limited to the "occupied" and "out of order" states, but may also display the percentage for other states.

[0494] 48 to 50 show examples of the operation status of karaoke booths, but the operation status of employees belonging to the store may also be displayed. For example, the information provider 317 of the infrastructure server 3 may derive the time required to clean the karaoke booth for each employee ID based on the data in the operation record DB related to the store ID specified in the operation status request, and display a screen showing the derived information (hereinafter also referred to as a cleaning report screen by employee) as the operation status.

[0495] FIG. 51 is a diagram showing an example of a cleaning report screen by person in charge displayed on the reception terminal 11. Note that the method of displaying the cleaning report screen by person in charge U is not particularly limited. For example, the cleaning report screen by person in charge U may be displayed by performing a predetermined operation on the operation status screen S. Also, for example, a dedicated tab operator for displaying the cleaning report screen by person in charge U may be provided on the operation screen A in FIG. 13.

[0496] As shown in FIG. 51, the cleaning report screen U by staff member has an information display field Ua and an operation status field Ub. The information display field Ua displays items such as the store name, period, staff member, and room number. The store name Uaa displays the name of the store. The period displays the period for which the operation status is to be derived. The staff member displays the employee ID and name of the employee for whom the operation status is to be derived. The room number displays the room ID of the karaoke booth for which the operation status is to be derived.

[0497] It is assumed that the items of period, person in charge, and room number can be edited via the operation unit 117, etc. FIG. 51 shows an example in which April 1, 2023, in the past, is set as the period. Also shown is an example in which employees with the names "XX Taro" and "△△ Hanako" are set as the person in charge. Also shown is an example in which karaoke booths with room IDs "2" and "8" are set as the room numbers.

[0498] The operation status column Ub displays, for each employee whose employee ID is set as the person in charge in the information display column Ua, the cleaning results, such as the time required for cleaning the karaoke booths with the room numbers in the information display column Ua, during the period specified in the information display column Ua. Figure 51 shows an example in which, for each employee name, the room IDs, start times, end times, and cleaning times of the karaoke booths that the employee was responsible for are displayed in association with each employee name. Here, the start times and end times correspond to the disclosure date and time and end time recorded in the operation results with the status information "cleaning in progress." The cleaning time is information indicating the time from the start date and time to the completion date and time, and represents the work period required for the cleaning work.

[0499] Additionally, the operation status field Ub has a total field for each employee ID. The total field displays the total cleaning time and the average cleaning time.

[0500] As a result, by viewing the cleaning report screen U by individual employee, the operator of the reception terminal 11 can easily check the time required for cleaning the karaoke booths by employees over a specified period, the average time, etc., and can grasp the employee's operating status from multiple angles. For example, the operator of the reception terminal 11 can identify employees who require a long time for cleaning. Therefore, the facility management system 100 can efficiently support the operation of the karaoke booths.

[0501] Since cleaning time may depend on the size of the karaoke booth, information indicating the size of the karaoke booth (for example, maximum capacity) may be displayed in association with the room ID in the operation status column Ub.

[0502] Here, an example of the operation of the infrastructure server 3 and the reception terminal 11 relating to the display of the operating status will be described with reference to Fig. 52. Fig. 52 is a sequence diagram showing an example of the processing relating to the display of the operating status carried out between the infrastructure server 3 and the reception terminal 11. Note that, as a premise of this processing, it is assumed that the operation screen A is displayed on the display unit 116 of the reception terminal 11.

[0503] When an instruction to display the operation status is given by operating the tab Abb or the like, the first cooperation processing unit 1103 of the reception terminal 11 transmits an operation status request including the store ID of the own store to the infrastructure server 3 (ACT211).

[0504] When the information providing unit 317 of the infrastructure server 3 receives the operation status request, it references the status management DB 335 and the operation record DB related to the store ID specified in the operation status request, and sets data entries representing past and current operation records as the analysis target (ACT212). Next, the information providing unit 317 generates support information representing the operation status of the karaoke booth or employees based on the data entries to be analyzed (ACT213). Next, the information providing unit 317 provides the generated support information to the reception terminal 11 that sent the operation status request (ACT214).

[0505] When the first collaboration processing unit 1103 of the reception terminal 11 receives support information from the infrastructure server 3 in response to the operation status request, it displays a screen (operation status screen S, room-by-room report screen T, cleaning report screen U by person in charge, etc.) showing the operation status of the karaoke booth or employee based on the support information on the display unit 116 (ACT215).

[0506] Furthermore, when the first collaboration processing unit 1103 of the reception terminal 11 receives an operation to change the conditions of the operation status or elements to be displayed, it returns to ACT211 and transmits an operation status request including the conditions to the infrastructure server 3. Then, the first collaboration processing unit 1103 displays a screen showing the operation status in ACT215 based on the support information generated by the infrastructure server 3 according to the changed conditions.

[0507] This allows the operator of the reception terminal 11 to understand the operating status of the karaoke booths and employees in their own store from multiple angles based on the screen displaying the operating status. Therefore, the facility management system 100 can efficiently support the operation of the karaoke booths.

[0508] In the above description, the reception terminal 11 is linked to the infrastructure server 3 to display various screens, but this is not limiting, and for example, the external sales terminal 5 or the store clerk terminal 14 may be linked to the infrastructure server 3 to display the various screens described above. In addition, the screens that can be displayed and the range of operations that can be performed may be limited depending on the role of the terminal in the store, the authority of the employee operating it, etc.

[0509] [Linkage between infrastructure server and external sales terminal] Next, we will explain an example of the operation performed between the infrastructure server 3 and the sales terminal 5. The second collaboration processing unit 513 of the sales terminal 5 starts collaboration with the infrastructure server 3 by performing processing similar to the collaboration start processing described above with the infrastructure server 3.

[0510] Specifically, when the information providing unit 317 of the infrastructure server 3 has successfully authenticated the sales representative who will be the operator, it identifies the store ID of the store to which the employee ID specified in the login request belongs from the employee management DB. Next, the information providing unit 317 provides support information related to the identified store ID to the sales terminal 5 that sent the login request, based on various information stored in various DBs.

[0511] For example, the information providing unit 317 of the infrastructure server 3 provides support information capable of displaying the above-mentioned basic operation screen (room list screen) to the sales terminal 5. Note that if multiple store IDs are associated with an employee ID, the information providing unit 317 provides support information capable of switching store IDs and displaying them on the screen.

[0512] When support information is provided from the infrastructure server 3 following successful authentication, the second collaboration processing unit 513 of the sales terminal 5 displays various screens based on the support information on the display unit 116. For example, the second collaboration processing unit 513 of the sales terminal 5 displays the above-mentioned room list screen B, etc., based on the support information provided from the infrastructure server 3. The sales representative operating the sales terminal 5 can check the availability and reservation status of karaoke booths by looking at the room button Bc displayed on the room list screen B.

[0513] If multiple store IDs are associated with the employee ID of the sales representative, the second collaboration processing unit 513 of the sales terminal 5 switches the store ID to be displayed in response to an operation to switch the store ID. For example, when an operation to swipe the room list screen B left or right is performed, the second collaboration processing unit 513 of the sales terminal 5 determines that an operation to switch the store ID has been performed, and displays the room list screen B related to the switched store ID.

[0514] In addition, the second collaboration processing unit 513 of the sales terminal 5 collaborates with the infrastructure server 3 to provide a screen that allows the sales staff to reserve a room in a karaoke booth as a support screen for supporting their sales activities.

[0515] Specifically, when the second linkage processing unit 513 of the sales terminal 5 receives an operation of the room button Bc of a karaoke box that is in the "vacant" state from the room list screen B, it causes the display unit 116 to display a room reservation screen that allows the user to reserve the karaoke box corresponding to that room button Bc.

[0516] Fig. 53 is a diagram showing an example of a room reservation screen displayed on the sales terminal 5. As shown in Fig. 53, the room reservation screen V has a reservation information field Va and an operator field Vb.

[0517] The reservation information field Va has fields such as a usage start time field Vaa, a usage duration field Vab, a desired price field Vac, a desired number of people field Vad, and a comment field Vae. The usage start time field Vaa is entered with the usage start time of the user attracted by the sales representative. The usage duration field Vab is entered with the planned usage time of the user attracted by the sales representative. The desired price field Vac is entered with the planned price for using the karaoke box desired by the user attracted by the sales representative. The desired number of people field Vad is entered with the number of users (number of people making a reservation) attracted by the sales representative.

[0518] Any string of characters can be entered in the comment field Vae. The salesperson can enter comments such as their employee ID, important information about the customer, or messages to store employees (such as requests for discounts or free time).

[0519] The operator field Vb is provided with various operators. For example, the operator field Vb is provided with a back button Vba, a room reservation button Vbb, etc. The back button Vba is an operator that instructs returning to the original screen. When the back button Vba is operated, the second link processing unit 513 displays the original screen.

[0520] The room reservation button Vbb is an operator that instructs the confirmation of the information entered in the reservation information field Va. When the room reservation button Vbb is operated, the second collaboration processor 513 sends a room reservation request including the store ID and room ID targeted by the operation, and the various information entered in the reservation information field Va, to the infrastructure server 3. The second collaboration processor 513 may also include the employee ID of the operator in the room reservation request before sending it.

[0521] When the reservation management unit 312 of the infrastructure server 3 receives a room reservation request from the external sales terminal 5, it associates the store ID and room ID specified in the room reservation request with various information and stores them in the reservation management DB 337. Specifically, the reservation management unit 312 stores information such as the start time of use, the duration of use, and the number of people making the reservation in the reservation information column of the reservation management DB 337. The reservation management unit 312 also stores the estimated price, comments, and the like in the additional information column. The reservation management unit 312 may also store the date and time when the room reservation request was received in the additional information column.

[0522] As a result, the reception terminal 11 of the store corresponding to the store ID specified in the room reservation request will display the start time of use specified in the room reservation request on the room button Bc of the corresponding room ID on the room list screen, etc. Therefore, the karaoke booth reserved by the sales representative will be secured so that it cannot be used by other users. Therefore, the sales representative can efficiently attract users using the sales terminal 5.

[0523] The reservation management unit 312 of the infrastructure server 3 constantly or at predetermined time intervals performs an elapsed time determination to detect reservation information for which a predetermined time has passed since the reservation date and time by comparing the current date and time with the reservation date and time of the reservation information stored in the reservation management DB 337. When the reservation management unit 312 detects reservation information for which a predetermined time has passed since the reservation date and time, it deletes the data entry related to that reservation information from the reservation management DB 337.

[0524] The predetermined elapsed time that serves as an index for judgment can be set arbitrarily. Furthermore, when deleting reservation information, the reservation management unit 312 may be configured to confirm with the operator of the reception terminal 11 or the external sales terminal 5 whether deletion is permitted, and to delete the reservation information from the reservation management DB 337 if the operator instructs that deletion is permitted.

[0525] This allows the store to prevent a karaoke booth reserved by a room reservation request from continuing to be reserved inadvertently, allowing the store to efficiently manage the karaoke booths and increase the rate at which the karaoke booths are used.

[0526] Here, an example of the operation of the infrastructure server 3 and the sales terminal 5 related to reserving a room at a karaoke booth will be described with reference to Fig. 54. Fig. 54 is a sequence diagram showing an example of the process related to reserving a room at a karaoke booth, which is carried out between the infrastructure server 3 and the sales terminal 5. Note that, as a premise of this process, it is assumed that the room list screen B is displayed on the display unit 116 of the sales terminal 5.

[0527] When the second collaboration processing unit 513 of the sales terminal 5 receives an operation on the room button Bc of a karaoke booth that is in the "vacant" state from the room list screen B (ACT221), it displays the room reservation screen V on the display unit 116 (ACT222).

[0528] Next, when the second collaboration processing unit 513 of the sales terminal 5 receives input of reservation information, etc., with the reservation date and time set via the room reservation screen V (ACT223), it sends a room reservation request to the infrastructure server 3, including the store ID and room ID of the target store, the entered reservation information, the employee ID of the operator operating the sales terminal 5, etc. (ACT224).

[0529] When the reservation management unit 312 of the infrastructure server 3 receives a room reservation request, it refers to the reservation management DB 337 and determines whether the room can be reserved based on the existing reservation information stored in association with the combination of the store ID and room ID specified in the room reservation request (ACT225).

[0530] For example, the reservation management unit 312 determines whether the time period specified in the room reservation request interferes with the date and time of an existing reservation. If the time period specified in the room reservation request does not interfere with the date and time of an existing reservation, the reservation management unit 312 determines that the room can be reserved. On the other hand, if the time period specified in the room reservation request interferes with the date and time of an existing reservation, the reservation management unit 312 determines that the room cannot be reserved.

[0531] If the reservation management unit 312 of the infrastructure server 3 determines that the room can be reserved, it registers the reservation information, employee ID, etc. in the reservation management DB 337 in association with the store ID and room ID specified in the room reservation request (ACT226). Next, the reservation management unit 312 cooperates with the information provision unit 317 to send support information reflecting the changes to the external sales terminal 5 (ACT1227).

[0532] The second cooperation processing unit 513 of the sales terminal 5 updates the room list screen B etc. based on the support information provided from the infrastructure server 3, thereby displaying a screen reflecting the changes (ACT1228).

[0533] Furthermore, if the reservation management unit 312 of the infrastructure server 3 determines that the room cannot be reserved, it cooperates with the information providing unit 317 to send response information including the reason why the room cannot be reserved to the reception terminal 11 (ACT229).

[0534] In this case, the second link processing unit 513 of the sales terminal 5 displays the reason why the room cannot be reserved, etc., based on the response information provided from the infrastructure server 3 (ACT230).

[0535] This allows the sales representative to secure karaoke booths for the customers they have attracted through their sales activities at the store to which the sales representative belongs. Therefore, the facility management system 100 can provide operational support for karaoke booths.

[0536] In addition, in the past, when a salesperson approached a potential customer, they had to confirm the customer's planned stay time and desired price, and then call the store or other means to confirm whether the customer was available to enter. Furthermore, because the salesperson was outside the store and could not grasp the store's real-time occupancy status, they were sometimes unable to provide the customer with the desired stay time. Even with online reservation systems, there were sometimes problems, such as bookings being made between a customer who made a reservation an hour later and the customer they approached. The requests of the invited customer also had to be communicated to the store by phone or other means, and the price information negotiated with the customer was not properly communicated to the store, which could lead to problems with the customer.

[0537] On the other hand, with the facility management system 100 of this embodiment, by inputting store entry information according to the customer's wishes from the sales terminal 5 and reserving a karaoke booth at the store, it is possible to prevent bookings with customers invited by the store or other sales staff. Furthermore, the facility management system 100 can store information such as the desired price confirmed during negotiations with the customer and notify the store, so that when the invited customer visits the store, the store staff can correctly grasp that information. Furthermore, with the facility management system 100, if the customer does not enter the store within a certain period of time after reserving the room, the room reservation status can be automatically canceled, allowing the room to be made available for use by another customer.

[0538] In this process, the infrastructure server 3 determines whether or not the room can be reserved (i.e., whether or not the reservation can be made) after receiving the room reservation request, but the timing of the determination is not limited to this. For example, the determination of whether or not the room can be reserved may be made when an operation to specify (select) the karaoke booth to be reserved is performed on the room list screen B.

[0539] Also, room buttons Bc of karaoke booths that can be reserved may be enabled to be selectable on the room list screen B. In this case, in addition to the condition of "vacant room," for example, room buttons Bc of karaoke booths that have no reservations, or karaoke booths that have reservations but whose reservation date and time is after a predetermined time (for example, more than five hours later or the next day), may be enabled.

[0540] In addition, in this process, the determination of whether or not a room can be reserved is made by the check-in processing unit 313 of the infrastructure server 3, but it may also be configured to be made by the second cooperation processing unit 513 of the sales terminal 5. In this case, if the second cooperation processing unit 513 determines that a room cannot be reserved, it notifies the sales person by displaying the reason why the room cannot be reserved, etc.

[0541] Furthermore, when a room reservation request is received, the reservation management unit 312 of the infrastructure server 3 may determine whether or not the room can be reserved (i.e., whether or not the reservation can be made) by comparing the maximum and minimum occupancy numbers of the karaoke booth specified in the room reservation request with the number of users specified in the room reservation request. For example, the reservation management unit 312 determines that the room can be reserved if the number of users specified in the room reservation request falls within the range of the maximum and minimum occupancy numbers of the karaoke booth. Furthermore, the reservation management unit 312 determines that the room cannot be reserved if the number of users specified in the room reservation request deviates from the range of the maximum and minimum occupancy numbers of the karaoke booth.

[0542] Furthermore, in the case of a room reservation request from a sales representative, the reservation manager 312 may determine whether or not to reserve the room within a range exceeding the maximum and minimum occupancy limits set for the karaoke booth. For example, when the reservation manager 312 determines that the reservation is made by a sales representative based on access from the sales terminal 5 or the employee ID included in the room reservation request, it may extend the maximum and / or minimum occupancy limits set for the karaoke booth by a predetermined amount and determine whether or not to reserve the room within the extended range. Alternatively, when the reservation manager 312 determines that the reservation is made by a sales representative, it may remove the restrictions on the maximum and / or minimum occupancy limits set for the karaoke booth.

[0543] It should be noted that the timing of the comparison with the maximum and minimum occupancies is not limited to this. For example, the comparison with the maximum and minimum occupancies may be performed when the operation to input the number of users is performed on the room reservation screen V.

[0544] The comparison with the maximum and minimum occupancy may be performed by the check-in processing unit 313 of the infrastructure server 3, or by the second cooperation processing unit 513 of the sales terminal 5. In this case, if the second cooperation processing unit 513 determines that the number of occupancies falls outside the range of the maximum and minimum occupancy, it notifies the salesperson by displaying the reason for not being able to reserve the room, that the number of occupancies falls outside the range of the maximum and minimum occupancy.

[0545] Next, a description will be given of an example of operation of the notification process performed by the notification processing unit 318 of the infrastructure server 3. Fig. 55 is a sequence diagram showing an example of the notification process performed by the notification processing unit 318 of the infrastructure server 3.

[0546] First, the notification processing unit 318 of the infrastructure server 3 performs a first detection process (ACT241) to detect a karaoke booth that has been reached a predetermined time before the scheduled departure date and time, based on the current date and time and the scheduled departure date and time of each data entry registered in the check-in management DB 336. When the notification processing unit 318 detects a karaoke booth that has been reached a predetermined time before the scheduled departure date and time, the notification processing unit 318 transmits first notification information to the user terminal 4 of the user who uses the karaoke booth, based on the member ID or contact information of the user, notifying that the scheduled departure date and time or the predetermined time before the scheduled departure date and time has been reached (ACT242).

[0547] Furthermore, the notification processing unit 318 of the infrastructure server 3 performs a second detection process (ACT243) to detect karaoke booths that have reached their scheduled departure date and time based on the current date and time and the scheduled departure date and time of each data entry registered in the check-in management DB 336. When the notification processing unit 318 detects a karaoke booth that has reached its scheduled departure date and time, it transmits second notification information to the user terminal 4 of the user who uses the karaoke booth based on the member ID or contact information of the user who uses the karaoke booth, notifying the user that the scheduled departure date and time has been reached (ACT244).

[0548] Furthermore, the notification processing unit 318 of the infrastructure server 3 performs a third detection process (ACT245) to detect karaoke booths for which a predetermined time has passed since the scheduled date and time of departure, based on the current date and time and the scheduled date and time of departure of each data entry registered in the check-in management DB 336. When the notification processing unit 318 detects a karaoke booth for which a predetermined time has passed since the scheduled date and time of departure, the notification processing unit 318 transmits third notification information to the user terminal 4 of the user using the karaoke booth, based on the member ID or contact information of the user, notifying the user of the scheduled date and time of departure or that a predetermined time has passed since the scheduled date and time of departure (ACT246).

[0549] As a result, users who are using the karaoke booth will receive notifications before, during, and after the scheduled time of departure, allowing them to efficiently prepare to leave the booth, extend their usage time, etc. Therefore, the facility management system 100 can provide support for users regarding the use of karaoke booths.

[0550] The user terminal 4 to which the notification information is sent may be, for example, the user terminal 4 of the user registered in the representative information field, or the user terminal 4 of another user. In the latter case, the notification information may be sent to the user terminals 4 of all users. It is preferable that the notification information be sent to the user terminal 4 of users whose entry / exit status is "entering" or "entered midway." Furthermore, if the user in the representative information field is "left midway" or "entry canceled," one user may be selected from the users whose entry / exit status is "entering" or "entered midway," and the notification information may be sent to the user terminal 4 of that user.

[0551] Furthermore, the notification destination of the notification information is not limited to the user terminal 4. For example, the notification processing unit 318 may send the notification information to the ordering terminal 12 provided in the corresponding karaoke booth based on the store ID and room ID included in the data entry of the check-in management DB 336. Also, for example, the notification processing unit 318 may send the notification information to the reception terminal 11 or the staff terminal 14 of the corresponding store based on the store ID included in the data entry of the check-in management DB 336.

[0552] In addition, in this process, the notification information is transmitted before and after the scheduled date and time of leaving the room and when the scheduled date and time of leaving the room is reached, but this is not limiting and the notification information may be transmitted at any timing. For example, the timing of transmitting the notification information may be stored in the store management DB in association with the store ID, so that the timing of transmitting the notification information can be set for each store.

[0553] As described above, the infrastructure server 3 associates each karaoke booth owned by the store with an identifiable room ID, and records the status of the karaoke booth and the period during which that status continued as operation results. Furthermore, the infrastructure server 3 generates support information indicating the operation status of the karaoke booth based on the operation results, and outputs the generated support information to the reception terminal 11, etc.

[0554] This allows store employees to understand the operating status of each karaoke booth by viewing a screen based on the support information generated by the infrastructure server 3, enabling them to take measures to improve efficiency and improve the operation of the facility. Therefore, the infrastructure server 3 can provide operational support for multiple facilities.

[0555] The infrastructure server 3 also generates support information that chronologically represents the state transition of the karaoke booths.The infrastructure server 3 also generates support information or aggregated support information that chronologically represents the periods during which the karaoke booths are unavailable, such as when they are being cleaned or broken down.

[0556] This allows store employees to understand the operating status of the karaoke booths from multiple angles by viewing the screen based on the support information generated by the infrastructure server 3. Therefore, the infrastructure server 3 can provide operational support for multiple facilities.

[0557] In addition, the infrastructure server 3 records the employee ID of the employee who was in charge of the work related to the status of the karaoke booth, in association with the status, and generates information representing the work period required for the work for the employee ID based on the recorded operating history.

[0558] This allows store employees to understand the working status of store employees by viewing a screen based on the support information generated by the infrastructure server 3. Therefore, the infrastructure server 3 can provide operational support for multiple facilities.

[0559] Furthermore, according to this embodiment, the amount of time spent in "out of order" or "cleaning" can be tallied by room and / or by person in charge, and the tallied results can be provided in the form of a list or the like. This makes it possible to provide guidance and work instructions to persons in charge who spend a long time cleaning. Furthermore, for rooms that spend a long time out of order, in combination with the function to register the reason for the malfunction, it is possible to understand what malfunction is taking time, and this can provide reference information for selecting equipment.

[0560] Furthermore, according to this embodiment, when a complaint is received from a user, the complaint can be registered. Then, according to this embodiment, when a complaint is registered, the registered details can be notified to the clerk terminal 14 carried by the employee. This improves the user experience and convenience for the user.

[0561] The above-described embodiment can be modified as needed by partially changing the configuration or functions of each of the above-described devices. Therefore, several modifications of the above-described embodiment will be described below as other embodiments. The following mainly focuses on differences from the above-described embodiment, and detailed descriptions of commonalities with the content already described will be omitted. The modifications described below may be implemented individually or in appropriate combination.

[0562] (Variation 1) In the above embodiment, the reception terminal 11 displays the operational performance of the store where the reception terminal 11 is installed, but the store to be displayed is not limited to this.

[0563] For example, the information providing unit 317 of the infrastructure server 3 may provide the reception terminal 11 with support information capable of displaying the operational records of multiple stores based on the store affiliation and authority associated with the employee ID of the operator operating the reception terminal 11. For example, if an employee is a manager of an area where multiple stores exist or a manager who oversees all stores, the information providing unit 317 generates and provides support information that indicates the operational records of multiple stores managed by the employee. In addition, the information providing unit 317 may derive the overall operating rate and failure rate of karaoke booths for a predetermined period for each store, and generate support information including the derived results.

[0564] When the first collaboration processor 1103 of the reception terminal 11 sends an operation record request to the infrastructure server 3, it includes the employee ID of the operator operating its own reception terminal 11 in the operation record request. The screen showing the operation record may be switched for each store, or the operation records of multiple stores may be displayed on the same screen so that the operation records can be compared between stores. In the latter case, the first collaboration processor 1103 displays the operation rates and failure rates of all karaoke booths over a predetermined period in a manner that allows them to be compared between stores.

[0565] This allows the operator of the reception terminal 11 to check the operating status of multiple stores, and therefore to understand the characteristics (features) and areas for improvement of each store. Therefore, the facility management system 100 can improve the convenience of operating karaoke booths.

[0566] (Variation 2) In the above embodiment, the reception terminal 11 is configured to be operated by an employee, but it may also be configured to be operated by the user himself / herself. In this case, the reception terminal 11 may be configured to selectively switch between an operation mode operated by an employee (hereinafter also referred to as an attended mode) and an operation mode operated by the user himself / herself (hereinafter also referred to as a self-mode).

[0567] There is no particular restriction on the method for switching the operation mode, and various methods can be used. For example, a method may be used in which an employee is authenticated by entering an employee ID and password to switch to manned mode, and then a command to switch to self-operated mode is given in this manned mode.

[0568] When the reception terminal 11 is operated in the self mode, it is preferable to restrict some of the above-mentioned functions and screens. For example, it is preferable to disable the function relating to displaying operation results. It is also possible to disable the function relating to complaint registration.

[0569] (Variation 3) In the above-described embodiment, a slip number is issued at check-in and printed on the slip, but this is not limiting and a configuration that does not use a slip number is also possible. Specifically, information that can identify a data entry related to the karaoke booth used by the user from the user database may be included and printed on the slip. For example, the first linking processor 1103 of the reception terminal 11 may print on the slip both or either the karaoke booth room ID and the representative member ID. The room ID and member ID may also be printed on the slip in the form of a code symbol.

[0570] This allows the infrastructure server 3 to omit the process of issuing the slip number, thereby improving the efficiency of the process.

[0571] (Variation 4) In the above embodiment, an example was described in which the infrastructure server 3 acts as the processing subject, but the reception terminal 11 may also be configured to act as the processing subject by having some or all of the functional configuration of the infrastructure server 3.

[0572] For example, the reception terminal 11 may be configured to include a check-in processing unit 313 and a check-out processing unit 316, thereby directly operating the user management DB held by the infrastructure server 3. Furthermore, for example, the reception terminal 11 may be configured to include an information providing unit 317, thereby deriving the operating status from various DBs held by the infrastructure server 3 and dynamically generating various screens.

[0573] (Variation 5) In the above-described embodiment, the facility used by the user is a karaoke booth, and the reception terminal 11 is installed at the reception desk of a store that has the karaoke booth. However, the facility is not limited to a karaoke booth, and the present invention can be applied to other types of facilities that are rented to users on an hourly basis. For example, the facility may be a leisure facility such as a darts bar or a manga cafe, or an exercise facility such as a sports gym, a golf course, or a bowling alley. In other words, the reception terminal 11 installed at the reception desk of these facilities may be configured as in the above-described embodiment.

[0574] Although the embodiments (and variations) of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, combinations, and modifications can be made without departing from the spirit of the invention. These embodiments and variations thereof are included within the scope and spirit of the invention, and are also included in the inventions and their equivalents as defined in the claims.

[0575] Furthermore, the programs executed by each device in the above embodiments are provided by being pre-installed in a storage medium (ROM or storage unit) included in the device, but this is not intended to be limiting. For example, the programs may be provided by being recorded in an installable or executable file format on a computer-readable storage medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk). Furthermore, the storage medium is not limited to a medium independent of the computer or embedded system, but also includes a storage medium that stores or temporarily stores a program downloaded via a LAN, the Internet, or the like.

[0576] In addition, the programs executed by each device in the above embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or may be configured to be provided or distributed via a network such as the Internet. [Explanation of symbols]

[0577] 1. Store system 2 Mobile Server 3 Infrastructure Server 4. User terminal 5. External sales terminal 11 Reception terminal 12 Ordering terminal 13 Kitchen terminal 14. Store clerk terminal 100 Facility Management System 311 Status Management Department 312 Reservation Management Department 313 Check-in Processing Unit 314 Order Reception Department 315 Claims Department 316 Checkout Processing Unit 1101 First display control unit 1102 First operation reception section 1103 First cooperation processing unit 511 Second display control unit 512 Second operation reception section 513 Second cooperation processing unit [Prior art documents] [Patent documents]

[0578] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-237961

Claims

1. a recording means for associating each facility owned by the store with an identifiable facility identifier and recording the state of the facility and the period during which the state continued as operation results; a generating means for generating information representing an operation status of the facility based on the operation record recorded by the recording means; an output means for outputting the information generated by the generation means; A business support device comprising:

2. the generating means generates information representing a time-series transition of a state of the facility. The business support device according to claim 1 .

3. the generating means generates information that chronologically represents or aggregates information about periods during which the facility is unavailable. The business support device according to claim 1 .

4. The recording means records an employee identifier of an employee who performed work related to the facility status in association with the facility status; the generating means generates information indicating the work period required for the work for each employee identifier based on the operation record. The business support device according to claim 1 .

5. providing means for providing an image representing each of the facilities in a displayable manner; an execution means for receiving an operation on the image and executing a process for switching a state of the facility corresponding to the image in accordance with the received operation; Equipped with The recording means records the operation results in response to the switching of the state. The business support device according to any one of claims 1 to 4.

6. Computers for business support devices, a recording means for associating each facility owned by the store with an identifiable facility identifier and recording the state of the facility and the period during which the state continued as operation results; a generating means for generating information representing an operation status of the facility based on the operation record recorded by the recording means; an output means for outputting the information generated by the generation means; A program to make it function as such.

Images