JP2018076641A - Key management device, key management system, and key management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable, even if a user has made a reservation for using a key, another user to use the key efficiently and properly.SOLUTION: If an operator H1 makes an advance reservation for using a key (S1), a management server 20 manages the reservation content as use reservation data 24d. If an operator H2 performs a take-out operation on the reserved key (S2), the management server 20 transmits an approval request to an administrator terminal 30 (S3). The administrator terminal 30 notifies an administrator H3 of the approval request, and allows the operator H2 to take-out the key (S5) when accepting the approval operation from the administrator H3 (S4).SELECTED DRAWING: Figure 1

Description

  The present invention provides a key management device, a key management system, and a key management that enable other users to use the key efficiently and appropriately even when a certain user has made a reservation for the use of the key. Regarding the method.

  2. Description of the Related Art Conventionally, money handling apparatuses such as teller machines and money changers are disposed in stores of financial institutions such as banks. In many cases, the money handling apparatus is provided with a plurality of locks. For example, the door of the teller machine and the money storage cassette are provided with separate locks. Further, the keys for locking and unlocking these locks are strictly managed in the key management device.

  For this reason, when unlocking the money handling apparatus, an operator performs a predetermined operation including designation of a key to be taken out from the key management apparatus, and obtains a desired key from the key management apparatus. The lock provided in the money handling apparatus is unlocked using the extracted key.

  Here, a technique for reserving the extraction of a key from such a key management apparatus is known. For example, Patent Document 1 manages a key use reservation or reservation change in a management server, and is managed by this management server. A network key management system configured to control the key management device based on the information is disclosed.

JP 2005-188199 A

  However, the above-mentioned Patent Document 1 has a problem that other users cannot use the corresponding key while the management server makes a reservation for the use of the key. For example, in a situation where a certain user A has made a key use reservation, if another user B needs to use the key immediately, a key use reservation by the user A who is the reservation person himself / herself Need to be canceled or changed. For this reason, the user B must notify the user A who is the reservation person to that effect, which may lead to complication of work. In particular, in a situation where the user A cannot be contacted, the user B cannot use the key, which causes a serious problem in business.

  Therefore, even when a key is reserved for use by a certain user, it is an important issue to make the key usable without requiring direct cancellation or change by the user. It was.

  The present invention has been made in order to solve the above-described problems of the prior art, and even when a key usage reservation is made by a certain user, the user can efficiently and appropriately perform the relevant operation. It is an object of the present invention to provide a key management device, a key management system, and a key management method that can use a key.

  In order to solve the above-described problems and achieve the object, the present invention has received a key holding unit that holds a key, an operation unit that receives a reservation operation for a key held in the key holding unit, and the operation unit. When a second reservation operation is newly received from the operation unit with respect to the storage unit storing the information related to the reservation operation and the key in which the information related to the first reservation operation is stored in the storage unit, And an output unit for outputting an approval request for the second reservation operation.

  Also, the present invention provides the operation unit according to the above-described invention, on the condition that a key storing information related to a first reservation operation in the storage unit is held in the key holding unit. 2 reservation operation is received.

  Further, the present invention is characterized in that, in the above invention, the output unit changes an output destination to output an approval request in accordance with a type of a key to be reserved.

  Further, in the present invention according to the above-described invention, the output unit may be configured on the condition that a key is not held in the key holding unit when the key take-out operation by the reservation person of the first reservation operation is accepted. As an example, information regarding a reservation person of the second reservation operation is output.

  Further, according to the present invention, in the above invention, if the output unit rents and returns a key to be reserved for the first reservation operation during the key reservation time by the first reservation operation. For example, the approval request is not output.

  The present invention also includes a key management unit that has a key holding unit that holds a key, and that allows a key user registered in advance to use the key, and a management device that manages key reservation information. A key management system communicably connected, wherein the key management device receives an operation unit that accepts a reservation operation for a key held in the key holding unit, and if the reservation operation is accepted by the operation unit, the management unit An inquiry unit that inquires whether or not the reservation operation is approved, and the management device stores a storage unit that stores information related to the reservation operation received from the key management device, and performs a reservation operation from the key management device. If an inquiry about approval / disapproval is accepted, a determination unit that determines whether the reservation operation is approved based on information related to the reservation operation stored in the storage unit, and the reservation operation determined by the determination unit Accepted The possibility is characterized in that a notification unit configured to notify the key management device.

  Further, according to the present invention, in the above invention, the management device further includes a management unit that manages the schedule information of the approver, and the notification unit receives an inquiry about whether or not the reservation operation is approved from the key management device. Then, based on the schedule information of the approver managed by the management unit, the key management device is notified of the estimated approval time.

  The present invention also provides a reservation operation receiving step for receiving a reservation operation for a key held in the key holding unit of the key management device, and storing information related to the reservation operation received in the reservation operation receiving step in a predetermined storage unit. And a second reservation operation approval request is output when a second reservation operation is newly received with respect to the storage step to be performed and a key in which information related to the first reservation operation is stored in the predetermined storage unit And an approval requesting step.

  The present invention also includes a key management unit that has a key holding unit that holds a key, and that allows a key user registered in advance to use the key, and a management device that manages key reservation information. A key management method in a communicably connected key management system, wherein the key management device accepts a reservation operation of a key held in the key holding unit by an operation unit, and a reservation operation by the operation unit If the management device receives an inquiry from the key management device as to whether or not to approve the reservation operation, a predetermined memory is stored. Determining whether to approve the reservation operation based on information related to the reservation operation stored in the unit, and notifying the key management device of approval of the reservation operation determined in the determination step Characterized in that it includes a knowledge process.

  According to the present invention, even when a key is reserved for use by a certain user, the key can be used efficiently and appropriately by another user.

