Information generating device and program

Abstract

To provide a reservation management system that can manage lending of an article such as a key according to a set schedule, and improve the utilization rate of an object to be lent.SOLUTION: A reservation management system comprises: an article management device that stores a facility related article for using a facility; a schedule management unit that manages a reservation for the facility; and a cooperation unit that, when detecting that the facility related article is present in the article management device earlier by a predetermined first advance notification time than a scheduled use start time in the reservation for the facility, notifies a user that the facility related article can now be taken out, and instructs the article management device to provide a setting allowing the user to take out the facility related article.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention provides Information generating device and program Regarding. [Background technology]

[0002] Regarding key lending management, the key lending management system described in Patent Document 1 pre-configures a key lending diagram showing the person to whom the key is to be lent and the lending time period based on reservation information. Furthermore, once this key management system identifies a user, for example by reading the user's ID card with a card reader, it references the key lending diagram and searches for keys reserved for lending at the specified time for the identified user. If a matching key is found, the key lending management system makes the key available for removal from the key management device in which it is stored. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-113220 Summary of the Invention [Problem to be solved by the invention]

[0004] The key lending management system described in Patent Document 1 can manage key lending according to a set schedule. In addition, it would be even more desirable if the utilization rate of the lending objects (for example, conference rooms or company cars) could be improved.

[0005] The present invention provides a reservation management system, a reservation management method, and a program that can manage the lending of items such as keys according to a set schedule and can improve the utilization rate of items that can be lent. [Means for solving the problem]

[0006] According to a first aspect of the present invention, an information generating device receives information from an article management device. , to use the facilities A record that generates facility usage history information based on the history of taking out and returning equipment-related items. history A generation unit and a facility usage history information generation unit For each facility group of randomly selected facilities and a statistical information generating unit that generates statistical information on the usage history of the facility.

[0007] The facility usage history information is When the user of the facility takes out or returns the facility-related item, the user inputs the information into the item management device. The statistical information generating unit may generate usage statistics for each user regarding facility usage, including user information, facility, pick-up date and time, and return date and time.

[0008] The facility usage history information includes at least the facility, the date and time of pick-up, and the date and time of return. 、 and , the user's belongings identified from the user information The statistical information generating unit may generate usage statistics for each organization regarding facility usage, including information about the organization.

[0009] The facility groups may be narrowed down by specifying a group in the facility grouping stored in a storage unit of a groupware server device to which the statistical information generating unit is connected. The facility groups may be narrowed down to a group of facilities registered in the selected facility management device by selecting the facility management device.

[0010] The statistical information on the facility usage history may include at least one of usage time, usage rate, number of uses, and average usage time. The facility usage history statistical information may be sorted in descending order of the usage time, the usage rate, the number of times of use, and the average usage time. According to a second aspect of the present invention, a program is provided for causing a computer to , to use the facilities Generate facility usage history information based on the facility-related item take-out history and return history, and based on the facility usage history information, For each arbitrarily selected facility group This is a program for generating statistical information on the usage history of the facility. [Effects of the Invention]

[0011] According to the present invention, it is possible to manage the lending of items such as keys according to a set schedule, and to improve the utilization rate of items to be lent. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a schematic diagram illustrating the device configuration of a reservation management system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a schematic diagram illustrating the functional configuration of a groupware server device according to the embodiment. [Figure 3] FIG. 10 is a diagram showing an example of a reservation registration screen displayed by a groupware client device according to the embodiment. [Figure 4] FIG. 10 is a diagram showing an example of a reservation list screen displayed by a groupware client device according to the embodiment. [Figure 5] 2 is a schematic block diagram showing the functional configuration of an article management device according to the embodiment. FIG. [Figure 6] 2 is a front view showing the state in which the front cover of the article management device according to the embodiment is open. FIG. [Figure 7] FIG. 2 is a perspective view showing a key body, a key holder, and a holding part according to the embodiment. [Figure 8] FIG. 2 is a perspective view of a storage section according to the embodiment. [Figure 9] FIG. 2 is a front view of an article management side operating unit according to the embodiment. [Figure 10] FIG. 2 is a schematic block diagram illustrating a functional configuration of a collaboration device according to the embodiment. [Figure 11] 10A and 10B are diagrams illustrating an example of user management information displayed by a linked-side display unit according to the embodiment. [Figure 12] 10A and 10B are diagrams illustrating an example of display of facility management information by a linked-side display unit according to the embodiment. [Figure 13] 10 is a diagram showing an example of usage status management information by a linked-side display unit according to the embodiment; FIG. [Figure 14] 10 is a diagram showing an example of a system operation setting screen displayed by a collaboration-side display unit according to the embodiment; FIG. [Figure 15] FIG. 10 is a diagram showing an example of a loaned email sent by the advance notification processing unit according to the embodiment. [Figure 16]10 is a diagram showing an example of an advancement available email sent by the advancement processing unit according to the embodiment. FIG. [Figure 17] 10 is a diagram showing an example of a retrieval completion notification email sent by a retrieval notification processing unit according to the embodiment; FIG. [Figure 18] 10 is a diagram showing an example of a cancellation notice email sent by the cancellation notice processing unit according to the embodiment. FIG. [Figure 19] FIG. 10 is a diagram showing an example of a returned notification email sent by a return notification processing unit according to the embodiment. [Figure 20] 10 is a diagram showing an example of a return reminder email sent by the return delay processing unit according to the embodiment. FIG. [Figure 21] 10 is a diagram illustrating an example of a display screen of usage history information displayed by a linked-side display unit according to the embodiment. FIG. [Figure 22] 10 is a diagram showing an example of display of individual facility usage statistics by a linked-side display unit according to the embodiment; FIG. [Figure 23] 10 is a diagram showing an example of display of organization-specific facility usage statistics by a linked-side display unit according to the embodiment. FIG. [Figure 24] 10 is a diagram showing an example of display of usage statistics by holder group of a facility by a linked-side display unit according to the embodiment. FIG. [Figure 25] 10 is a diagram showing an example of a display of a holder group setting screen on a linked-side display unit according to the embodiment. FIG. [Figure 26] 10 is a diagram showing an example of a holder group management screen displayed by a linked-side display unit according to the embodiment; FIG. [Figure 27] 10 is a diagram showing an example of display of information on frequently used facilities by a linked-side display unit according to the embodiment. FIG. [Figure 28] 10 is a diagram showing an example of displaying information about rarely used equipment by a linked-side display unit according to the embodiment. FIG. [Figure 29] 10 is a sequence diagram showing an example of a processing procedure in which the reservation management system according to the embodiment receives a reservation for equipment and handles the removal of equipment-related items. FIG. [Figure 30]FIG. 10 is a sequence diagram illustrating an example of a processing procedure in the embodiment in which the equipment-related item has not been returned when the advance notification time comes before the scheduled start time of use. [Figure 31] FIG. 10 is a sequence diagram showing a first example of a processing procedure in which the groupware server device according to the embodiment cancels a facility reservation. [Figure 32] FIG. 10 is a sequence diagram showing a second example of the processing procedure by which the groupware server device according to the embodiment cancels a facility reservation. [Figure 33] 10 is a flowchart illustrating an example of a processing procedure in which the item management device according to the embodiment outputs an alarm about an equipment-related item not being removed. [Figure 34] FIG. 10 is a sequence diagram showing a first example of a procedure of a process performed by a linkage device according to the embodiment when returning an equipment-related item. [Figure 35] FIG. 10 is a sequence diagram showing a second example of the procedure of the process performed by the linking device according to the embodiment when returning the equipment-related item. [Figure 36] FIG. 10 is a sequence diagram showing a third example of a procedure of a process performed by a linking device according to the embodiment when returning an equipment-related item. [Figure 37] 10 is a flowchart illustrating an example of a processing procedure in which the item management device according to the embodiment outputs an alarm about a failure to return an equipment-related item. DETAILED DESCRIPTION OF THE INVENTION

[0013] The following describes embodiments of the present invention, but the following embodiments do not limit the scope of the invention as claimed. Furthermore, not all of the combinations of features described in the embodiments are necessarily essential to the solution of the invention. 1 is a schematic diagram showing the device configuration of a reservation management system according to an embodiment of the present invention. As shown in FIG. 1, the reservation management system 1 includes a groupware server device 100, an item management device 200, and a collaboration device 300.

[0014] The groupware server device 100 and the collaboration device 300 are communicatively connected via an internal network 500. The item management device 200 and the collaboration device 300 are also communicatively connected via the internal network 500. Furthermore, the groupware server device 100 and the groupware client device 400 are also communicatively connected via the internal network 500. Furthermore, the collaboration device 300 and the mobile terminal device 800 are communicatively connected via the internal network 500, a gateway device 600, and an external network 700. The reservation management system 1 may include any one or more (or all) of the groupware client device 400, the internal network 500, the gateway device 600, and the mobile terminal device 800.

[0015] The reservation management system 1 manages reservations for shared facilities such as conference rooms and company cars, as well as the rental of items for using these facilities, such as keys to these facilities. Hereinafter, items for using facilities that are the subject of reservations in the reservation management system 1 will be referred to as facility-related items. Furthermore, facility-related items for using a certain facility will be referred to as facility-related items for that facility. In the following, an example will be described in which the reservation management system 1 is used in a company, but the application of the reservation management system 1 is not limited to companies. For example, the reservation management system 1 may be applied to a public institution such as a city hall.

[0016] The groupware server device 100 manages facility use reservations. Specifically, the groupware server device 100 manages facility use reservations through schedule management to prevent overlapping of facility use reservations (so-called overbooking). Hereinafter, a facility use reservation will also be simply referred to as a reservation. Information indicating a facility use reservation will also be referred to as reservation information.

[0017] In the following, an example will be described in which the groupware server device 100 manages facility reservations as one function of groupware (a mechanism for supporting collaboration among multiple people). However, this is not limiting. For example, the reservation management system 1 may include a server device dedicated to facility reservation management instead of the groupware server device 100. The groupware server device 100 is configured using a computer such as a workstation (WS) or a personal computer (PC).

[0018] The item management device 200 manages facility-related items. The reservation management system 1 may include one or more item management devices 200. The collaboration device 300 collaborates with the groupware server device 100 and the item management device 200. Specifically, the collaboration device 300 controls the item management device 200 to lend facility-related items to users according to the timing of facility use, in accordance with the facility use schedule for reservations managed by the groupware server device 100. The user here is a person who is registered in the facility reservation as a user of the facility.

[0019] The linked device 300 also provides various notifications to the user, such as advance notice that the scheduled start time of use is approaching. Furthermore, the linkage device 300 generates facility usage history information and statistical information thereof based on the rental record of the facility-related item by the item management device 200. The linked device 300 is configured using a computer such as a workstation or a personal computer.

[0020] The groupware client device 400 functions as a user terminal of the groupware server device 100. In particular, a user of the reservation management system 1 makes reservations for facilities using the groupware client device 400. The groupware client device 400 is configured using a computer such as a personal computer assigned to each employee who is a user of the reservation management system 1, for example.

