Reservation management device and program

Abstract

To provide a reservation management device and program that can promote mutual consideration among users. [Solution] In a reservation management system that manages reservations for two or more facilities, equipment, fixtures, and other managed items, if a reservation received by the reservation acceptance unit is in a waiting list state, the reservation optimization unit, which optimizes reservations, requests a change from the user of another reservation that can be changed to a confirmed state by changing the date and time of use, and if the change request is accepted, the date and time of use of the other reservation is changed.

Description

Technical Field

[0001] The present invention relates to a reservation management device and a program, and more specifically, to a reservation management device and a program that can promote the transfer between users.

Background Art

[0002] As an information processing system for managing reservation of use of facilities, equipment, furniture, etc., for example, the online reservation system of Patent Document 1 is known.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Normally, the number of facilities, equipment, and furniture owned by companies and other organizations is less than the number of personnel belonging to the organization such as employees, and the facilities, equipment, and furniture are not always available. In addition, recently, with the convergence of the COVID-19 pandemic, the way employees work has increased from telecommuting to going to the office to perform their duties. However, in organizations such as companies that have downsized their offices during the COVID-19 pandemic, there are fewer meeting rooms and other facilities, equipment, and furniture compared to the number of workers, and there is a problem that they cannot be used at the desired date and time.

[0005] In the conventional technology, when making a reservation for a facility, equipment, or furniture that has already been reserved by others, it is possible to make a reservation in a waiting cancellation state, and it has a certain effect when the reservations are concentrated.

[0006] However, with conventional technology, when a waiting list was created, it was left to negotiations between users whether or not they could use the facilities, equipment, and furnishings. There was a need to use information processing to facilitate mutual consideration among users.

[0007] In view of the above-mentioned problems, the present invention aims to provide a reservation management device and program that can promote mutual consideration among users. [Means for solving the problem]

[0008] The reservation management device according to the present invention, made to solve the aforementioned problems, is a reservation management device for managing reservations for two or more facilities, equipment, fixtures and other managed objects, and includes: a reservation acceptance unit that accepts a user's reservation for use of the managed objects and records at least the user, the managed object to be used, the date and time of use, and the reservation status indicating that the reservation is confirmed to be able to use the managed object at the date and time of use or is on the waiting list; a reservation cancellation unit that deletes the record for the specified reservation and cancels the reservation; and for reservations within a predetermined period, by changing the managed object to be used to another replaceable managed object, The system includes a reservation optimization unit that performs reservation optimization to attempt to secure the managed items and / or usage time, and a status change unit that changes the reservation status of the waiting list reservation to a confirmed state when the managed items become available due to the cancellation of another reservation or the reservation optimization, wherein the reservation optimization unit changes the usage date and time of the other reservation when, as a result of the reservation optimization, the waiting list reservation can be changed to a confirmed state by changing the usage date and time of another reservation, and the user of the other reservation accepts the change request from the user to the user of the other reservation.

[0009] The reservation management device according to the present invention may be configured to grant predetermined benefits to users of other reservations who have accepted the change request.

[0010] The reservation management device according to the present invention may also be configured such that the predetermined benefit is the awarding of predetermined points.

[0011] The reservation management device according to the present invention may also be configured so that the user who made the change request consumes a predetermined number of points. [Effects of the Invention]

[0012] According to the configuration of the present invention, when a reservation is in a waiting list state and can be changed to a confirmed state by changing the date and time of another reservation, the user can request the other user to make the change, and when the change request is accepted, the date and time of the other reservation is changed, thereby promoting mutual consideration among users when managing the facilities. [Brief explanation of the drawing]

[0013] [Figure 1] This figure shows the configuration of a reservation management device in one example of an embodiment of the present invention. [Figure 2] This flowchart shows the flow of a reservation in one example of the embodiment described above. [Figure 3] This figure shows the configuration of the reservation screen in one example of the same embodiment. [Figure 4] This figure shows an example of the state before optimization of the reservation in one example of the same embodiment. [Figure 5] This figure shows an example of the state during the optimization of the reservation in one example of the same embodiment. [Figure 6] This figure shows an example of the optimized state of the reservation system in one example of the same embodiment. [Figure 7] This figure shows the concept of point management in one example of the same embodiment. [Modes for carrying out the invention]

[0014] Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings. Figure 1 is a diagram showing the configuration of a reservation management device 1 in an example of an embodiment of the present invention. As shown in Figure 1, the reservation management device 1 in this example includes a reservation acceptance unit 11, a reservation cancellation unit 12, a reservation optimization unit 13, a status change unit 14, a point management unit 15, and a database 16.