FIG. 1 is a diagram for explaining the concept of processing of the key management system according to the present embodiment. FIG. 2 is a system configuration diagram showing the configuration of the key management system. FIG. 3 is a perspective view showing the external appearance of the key management device. FIG. 4 is a functional block diagram showing the configuration of the key management apparatus. FIG. 5 is a diagram showing a specific example of the holder setting data. FIG. 6 is a diagram illustrating a specific example of loan history data. FIG. 7 is a diagram showing a specific example of use reservation data. FIG. 8 is a functional block diagram showing the configuration of the management server. FIG. 9 is a diagram illustrating a specific example of user data. FIG. 10 is a diagram illustrating a specific example of authentication management data. FIG. 11 is a diagram illustrating a specific example of the approver schedule data. FIG. 12 is a flowchart showing a reservation processing procedure by the key management system. FIG. 13 is a flowchart showing a key extraction processing procedure by the key management system. FIG. 14 is a flowchart showing details of the interrupt use process shown in FIG. FIG. 15 is a functional block diagram illustrating a configuration of a key management apparatus having a management server function.

  Exemplary embodiments of a key management device, a key management system, and a key management method according to the present invention will be described below in detail with reference to the accompanying drawings.

<Concept of processing by key management system>
First, the concept of processing by the key management system according to the present embodiment will be described. FIG. 1 is a diagram for explaining the concept of processing of the key management system according to the present embodiment. A key management device 10 shown in FIG. 1 is a device that is provided in a store of a financial institution such as a bank and stores keys such as a money handling device and a safe.

  Specifically, the key management device 10 has a key storage, and the key storage is provided with a plurality of holder storage units for storing holders 14 for holding keys. Each holder storage portion can lock the holder 14 in a state where the corresponding holder 14 is inserted, and restrict the removal of the holder 14.

  The key management device 10 is connected to the management server 20 and the administrator terminal 30 via a predetermined network. The management server 20 is a device that manages keys. Specifically, the management server 20 holds data relating to the holder of the key management device 10, the user who uses the key management device 10, and user authentication, and performs processing related to user authentication. In addition, the management server 20 accepts a reservation for use of the key and stores it as use reservation data 24d.

  The administrator terminal 30 is a device used by an administrator who has a predetermined authority for key management. The administrator terminal 30 is used for generating, referring to, and changing data held by the management server 20. Further, the administrator terminal 30 is used to approve the removal of the key by another user when another operator uses the reserved key.

  In FIG. 1, the operator H1 reserves the use of the key in advance (S1). This reservation may be performed by an operation on the key management device 10 or may be performed from another terminal device. The management server 20 registers the user ID that identifies the operator H1, the holder storage unit number that identifies the holder 14 to be reserved, and the reservation date and time in association with the reservation data 24d.

  Thereafter, when the operator H2 performs the key removal operation, the management server 20 refers to the use reservation data 24d and determines whether or not the holder 14 to be removed is reserved and within the reservation time. If not reserved, allow removal. Here, if the holder H1 to be taken out is in a reserved state and within the reservation time, but the take-out by the reserved operator H1 is not performed, the operator H2 interrupts the reservation. be able to. Here, “interrupt” means that a key reserved by another operator can be temporarily used.

  When the operator H2 interrupts (S2), the management server 20 transmits an approval request to the administrator terminal 30 (S3). The administrator terminal 30 notifies the administrator H3 of an interrupt approval request, and if an approval operation is received from the administrator H3 (S4), permits the operator H2 to take out the key (S5). If approval by the administrator H3 is not made, the key removal is prohibited because the reservation has been made.

  As described above, in the key management system according to the present embodiment, the management server 20 manages the key use reservation based on the use reservation data 24d, and when the key management apparatus 10 accepts the key removal operation, the management server 20 Inquiries are made regarding whether or not the key can be taken out, and even if the reservation is made by another operator, the key is allowed to be taken out subject to the approval of the administrator. For this reason, even when a key use reservation is made by a certain operator, the key can be used by another operator efficiently and appropriately.

<Configuration of key management system>
Next, the configuration of the key management system will be described. FIG. 2 is a system configuration diagram showing the configuration of the key management system. As shown in FIG. 2, in the key management system according to the present embodiment, the key management device 10, the management server 20, the administrator terminal 30, and a plurality of usage terminals 40 are connected via a predetermined network.

  The use terminal 40 is a money deposit / withdrawal machine, an important material management device, an ATM (Automated Teller Machine), a money changer, or the like, and keys used for these devices are stored in the key management device 10. The key management device 10 is not limited to the key used for the use terminal 40 connected to the network, and can store an arbitrary key such as a safe key.

  The management server 20 is a device that manages keys. Specifically, the management server 20 holds data relating to the holder of the key management device 10, the user who uses the key management device 10, and user authentication, and performs processing related to user authentication. In addition, the management server 20 accepts a reservation for use of the key and stores it as use reservation data 24d.

  The administrator terminal 30 is a device used by an administrator who has a predetermined authority for key management. The administrator terminal 30 is used for generating, referring to, and changing data held by the management server 20. Further, the administrator terminal 30 is used to approve the removal of the key by another user when another operator uses the reserved key.