[0021] The internal network 500 is, for example, a local area network (LAN) such as an in-house network, and transmits communications between the groupware server device 100, the item management device 200, the collaboration device 300, the groupware client device 400, and the gateway device 600. The gateway device 600 transmits communications between the internal network 500 and the external network 700 .

[0022] The external network 700 transmits communications between the gateway device 600 and the mobile terminal device 800. The external network 700 is configured, for example, by a combination of the Internet and a mobile phone network (a communication network provided by a telecommunications carrier for mobile phone terminal devices such as smartphones). Communications are transmitted between the linked device 300 and the mobile terminal device 800 through a combination of the internal network 500, the gateway device 600, and the external network 700.

[0023] The mobile terminal device 800 receives and displays the message from the linked device 300, thereby notifying the user of the message. The mobile terminal device 800 may be, for example, a mobile phone terminal device carried by a user of the reservation management system 1. Alternatively, the mobile terminal device 800 may be configured as a device dedicated to the reservation management system 1.

[0024] The linked device 300 may send a message to the groupware client device 400 in addition to or instead of the mobile terminal device 800, and the groupware client device 400 may display the message. The groupware server device 100 and the collaboration device 300 may be configured as separate devices as shown in FIG. 1, or may be configured as an integrated device (that is, as a single device).

[0025] When a groupware system is newly introduced, hardware costs can be reduced by integrating the groupware server device 100 and the collaboration device 300 on the same server device. On the other hand, when configuring the reservation management system 1 using an existing groupware system, by configuring the groupware server device 100 and the collaboration device 300 as separate devices, the reservation management system 1 can be constructed with almost no need to make any changes to the existing groupware server device 100.

[0026] Fig. 2 is a schematic diagram showing the functional configuration of the groupware server device 100. As shown in Fig. 2, the groupware server device 100 includes a groupware-side communication unit 110, a groupware-side storage unit 180, and a groupware-side control unit 190. The groupware-side control unit 190 includes a schedule management unit 191. The groupware-side communication unit 110 communicates with other devices via the internal network 500. In particular, the groupware server device 100 is connected to and communicates with the groupware client device 400, causing the groupware client device 400 to function as a user terminal of the groupware server device 100.

[0027] The groupware-side storage unit 180 stores various data such as facility reservation information, etc. The groupware-side storage unit 180 is configured using a storage device provided in the groupware server device 100. The groupware-side control unit 190 executes various processes by controlling each unit of the groupware server device 100. The groupware-side control unit 190 is configured by a CPU (Central Processing Unit) provided in the groupware server device 100 reading and executing a program from the item management-side storage unit 212.

[0028] The schedule management unit 191 manages reservations for facilities. In particular, the schedule management unit 191 registers, updates, and deletes reservations based on user operations performed on the groupware client device 400 by a user of the reservation management system 1. Hereinafter, a person who performs any of the user operations of registering, updating, and deleting a reservation will be referred to as a reservation operator. Of the reservation operators, a person who performs the user operation of registering a reservation will be referred to as a registrant. When a reservation registration request is received from a user on the groupware client device 400, the schedule management unit 191 determines whether or not there is a schedule overlap with a registered reservation. If it determines that there is no schedule overlap, the schedule management unit 191 stores the reservation requested for registration in the groupware-side storage unit 180, thereby registering the reservation.

[0029] On the other hand, if it is determined that at least a portion of the schedule of a registered reservation overlaps with that of an existing reservation, the schedule management unit 191 does not register the reservation. In this case, the schedule management unit 191 displays a message on the groupware client device 400 indicating that the schedule of the reservation requested to be registered cannot be registered because it overlaps with the schedule of an existing reservation. The reservation schedule here refers to the schedule for facility use in the reservation.

[0030] Regarding reservation updates, when a reservation extension request is received from a user on the groupware client device 400 and there are no reservations for the requested extension period, the schedule management unit 191 extends the reservation in accordance with the extension request. When there are no reservations for the requested extension period, this means that none of the other registered reservations fall within the requested extension period.

[0031] Fig. 3 is a diagram showing an example of a reservation registration screen displayed by the groupware client device 400. The reservation registration screen shown in Fig. 3 has a usage date and time column, a facility column, a content column, a participant column, and a registrant column. The usage date and time field is a field for inputting the planned date and time when the facility is to be used. The equipment field is the input field for the equipment that you want to reserve. In the example in Figure 3, when the registrant presses the triangle mark ("▼") in the equipment field (for example, by clicking with the mouse), a list of equipment is displayed. The registrant selects the equipment that they want to reserve by clicking with the mouse, etc. Alternatively, the registrant can select equipment by entering the name of the equipment in the equipment field.

[0032] The content field is a field for inputting the content of use, such as the purpose of using the facility. The Participant column is the column where participants are entered when using the facility. In the example in Figure 3, when the registrant presses the triangle mark in the Participant column, a list of employees (list of potential participants) is displayed. The registrant can enter participants by selecting them from the list with a mouse click, etc., and pressing the Add button. Alternatively, the registrant can enter participants by entering their names in the Participant column.

[0033] The reservation management system 1 treats the participants entered in the participant field as users (joint users). For example, any participant can take out facility-related items from the item management device 200 when using the facility. The registrant column indicates the person who has registered the reservation for the use of the facility (the person who is registering). In the example of Fig. 3, the name of the person who logged in to the groupware client device 400 to register the reservation is shown in the registrant column as the name of the registrant. When the user enters the necessary information into the reservation registration screen and presses the registration button, the groupware client device 400 sends a reservation registration request to the groupware server device 100 .

[0034] FIG. 4 is a diagram showing an example of a reservation list screen displayed by the groupware client device 400. As shown in FIG. In the example of Figure 4, reservations are shown by facility, such as Conference Room 1 and Conference Room 2, and by date. As long as the times do not overlap, multiple reservations can be made for the same facility on the same day. In the example of Figure 4, multiple reservations for Conference Room 1 on August 3rd have been registered.

[0035] Fig. 5 is a schematic block diagram showing the functional configuration of the article management device 200. As shown in Fig. 5, the article management device 200 includes an article management display unit 31, an article management operation unit 32, a card reader 33, a holder 41, a storage unit 42, a cover lock mechanism 61, a full-closure detection sensor 62, an article management control unit 211, an article management memory unit 212, an alarm generator 213, and an article management communication unit 221. The holder 41 includes a key lock mechanism 76, an indicator lamp 81, an operation button 82, and an IC tag reader 85. The storage unit 42 includes the indicator lamp 81, the operation button 82, a drawer lock mechanism 92, a push-in detection sensor 98, and a presence / absence detection sensor 99. 5 also shows an IC tag 73 used in the IC tag reader 85 and an ID card 34 used in the card reader 33. The item management device 200 stores equipment-related items. As described above, the equipment-related items are items for using the equipment that is the subject of a reservation in the reservation management system 1.

[0036] FIG. 6 is a front view showing the article management device 200 with the front cover open. In the following description, "front" refers to the front side in the front-to-back direction, i.e., the front side as seen from the user's perspective, "rear" refers to the rear side in the front-to-back direction, i.e., the back side as seen from the user's perspective, "left" refers to the left side as seen from the user's perspective, and "right" refers to the right side as seen from the user's perspective.

[0037] As shown in FIG. 6, the article management device 200 includes a front cover 13 and a hinge 23 in addition to the components shown in FIG. The front side of the device body 12 is stepped so that the left side is located further back than the right side. The portion of the device body 12 from the center to the left constitutes an opening / closing section 21 that is opened and closed by the front cover 13, and the right side that protrudes forward beyond the opening / closing section 21 constitutes a front surface component 22 that is always exposed without being opened or closed by the front cover 13. One end of the front cover 13 is rotatably connected to the device body 12 via a hinge 23 provided on the left edge of the device body 12, and opens and closes the front surface of the opening / closing section 21.

[0038] The device main body 12 has an item management side display unit 31 consisting of an LCD display that displays the date and time, operating status, alarm information, guidance, etc., at the top of the front of the right-side front component 22, and below that is an item management side operation unit 32 (input unit, setting unit) where users of the item management device 200 can input characters such as numbers, katakana, and alphabets.

[0039] Also, to the right of these is provided a card reader 33 that reads data from an ID card 34 shown in Figure 5 when the ID card 34 is scanned. The goods management side display unit 31 and the goods management side operation unit 32 may be configured as an integrated touch panel. The ID card 34 consists of an electronic card with an IC chip or a magnetic card, etc., and is prepared individually for each person authorized to use the item management device 200, and stores individual user identification information, etc., for identification purposes.

[0040] The opening / closing section 21, which is opened and closed by the front cover 13 of the device main body 12, is provided with a plurality of holding sections 41 (storage sections) and a plurality of storage sections 42 (storage sections) at its front position for storing items so that they can be taken out and returned. The holding sections 41 are arranged in multiple positions, specifically ten, in the left-right direction, aligned vertically, and these ten arranged holding sections 41 are arranged in multiple tiers, specifically two tiers, vertically, i.e., in the height direction. The storage sections 42 are located below all of the holding sections 41 and are arranged in multiple positions, specifically ten, in the left-right direction, aligned vertically. However, the number and arrangement of the holding sections 41 provided in the item management device 200 are not limited to those shown in FIG. 6.

[0041] FIG. 7 is a perspective view showing the key body, the key holder, and the holder. 7, the item management device 200 has key holders 52 that hold key bodies 51 that correspond one-to-one to each other, and the holding units 41 detachably support the corresponding key holders 52. The holding units 41 hold the corresponding key holders 52 in a locked state so that they cannot be removed.

[0042] The connected key body 51 and key holder 52 constitute a key 53. The holding unit 41 holds the key holder 52, i.e., the key 53, as a holding target item (in other words, an item to be managed). The storage unit 41 stores keys 53 for facilities that are the subject of reservation in the groupware server device 100, such as a conference room key 53 and a company car key 53. These keys 53 are examples of facility-related items.

[0043] As shown in FIG. 6 , the device main body 12 has electromagnetically driven cover lock mechanisms 61 at two locations, one above the other, on the front side of the opening / closing section 21 of the device main body 12. The electromagnetically driven cover lock mechanisms 61 lock engagement portions (not shown) provided on the front cover 13 when the front cover 13 is in the closed state. The device main body 12 also has a full-closure detection sensor 62 on the front side of the opening / closing section 21 of the device main body 12 that detects whether the front cover 13 is in the fully closed state by detecting a detection portion (not shown) of the front cover 13 when the front cover 13 is in the closed state. The cover lock mechanism 61 locks the engagement portions to lock the front cover 13 in the closed state when the full-closure detection sensor 62 detects that the front cover 13 is closed. The cover lock mechanism 61 is also driven to unlock the engagement portions.