[0015] In one example of this embodiment, the reservation management device 1 is a device that manages reservations for the use of two or more facilities, equipment, furniture, and other managed objects 4. The reservation management device 1 is configured using a server computer. The HDD (Hard Disk Drive), SSD (Solid State Drive), or other storage device of the server computer has a program pre-recorded in it that enables the server computer to function as the reservation management device 1. This program is loaded into the memory of the server computer and executed by the CPU (Central Processing Unit), thereby enabling the server computer to function as the reservation management device 1.

[0016] The hardware configuration of the reservation management device 1 can be changed as desired. For example, the reservation management device 1 may be configured using two or more computers. The roles assigned to each of the two or more computers can also be arbitrarily selected. For example, all computers constituting the reservation management device 1 may be configured to have reservation acceptance units 11 to database 16, or the reservation management device 1 may be configured with, for example, a computer with reservation acceptance units 11 to status change units 14, a computer with a point management unit 15, and a computer with a database 16. Furthermore, the computers constituting the reservation management device 1 may be arbitrarily selected according to the required performance and other requirements.

[0017] The reservation reception unit 11 accepts reservations from users for the use of the managed equipment 4. In one example of this embodiment, the reservation is recorded in the database 16, which will be described later, as information including at least the user, the managed equipment 4 to be used, the date and time of use, and the reservation status, which indicates either a confirmed status or a waiting list status.

[0018] In an example of this embodiment, a confirmed reservation for use means a reservation for use in which it is confirmed that the user can use the management target 4 at the use date and time, and a reservation for use in a cancellation-waiting state means that the management target 4 is the same as that of another reservation for use received earlier, and due to a partial or total overlap of the use date and time, the user cannot use the management target 4 at the use date and time. The reservation for use in the cancellation-waiting state is changed to the confirmed state by a state change unit 14 described later when the above-mentioned other reservation for use is cancelled. Note that the state of the reservation for use may be arbitrarily changed. For example, in an example of this embodiment, as will be described later, the reservation optimization unit 13 may change the management target 4 to another management target that can be exchanged. However, a state in which such an exchange is possible may be set as a provisional reservation state, and a state in which such an exchange is not possible or not allowed may be set as the main reservation state.

[0019] Also, the specific configuration of the information indicating the above reservation for use may be arbitrarily selected. For example, the information indicating the use date and time may be composed of the use start date and time and the use end date and time, or may be composed of the use start date and time and the use duration.

[0020] The reservation cancellation unit 12 cancels the reservation for use received by the reservation reception unit 11. As described above, in an example of this embodiment, when the user makes a reservation for use of the management target, the information indicating the reservation for use is recorded in the database 16 by the reservation reception unit 11. The reservation cancellation unit 12 cancels the reservation for use by deleting the information recorded by the reservation reception unit 11.

[0021] The reservation optimization unit 13 attempts to secure a reservable management target and / or use time by changing the management target to be used to another management target that can be exchanged for the reservation for use within a predetermined period.

[0022] The status change unit 14 changes the reservation status of usage reservations that have become available for use due to cancellation of the usage reservation or optimization of the usage reservation to the confirmed status. As described above, in this example embodiment, the information recorded in the database 16 by the usage reservation includes the reservation status, and one of the usage reservation statuses indicated by the reservation status is "waiting for cancellation," which is a state in which the use of the usage reservation has not been confirmed due to other usage reservations that were accepted earlier. The status change unit 14 changes the reservation status to the confirmed status for usage reservations that can be confirmed for use of the usage reservation due to cancellation of the usage reservation by the reservation cancellation unit 12 or optimization of the usage reservation by the reservation optimization unit 13.

[0023] The point management unit 15 causes users to consume or acquire predetermined points in response to predetermined activities. In one example of this embodiment, predetermined points are consumed when a user uses the managed service 4, and when a user requests a change from another user, and predetermined points are acquired when a user accepts a change request from another user. The point management unit 15 includes a pricing unit 15a, a usage status collection unit 15b, and an operation status collection unit 15c.

[0024] The pricing unit 15a determines, for each of the managed items 4, the points to be consumed or awarded for some or all of the user's specified activities, based on the usage status collected by the usage status collection unit 15b (described later) and the operational status collected by the operational status collection unit 15c (described later).