<Configuration of key management device>
Next, the external appearance of the key management device 10 will be described. FIG. 3 is a perspective view showing the external appearance of the key management device 10. As shown in FIG. 3, the key management apparatus 10 includes a key storage 10b that is opened and closed by a door 10a, a display operation unit 11, a finger vein reading unit 11a, a card reader 12, and a receipt outlet 15a.

  A plurality of holder storage portions 13 are provided in the key storage case 10b. The holder storage unit 13 detachably stores a holder 14 in which keys to be stored are connected by a ring. Each holder storage unit 13 has a lock mechanism (not shown) so that the holder 14 can be taken out or prohibited. The key management device 10 controls permission or prohibition of taking out each holder 14 by controlling a lock mechanism for each holder storage portion 13.

  The key management device 10 also has a display operation unit 11. The display operation unit 11 is a touch panel display or the like, and is used for receiving an operation input from an operator and displaying various information. The finger vein reading unit 11a is used when reading the vein state from the operator's finger as biometric information. In this embodiment, the case where the finger vein is used as biometric information will be described as an example. However, any biometric information such as a fingerprint, a voiceprint, and a retina can be used for authentication of the investigator. Also, image authentication using a face image or the like as biometric information may be used. The card reader 12 is used when reading identification information or the like from a card carried by the operator. The receipt outlet 15a discharges the paper printed by a printer 15 (not shown) so that it can be taken out.

  Next, the configuration of the key management device 10 will be described. FIG. 4 is a functional block diagram showing the configuration of the key management apparatus 10. As shown in FIG. 4, the key management device 10 includes a door locking mechanism 10c, a display operation unit 11, a finger vein reading unit 11a, a card reader 12, a holder storage unit 13, a printer 15, a communication unit 16, a storage unit 17, and a control. Part 18. Since the display operation unit 11, the finger vein reading unit 11a, the card reader 12, and the holder storage unit 13 have been described with reference to FIG. 3, description thereof will be omitted.

  The door locking mechanism 10c is a mechanism that locks the door 10a of the key storage 10b. The printer 15 is a thermal or ink jet printing unit that prints on roll paper, and prints the usage status of each key managed by the key management device 10. The communication unit 16 is an interface unit for data communication with the management server 20.

  The storage unit 17 is a storage device including a hard disk device, a nonvolatile memory, and the like. The storage unit 17 stores holder setting data 17a, rental history data 17b, and use reservation data 17c. The holder setting data 17a is data in which various types of information related to the holder 14 such as a holder storage unit number, a key name, the number of keys, and an interrupt approval request destination are associated with each other. The lending history data 17b is data indicating a key lending history. The use reservation data 17c is data having the same contents as the use reservation data 24d stored in the management server 20, and includes the user ID of the operator who made the reservation, the holder storage unit number that identifies the holder 14 to be reserved, The reservation date and time are associated.

  The control unit 18 is a control unit that controls the entire key management apparatus 10, and includes a holder setting unit 18a, a reservation processing unit 18b, an inquiry unit 18c, an output control unit 18d, an authentication processing unit 18e, and a lending processing unit 18f. Actually, programs corresponding to the holder setting unit 18a, the reservation processing unit 18b, the inquiry unit 18c, the output control unit 18d, the authentication processing unit 18e, and the lending processing unit 18f are stored in a storage device such as a nonvolatile memory or a magnetic disk device. By loading these programs into the memory and executing them by a CPU (Central Processing Unit), the corresponding processes are executed.

  The holder setting unit 18a is a processing unit that generates and updates the holder setting data 17a. The holder setting data 17a is configured such that the name and number of keys held by the holder 14 stored in the holder storage unit 13, the number of keys stored in the holder storage unit 13, and the holder storage unit number which is identification information of the holder storage unit 13 This is data in which an approval request destination in the case of interrupting a reservation is associated. When setting or updating the holder setting data 17a, the holder setting unit 18a stores the holder setting data 17a in the storage unit 17 and transmits the holder setting data 17a to the management server 20.

  The reservation processing unit 18b is a processing unit that performs processing related to key use reservation. Specifically, when the reservation operation unit 18b receives a reservation operation for requesting a new use reservation from the display operation unit 11, the user ID of the operator, the holder storage unit number to be reserved, the date and time of reservation And identify.

  The reservation processing unit 18b manages key use reservation data 17c. Specifically, the inquiry unit 18c, which will be described later, inquires the management server 20 about whether or not the use reservation is permitted. If the use reservation is permitted, the use reservation data 17c is updated, and the updated use reservation data 17c is updated. It transmits to the management server 20. Further, when the management server 20 updates the use reservation data, the updated use reservation data is received from the management server 20 and the use reservation data 17c is updated.

  In addition, when the display operation unit 11 accepts a key removal operation, the reservation processing unit 18b specifies the user ID of the operator and the holder storage unit number to be removed.

  The inquiry unit 18c is a processing unit that makes an inquiry to the management server 20 based on the data specified by the reservation processing unit 18b. When making a new reservation, the inquiry unit 18 c transmits an inquiry for a new reservation including the user ID, the holder storage unit number, and the date and time of the reservation to the management server 20. If there is no existing reservation competing with the new reservation, the reservation is received from the management server 20 and the reservation is made. In addition, there is an existing reservation, but if approval by an administrator or the like is obtained, the fact that it is an interrupt reservation is notified, and a reservation is made. If the person who performs the approval has a plan and the immediate approval cannot be made, the estimated approval time is notified based on the schedule of the person who performs the approval, and an interrupt reservation is made when the approval is obtained. If the approval is not obtained, the interrupt reservation for the existing reservation is not performed.

  When the key is to be extracted, the inquiry unit 18 c transmits a key extraction inquiry including the user ID and the holder storage unit number to the management server 20. If there is no existing reservation that conflicts with key retrieval, the key retrieval permission is received from the management server 20. In addition, when there is an existing reservation but the approval by the administrator or the like is obtained, the fact that it is an interruption is notified and the key is permitted to be taken out. If there is a plan for the person to be approved and immediate approval is not possible, the estimated approval time is notified based on the schedule of the person to be approved, and the key can be taken out when the approval is obtained. . If approval is not obtained, key removal is prohibited.

  The output control unit 18d is a processing unit that performs various outputs related to new reservations and key extraction. Specifically, the output control unit 18d uses the display operation unit 11 to complete a new reservation, permit key removal, notify that there is a competing existing reservation, notify that it is an interrupt reservation, and approve it. Notification of predicted time, notification that approval was not obtained, etc. are performed.

  The authentication processing unit 18e performs an operator authentication process using the user ID and the authentication data. As the user ID, an employee number assigned to the employee or a card ID can be used. When an employee number or the like is used as the user ID, the operator performs input using the display operation unit 11. When the card ID is used as the user ID, the operator passes the card through the card reader 12 to read the card ID. As the authentication data, a personal identification number or biometric information acquired by the finger vein reading unit 11a is used. The authentication processing may be executed by the authentication processing unit 18e itself or may be performed by the management server 20. When the management server 20 performs authentication processing, the authentication processing unit 18e transmits the user ID and authentication data to the management server 20 and receives the authentication result.

  The lending processing unit 18f is an operator who has the authority to take out the key as a result of the authentication, and locks the holder storage unit 13 designated as the door locking mechanism 10c when the use prohibition based on the existing reservation is not performed. Is released. Further, when the lending processing unit 18f detects removal of the holder 14, the lending date / time is set as the lending date / time, and the lending date / time is associated with the user ID, lending type, and holder storage unit number in the lending history data 17b. sign up. The loan type indicates whether the use is based on interruption or normal use that is not interruption. In the case of interruption, the purpose of use is further included.

  The lending processing unit 18 f locks the holder storage unit 13 when the holder 14 is returned to the holder storage unit 13. Then, the date and time at that time is registered in the lending history data 17b as the return date and time.

  The lending processing unit 18f manages key lending time. Specifically, the upper limit of the lending time is set in the holder storage unit 13, and an alarm is output when the time from the lending date to the return date exceeds the upper limit.

  Next, the data stored in the storage unit 17 of the key management apparatus 10 shown in FIG. 4 will be specifically described. FIG. 5 is a diagram showing a specific example of the holder setting data 17a. As shown in FIG. 5, the holder setting data 17 a associates a key name, the number of keys, and an interrupt approval request destination with a holder storage unit number that is identification information of the holder storage unit 13.

  In FIG. 5, the holder storage unit number “01” is associated with the key name “safety key”, the number of keys “1”, the multiple authentication method support “impossible”, and the interrupt approval request destination “manager”. Further, the holder storage unit number “02” is associated with the key name “money deposit / withdrawal machine key”, the number of keys “3”, and the interruption approval request destination “pre-reserved person”. Here, the interruption approval request destination “preliminary reservation person” indicates that an approval by a person who has made an existing reservation is requested.

  FIG. 6 is a diagram illustrating a specific example of the lending history data 17b. As shown in FIG. 6, the lending history data 17b is data in which a lending date / time, a return date / time, a user ID, a lending type, and a holder storage unit number are associated with each other. Specifically, the operator having the user ID “1101” takes out the holder 14 corresponding to the holder storage unit number “03” at the rental date “2016 07/16 10:40” and returns the date “2016 07/16”. 10:53 "is shown. Further, it is shown that the loan type at this time was “normal” which is not an interruption.

  Similarly, after the operator with the user ID “2001” has taken out the holder 14 corresponding to the holder storage unit number “02” at the rental date “2016 07/16 12:15”, the operator has not returned it. It is shown. Further, it is shown that the loan type at this time was “normal” which is not an interruption.

  Further, the operator with the user ID “1008” takes out the holder 14 corresponding to the holder storage unit number “08” at the rental date “2016 07/16 12:30” and returns the date “2016 07/16 15:00”. ”Indicates that it has been returned. In addition, the lending type at this time is “interrupt (delivery)”, which indicates that an existing reservation has been interrupted for delivery.

  FIG. 7 is a diagram showing a specific example of the use reservation data 17c. In FIG. 7, the person with the user ID “1021” from “2016 07/16 09:00” to “2016 07/16 16:30” is the target for the holder storage unit number “8” for storing the company car key. This indicates that a reservation is being made for "customer visit". Furthermore, as an interrupt reservation for this reservation, a person with a user ID “1008” from “2016 07/16 12:30” to “2016 07/16 15:00” makes a reservation for the purpose “delivery”. It shows that.