[0044] As shown in Figure 7, key holder 52 is made up of a detachable member 71 and a connecting member 72 that connects key body 51 to detachable member 71. Detachable member 71 has an IC tag 73 (shown in Figure 5) that stores individual holder identification information for distinguishing key holder 52 from other key holders 52.

[0045] As shown in Fig. 7, each of the holding parts 41 has an individual insertion hole 75 into which a detachable member 71 of a key holder 52 connected to a key main body 51 is inserted and removed. The detachable member 71 is detachable from the holding part 41 and is locked in the attached state. Each of the holding parts 41 has an electromagnetically driven key lock mechanism 76 shown in Fig. 5 that locks and supports the detachable member 71 when it is inserted into the insertion hole 75 and can also be unlocked.

[0046] 7, each of the multiple holding parts 41 has an operation button 82 integrated with an indicator lamp 81. The operation button 82 is positioned vertically adjacent to and aligned with the insertion hole 75 constituting the same holding part 41 in the left-right direction. The operation button 82 is an operation button that is pressed when releasing the lock provided by the key lock mechanism 76 shown in FIG. 5 constituting each of the same holding parts 41, and the indicator lamp 81 guides the operation by turning off, on, and flashing.

[0047] In the holding unit 41, for example, based on reservation information managed by the groupware server device 100, the indicator lamp 81 of the holding unit 41 that holds the key 53 that can be removed lights up to indicate the key 53 that can be removed. When an operation button 82 integrated with a lit indicator lamp 81 is pressed, the key lock mechanism 76 of the holding part 41 on which the operation button 82 is provided is unlocked, and the key holder 52 is removed from the holding part 41.

[0048] 5 of the attached detachable member 71, and detects the removal of the key holder 52, i.e., the key 53, by switching from a communication state to a non-communication state, and detects the return of the key 53 by switching from a non-communication state to a communication state. In this way, the IC tag reader 85 detects the removal and return of the key 53, including the key holder 52, as an article to be managed.

[0049] FIG. 8 is a perspective view of the storage section 42. As shown in FIG. As shown in Figure 8, the multiple storage sections 42 are of a drawer type, and each has a drawer member 91 that can be pulled out forward and pushed in backward, and an electromagnetically driven drawer lock mechanism 92 shown in Figure 5 that locks the pushed-in drawer member 91 so that it cannot be pulled out and can also be unlocked. The drawer member 91 is box-shaped and opens upward, and stores items that cannot be attached to the key holder 52 or that are attachable but are not suitable for holding in the holding section 41 when attached to the key holder 52.

[0050] The storage unit 42 stores items to be used when using the reserved facility, such as a fuel card, which is a corporate credit card that can be used when refueling a company vehicle, and an ETC (registered trademark) card. These items are examples of facility-related items. In the following, an example will be described in which the items stored in the item management device 200 are only facility-related items, but the item management device 200 may also store items other than facility-related items. Examples of items other than facility-related items include items for using facilities that are not subject to reservation in the groupware server device 100, and items that are used independently of specific facilities.

[0051] Each of the multiple storage sections 42 has an operation button 82 integrated with an indicator lamp 81. The operation button 82 is aligned with the drawer member 91 constituting the same storage section 42 in the left-right direction and is adjacent to it in the vertical direction. The operation button 82 is an operation button that is pressed when releasing the lock by the drawer lock mechanism 92 constituting the same storage section 42, and the indicator lamp 81 can guide the operation by turning off, on, or flashing.

[0052] In the storage unit 42, for example, based on reservation information managed by the groupware server device 100, the indicator lamp 81 of the storage unit 42 holding stored items that can be taken out lights up to indicate the stored items that can be taken out. When the operation button 82 integrated with the lit indicator lamp 81 is pressed, the drawer lock mechanism 92 (shown in Fig. 5) of the storage section 42 in which the operation button 82 is provided is unlocked, allowing the drawer member 91 to be drawn out from the storage section 42. In this state, the drawer member 91 is drawn out and the stored item is removed, and then the drawer member 91 is pushed in.

[0053] Each of the storage sections 42 has a push-in detection sensor 98 shown in Fig. 5 that detects whether the drawer member 91 is pushed in. The storage section 42 holds stored items as the items to be held. Each of the storage sections 42 has a presence / absence detection sensor 99 shown in Fig. 5 that serves as an item detection means that detects whether an item is stored in the drawer member 91. The presence / absence detection sensor 99 is a photosensor that detects the presence of an item in the drawer member 91 by blocking a light path, a weight sensor that detects the presence of an item in the drawer member 91 by detecting a change in weight on the bottom of the drawer member 91, or the like.

[0054] The item management device 200 detects the removal and return of stored items as items to be managed based on the detection of the pushed-in detection sensor 98 and the presence / absence detection sensor 99. That is, when the state changes from one in which the pushed-in detection sensor 98 detects that the drawer member 91 is pushed in and the presence / absence detection sensor 99 detects that there is an item in the drawer member 91 to one in which the pushed-in detection sensor 98 detects that the drawer member 91 is pushed in and the presence / absence detection sensor 99 detects that there is no item in the drawer member 91, it detects that an item has been removed. Also, when the state changes from one in which the pushed-in detection sensor 98 detects that the drawer member 91 is pushed in and the presence / absence detection sensor 99 detects that there is an item in the drawer member 91, it detects that an item has been returned.

[0055] 5 stores various data. The goods management side storage unit 212 is configured using a storage device provided in the goods management apparatus 200. The goods management side control unit 211 controls each unit of the goods management device 200 to perform various processes. The goods management side control unit 211 is configured, for example, by a CPU provided in the goods management device 200 reading and executing a program from the goods management side memory unit 212. The goods management side control unit 211 and the goods management side memory unit 212 may be configured using a computer such as a microcomputer. Alternatively, the goods management side control unit 211 may be configured as hardware dedicated to the goods management device 200, for example, using an ASIC (Application Specific Integrated Circuit).

[0056] The notification sound generating unit 213 generates a notification sound. The item management device 200 stores multiple equipment-related items for one piece of equipment, and if only some of the multiple equipment-related items are removed, it outputs an alarm by displaying a message on the item management display unit 31 and emitting an alarm sound from the alarm sound generating unit 213. For example, if the item management device 200 stores the keys and fuel card for one company car and only the key is removed, the item management display unit 31 displays a message indicating that the fuel card has not been removed, and the alarm sound generating unit 213 generates an alarm sound. This reduces the possibility that equipment-related items will be left out.

[0057] Furthermore, when multiple facility-related items have been removed from one facility and only some of the multiple facility-related items have been returned, the item management device 200 outputs an alarm by displaying a message on the item management display unit 31 and emitting an alarm sound from the alarm sound generating unit 213. For example, when the keys and fuel card for a company car are on loan and only the key is returned, the item management display unit 31 displays a message indicating that the fuel card has not been returned, and the alarm sound generating unit 213 generates an alarm sound. This reduces the possibility that equipment-related items will not be returned.

[0058] The method by which the item management device 200 outputs an alarm is not limited to a method using a combination of the item management display unit 31 and the alarm sound generating unit 213. For example, the item management display unit 31 may display a message without generating an alarm sound from the alarm sound generating unit 213. Alternatively, the alarm sound generating unit 213 may generate an alarm sound without displaying a message on the item management display unit 31. Alternatively, the item management device 200, or the linked device 300 that has received a notification from the item management device 200, may send a message such as an email to the user's mobile terminal device 800.

[0059] The item management side communication unit 221 communicates with other devices. In particular, the item management side communication unit 221 receives an item removal permission notification from the linked device 300. The item removal permission notification includes information indicating facility-related items that can be removed from the item management device 200 based on the reservation information and users who can remove the facility-related items. Furthermore, the item management side communication unit 221 transmits information related to the item storage status, such as item removal information and item return information, to the linkage device 300 in response to a request from the linkage device 300. For example, the item removal information is information indicating an equipment-related item removed from the item management device 200, the person who removed it, and the date and time of removal. The item return information is information indicating an equipment-related item returned to the item management device 200, the person who returned it, and the date and time of return.

[0060] FIG. 9 is a front view of the goods management side operation unit 32. As shown in FIG. As shown in FIG. 9, the goods management side operation unit 32 has a character key 231, an up key 232, a down key 233, a left key 234, a right key 235, an ENTER key 236, a character input key group 237 consisting of multiple keys, and a CE key 238, all of which detect input when pressed.

[0061] The up key 232, down key 233, left key 234, and right key 235 are pressed to move the cursor or arrow displayed on the goods management side display unit 31 in the respective directions, etc. The ENTER key 236 is pressed to confirm input, etc. The character input key group 237 is pressed to input characters such as numbers, katakana, and alphabets. The CE key 238 is pressed to erase input characters and return to the previous display screen, etc. The character key 231 is pressed to switch the character input key group 237 between number input, katakana input, and alphabet input.

[0062] Next, the procedure for lending (taking out) and returning equipment-related items in the item management device 200 will be described. In the reservation management system 1, a person who is registered as a user of the item management device 200 can open the front cover 13 of the item management device 200 at any time and can return equipment-related items at any time.

[0063] On the other hand, in the reservation management system 1, a user registers a reservation for using a facility in the groupware server device 100, and then retrieves facility-related items from the item management device 200 to use the facility. For this reason, among those who are registered as users in the item management device 200, only those who are registered as facility users in a reservation managed by the groupware server device 100 are set to be able to retrieve facility-related items from the item management device 200. As described above, not only the person who registered the reservation but also the person who is registered in the reservation as a person who will use the facility are considered users and can retrieve facility-related items from the item management device 200. Note that reservations can also be made in which the person who registered the reservation (the registrant) is not included in the users, such as when reserving facility on behalf of another person.

[0064] When the goods management device 200 is in a standby state with the front cover 13 closed, the goods management side control unit 211 causes the goods management side display unit 31 to display a standby display screen prompting the card reader 33 to scan the ID card 34. When the ID card 34 is scanned in the standby state, the card reader 33 reads out from the ID card 34 individual user identification information that is stored in advance in the ID card 34 and that is used to distinguish the user from other users.

[0065] The goods management side control unit 211 checks the user identification information read from this ID card 34 against an available user list stored in advance in the goods management side storage unit 212. The available user list is a list showing the identification information (user identification information) of users who can use the goods management device 200. Through this matching, the goods management side control unit 211 identifies the user (the person who takes out or returns the equipment-related goods) when the goods are taken out or returned. The combination of the card reader 33, the goods management side control unit 211, and the goods management side memory unit 212 corresponds to an example of a user identification unit.

[0066] If the user identification information in the available user list does not contain the same user identification information as that read from the ID card 34, the goods management side control unit 211 causes the goods management side display unit 31 to display that the goods management device 200 is not available, and causes the alarm sound generating unit 213 to generate an alarm sound for a predetermined period of time, and returns to standby mode.

