Event recording device, on-vehicle unit, operation management device, event recording program, and operation management program

Abstract

To reduce work of a manager by outputting information, which is recorded as a specific event, as a daily report.SOLUTION: An on-vehicle unit 10 comprises a detection section 13, which detects occurrence and end of an unexpected even that may disturb an operation of a vehicle 1, and a recording section 17 which records a specific event including the time of occurrence of the event and the time of end of the event. The on-vehicle unit 10 also comprises a speed acquisition section 14 which acquires time-series data of a speed of the vehicle, and the detection section 13 detects the occurrence and end of the event and the type of the event based on the time-series data of the speed.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an event recording device, an in-vehicle device, a traffic management device, an event recording program, and a traffic management program. [Background technology]

[0002] There is a demand for improvements in working conditions, including working hours, for truck drivers. Truck transport companies manage the labor of their drivers based on work records such as daily reports. This labor management utilizes the operation records stored in on-board devices installed in trucks (see, for example, Patent Documents 1 and 2).

[0003] In light of the recent social problem of excessive driver workloads, new standards regarding working conditions have been established. For example, the newly applied "Standards for the Improvement of Working Hours, etc. of Automobile Drivers" (Improvement Standards Notification) newly stipulates on-duty time, rest time, continuous driving time, etc. within a specified period. On the other hand, this Improvement Standards Notification also stipulates that, under certain conditions, the time spent responding to unforeseen events can be excluded from the application of the regulations regarding on-duty time, driving time, and continuous driving time. In other words, if a driver encounters an unforeseen event such as an accident, breakdown, or disaster, causing a certain delay, the time spent responding to the event can be excluded from the actual driving time. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-061482 [Patent Document 2] Japanese Patent Application Publication No. 2023-069859 Summary of the Invention [Problem to be solved by the invention]

[0005] The above-mentioned unforeseen events are events that hinder vehicle operation, including the vehicle being caught in a traffic jam. Currently, the onboard device (digital tachograph) installed in the vehicle calculates and records driving time, continuous driving time, and restrained time based on the vehicle's speed information. Some onboard devices do not count continuous driving time if the vehicle's speed remains at 0 km / h for, for example, 10 minutes or more. However, because the vehicle does not completely stop when a traffic jam occurs, the onboard device continuously counts each time the vehicle travels at a low speed, making it difficult to automatically include the time it takes for the vehicle to escape the traffic jam in the daily report. As a result, if information about responding to an unforeseen event, as stipulated in the Improvement Standards Notification, is to be included in the daily report, manual entry is required, which is inefficient and may increase the workload.

[0006] The present invention provides an event recording device, an in-vehicle device, an operation management device, an event recording program, and an operation management program that can reduce the workload of an administrator and facilitate management. [Means for solving the problem]

[0007] In order to achieve the above object, an event recording device according to the present invention has the following features. a detection unit that detects the occurrence and end of an unexpected event that interferes with the operation of the vehicle; a recording unit that records a specific event including the occurrence time of the event and the end time of the event, Event recorder.

[0008] In order to achieve the above-mentioned object, the vehicle-mounted device according to the present invention has the following features. An in-vehicle device equipped with the event recording device.

[0009] In order to achieve the above-mentioned object, the operation management device according to the present invention has the following features. an operation information acquisition unit that acquires operation information including the specific event from the in-vehicle device; a daily report output unit that outputs a daily report including at least the specific event based on the operation information. Operation control device.

[0010] In order to achieve the above object, an event recording program according to the present invention has the following features. Detecting the occurrence and termination of an unexpected event that interferes with the operation of the vehicle; recording a specific event including a time when the event occurred and a time when the event ended; An event recording program that causes a computer to execute

[0011] In order to achieve the above-mentioned object, the operation control program according to the present invention has the following features. acquiring operation information including the specific event generated as a result of the event recording program causing a computer to execute each step; outputting a daily report including at least the specific event based on the operation information; An operation management program that causes a computer to execute the above. [Effects of the Invention]

[0012] According to the present invention, it is possible to reduce the workload of the administrator and to facilitate management.

[0013] The present invention has been briefly described above. The details of the present invention will become clearer by reading the following detailed description of the invention (hereinafter referred to as "embodiments") with reference to the accompanying drawings. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a system configuration diagram showing an example of the configuration of an operation control system according to one embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of an in-vehicle device according to one embodiment of the present invention. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of an office PC according to an embodiment of the present invention. [Figure 4] FIG. 4 is a flowchart (part 1) showing a procedure for recording a specific event executed by the vehicle-mounted device. [Figure 5] FIG. 5 is a flowchart (part 2) showing the procedure for recording a specific event executed by the vehicle-mounted device. [Figure 6] FIG. 6 is a flowchart showing the procedure of operation management executed by the office PC. [Figure 7] Figure 7 is an example of a map shown in a daily report. DETAILED DESCRIPTION OF THE INVENTION