[0025] The usage information collection unit 15b collects information on the usage of the managed object 4 by users. In this example, the usage information includes the user, the managed object 4 used by the user, and the date and / or period during which the user used the managed object 4. The usage information collection unit 15b records the collected usage information in the database 16, and the recorded usage information is used by the pricing unit 15a when determining points.

[0026] The operational status collection unit 15c collects the operational status of the managed device 4. In this example, the operational status includes information about the managed device 4 and the time it was in operation, that is, the time it was being used by any user. The operational status collection unit 15c records the collected operational status in the database 16, and the recorded operational status is used by the pricing unit 15a when determining points.

[0027] Database 16 is a database that manages the information handled by the reservation management device 1. In this example, database 16 is an RDBMS (Relational Database Management System) built on the reservation management device 1, but the specific configuration of database 16 can be changed as desired. For example, a predetermined area of ​​the storage device provided by the reservation management device 1 may be treated as database 16, or some predetermined information may be managed by the RDBMS and the remaining information may be recorded in a predetermined area of ​​the storage device.

[0028] In this embodiment, the reservation management device 1 is configured using a server computer as described above. When managing reservations using the reservation management device 1, the user operates the user terminal 2, which is connected to the reservation management device 1 via a network 3 described later.

[0029] User terminal 2 is a terminal used by users who make reservations for managed services, and is equipped with a display or other display device 21 and an input device 22 such as a keyboard, mouse, touch panel, etc. As described above, the reservation management device 1 in this example is configured using a server computer, and users operate user terminal 2 to make reservations and perform other operations.

[0030] User terminal 2 may be configured using a well-known computer. For example, a stationary personal computer may be used, or a notebook computer may be used. Alternatively, user terminal 2 may be configured using a smartphone, tablet computer, or other portable device owned by the user.

[0031] Furthermore, the specific configuration of communication between the user terminal 2 and the reservation management device 1 can be arbitrarily chosen. For example, the reservation management device 1 may be configured to function as a web application server, with the user terminal 2 accessing a predetermined URL (Uniform Resource Locator) of the reservation management device 1, thus providing functionality as a so-called web application. Alternatively, a client application installed on the user terminal 2 may be configured to communicate with the reservation management device 1 using a predetermined communication protocol.

[0032] As described above, in this example of the embodiment, the reservation management device 1, the user terminal 2, and the managed device 4 (described later) are connected to each other via network 3. The specific configuration of network 3 can be arbitrarily selected. For example, network 3 may be the Internet or other wide-area network, or a LAN (Local Area Network) may be used as network 3, or a VPN (Virtual Private Network) built on a wide-area network may be used as network 3. In this example of the embodiment, the reservation management device 1 communicates with the user terminal 2 and the managed device 4, but the user terminal 2 and the managed device 4 do not communicate with each other. Network 3 may be configured from a network used for communication between the reservation management device 1 and the user terminal 2, and another network used for connecting the reservation management device 1 and the managed device 4.

[0033] Targeted Items 4 are those for which reservations can be made. Targeted Items 4 can be arbitrarily designated as those for which users can make reservations, such as offices, resorts and other facilities, meeting rooms, work booths and other equipment, desks and chairs, computers, projectors and other furniture, etc.

[0034] Furthermore, in this example, the managed object 4 is connected to the reservation management device 1 via the network 3 in a communicative manner. As described above, the point management unit 15 of the reservation management device 1 includes an operational status collection unit 15c that collects the operational status of the managed object 4, and the operational status collection unit 15c collects the operational status of the managed object 4 via the network 3. The specific method by which the operational status collection unit 15c collects the operational status can be arbitrarily changed, and if the operational status can be collected by a well-known method that does not involve the network 3, the managed object 4 does not need to be connected to the network 3. For example, if there is a computer that manages the operational status of the managed object 4, the reservation management device 1 may be configured to be connected to the computer in a communicative manner.

[0035] The above describes the configuration of the reservation management device 1 in one example of this embodiment. Next, the reservation management flow in one example of this embodiment will be described. Figure 2 is a flowchart showing the reservation flow in one example of this embodiment.

[0036] First, the user operates the user terminal 2 to make a reservation with the reservation management device 1 (step S1).

[0037] Figure 3 shows the configuration of the reservation screen W1 in one example of this embodiment. As shown in Figure 3, the reservation screen W1 includes the reservation title W11, participants W12, date and time of use W13, usage conditions W14, and a confirmation button W15.

[0038] When a user enters or selects items on the aforementioned reservation screen W1 and presses the OK button W15, the user terminal 2 sends a reservation request including the entered and selected items to the reservation management device 1. The reservation acceptance unit 11 of the reservation management device 1 receives the aforementioned request and accepts the reservation.