[0067] If the same user identification information read from the ID card 34 is found in the user identification information on the available user list, the goods management side control unit 211 unlocks the cover lock mechanism 61 to open the front cover 13. Then, the goods management side control unit 211 displays a display screen on the goods management side display unit 31 prompting the user to input whether to remove or return the key 53 or stored item, which is the item to be held, and waits for the selection to be input.

[0068] When removal is selected, the goods management side control unit 211 turns on the indicator lamp 81 of the holding unit 41 that holds the key 53 that the user identified by the user identification information is permitted to remove in the goods removal permission notice. The goods management side control unit 211 also turns on the indicator lamp 81 of the storage unit 42 that holds the stored item that the user identified by the user identification information is permitted to remove in the goods removal permission notice. The user can remove the key 53, the stored item, or both from the holding unit 41 or storage unit 42, or both, whose indicator lamp 81 is lit. On the other hand, if the user identified by the user identification information does not have any keys 53 or stored items that are permitted to be removed in the item removal permission notice, the item management side control unit 211 does not light any of the indicator lamps 81. In this case, the user cannot remove the keys 53 or stored items from the item management device 200.

[0069] When "return" is selected from the selection input waiting state, the goods management side control unit 211 lights up the indicator lamp 81 of the holding unit 41 to which the key 53 has not been returned, and the indicator lamp 81 of the storage unit 42 to which the goods have not been returned. The user can return the equipment-related goods (key 53 or stored goods) to the holding unit 41 or storage unit 42 whose indicator lamp is lit.

[0070] Fig. 10 is a schematic block diagram showing the functional configuration of the linked device 300. As shown in Fig. 10, the linked device 300 includes a linked communication unit 310, a linked display unit 320, a linked operation unit 330, a linked storage unit 360, and a linked control unit 370. The linked control unit 370 includes a linked unit 380, a history information generation unit 391, and a statistical information generation unit 392. The linked unit 380 includes a prior notification processing unit 381, an advance processing unit 382, ​​a removal notification processing unit 383, a cancellation notice processing unit 384, a cancellation processing unit 385, a return notification processing unit 386, and a return delay processing unit 387.

[0071] The collaboration-side communication unit 310 communicates with other devices. In particular, the collaboration-side communication unit 310 acquires (receives) facility reservation information from the groupware server device 100. The collaboration-side communication unit 310 also transmits to the item management device 200 an instruction to enable facility-related items to be retrieved from the item management device 200. The collaboration-side communication unit 310 also receives record information on the retrieval (loan) and return of facility-related items from the item management device 200.

[0072] The linked display unit 320 has a display screen such as a liquid crystal panel, and displays various images. In particular, the linked display unit 320 displays a setting screen for setting up the link between the groupware server device 100 and the item management device 200, and a list screen of the settings. The cooperation-side operation unit 330 includes input devices such as a keyboard and a mouse, and receives user operations. In particular, the cooperation-side operation unit 330 receives user operations for setting up cooperation between the groupware server device 100 and the item management device 200. The linked-side display unit 320 and the linked-side operation unit 330 may be configured as a terminal device in a housing separate from the linked device 300. Alternatively, the groupware client device 400 may be configured as a terminal device of the linked device 300 and function as the linked-side display unit 320 and the linked-side operation unit 330.

[0073] The coordination-side storage unit 360 stores various types of data. For example, the coordination-side storage unit 360 stores various types of information for linking the groupware server device 100 and the item management device 200. Examples of the information stored in the coordination-side storage unit 360 for linking the groupware server device 100 and the item management device 200 include user management information, facility management information, usage status management information, and system operation setting information. The coordination-side storage unit 360 also stores reservation information acquired from the groupware server device 100.

[0074] 11 is a diagram showing an example of user management information displayed by the linked display unit 320. The user management information is information that associates a login name in the groupware server device 100 with a user ID in the item management device 200. The login name is identification information used by the groupware server device 100 to identify a user, and one login name is assigned to one user. In the user management information shown in Fig. 11, the user name shown in the user name column and the login name shown in the login name column are associated one-to-one.

[0075] The user ID is identification information used by the item management device 200 to identify the user of the item management device, and one user ID is assigned to one user for each item management device 200. The user management information shown in Fig. 11 indicates the item management devices 200 available for each user, and one user ID is indicated for each user of the item management device and for each item management device 200. By storing the user management information in the collaboration-side storage unit 360, it is possible to determine whether the user in the reservation is the same as the person attempting to retrieve a facility-related item from the item management device 200. Specifically, when the collaboration device 300 acquires reservation information from the groupware server device 100, it transmits to the item management device 200 an instruction to enable retrieval of facility-related information for the facility to be used at a timing according to the scheduled time of use of the facility. At that time, the collaboration device 300 reads a user ID indicating the user from the user management information and transmits the read user ID together with the instruction.

[0076] 12 is a diagram showing an example of facility management information displayed by the linked display unit 320. The facility management information is information that associates a facility with a storage location of facility-related items used to use the facility. 12 shows the equipment code for each piece of equipment, as well as the name and holder number of the item management device in which the equipment-related items used to use the equipment are stored. The equipment code is identification information that identifies the equipment, and one equipment code is shown for one piece of equipment.

[0077] The holder number is information that identifies a holder (holding section 41 or storage section 42) within the item management device 200. The storage location of an equipment-related item is uniquely identified by the combination of the item management device name and the holder number. In the equipment management information shown in FIG. 12, for each piece of equipment, combinations of item management device name and holder number are shown for the same number of equipment-related items used to utilize the equipment. By storing the facility management information in the coordination-side storage unit 360, the coordination device 300 can identify a storage location of the facility-related item to be used for using the facility indicated in the reservation information. Then, the coordination device 300 can transmit an instruction to the item management device 200 to make it possible to retrieve the facility-related item from the identified storage location.

[0078] 13 is a diagram showing an example of the use status management information stored in the linked display unit 320. The use status management information is information indicating whether or not a facility-related item is in the item management device 200 (whether or not it has been returned). The usage status management information shown in Figure 13 indicates, for each facility, a facility code that identifies the facility, the item management device name and holder number that indicate the storage location of facility-related items used to use the facility, and the holder status indicating whether the facility-related item has been returned. Furthermore, if a facility-related item has been returned, the last user (the most recent facility user) of the facility-related item and the last date and time of use are also indicated. The last user and last date and time of use can be, for example, the person who returned the facility-related item and the return date and time. If the equipment-related item has not been returned (if the holder status is "removed"), the person who removed the equipment-related item from the item management device 200 and the removal date and time may be used as the last user and last usage date and time.

[0079] By storing the usage status management information in the coordination side storage unit 360, the coordination device 300 can perform processing depending on whether or not a facility-related item has been returned. For example, when the scheduled start time of the next reservation approaches, if a facility-related item has been returned, the coordination device 300 instructs the item management device 200 to make the facility-related item available for the user of the next reservation to pick up. On the other hand, if a facility-related item has not been returned, the coordination device 300 notifies the user of the next reservation that the facility-related item has not been returned.

[0080] FIG. 14 is a diagram showing an example of a system operation setting screen displayed by the linked-side display unit 320. As shown in FIG. The system operation setting screen shown in FIG. 14 has an email transmission / non-transmission field, an advance pick-up time field, a cancellation time field, an advance notice of completion time field, and a return reminder time field. In the "Email Transmission" field, a setting is made as to whether or not the linked device 300 will transmit various notification emails to the user.

[0081] The advance take-out time field is used to set an advance take-out time. The user can take out facility-related items from the item management device 200 from the advance take-out time before the start time of the reserved facility use. In the cancellation time field, whether or not to automatically cancel the reservation is set, and the cancellation notice time and cancellation time when the reservation is automatically canceled are set.

[0082] If the setting is such that the reservation is automatically canceled, the coordinating device 300 determines whether the equipment-related items for the reserved facility have already been removed from the item management device 200 when the cancellation notice time has elapsed from the scheduled start time of use in the reservation. If it determines that the equipment-related items have not been removed, the coordinating device 300 sends a notice of reservation cancellation by email to the user's mobile terminal device 800.

[0083] Furthermore, the coordinating device 300 determines whether or not the equipment-related items for the reserved equipment have already been removed from the item management device 200 when the cancellation time has elapsed from the scheduled start time of use in the reservation. If it is determined that the equipment-related items have not been removed, the coordinating device 300 cancels (cancels) the reservation.

[0084] By canceling the reservation by the linked device 300, another user can set a new reservation for the reserved time period. The user with the newly set reservation can use the facility, which improves the utilization rate of the facility.

[0085] The notice of end time field is where the notice of end time is set. The linked device 300 sends the user an email message informing them that the scheduled end time of the reservation is approaching before the notice of end time of the scheduled end time of the reservation. The user can refer to this email and take appropriate action. For example, if the facility is a conference room and the user is holding a meeting, the user can see the message that the scheduled end time is approaching and speed up the progress of the meeting to end it early. Also, if the facility is a company vehicle and the user is caught in traffic, the user can determine whether they will be able to return to the office by the scheduled end time, and if they determine that they will not be able to return by the scheduled end time, they can contact the company to inform them that they will be late.

[0086] The cooperation-side control unit 370 executes various processes by controlling each unit of the cooperation device 300. The cooperation-side control unit 370 is configured, for example, by the CPU included in the cooperation device 300 reading and executing a program from the cooperation-side storage unit 360. The linking unit 380 performs processing for linking the groupware server device 100 and the item management device 200 together. If the facility-related item has not been returned to the item management device 200 a predetermined advance notification time before the scheduled start time of use, the advance notification processing unit 381 notifies the user by email that the facility-related item has not been returned. The advance notification time here is set in advance as a predetermined time indicating the timing for notifying the user prior to the scheduled start time of use. For example, if the user is notified five minutes before the scheduled start time of use, the advance notification time is set to five minutes.

[0087] 15 is a diagram showing an example of a "rented" email sent by the advance notification processing unit 381. The "rented" email is an email notifying that a facility-related item has not been returned. 15, the advance notification processing unit 381 notifies the user that the key to the reserved first conference room has not been returned. Furthermore, the advance notification processing unit 381 also informs the user of other available facilities in this email. The user who receives this notification can avoid wasting time and effort by visiting the item management device 200 to retrieve the equipment-related item. Also, the user who receives this email can take action, such as rebooking another piece of equipment.

[0088] On the other hand, if the equipment-related item is returned to the item management device 200 a predetermined notification time before the scheduled start time of use, the advance notification processing unit 381 notifies the user by email that the equipment is now available for use. Upon receiving this notification, the user can remove the facility-related item from the item management device 200 and start using the facility.

[0089] If equipment-related items for a certain piece of equipment are returned to the item management device before the scheduled end time of use, and if the next reservation for that equipment is registered within a specified advance time after the scheduled end time of use, the advance processing unit 382 notifies the user of the next reservation by email that the equipment can be used early.