[0015] Specific embodiments of the present invention will be described below with reference to the accompanying drawings.

[0016] 1, a traffic management system 100 according to an embodiment is a system operated by a service provider whose clients are businesses that manage the operation of vehicles 1, such as trucks and taxis. The traffic management system 100 includes an on-board device 10 mounted on the vehicle 1, a server 20 that can communicate with the on-board device 10, and an office PC (personal computer) 40 that is a communication terminal that can communicate with the on-board device 10 and the server 20.

[0017] The in-vehicle device 10 is mounted on a vehicle 1, such as a truck, and records operational information such as the time of entry and exit of the vehicle 1, mileage, driving time, driving speed, speed limit, engine speed limit, sudden start, sudden acceleration, and sudden deceleration. One day's worth of operational information is used, for example, to create a daily report. The in-vehicle device 10 can be wirelessly connected to a network N, such as the Internet, via a base station B, for example, via wireless communication. The in-vehicle device 10 can be operated not only via a communication system that provides operational information about the vehicle 1 to an office PC 40 via wireless communication, but also via a card system that provides operational information about the vehicle 1 to the office PC 40 via a recording medium such as a memory card. The in-vehicle device 10 is sometimes called a "digital tachometer" or "digital tachograph." As will be described later, the in-vehicle device 10 also functions as an event recording device that records the occurrence of unexpected events (specific events) that interfere with the operation of the vehicle 1.

[0018] The server 20 is a computer device that can communicate with the vehicle-mounted device 10 and the office PC 40 via the network N and exchanges operation information of the vehicle 1 with the vehicle-mounted device 10 and the office PC 40. The server 20 is installed, for example, by a service provider.

[0019] The office PC 40 is a communication terminal used by an administrator of a business operator such as a transportation company that operates the vehicle 1, and is capable of communicating with at least one of the vehicle-mounted device 10 and the server 20, or both in this embodiment, via the network N. The communication terminal is not limited to a fixed type, but may also be a portable device such as a tablet, smartphone, or mobile phone. As will be described later, the office PC 40 functions as a traffic management device that outputs daily reports. The office PC 40 may also function as an event recording device instead of the vehicle-mounted device 10.

[0020] 2 is a block diagram showing an example of the configuration of the vehicle-mounted device 10 according to the embodiment. The vehicle-mounted device 10 includes a control unit 11, a communication unit 12, a detection unit 13, a speed acquisition unit 14, a position acquisition unit 15, a traffic information acquisition unit 16, and a recording unit 17.

[0021] The control unit 11 is a processing unit (computer) that mainly controls the vehicle-mounted device 10. The control unit 11 reads a program stored in an internal memory (not shown) or a recording medium such as a memory card that can be inserted into or removed from the vehicle-mounted device 10, and causes each unit of the vehicle-mounted device 10 to execute predetermined processing. This program may be an event recording program for executing a procedure for recording a specific event, which will be described with reference to FIGS. 4 and 5.

[0022] The communication unit 12 functions as a transmitting unit that transmits operation information of the vehicle 1 to the server 20, the office PC 40, etc. via the network N, and also functions as a receiving unit that receives information from the server 20, the office PC 40, etc.

[0023] The detection unit 13 detects the occurrence and end of an unexpected event (hereinafter also referred to as a "specific event") that interferes with the operation of the vehicle 1. The detection unit 13 detects the occurrence and end of the specific event and the type of the specific event based on time-series data of the speed of the vehicle 1 acquired by the speed acquisition unit 14. As an example, the detection unit 13 detects the occurrence of the specific event when the speed of the vehicle 1 remains equal to or less than a first threshold for a first hour or more, and detects the end of the specific event when, after detecting the occurrence of the specific event, the speed remains equal to or greater than a second threshold for a second hour or more. The first threshold is, for example, 40 km / h, and the first time is, for example, 15 minutes. The detection unit 13 detects the occurrence of a traffic jam when the speed of the vehicle 1 remains equal to or less than 40 km / h for a second hour or more. The second threshold is, for example, 40 km / h, and the second time period is, for example, 5 minutes. The detection unit 13 detects that the congestion has been resolved when the speed of the vehicle 1 exceeds 40 km / h for 5 minutes or more after the occurrence of the congestion. The first threshold, the first time period, the second threshold value, and the second time period can be set by the user. The detection unit 13 may also detect a road closure, which is an example of a specific event, based on, for example, the vehicle 1 being stopped for a certain period of time or more.