[0039] The reservation reception unit 11 determines, based on the received reservation and other reservations received prior to it, whether the received reservation allows the user to use the managed facility 4 on the scheduled date and time. Based on the determination result, the reservation status is recorded in the database 16 as either confirmed or on a waiting list.

[0040] If the reservation status of a received reservation is in a waiting list state, the reservation management device 1 performs reservation optimization using the reservation optimization unit 13 (step S2). In this example of the embodiment, the optimization is a process in which the reservation optimization unit 13 attempts to secure reservable management units and / or usage time by changing the management unit used for reservations for a predetermined period to another interchangeable management unit.

[0041] Figures 4-6 are conceptual diagrams illustrating an example of optimizing usage reservations in one example of this embodiment. Figure 4 shows the state before optimization, Figure 5 shows the state during optimization, and Figure 6 shows an example of the state after optimization. In the example shown in Figures 4-6, meeting rooms A-E, which are managed 4, are used in 30-minute increments from 8:00 to 19:00.

[0042] As shown in Figure 4, in the pre-optimization state, a total of 29 reservations (R1-29) have already been accepted for meeting rooms A-E. Of these reservations, reservations R1, R5, R13, and R16 are reservations where the designated meeting room cannot be changed to another meeting room.

[0043] Furthermore, the system may be configured to determine which of the conference rooms A to E is interchangeable based on the capacity and equipment of each conference room, as well as the user's preferences in the reservation. In one example of this embodiment, as described above, the reservation screen W1 is equipped with usage conditions W14, allowing the user to select the purpose of use and the equipment to be used. For example, if a projector is selected as the equipment to be used in a reservation, the conference rooms A to E that are equipped with projectors are interchangeable, but the system may be configured so that it cannot be changed to a conference room that is not equipped with a projector.

[0044] In the state shown in Figure 4, when a reservation is received for the use of any of the A to E conference rooms between 16:00 and 18:00, the reservation optimization unit 13 optimizes the reservations for a predetermined period. In one example of this embodiment, the predetermined period is from two hours before the newly received reservation to two hours after the newly received reservation. As mentioned above, in the example in Figure 4, reservations can be made until 19:00, so the optimization for the above reservations applies to reservations R6, R7, R8, R12, R14, R15, R19, R20, R24, R25, and R29, which are for use between 14:00 and 19:00.

[0045] As a specific optimization method in one example of this embodiment, reservations for use within a predetermined period and newly accepted reservations are assigned to conference rooms A to E in order from those with the longest usage time. In the example shown in Figure 4, reservations R8, R25, and the newly accepted reservation RN are 2-hour reservations, and are the reservations with the longest usage time. As shown in Figure 5, the reservation optimization unit 13 assigns reservations R8, R25, and RN to conference rooms A, C, and D, respectively.

[0046] The next longest reservations are reservations R24 and R29, both lasting 1.5 hours. As shown in Figure 5, the reservation optimization unit 13 assigns reservations R24 and R29 to conference room D and conference room A, respectively.

[0047] The next longest reservations are reservations R6, R15, R19, and R20, each lasting 1 hour. The reservation optimization unit 13 assigns reservations R6, R15, R19, and R20 to conference rooms C, B, E, and C, respectively.

[0048] Next in length are reservations R7, R12, and R14, each with a usage time of 30 minutes, as mentioned earlier. The reservation optimization unit 13 assigns reservations R7, R12, and R14 to meeting rooms A, B, and B, respectively. Since reservations R7, R12, and R14 have a usage time of 30 minutes, and there are no reservations with a shorter usage time, the optimization by the reservation optimization unit 13 is completed, resulting in the state shown in Figure 6.

[0049] The reservation optimization unit 13 performs the above process for all usage reservations for a predetermined period and for newly accepted usage reservations. If all usage reservations are assigned, the optimization is considered successful; if any usage reservations are not assigned, the optimization is considered a failure, and the subsequent processes are executed.

[0050] The examples shown in Figures 4 to 6 represent cases where optimization is successful. In these cases, the newly accepted reservation RN is recorded in database 16 as a reservation in which conference room D is confirmed to be available for use for two hours from 16:00 to 18:00. Furthermore, if the conference room used for a reservation is changed due to optimization, the record in database 16 is also updated. On the other hand, if optimization fails, the newly accepted reservation is recorded in database 16 as a reservation on the waiting list.

