JP6988527B2 - Key management device, key management system, key management method, and program - Google Patents

Description

The present invention relates to a key management device for managing vehicle keys, a key management system, a key management method, and a program.

Businesses such as the transportation industry carry out roll calls face-to-face before and after the driver gets on board the vehicle. At the time of delivery call before the flight, the driver reports on daily inspections, the driver's health condition, and whether or not he / she is drunk, and gives necessary instructions to ensure safety. Similarly, when they return home after completing the day's flight, they make a roll call by face-to-face, etc., receive reports on the vehicles, roads, operation status, etc. on board, and confirm whether or not they are drunk.

In order to support such roll call work, a system using a computer is used. In the conventional system, the expiration date of the license, the alcohol concentration of the driver's breath are checked, and the result of the roll call is input to the computer and recorded. The vehicle key is handed to the driver after the roll call is completed.

Patent Document 1 describes a key management device that prevents a vehicle key from being illegally taken out by a person other than the driver. The key management device of Patent Document 1 receives personal identification information from the driver-side roll call device, and collates whether or not the personal identification information matches the personal identification information previously held in the key management device. The vehicle key can be taken out only when the collation result is good. As a result, only the driver who has confirmed his / her identity by roll call can take out the key of the vehicle stored in the key management device.

Japanese Unexamined Patent Publication No. 2016-069931

However, the key management device of Patent Document 1 does not confirm whether or not the driver can drive the vehicle based on the driver's license type (the type of vehicle for which the driver has obtained a driver's license). Therefore, there is a risk of handing over the key of a vehicle that is not exempt from the driver.

In recent years, a quasi-medium-sized license has been newly established, and as a result, there are generally eight types of exemptions: large special, large-sized, large-sized (micro limited), medium-sized, medium-sized (8t limited), quasi-medium-sized, quasi-medium-sized (5t limited), and ordinary. It became. Furthermore, the combination of AT-only, towing, and two-class license conditions complicates the types of licenses that require a driver's license. In fact, the crackdown may reveal that the driver is driving a vehicle that is not exempt, so it is important to ensure that the key to the type of vehicle that corresponds to the driver's exemption is handed over.

The present invention has been made in view of such a problem, and an object of the present invention is to provide a key management device or the like capable of reliably delivering a key of a vehicle of a type corresponding to a driver's exemption.

The first invention for solving the above-mentioned problems is a key management device for managing the key of a key storage device having a plurality of key boxes for storing and locking the key of the vehicle driven by the driver, and is a vehicle ID of the vehicle. In the vehicle selection unit that stores vehicle data including the key ID of the vehicle key and displays the vehicle ID of the type of vehicle corresponding to the driver's exemption so as to be selectable, and in the selected vehicle ID. It is a key management device including an unlocking permission unit for setting the key box of the key of the corresponding key ID in the unlocking permission state.

The key management device of the present invention can selectably display the vehicle ID of the type of vehicle corresponding to the driver's exemption. When the vehicle ID is selected, the key ID corresponding to the selected vehicle ID is extracted from the vehicle data, and the key box corresponding to the key ID is set to the unlock permission state. As a result, it is possible to hand over the key of the type of vehicle corresponding to the driver's exemption and dispatch the vehicle to prevent the driver from unqualified driving. Further, by permitting the key box of the selected vehicle key to be unlocked and locking the other key boxes, it is possible to prevent the key from being mixed up.

It is desirable that the key management device has a vehicle ID extraction unit that extracts the vehicle ID of the type of vehicle corresponding to the driver's license from the information read from the driver's license. It is desirable that the above information is the basic information of the driver's license that can be read from the IC chip of the driver's license without inputting the password.
The vehicle ID of the type of vehicle corresponding to the driver's license can be extracted by reading the information of the driver's license and identifying the driver from the information. By using the above information as basic information that can be read from the driver's license without inputting a password, it is possible to save the trouble of operation.

It is desirable that the key management device further has a roll call content recording unit that records the roll call content made between the driver and the roll call executor. It is also desirable to have an alcohol concentration recording unit that records the measured value of the alcohol concentration in the exhaled breath of the driver.
The key management device of the present invention has a roll call support function for recording the results of a roll call, an alcohol test, and the like, and can execute unlocking permission after the roll call and the alcohol test.