[0090] 16 is a diagram showing an example of an advance availability email sent by the advance availability processing unit 382. The advance availability email is an email notifying that the facility can be used in advance. In the email shown in FIG. 16, the advancement processing unit 382 notifies the user that the reserved first conference room can be used earlier. In this case, the user or other person who registered the reservation may have set the scheduled start time to match the immediately preceding reservation, and may have wanted to start earlier if there were no immediately preceding reservations. In this case, the user who received the notification can start using the facility (Conference Room 1) earlier as desired.

[0091] In this case, the advance processing unit 382 may advance the scheduled start time of use for the next reservation (for example, the reservation that is the subject of the email in FIG. 16). This allows the user to use the facility from an earlier time without having to change the reservation. When the advance processing unit 382 automatically advances the scheduled start time of use, the original scheduled start time of use may be used as the basis for canceling the reservation so as not to put the user at a disadvantage.

[0092] Alternatively, the advance processing unit 382 may instruct the groupware server device 100 to stop new registrations of reservations for the facility prior to the next reservation (for example, the reservation that is the subject of the email in Figure 16) by anyone other than the user of the next reservation. This makes it possible to avoid a situation where, when a user attempts to advance the next reservation for use of the facility, the advance cannot be made because another reservation has been registered.

[0093] Alternatively, the advance processing unit 382 may instruct the item management device 200 to allow the user of the next reservation (for example, the reservation that is the subject of the email in Figure 16) to pick up the equipment-related items immediately (without waiting a specified time before the scheduled start time of use). This allows the user making the next reservation to use the facility from an earlier time without having to change the reservation.

[0094] When there are multiple users in a reservation and an equipment-related item is removed from the item management device 200, the removal notification processing unit 383 notifies by email at least those users other than the remover identified by the item management device 200 that the equipment-related item has been removed. 17 is a diagram showing an example of a taken-out notification email sent by the take-out notification processing unit 383. The taken-out notification email is an email notifying that a facility-related item has been taken out.

[0095] In the email shown in FIG. 17, the removal notification processor 383 notifies that the reserved key to the first conference room has been removed. Upon receiving this notification, the user can head to the facility (the first conference room in the example of FIG. 17) without trying to remove the facility-related item from the item management device 200. This can prevent the user from wasting time and effort by trying to remove the facility-related item from the item management device 200.

[0096] If no equipment-related item is removed from the item management device 200 within a predetermined cancellation notice time that is shorter than the cancellation time from the scheduled start time of use, the cancellation notice processing unit 384 notifies the user by email of the reservation cancellation notice. 18 is a diagram showing an example of a cancellation notice email sent by the cancellation notice processing unit 384. The cancellation notice email is an email that notifies the user that a reservation will be canceled.

[0097] In the mail shown in FIG. 18, the cancellation notice processor 384 notifies the user that the reservation will be canceled if the facility-related item is not removed within a predetermined time. Upon receiving this notification, the user can take action such as retrieving the facility-related item from the groupware server device 100 within the specified time or changing the reservation.

[0098] If the equipment-related item is not removed from the item management device 200 until a predetermined cancellation time has elapsed from the scheduled start time of use in the equipment reservation, the cancellation processing unit 385 causes the schedule management unit 191 of the groupware server device 100 to cancel the reservation. The cancellation processing unit 385 causes the schedule management unit 191 to cancel the reservation, so that another user can make a new reservation for the reserved time period. The user who makes the new reservation can use the facility, which improves the utilization rate of the facility.

[0099] If the scheduled start time of use is updated within the reservation time range between the scheduled start time of use and the cancellation time has elapsed, the cancellation notice processing unit 384 and the cancellation processing unit 385 stop processing based on the scheduled start time of use before the update and perform processing based on the scheduled start time of use after the update. Therefore, the user can avoid canceling the reservation by delaying the scheduled start time of use.

[0100] When there are multiple users for a reservation and an equipment-related item is returned to the item management device 200, the return notification processing unit 386 notifies at least one of the multiple users other than the returner identified by the item management device 200 that the equipment-related item has been returned. 19 is a diagram showing an example of a returned notification email sent by the return notification processing unit 386. The returned notification email is an email notifying that the equipment-related item has been returned. In the email shown in FIG. 19, the return notification processor 386 notifies that the reserved key to the first conference room has been returned. Upon receiving this notification, the user can confirm that the equipment-related items have been returned.

[0101] If an equipment-related item has not been returned to the item management device 200 after a specified return reminder time has elapsed from the scheduled end time of use for the reservation, the return delay processing unit 387 notifies the user of a return reminder and causes the schedule management unit 191 of the groupware server device 100 to stop registering new reservations for the equipment. 20 is a diagram showing an example of a return reminder email sent by the return delay processing unit 387. The return reminder email is an email reminding the return of equipment-related items.

[0102] In the email shown in FIG. 20, the return delay processor 387 urges the user to return the key to the first conference room. It is expected that the user who receives this notification will return the facility-related item to the item management device 200 as soon as possible. In addition, the return delay processing unit 387 causes the schedule management unit 191 to stop registering new reservations for the facility, allowing users to avoid the facility, which is relatively likely to be unavailable, and reserve other facilities instead.

[0103] The history information generating unit 391 generates facility usage history information based on the history of taking out and returning facility-related items from the item management device 200. FIG. 21 is a diagram showing an example of a display screen of the usage history information displayed by the linked-side display unit 320. As shown in FIG. The screen shown in Fig. 21 has columns for the target period, holder group, facility, and item management device. Below these columns, a display area for the usage history is provided.

[0104] The target period field is a field for specifying the period for which the usage history is to be displayed. The holder group field is a field for inputting the holder group name when specifying the holder group for which the usage history is to be displayed. The holder group here refers to one or more holders in the item management device 200 grouped together. The facility field is a field for inputting the facility name when the facility is specified as the target for displaying the usage history. The goods management device field is an input field for the name of the goods management device when specifying the goods management device for which the usage history is to be displayed. Those who wish to refer to the usage history do not need to fill in all of these fields; they can simply enter information in the fields for which they wish to specify a range and press the output button.

[0105] In the usage history displayed in the usage history display area, each row shows the usage history information for one reservation. For each reservation, the holder group name, item management device name, holder number, facility name, pick-up date and time, return date and time, organization name, and facility user name are displayed. The storage location of the equipment-related item is indicated by the combination of the item management device name and the holder number. The equipment used is indicated by the equipment name. In addition, the pick-up date and time and return date and time of the equipment-related item in the item management device 200 are indicated, indicating the actual date and time when the equipment was used, rather than the planned use in the reservation. The equipment user is indicated by the combination of the organization name and the equipment user name. The facility users here may be all users (everyone who has used the facility) or a portion of the users, such as those who retrieve or return facility-related items. In addition, the usage history may be configured to show the scheduled start time and scheduled end time of the reservation in association with the pick-up date and time and return date and time of the equipment-related item in the item management device 200. By comparing the reservation time with the actual equipment usage time and calculating the difference between them, it is possible to grasp the amount of unused reservation time. The linkage device 300 may identify users who are likely to have this tendency and notify the mobile terminal device 800 of the users by a message such as an email to encourage them to make appropriate reservations.

[0106] The statistical information generating unit 392 generates statistical information on the usage history of the facility. For example, the statistical information generating unit 392 generates statistics on individual facility usage. FIG. 22 is a diagram showing an example of display of individual facility usage statistics by the linked display unit 320. In FIG. The usage statistics shown in Figure 22 show the total usage time for one month, the number of times used, and the average usage time per time for each facility and for each individual. The values ​​for each department and for all usage of each facility are also shown.

[0107] The utilization rate column displays the percentage of time an individual or organization is using the facility compared to the total time the facility is being used. In this way, the statistical information generating unit 392 generates statistical information on the usage history of the equipment, and the equipment manager can refer to this statistical information to understand the usage status of the equipment. By understanding the usage status of the equipment, the equipment manager can take measures such as improving the usage rate of equipment with low utilization rate or abolishing the equipment. Furthermore, by referring to the statistical information on facility usage history generated by the statistical information generating unit 392, it is possible to consider ways to improve work efficiency, such as shortening meeting times.

[0108] The statistical information on facility usage history generated by the statistical information generating unit 392 is not limited to the individual statistical information shown in FIG. 22, but may be various other information. For example, the statistical information generating unit 392 may generate organization-specific usage statistics for the facility.

[0109] FIG. 23 is a diagram showing an example of the display of facility usage statistics by organization by the linked-side display unit 320. In FIG. The usage statistics shown in Figure 23 show the total usage time for one month, the number of times used, and the average usage time per use, for each facility and each organization. The display items in the usage statistics shown in Figure 23 are the same as those in Figure 22, except that there are no items that identify individuals (for example, individual names). In this way, the statistical information generating unit 392 generates facility usage statistics by organization, which enables billing measures such as recording facility usage fees as organizational expenses according to the facility usage rate. Also, as in the case of Fig. 22, it is possible to consider points for improving work efficiency, such as shortening meeting times.

[0110] Alternatively, the statistical information generating unit 392 may generate usage statistics for each facility holder group. FIG. 24 is a diagram showing an example of display of facility usage statistics by holder group on the linked-side display unit 320. In FIG. In the usage statistics shown in FIG. 24, the facilities are displayed categorized into holder groups such as "Head office conference room," "Head office company car," "Head office bicycle," and "Head office other." For example, the first and second conference rooms are classified as the main conference room, and their usage statistics are displayed consecutively. Furthermore, the usage statistics for the first and second conference rooms are combined and displayed as the usage statistics for the main conference room.

[0111] The holder group is set by the user. FIG. 25 is a diagram showing an example of a display of a holder group setting screen on the linked-side display unit 320. As shown in FIG. The holder group setting screen shown in Figure 25 displays a holder group ID column, a holder group name column, and a display order column, and further displays an equipment group column, an item management device column, and an equipment column as selection columns for the target equipment.

[0112] Enter the holder group ID in the Holder Group ID field. The holder group ID is used as identification information for the holder group. A holder group name is input in the holder group name field. The linked device 300 uses the input holder group name to display a usage statistics screen by holder group, for example, as shown in FIG.

[0113] In the Display Order field, enter the display order of the holder group (hierarchical relationship with other holder groups). The smaller the display order value, the higher the display order in the usage statistics by holder group. The facility group field is a field for selecting a facility according to the grouping when the facilities have already been grouped in the groupware. In the item management device field, if the equipment has already been registered in the item management device, DeviceThis is a field for selecting equipment based on the The equipment column is a column for directly selecting equipment from the equipment name. The user can select the facility using any of these three fields, and does not need to enter information in all three fields.

[0114] 26 is a diagram showing an example of a holder group management screen displayed by the linked-side display unit 320. The holder group management screen displays a list of the holder group names, holder group IDs, and display order of registered holder groups. Each holder group name can be selected by clicking the mouse, etc. When one of the holder groups is selected, the linked display unit 320 displays the holder group registration screen along with information about the selected holder group. In this state, the linked device 300 accepts updates to the holder group being displayed. Furthermore, when the new registration button on the holder group management screen is pressed, the linked display unit 320 displays the holder group registration screen and accepts the registration of a new holder group.