[0051] If, as a result of the optimization in step S2, a newly accepted reservation goes into a waiting list state, the reservation optimization unit 13 of the reservation management device 1 then determines whether the newly accepted reservation can be changed to a confirmed state by changing the usage date and time of another reservation, and selects candidates for changing the usage date and time (step S3).

[0052] For example, in the example shown in Figure 6, if a new reservation is accepted for use of any of conference rooms A to E from 16:30 to 18:00, the new reservation cannot be confirmed even after performing the optimization described above. On the other hand, in Figure 6, if the reservation R19 for use of conference room E from 16:00 to 17:00 is changed to use from 15:30 to 16:30, the new reservation can be confirmed. In step S3, if a reservation that is on the waiting list can be changed to a confirmed state by changing the use date and time of another reservation, it is selected as a candidate for change.

[0053] When the reservation optimization unit 13 of the reservation management device 1 selects a candidate for change in step S4 described above, it sends a change request from the user who made the new reservation to the user of the candidate for change (step S4). In one example of this embodiment, as described above, the user makes a reservation by operating the reservation screen W1 displayed on the user terminal 2, but in step S5, a dialog box is displayed on the reservation screen W1 asking whether or not to request a change in the date and time of use for the selected candidate.

[0054] If a user decides to make the aforementioned change request, the reservation management device 1 will send a request to the candidate user to change the date and time of use. The specific method for making the change request can be arbitrarily selected; for example, it may be configured to send an email or SMS (Short Message Service) containing a URL that leads to a screen where the user can choose to accept or reject the request.

[0055] When a user who has received a change request accepts the request, the reservation optimization unit 13 of the reservation management device 1 changes the usage date and time of the reservation that is the subject of the change request, i.e., the candidate reservation selected in step S3 above (step S5). In the example of Figure 8 above, reservation R19 is the reservation that is the subject of the change request, and in step S5, the usage date and time of reservation R19 is changed to 15:30 to 16:30.

[0056] When the date and time of a reservation are changed in step S5, the status change unit of the reservation management device 1 changes the reservation status of any reservations that were in a waiting list state due to the changed reservation to a confirmed state (step S6).

[0057] On the other hand, if the user does not submit a change request, or if the user of the aforementioned candidate reservation does not accept the change request, the reservation status will remain in a waiting list state.

[0058] The above describes the reservation process in one example of this embodiment. Next, we will explain the point management in one example of this embodiment.

[0059] Figure 7 shows an overview of point management in an example of this embodiment. In this example, when a user performs a predetermined activity, the user consumes points according to the predetermined activity, or points are awarded to the user as a reward. As shown in Figure 7, in this example, when user U uses facilities, equipment, fixtures, and other managed items 4 as a predetermined activity, and when the user makes the aforementioned change request to another user, predetermined points are consumed. On the other hand, if the user accepts the change request from another user, predetermined points are awarded as a reward.

[0060] The timing of point consumption can be arbitrarily selected. In one example of this embodiment, points are consumed at the time a reservation is accepted in order to determine whether or not a reservation is possible based on the point balance. However, points may also be consumed at the time when user U actually uses the managed device 4, or at specific times such as daily or weekly.

[0061] In one example of this embodiment, the points held by each user, and the points corresponding to the use of managed item 4, are recorded in the aforementioned database 16. When a user uses managed item 4, the point management unit 15 acquires the points corresponding to the use of managed item 4 and subtracts them from the points held by the user. The result of the subtraction is recorded in the database 16 as the points held after use.

[0062] In one example of this embodiment, some or all of the points consumed or earned by the user through predetermined activities are updated at predetermined timings by the pricing unit 15a based on usage status collected by the usage status collection unit 15b and operation status collected by the operation status collection unit 15c.

[0063] When user U uses managed equipment 4, the reservation management device 1 collects the usage status of managed equipment 4 by user U using the usage status collection unit 15b. In one example of this embodiment, the usage status is recorded in the database 16 as information including user U, the managed equipment 4 used by user U, and the usage period.

[0064] Furthermore, the reservation management device 1 collects the operating status of the managed device 4 using the operating status collection unit 15c. In this example of the embodiment, the operating information is recorded in the database 16 as information indicating the time that the managed device 4 was in operation, that is, the time that it was being used by any user U. As mentioned above, in this example of the embodiment, the reservation management device 1 and the managed device 4 are connected to each other via the network 3, and the operating status collection unit 15c directly collects the operating status from the managed device 4. However, the specific method for collecting the operating status can be arbitrarily changed. For example, the device may receive a CSV (Comma Separated Values) or other file containing the operating status of the managed device 4 from a predetermined computer.