[0024] The speed acquisition unit 14 acquires time-series data of the speed of the vehicle 1. The speed acquisition unit 14 acquires time-series data of the speed based on, for example, an input of a vehicle speed pulse signal output from the vehicle side. Note that the detection unit 13 and the speed acquisition unit 14 may be software realized by a program stored in an internal memory (not shown) of the control unit 11 or a recording medium.

[0025] The position acquisition unit 15 acquires position information (including latitude and longitude) of the vehicle 1 based on signals received from GPS satellites S. The acquired position information is linked to time information and recorded as part of operation information.

[0026] The traffic information acquisition unit 16 acquires traffic information related to the vehicle 1's travel route. The traffic information acquisition unit 16 acquires traffic information received by an ETC2.0 on-board unit (not shown) mounted on the vehicle 1 and connected to the on-board unit 10 via an interface. The ETC2.0 on-board unit performs road-to-vehicle wireless communication with, for example, a roadside device (not shown) on an expressway or toll road. Through this wireless communication, the ETC2.0 on-board unit acquires traffic information related to the vehicle 1's travel route from the roadside device. The traffic information includes congestion information, road closure information, and information on snow and ice on the road surface. The traffic information includes text information and image information. The ETC2.0 on-board unit also exchanges information necessary for toll settlement with the roadside device. The information exchanged with the roadside device includes information on toll gates the vehicle 1 has passed through. The traffic information acquisition unit 16 can acquire various information received by the ETC2.0 on-board unit from the roadside device, and can extract information such as the type (reason) of a specific event and the location where the specific event occurred from the text information.

[0027] The recording unit 17 records the collected operation information in an internal memory or a recording medium. When the detection unit 13 detects the occurrence and end of an unexpected event, the recording unit 17 records operation information including a specific event event, including the occurrence and end times of the event. The recording unit 17 also records time-series data (GPS data) of the position information of the vehicle 1 acquired by the position acquisition unit 15, and response information regarding a response to the specific event. The response information includes the elapsed time from the occurrence to the end of the specific event, the distance from the position of the vehicle 1 at the occurrence time (occurrence position) to the position of the vehicle 1 at the end time (end position), and time-series data of the position information from the occurrence position to the end position. Furthermore, the recording unit 17 records the traffic information acquired by the traffic information acquisition unit 16 in association with the specific event event.

[0028] 3 is a block diagram showing an example of the configuration of the office PC 40 according to the embodiment. The office PC 40 includes a control unit 41, a communication unit 42, an operation information acquisition unit 43, a calculation unit 44, and a daily report output unit 45.

[0029] The control unit 41 is a processing unit (computer) that mainly controls the office PC 40. The control unit 41 reads a program stored in an internal memory (not shown) and causes each unit of the office PC 40 to execute a predetermined process. This program may be a traffic management program for executing the traffic management procedure described in FIG. 6.

[0030] The communication unit 42 functions as a receiving unit that receives operation information of the vehicle 1 from the in-vehicle device 10 or the server 20 via the network N, and also functions as a transmitting unit that transmits information to the server 20, the office PC 40, etc. The office PC 40 is provided with a card interface (I / F), and the control unit 41 may read data from a recording medium removed from the in-vehicle device 10 via the card I / F, as will be described later.

[0031] The operation information acquisition unit 43 acquires operation information including specific events from the vehicle-mounted device 10. The operation information acquisition unit 43 may acquire the operation information directly from the vehicle-mounted device 10 or may acquire it via the server 20.

[0032] The calculation unit 44 calculates the response time for a specific event based on the occurrence and end times of the specific event. The calculation unit 44 calculates the response time using information extracted from traffic information included in the operation information. As an example, when the traffic information is congestion information, the calculation unit 44 extracts information such as the congestion section, congestion distance, cause of the congestion, and congestion occurrence time from the congestion information as text information. The calculation unit 44 compares this information with time-series data of the time from the occurrence to the end of the specific event and location information acquired from the in-vehicle device 10 to calculate the response time. Furthermore, when the operation information acquisition unit 43 acquires the cumulative operation time of the vehicle 1 as operation information, the calculation unit 44 calculates the time obtained by subtracting the response time from this cumulative operation time as the working time. The working time includes working hours, breaks, and other time spent by the employer.