<Configuration of management server>
Next, the configuration of the management server 20 will be described. FIG. 8 is a functional block diagram showing the configuration of the management server 20. As illustrated in FIG. 8, the management server 20 includes a display unit 21, an input unit 22, a communication unit 23, a storage unit 24, and a control unit 25.

  The display unit 21 is a display device such as a liquid crystal display device. The input unit 22 is an input device such as a keyboard or a mouse. The communication unit 23 is a communication interface that performs communication with the key management device 10, the administrator terminal 30, the use terminal 40, and the like.

  The storage unit 24 is a storage device such as a hard disk device or a nonvolatile memory, and stores holder setting data 24a, user data 24b, authentication management data 24c, use reservation data 24d, and approver schedule data 24e. The holder setting data 24 a is the same data as the holder setting data 17 a of the key management device 10. The user data 24b is data relating to a user who uses the key management apparatus 10. The authentication management data 24c is data used for user authentication. The use reservation data 24d is the same data as the use reservation data 17c of the key management device 10. The approver schedule data 24e is data indicating a schedule of a person who approves an interrupt.

  The control unit 25 is a control unit that controls the entire management server 20, and includes a holder setting management unit 25a, a user management unit 25b, a reservation management unit 25c, an approval management unit 25d, a notification control unit 25e, and an authentication management unit 25f. Have. Actually, programs corresponding to these functional units are stored in a ROM or non-volatile memory (not shown), and these programs are loaded into a CPU (Central Processing Unit) and executed, whereby the holder setting management unit 25a. The user management unit 25b, the reservation management unit 25c, the approval management unit 25d, the notification control unit 25e, and the authentication management unit 25f execute corresponding processes.

  The holder setting management unit 25a performs processing for storing the holder setting data 19a received from the key management device 10 in the storage unit 24 as the holder setting data 24a. Further, the holder setting data 24a can be generated or changed in response to an operation from the administrator via the administrator terminal 30. When the holder setting data 24a is generated or changed in response to an operation from the administrator, the holder setting management unit 25a transmits the holder setting data 24a to the key management device 10, and the key management device 10 manages the holder setting data 24a. The holder setting data 17a is updated.

  The user management unit 25b is a processing unit that manages the user data 24b. The user data 24b is data in which a user attribute, a user name, a contact address, and the like are associated with the user ID. For example, “employee”, “administrator”, “part-time work”, “warning officer” can be set as the user attribute. The user name may be an individual name or the name of a police company.

  The reservation management unit 25c is a processing unit that manages key use reservations. Specifically, if the reservation management unit 25c receives an inquiry about a new reservation from the key management device 10 or the administrator terminal 30 or the like, the user ID indicated in the inquiry, the holder storage unit number to be reserved The use reservation data 24d is referred to based on the reservation date and time. As a result, if there is no existing conflicting reservation, a reservation permission is transmitted and a new reservation is registered in the use reservation data 24d. If there is a conflicting existing reservation, an approval request is requested to the approval management unit 25d, and a reservation is made when approval is obtained.

  The reservation management unit 25c manages the key use reservation data 17c. Specifically, when the key management device 10 updates the use reservation data, the updated use reservation data is received from the key management device 10 and the use reservation data 24d is updated. Furthermore, it is possible to accept cancellation or change of the reservation by the person who made the reservation.

  Further, when the reservation management unit 25c receives an inquiry about the key extraction from the key management device 10, the reservation management unit 25c refers to the use reservation data 24d based on the user ID indicated in the inquiry and the holder storage unit number to be extracted. To do. As a result, if there is no conflicting existing reservation, a key retrieval permission is transmitted. If there is a conflicting existing reservation, an approval request is requested to the approval management unit 25d.

  The approval management unit 25d is a processing unit that performs processing related to the approval request. First, the approval management unit 25d registers and manages the schedule of the approver who is a person registered in the approval request destination of the holder setting data 24a in the approver schedule data 24e.

  When the approval management unit 25d receives an approval request request from the reservation management unit 25c, the approval management unit 25d refers to the holder setting data 24a and identifies an approver corresponding to the holder storage unit number indicated in the approval request request. Thereafter, the schedule of the identified approver is read from the approver schedule data 24e. If there is no plan, it is determined that immediate approval is possible, and an approval request is output to the approver. If there is a plan, the approval management unit 25d informs the inquiry source of the scheduled end date and time as an estimated prediction time, and outputs an approval request to the approver. At this time, the approval request may be output immediately or in accordance with the scheduled end date and time.

  The notification control unit 25e is a processing unit that notifies the inquiry source of approval or disapproval based on the operation of the approver. If the approver performs an operation to approve, the notification control unit 25e notifies the approval “permitted”, and if the approver performs an operation not to approve, the notification control unit 25e Notification of approval “non-” is made. In addition, whether or not to approve is also notified to the reservation management unit 25c, and when the notification of approval is “permitted” for the interrupt reservation, the reservation management unit 25c registers the reservation.

  The authentication management unit 25f is a processing unit that manages the authentication management data 24c. At the time of registration, the authentication management unit 25f performs a process of receiving a user ID and authentication data from the key management device 10 and adding them to the authentication management data 24c in association with the target holder storage unit number. When the user ID and the authentication data are received from the key management device 10, the authentication process is executed by comparing the received authentication data with the authentication data registered in the authentication management data 24c. The authentication result is transmitted to the key management device 10.

  Next, data stored in the storage unit 24 of the management server 20 illustrated in FIG. 8 will be specifically described. FIG. 9 is a diagram showing a specific example of the user data 24b. As shown in FIG. 9, the user data 24b is data in which a user attribute, a user name, a contact address, and the like are associated with a user ID.

  In FIG. 9, the user data 24b associates the user ID “1001” with the user attribute “employee manager”, the user name “AB”, and the contact “extension 1001”. Similarly, the user attribute “employee general”, the user name “CD”, and the contact “extension 1002” are associated with the user ID “1002”. In the user data 24b, the user attribute “part-time work”, the user name “EF”, and the contact “extension 1103” are associated with the user ID “1103”. Further, the user ID “2001” is associated with the user attribute “security officer”, the user name “security company G”, and the contact information “090-XXXX-XXXX”.

  FIG. 10 is a diagram illustrating a specific example of the authentication management data 24c. As shown in FIG. 9, the authentication management data 24c is data in which a holder ID is associated with a user ID, an authentication method, authentication data, and a lending time upper limit.

  Specifically, the authentication management data 24c includes a holder storage unit number “01”, a user ID “1001”, an authentication method “user ID + finger vein”, authentication data “(finger vein data)”, and a lending time upper limit. “60 minutes” is associated. Similarly, the holder storage unit number “01” is associated with the user ID “1002”, the authentication method “user ID + finger vein”, the authentication data “(finger vein data)”, and the lending time upper limit “60 minutes”. Yes.

  In the authentication management data 24c, the holder ID “02” is associated with the user ID “1001”, the authentication method “card”, the authentication data “(unnecessary)”, and the lending time upper limit “60 minutes”. . Similarly, the holder storage unit number “02” is associated with the user ID “1002”, the authentication method “user ID + password”, the authentication data “(password)”, and the lending time upper limit “60 minutes”. . Further, the holder ID “02” is associated with the user ID “1103”, the authentication method “card + authentication number”, the authentication data “(password)” and the lending time upper limit “30 minutes”. Similarly, the holder ID “02” is associated with the user ID “2001”, the authentication method “card + password”, the authentication data “(password)” and the lending time upper limit “20 minutes”.

  FIG. 11 is a diagram showing a specific example of the approver schedule data 24e. In FIG. 11, as the schedule of the person with the user ID “1001”, from “2016 07/16 09:00” to “2016 07/16 10:00” “internal meeting”, “2016 07/16 12:00”. To “2016 07/16 13:30”.