[0115] Fig. 27 is a diagram showing an example of displaying information on frequently used facilities by the linked display unit 320. In the example of Fig. 27, the linked display unit 320 displays information on the three facilities ranked in descending order of usage time: the first conference room, the second conference room, and company car 1. The display items are the same as in Fig. 24: holder group, item management device name, holder No., facility name, usage time, usage rate, number of uses, and average usage time.

[0116] Fig. 28 is a diagram showing an example of displaying information on less used facilities by the linked display unit 320. In the example of Fig. 27, the linked display unit 320 shows information on Bicycle B, Seminar Room, and Bicycle A as the top three facilities in order of least usage time. The display items are the holder group, item management device name, holder No., facility name, usage time, usage rate, number of uses, and average usage time, as in Fig. 24.

[0117] Next, the operation of the reservation management system 1 will be described with reference to FIGS. FIG. 29 is a sequence diagram showing an example of a processing procedure in which the reservation management system 1 receives a reservation for equipment and handles the removal of equipment-related items. In the process of FIG. 29, the user performs a facility reservation operation on the groupware facility reservation screen of the groupware client device 400 (sequence S111), and the groupware server device 100 registers the reservation information (sequence S112).

[0118] Furthermore, the groupware server device 100 transmits reservation information to the coordination device 300 in response to a request from the coordination device 300 (sequence S113). The coordination device 300 stores the reservation information received from the groupware server device 100 in the coordination-side storage unit 360 and monitors the stored reservation information. When the coordination device 300 detects that the advance notification time of the scheduled start time of use in the reservation information has arrived (sequence S114), it detects the removal status of the facility-related item in the item management device 200 (sequence S115). In the example of FIG. 29, the coordination device 300 detects that the facility-related item exists in (has been returned to) the item management device 200. The advance notification time in sequence S114 is referred to as a first advance notification time.

[0119] The coordinating device 300 detects the removal status of facility-related items by referring to the usage status management information described with reference to Fig. 13. For example, every time a facility-related item is removed or returned, the item management device 200 notifies the coordinating device 300 in real time of the removal or return of the facility-related item. The coordinating device 300 updates the usage status management information in real time in response to the notification from the item management device 200. This makes it possible to detect the removal status of facility-related items by referring to the usage status management information.

[0120] The coordinating device 300, which has detected the presence of the facility-related item, sends a preparation completion email to the mobile terminal devices 800 of all registered users (sequence S116). The preparation completion email here is an email notifying that the facility-related item can be retrieved. Since any user can retrieve the facility-related item from the item management device 200, the coordinating device 300 sends the preparation completion email to all users. The user's mobile terminal device 800 displays the received preparation completion email (sequence S117). The preparation completion email is sent between the advance notification time of the scheduled start time of use in the reservation information and the scheduled end time of use, and at the timing when the item management device 200 detects that a facility-related item is present. In other words, there may be cases where the preparation completion email is sent after the scheduled start time of use.

[0121] The linking device 300 also instructs the item management device 200 to set up the device so that the user can retrieve equipment-related items (sequence S118). The item management device 200 sets up the device so that the user can retrieve equipment-related items according to the instruction from the linking device 300 (sequence S119). Specifically, the user is authenticated by inputting their user ID into the item management device 200 and passing their ID card through a card reader. Once authenticated, the door of the item management device 200 can be opened, and the user can retrieve equipment-related items for the reserved equipment.

[0122] When the user removes the facility-related item from the item management device 200 (sequence S120), the item management device 200 notifies the linkage device 300 of the removal of the facility-related item. As a result, the linkage device 300 detects the removal of the facility-related item (sequence S121). The linked device 300, which has detected that the facility-related item has been removed, transmits a removed notification email to all users (sequence S122). The removed notification email here is an email notifying that the facility-related item has been removed. Alternatively, the linked device 300 may transmit the retrieval notification email to a user other than the retriever (the person who retrieved the facility-related item). The user's mobile terminal device 800 displays the received retrieval notification mail (sequence S123).

[0123] FIG. 30 is a sequence diagram showing an example of a processing procedure when the equipment-related item has not been returned when the advance notification time comes before the scheduled start time of use. Sequences S161 to S164 in Figure 30 are the same as sequences S111 to S114 in Figure 29. After sequence S164, the coordinating device 300 detects the removal status of the equipment-related items in the item management device 200 (sequence S165), similar to sequence S115 in Figure 29. However, unlike the case in Figure 29, here the coordinating device 300 detects that there are no equipment-related items. The advance notification time in sequence S164 is referred to as a second advance notification time. The second advance notification time may be the same as the first advance notification time, or may be different from the first advance notification time.

[0124] The linked device 300, which detects that the equipment-related item is missing, sends a "rented out" email to the mobile terminal devices 800 of all registered users (sequence S166). The "rented out" email here is an email notifying that the previous equipment user has not returned the equipment-related item. In this case, the user cannot retrieve the equipment-related item even if they operate the item management device 200. By referring to the "rented out" email, the user can avoid making a pointless trip to the item management device 200. Furthermore, the user will know that the equipment they reserved is unavailable and can take alternative measures, such as reserving another piece of equipment. The user's mobile terminal device 800 displays the received email (sequence S167).

[0125] Fig. 31 is a sequence diagram showing a first example of the processing procedure leading to cancellation of facility reservation by the groupware server device 100. Fig. 31 shows an example of a case where facility reservation is set to be cancelled without notice. The processing in FIG. 31 shows processing from a state where the facility is available but the facility-related item has not been removed from the item management device 200, such as after sequence S119 in FIG.

[0126] In the process of Figure 31, when the coordinating device 300 detects that a predetermined cancellation time has elapsed since the scheduled start time of use (or the time of the preparation completion email notification if the preparation completion email notification is received after the scheduled start time of use) (sequence S211), it detects the removal status of the facility-related item in the item management device 200 (sequence S212). In the example of Figure 31, the coordinating device 300 detects that there is a facility-related item. Therefore, the user has not yet removed the facility-related item from the item management device 200.

[0127] The linked device 300, which has detected that there is a facility-related item in the item management device 200, sends a cancellation notification email to the mobile terminal devices 800 of all users registered as users (sequence S213). The cancellation notification email here is an email notifying that the reservation will be canceled. The user's mobile terminal device 800 displays the received cancellation notification email (sequence S214).

[0128] The collaboration device 300 also instructs the groupware server device 100 to cancel the reservation (sequence S215). The groupware server device 100 cancels the reservation in accordance with the instruction from the collaboration device 300 (sequence S216). Furthermore, the linked device 300 instructs the item management device 200 to cancel the setting that allows the user to take out the equipment-related item (sequence S217). The item management device 200 cancels the setting that allows the user to remove the equipment-related item in accordance with the instruction from the linkage device 300 (sequence S218).

[0129] Fig. 32 is a sequence diagram showing a second example of the processing procedure leading to cancellation of facility reservation by the groupware server device 100. Fig. 32 shows an example of a setting in which facility reservation is cancelled after advance notice. The processing in FIG. 32 shows processing from a state where the facility is available but the facility-related item has not been removed from the item management device 200, such as after sequence S119 in FIG.

[0130] 32, when the linked device 300 detects that the cancellation notice time has passed since the scheduled start time of use (sequence S261), it detects the removal status of the equipment-related items in the item management device 200 (sequence S262). The cancellation notice time here is set to a time shorter than the cancellation time. 32, the linked device 300 detects that there is an equipment-related item. Therefore, the user has not yet removed the equipment-related item from the item management device 200.

[0131] The linked device 300, which has detected that there is a facility-related item in the item management device 200, sends a cancellation notice email to the mobile terminal devices 800 of all users registered as users (sequence S263). The cancellation notice email here is an email notifying users that the reservation will be canceled. The user's mobile terminal device 800 displays the received cancellation notice email (sequence S264). The sequences S265 to S272 are similar to the sequences S211 to S218 in FIG.

[0132] FIG. 33 is a flowchart showing an example of a processing procedure in which the item management device 200 outputs an alarm for an equipment-related item that has not been removed. When an operation to remove an equipment-related item is performed, the item management device 200 determines whether any equipment-related items have been removed, and outputs an alarm if it determines that any equipment-related items have been removed. In particular, when there are multiple equipment-related items for scheduled equipment, the item management device 200 determines whether all of these multiple equipment-related items have been removed, and outputs an alarm if it determines that any equipment-related items have been removed. Hereinafter, all of the equipment-related items for a certain piece of equipment will be referred to as a set. A set may include one or more equipment-related items.

[0133] 33, the item management device 200 checks the removal status of the facility-related items (step S311). Specifically, the item management device 200 identifies the user who operated the item management device 200 through authentication processing of the user. The item management device 200 also receives notification from the linked device 300 of the facility-related items that the identified user is permitted to remove. The item management device 200 makes the facility-related items notified by the linked device 300 available for removal and waits for removal.

[0134] When the door of the item management device 200 itself is closed, the item management device 200 determines, for each of the equipment-related items notified by the linked device 300, whether or not the equipment-related item has been removed. Then, the item management device 200 determines whether all of the equipment-related items (the set of equipment-related items) notified by the linked device 300 have been removed (step S312). If it is determined that all of the equipment-related items have been removed (step S312: YES), the processing of FIG. 33 ends.

[0135] On the other hand, if it is determined that there is an equipment-related item that has not been taken out among the equipment-related items notified by the linkage device 300 (step S312: NO), the item management device 200 outputs an alarm to the effect that there is an equipment-related item that has not been taken out (step S313). After step S313, the processing of FIG. 33 ends.

[0136] Fig. 34 is a sequence diagram showing a first example of the procedure of processing when returning a facility-related item performed by the linked device 300. Fig. 34 shows an example in which the facility-related item is returned around the scheduled end time of use in the reservation. 34, when the coordinating device 300 detects that the predicted end time has come before the scheduled end time of the reservation (sequence S411), it detects the removal status of the equipment-related items in the item management device 200 (sequence S412). In the example of FIG. 34, the coordinating device 300 detects that there are no equipment-related items (they have not been returned to the item management device 200).

[0137] The linked device 300, which has detected that the facility-related items have not been returned to the item management device 200, sends an email to all users informing them that the scheduled end time of use is approaching (Sequence S413). The email informing them that the scheduled end time of use is approaching the notice of the scheduled end time of use. The user's mobile terminal device 800 displays the received email indicating that the usage is about to end (sequence S414).

[0138] Thereafter, the coordinating device 300 monitors the return of the facility-related item (sequence S415). The coordinating device 300 continues monitoring until it detects that the facility-related item has been returned. In the example of Fig. 34, the coordinating device 300 detects that the facility-related item has been returned and ends the process of sequence S417. If multiple equipment-related items have been rented for the equipment that is the subject of the reservation, the linked device 300 continues monitoring until it detects that all of the multiple equipment-related items have been returned.