The second invention is a key management system having a key storage device having a plurality of key boxes for storing and locking the keys of a vehicle driven by a driver, and a key management device for managing the keys. , A vehicle selection unit that stores vehicle data including the vehicle ID of the vehicle and the key ID of the vehicle key and displays the vehicle ID of the type of vehicle corresponding to the driver's exemption in a selectable manner. The key management system is characterized by comprising an unlocking permission unit for setting the key box of the key of the key ID corresponding to the vehicle ID to the unlocking permission state.

The third invention is a key management device that manages the key of a key storage device having a plurality of key boxes for storing and locking the key of the vehicle driven by the driver, and obtains the vehicle ID of the vehicle and the key ID of the vehicle key. The key management device that stores the vehicle data including the vehicle data in the storage unit can selectably display the vehicle ID of the vehicle of the type corresponding to the driver's exemption, and the key ID corresponding to the selected vehicle ID. It is a key management method characterized by executing a step of setting the key box of a key to an unlocking permission state.

A fourth invention is a key storage device having a plurality of key boxes for storing and locking a computer for storing vehicle data including a vehicle ID of a vehicle driven by a driver and a vehicle key key ID in a storage unit. A key management device that manages the key of the vehicle, the vehicle selection unit that selectively displays the vehicle ID of the vehicle of the type corresponding to the driver's exemption, and the key ID corresponding to the selected vehicle ID. It is a program for functioning as a key management device including an unlocking permission unit for setting the key box of a key in an unlocking permission state.

INDUSTRIAL APPLICABILITY According to the present invention, it is possible to provide a key management device or the like capable of reliably delivering a key of a vehicle of a type corresponding to a driver's exemption.

The figure which shows the whole structure of a key management system 10. The figure which shows the hardware composition of the key management apparatus 1. The figure which shows the functional structure of the key management system 10. The figure which shows the license data 21 and the vehicle data 22. The figure which shows the license registration screen 200. The figure which shows the vehicle registration screen 300. The flowchart which shows the process of a key management system 10. The figure which shows the roll call screen 100. An example of the driver's license confirmation screen 110. An example of the alcohol test screen 120. An example of the roll call content recording screen 130. The flowchart which shows the input procedure such as a vehicle number 222. The figure which shows a part of the roll call content recording screen 130. The figure which shows the usage state data 23. The figure which shows the license data 21, the vehicle data 22, and the vehicle allocation data 24.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

[First Embodiment]
(1. Key management system 10)
FIG. 1 is a diagram showing an overall configuration of a key management system 10 according to an embodiment of the present invention. As shown in FIG. 1, the key management system 10 includes a key management device 1, a reading device 3, a key storage device 4, an alcohol detector 5, a camera 6, and the like.

The key management device 1 executes a process related to key management of a vehicle driven by a driver (driver) in a business operator such as a transportation industry. Further, the key management device 1 of the present embodiment also executes a process related to a driver's roll call and an alcohol test as a roll call support device.

FIG. 2 is a diagram showing a hardware configuration of the key management device 1. As shown in FIG. 2, the key management device 1 includes a control unit 11, a storage unit 12, a media input / output unit 13, a communication control unit 14, an input unit 15, a display unit 16, a peripheral device I / F unit 17, and the like. It can be realized by a computer connected via. The configuration shown in FIG. 2 is an example, and the key management device 1 can have various configurations depending on the application and purpose.

The control unit 11 has a CPU, ROM, RAM, and the like. The CPU calls a program stored in a recording medium such as a storage unit 12 or a ROM into a work memory area on RAM and executes it, and drives and controls each unit connected via a bus to drive and control each unit, which will be described later in the key management device 1. Realize each process. ROM is a non-volatile memory and permanently holds programs such as computer boot programs and BIOS, and data. The RAM is a volatile memory, and includes a work area used by the control unit 11 to perform various processes while temporarily holding programs and data loaded from a recording medium such as a storage unit 12 or a ROM.

The storage unit 12 is a hard disk drive, a flash memory, or the like, and stores a program executed by the control unit 11, data necessary for program execution, an OS, and the like. In particular, in the present embodiment, the storage unit 12 stores an application program and a database 2 for causing the key management device 1 to execute the processing described later.

The media input / output unit 13 is an interface for writing data to and reading data from a recording medium (media) such as a memory card.