<System operation>
Next, various processing operations of the key management system will be described. Here, the reservation processing procedure by the key management system and the key extraction processing procedure will be described. In the reservation processing procedure, when a reservation operation is accepted, if another reservation already exists and the reservation time overlaps, an interrupt reservation is made for the conflicting reservation. However, even if there is a conflicting reservation, if it is already used and returned, a normal reservation can be made instead of an interrupt reservation. In the key extraction processing procedure, processing changes depending on whether or not the target key is in use at that time.

  FIG. 12 is a flowchart showing a reservation processing procedure by the key management system. First, when the key management device 10 or the like accepts a reservation operation (step S101), the key management device 10 or the management server 20 determines whether there is a conflicting reservation (step S102). If there is no conflicting reservation (step S102; No), a reservation is set based on the user ID, reservation target holder number and reservation date and time indicated in the reservation operation (step S111), and the process ends. .

  If there is a conflicting reservation (step S102; Yes), the key management device 10 or the management server 20 determines whether or not the reserved user has already returned the key (step S103). If the key has been returned (step S103; Yes), an approval request for interruption is unnecessary, so the user ID indicated in the reservation operation, the holder storage unit number to be reserved, and the date and time of the reservation A reservation is set based on (Step S111), and the process is terminated.

  If the key has not been returned (step S103; No), the approval manager 25d of the management server 20 identifies the corresponding approver (step S104) and refers to the approver schedule data 24e to determine the approver's schedule. Confirm (step S105). As a result, if there is no plan and immediate approval is possible (step S106; Yes), the approval management unit 25d outputs an approval request to the approver (step S108). On the other hand, if a schedule is entered and immediate approval is not possible (step S106; No), the end date and time of the schedule is notified to the inquirer as an estimated approval time (step S107), and an approval request is output to the approver (step S107). S108).

  If the approver performs an operation to approve after step S108 (step S109; Yes), the key management device 10 or the management server 20 stores the user ID indicated in the reservation operation and the holder to be reserved. A reservation is set based on the copy number and the date and time of the reservation (step S111), and the process ends. If the approver performs an operation not to approve (step S109; No), the key management device 10 or the management server 20 notifies that the interrupt is impossible (step S110), and ends the process. .

  FIG. 13 is a flowchart showing a key extraction processing procedure by the key management system. First, when the key management apparatus 10 receives a key extraction operation (step S201), the key management apparatus 10 determines whether or not a reservation is made by the same user (step S202). If a reservation by the same user has been made (step S202; Yes), it is determined whether or not the key to be taken out is being used by interruption (step S203). If it is in use by interruption and the key is taken out (step S203; Yes), information about the user currently in use, such as name and contact information, is notified (step S204), and the process is terminated. To do.

  If it is not in use by interruption (step S203; No), the key management apparatus 10 permits the key to be taken out on condition that the operator is properly authenticated (step S206), and the lending history data 17b is stored. Update (step S207), and the process ends.

  If no reservation is made by the same user (step S202; No), the key management device 10 or the management server 20 determines whether there is a conflicting reservation (step S205). If there is a conflicting reservation (step S102; Yes), an interrupt use process is executed (step S208), and the process ends. Details of this interrupt use processing will be described later.

  If there is no conflicting reservation (step S205; No), the key management apparatus 10 permits the key to be taken out on condition that the operator is properly authenticated (step S206), and stores the lending history data 17b. Update (step S207), and the process ends.

  FIG. 14 is a flowchart showing details of the interrupt use process shown in FIG. First, the key management apparatus 10 determines whether or not a key to be taken out is in use (step S301). If the key is being used, that is, if the key has been taken out (step S301; Yes), the interrupt disabled use is notified (step S302), and the process is terminated.

  If the key is not in use, that is, if the target key is stored (step S301; No), the key management device 10 or the management server 20 has returned the key by the reserved user himself / herself. Is determined (step S303). If the key has been returned (step S303; Yes), an approval request for interruption is not required, so that key extraction is permitted on condition that the operator is properly authenticated (step S303). S310), the lending history data 17b is updated (step S311), and the process is terminated.

  If the key has not been returned (step S303; No), the approval manager 25d of the management server 20 identifies the corresponding approver (step S304) and refers to the approver schedule data 24e to determine the approver's schedule. Confirmation (step S305). As a result, if there is no plan and immediate approval is possible (step S306; Yes), the approval management unit 25d outputs an approval request to the approver (step S308). On the other hand, if the schedule is entered and immediate approval is not possible (step S306; No), the end date and time of the schedule is notified to the inquirer as the estimated approval time (step S307), and an approval request is output to the approver (step S307). S308).

  After step S308, if the approver performs an operation to approve (step S309; Yes), the key management apparatus 10 permits the key extraction on condition that the operator is properly authenticated. (Step S310), the lending history data 17b is updated (Step S311), and the process ends. If the approver performs an operation not to approve (step S309; No), the key management device 10 or the management server 20 notifies that the interrupt is impossible (step S302), and ends the process. .