[0033] The daily report output unit 45 outputs a daily report including a specific event based on the operation information. The daily report output unit 45 outputs a daily report including an indication that a specific event has been responded to, the reason such as traffic congestion due to a vehicle accident, the response time, and the response section. The response section is an example of the location where the specific event occurred, and includes the occurrence position and end position of the specific event. The daily report may be in the form of digital data or on paper media. The daily report output unit 45 may include a display device (display) that displays digital data, or may include a printer that can print on paper media.

[0034] 4 and 5 are flowcharts showing a procedure for recording a specific event executed by the on-board device 10, which is an example of an event recording device. When the control unit 11 of the on-board device 10 detects that the vehicle 1 has left the parking lot (step S1), it starts acquiring time-series data such as the speed, position, and acceleration of the vehicle 1. The acquired time-series data is recorded by the recording unit 17. The control unit 11 determines whether the vehicle 1 is traveling on an expressway, for example, based on toll gate information acquired by the traffic information acquisition unit 16 (step S2). If the vehicle 1 is traveling on an expressway (Yes in step S2), the traffic information acquisition unit 16 starts acquiring traffic information related to the vehicle 1's travel route via the ETC 2.0 on-board device (step S3). The traffic information acquisition unit 16 periodically acquires traffic information. The traffic information is recorded by the recording unit 17. The detection unit 13 determines whether the speed of the vehicle 1 has been below 40 km / h (first threshold) for 15 minutes (first time) or more, i.e., whether a traffic jam has occurred (step S4). The conditions used for determining whether a traffic jam has occurred are merely examples. The first threshold and the first time period are set values ​​stored in, for example, an internal memory or a recording medium and can be changed by the user. If the result of step S4 is Yes, the detection unit 13 detects the occurrence of a traffic jam and temporarily records the traffic jam event (specific phenomenon event) in the internal memory using the recording unit 17, with the start time (occurrence time) being 15 minutes before the time when the traffic jam was detected. A traffic jam is an example of an unexpected event that interferes with the operation of the vehicle 1. Upon detecting the occurrence of a traffic jam, the control unit 11 starts measuring corresponding information based on the time-series data of the speed and position acquired via the speed acquisition unit 14 and the position acquisition unit 15 (step S5). The corresponding information includes information such as the elapsed time from the occurrence time, the distance traveled by the vehicle 1 from the occurrence time, and the current position of the vehicle 1. The detection unit 13 determines whether the speed of the vehicle 1 has exceeded 40 km / h (second threshold) for five minutes or more (second time period), i.e., whether the traffic jam has been resolved (step S6). The conditions used for determining whether the congestion has been resolved are merely examples, and the second threshold value and the second time period are set values ​​stored in, for example, an internal memory or a recording medium, and can be changed by the user. If the result of step S6 is Yes, the detection unit 13 detects that the congestion has been resolved (ended), and the control unit 11 ends the measurement of the corresponding information (step S7).Furthermore, the detection unit 13 sets the end time of the congestion event as the time five minutes prior to the time when the congestion relief was detected, and temporarily records the congestion event in the internal memory by the recording unit 17. If the control unit 11 does not detect the congestion relief (No in step S6), the control unit 11 continues measuring the corresponding information.

[0035] If the vehicle is not traveling on an expressway (No in step S2), the control unit 11 waits until it detects that the vehicle is traveling on an expressway. If the occurrence of a traffic jam is not detected (No in step S4), the detection unit 13 continues to acquire time-series data such as speed.

[0036] When the measurement of the corresponding information is completed (step S7), the recording unit 17 temporarily records the operation information including the congestion event in the internal memory (step S8). The recording unit 17 temporarily records, in the internal memory, time series data of the position information of the vehicle 1 from the occurrence time of the congestion event to the end time, time series data of the time required from the occurrence time of the congestion event to the end time, the travel distance, the speed, and the traffic information, in association with the congestion event. The various information recorded in step S8 may be referred to as congestion event information.

[0037] If the vehicle-mounted device 10 is operated in a manner that communicates with an external device such as the office PC 40 via the network N (Yes in step S9), the communication unit 12 transmits data including the recorded operation information to the office PC 40 (step S10). The operation information includes congestion event information. The communication unit 12 may transmit the data to the server 20, and the server 20 may transmit the data to the office PC 40.

[0038] On the other hand, if the operation mode of the vehicle-mounted device 10 is not the communication mode but the card mode (No in step S9), the recording unit 17 records data including the operation information on a recording medium such as a memory card (step S12).