The communication control unit 14 is a communication interface that mediates the communication of the key management device 1, and controls the communication with other devices and the like via the network. The network can be wired or wireless.

The input unit 15 includes an input device such as a keyboard, a mouse, and a touch panel. The input unit 15 transmits data and operation instructions input via the input device to the control unit 11.

The display unit 16 includes a display such as a liquid crystal panel, and displays data such as an image or text on the display according to the instructions of the control unit 11.

The peripheral device I / F (interface) unit 17 is a port for connecting peripheral devices, and the control unit 11 transmits / receives data to / from peripheral devices via the peripheral device I / F unit 17.

Returning to the description of FIG. The reading device 3 reads the driver's license, and includes a reader and a scanner. The reader reads the basic information of the driver's license stored in the IC chip (not shown) of the driver's license. Basic information will be described later. The scanner captures the driver's license placed on the glass table with an image sensor such as CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor) and acquires the license image.

The key storage device 4 has a plurality of key boxes 41 for storing the keys of the vehicle driven by the driver, and locks each key box 41. The key of the vehicle owned by the business operator is stored in each key box 41, and the key ID of the key to be stored is assigned to each of these key boxes 41. In the present embodiment, the key number described later is used as the key ID, but the present invention is not limited to this, and any identification information that can identify each key may be used.

The alcohol detector 5 measures the alcohol concentration of the driver's exhaled breath. A known alcohol detector 5 can be used.

The camera 6 is a camera that uses an image pickup device such as a CCD or CMOS, and captures the appearance of the driver at the time of roll call as a moving image.

FIG. 3 is a diagram showing a functional configuration of the key management system 10. As shown in FIG. 3, the key management device 1 of the key management system 10 includes a vehicle ID extraction unit 101, a vehicle selection unit 102, an unlocking permission unit 103, an alcohol concentration recording unit 104, a roll call content recording unit 105, and the like. Further, the license data 21, the vehicle data 22, and the like are stored in the database 2 of the storage unit 12.

The vehicle ID extraction unit 101 identifies the driver using the basic information read from the driver's driver's license, and corresponds to the driver's license (the type of vehicle for which the driver has a driver's license). Extract the vehicle ID of the vehicle. The types of vehicles include, for example, large special, large size, large size (micro limited), medium size, medium size (8t limited), quasi-medium size, quasi-medium size (5t limited), and ordinary. In the present embodiment, the vehicle number described later is used for the vehicle ID, but the present invention is not limited to this, and any identification information that can identify individual vehicles may be used.

The vehicle selection unit 102 can selectably display the vehicle ID of the type of vehicle corresponding to the driver's exemption on the display unit 16.

The unlocking permission unit 103 sets the key box 41 of the key of the key ID corresponding to the selected vehicle ID to the unlocking permission state.

The alcohol concentration recording unit 104 records the measured value of the alcohol concentration in the exhaled breath of the driver input from the alcohol detector 5.

The roll call content recording unit 105 records the roll call content made between the driver and the roll call executor.

(2. License data 21 and vehicle data 22)
As shown in FIG. 4, the license data 21 includes the driver's license license number 211, issuance date 212, expiration date 213, license image 214, driver's name 215, date of birth 216, and license. Information such as acquisition date 217, license 218, license condition 219, etc. is recorded. This information is registered for each driver. The exemption type 218 is, for example, the above-mentioned large special, large size, large size (micro limited), medium size, medium size (8t limited), quasi-medium size, quasi-medium size (5t limited), normal and the like.

Information other than the license image 214 is also stored in the IC chip of the driver's license, of which the license number 211, the date of issuance 212, and the expiration date 213 can be read from the IC chip without entering the password. Information 210.

The license data 21 can be registered by displaying the license registration screen 200 as shown in FIG. 5 on the display unit 16 of the key management device 1. The license registration screen 200 includes a license image display field 201, a basic information display field 202, a license data input field 204, a "registration" button 206, a "password input" button 207, and the like. In addition, on the license registration screen 200, a button for giving a driver's license reading instruction to the reading device 3, a button for returning to the previous screen, an operation guide, and the like may be displayed.