<Modification>
Next, a modification of the key management device will be described. The key management device can be configured so that it can be operated alone, or can have a function of the management server 20. FIG. 15 is a functional block diagram illustrating a configuration of the key management apparatus 110 having the function of the management server 20.

  In the key management device 110 shown in FIG. 15, the storage unit 17 further includes user data 117d, authentication management data 117e, and approver schedule data 117f, and the control unit 18 includes an approval management unit 118c instead of the inquiry unit 18c. This is different from the key management device 10 shown in FIG.

  The user data 117d is data related to the user who uses the key management device 110, similarly to the user data 24b of the management server 20. The authentication management data 117e is data used for user authentication, like the authentication management data 24c of the management server 20. The approver schedule data 117f is data indicating the schedule of the approver, similar to the approver schedule data 24e of the management server 20.

  The approval management unit 118c is a processing unit that performs processing related to the approval request. First, the approval management unit 118c registers and manages the schedule of the approver who is a person registered in the approval request destination of the holder setting data 17a in the approver schedule data 117f.

  If the reservation processing unit 18b identifies the user ID, the reservation target holder storage unit number, and the date and time of the reservation based on the reservation operation, the approval management unit 118c The corresponding approver is specified with reference to the holder setting data 17a. Thereafter, the schedule of the specified approver is read from the approver schedule data 117f, and if there is no plan, it is determined that immediate approval is possible, and the output control unit 18d outputs an approval request to the approver. If there is a plan, the approval management unit 25d notifies the operator of the scheduled end date and time as an estimated prediction time, and also outputs an approval request to the approver. At this time, the approval request may be output immediately or in accordance with the scheduled end date and time.

  When the approver performs an operation to approve, or when there is no competing reservation, the reservation processing unit 18b makes an interrupt reservation for the existing reservation. If there is a conflicting reservation and approval is not obtained, no interrupt reservation is made for the existing reservation.

  Further, when the reservation processing unit 18b identifies the user ID and the holder storage unit number to be extracted based on the key extraction operation, the approval management unit 118c determines that there is a conflicting reservation if n exists. The corresponding approver is specified with reference to the setting data 17a. Thereafter, the schedule of the specified approver is read from the approver schedule data 117f, and if there is no plan, it is determined that immediate approval is possible, and the output control unit 18d outputs an approval request to the approver. If there is a plan, the approval management unit 25d notifies the operator of the scheduled end date and time as an estimated prediction time, and also outputs an approval request to the approver. At this time, the approval request may be output immediately or in accordance with the scheduled end date and time.

  When the approver performs an operation to approve, or when there is no conflicting reservation, key retrieval is permitted. If there are competing reservations and no approval is obtained, key retrieval is prohibited.

  Since other configurations and operations are the same as those of the key management apparatus 10 shown in FIG. 4, the same components are denoted by the same reference numerals and description thereof is omitted. Further, the key management apparatus 110 can be connected to a predetermined terminal and can perform registration operation of each data and reference operation of each data from the terminal.

  As described above, in the key management system according to the present embodiment, the management server 20 manages the key use reservation by the use reservation data 24d, and when the key management apparatus 10 accepts the key removal operation, the management server 20 20 is inquired of whether or not the key can be taken out, and even if it is reserved by another operator, the key is allowed to be taken out under the condition of approval by the administrator. For this reason, even when a key use reservation is made by a certain operator, the key can be used by another operator efficiently and appropriately.

  If the reserved operator is using the key, no interrupt is used, so unnecessary approval processing does not occur. In addition, since different approvers can be set for each type of key and approval can be requested from an appropriate approver, the key can be used more smoothly. Furthermore, according to an approver's schedule, approval and interruption can be performed at an appropriate timing. Furthermore, when the operator related to the original reservation cannot use the key due to the use of the interrupt, the information of the operator who used the interrupt can be notified.

  Moreover, in the said Example, after the operator who concerns on the original reservation uses a key and returns, the approval is unnecessary even if the reservation itself remains. After returning by the principal, the deletion or change of the reservation by another operator may be executed without approval.

  It is also possible to update the conflicting reservation at the time of interruption. In this case, it is desirable to request approval by the approver depending on the importance. In addition, priorities may be set for interrupts and schedules, and an approver who has plans may be requested to approve immediately depending on the priorities of the schedule and interrupts. In addition, a scheduled approver may be set to allow another person to approve on behalf of another person.

  In the above embodiment, the key management system in a store of a financial institution such as a bank has been described as an example. However, the present invention is not limited to this, and can be widely applied to a key management system that manages a plurality of keys. Can be applied.

  Further, the key management device need not be fixedly installed, and the present invention may be applied to a portable key management device.

  In addition, each configuration illustrated in the above-described embodiments is functionally schematic and does not necessarily need to be physically illustrated. That is, the form of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed / integrated in an arbitrary unit according to various loads or usage conditions. Can be configured.

  The key management apparatus, key management system, and key management method of the present invention enable efficient and proper use of the key by other users even when a key usage reservation is made by a certain user. It is useful to.