[0039] When the data transmission is completed (Yes in step S11) or when the recording to the memory card is completed (Yes in step S13), the control unit 11 discards the data temporarily recorded in the internal memory (step S14).

[0040] 6 is a flowchart showing the procedure of operation management executed by the office PC 40, which is an example of an operation management device. When the entry of the vehicle 1 is detected (step S21), if the operation mode of the in-vehicle device 10 employs a communication method (Yes in step S22), the communication unit 42 of the office PC 40 receives data including operation information from the in-vehicle device 10, and the control unit 41 starts the daily report recording process (step S24). If the operation mode of the in-vehicle device 10 does not employ a communication method (No in step S22), the control unit 41 reads the data including operation information from the memory card removed from the in-vehicle device 10 by the driver (step S23), and starts the daily report recording process (step S24).

[0041] When the operation information acquisition unit 43 acquires operation information and the acquired operation information does not include a congestion event (specific event) (No in step S25), the daily report output unit 45 outputs a normal daily report that does not include information about the specific event (step S30). On the other hand, when a congestion event is present in the operation information (Yes in step S25), the calculation unit 44 extracts corresponding congestion information by comparing the congestion event information with congestion information included in the traffic information (step S26). The congestion event information includes the start and end times of the congestion event, the position of the vehicle 1 at the start time of the congestion event (occurrence position), and the position of the vehicle 1 at the end time of the congestion event (end position). The congestion information included in the traffic information includes information about the congestion section, congestion distance, cause of the congestion, and the time the congestion occurred. Although the congestion information included in the traffic information may also include information about congestion other than the congestion in which the vehicle 1 is involved, the calculation unit 44 extracts congestion information related to the congestion in which the vehicle 1 is actually involved by comparing the congestion event information with the congestion event information. The calculation unit 44 extracts information necessary for calculating the response time from the congestion information extracted in step S26 (step S27). The necessary information includes the congested section, the congestion distance, the cause of the congestion, and the time of occurrence. The calculation unit 44 calculates the response time from the extracted information (step S28). The response time is the time required in addition to normal operation due to the occurrence of congestion. The response time is calculated by subtracting the time required for vehicle 1 to travel from the point where it is caught in the congestion to the point where it has escaped from the congestion. The former is calculated by subtracting the end time of the congestion event from the start time of the congestion event, and the latter is calculated by dividing the congestion section by the normal speed. The normal speed is set, for example, by the user and stored in the internal memory.

[0042] The calculation unit 44 refers to the response time calculated in step S28 and calculates the driving time, continuous driving time, and commitment time by subtracting the response time from the driving time, continuous driving time, and cumulative driving time of the vehicle 1 included in the operation information (step S29). The calculation unit 44 calculates the commitment time as the time obtained by subtracting the driver's response time from the cumulative driving time for a predetermined period (one day). The daily report output unit 45 outputs a daily report that includes at least congestion events (step S30). The daily report includes the driver's response time. The daily report includes start position information and end position information.

[0043] As described above, according to the vehicle-mounted device 10 of this embodiment, when a specific event that interferes with the operation of the vehicle 1 occurs, such as being caught in traffic, a specific event including the occurrence time and end time of the specific event can be recorded (step S8). For example, when the vehicle is caught in traffic, a specific event including the time the vehicle became caught in traffic and the time the vehicle escaped from the traffic jam can be automatically recorded. Therefore, the information recorded by the vehicle-mounted device 10 as a specific event occurrence can be output as a daily report (step S30). Therefore, the occurrence of an unexpected event can be output without the manager having to manually enter it. This reduces the workload of the manager and prevents human error due to manual input, making management easier.

[0044] In particular, the detection unit 13 of the vehicle-mounted device 10 detects the occurrence and end of a specific event and that the type of the specific event is traffic congestion based on the time-series data of the speed of the vehicle 1 (steps S4, S6). Therefore, based on the time-series data of the speed of the vehicle 1, it is possible to detect the occurrence of an unexpected event, such as being caught in traffic congestion.

[0045] The vehicle-mounted device 10 is equipped with a position acquisition unit 15 that acquires time-series data on the position of the vehicle 1, and the recording unit 17 can record, in association with a congestion event, occurrence position information, which is the position information of the vehicle 1 at the time when the vehicle 1 was caught in a congestion, and end position information, which is the position information of the vehicle 1 at the time when the vehicle 1 escaped from the congestion. This allows the location information to be recorded in addition to the occurrence and end of the congestion event, thereby making the congestion event information more comprehensive.