At the time of registration of the license data 21, the driver causes the reading device 3 to read the driver's license. That is, the reading device 3 reads the basic information 210 from the IC chip of the driver's license, takes a picture of the driver's license, acquires the license image 214, and obtains the basic information 210 and the license from the reading device 3 to the key management device 1. The driver's license image 214 is input. The license image 214 is displayed in the license image display field 201, and the basic information 210 (license number 211, issuance date 212, expiration date 213) is displayed in the basic information display field 202.

In the basic information display field 202, the result of the forgery determination as to whether or not the driver's license is forged 2021 and the number of remaining days 2022 until the expiration date 213 are also displayed. The forgery determination can be performed using the license image 214, and the remaining days 2022 are calculated by the key management device 1 as the number of days from the day when the driver's license is read to the expiration date 213. By confirming this information, only the license data 21 of a valid driver's license can be registered.

The license data input field 204 is for inputting information of the license data 21 other than the basic information 210 and the license image 214. The information can be directly input by typing in each input field, but it can also be automatically input by pressing the "PIN input" button 207. That is, by pressing the "password input" button 207 to display the password input screen (not shown) and inputting the driver's license password on the screen, other than the basic information 210 and the license image 214. The information of the license data 21 is read from the IC chip of the driver's license and automatically input into each input field of the license data input field 204.

The "registration" button 206 is a button for registering the license data 21. When the "register" button 206 is pressed, the key management device 1 registers the input license data 21 in the database 2.

On the other hand, as shown in FIG. 4, the vehicle data 22 includes the vehicle name 221 of the vehicle, the vehicle number 222, the vehicle type 223, the gross vehicle weight 224, the maximum load capacity 225, the passenger capacity 226, the vehicle inspection expiration date 227, and the vehicle. The key number 228 and the like of the key are recorded for each vehicle owned by the business operator. The type 223 of the vehicle is the same as the above-mentioned exemption type 218, for example, the above-mentioned large special, large size, large size (micro limited), medium size, medium size (8t limited), quasi-medium size, quasi-medium size (5t limited), normal and the like. be.

The vehicle data 22 can be registered by displaying the vehicle registration screen 300 as shown in FIG. 6 on the display unit 16 of the key management device 1. The vehicle registration screen 300 has a vehicle data input field 301, an "update" button 304, and the like. The registrant inputs each information of the vehicle data 22 in each input field of the vehicle data input field 301, and presses the "update" button 304. Then, the key management device 1 registers the input vehicle data 22 in the database 2. In addition, the vehicle registration screen 300 may be provided with a button for closing the vehicle registration screen 300 and canceling the vehicle registration, a button for deleting the input content, and the like.

(3. Key management method)
Next, the flow of the key management method in the key management system 10 will be described with reference to FIG. 7 and the like. FIG. 7 is a flowchart showing the process of the key management system 10, and S1, S4 to S7, and S10 to S16 in the figure are processes executed by the control unit 11 of the key management device 1. S2 and 3 are the control unit of the reading device 3 (not shown), S8 and 9 are the control unit of the alcohol detector 5 (not shown), and S17 and 18 are the control unit of the key storage device 4 (not shown). Run.

The key management device 1 starts the application in response to the instruction input of the roll call executor, and displays the roll call screen 100 as shown in FIG. 8 (S1). The roll call screen 100 includes a driver's license confirmation screen 110, an alcohol inspection screen 120, a roll call content recording screen 130, a roll call status confirmation screen 140, and the like.

On the driver's license confirmation screen 110, an operation guide such as "Please hold your license" is displayed. When the driver holds the driver's license over the reading device 3, the reading device 3 reads the basic information 210 from the IC chip of the driver's license (S2) and transmits the basic information 210 to the key management device 1 (S3).

When the key management device 1 receives the basic information 210 (S4), the license data 21 including the basic information 210 is extracted from the database 2 (S5), whereby the driver holding the driver's license holds the driver's license on the system. Be identified. If the driver's license data 21 including the basic information 210 is not registered in the database 2, it is possible to display on the driver's license confirmation screen 110 that the driver's license held by the driver is invalid.

The key management device 1 displays the license data 21 extracted in S5 on the driver's license confirmation screen 110 (S6). FIG. 9 is an example of the driver's license confirmation screen 110 at this time, and the expiration date 213, the license image 214, the driver's name 215, the license type 218, the license condition 219, etc. are displayed as the license data 21. Further, on the driver's license confirmation screen 110, the number of remaining days up to the expiration date 213, the roll call date and time 112 (current date and time), the "delivery" button 113, the "intermediate" button 114, the "return" button 115, and the like are also displayed.