[0139] The linked device 300, which has detected that the facility-related item has been returned, sends a return completion notification email to all users (sequence S416). The return completion notification email here is an email notifying that the facility-related item has been returned. Alternatively, the linked device 300 may transmit the return completion notification email to a user other than the returner (the person who returned the equipment-related item). The user's mobile terminal device 800 displays the received return completion notification email (sequence S417).

[0140] The collaboration device 300 also notifies the groupware server device 100 of the return information (sequence S418). The return information here is information indicating the return of the facility-related item. For example, the return information includes the returned facility-related item, the date and time of return, and the identification information of the returner. The groupware server device 100 records the return information received from the collaboration device 300 (sequence S419).

[0141] Fig. 35 is a sequence diagram showing a second example of the procedure of the process when returning the facility-related item performed by the linking device 300. Fig. 35 shows an example in which the return of the facility-related item is delayed. In the process of Fig. 35, the linked device 300 monitors the return of the facility-related item (sequence S461). In the example of Fig. 35, the facility-related item has not been returned until the return reminder time has elapsed from the scheduled end time of use.

[0142] In this case, the cooperating apparatus 300 transmits a return reminder email to all users (sequence S462). The return completion notification email here is an email reminding the users to return the equipment-related items. The user's mobile terminal device 800 displays the received return reminder email (sequence S463).

[0143] The collaboration device 300 also notifies the groupware server device 100 that the facility-related item has not been returned (sequence S464). In response to the notification from the coordinating device 300, the groupware server device 100 stops accepting reservations for the facility for which the facility-related items have not been returned (sequence S465). For example, the groupware server device 100 stops accepting reservations for a schedule in which the expected start time for use is within one day of receiving the notification from the coordinating device 300.

[0144] The coordinating device 300 continues to monitor the return of the facility-related item (sequence S466). As described above, the coordinating device 300 continues monitoring until it detects the return of the facility-related item. In sequence S466, the coordinating device 300 also detects the return of the facility-related item and ends monitoring. The linked device 300, which has detected that the equipment-related item has been returned, transmits a return completion notification email to all users (sequence S467). The user's mobile terminal device 800 displays the received return completion notification email (sequence S468).

[0145] The collaboration device 300 also notifies the groupware server device 100 of the return information (sequence S469). The groupware server device 100 records the return information received from the collaboration device 300 (sequence S470). Furthermore, the groupware server 100 cancels the suspension of reservation acceptance set in sequence S465 (sequence S471).

[0146] Fig. 36 is a sequence diagram showing a third example of the procedure of the process when returning a facility-related item performed by the linked device 300. Fig. 35 shows an example in which the facility-related item is returned before the scheduled end time of use. 36, the coordinating device 300 monitors the return of the facility-related item (sequence S511). Here, the coordinating device 300 detects the return of the facility-related item before the scheduled end time of use.

[0147] The coordinating device 300 that has detected the return of the equipment-related item transmits a return completion notification email to all users (sequence S512). Alternatively, the coordinating device 300 may transmit the return completion notification email to users other than the user who returned the equipment-related item. The user's mobile terminal device 800 displays the received return completion notification email (sequence S513).

[0148] The groupware server device 100 that has received the return information records the return information (sequence S515). Furthermore, the groupware server device 100 changes the schedule in accordance with the return information (sequence S516). Specifically, the groupware server device 100 advances the scheduled end time of the reservation for the facility to which the facility-related item has been returned to the time when the facility-related item is returned.

[0149] The coordinating device 300 also checks (determines) whether or not there is a next user by referring to the schedule managed by the groupware server device 100 (sequence S517). For example, the coordinating device 300 checks whether or not there is a schedule within three hours of the scheduled end time of use before the earlier date. In the example of FIG. 36, the coordinating device 300 detects the next user. The linked device 300 that has detected the next user advances the time at which the detected next user can take out the facility-related item (sequence S518).

[0150] When the advanced time arrives, the cooperating device 300 transmits a take-out availability notification email to all users (sequence S519). The take-out availability notification email here is an email notifying that the facility-related item is now available for take-out. The user's mobile terminal device 800 displays the received notification mail that the item is ready for retrieval (sequence S520).

[0151] 37 is a flowchart showing an example of a processing procedure in which the item management device 200 outputs an alarm for a missed return of an equipment-related item. When an operation to return an equipment-related item is performed, the item management device 200 determines whether any items have been returned, and outputs an alarm if it determines that any items have been returned. In particular, when there are multiple equipment-related items, the item management device 200 determines whether all of the multiple equipment-related items have been returned, and outputs an alarm if it determines that any items have not been returned.

[0152] 37, the item management device 200 checks the return status of the facility-related items (step S561). Here, the item management device 200 receives an instruction from the linkage device 300 regarding the facility-related items that the user should be able to take out. The item management device 200 is notified of information about the facility-related items in the set by the instruction from the linkage device 300.

[0153] When the goods management device 200 receives the return of the equipment-related item and closes its own door, it determines whether or not each of the equipment-related items that are set with the returned equipment-related item has been returned. Then, the item management device 200 determines whether all of the equipment-related items in the set have been returned (step S562). If it is determined that all of the equipment-related items have been returned (step S562: YES), the processing of FIG. 37 ends. On the other hand, if it is determined that there is an equipment-related item that has not been returned among the equipment-related items in the set (step S562: NO), the item management device 200 outputs an alarm that there is an equipment-related item that has not been returned (step S563). After step S563, the processing of FIG. 37 ends.

[0154] As described above, the item management device 200 stores facility-related items (such as keys) for using the facility. The schedule management unit 191 manages facility reservations. When the coordination unit 380 detects that a facility-related item is present in the item management device 200 a predetermined first advance notification time before the scheduled start time of facility use in the facility reservation, the coordination unit 380 notifies the user who has reserved the facility that the facility-related item is now available for retrieval, and instructs the item management device 200 to set the facility-related item so that the user can retrieve it. The linking unit 380 detects that a facility-related item is present in the item management device 200 and notifies the user, so that the user knows that the time to start using the facility is approaching and understands that the facility is available for use. This prevents a situation in which a user forgets to make a reservation and the reserved facility goes unused. In addition, it is expected that user convenience will be improved in that the user will not end up wasting their time trying to retrieve a facility-related item from the item management device 200 because the facility-related item is not there. In this respect, the reservation management system 1 can manage the lending of items such as keys according to a set schedule, and can also improve the utilization rate of items to be lent.

[0155] Furthermore, if the equipment-related item is not removed from the item management device 200 until a predetermined cancellation time has elapsed from the scheduled start time of use, the linking unit 380 notifies the user that the reservation will be cancelled and causes the schedule management unit 191 to cancel the reservation. When the schedule management unit 191 cancels a reservation in accordance with an instruction from the linking unit 380, it becomes possible to register a new reservation for the time period for which the reservation was canceled and use the facility. In this respect, the reservation management system 1 can manage the lending of items such as keys according to a set schedule, and can also improve the utilization rate of items to be lent.

[0156] In addition, if the equipment-related item is not removed from the item management device 200 within a predetermined cancellation notice time that is shorter than the cancellation time from the scheduled start time of use, the linking unit 380 notifies the user of the cancellation of the reservation. This reduces the possibility that a user will be disadvantaged by a sudden cancellation of their reservation. When a user receives a reservation cancellation notice, they can take action, such as removing any equipment related items before their reservation is canceled or registering a new reservation.

[0157] Furthermore, if the scheduled start time of use is updated within the reservation time range between the scheduled start time of use and the elapse of the cancellation time, the linking unit 380 stops processing based on the scheduled start time of use before the update and performs processing based on the scheduled start time of use after the update. This allows the user to avoid canceling the reservation by postponing the scheduled start time of use.

[0158] In addition, if the equipment-related item has not been returned to the item management device 200 a predetermined second advance notification time before the scheduled start time of use, the linking unit 380 notifies the user that the equipment-related item has not been returned. If the equipment-related items have not been returned, the user will not be able to retrieve the equipment-related items even if he or she visits the item management device 200, resulting in a wasted trip. In response to this, the linking unit 380 notifies the user that the equipment-related items have not been returned, allowing the user to avoid wasting time by visiting the item management device 200. Furthermore, the user can take measures such as reserving other equipment as a countermeasure for not being able to use the reserved equipment.

[0159] Furthermore, the user identification unit (combination of the card reader 33, the item management side control unit 211, and the item management side memory unit 212) of the item management device 200 identifies the person who removed the equipment-related item when it is removed. When there are multiple users in the reservation and an equipment-related item is removed from the item management device 200, the linking unit 380 notifies at least one of the multiple users other than the remover identified by the item management device 200 that the equipment-related item has been removed. This allows the user to know that the equipment-related item has already been taken out. By knowing that the equipment-related item has already been taken out, the possibility that the user will have to go to the item management device 200 to take out the equipment-related item in person and end up wasting their time can be reduced.

[0160] Furthermore, the item management device 200 stores a plurality of the equipment-related items for one piece of equipment, and outputs an alarm when only some of the equipment-related items are taken out. This reduces the possibility that equipment-related items will be left out.

[0161] Furthermore, the linking unit 380 notifies the user that the scheduled end time of use is approaching, a predetermined time before the scheduled end time of use in the reservation. The user can refer to this email and take appropriate action. For example, if the facility is a conference room and the user is holding a meeting, the user can see the message that the scheduled end time is approaching and speed up the progress of the meeting to end it early. Also, if the facility is a company vehicle and the user is caught in traffic, the user can determine whether they will be able to return to the office by the scheduled end time, and if they determine that they will not be able to return by the scheduled end time, they can contact the company to inform them that they will be late.

[0162] Furthermore, when a request for extending a reservation is received and there is no reservation for the requested extension period, the schedule management unit 191 extends the reservation in accordance with the extension request. This allows users to continue using the facilities. In this respect, the reservation management system 1 allows for flexible operation of the facilities.

[0163] In addition, if the equipment-related item has not been returned to the item management device 200 after a specified return reminder time has elapsed from the scheduled end time of use for the reservation, the collaboration unit 380 notifies the user of a return reminder and causes the schedule management unit 191 to stop registering new reservations for the equipment. The linking unit 380 urges the user to return the equipment-related items, which is expected to result in the equipment-related items being returned. Also, the schedule management unit 191 stops the registration of new reservations for the equipment, which can prevent a situation in which a new reservation for the equipment is registered but the equipment-related items are not returned and the equipment cannot be used. The user can take countermeasures such as reserving another equipment instead of the equipment in question.

[0164] Furthermore, the user identification unit (combination of the card reader 33, the item management side control unit 211, and the item management side memory unit 212) of the item management device 200 identifies the returner when the equipment-related item is returned. When there are multiple users in the reservation and the equipment-related item is returned to the item management device 200, the linking unit 380 notifies at least one of the multiple users other than the returner identified by the item management device 200 that the equipment-related item has been returned. This allows the user to know that the equipment-related items have been returned, and thereafter, there is no need for the user to follow up on the return of the equipment-related items, thereby reducing the burden on the user.