[0046] The vehicle-mounted device 10 includes a traffic information acquisition unit 16 that acquires traffic information related to the route of the vehicle 1, and a recording unit 17 that records this traffic information in association with congestion events, so that the traffic information can be used when outputting a daily report, etc. Therefore, information on the cause of congestion, etc. can be included in the daily report. The vehicle-mounted device 10 is mounted on the vehicle 1, and can easily acquire specific events.

[0047] Furthermore, according to the office PC 40 of this embodiment, the daily report output by the daily report output unit 45 includes specific events (steps S25 to S30), so a daily report indicating the occurrence and completion of specific events can be output without the manager having to manually enter the information. This reduces the workload of the manager and prevents human errors due to manual input, making management easier.

[0048] The office PC 40 is equipped with a calculation unit 44 that calculates the response time to a congestion event based on the occurrence time and end time of the congestion event, and the daily report output unit 45 outputs a daily report including this response time, making it easy to comply with the standard of excluding response time to unforeseen events from commitment time, etc.

[0049] In the office PC 40, the operation information acquisition unit 43 acquires traffic information related to the travel route of the vehicle 1 linked to the congestion event (steps S23 and S24), and the calculation unit 44 calculates the response time using information extracted from the traffic information (step S28). Therefore, since the response time can be calculated based on traffic information acquired from outside, a daily report including a more accurate response time can be output.

[0050] In the office PC 40, the calculation unit 44 calculates the commitment time, and the operation information acquisition unit 43 acquires the cumulative operation time of the vehicle 1 as operation information, and the calculation unit 44 can calculate the time obtained by subtracting the response time from the cumulative operation time as the commitment time. The daily report output unit 45 can output a daily report including the commitment time. As a result, the daily report includes the commitment time excluding the response time, making it easier to comply with standards excluding the response time for unforeseen events.

[0051] Furthermore, the daily report output unit 45 may output a daily report including a map showing the location of the congestion event (the route of the vehicle 1 from the occurrence location to the end location, the corresponding section) based on the location information. As a result, the daily report includes a map showing the location of the congestion event, making the information in the daily report more comprehensive. FIG. 7 is an example of a map shown in the daily report, on which the location of the congestion event where the vehicle 1 is located is indicated by a thick solid line. For example, by displaying the following information in the daily report together with this map, the manager can easily understand the situation. "Response to unexpected events" Yes (1 item) "Reason": Traffic jam due to vehicle accident "Response time" 0:36:30.0 "Running time": 9:50:47.0 -0:36:30.0 = 9:14:17.0 "Continuous running time": 4:10:55.0 - 0:36:30.0 = 3:34:25.0 "Detention time" 12:40:50.0 -0:36:30.0 = 12:04:20.0 "Corresponding section" Point A1-Point A2

[0052] The present invention is not limited to the above-described embodiments, and can be appropriately modified, improved, etc. In addition, the material, shape, dimensions, numerical values, form, number, location, etc. of each component in the above-described embodiments are arbitrary and not limited as long as they can achieve the present invention.

[0053] In the above embodiment, the vehicle-mounted device 10 records specific events, but the office PC 40 may function as an event recording device that records specific events. In this case, the office PC 40 acquires operation information including time-series data such as the speed and location information of the vehicle 1 from the vehicle-mounted device 10 via the network N, detects the occurrence and end of specific events, and records the specific events.

[0054] Furthermore, in the above embodiment, an example was given in which the unexpected event was a traffic jam, but the unexpected event may be any event that hinders vehicle operation, such as a road closure or traffic restrictions due to snow or ice on the road surface.

[0055] Here, the features of the embodiments of the event recording device, the operation management device, the in-vehicle device, the event recording program, and the operation management program according to the present invention will be briefly summarized and listed below in [1] to

[13] .

[0056] [1] A detection unit (13) that detects the occurrence and termination of an unexpected event that interferes with the operation of the vehicle (1); a recording unit (17) for recording a specific event including the occurrence time of the event and the end time of the event; Event recording device (vehicle-mounted device 10 or office PC 40).

[0057] According to the event recording device configured as described above in [1], when a specific event that impedes vehicle operation, such as being caught in traffic, occurs, a specific event including the time the specific event occurred and the time it ended can be recorded. For example, when a vehicle is caught in traffic, a specific event including the time the vehicle became caught in traffic and the time the vehicle escaped the traffic jam can be automatically recorded. Therefore, the information recorded as the specific event occurrence can be output as a daily report, so that the occurrence of unexpected events can be output without the need for a manager to manually enter the information. This reduces the workload of the manager and prevents human error due to manual input, making management easier.