[0065] Furthermore, the collection of usage status by the usage status collection unit 15b and the collection of operation status by the operation status collection unit 15c may be performed at any time. For example, the usage status collection unit 15b and the operation status collection unit 15c may be set to run daily, or the reservation acceptance unit 11 may collect usage status based on the accepted usage reservation when it accepts a usage reservation for the managed device 4.

[0066] The usage data collected by the usage data collection unit 15b and the operational data collected by the operational data collection unit 15c are used by the pricing unit 15a for pricing, that is, for determining the points to be consumed or awarded for a user's specified activities. The points determined by the pricing unit 15a are recorded in the database 16 and used as points to be consumed or awarded for subsequent specified activities.

[0067] As described above, in this example of the embodiment, points are consumed when a user uses the managed service 4 and when a user requests another user to change their reservation, and points are awarded as a reward when a user accepts a change request from another user. However, the predetermined activities in which points are consumed or awarded can be arbitrarily selected, and in addition to the predetermined activities, points may be awarded to each user U at periodic timings such as the end of the fiscal year, or points may be awarded according to the performance and achievements of user U.

[0068] This concludes the description of this example embodiment. In this example embodiment, the reservation received by the reservation acceptance unit 11 has a reservation status indicating either a confirmed state or a waiting list state. A reservation in the waiting list state is changed to a confirmed state when another reservation received earlier than the current reservation, which has the same managed object 4 and overlaps with part or all of the usage date and time, is canceled by the reservation cancellation unit 12. In addition, if the reservation can be changed by changing the usage date and time of the other reservation, a request for change is made to the user of the other reservation, and the usage date and time are changed if the user agrees. With this configuration, this example embodiment can promote mutual consideration among users when using managed object 4.

[0069] Furthermore, the reservation management device 1 in this example includes a point management unit 15. When a user requests a change from another user, a predetermined number of points are consumed, and when a change request from another user is accepted, a predetermined number of points are awarded as a reward. This configuration further promotes mutual consideration among users when using the managed service 4 in this example.

[0070] However, the embodiments of the present invention are not limited to those described above. For example, in one embodiment, the reservation acceptance unit 11 accepts usage reservations, and if the accepted usage reservation is in a waiting list state, the reservation optimization unit 13 is configured to optimize the usage reservation. However, optimization may be performed at any time, for example, in addition to when a usage reservation is accepted, optimization may be performed at periodic timings such as daily.

[0071] Other specific configurations are not limited to this embodiment, and various modifications are possible without departing from the spirit of the present invention. [Explanation of Symbols]

[0072] 1. Reservation management device 11 Reservation Department 12. Reservation Cancellation Department 13. Reservation Optimization Department 14. State Change Section 15. Point Management Department 15a Pricing section 15b Usage Data Collection Department 15c Operation Status Collection Unit 16 Databases 2. User terminals 3 Network 4. Managed items

Claims

1. A reservation management device for managing reservations for two or more facilities, equipment, fixtures, and other items under management, A reservation reception unit that accepts reservations from users for the use of the aforementioned managed equipment and records at least the user, the managed equipment to be used, the date and time of use, and the reservation status indicating that the reservation is confirmed to allow the use of the managed equipment at the date and time of use or that the user is on a waiting list for cancellations. A reservation cancellation unit that deletes the record of the specified reservation and cancels the reservation, A reservation optimization unit performs reservation optimization by attempting to secure reservable management targets and / or usage time for the aforementioned usage reservations within a predetermined period by changing the management target being used to another interchangeable management target; A status change unit changes the status of the reservation to a confirmed status when the aforementioned reservation on the waiting list becomes available due to the cancellation of another aforementioned reservation or the aforementioned reservation optimization. Equipped with, The reservation optimization unit, as a result of the reservation optimization, changes the usage date and time of the other reservation if the reservation in the waiting list state can be changed to the confirmed state by changing the usage date and time of another reservation, and the user of the other reservation accepts the change request from the user to the user of the other reservation. Reservation management device.

2. The user of the other reservation who has agreed to the aforementioned change request will be granted a predetermined benefit. The reservation management device according to claim 1.

3. The aforementioned predetermined benefit is the awarding of predetermined points. The reservation management device according to claim 3.

4. The user who made the aforementioned change request consumes a predetermined number of points. The reservation management device according to claim 2.

5. A program that causes a computer to function as a reservation management device according to any one of claims 1 to 4.

Images