[0165] Furthermore, the item management device 200 outputs an alarm when a plurality of equipment-related items have been taken out for one piece of equipment and only a portion of the plurality of equipment-related items have been returned. This reduces the possibility that equipment-related items will not be returned.

[0166] In addition, if equipment-related items for a certain facility are returned to the item management device 200 before the scheduled end time of use, and the next reservation for the facility is registered within a specified advance target time after the scheduled end time of use, the collaboration unit 380 notifies the user of the next reservation that the facility can be used early. In this case, the next user may have reserved the facility for a time slot later than the desired time slot because a reservation has already been registered. In this case, the next user who receives notification that the facility is available for use earlier can use the facility earlier at a more suitable time slot.

[0167] Furthermore, the linking unit 380 advances the scheduled start time of use for the next reservation, allowing the next user to use the facility at a more suitable time slot without having to go through the procedure for advancing the time slot.

[0168] Furthermore, the cooperation unit 380 causes the schedule management unit 191 to stop new registration of reservations for the facility before the next reservation by anyone other than the user of the next reservation. This makes it possible to avoid a situation where, when the next user attempts to advance the scheduled start time of use of the facility, another new reservation has already been registered and the advance cannot be made.

[0169] Furthermore, the linking unit 380 causes the item management device 200 to permit the user of the next reservation to remove the equipment-related item for the equipment before the scheduled start time of use of the next reservation. This allows the next user to use the facility at a more suitable time slot, without having to go through the procedure for moving up the time slot. Also, because the reservation itself is not changed, the coordination unit 380 does not need to perform any processing to prevent the reservation from being canceled against the user's will, and in this respect the load on the coordination unit 380 can be reduced.

[0170] Here, if the schedule management unit 191 automatically advances the scheduled start time of use, and the time at which the reservation is automatically canceled is also advanced accordingly, this may actually be detrimental to the user. In this case, the cooperation unit 380 (or the schedule management unit 191) needs to perform processing such as leaving the original cancellation time of the reservation as is so as not to cause any disadvantage to the user. In contrast, in the above case, the reservation itself is not changed, so the linking unit 380 does not need to perform any processing to prevent the reservation from being cancelled against the user's will.

[0171] Furthermore, the linking unit 380 generates usage history information including information on the date and time when the facility was actually used, based on the history of taking out and returning the facility-related items from the item management device 200. Here, it is considered that the history of taking out and returning equipment-related items from the item management device 200 reflects the actual usage of the equipment more accurately than the schedule indicated in the reservation information. In this respect, the linking unit 380 can generate more accurate usage history information.

[0172] The linking unit 380 also generates statistical information on the usage history of the facility. The linking unit 380 generates statistical information based on the above-mentioned usage history information, thereby making it possible to generate more accurate statistical information.

[0173] Note that a program for realizing all or part of the functions of the processing performed by the linked device 300 may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to perform the processing of each part. Note that the term "computer system" here includes hardware such as an OS and peripheral devices. Furthermore, if a WWW system is used, the "computer system" also includes the homepage provision environment (or display environment). Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into computer systems. The program may be one that realizes part of the functions described above, or may be one that can realize the functions described above in combination with a program already recorded in the computer system.

[0174] Although an embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like are also included within the scope that does not deviate from the gist of the present invention. For example, the following modifications are possible. (Variation 1) When making it possible to remove keys for a company car or keys for a storage cabinet for chemicals, hazardous materials, etc., the item management device 200 may allow removal of the keys only if it is confirmed that the person has a valid license. For example, before making it possible to remove the keys for a company car, the item management device 200 reads data from the IC chip of the driver's license using the card reader 33, and controls so as to permit removal of the keys if it determines that the license is valid (whether the license is within the validity period, has not been suspended or revoked due to administrative action, etc.). Whether or not to perform this confirmation may be stored in advance as setting information for each holder number in the item management side memory unit 212 of the item management device 200, or may be performed in response to an instruction from the linked device 300. (Variation 2) Furthermore, in the above embodiment, a reservation is made when retrieving a facility-related item from the item management device 200 to use a certain facility. However, if there is no reservation for the facility corresponding to the facility-related item, the facility-related item may be retrieved from the item management device 200 without a reservation procedure, limited to short-term use (e.g., 10 minutes or 30 minutes). In this case, when the item management device 200 receives a specification of a holder number for the facility-related item to be retrieved by a user, the item management device 200 inquires of the coordination device 300 whether a reservation is available for short-term use of the facility corresponding to the facility-related item specified by the holder number. The coordination device 300 checks the reservation information and, if there is no reservation for the facility, transmits a notification to the item management device 200 permitting short-term use. Upon receiving this permission notification, the item management device 200 permits retrieval of the facility-related item corresponding to the specified holder number. For this short-term use, as in the above embodiment, the coordination device 300 can generate facility usage history information based on the retrieval history and return history of facility-related items from the item management device 200. Furthermore, when the cooperating device 300 transmits a permission notice for short-term use to the item management device 200, the cooperating device 300 may also notify the groupware server device 100 of the same. This allows the groupware server device 100 to manage short-term use in the schedule management, thereby making it possible to manage reservations for facility use so that overlaps do not occur.

[0175] Some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes.

[0176] (Appendix 1) an item management device for storing facility-related items for use of the facility; a schedule management unit that manages reservations for the facility; a linking unit that, when detecting that the facility-related item is present in the item management device a predetermined first advance notification time before the scheduled start time of use for the facility reservation, notifies the user who has reserved the facility that the facility-related item is available for removal, and instructs the item management device to set the facility-related item so that the user can remove it; A reservation management system comprising:

[0177] (Appendix 2) If the facility-related item is not removed from the item management device until a predetermined cancellation time has elapsed from the scheduled start time of use, the cooperation unit notifies the user that the reservation will be canceled and causes the schedule management unit to cancel the reservation. Reservation management system as described in Appendix 1.

[0178] (Appendix 3) When the facility-related item has not been returned to the item management device a predetermined second advance notification time before the scheduled start time of use, the linking unit notifies the user that the facility-related item has not been returned. Reservation management system as described in Appendix 1.

[0179] (Appendix 4) the item management device stores a plurality of the equipment-related items for one of the equipment, and outputs an alarm when only a part of the plurality of equipment-related items is taken out. Reservation management system according to any one of appendices 1 to 3.

[0180] (Appendix 5) the linking unit notifies the user that the scheduled end time of use in the reservation is approaching a predetermined time before the scheduled end time of use; 7. A reservation management system according to any one of appendices 1 to 4.

[0181] (Appendix 6) the linking unit notifies the user of a return reminder when the equipment-related item has not been returned to the item management device after a predetermined return reminder time has elapsed from the scheduled end time of use in the reservation, and causes the schedule management unit to stop registering new reservations for the equipment. 6. A reservation management system according to any one of appendices 1 to 5.

[0182] (Appendix 7) the item management device outputs an alarm when a plurality of the equipment-related items have been taken out for one of the equipment and only a part of the plurality of equipment-related items has been returned. 7. A reservation management system according to any one of appendices 1 to 6.

[0183] (Appendix 8) When equipment-related items for a certain facility are returned to the item management device before the scheduled end time of use, and the next reservation for the facility is registered within a predetermined advance target time after the scheduled end time of use, the linking unit notifies the user of the next reservation that the facility can be used early. 8. A reservation management system according to any one of appendices 1 to 7.

[0184] (Appendix 9) the linking unit generates usage history information including information on the date and time when the facility was actually used based on the history of taking out and returning the facility-related items from the item management device. 7. A reservation management system according to any one of appendices 1 to 6.

[0185] (Appendix 10) When detecting that a facility-related item for using the facility is present in the item management device a predetermined first advance notification time before the scheduled start time of use of the facility, notifying the user who has reserved the facility that the facility-related item is available for removal, and instructing the item management device to set the facility-related item so that the user can remove it. How to manage reservations.

[0186] (Appendix 11) an item management device for storing facility-related items for use of the facility; a schedule management unit that manages reservations for the facility; A computer that operates in cooperation with A program for notifying a user of the equipment reservation that the equipment-related item is available for removal when the equipment management device detects that the equipment-related item is present a predetermined first advance notification time before the scheduled start time of use for the equipment reservation, and for instructing the equipment management device to set the equipment-related item so that the user can remove it. [Explanation of symbols]

[0187] 1. Reservation Management System 100 Groupware server device 110 Groupware communication section 180 Groupware side memory section 190 Groupware side control unit 191 Schedule Management Department 200 Article management equipment 300 Linkage Device 310 Collaboration Communication Department 320 Linked display unit 330 Linked operation unit 360 Linked storage unit 370 Linked side control unit 380 Collaboration Department 381 Advance Notice Processing Unit 382 Carrying-up processing unit 383 Retrieval notification processing section 384 Cancellation Notice Processing Unit 385 Cancellation Processing Unit 386 Return notification processing section 387 Return Delay Processing Unit 391 History Information Generation Unit 392 Statistical information generation section 400 Groupware client device 500 Internal Network 600 Gateway Device 700 External Network 800 Mobile terminal device

Claims

1. a history information generating unit that generates facility usage history information based on the history of taking out and returning facility-related items for using the facility, the history information being acquired from the item management device; a statistical information generating unit that generates statistical information on the usage history of the facilities for each facility group of arbitrarily selected facilities based on the usage history information of the facilities; An information generating device comprising:

2. The facility usage history information includes either user information registered in reservation information acquired from a server device that manages facility usage reservations, or user information input by a facility user to the item management device when picking up or returning the facility-related item, the facility, pick-up date and time, and return date and time, The statistical information generating unit generates usage statistics for each user regarding facility usage. The information generating device according to claim 1 .

3. The facility usage history information includes at least the facility, the date and time of pick-up, the date and time of return, and information on the organization to which the user belongs; The statistical information generating unit generates usage statistics for each organization regarding facility usage. The information generating device according to claim 2 .

4. The facility groups can be narrowed down by selecting a group from the facility groupings stored in the storage unit of the groupware server device to which the statistical information generating unit is connected. The information generating device according to claim 1 .

5. By selecting the item management device, the equipment group can be narrowed down to a group of equipment registered in the selected item management device. The information generating device according to claim 1 .

6. Statistical information on the usage history of the equipment At least one of the following is included: usage time, usage rate, usage frequency, and average usage time The information generating device according to any one of claims 1 to 5.

7. The facility usage history statistical information is Any of the use time, the use rate, the number of times of use, and the average use time is in descending order. The information generating device according to claim 6.

8. On the computer, generating facility usage history information based on the history of taking out and returning facility-related items for using the facility, which history is acquired from the item management device; Based on the facility usage history information, statistical information on the facility usage history is generated for each facility group of arbitrarily selected facilities. Program for.

Images