DESCRIPTION OF SYMBOLS 10,110 Key management apparatus 10a Door 10b Key storage 10c Door locking mechanism 11 Display operation part 11a Finger vein reading part 12 Card reader 13 Holder storage part 14 Holder 15 Printer 15a Receipt outlet 16, 23 Communication part 17, 24 Storage part 17a, 24a Holder setting data 17b Lending history data 17c, 24d Usage reservation data 18, 25 Control unit 18a Holder setting unit 18b Reservation processing unit 18c Inquiry unit 18d Output control unit 18e Authentication processing unit 18f Lending processing unit 20 Management server 21 Display unit 22 Input unit 24b, 117d User data 24c, 117e Authentication management data 24e, 117f Approver schedule data 25a Holder setting management unit 25b User management unit 25c Reservation management unit 25d, 118c Approval management unit 25e Notification control unit 5f authentication management unit 30 administrator terminal 40 use terminal

Claims (9)

A key holding unit for holding a key;
An operation unit that accepts a reservation operation of a key held in the key holding unit;
A storage unit for storing information related to the reservation operation received by the operation unit;
An output unit that outputs an approval request for the second reservation operation when a second reservation operation is newly received from the operation unit for the key in which information related to the first reservation operation is stored in the storage unit And a key management device. The operation unit is
The second reservation operation is received on condition that a key in which information related to the first reservation operation is stored in the storage unit is held in the key holding unit. Key management device. The output unit is
The key management apparatus according to claim 1 or 2, wherein an output destination for outputting an approval request is changed according to a type of a key to be reserved. The output unit is
When the key take-out operation by the reservation person of the first reservation operation is accepted, information on the reservation person of the second reservation operation is output on condition that the key is not held in the key holding unit. The key management apparatus according to claim 1, wherein the key management apparatus is a key management apparatus. The output unit is
The approval request is not output if a key to be reserved for the first reservation operation is lent and returned during the key reservation time of the first reservation operation. The key management device according to any one of 1 to 4. A key having a key holding unit for holding a key, and a key management device that permits a key user registered in advance to use the key and a management device that manages key reservation information, which are communicably connected to each other A management system,
The key management device includes:
An operation unit that accepts a reservation operation of a key held in the key holding unit;
If a reservation operation is accepted by the operation unit, the inquiry unit for inquiring whether the reservation operation is approved or not to the management device,
The management device
A storage unit for storing information related to the reservation operation received from the key management device;
A determination unit that determines whether approval of the reservation operation is permitted based on information related to the reservation operation stored in the storage unit if an inquiry about whether the reservation operation is approved is accepted from the key management device;
A key management system comprising: a notification unit that notifies the key management device of whether the reservation operation approved by the determination unit is approved. The management device
It further includes a management unit that manages the approver's schedule information,
The notification unit
If an inquiry about whether or not the reservation operation is approved is accepted from the key management device, the key management device is notified of the estimated approval time based on the schedule information of the approver managed by the management unit. The key management system according to claim 6. A reservation operation receiving step for receiving a reservation operation for a key held in the key holding unit of the key management device;
A storage step of storing information related to the reservation operation received in the reservation operation reception step in a predetermined storage unit;
An approval request step for outputting an approval request for the second reservation operation when a second reservation operation is newly received for the key in which the information related to the first reservation operation is stored in the predetermined storage unit; A key management method characterized by including: A key having a key holding unit for holding a key, and a key management device that permits a key user registered in advance to use the key and a management device that manages key reservation information, which are communicably connected to each other A key management method in a management system,
An accepting step in which the key management device accepts a reservation operation of a key held in the key holding unit at an operation unit;
If a reservation operation is accepted by the operation unit, an inquiry step for inquiring whether the reservation operation is approved or not to the management device;
If the management device receives an inquiry about whether or not the reservation operation is approved from the key management device, the determination for determining whether or not the reservation operation is approved based on information related to the reservation operation stored in a predetermined storage unit Process,
And a notifying step of notifying the key management device of whether or not the reservation operation approved in the determining step is approved.

Images