[0058] [2] A speed acquisition unit (14) for acquiring time series data of the speed of the vehicle, The event recording device according to [1], wherein the detection unit (13) detects the occurrence and end of the event and the type of the event based on the time series data of the speed.

[0059] According to the event recording device configured as described above in [2], it is possible to detect the occurrence of an unexpected event, such as when the vehicle is caught in a traffic jam, based on the time-series data of the vehicle speed.

[0060] [3] The detection unit (13) detects the occurrence of the event when the state in which the speed is equal to or less than a first threshold continues for a first time or more, and after detecting the occurrence of the event, detects the end of the event when the state in which the speed is equal to or more than a second threshold continues for a second time or more. The event recording device according to [2] above.

[0061] The event recording device configured as described above in [3] can detect and record unexpected events such as being caught in traffic jams.

[0062] [4] A position acquisition unit that acquires time-series data of the position of the vehicle, the recording unit records occurrence location information, which is location information of the vehicle at the time when the event occurred, and end location information, which is location information of the vehicle at the time when the event ended, in association with the specific event. An event recording device according to any one of [1] to [3].

[0063] According to the event recording device configured as described above in [4], in addition to the information that an unexpected event has occurred, location information is also recorded, so that the information on the specific event becomes more comprehensive.

[0064] [5] A traffic information acquisition unit (16) for acquiring traffic information related to the travel route of the vehicle, The recording unit (17) records the traffic information in association with the specific event. An event recording device according to any one of [1] to [4].

[0065] According to the event recording device configured as described above in [5], traffic information acquired from linked devices, servers, etc. is recorded in association with specific incident events, so that various information contained in the traffic information can be used when outputting daily reports, etc. For example, if the traffic information includes information on the type (cause) and location of a specific incident, such information can be included in the daily report.

[0066] [6] An in-vehicle device equipped with the event recording device described in any one of [1] to [5] above.

[0067] According to the vehicle-mounted device having the configuration [6] above, the event recording device mounted on the vehicle records the specific event, so that information about the specific event can be easily obtained.

[0068] [7] An operation information acquisition unit (43) that acquires operation information including the specific event from the on-board device described in [6] above; a daily report output unit (45) that outputs a daily report including at least the specific event based on the operation information. Operation control device (office PC40).

[0069] According to the operation management device configured as described above in [7], the daily report includes specific events, so the manager can output a daily report indicating the occurrence and completion of specific events without having to manually enter them. This reduces the manager's workload and prevents human error due to manual input, making management easier.

[0070] [8] A calculation unit (44) for calculating a response time to the specific event based on the occurrence time and end time of the event, The daily report output unit (45) outputs the daily report including the response time. [7] The operation management device described in [7].

[0071] According to the configuration of [8] above, since the daily report includes the response time, it becomes easy to comply with the criteria excluding the response time for unforeseen events.

[0072] [9] The operation information acquisition unit (43) acquires traffic information related to the specific event and related to the travel route of the vehicle, the calculation unit (44) calculates the response time using information extracted from the traffic information. [8] The operation management device described in [8].

[0073] According to the traffic management device described above in [9], the response time can be calculated based on traffic information obtained from outside, so that a daily report including a more accurate response time can be output.

[0074]

[10] The calculation unit (44) calculates the restraint time, the operation information acquisition unit acquires, as the operation information, a cumulative operation time of the vehicle; the calculation unit calculates the time obtained by subtracting the response time from the cumulative operation time as the restraint time, the daily report output unit outputs the daily report including the on-duty time. The traffic management device according to [8] or [9] above.

[0075] According to the operation management device having the configuration described above in

[10] , the daily report includes the on-duty time excluding the response time, so that it becomes easy to comply with the standard excluding the response time for unforeseen events.

[0076]

[11] An operation information acquisition unit that acquires operation information including the specific event from an in-vehicle device equipped with the event recording device described in [4] above; a daily report output unit that outputs a daily report including the start position information and the end position information based on the operation information, the daily report output unit outputs the daily report including a map showing the location where the event occurred based on the occurrence location information, the end location information, and the time-series data of the location. Operation control device.

[0077] According to the traffic management device having the configuration described above in

[11] , the daily report includes a map showing the location of an unexpected event, so that the information in the daily report becomes more comprehensive.

[0078]