The number of remaining days 111 is calculated by the key management device 1 by comparing the roll call date and time 112 with the expiration date 213. Further, the "delivery" button 113 is a button for recording the roll call history information described later as a delivery time call. The "intermediate" button 114 is a button for recording the roll call history information as a roll call (between delivery and return) not before and after the flight. The "return" button 115 is a button for recording roll call history information as a call at the time of return.

The roll call executor confirms that the driver's license is valid by looking at the license image 214 and the expiration date 213 of the driver's license confirmation screen 110, and confirms that the driver's license is valid, and the "delivery" button 113, "intermediate" button 114, and "return" Press any of the buttons 115. Then, the key management device 1 records the confirmation result of the driver's license (the driver's license is valid) and the roll call date / time 112 in the storage unit 12 or the like (S7).

In this embodiment, an example of making a call at the time of delivery is described, and here, it is assumed that the “delivery” button 113 is pressed. A mark indicating that the driver's license has not been confirmed is displayed on the driver's license confirmation screen 110 until any of the "delivery" button 113, the "intermediate" button 114, and the "return" button 115 is pressed. When any of the "delivery" button 113, the "intermediate" button 114, and the "return" button 115 is pressed, a mark indicating that the driver's license has been confirmed is displayed on the driver's license confirmation screen 110. good.

Subsequently, the key management device 1 displays an initial screen as shown in FIG. 10A on the alcohol inspection screen 120. On the alcohol inspection screen 120, a real-time moving image 121 of the driver taken by the camera 6 is displayed, and an operation guide such as "Please blow breath" is displayed in the message field 122. When the driver presses the measurement button (not shown) of the alcohol detector 5 and blows the alcohol detector 5, the alcohol detector 5 measures the alcohol concentration in the exhaled breath (S8), and the measured value is used as the key management device 1. (S9).

When the key management device 1 receives the measured value of the alcohol concentration (S10), the received measured value is displayed in the alcohol concentration column 123 as shown in FIG. 10 (b) (S11). In the message field 122, the fact that the analysis has been completed and the operation guide are displayed. The measured value of the alcohol concentration can also be directly input to the alcohol concentration column 123.

The "confirm" button 124 on the alcohol test screen 120 is a button for confirming the measured value of the alcohol concentration, and the roll call executor confirms the alcohol concentration and presses the "confirm" button 124 to measure the alcohol concentration. The value is recorded in the storage unit 12 or the like (S12).

It is also possible that the key management device 1 determines whether or not the driver can be on board by comparing the measured value of the alcohol concentration with a predetermined value, and records the determination result together with the measured value in S12. If it is determined that the flight is not possible, it is possible not to grant the unlocking permission described later. Further, as described above, a mark indicating that the alcohol test has not been executed is displayed on the alcohol test screen 120 until the "confirm" button 124 is pressed, and when the "confirm" button 124 is pressed, the alcohol test is performed. The mark indicating that the above has been executed may be displayed on the alcohol test screen 120.

Subsequently, the roll call executor makes a roll call with the driver. The roll call content is input to the roll call content recording screen 130, and the key management device 1 accepts the input of the roll call content (S13). Here, it is assumed that a face-to-face roll call is performed. The face-to-face roll call is a process in which the driver and the roll call executor face each other to check the driver's health condition, give cautions and instructions, confirm the driver's identity, confirm the vehicle allocation, and the like.

In S13, the roll call content is input and displayed in the roll call content input field 131 of the roll call content recording screen 130 shown in FIG. In the roll call content input field 131, the weather at the time of the roll call 1310, the health condition of the driver 1311, the result of the daily inspection 1312, the confirmation item 1313 at the time of the roll call, the instruction item 1314, the name of the operation manager 1315, the name of the roll call executor 1316, The driver's name 215, work content 1318, etc. are input.

For example, the weather 1310 can be selected and input from the weather conditions such as sunny, cloudy, wind, rain, and snow. The initial value of the driver's health state 1311 is "○", but when a special item is input, the display of "○" disappears and the special item is displayed. The result of the daily inspection 1312 is the result of the daily inspection of the vehicle driven by the driver, and the initial value is "○" as above. Is displayed. The driver's name 215 is automatically input from the license data 21 extracted in S5.

Further, in the roll call content input field 131, the vehicle number 222, the type 223, the vehicle inspection expiration date 227, the key number 228, and the like of the vehicle driven by the driver are also input. The details of this input procedure will be described later. Other roll call contents can be input directly in the input field, but input candidates can be displayed as options and input by selecting from there.

When the roll call executor confirms that the driver can carry out the crew with the vehicle number 222 by looking at the roll call contents in each input field, he presses the "roll call end" button 134. Then, the key management device 1 records the roll call content input in the roll call content input field 131 in the storage unit 12 or the like (S14). Similar to the above, a mark indicating that the roll call has not been executed is displayed on the roll call content recording screen 130 until the "roll call end" button 134 is pressed, and when the "roll call end" button 134 is pressed, the roll call is performed. The mark indicating that the above has been executed may be displayed on the roll call content recording screen 130.

Further, when the roll call executor presses the "record" button 136, the key management device 1 has the confirmation result of the driver's license recorded in the storage unit 12 or the like, the roll call date and time, the measured value of the alcohol concentration, the roll call content, etc. Is linked and registered in the storage unit 12 as roll call history information (S15). Depending on which of the "delivery" button 113, the "intermediate" button 114, and the "return" button 115 in FIG. 9 is pressed, the roll call history information is the one at the time of delivery and the one not before and after the flight (delivery and return). It is registered as either the one in the warehouse) or the one at the time of returning. It is also possible to register a moving image of the driver taken by the camera 6 or a still image obtained by cutting out a predetermined timing of the moving image as roll call history information.

The roll call history information is displayed on the roll call status confirmation screen 140, which can be confirmed and printed out as a roll call record book. On the roll call status confirmation screen 140, it is also possible to display roll call history information for each driver's crew status, such as the driver has returned to the garage or the driver has not returned to the garage. The roll call content recording screen 130 shown in FIG. 11 may be provided with a button for closing the roll call content recording screen 130 and a button for erasing the content input in the roll call content input field 131.

After registering the roll call history information, the key management device 1 unlocks the key including the key number 228 so as to set the key box 41 of the key number 228 entered in the roll call content input field 131 to the unlock permission state. The permission is transmitted to the key storage device 4 (S16).

When the key storage device 4 receives the unlock permission from the key management device 1 (S17), the key box 41 of the key with the key number 228 is set to the unlock permission state (S18). In the present embodiment, the door of the key box 41 is unlocked by setting the key box 41 in the unlock permission state and the driver inputting specific information into the key storage device 4. The specific information is, for example, the information of the license data stored in the IC chip of the driver's license, the password for unlocking, and the like.

(4. Input of vehicle number 222 etc.)
As described above, in S13, information such as the vehicle number 222, the type 223, the vehicle inspection expiration date 227, and the vehicle key key number 228 of the vehicle driven by the driver is input to the roll call content input field 131. FIG. 12 is a flowchart showing this input procedure, and each step in the figure is executed by the control unit 11 of the key management device 1.

In this embodiment, as shown in FIG. 13A as a part of the roll call content recording screen 130, an operation guide such as "Please select a vehicle number" is displayed in the input field of the vehicle number 222, and the roll call is executed. Selects this input field. Then, the key management device 1 refers to the vehicle data 22 and extracts all the vehicle numbers 222 of the vehicle of the type 223 corresponding to the license type 218 of the license data 21 obtained in S5 (S21), and the extracted vehicle number 222. Is displayed selectably by a pull-down list 137 or the like as shown in FIG. 13 (b) (S22).

When the roll call executor selects the vehicle number 222 of the vehicle driven by the driver based on the roll call result with the driver, the key management device 1 has the key number 228, the type 223, and the vehicle inspection expiration date 227 corresponding to the vehicle number 222. (S23), the vehicle number 222 selected as shown in FIG. 13 (c), the corresponding key number 228, the type 223, and the vehicle inspection expiration date 227 are entered in the roll call content input field 131, respectively. Automatically input and display (S24).

In this way, when the vehicle number 222 is input, only the vehicle number 222 of the vehicle of the type 223 corresponding to the driver's exemption type 218 is displayed so as to be selectable, so that the key of the vehicle other than the driver's exemption type in S16 is displayed. It is no longer necessary to permit unlocking of the box 41, and it is possible to prevent the driver from unqualified driving.

According to the present embodiment described above, the key management device 1 can selectably display the vehicle number 222 of the vehicle of the type 223 corresponding to the driver's exemption type 218. When the vehicle number 222 is selected, the key number 228 corresponding to the selected vehicle number 222 is extracted from the vehicle data 22, and the key box 41 corresponding to the key number 228 is set to the unlock permission state. As a result, it is possible to hand over the key of the vehicle of the type 223 corresponding to the driver's exemption type 218 and dispatch the vehicle, and prevent the driver from unqualified driving. Further, by permitting the key box 41 of the selected vehicle key to be unlocked and locking the other key boxes 41, it is possible to prevent the key from being mixed up.

The vehicle number 222 of the vehicle of type 223 corresponding to the driver's license type 218 can be extracted by reading the basic information 210 from the driver's license and specifying the driver (license data 21) from the basic information 210. .. Since the above basic information 210 is information that can be read from the driver's license without inputting a password, it is possible to save the trouble of operation. However, other information of the license data 21 may be read from the driver's license by inputting a password or the like.

Further, the key management device 1 of the present embodiment has a roll call support function for recording the results of a roll call, an alcohol test, and the like, and can execute unlocking permission after the roll call and the alcohol test.

However, the present invention is not limited to this. For example, in the present embodiment, face-to-face roll call is performed, but the alcohol detector 5 and the reader 3 are installed in a place away from the key management device 1 so as to be able to communicate with the key management device 1, and the roll call is executed by using a telephone or the like. It is also possible to perform alcohol tests and roll calls for drivers who are far away from the person.

Further, in the present embodiment, in order to identify the driver, the driver's license basic information 210 is read by the reading device 3 in S2, and the license data 21 corresponding to the basic information 210 is extracted in S5. Some information of the license data 21 such as the name 215 may be directly input to the key management device 1 to extract the license data 21 corresponding to the information.

Further, it is also possible to further store the vehicle usage status data 23 as shown in FIG. 14 in the database 2. The usage status data 23 is a link between the vehicle number 222 of each vehicle owned by the business operator and the usage status 231 thereof. The usage status 231 records whether the vehicle is in use or not. For example, when the key box 41 is unlocked by the key storage device 4, the vehicle number 222 corresponding to the key number 228 of the key box 41 in the vehicle data 22. The usage status 231 of the above is defined as "in use".

In the above S22 (see FIG. 12), the usage status data 23 is referred to, and the vehicle number 222 whose usage status 231 is "in use" is not displayed as the selectable vehicle number 222, or is in use. It is displayed so that it can be recognized, and this vehicle number 222 is not selected. This makes it possible to prevent the vehicle number 222 of the vehicle in use from being erroneously selected.

Next, another example of the present invention will be described as a second embodiment. The second embodiment will be described with respect to the points different from those of the first embodiment, and the same points will be omitted by the same reference numerals in the drawings and the like.

[Second Embodiment]
In the second embodiment, the database 2 further has vehicle allocation data 24 including the driver's name 215, vehicle number 222, work content 241 and the like, as shown in FIG.

The vehicle number 222 of the vehicle allocation data 24 is a pre-recorded vehicle number 222 of the type 223 vehicle corresponding to the driver exemption type 218 among the vehicle number 222 of the vehicle data 22. Further, the work performed by the driver using the vehicle having the vehicle number 222 is input to the work content 241.

The key management method is basically the same as that of the first embodiment. However, in the present embodiment, the vehicle allocation data 24 is referred to in the above S21 (see FIG. 12), all the vehicle numbers 222 corresponding to the name 215 of the license data 21 obtained in S5 are extracted, and the extracted vehicle number 222 is used. In S22, the roll call content input field 131 is displayed so as to be selectable in the same manner as in FIG. 13 (b). When the roll call executor selects the vehicle number 222, the key management device 1 extracts the work content 241 corresponding to the vehicle number 222 from the vehicle allocation data 24 in addition to the key number 228 and the like described above, and automatically inputs the work content 241 into the roll call content input field 131. do.

In the present embodiment, the vehicle number 222 of the vehicle of the type 223 corresponding to the driver's exemption type 218 can be extracted from the vehicle allocation data 24, and by displaying this in a selectable manner, the same effect as that of the first embodiment can be obtained. Be done. Further, in the present embodiment, by registering which driver uses which vehicle and what kind of work is performed as vehicle allocation data 24, it is possible to smoothly allocate an appropriate vehicle according to the type of driver's license. ..

In addition, prioritize the vehicle number 222 of the vehicle allocation data 24 according to the driver's work, etc., and when displaying the vehicle number 222 selectably in S22, the display order of the vehicle number 222 based on the vehicle allocation data 24. It is also possible to set. For example, the vehicle number 222 related to a higher priority business can be displayed higher.

Although the preferred embodiments of the present invention have been described above with reference to the accompanying drawings, the present invention is not limited to these examples. It is clear that a person skilled in the art can come up with various modified or modified examples within the scope of the technical idea disclosed in the present application, and these also naturally belong to the technical scope of the present invention. Understood.

1: Key management device 2: Database 3: Reading device 4: Key storage device 5: Alcohol detector 6: Camera 10: Key management system 21: License data 22: Vehicle data 23: Usage status data 24: Vehicle allocation data 41: Key box 210: Basic information 211: License number 212: Date of issuance 213: Expiration date 214: License image 215: Name 216: Date of birth 217: License acquisition date 218: License type 219: License condition 221: Vehicle Name 222: Vehicle number 223: Vehicle type 224: Gross vehicle weight 225: Maximum load capacity 226: Riding capacity 227: Vehicle inspection expiration date 228: Key number 231: Usage status 241: Work content

Claims (8)

A key management device that manages the keys of a key storage device that has multiple key boxes that store and lock the keys of the vehicle driven by the driver.
Vehicle data including the vehicle ID of the vehicle and the key ID of the vehicle key is stored in the storage unit.
A vehicle selection unit that selectively displays the vehicle ID of the type of vehicle corresponding to the driver's exemption, and
An unlocking permission unit that sets the key box of the key of the key ID corresponding to the selected vehicle ID to the unlocking permission state, and
A key management device characterized by being equipped with. The key management device according to claim 1, further comprising a vehicle ID extraction unit that extracts the vehicle ID of a vehicle of a type corresponding to the driver's license from the information read from the driver's license. The key management device according to claim 2, wherein the information is basic information of a driver's license that can be read from an IC chip of the driver's license without inputting a personal identification number. The key management device according to any one of claims 1 to 3, further comprising a roll call content recording unit for recording the roll call content made between the driver and the roll call executor. The key management device according to any one of claims 1 to 4, further comprising an alcohol concentration recording unit for recording an alcohol concentration measurement value in the exhaled breath of a driver. It is a key management system having a key storage device having a plurality of key boxes for storing and locking the keys of a vehicle driven by a driver, and a key management device for performing key management.
The key management device is
Vehicle data including the vehicle ID of the vehicle and the key ID of the vehicle key is stored in the storage unit.
A vehicle selection unit that selectively displays the vehicle ID of the type of vehicle corresponding to the driver's exemption, and
An unlocking permission unit that sets the key box of the key of the key ID corresponding to the selected vehicle ID to the unlocking permission state, and
A key management system characterized by being equipped with. It is a key management device that manages the key of a key storage device having a plurality of key boxes for storing and locking the key of the vehicle driven by the driver, and stores vehicle data including the vehicle ID of the vehicle and the key ID of the vehicle key. The key management device to be stored in
A step of selectively displaying the vehicle ID of the type of vehicle corresponding to the driver's exemption, and
A step of setting the key box of the key of the key ID corresponding to the selected vehicle ID to the unlock permission state, and
A key management method characterized by executing. A computer that stores vehicle data including the vehicle ID of the vehicle driven by the driver and the key ID of the vehicle key in the storage unit.
A key management device that manages the keys of a key storage device that has multiple key boxes for storing and locking vehicle keys.
A vehicle selection unit that selectively displays the vehicle ID of the type of vehicle corresponding to the driver's exemption, and
An unlocking permission unit that sets the key box of the key of the key ID corresponding to the selected vehicle ID to the unlocking permission state, and
A program for functioning as a key management device.

Images