Driving Management System

Abstract

To provide a driving management system and a driving management server that facilitate the creation of usage reports.SOLUTION: A driving management system 1 includes: an on-vehicle apparatus 10 that is mounted on a vehicle and acquires a traveling status of the vehicle; and a server 50 that can communicate with the on-vehicle apparatus 10 via a wireless communication line. The server 50 includes: a communication unit 51 that receives the traveling status from the on-vehicle apparatus 10; and a report creation unit 52 that creates vehicle usage report data based on the traveling status.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to a driving management system and a server for driving management.

Background Art

[0002] A system that determines a driver (i.e., a user) and permits the use of a vehicle is known (see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the case of a vehicle used in a business (i.e., a company vehicle), the user needs to create a usage report after using the vehicle. The usage report needs to describe information such as the boarding time and location, the alighting time and location, etc.

[0005] Therefore, in a vehicle that travels to multiple locations, the amount of information to be described increases, resulting in an increase in the user's effort. In addition, there is a risk of incorrect entry or omission in the usage report, making it impossible to properly manage the vehicle.

[0006] One aspect of the present disclosure aims to provide a driving management system that facilitates the creation of a usage report.

Means for Solving the Problems

[0007] One aspect of the present disclosure is a driving management system comprising an in-vehicle device installed in a vehicle and configured to acquire the vehicle's driving conditions, and a server capable of communicating with the in-vehicle device via a wireless communication line. The server includes a communication unit configured to receive driving conditions from the in-vehicle device, and a report generation unit configured to create vehicle usage report data based on the driving conditions.

[0008] With this configuration, usage report data is automatically generated based on driving conditions acquired by in-vehicle equipment, making it easier to create usage reports. Furthermore, errors and omissions in usage reports can be reduced.

[0009] In one aspect of this disclosure, the usage report data may include at least one boarding time, at least one alighting time, at least one boarding location, at least one alighting location, travel time, and travel distance for the vehicle. Such a configuration reduces the input burden on users when filling out usage reports.

[0010] One aspect of this disclosure may further include a terminal device capable of communicating with a server. The server may have an operating rate recording unit configured to record the daily operating rate of a vehicle based on its driving conditions. The communication unit may be configured to transmit the operating rate to the terminal device. The terminal device may have a display unit configured to highlight and display the operating rate according to its magnitude. With such a configuration, the user's health can be managed based on the operating rate.

[0011] In one aspect of this disclosure, the server may have a driving evaluation unit configured to evaluate the degree of safe driving in the vehicle based on driving conditions. Such a configuration allows for understanding the user's health status, educational needs, etc.

[0012] One aspect of this disclosure may further include an alcohol checker for performing alcohol checks on vehicle users. The report generation unit may be configured to embed the user's test results obtained by the alcohol checker into the usage report data. Such a configuration facilitates a reduction in the effort required to create usage reports.

[0013] One aspect of this disclosure may further include a terminal device capable of communicating with a server. The server may have a notification unit configured to notify the terminal device of the approaching of a predetermined vehicle inspection date. Such a configuration facilitates the management of vehicle inspection dates by the user or administrator.

[0014] Another aspect of this disclosure is a driving management server that is mounted in a vehicle and is capable of communicating via a wireless communication line with an in-vehicle device configured to acquire the vehicle's driving status. The driving management server comprises a communication unit configured to receive driving status from the in-vehicle device, and a report generation unit that creates vehicle usage report data based on the driving status.

[0015] With this configuration, the items in the usage report data are automatically entered based on the driving status of the in-vehicle equipment, making it easier to create the usage report. [Brief explanation of the drawing]

[0016] [Figure 1] Figure 1 is a block diagram schematically showing the configuration of the operation management system in the embodiment. [Figure 2] Figure 2 shows an example of how usage report data generated by the server's report generation unit in the operation management system shown in Figure 1 is displayed. [Figure 3] Figure 3 is a block diagram schematically showing the configuration of an operation management system in an embodiment different from that shown in Figure 1. [Modes for carrying out the invention]

[0017] Embodiments to which this disclosure applies will be described below with reference to the drawings. [1. First Embodiment] [1-1. Configuration] The operation management system 1 shown in FIG. 1 manages a plurality of business vehicles. The operation management system 1 includes an in-vehicle device 10, an alcohol checker 30, a server 50, and a terminal device 70.

[0018] [In-vehicle device] The in-vehicle device 10 is mounted on each of a plurality of vehicles and is configured to acquire the running status of the mounted vehicle. The in-vehicle device 10 can communicate with the server 50 via a wireless communication line. The in-vehicle device 10 has an acquisition unit 11 and a recording unit 12.

[0019] [Acquisition unit] The acquisition unit 11 is configured to acquire the running status of the vehicle. The running status acquired by the acquisition unit 11 includes running information data such as the current position of the vehicle, the route traveled by the vehicle, the speed history, the position where the vehicle stopped, the operating period of the prime mover (that is, the engine or motor), and the presence or absence of impact occurrence.

[0020] The acquisition unit 11 acquires running information data from various sensors of the in-vehicle device 10 or the vehicle. Examples of the sensors include a position sensor using GPS (Global Positioning System), an acceleration sensor, and the like.

[0021] In addition, the acquisition unit 11 recognizes the user by the user's mobile terminal 100 (for example, a smartphone), reading the driver's license, or a camera of the in-vehicle device 10. The acquisition unit 11 recognizes the user when the vehicle is started (that is, when the in-vehicle device 10 is started). When the time from the stop to the restart of the in-vehicle device 10 is less than or equal to a predetermined threshold value, the acquisition unit 11 uses the user information before the stop as the user information after the restart and does not perform user recognition again.

[0022] [Recording unit] The recording unit 12 records the identification information of the vehicle user, the running information data acquired by the acquisition unit 11, and the like.

[0023] <Alcohol checker> The alcohol checker 30 performs an alcohol check on the user (i.e., the driver). The alcohol checker 30 is a known device that detects the alcohol concentration in the breath.

[0024] The alcohol checker 30 is installed inside the vehicle or in the vehicle's storage area. Users should take a test using the alcohol checker 30 at the designated time (for example, at the start of driving).

[0025] The test results from the alcohol checker 30 are sent to the server 50, for example, via the user's mobile terminal 100, along with the user's identification information. The alcohol checker 30 may also be connected to the in-vehicle device 10 by wire or wireless connection. This allows the in-vehicle device 10's camera to capture images of the test process and send the test images along with the test results to the server 50.

[0026] <server> The server 50 is capable of communicating with in-vehicle equipment 10 installed in each of the multiple vehicles via wireless communication lines, and also with terminal devices 70.

[0027] Server 50 is composed of a computer, for example, a processor, a storage medium, and a communication interface. Server 50 has a communication unit 51, a report generation unit 52, an operating rate recording unit 53, an operation evaluation unit 54, and a notification unit 55.

[0028] (Communications Department) The communication unit 51 is configured to receive driving conditions, user identification information, and the test results from the alcohol checker 30 from the in-vehicle equipment 10 and the mobile terminal 100.

[0029] Furthermore, the communications unit 51, upon receiving a request from the terminal device 70, transmits management information for the designated vehicle to the terminal device 70. The management information includes usage report data, operating rate, and degree of safe driving.

[0030] (Report Preparation Department) The report generation unit 52 is configured to create vehicle usage report data based on the driving conditions received by the communication unit 51.

[0031] Figure 2 shows an example of the display of usage report data created by the report creation unit 52. Figure 2 is an image of the usage report data displayed on the display unit 72 of the terminal device 70.

[0032] The usage report data includes at least one boarding time, at least one alighting time, at least one boarding location, at least one alighting location, travel time, and travel distance for the vehicle in question. The report creation unit 52 extracts these items from the travel information data and sorts them.

[0033] The usage report data also includes user information (e.g., name, affiliation, identification number, etc.), the user's alcohol test results, information on other passengers in the vehicle, and other information.

[0034] The report creation unit 52 uses, for example, identification information transmitted from the user's mobile terminal 100 to the server 50 when the user is recognized, as user information. The report creation unit 52 also embeds the user's test results obtained by the alcohol checker 30 into the user report data.

[0035] Information about passengers may be automatically detected by the in-vehicle device 10, or it may be directly entered by the user via the terminal device 70. Other information may include, for example, whether or not refueling, car washing, and toll roads were used or the fees charged. Other information may also include any vehicle abnormalities detected by the user. This other information may be entered by the user via the terminal device 70, for example.

[0036] The format of the usage report data can be designed as appropriate to suit the operators of the operation management system 1. The report creation unit 52 outputs the usage report data in CSV format, for example, which is easily convertible to other data formats.

[0037] The report creation unit 52 creates usage report data in response to a request from the user's mobile terminal 100 or terminal device 70. The report creation unit 52 may also automatically create the usage report data for the day at a predetermined time (for example, the end of business hours).

[0038] (Operating rate recording unit) The operating rate recording unit 53 shown in Figure 1 is configured to record the daily operating rate of the vehicle based on the driving conditions received by the communication unit 51.

[0039] Specifically, the operating rate recording unit 53 calculates and lists the total daily driving time of the target vehicle, or the total driving time divided by a specific period (for example, 24 hours or a predetermined business time).

[0040] (Operation Evaluation Department) The driving evaluation unit 54 is configured to evaluate the degree of safe driving in the vehicle based on the driving conditions received by the communication unit 51.

[0041] Specifically, the driving evaluation unit 54 evaluates the degree of safe driving by comparing (for example, a ratio) the number of dangerous events per unit time with an acceptable value. In other words, the driving evaluation unit 54 considers the degree of safe driving to be higher the fewer dangerous events occur. The acceptable value for the number of dangerous events is set based on information such as distance traveled, travel time, and travel route included in the driving conditions received by the communication unit 51.

[0042] Dangerous events include the number of times sudden acceleration or deceleration occurs, the number of times the legal speed limit is exceeded, the number of times impacts are detected, the number of times the driver swerves, falls asleep at the wheel, is distracted, uses a mobile phone, smokes, exceeds the alcohol concentration limit, and engages in aggressive driving. The number of times the driver falls asleep, is distracted, uses a mobile phone, and smokes is determined by the driving evaluation unit 54 based on images acquired by, for example, the camera of the in-vehicle device 10.

[0043] (Notification Department) The notification unit 55 is configured to notify the terminal device 70 of the approaching date of a predetermined vehicle inspection.

[0044] The inspection date is the date of a legally mandated vehicle inspection or an inspection voluntarily conducted by the vehicle manager. The inspection date is entered for each vehicle via the terminal device 70 and recorded on the server 50.

[0045] Notification of inspection dates is given at regular intervals, or if the inspection record is not entered into the server 50 by a predetermined deadline (for example, one month before the inspection deadline). The notification unit 55 may also notify the terminal device 70 of the vehicle's inspection deadline and the renewal date of the driver's license of the registered vehicle user. Furthermore, the notification unit 55 may also notify the terminal device 70 when the vehicle's mileage exceeds a certain amount.

[0046] As shown in Figure 3, the server 50 may communicate with the in-vehicle device 10 via the mobile terminal 100. In other words, the communication unit 51 of the server 50 does not need to communicate directly with the in-vehicle device 10.

[0047] <Terminal device> The terminal device 70 can communicate with the server 50 via a wide-area network such as the Internet. The terminal device 70 is composed of a computer, for example, a processor, a storage medium, an input / output unit, and a communication interface.

[0048] For example, a smartphone, tablet, or personal computer can be used as the terminal device 70. The terminal device 70 has a receiving unit 71 and a display unit 72.

[0049] (Receiving unit) The receiving unit 71 is configured to receive vehicle management information and notifications from the server 50.

[0050] (Display) The display unit 72 is configured to display as an image the vehicle management information received by the receiving unit 71 (i.e., usage report data, operating rate, and degree of safe driving) and the notification content issued by the notification unit 55.

[0051] The display unit 72 displays the usage report data according to the set format. The display unit 72 also highlights the utilization rate according to the magnitude of the utilization rate included in the management information. For example, the display unit 72 sets the background of utilization rates above a certain value to a warning color (e.g., red) and increases the display size of the utilization rate (i.e., the font size). Furthermore, the display unit 72 displays a warning icon next to utilization rates above a certain value.

[0052] [1-2. Effects] According to the embodiments described in detail above, the following effects can be obtained. (1a) Since the items of the usage report data are automatically entered based on the driving conditions acquired by the in-vehicle device 10, it becomes easier to create the usage report. In addition, errors and omissions in the usage report can be suppressed.

[0053] (1b) The user's input burden on the usage report is reduced by including at least one boarding time, at least one alighting time, at least one boarding location, at least one alighting location, travel time, and travel distance in the usage report data.

[0054] (1c) By highlighting the utilization rate according to the magnitude of the vehicle's daily utilization rate, it is possible to manage the health of users based on the utilization rate. In addition, it is possible to review the number of vehicles to be managed (i.e., to be kept) based on the utilization rate.

[0055] (1d) By evaluating the degree of safe driving in the vehicle based on driving conditions, it is possible to understand the user's health condition and educational needs.

[0056] (1e) By embedding the user's test results obtained by the alcohol checker 30 into the usage report data, the effort required to create usage reports is reduced. (1f) Notification of inspection dates by the notification unit 55 makes it easier for users or administrators to manage vehicle inspection dates.

[0057] [2. Other Embodiments] While embodiments of this disclosure have been described above, it goes without saying that this disclosure is not limited to the embodiments described above and can take various forms.

[0058] (2a) In the operation management system of the above embodiment, the server does not necessarily have to have an operating rate recording unit and an operation evaluation unit. Also, the report creation unit does not necessarily have to embed the user test results obtained by the alcohol checker into the usage report data.

[0059] (2b) The functions of one component in the above embodiment may be distributed among multiple components, or the functions of multiple components may be integrated into one component. Also, some parts of the configuration of the above embodiment may be omitted. Also, at least some parts of the configuration of the above embodiment may be added to, substituted for, or otherwise used in the configuration of other above embodiments. Any aspect of the technical concept specified by the wording of the claims is an embodiment of the present disclosure. [Explanation of Symbols]

[0060] 1...Driving management system, 10...In-vehicle equipment, 11...Acquisition unit, 12...Recording unit, 30...Alcohol checker, 50...Server, 51...Communications department, 52...Report creation department 53...Operating rate recording unit, 54...Operation evaluation unit, 55...Notification unit, 70...Terminal device, 71...Receiver, 72...Display unit, 100...Portable terminal.

Claims

1. An in-vehicle device that is installed in a vehicle and configured to acquire the vehicle's driving conditions, A server capable of communicating with the in-vehicle equipment via a wireless communication line, A terminal device capable of communicating with the aforementioned server, Equipped with, The aforementioned in-vehicle equipment is An acquisition unit configured to recognize a user when the in-vehicle device is started, and which is configured to use the user recognized before the shutdown as the user after the restart if the time from the shutdown to the restart of the in-vehicle device is less than or equal to a predetermined threshold, The aforementioned server, A communication unit configured to receive the driving conditions and user information from the in-vehicle equipment, A report creation unit configured to create a vehicle usage report data based on the aforementioned driving conditions and user information, A utilization rate recording unit configured to record the daily utilization rate of the vehicle based on the aforementioned driving conditions, It has, The communication unit is configured to transmit the operating rate to the terminal device. The terminal device has a display unit configured to display the operating rate with emphasis according to the magnitude of the operating rate. Driving management system.

2. The operation management system according to claim 1, The acquisition unit is configured to recognize the user by reading the user's mobile device, driver's license, or camera. Driving management system.

3. An operation management system according to claim 1 or claim 2, The acquisition unit is configured to re-recognize the user if the time from the shutdown to the restart of the in-vehicle equipment exceeds a predetermined threshold. Driving management system.

4. An operation management system according to claim 1 or claim 2, A driving management system in which the usage report data includes at least one boarding time, at least one alighting time, at least one boarding location, at least one alighting location, driving time, and driving distance for the vehicle.

5. An operation management system according to claim 1 or claim 2, The server has a driving evaluation unit configured to evaluate the degree of safe driving in the vehicle based on the driving conditions, and is a driving management system.

6. An operation management system according to claim 1 or claim 2, The vehicle is further equipped with an alcohol checker for checking the alcohol content of its users. The aforementioned report creation unit is configured to embed the user's test results obtained by the alcohol checker into the usage report data, thereby providing an operational management system.

7. An operation management system according to claim 1 or claim 2, The aforementioned server has a notification unit configured to notify the terminal device of the approaching inspection date of the vehicle, in an operation management system.

Images