[12] Detecting the occurrence and termination of an unexpected event that interferes with the operation of the vehicle; recording a specific event including a time when the event occurred and a time when the event ended; An event recording program that causes a computer to execute

[0079] According to the event recording program configured as described above in

[12] , when a specific event that hinders vehicle operation, such as being caught in traffic, occurs, a specific event including the time the specific event occurred and the time it ended can be recorded. For example, when a vehicle is caught in traffic, a specific event including the time the vehicle became caught in traffic and the time the vehicle escaped from the traffic jam can be automatically recorded. Therefore, the information recorded as a specific event occurrence can be output as a daily report, so that the occurrence of unexpected events can be output without the administrator having to manually enter the information. This reduces the administrator's workload and prevents human error due to manual input, making management easier.

[0080]

[13] A step of acquiring operation information including the specific event generated as a result of the event recording program described in

[12] above causing a computer to execute each step; outputting a daily report including at least the specific event based on the operation information; An operation management program that causes a computer to execute the above.

[0081] According to the operation management program configured as described above in

[13] , the daily report includes specific events, and the information recorded as specific event occurrences can be output as a daily report, so the occurrence of unexpected events can be output without the manager having to enter it manually. This reduces the workload of the manager and prevents human error due to manual input, making management easier. [Explanation of symbols]

[0082] 1 vehicle 10. In-vehicle device (event recording device) 11 Control section 12 Communications Department 13 Detection unit 14 Speed ​​acquisition section 15 Position acquisition part 16 Traffic information acquisition department 17 Recording Section 20 servers 40 Office PC (event recording device, operation management device) 41 Control Unit 42 Communications Department 43 Operation information acquisition department 44 Calculation section 45 Daily report output section 100 Traffic Management System B base station N Network S GPS satellite

Claims

1. a detection unit that detects the occurrence and end of an unexpected event that interferes with the operation of the vehicle; a recording unit that records a specific event including the occurrence time of the event and the end time of the event, Event recorder.

2. a speed acquisition unit that acquires time series data of the speed of the vehicle; The event recording device according to claim 1 , wherein the detection unit detects the occurrence and end of the event and the type of the event based on the time-series data of the speed.

3. 3. The event recording device of claim 2, wherein the detection unit detects the occurrence of the event when the speed remains below a first threshold for a first period of time or more, and detects the end of the event when, after detecting the occurrence of the event, the speed remains above a second threshold for a second period of time or more.

4. a position acquisition unit that acquires time-series data of the position of the vehicle; the recording unit records occurrence location information, which is location information of the vehicle at the time when the event occurred, and end location information, which is location information of the vehicle at the time when the event ended, in association with the specific event. The event recording device according to claim 1 .

5. a traffic information acquisition unit that acquires traffic information related to a travel route of the vehicle; The recording unit records the traffic information in association with the specific event. The event recording device according to claim 1 .

6. An in-vehicle device comprising the event recording device according to any one of claims 1 to 5.

7. an operation information acquisition unit that acquires operation information including the specific event from the vehicle-mounted device according to claim 6; a daily report output unit that outputs a daily report including at least the specific event based on the operation information. Operation control device.

8. a calculation unit that calculates a response time to the specific event based on an occurrence time and an end time of the event; The daily report output unit outputs the daily report including the response time. The operation management device according to claim 7.

9. the operation information acquisition unit acquires traffic information related to a travel route of the vehicle, the traffic information being linked to the specific event; the calculation unit calculates the response time using information extracted from the traffic information. The operation management device according to claim 8.

10. the operation information acquisition unit acquires, as the operation information, a cumulative operation time of the vehicle; The calculation unit calculates a time obtained by subtracting the response time from the cumulative operation time as a restraint time, the daily report output unit outputs the daily report including the on-duty time. The operation management device according to claim 9.

11. an operation information acquisition unit that acquires operation information including the specific event from an in-vehicle device that includes the event recording device according to claim 4; a daily report output unit that outputs a daily report including the start position information and the end position information based on the operation information, the daily report output unit outputs the daily report including a map showing the location where the event occurred based on the occurrence location information, the end location information, and the time-series data of the location. Operation control device.

12. Detecting the occurrence and termination of an unexpected event that interferes with the operation of the vehicle; recording a specific event including a time when the event occurred and a time when the event ended; An event recording program that causes a computer to execute

13. acquiring operation information including the specific event generated as a result of causing a computer to execute each step of the event recording program according to claim 12; outputting a daily report including at least the specific event based on the operation information; An operation management program that causes a computer to execute the above.

Images