Vehicle operation management system

LAP443AUndetermined Publication Date: 2022-02-04MATSUO ASSOC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
LAP443
Authority / Receiving Office
LA · LA
Patent Type
Applications
Current Assignee / Owner
Priority Date
2014-04-11
Filing Date
2015-04-09
Publication Date
2022-02-04

AI Technical Summary

Technical Problem

Current digital tachograph systems are expensive and inflexible, making it difficult for small and medium-sized transportation companies to adopt high-performance systems, while low-cost options lack functionality and require frequent device replacements due to regulatory changes.

Method used

A vehicle operation management system utilizing a smartphone or tablet PC as the on-board tachograph device, connected via a packet communication system to a management server, which processes and stores vehicle data, allowing for easy expansion and updates without the need for dedicated hardware replacements.

Benefits of technology

This solution significantly reduces the cost and complexity of implementing and maintaining digital tachograph systems, enabling more companies to adopt digital tachograph technology and facilitating easier adaptation to changing regulations and industry needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

[Problem] To provide a digital tachograph system which is inexpensive and has a system configuration easy to change and extend. [Solution] A vehicle-mounted tachograph is configured from a speed data acquisition unit (5) which is connected to a sensor (8) provided in a drive system of a vehicle, and a general-purpose terminal (4) which is a smartphone or other general-purpose portable computer capable of transmitting and receiving speed data to and from the speed data acquisition unit (5) via a general-purpose interface cable or short-distance radio communication, and the speed data at each point in time of an operation is transmitted to a management server (1) via the general-purpose terminal (4) in each transmission cycle, and recorded on a performance data file (26) stored in a storage unit (2). The contents of the performance data file (26) including three-element data are browsed on a management terminal (3) by access via the Internet (6). The general-purpose terminal (4) is removably held by a holder (7) so as not to fall during traveling.
Need to check novelty before this filing date? Find Prior Art

Description

The present invention relates to a vehicle operation management system including a digital tachograph. A tachograph is a type of vehicle-mounted driving recorder that graphs changes in driving speed and other parameters during operation, allowing for an understanding of the vehicle's operational status. Of the data recorded by a tachograph, driving time or time, distance traveled, and speed (instantaneous speed) are called the three basic elements. Recently, digital tachographs (hereinafter referred to as "digital tachographs"), which record each element as digital information, have become common. Hereafter, driving time or time, distance traveled, and speed (instantaneous speed) will be referred to as the three elements of a digital tachograph or simply the three elements. Such tachographs are ideally suited for management (safety management, labor management) to prevent unsafe driving practices such as speeding and excessively long driving hours. They can also be used to reduce fuel consumption by minimizing unnecessary acceleration and engine revving, leading to cost savings and demonstrating that a company is environmentally conscious. For these reasons, vehicle operation management systems using tachographs, especially digital tachographs, are sold by various companies and are used by major transportation companies and taxi companies. The Ministry of Land, Infrastructure, Transport and Tourism also highly values ​​the usefulness of vehicle operation management systems using digital tachographs and has indicated a policy to further promote their widespread adoption by expanding the scope of mandatory tachograph installation to include commercial freight vehicles with a gross vehicle weight of 7 to 8 tons, in order to implement even more focused safety measures from the perspective of reducing traffic accidents. Vehicle operation management systems using digital tachographs (hereinafter referred to as "digital tachograph systems") are becoming more sophisticated, including network compatibility. Specifically, the digital tachographs installed in vehicles (hereinafter referred to as "digital tachograph onboard units") are designed to be network-compatible, such as the internet. Digital tachograph system vendors provide various operation management software on servers set up on the network and offer vehicle operation management services using this software to purchasers of digital tachographs (such as transportation companies). As part of the advancement in functionality, many digital tachograph systems now include a drive recorder (dashcam) in addition to the digital tachograph onboard unit. In vehicles equipped with a dashcam, in addition to the three elements of digital tachograph data, forward-facing image data of the vehicle at the time the data was taken can be obtained, which is useful for confirming the situation in the event of an accident. While these high-performance digital tachograph systems are highly beneficial from the perspectives of safety management and labor management, they have the drawback of high equipment prices and maintenance costs (software usage fees, etc.). On the other hand, in contrast to these high-performance systems, low-priced digital tachographs with limited functionality are also available. These types of digital tachographs are instruments limited to collecting data for the three elements of digital tachography, and data is acquired via media such as memory cards. Thus, the digital tachograph industry is currently becoming polarized. Japanese Patent Publication No. 2013-141126 As mentioned above, digital tachograph systems are extremely beneficial from the perspectives of safety management, driver labor management, cost reduction, and environmental considerations in commercial vehicles, and are expected to become widely adopted in society, including through expanded mandatory use. However, in reality, the transportation industry includes not only large transportation companies but also numerous small and micro-transportation businesses. These small and micro-transportation businesses have a small scale of operations and limited financial strength, making it difficult for them to make large capital investments. For this reason, even though the benefits of high-performance digital tachograph systems are known, their introduction is difficult. The same situation applies to the taxi industry and privately owned logistics vehicles (so-called white-plated vehicles), where small and micro-taxi companies, including individual taxis, and small-scale private logistics companies find it difficult to introduce digital tachograph systems, which require significant investment and expense. According to one estimate, only about 600,000 commercial vehicles (7% of the total) have introduced digital tachograph systems. On the other hand, low-cost digital tachographs have very limited functionality, making it impossible to adequately analyze driving conditions through various data processing. Furthermore, they lack even the simplest functions, such as checking the closure of refrigerated compartment doors in refrigerated trucks, resulting in a significant lack of expandability. Furthermore, whether it's a high-performance or low-cost type, since it involves installing a dedicated digital tachograph unit as an in-vehicle device, any system configuration improvements or version upgrades require the entire in-vehicle device to be redesigned (i.e., developed). Users then need to purchase the newly developed in-vehicle device and replace the old one. In reality, digital tachograph systems need to be updated from time to time to adapt to various changes such as changes in the industry environment, changes in traffic conditions, and innovations in vehicle technology. However, with conventional systems that use a dedicated digital tachograph unit as an in-vehicle device, the entire in-vehicle device needs to be replaced, making it expensive. If a company installs a low-cost digital tachograph in each of its vehicles because it's cheap, and then, for example, a change in the law mandates the collection of new elements (data), the entire in-vehicle device will have to be replaced, which could end up being more expensive in the long run. The invention of this application has been made in consideration of the above circumstances surrounding the digital ecosystem. It is an inexpensive digital ecosystem that can be introduced even by companies with weak business strength, while also providing a digital ecosystem that is easy to change and expand the system configuration, aiming to contribute to the further spread of the digital ecosystem. To solve the above problems, the invention described in claim 1 of the present application is a vehicle operation management system comprising a tachograph onboard unit, a management server, and a storage unit, wherein the tachograph onboard unit consists of a terminal which is a smartphone or tablet PC and a signal collection unit which collects vehicle information and transmits it to the terminal which is a smartphone or tablet PC, the terminal which is a smartphone or tablet PC is able to access the management server via a packet communication system, the vehicle information collected by the signal collection unit includes a vehicle speed pulse signal, the terminal which is a smartphone or tablet PC transmits the vehicle information to the management server via a packet communication system, the management server has a program implemented which processes the vehicle speed pulse signal included in the vehicle information transmitted from the terminal which is a smartphone or tablet PC and stores the mileage, time and speed in the storage unit, and the stored mileage, time and speed are transmitted from the management server to an office terminal via the internet and can be viewed on the office terminal.Furthermore, in order to solve the above problems, the invention described in claim 2 is a vehicle operation management system that manages at least the speed, distance traveled and time of a vehicle, comprising a tachograph on-board unit mounted on a vehicle, a management server, and a storage unit, wherein the tachograph on-board unit consists of a speed data acquisition unit connected to a sensor provided in the vehicle's drive system and a general-purpose terminal connected to the speed data acquisition unit, the general-purpose terminal is a smartphone or a general-purpose portable computer other than a smartphone that can access the management server via a network, the general-purpose terminal has application software for on-board units installed which includes a data storage module that transmits speed data at each point in time of operation acquired by the speed data acquisition unit to the management server at each transmission cycle and stores it in the storage unit, the management server accepts access from general-purpose terminals via a network and access from management terminals, the management server has vehicle operation management server software implemented which includes a performance data registration program, and the storage unit stores performance data files, the performance data registration program is a program that records and registers speed data transmitted from the general-purpose terminal by the data storage module in the performance data file, and the vehicle operation management server software includes a three-element viewing program. The three-element viewing program is a program for displaying three-element data—distance traveled, travel time, and travel speed at each point in time during a day or a single operation—on a management terminal, based on speed data recorded in the performance data file. The vehicle is equipped with a terminal holder that holds a general-purpose terminal, and the terminal holder is designed to hold the general-purpose terminal detachably and to prevent it from falling during operation. The speed data acquisition unit and the general-purpose terminal are connected by a general-purpose interface cable, enabling the transmission and reception of speed data, or the transmission and reception of speed data is possible via short-range wireless communication.Furthermore, in order to solve the above problems, the invention described in claim 3 has the configuration of claim 2, wherein the speed data acquisition unit is provided with a general-purpose interface output terminal, the terminal holder is provided with a general-purpose interface connector terminal that contacts the general-purpose interface input terminal of the general-purpose terminal when attached, and the general-purpose interface connector terminal is connected to the general-purpose interface output terminal of the speed data acquisition unit by a general-purpose interface cable. Furthermore, in order to solve the above problems, the invention described in claim 4 has the configuration of claim 2, wherein the general-purpose terminal is provided with a short-range wireless receiver that receives information by short-range wireless communication using a general-purpose interface standard, and the speed data acquisition unit is provided with a short-range wireless transmitter that wirelessly transmits speed data using the same general-purpose interface standard as the short-range wireless receiver of the general-purpose terminal. Furthermore, in order to solve the above problems, the invention described in claim 5 has the configuration of claim 4, wherein the short-range wireless transmitter and the short-range wireless receiver are capable of transmitting and receiving without facing each other.Furthermore, in order to solve the above problems, the invention described in claim 6 has the following configuration in any of the configurations of claims 2 to 5, wherein the vehicle belongs to a transportation business company that operates vehicles as a business, and the transportation business company has multiple vehicles, each vehicle being equipped with the speed data acquisition unit and the general-purpose terminal, the storage unit stores a vehicle information file that records vehicle information including the vehicle ID of each vehicle belonging to the transportation business company, and a business information file that records information about the business, the vehicle operation management server software includes a business registration program, the in-vehicle device application software includes a business start module that is executed when the business is performed, the business start module is a program module that inputs information to identify the vehicle ID of the vehicle to be used in the business for the day or for a single business and sends it to the management server, and records the vehicle ID in the business information file by the business registration program, and the three-element viewing program is a program that, when the three-element data is displayed on the management terminal, obtains information about the vehicle that was the data source of the three-element data from the vehicle information file and displays it together. Furthermore, in order to solve the above problems, the invention described in claim 7 has a configuration in which, in any of the configurations of claims 2 to 6, the speed data acquired by the speed data acquisition unit is a vehicle speed pulse, and the actual data registration program implemented in the management server is a program that converts the vehicle speed pulse to calculate the driving speed.Furthermore, in order to solve the above problems, the invention described in claim 8 has the following configuration in any of the configurations of claims 2 to 7: the speed data acquisition unit has an input section that receives signals from other devices attached to the vehicle other than the speed sensor; the speed data acquisition unit outputs data based on signals received from other devices along with the speed data to the general-purpose terminal; the data storage module collects the data based on signals received from other devices and the speed data and transmits it to the management server; and the performance data registration program is a program that records data based on signals received from other devices together with the speed data in a performance data file.Furthermore, in order to solve the above problems, the invention described in claim 9 is a vehicle operation management system for managing the speed of a vehicle, comprising a tachograph on-board unit mounted on a vehicle, a management server, and a storage unit, wherein the tachograph on-board unit consists of a speed data acquisition unit connected to a sensor provided in the vehicle's drive system and a general-purpose terminal connected to the speed data acquisition unit, the general-purpose terminal is a smartphone or a general-purpose portable computer other than a smartphone that can access the management server via a network, the general-purpose terminal has application software for on-board units installed, which includes a data storage module that transmits speed data acquired by the speed data acquisition unit to the management server and stores it in the storage unit, the management server accepts access from general-purpose terminals via a network and access from management terminals, the management server has vehicle operation management server software implemented which includes a performance data registration program, and the storage unit stores performance data files, the performance data registration program is a program that records and registers speed data transmitted from the general-purpose terminal by the data storage module in the performance data file, and the vehicle operation management server software includes a viewing program. The viewing program is a program for displaying speed data recorded in the performance data file on a management terminal. The vehicle is equipped with a terminal holder that holds a general-purpose terminal, and the terminal holder is designed to hold the general-purpose terminal in a detachable manner and to prevent the general-purpose terminal from falling off while driving. The speed data acquisition unit and the general-purpose terminal are connected by a general-purpose interface cable, enabling the transmission and reception of speed data, or the transmission and reception of speed data is enabled by short-range wireless communication. As explained below, according to the invention of claim 1 of this application, the in-vehicle device consists of a terminal which is a smartphone or tablet PC and a speed data acquisition unit, and the main functions such as transmitting speed data to a management server are handled by the smartphone or tablet PC, so the cost of introducing the system can be made significantly cheaper than conventional methods. Furthermore, according to the invention of claim 2 or 9, the in-vehicle device consists of a speed data acquisition unit and a general-purpose terminal, and the main functions such as transmitting speed data to a management server are handled by the general-purpose terminal, and the general-purpose terminal is a smartphone or another general-purpose portable computer, so the cost of introducing the system can be made significantly cheaper than conventional methods. Furthermore, according to the invention described in claim 3, in addition to the above effects, the general-purpose terminal is held in the vehicle by a terminal holder so as not to fall during driving, and this terminal holder has a general-purpose interface connector terminal that contacts the general-purpose interface input terminal of the general-purpose terminal when attached, so by attaching a general-purpose interface cable to the general-purpose interface output terminal of the terminal holder in advance and connecting it to the speed data acquisition unit, speed data can be acquired into the general-purpose terminal simply by attaching it to the terminal holder. For this reason it is extremely simple. Furthermore, according to the invention described in claim 4, in addition to the above effects, the exposed cable does not detract from the appearance, and the interior of the vehicle does not become cluttered. Also, even if a dedicated terminal holder is not commercially available for the general-purpose terminal, there is no need to develop or purchase a new dedicated one, which has the advantage of reducing development costs and system costs. Furthermore, according to the invention described in claim 5, in addition to the above effects, the short-range wireless transmission unit and the short-range wireless reception unit can transmit and receive data without facing each other, making it particularly suitable for vehicle operation management systems in which both the speed data acquisition unit and the general-purpose terminal are often mounted on the dashboard. Furthermore, according to the invention described in claim 6, in addition to the above effects, it has the significance of enabling detailed management according to the characteristics of the vehicle. Furthermore, according to the invention described in claim 7, in addition to the above effects, the load on the general-purpose terminal is low, so there is no problem of slow speed data transfer.Furthermore, according to the invention described in claim 8, in addition to the above effects, data indicating the vehicle's status other than the three elements of the digital tachograph is acquired via the speed data acquisition unit, making it suitable for further enhancing and improving the functionality of vehicle operation management. In this case, if data is transmitted directly to a general-purpose terminal, there may be limitations on the number of general-purpose interface connector terminals on the general-purpose terminal, but the invention of claim 7 does not have this problem. This is a schematic diagram of the vehicle operation management system according to the first embodiment. This is a schematic diagram showing the installation of the in-vehicle device inside the vehicle. This is a perspective schematic diagram showing the terminal holder and the structure for holding a general-purpose terminal by the terminal holder. This is a diagram showing the schematic configuration of the speed data acquisition unit in the embodiment. This is a schematic diagram showing the structure of the in-vehicle device application. This is a schematic diagram showing an example of the main screen displayed by the main module of the in-vehicle device application. This is a flowchart showing the outline of the work start module. This is a schematic diagram showing an example of the structure of the vehicle information file. This is a schematic diagram showing an example of the vehicle selection screen. This is a flowchart showing the outline of the data storage module. This is a schematic diagram showing an example of the structure of the temporary file. This is a flowchart showing the outline of the data transmission sub. This is a diagram illustrating the structure of the work information file. This is a schematic diagram illustrating the structure of the actual data file. This is a schematic diagram showing an example of the initial screen displayed on the management terminal by the operation management application. This is a schematic diagram showing an example of the three-element viewing screen displayed on the management terminal. This is a schematic diagram showing an example of the diagnostic / work understanding screen displayed on the management terminal by the diagnostic / work understanding program. This is a schematic diagram showing an example of the eco evaluation screen displayed on the management terminal by the eco evaluation program. This is a schematic diagram showing an example of the safety management screen displayed on the management terminal by the safety management program. This is a schematic diagram of the main components of the vehicle operation management system according to the second embodiment. Next, embodiments for carrying out the present invention (hereinafter referred to as embodiments) will be described. Figure 1 is a schematic diagram of a vehicle operation management system according to the first embodiment. The vehicle operation management system shown in Figure 1 is a digital tachograph system and comprises a tachograph on-board unit (hereinafter simply referred to as the on-board unit) mounted on a vehicle, a management server 1, a storage unit 2, and a management terminal 3. A major feature of the vehicle operation management system of the embodiment is that the on-board unit is not a dedicated unit, but is configured to include a general-purpose terminal 4. That is, the on-board unit in the embodiment consists of a speed data acquisition unit 5 connected to a sensor 8 provided in the vehicle's drive system, and a general-purpose terminal 4 connected to the speed data acquisition unit 5. First, the general-purpose terminal 4 and speed data acquisition unit 5 that constitute the in-vehicle device will be described. The general-purpose terminal 4 is a smartphone or a general-purpose portable computer other than a smartphone, but for example, a tablet PC of about 10 inches is used. The general-purpose terminal 4 is capable of accessing the management server 1 via a network. In this embodiment, the network is assumed to be the internet 6. However, in a broad sense, the network may include a mobile phone line or wireless LAN for connecting to the internet 6 as needed. The general-purpose terminal 4 includes a mobile data communication interface, as is well known. Furthermore, whether data communication is via the internet 6 or via a mobile phone line or wireless LAN, data is transmitted in packet form, so the communication system interposed between the general-purpose terminal 4 and the management server 1 can be called a packet communication system. Figure 2 is a schematic diagram showing the installation of an in-vehicle device inside a vehicle. As shown in Figure 2, the general-purpose terminal 4 of the in-vehicle device is installed while being held in a terminal holder 7. The terminal holder 7 is fixed to the dashboard. Figure 3 is a schematic perspective view showing the structure of the terminal holder 7 holding the general-purpose terminal 4. The terminal holder 7 can take various structures, but as shown in Figure 3, in this example it is frame-shaped. The terminal holder 7 has a structure consisting of a base plate 71 fixed to the vehicle's dashboard, an arm 72 extending from the base plate 71, and frame parts 73 to 75 provided at the ends of the arm 72. The base plate 71 is a part that is firmly fixed to the dashboard by screws or the like. In this example, the frame parts 73 to 75 are U-shaped and have a structure that holds the general-purpose terminal 4 on three sides: left, right, and bottom. A small support column 78 with a built-in vertical rotation axis is provided at the end of the arm 72, and each frame part 73 to 75 is supported by the support column 78. Each frame section 73-75 has a groove formed therein that corresponds to the thickness of the general-purpose terminal 4. As shown in Figure 3, when holding the general-purpose terminal 4, the general-purpose terminal 4 is inserted into the terminal holder 7 from above and dropped into the grooves of each frame section 73-75. The spacing between the left and right frame sections 73 and 74 is slightly narrower than the width of the general-purpose terminal 4, and the parts of the arm 72 that connect to the left and right frame sections 73 and 74 (hereinafter referred to as the left and right arm sections) 721 and 722 have some elasticity. Therefore, when inserting the general-purpose terminal 4 as described above, the elasticity of the left and right arm sections 721 and 722 pushes the left and right frame sections 73 and 74 apart slightly. As a result, the restoring force of the left and right arm sections 721 and 722 puts pressure on the general-purpose terminal 4, and the general-purpose terminal 4 is held firmly. Therefore, the general-purpose terminal 4 will not fall off while driving. As an alternative configuration, a cushioning member may be provided in the grooves of the frame sections 73-75, and the general-purpose terminal 4 may be held in place by its elasticity. As shown in Figure 2, a connector terminal 76 is provided in the groove of the lower frame portion 75, which contacts the general-purpose interface terminal of the general-purpose terminal 4. In this embodiment, USB is assumed as the general-purpose interface, and the connector terminal 76 is a USB terminal. Since the USB terminal of the general-purpose terminal 4 is usually female, the connector terminal (USB terminal) 76 provided in the groove of the lower frame portion 75 is male. Furthermore, an external USB terminal (female) 77 is provided on the outer surface of the right-side frame portion 74. The external USB terminal 77 and the connector terminal 76 are connected by wiring (not shown) provided within the frame portions 74 and 75. Therefore, by connecting a USB cable (general-purpose interface cable) 70 to the external USB terminal 77, the general-purpose terminal 4 can be connected to other devices via USB. If the USB cable 70 is connected to the external USB terminal of the terminal holder 7 in advance, the general-purpose terminal 4 can be connected via USB simply by inserting it into the terminal holder 7, resulting in a simple structure. To remove the general-purpose terminal 4 from the terminal holder 7, lift the general-purpose terminal 4 while slightly spreading the left and right frame portions 73 and 74. In other words, the terminal holder 7 holds the general-purpose terminal 4 in a detachable manner. Furthermore, the base plate 71 and the arm 72 are connected by a connecting body 79 that incorporates a horizontal rotation axis. Therefore, the arm 72 and the frame sections 73-75 can be adjusted inclined relative to the horizontal axis. In addition, since the frame sections 73-75 are supported by a support column 78 that incorporates a vertical rotation axis, the frame sections 73-75 on the vertical axis can be adjusted inclined relative to the vertical axis. Therefore, the general-purpose terminal 4 held by the frame sections 73-75 can be positioned appropriately by adjusting these inclination angles. As shown in Figure 2, the mounting position of the terminal holder 7 is set so that the driver can tap the display of the general-purpose terminal 4 while seated in the driver's seat. At this time, the position of the frame sections 73-75 of the terminal holder 7 is adjusted as appropriate, as described above, and the orientation of the general-purpose terminal 4 is changed as appropriate. Next, the speed data acquisition unit 5 will be described. Figure 4 is a diagram showing the schematic configuration of the speed data acquisition unit 5 in this embodiment. As mentioned above, the speed data acquisition unit 5 is used to acquire speed data necessary for vehicle operation management from the drive system sensor 8. In this embodiment, many elements of the conventional in-vehicle device have been replaced by the general-purpose terminal 4, and the elements that could not be replaced correspond to the speed data acquisition unit 5. The speed data acquisition unit 5 is connected to a signal line 82 that is branched off from a signal line 81 to the vehicle's speedometer 80. Speedometers come in two types: electric and mechanical. Electric speedometers measure speed from engine rotation by counting the voltage applied to the ignition coil, while mechanical speedometers measure speed by mechanically detecting rotation using a gear mechanism installed on the engine's crankshaft. The speed data acquisition unit 5 in this embodiment can be used in either case and is installed by connecting a new signal line branched off from the signal line to the speedometer. In these examples, the part that counts the voltage applied to the ignition coil and the gear mechanism installed on the crankshaft correspond to "sensors installed in the vehicle's drive system". Figure 4 illustrates an example of a mechanical speedometer 80. Whether electrical or mechanical, the transmitted signal is digitized and becomes a vehicle speed pulse signal (hereinafter abbreviated as vehicle speed pulse). The vehicle speed pulse is converted into a driving speed (absolute value) according to a predetermined correspondence. This process is performed on the management server 1, as described later. In addition, a pulse matching device may be provided between the sensor 8 and the speedometer 80 to obtain more accurate speed data. In this case, the signal line is branched on the output side of the pulse matching device (between the pulse matching device and the speedometer 80) and connected to the speed data acquisition unit 5. As shown in Figure 4, the speed data acquisition unit 5 includes an input unit 51 that includes a port to which a signal line (hereinafter referred to as the speed signal line) 82 branched from a signal line 81 to the speedometer 80 is connected, an output unit 52 that outputs various data including speed data, and an output processor 53. The speed data acquisition unit 5 is also used to acquire rotational speed pulses. That is, the vehicle's engine is equipped with a sensor that detects rotational speed, and the rotational speed pulses acquired here are displayed on the tachometer 83. As shown in Figure 4, another signal line 84 is connected by branching off from the wiring to the tachometer 83, and this signal line 83 is connected to the speed data acquisition unit 5. The system of this embodiment is based on management using the three elements of a digital tachograph, but it also performs other management functions, and input ports for signals other than speed data are provided in the input unit 51. The number of input ports can be appropriately determined, ranging from 4 to 8. In this embodiment, there are 8 input ports, and as shown in Figure 4, port A is connected to the vehicle speed pulse signal line (hereinafter referred to as the speed signal line) 82, port B to the rotation speed pulse signal line 84, port C to the signal line from the refrigerator door sensor 91, port D to the signal line from the refrigerator temperature sensor 92, and port E to the signal line from the driver's seat side door sensor 93. Ports F to H are left empty. The output unit 52 transmits data to the general-purpose terminal 4 and therefore includes a general-purpose interface circuit 521. In this embodiment, a USB interface is used as the general-purpose interface and includes a USB terminal 522. The output processor 53 aggregates the data from the input unit 51 so that each data is output according to a general-purpose interface. For example, it aggregates data such as port A: xxxx, port B: yyyy, port C: 0, port D: zz, port E: 0, port F: -, port G: -, port H: - and outputs it in a general-purpose format. The general-purpose format is, for example, CSV. In this case, "xxxx" in port A is the vehicle speed pulse, and it is the number of pulses. Similarly, port B is also the number of pulses. "0" in port C means that the refrigerator door is closed (it would be 1 if it were open), and yy in port D is the temperature, so the unit is °C. Furthermore, "0" in port E means that the driver's side is closed (it would be "1" if it were open). Ports F to H mean that the data is void. USB has various transfer methods, but in this embodiment, interrupt transfer is performed. That is, in accordance with polling from the host side (general-purpose terminal 4 in this embodiment), data in the above general-purpose format is output periodically at regular intervals from the USB terminal 522. In the above example, all of ports A to E are digital signals, but when an analog signal is input, an AD converter is provided between that port and the output unit 52, and the signal is digitized and output from the output unit. As shown in Figure 2, the speed data acquisition unit 5 is connected to the general-purpose terminal 4 by a general-purpose interface cable 70, so it is desirable that it be installed in a location not far from the mounting position of the general-purpose terminal 4 (the position where the terminal holder 7 is attached). It is also necessary that it be in a location that makes it easy to connect the speed signal line 82. In this embodiment, the speed data acquisition unit 5 is assumed to be installed in the DIN space of the dashboard and is 1DIN size. However, this is not mandatory, and it does not have to be in a DIN space. Although not shown in the figure, the speed data acquisition unit 5 has a housing case that houses the above parts. Each input port included in the input section 51 is provided on the back of the housing case. The USB terminal 522 included in the output section 52 is provided on the front of the housing case. In addition, a minimum number of operation buttons, such as an ON / OFF switch, are provided on the front of the housing case. Next, the management server 1 will be described. The management server 1 is a server computer having a processor (not shown) and a memory unit 2, and various programs are implemented on it. The management server 1 accepts access from general-purpose terminals 4 and management terminals 3 via the internet 6, so it is an internet server, and it also handles various database files, so it is a database server. The management server 1 is a server on the internet 6, but it may also be a server in so-called cloud computing. The management server 1 may be a single server, or it may be a configuration of multiple servers on the internet 6 virtually set up as one server. The memory unit 2 may be provided by the management server 1, or it may be the memory unit of a server (such as a storage server) that is provided separately from the management server 1. The management server 1 processes data sent from the in-vehicle device as appropriate, stores it in the storage unit 2, and provides a service that allows the management terminal 3 to view the data on a screen (report) in an appropriate format for vehicle operation management. Hereinafter, this service will be referred to as the vehicle operation management support service. The management server 1 implements software for the vehicle operation management support service (hereinafter referred to as the vehicle operation management server software), which includes a performance data registration program 11 that stores and registers performance data in the storage unit 2, and various viewing programs 13 to 16 that transmit data to the management terminal 3 for viewing. The vehicle operation management system in this embodiment is a system for managing the operation of commercial vehicles such as vehicles of various transportation companies, taxi companies, and companies that conduct their own logistics. Hereinafter, these vehicles will be collectively referred to as commercial vehicles, and the companies that operate commercial vehicles will be referred to as operating companies. The management server 1 is usually operated and managed by a business entity that provides vehicle operation management support services. This business entity (hereinafter referred to as the system provider) sells or leases speed data acquisition units 5 to operating companies, and operates the management server 1 on the Internet 6, providing various services including vehicle operation management support services. Therefore, the system provider is both the seller (or lessor) of the speed data acquisition unit 5 and a business that provides vehicle operation management support services in the form of ASP, SaaS, etc. Furthermore, since the system provider provides vehicle operation management systems to a large number of operating companies, the management server 1 is accessed from the management terminals 3 of each operating company. In addition, the general-purpose terminals 4 are accessed from general-purpose terminals 4 on vehicles operated by each operating company. Although only one management server 1 is depicted in Figure 1, multiple servers may be provided for each operating company. Alternatively, one management server 1 may be divided and used for each operating company. Next, the management terminal 3 will be described. As mentioned above, the system of this embodiment has a transportation company as its user. The transportation company owns a large number of commercial vehicles and has a department that manages their operations. A terminal (management terminal) 3 for vehicle operation management is provided in this department. The management terminal 3 may be a desktop PC or notebook PC, etc., installed in the office of the department that performs the management. Note that the management terminal 3 does not constitute a vehicle operation management system. Also, the management terminal 3 corresponds to the "office terminal" in claim 1, in the sense that it is a terminal installed in the office of the department that performs the management. The management terminal 3 has application software (hereinafter referred to as the "operation management app") for receiving vehicle operation management services pre-installed. While it is possible to have all of the software on the management server 1, considering the convenience of the management staff, a portion of it is installed on the management terminal 3, and this constitutes the operation management app. The operation management app includes a program for accessing the management server 1, a program for displaying data transmitted from the management server 1 on the display, etc. Next, we will describe the vehicle operation management support service provided by the general-purpose terminal 4 and the management server 1. First, we will explain the transmission of data from the general-purpose terminal 4 to the management server 1 and the storage of data by the management server 1. The general-purpose terminal 4 constitutes a digital tachograph in-vehicle unit, and one of its main purposes is to transmit data to the management server 1. Application software for this purpose (hereinafter referred to as the in-vehicle unit application) is pre-installed on the general-purpose terminal 4. Figure 5 is a schematic diagram showing the structure of the in-vehicle application. The in-vehicle application is programmed using object-oriented programming techniques and consists of various program modules and data files. As shown in Figure 5, the in-vehicle application is a program that runs on a general-purpose OS 40 running on a general-purpose terminal 4, and has a main module 41, a task start module 42, and a data storage module 43 that acquires speed data from the speed data acquisition unit 5, stores it temporarily, and collects the acquired speed data in certain units and sends it to the management server 1 for storage. In addition, the in-vehicle application has a location information module 44, a task recognition module 45, a voice playback module 46, a settings module 47, etc. The configuration module 47 is a module for setting various information necessary for vehicle operation management. The information set here includes information about the user, i.e., the driver, who uses the in-vehicle application. As shown in Figure 5, the in-vehicle application includes a configuration information file 48 that records the configuration information. The information recorded in the configuration information file 48 is configuration information such as the general-purpose terminal ID, driver ID, and driver name. The configuration module 47 displays a screen for entering each piece of information and records and registers the entered information in the configuration information file 48. Meanwhile, the storage unit 2 of the management server 1 also stores a file (hereinafter referred to as the driver information file) 21 containing user information (driver information) for the in-vehicle device application of each general-purpose terminal 4. The driver information file 21 is a database-style file that records the above-mentioned setting information for each driver ID. The driver information file 21 also serves the purpose of authentication and includes a field for recording a password that is registered in advance. Next, the main module 41 of the in-vehicle application will be described. The main module 41 is a module that is automatically executed when the in-vehicle application is launched. The main module 41 is a module that resides in the background while the in-vehicle application is running, and it is responsible for executing other modules and switching screen modes. Figure 6 is a schematic diagram showing an example of a screen displayed by the main module 41 (hereinafter referred to as the in-vehicle main screen). As shown in Figure 6, the in-vehicle main screen is provided with a command button labeled "Start Operations" (hereinafter referred to as the "Start Operations button") 410, a command button labeled "Complete Operations" (hereinafter referred to as the "Complete Operations button") 419, a command button labeled "Initial Settings", and the like. The business start button 410 is the start button for the business start module 42. Figure 7 is a flowchart showing an overview of the business start module 42. As shown in Figure 7, after starting up, the business start module 42 first determines whether the speed data acquisition unit 5 is correctly recognized. In this embodiment, the speed data acquisition unit 5 is recognized as a peripheral device of the general-purpose terminal 4. That is, as shown in Figure 5, a device driver (hereinafter simply referred to as a device driver) 49 for using the speed data acquisition unit 5 is pre-installed on the general-purpose terminal 4 and is configured to operate normally on the general-purpose OS 40. When the business start module 42 is started, it first determines whether the speed data acquisition unit 5 is correctly recognized by the device driver 49. If it is not recognized, it returns an error message and terminates the program. If it is correctly recognized, the business start module 42 then executes the login submodule (hereinafter referred to as login sub) 420. The login sub 420 is a module for establishing access rights to the management server 1. The management server 1 has a login program (not shown) implemented on it, and the login sub 420 executes the login program on the management server 1 by specifying a predetermined URL for the management server 1. The login program displays an authentication screen on the general-purpose terminal 4 that prompts the user to enter a driver ID and password. The authentication screen includes a submit button, and the login program compares the submitted driver ID and password with the contents of the driver information file 21. If they are correct, it establishes access rights to the management server 1 and starts a session. Once login is complete, the business start module 42 executes a submodule (hereinafter referred to as the vehicle selection sub) 421 for inputting information to identify the vehicle to be used for the business. The storage unit 2 of the management server 1 stores a database file (hereinafter referred to as the vehicle information file) 22 that records information on each vehicle operated by the transportation company. Figure 8 is a schematic diagram showing an example of the structure of the vehicle information file 22. As shown in Figure 8, the vehicle information file 22 is a database file that registers records for each vehicle, each consisting of fields such as "Vehicle ID," "Registration Number," "Vehicle Description," "Presence or Absence of Refrigerator," "Set Refrigeration Temperature," "Vehicle Speed ​​Pulse Conversion ID," and "Rotation Speed ​​Pulse Conversion ID." The "Registration Number" records the license plate number of the vehicle. The "Vehicle Description" is a field where a description of the vehicle is entered as text. The "Set Refrigeration Temperature" is a field for setting a threshold for the refrigeration temperature, and a value exceeding this threshold will be entered to indicate an abnormal refrigeration temperature. Since the refrigeration temperature may differ for each vehicle, it is managed in the database. The "Vehicle Pulse Conversion ID" is an ID for selecting the conversion formula when converting the vehicle speed pulse, and the "Rotation Speed ​​Pulse Conversion ID" is an ID for selecting the conversion formula when converting the rotation speed pulse. Meanwhile, when the vehicle selection sub-system 421 is started, it displays a vehicle selection screen (hereinafter referred to as the vehicle selection screen) on the general-purpose terminal 4. Figure 9 is a schematic diagram showing an example of the vehicle selection screen. The vehicle selection screen displays a list of information on all vehicles operated by the affiliated transportation company. The vehicle selection sub-system 421 is programmed to obtain this information from the vehicle information file 22 on the management server 1 and display it on the vehicle selection screen. At the far right of each row in the list on the vehicle selection screen, there is a command button (hereinafter referred to as the "select button") 423 labeled "Select". When the select button 423 of any row is tapped, the vehicle in that row is selected. The vehicle selection sub 421 temporarily stores the vehicle ID of the selected vehicle in a memory variable. Since drivers often use the same vehicle for each job, it is preferable that the vehicle ID selected during the previous execution is stored on the general-purpose terminal 4 or the management server 1 in the in-vehicle application so that when the vehicle selection screen is displayed, the information of that vehicle ID is displayed at the top of the list. Alternatively, a checkbox labeled "Same as last time" may be provided, and checking this box will store the same vehicle ID as last time in the memory variable. After logging in and selecting a vehicle ID, the business start module 42 is configured to then execute a submodule (hereinafter referred to as the route selection sub) 422 that prompts the user to select a route to perform the work. The storage unit 2 of the management server 1 stores a route information file 23 that records information on transportation routes for each transportation company. Although not shown in the diagram, the route information file 23 is a database file that records records for each route, consisting of fields such as "route ID," "route name," and "hazardous location information file name." Furthermore, the storage unit 2 of the management server 1 stores a hazardous location information file 24 corresponding to each record in the route information file 23. The hazardous location information file 24 is a file created for each route and is a database file that records the number of hazardous locations, each consisting of records with fields such as "hazardous location information (numerical value)" and "hazardous location information (text)". Of these, "hazardous location information (numerical value)" is a field that records the hazardous location on the route as latitude and longitude information, such as GPS information. "Hazardous location information (text)" is text that describes the hazardous location. The route selection sub 422 is programmed to open the route information file 23 of the relevant transportation company according to the driver ID, and to display a list of route names on the route selection screen (not shown) for the driver to select. As a result of the selection, the route ID of that route is stored in a memory variable on the in-vehicle device application. Once the vehicle ID and route ID are stored in memory variables, the business start module 42 automatically generates a new business ID and stores it in another memory variable. The business ID is an ID generated for each day or each business operation of a particular driver, and is an ID generated for each unit of vehicle operation management. For example, it is automatically generated from the driver ID and the system date and time when the business start button 410 is tapped. For example, if the driver ID is "AA0001" and the date and time when the business start button 410 is tapped is 9:00 AM on October 1, 2014, then "AA0001-201410010900" is generated as the business ID. The business ID is always stored in a memory variable while the in-vehicle application is running. As shown in Figure 7, after generating and storing the business ID, the business start module 42 assigns "1", which means "operating" (driving), to a memory variable for status determination (hereinafter referred to as the status variable) and stores it. The state variable holds information corresponding to the status of the operational tasks being performed using the in-vehicle device application, with "0" indicating non-work status (after work has finished but before work has started). Meanwhile, the management server 1 has a business registration program 12 implemented as a server-side program, as described later. The business registration program 12 is called and executed by the business start module 42, and is responsible for adding records to the business information file 25, adding new records to the performance data file 26, etc. As shown in Figure 7, the business start module 42 performs login, vehicle selection, route selection, and status variable update in order, and then executes the business registration program 12 on the management server 1. When the management server 1 sends a reply (return value) indicating that the business registration program 12 has been successfully executed, the business start module 42 terminates. Next, the work tracking module 45 will be described. The work tracking module 45 is a module for tracking the driver's current work status for management purposes. In this embodiment, the work tracking module 45 is a module that supports work tracking by transmitting information entered by the driver on the general-purpose terminal 4 and the output of equipment installed in the vehicle to the management server 1. Specifically, as shown in Figure 6, the main screen of the in-vehicle device is provided with a frame for work tracking, and several command buttons for work tracking (hereinafter referred to as work tracking buttons) 411 to 419 are provided within this frame. In this example, there are a total of eight work tracking buttons 412 to 419, each labeled "Loading," "Unloading," "Break," "Inspection," "Refueling," "Wash," and "Return to Depot." As mentioned above, once work begins and a work ID is assigned, the status variable is set to "1", which means work is in progress (driving). The work tracking module 45 changes the value of this status variable according to the tap status of each of the work tracking buttons 411 to 419. For example, Driving: 1 Loading: 2 Standby: 3 Unloading: 4 Break: 5 Inspection: 6 Refueling: 7 Washing: 8 Returning to depot: 9 Variables are assigned according to each state. For example, if the "Loading" button 412 shown in Figure 5 is tapped, the work tracking module 45 changes the status variable to "2". If the "Standby" button 413 is tapped, the work tracking module 45 changes the status variable to "3". The same applies to the other buttons. Note that "Standby" means the state of waiting for loading or unloading. In this way, the state variables, which are changed according to the tap status of the work tracking buttons 411 to 419, are sent to the management server 1 along with the speed data by the data transmission sub 432 of the data storage module 43, as will be described later. These are then used for vehicle operation management via the management server 1. Next, the location information module 44 will be described. The location information module 44 is a module that uses the location information notification function of the general-purpose terminal 4 to notify the management server 1 of the vehicle's current location. Most portable general-purpose terminals 4 currently on the market, whether tablet PCs or smartphones, are equipped with a location information notification function such as GPS. Various general-purpose operating systems such as Android, iOS, and Windows 8 provide APIs for location information notification to developers. The location information module 44 is a module that acquires location information using the location information API corresponding to the OS installed in the general-purpose terminal 4 and stores it in a memory variable (hereinafter referred to as the location information variable) on the in-vehicle application. The location information stored is the location at the time the location information module 44 is started. Next, the data storage module 43 will be described. Figure 10 is a flowchart showing an overview of the data storage module 43. As shown in Figure 10, the data storage module 43 is a module that, in general terms, executes a data acquisition submodule (hereinafter referred to as the data acquisition sub) 431 and, in parallel, executes a data transmission submodule (hereinafter referred to as the data transmission sub) 432 at regular intervals. The data acquisition sub 431 is a module that is always in the running state after the execution of the business start module 42, as long as the state variable is not "0". The data acquisition sub-system 431 is a program that acquires speed data from the speed data acquisition unit 5 via the USB interface. The data acquisition sub-system 431 accesses the speed data acquisition unit 5 and interrupts the transfer of data held in the output section of the speed data acquisition unit 5. The transfer period is set by the device driver 49, and is set appropriately within a range of approximately 5 ms to 100 ms (hereinafter referred to as the device period). The in-vehicle device application includes a file for temporarily recording data (hereinafter referred to as a temporary file). Figure 11 is a schematic diagram showing an example of the structure of a temporary file. The temporary file is a general-purpose database file such as CSV. As shown in Figure 11, the temporary file consists of a "Business ID" field, a "Transfer Date and Time" field, a field for recording data for each port, a "Task" field, a "Location Information" field, and so on. The speed data acquisition unit 5 sends data at the device cycle set by the device driver 49. Therefore, to acquire speed data as frequently as possible, it is possible to acquire speed data at the device cycle, but since the amount of data would become too large, speed data is acquired at a longer cycle than the device cycle (hereinafter, this cycle is called the acquisition cycle). The acquisition cycle is, for example, 0.5 seconds. That is, new data is transferred and updated to the USB port of the general-purpose terminal 4 at the device cycle, but the data acquisition sub 431 acquires data from the USB port at the acquisition cycle of 0.5 seconds, which is longer than the device cycle, and adds the new record to the temporary file for recording. Furthermore, the data acquisition sub-system 431 stores the state variable at the time the acquisition cycle is reached in the "Work" field of the temporary file. In addition, the data acquisition sub-system 431 reads the value stored in the location information variable at that time (the execution result of the location information module 44) and stores it in the "Location Information" field. Meanwhile, while the data storage module 43 is executing the data acquisition sub 431, it executes the data transmission sub 432 at a fixed interval (hereinafter referred to as the transmission period), as shown in Figure 10. The transmission period is, for example, 10 minutes. Figure 12 is a flowchart showing an overview of the data transmission sub 432. As shown in Figure 12, the data transmission sub 432 first sends the data of all records currently recorded in the temporary file to the management server 1 as a file in a general-purpose format such as CSV, along with location information. That is, it calls the performance data registration program 11 implemented in the management server 1, passes the data to it, and has it executed. Next, the data transmission sub-system 432 copies each record from the temporary file to the backup file, then deletes each record from the temporary file to set the record count to zero. The backup file is a database file with the same structure as the temporary file and is stored on the storage unit 2 (hard disk, etc.) on the general-purpose terminal 4. The data transmission sub-system 432 terminates after transmitting data to the management server 1 and recording the data to the backup file. Although the explanation of the backup file has been omitted, it is created as a new file when the business start module 42 is started. The file name is a file name using the business ID, and it is intended to be easily found by specifying the business ID. Next, the audio playback module 46 will be described. The audio playback module 46 is a module that enables playback of audio files sent from the management server 1 on the in-vehicle application by incorporating an audio playback API into the in-vehicle application. As will be described later, when the diagnostic / work awareness program 14 or the safety management program 16 on the management server 1 is being executed, an audio file may be sent to the general-purpose terminal 4 by an operation from the management terminal 3. The audio playback module 46 is used to play this audio file on the in-vehicle application and to convey an audio message to the driver. Next, we will explain the various programs and files on the management server 1. Corresponding to the business start module 42 of the in-vehicle device application mentioned above, the management server 1 has a business registration program 12 implemented. In addition, the performance data registration program 11 is implemented corresponding to the data transmission sub 432 of the data storage module 43 of the in-vehicle device application. First, we will explain the business registration program 12. As mentioned above, the business registration program 12 is called and executed by the business start module 42 and is a program that adds records to the business information file 25, adds new records to the performance data file 26, etc. The business information file 25 will be explained using Figure 13. Figure 13 is an illustrative diagram showing the structure of the business information file 25. As shown in Figure 13, the business information file 25 is a database file in which many records consisting of fields such as "Business ID," "Driver ID," "Driver Name," "Vehicle ID," "Business Start Date and Time," and "Business End Date and Time" are recorded. Next, the performance data file 26 will be explained using Figure 14. Figure 14 is a schematic diagram illustrating the structure of the performance data file 26. The performance data file 26 is a file that is newly generated when a new business ID is assigned by the business start module 42. The performance data file 26 is usually named using the business ID. As shown in Figure 14, the performance data file 26 is a file that records many records consisting of fields such as "time," "travel time," "travel distance," "instantaneous speed," "location information," and "work." When the business registration program 12 is called and started by the business start module 42, it adds a new record to the business information file 25 and records the information in each field. The business start module 42 is executed with the business ID, driver ID, and vehicle ID stored in memory variables as arguments, and the business registration program 12 records this information in the "Business ID", "Driver ID", and "Vehicle ID" fields of the added record. It also records the start date and time of the business registration program 12 in "Business Start Date and Time". The business registration program 12 also creates a new performance data file 26 with a file name using the business ID and stores it in the storage unit 2. The created performance data file 26 is left open and in a state where records can be added. The business registration program 12 then terminates in this state. Furthermore, as mentioned above, the performance data registration program 11 is called and executed by the data transmission sub-function 432 of the in-vehicle device application, which is executed at each transmission cycle. The performance data registration program 11 is executed with the business ID as an argument, and after startup, it is programmed to add one record to the corresponding performance data file 26, record the values ​​of each field, and register them. Specifically, it records the "Transfer Date and Time" data from the temporary file in the "Time" field, the vehicle speed pulse data, which is the data from port A, in the "Vehicle Speed ​​Pulse" field, the rotation speed pulse data, which is the data from port B, in the "Rotation Speed ​​Pulse" field, the data from port C in the "Refrigerator Door" field, the data from port D in the "Refrigeration Temperature" field, and the data from port E in the "Driver's Side Door" field. In addition, it records the data from the "Temporary Information" field of the temporary file in the "Location Information" field. Furthermore, the performance data registration program 11 is programmed to calculate the instantaneous speed and rotational speed through calculation processing and record them in the performance data file 26. Specifically, the vehicle speed pulse is a pulse corresponding to the vehicle's driving speed, but the speed of one pulse varies slightly depending on the vehicle manufacturer. As shown in Figure 8, the vehicle information file 22 has a field called "vehicle speed pulse conversion ID". The performance data registration program obtains the vehicle ID from the business information file 25 according to the business ID and obtains the vehicle speed pulse conversion ID for that vehicle. Then, the performance data registration program selects a conversion formula according to the vehicle speed pulse conversion ID and calculates the instantaneous speed from the transmitted vehicle speed pulse. As for the rotational speed pulse, there is not much difference in specifications among vehicle manufacturers, but similarly, a conversion formula is selected according to the vehicle ID and calculation processing is performed. That is, the performance data registration program 11 is programmed to obtain the value of the "rotational speed pulse conversion ID" field in the vehicle information file 22, select a conversion formula for the rotational speed pulse, and calculate the rotational speed using the selected conversion formula. As described above, in the system of this embodiment, speed data acquired by the speed data acquisition unit 5 is sent to the management server 1 via the general-purpose terminal 4, and the performance data registration program 11 calculates the instantaneous speed and rotational speed through computational processing and records each data in the performance data file 26 on the storage unit 2 on the management server 1. If the general-purpose terminal 4 is a tablet PC, it is preferable that it be a cellular type. If it is a Wi-Fi type, a Wi-Fi router will be used in conjunction with it, but since the access points are limited, it is not very suitable for usage patterns that require constant connection to the management server 1 during business hours, as in the vehicle operation management system of this embodiment. As described above, the information recorded in the performance data file 26 is viewed as needed on the management terminal 3 for vehicle operation management. The management server 1 has various programs 13 to 16 for viewing as part of the vehicle operation management support service. Next, these viewing programs 13 to 16 will be described. As shown in Figure 1, the management server 1 has a three-element viewing program 13 for viewing digital tachograph three-element data, a diagnostic / work understanding program 14 for viewing vehicle status diagnostic information and work understanding information, an eco-evaluation program 15 for viewing eco-driving evaluation information, a safety management program 16, etc. implemented on it. As described above, the operation management application is pre-installed on the management terminal 3. The operation management application is provided to the operation company in advance and installed on the management terminal 3. Figure 15 is a schematic diagram showing an example of the initial screen displayed on the management terminal 3 by the operation management application (hereinafter referred to as the management application initial screen). Although not shown in the diagram, when the operation management application is launched on the management terminal 3, it automatically logs in to the management server 1. An office ID is issued in advance to the operation company, and a person in charge ID is issued to the person in charge of management. The storage unit 2 of the management server 1 stores an office information file (not shown) that records office information and a person in charge information file (not shown) that records information on the person in charge of management at each office. The operation management application prompts the user to enter the office ID, person in charge ID, and password on the login screen and submits them. The entered information is then compared with the information in the office information file and person in charge information file to log in (i.e., establish access rights to the management server 1). Once logged in, the management application initial screen shown in Figure 15 is displayed on the management terminal 3. As shown in Figure 15, the initial screen of the management application is equipped with buttons such as a button labeled "Driver / Date Selection" (hereinafter referred to as the "task selection button") 311, a button labeled "Three-Element Display" (hereinafter referred to as the "three-element viewing button") 312, a button labeled "Diagnosis / Work Understanding" (hereinafter referred to as the "diagnosis / work understanding button") 313, a button labeled "Eco Evaluation" (hereinafter referred to as the "eco evaluation button") 314, and a button labeled "Safety Management" (hereinafter referred to as the "safety management button") 315. The task selection button 311 is a button for selecting the operation task to be managed. As shown in Figure 1, the storage unit 2 of the management server 1 stores a driver information file 21 that records driver information. A driver information file 21 is provided for each business office (one for each business office ID), and it is a database file that records the names, driver IDs, etc., of the drivers working at that business office. When the task selection button 311 is tapped, the task selection program 17 on the management server 1 is started. The task selection program 17 displays a task selection screen having a driver selection field and a date selection field on the management terminal 3, and temporarily stores the driver ID of the selected driver and the date in memory variables. The task selection program 17 searches the task information file 25 using the selected driver ID and date, identifies the corresponding record, activates it, and reads the task ID of the record. It then temporarily stores the task ID in a memory variable. If the three-element view button or similar is tapped before the task ID is stored in the memory variable, an error message such as "Please select the driver and date first." is displayed to prompt the administrator to identify the task. On the other hand, the three-element viewing button shown in Figure 15 is the execution button for the three-element viewing program 13. The three-element viewing program 13 reads the business ID from a memory variable and opens the performance data file 26, which has that business ID as its filename. It then reads the data from each record in the performance data file 26, processes the data as appropriate, and sends a screen (hereinafter referred to as the three-element viewing screen) embedded in a viewing form to the management terminal 3, where it is programmed to be displayed. Figure 16 is a schematic diagram showing an example of the three-element viewing screen displayed on the management terminal 3. As shown in Figure 16, the three-element viewing program 13 displays various information such as the driver ID, and also displays the three-element operation data as graphs. In this example, the time-versus-speed graph and the time-versus-distance graph are displayed vertically. The time-versus-distance graph is a graph that turns back at 5 km intervals. The data processing for displaying these graphs is straightforward for those skilled in the art, so no explanation is provided. As shown in Figure 16, the time axis can be selected from 24-hour, 8-hour, and other spans, and the data can be displayed within the selected span. When a narrow span is selected, a scroll bar is displayed in the graph display frame, and the program is programmed to scroll as needed. In addition, regarding the time information among the three elements, in addition to displaying the time from the start of driving (driving time), the time for each driving distance and each instantaneous speed data may also be displayed. Next, the diagnostic and work tracking program 14 will be explained. The diagnostic and work tracking program 14 is a program that diagnoses the condition of the vehicle and tracks the driver's work based on data transmitted from the general-purpose terminal 4. Tapping the diagnostic and work tracking button 313 shown in Figure 15 starts the diagnostic and work tracking program 14. Figure 17 is a schematic diagram showing an example of the screen displayed on the management terminal 3 by the diagnostic and work tracking program 14 (hereinafter referred to as the diagnostic and work tracking screen). The diagnostic and work tracking program 14 is also executed when a task is selected (when the task ID is stored in a memory variable). If nothing is selected, an error message is displayed, and the user is prompted to make a selection. The diagnostic and work tracking is basically vehicle operation management during the execution of tasks. The task selection screen includes a button labeled "Today," and when this is tapped, a list of tasks being performed on that day is displayed, and the program is programmed to select any task (i.e., a driver) from among them. As shown in Figure 17, the diagnostic and work management screen displays information such as the driver's information and the start date and time of the work for the selected work ID. This information is retrieved and displayed from the work information file 25 according to the work ID. Information such as driving time and distance is also displayed, and this information is calculated and displayed based on data retrieved from the actual data file 26 for the relevant work according to the work ID. Normally, since work is in progress, the data such as driving time is data up to that point (when the diagnostic and work management program 14 is started). As shown in Figure 17, a display area for the driver's current status (hereinafter referred to as the "current status display area") 331 is provided in the middle of the diagnostic and work tracking screen. The diagnostic and work tracking program 14 is programmed to read the value of the "Work" field in the latest record of the performance data file 26 and display the current status as text in the current status display area 331 according to the aforementioned correspondence. Therefore, this area is basically based on the result of the driver tapping on the in-vehicle device application on the general-purpose terminal 4 (i.e., self-reporting). However, there are also cases where the program makes a logical determination from the values ​​of other fields in the performance data file 26 before displaying in the current status display area 331. For example, the program is programmed to display "Driving" in the current status display area 331 only if the value of the "Work" field is "1" and the value of the "Instantaneous Speed" field is above a certain threshold. In this example, if the value of the "Instantaneous Speed" field is below the threshold, an error message will be displayed in the current status display area 331. Alternatively, the program may determine whether or not the driver is driving based solely on the value of the "Instantaneous Speed" field and display accordingly. Below the current status display area 331, there are fields 332 for displaying the open / closed status of the driver's side door, 333 for displaying the refrigeration temperature, and 334 for displaying the open / closed status of the refrigerator door. The diagnostic and work understanding program 14 is programmed to read and display these fields 332 to 334 from the latest record in the performance data file 26, specifically from the "driver's side door," "refrigeration temperature," and "refrigerator door" fields. Note that in the "driver's side door" and "refrigerator door" fields, "0" means closed and "1" means open, so the text is converted accordingly. To the right of the current status display area 331, there is a map display area 335 that displays the vehicle's current location on a map. The diagnostic and work tracking program 14 is similarly programmed to obtain location information from the "location information" field of the latest record in the performance data file 26, separately obtain map data, and then display the vehicle's location on the map with a special mark (in this example, "◎"). Map data is obtained from a separate database file based on location information, but because the amount of data is enormous, it is usually stored on a server separate from the management server 1. In some cases, the data may be obtained from a server of another company that supplies map data. Furthermore, below the map display area 335, there is a field for displaying location information based on latitude and longitude. This field displays the location information obtained directly from the performance data file 26. Below this field, there is a field for displaying the current location information as text. The information in this field is also usually obtained from the server that provides the map data. This type of server has a database that represents the current location in text corresponding to the latitude and longitude information, and is able to provide the current location as text information. The diagnostic and work understanding program 14 is programmed to use this service to insert the text information. Furthermore, as shown in Figure 17, a section labeled "Diagnosis Result" (hereinafter referred to as the "Diagnosis Result Display Section") 336 is provided in the lower middle of the diagnosis / work monitoring screen, and either a "Normal" or "Abnormal" lamp lights up (more accurately, a checkbox is checked, but this is expressed figuratively). The diagnosis / work monitoring 14 has a module (hereinafter referred to as the "Diagnosis Module") that diagnoses the current status of the vehicle from the values ​​of each record in the performance data file 26. The diagnostic module determines the diagnostic result by making some judgments based on the values ​​of each field in the performance data file 26. The diagnosis covers multiple items, and each item is judged as normal or abnormal. The diagnostic module is programmed to illuminate the "abnormal" lamp if any item is judged to be abnormal, and the "normal" lamp otherwise. For example, if the "driver's side door" field has a false value (open state), the module will judge it as abnormal only if the "state variable" field is "1", which means driving, and will judge it as normal otherwise. Similarly, if the "refrigerated compartment door" field has a false value (open state), the module will judge it as normal only if the "state variable" field is "2", which means "loaded", and will judge it as abnormal in all other cases. Furthermore, the value of the "Cooling Temperature" field is obtained when the diagnostic / work tracking program 14 is started, and normal or abnormal status is determined according to this value. Specifically, the diagnostic / work tracking program 14 searches the business information file 25 according to the business ID held in the memory variable and obtains the vehicle ID from the corresponding record. Then, it obtains the value of the set cooling temperature from the vehicle information file 22, and if the value of the "Cooling Temperature" field is less than or equal to that value, it is determined to be normal, and if it is higher than that value, it is determined to be abnormal. As shown in Figure 17, the diagnosis and work management screen has a field 337 for communicating the details of an abnormality (hereinafter referred to as the abnormality notification field). The abnormality notification field 337 is a text box, and the diagnosis module is programmed to display text in the abnormality notification field 337 to communicate the details of the abnormality if an abnormality is determined in each diagnosis result. The text here is a standard phrase that has been set in advance within the module corresponding to each item. For example, a sentence such as "The cooling temperature exceeds the standard value. Please check it." Furthermore, a command button (hereinafter referred to as the voice notification button) 338 labeled "Notify the driver of the abnormality by voice" is provided in the lower left corner of the diagnostic and work management screen. Correspondingly, the diagnostic and work management program 14 includes a voice notification module. The voice notification module is a module that informs the driver of the abnormality by voice when the diagnostic module determines that an abnormality has occurred. The voice notification module is a program on the management server 1, and correspondingly, as mentioned above, the in-vehicle application on the general-purpose terminal 4 includes a voice playback module 46. The storage unit 2 of the management server 1 stores audio files for anomaly notification (hereinafter simply referred to as "audio files") according to the nature of the anomaly for each item. The audio notification module is programmed to select an audio file according to the item determined to be an anomaly by the diagnostic module and send it to the general-purpose terminal 4. Specifically, the audio notification module obtains the IP address (fixed IP address) of the general-purpose terminal 4 from the environment variables used during login and executes the audio playback module 46 of the in-vehicle application running on the terminal at this address. The audio playback module 46 is programmed to display a message on the screen of the general-purpose terminal 4 indicating that an audio file (anomaly notification message) has been received, and to play the transmitted audio file through the built-in speaker of the general-purpose terminal 4. Next, the eco-evaluation program 15 will be described. Figure 18 is a schematic diagram showing an example of a screen displayed on the management terminal 3 by the eco-evaluation program 15 (hereinafter referred to as the eco-evaluation screen). As shown in Figure 18, the eco-evaluation screen includes a section 341 for displaying graphs related to the eco-evaluation (hereinafter referred to as the graph display section) and a section 342 for displaying the eco-evaluation score (hereinafter referred to as the score display section). The eco-evaluation program 15 evaluates the degree to which a vehicle's operation is environmentally conscious based on data transmitted from the general-purpose terminal 4, and allows users to view the results. Specifically, the eco-evaluation program 15 draws an ideal reference speed curve for the operation based on the actual driving data sent from the general-purpose terminal 4, and performs an eco-evaluation based on the degree of deviation from this curve. Whether driving is environmentally conscious (eco-driving) can be simply indicated by the amount of CO2 emissions (exhaust gas). In this case, repeatedly accelerating and decelerating suddenly without regard for safety will result in a large amount of exhaust gas and will not be considered eco-driving. Unnecessary sudden acceleration and deceleration often occur when the distance between vehicles is too short, as drivers try to keep up with the vehicle in front without maintaining a safe distance, leading to frequent sudden acceleration and deceleration. If a sufficient distance is maintained between vehicles, sudden acceleration and deceleration will decrease, and even if the same distance is traveled, the amount of exhaust gas will be lower. Lower exhaust gas means less fuel consumption, which is a cost benefit for transportation companies, and maintaining a sufficient distance between vehicles is also desirable from the perspective of accident prevention. For example, Japanese Patent Publication No. 3944549 discloses a technique for performing eco-evaluation by obtaining a smooth curve (a reference speed curve in this example) by performing a Fourier transform on a graph of speed data (a graph of speed versus time), and the technique described in that publication can be used. Alternatively, a reference speed curve can be obtained by identifying inflection points in the speed data graph (time points where the speed changes by more than a certain amount), calculating the intermediate speeds at the preceding and succeeding time points, and connecting the intermediate points. In any case, the reference speed curve can be said to be a graph of speed data in an ideal driving situation without sudden acceleration or deceleration (or with as little as possible). The eco-evaluation program 15 compares the reference speed curve created by any of the above methods with the speed curve of the actual data, which is the original data, and calculates the amount of deviation therebetween. An eco-evaluation score is calculated according to the magnitude of the amount of deviation. Naturally, a smaller amount of deviation results in a higher score. As shown in FIG. 18, the eco-evaluation program 15 is programmed to display the speed curve 344 of the actual data and the calculated reference speed curve 343 in the graph display column, and display the calculated eco-evaluation score in the score display column 342. Incidentally, for the eco-evaluation, in some cases, data on fuel consumption may also be taken into account. Data on fuel consumption is usually obtained by the full-tank method. That is, the fuel tank is always filled up at the time of refueling, and it is specified that the total amount of fuel filled at a certain refueling is the amount of fuel used from the previous refueling to the current refueling. Then, the average fuel consumption is calculated from the relationship with the cumulative mileage during that period, and it may be used as the eco-evaluation for the vehicle or driver. To enable such management, a database file recording the refueling data (refueling date, amount of fuel) of each vehicle is stored in the storage unit 2, and a program for storing the amount of fuel via the general-purpose terminal 4 is installed in the management server 1. Next, the safety management program 16 will be described. FIG. 19 is a schematic diagram showing an example of a screen (hereinafter, safety management screen) displayed on the management terminal 3 by the safety management program 16. As shown in FIG. 19, the safety management screen includes a column (hereinafter, passing status display column) 351 for displaying the passing status of dangerous locations, a column (hereinafter, exceeding times display column) 352 for displaying the number of times of speed exceeding, and the like. Regarding the passage status display area 351, the safety management program 16 is programmed to display a list of hazardous locations and their passage status. Specifically, the safety management program 16 searches the business information file 25 according to the business ID held in a memory variable to obtain the route ID, and obtains the file name of the hazardous location information corresponding to that route ID from the route information file 23. Then, it opens the hazardous location information file 24 and is programmed to display the "hazardous location information (text)" of each record in a list in the passage status display area 351. Then, the safety management program 16 opens the latest record in the performance data file 26 and obtains the value of the "location information" field. Since this information is numerical information of latitude and longitude, the program compares this value with the value of "hazardous location information (numerical value)" in the hazardous location information file 24 to determine whether or not the vehicle has passed through the hazardous location. If it has passed through, the safety management program 16 switches the display in the row of the passage status display column 351 to "Passed". Furthermore, regarding speeding, the safety management program 16 determines how many times the maximum speed limit for public roads, 60 km / h, was exceeded along the entire length of the route. Specifically, the safety management program 16 counts the number of records in the performance data file 26 where the "instantaneous speed" field is 60 km / h. In this case, consecutive records are counted as one instance (one record). The program is then programmed to display the total count in the overrun display field 352. However, this part is customizable, allowing the operating company to set its own speed limits. For example, it is possible to limit the speed to 50 km / h for the entire route, or to set a lower speed limit than the legal limit in specific sections. For example, if it is determined that a specific expressway has been entered based on data from the ETC onboard unit or location information (described later), the speed limit on that expressway could be limited to 90 km / h, lower than the legal limit. Also, as shown in FIG. 19, at the lower left within the safety management screen, there is a command button (hereinafter referred to as the danger notification button) 353 labeled "Notify the driver about dangerous locations by voice". When the danger notification button 353 is clicked, the memory variable regarding danger notification on the safety management program 16 is changed to the notification mode. In the notification mode, based on the position information transmitted from the general-purpose terminal 4, when it is determined that the vehicle is approaching a dangerous location, a voice file with content such as "You are approaching a dangerous location. Please be careful." is programmed to be transmitted to the general-purpose terminal 4. Incidentally, on the safety management screen, there is a command button 354 labeled "Update". When this button 354 is clicked or tapped, the values of the fields of the records in the performance data file 26 are re-read, and it is programmed to redisplay the information in the passing status display column 351 and the overrun count display column 352 based on that information. Additionally, a configuration that automatically updates at regular intervals may also be adopted. In the safety management program 16 described above, it is also possible to record the information on the maximum speed at each location of the route in a file in advance and store it in the storage unit 2 of the management server 1, and then finely determine the overrun count while referring to this information. Incidentally, as shown in FIG. 19, on the safety management screen, as reference information, there are provided a map display column 355 for displaying the current position of the vehicle and a column for displaying the information on the current position in numerical or text form. However, instead of (or in addition to) this, a column for displaying three-element data may also be provided. Next, a general description will be given of the overall operation of the vehicle operation management system according to the above-described embodiment. The operation system business company attaches the speed data acquisition unit 5 and the terminal holder 741 to each vehicle that needs to be operationally managed as described above. Also, it receives the in-vehicle device application from the system provider company and installs it on each general-purpose terminal 4 that is planned to be used. Also, for the operation management application, it receives the application from the system provider company and installs it on the management terminal 3. Then, the operation system business company concludes a usage contract for various services on the management server 1 with the system provider company and makes various programs on the management server 1 executable from the management terminal 3. During daily operations (driving duties), the driver brings the general-purpose terminal 4 into the vehicle and attaches it to the terminal holder 741. The general-purpose terminal 4 is also connected to the cigarette lighter socket using a USB power cable. The driver turns on the power to the general-purpose terminal 4, starts the OS, and then launches the in-vehicle application. Following the operation start module 42, the driver selects a vehicle and route, enters their user ID, and logs into the management server 1. This executes the operation registration program 12, adding a new record to the operation information file 25, and creating and storing a new performance data file 26. Meanwhile, the driver, while remaining logged in, starts the vehicle and begins their driving duties. The driver operates the vehicle, loading cargo at designated locations, transporting it to designated locations for unloading, and returning to the depot. During this time, the speed data acquisition unit 5 acquires speed data from the sensor 8 and interrupts the transfer of information from each input port A to H via a USB cable to the general-purpose terminal 4 at each transfer cycle. The in-vehicle application checks the USB input terminal at each acquisition cycle, reads the contents of the data file being transferred (a general-purpose file such as CSV), and records it in a temporary file. Then, at each transmission cycle, the data transmission sub 432 operates and sends the contents of the temporary file to the management server 1. On the management server 1, the performance data registration program 11 is called by the data transmission sub 432, adds records to the performance data file 26, and records the contents of each record in the transmitted temporary file. In addition, the driving speed is calculated from the vehicle speed pulse, and the rotational speed is calculated from the rotational speed pulse and similarly recorded in the new records of the performance data file 26. The driver takes breaks and refuels as needed during the above-mentioned work. When taking a break, the driver taps the break button 415 on the initial screen of the in-vehicle device application. This changes the status variable to "5", and this value is reflected in the information sent to the management server 1 by the data transmission sub 432. The same applies to refueling and car washing; tapping the respective buttons 411 to 419 changes the status variable, and the changed information is sent to the management server 1. Therefore, the value of the status variable at that time is recorded in the "Work Status" field of the performance data file 26. Meanwhile, the management staff of the transportation company log in to the management server 1 by operating the management terminal 3. Then, they click the task selection button 311 on the initial management application screen to display the task selection screen and select a task. After that, they display one of the management screens and perform transportation management. For example, to check the status of the three elements of the digital tachograph for a specific task in the past, they click the three-element viewing button 312 to display the three-element viewing screen shown in Figure 16. Also, to perform an eco-evaluation for the selected task, they click the eco-evaluation button 313 to display the eco-evaluation screen shown in Figure 18. Furthermore, when primarily managing operations on the day of work, a specific driver is selected on the work selection screen, and the date is set to "Today." Then, for example, the diagnosis / work management button 314 is clicked to display the diagnosis / work management screen shown in Figure 17. When performing safety management, the safety management button 315 is clicked to display the safety management screen shown in Figure 19. In these cases, the voice notification button 338 (Figure 17) is clicked to inform the driver via voice that there is an abnormality, or the hazard notification button 353 is clicked to inform the driver via voice that a hazardous area is approaching, as appropriate. In this manner, the driver performs daily operational tasks, and the manager manages operations using the management terminal 3. When the vehicle returns to the depot, the driver taps the task completion button 419 on the main screen of the in-vehicle device on the general-purpose terminal 4. This executes a task completion module that terminates access to the management server 1 (logs off), stores the backup file in the storage unit of the general-purpose terminal 4, and then closes the in-vehicle device application. After that, the driver removes the general-purpose terminal 4 from the terminal holder 741 and stores it in the designated storage location. For the next task, the driver reattaches the general-purpose terminal 4 to the terminal holder 741. Note that removing and attaching the general-purpose terminal 4 is not mandatory, and if the same vehicle is to be used for the next task, the general-purpose terminal 4 may be left attached. In the above operation, the backup file stored in the memory unit 2 of the general-purpose terminal 4 similarly records all the contents recorded in the temporary file during a day or a single business operation. The backup file is referenced or copied as needed for vehicle operation management. For example, if actual data is not sent to the management server 1 due to some communication trouble, the data for that time period is copied from the backup file and recorded in the actual data file 26. According to the vehicle operation management system of the embodiment described above, the in-vehicle unit consists of a speed data acquisition unit 5 and a general-purpose terminal 4, with the general-purpose terminal 4 handling the main functions, such as transmitting speed data to the management terminal 3. Since the general-purpose terminal 4 is a smartphone or tablet PC, it is inexpensive and can be used for other purposes as well, so the cost of introducing the system can be significantly lower than conventional systems. In addition, the speed data acquisition unit 5 has a simple configuration that only collects signals from the drive system sensors 8 and other in-vehicle equipment and transfers them to the general-purpose terminal 4, making it very inexpensive. In this respect as well, the introduction cost of the system in this embodiment is low. As mentioned above, input ports F to H of the speed data acquisition unit 5 are unused. If changes in laws, administrative guidance, or other environmental changes necessitate the management of other items in the digital tachograph system, the new data from the sensors in the vehicle will be recorded in the actual data file 26 of the storage unit 2 simply by connecting the new data to any of the available input ports. Therefore, by appropriately configuring the viewing program on the management server 1, the management of other items can also be easily performed. Thus, the system in this embodiment is simple and low-cost in terms of expandability. Furthermore, when consolidating inputs from other devices, it is possible to configure the system to perform this process on the general-purpose terminal 4 without going through the speed data acquisition unit 5. In this case, signals from each device would be connected to the general-purpose interface input terminals of the general-purpose terminal 4 using appropriate conversion cables. However, the number of general-purpose interface connector terminals on the general-purpose terminal is limited, and considering its portability, the number is small. In the case of USB, a tree configuration is possible, but this presents the problem of cumbersome cables. If the speed data acquisition unit 5 is provided with a sufficient number of input ports, these problems can be avoided, and the system can easily accommodate an increase in the types of data. Furthermore, the general-purpose terminal 4 functions as a transit point for data transfer from the speed data acquisition unit 5 and is configured not to perform computational processing that would place a heavy load on it. In other words, in this embodiment, the calculation of instantaneous speed from the vehicle speed pulse and the calculation of rotational speed from the rotational speed pulse are performed by a program on the management server 1 (performance data registration program), not by the general-purpose terminal 4. As a result, the data transfer speed is not slowed down, and rapid registration of performance data is possible. Since the general-purpose terminal 4 transfers data via a mobile communication network such as a mobile phone line or wireless LAN, data transfer tends to be slower compared to a wired connection. In this embodiment, this point is taken into consideration, and the load on the general-purpose terminal 4 during data transfer is minimized as much as possible. For this reason, the calculation of driving speed from the vehicle speed pulse and the calculation of rotational speed from the rotational speed pulse are performed by the management server 1. From a similar viewpoint, it is also possible that the contents of temporary files for backup are not stored on the general-purpose terminal 4. However, the present invention does not exclude the possibility of performing calculations to calculate driving speed and rotational speed on the general-purpose terminal 4. Furthermore, if instantaneous speed and rotational speed can be obtained as absolute values ​​from a pre-installed device (ECU) within the vehicle, calculation processing on the management server 1 becomes unnecessary. Furthermore, in this embodiment, the general-purpose terminal 4 is held in the vehicle by the terminal holder 741 to prevent it from falling during driving. The terminal holder 741 has a general-purpose interface connector terminal that contacts the general-purpose interface input terminal of the general-purpose terminal 4 when attached. Therefore, by attaching a general-purpose interface cable to the general-purpose interface connector terminal of the terminal holder 741 and connecting it to the speed data acquisition unit 5 in advance, speed data can be acquired into the general-purpose terminal 4 simply by attaching it to the terminal holder 741. This makes it very easy to use. The terminal holder 741 may also be a cable-integrated type with a general-purpose interface cable extending from the general-purpose interface connector terminal. In the system of this embodiment, a vehicle is selected in the business start module 42 of the in-vehicle device application, and the vehicle ID of the selected vehicle is recorded in the business information file 25 on the management server 1. When each piece of information is viewed on the management terminal 3, the vehicle information is also displayed, so it is possible to confirm which vehicle was used to perform the work. The above point is particularly important in relation to the fact that the system of this embodiment is configured with a general-purpose terminal 4 to form the digital tachograph in-vehicle device. Adopting a general-purpose terminal 4 has the effect of reducing the cost of the system as described above, but another significance is that it can be attached to different vehicles. For example, one general-purpose terminal 4 may be exclusively lent to one driver, and if the vehicle that the driver is driving changes, the general-purpose terminal 4 may also be attached to the new vehicle. In this operation, the driver using the general-purpose terminal 4 is the same, but the data source of speed data (i.e., the vehicle) is different each time. In this case, in order to manage not only the driver's driving skills but also the characteristics of the vehicle (for example, the cooling temperature of a refrigerated storage unit), the vehicle needs to be identified. In conventional systems, the digital tachograph onboard unit is dedicated to the unit and is fixed to the vehicle (not detachable), so the ID of the digital tachograph onboard unit is the same as the vehicle ID. In other words, there is always a fixed one-to-one relationship between the ID of the speed data transmission source and the vehicle. Therefore, it is sufficient to manage only the ID of the digital tachograph onboard unit, and there is no need to manage the vehicle ID separately from the management of the digital tachograph onboard unit ID. On the other hand, in the system of this embodiment, the general-purpose terminal 4 can be installed in various vehicles, which is an advantage, so it is desirable to identify which vehicle it is installed and used in, in order to enable detailed management according to the characteristics of the vehicle. The business start module 42 and business registration program 12 in this embodiment are significant because they enable such detailed management according to the characteristics of the vehicle. For example, by setting a standard refrigeration temperature for each vehicle and recording it in the vehicle information file 22, the refrigeration temperature during operation can be checked for each vehicle at the management terminal 3. Next, a vehicle operation management system of the second embodiment will be described. Figure 20 is a schematic diagram of the main parts of the vehicle operation management system of the second embodiment. The system of the second embodiment differs in the method of data transmission and reception between the speed data acquisition unit 5 and the general-purpose terminal 4. That is, in the second embodiment, the speed data acquisition unit 5 and the general-purpose terminal 4 transmit and receive data using short-range wireless communication. Specifically, as shown in Figure 20, the general-purpose terminal 4 is equipped with a short-range wireless receiver 400 of the general-purpose interface standard, and the speed data acquisition unit 5 is equipped with a short-range wireless transmitter 54 of the same general-purpose interface standard as the short-range wireless receiver 400 of the general-purpose terminal 4. Typically, infrared communication or Bluetooth (a registered trademark of Bluetooth SG Corporation) is used as the short-range wireless transmission standard. Most commercially available smartphones and portable computers are equipped with both of these wireless transceivers as interfaces. The speed data acquisition unit 5 may be equipped with short-range wireless transmitters of both standards, but it is sufficient to be equipped with either one, for example, a short-range wireless transmitter 54 that transmits data via Bluetooth. The short-range wireless transmitter 54 replaces the output unit in the first embodiment and outputs the data output from the output processor using a protocol and radio waves in accordance with the Bluetooth standard. Furthermore, Bluetooth is more suitable for the system of this embodiment than infrared communication (IrDA). In the case of infrared communication, the transmitter and receiver must be facing each other and close together, but with Bluetooth, this is not necessary, and transmission and reception are possible even when they are somewhat far apart compared to infrared communication. As can be seen from Figure 2, in the configuration as an in-vehicle device, both the speed data acquisition unit 5 and the general-purpose terminal 4 are often mounted on the dashboard, and it is often difficult to mount them facing each other. If there is a standard other than Bluetooth that allows transmission and reception without facing each other, it can be suitably adopted. Furthermore, in the case of a configuration that uses infrared communication for transmission and reception, for example, it is preferable to use an L-shaped rod-shaped member (antenna) as the wireless transmitter of the speed data acquisition unit 5, and to position the tip of the member close to and facing the wireless receiver of the general-purpose terminal 4. Except for the difference in the method of sending and receiving data, this is the same as the first embodiment. Therefore, the explanation will be omitted. In the second embodiment, since the in-vehicle device is made up of a general-purpose terminal 4, the cost of introducing the system can be reduced, and the general-purpose terminal 4 is not likely to fall off while driving, which is preferable. Furthermore, in the second embodiment, speed data and the like are sent and received by wireless communication, so compared to the first embodiment, there is no unsightly appearance due to exposed cables, and the interior of the vehicle does not become cluttered. Furthermore, in the first embodiment, the terminal holder 7 must have a connector terminal 76 positioned to correspond to the general-purpose interface input terminal (USB terminal) of the general-purpose terminal 4, thus making it a dedicated holder for the general-purpose terminal 4. While such holders (car mounts for smartphones and tablet PCs) are commercially available from various companies, if there is no connector terminal or external USB terminal (or if their positions are different), it is necessary to develop a new dedicated holder. In the second embodiment, there is no need to develop a new dedicated terminal holder 7. From the perspective of the system's implementer, there is no need to purchase a new dedicated terminal holder 7. These points are also advantages of the second embodiment. Although not explicitly stated, in each of the above embodiments, it is assumed that one general-purpose terminal 4 is used exclusively by one driver. However, this is not essential in the applied invention, and it is possible that multiple drivers may use one general-purpose terminal 4. In this case, it is preferable for the in-vehicle application to include the terminal ID as internal configuration information. The terminal ID is automatically generated and recorded as configuration information when the in-vehicle application is installed. The business start module 42 is programmed to send the terminal ID along with the driver ID when it sends the driver ID to the management server 1. The business information file 25 on the management server 1 also records the terminal ID information of the terminal used in each business. This is preferable because it allows the system to determine which general-purpose terminal 4 to retrieve the backup file from when it is necessary to refer to it. In the vehicle operation management systems of each of the above embodiments, the three-element data acquired from the speed data acquisition unit 5 and recorded in the performance data file 26 of the storage unit 2 via the general-purpose terminal 4 and management server 1 must be in a state that prevents tampering. This is in line with the guidance of the Ministry of Land, Infrastructure, Transport and Tourism. Technically, the contents of the temporary file are deleted on the general-purpose terminal 4 without external manipulation, so tampering is impossible. As for backup files, they should be stored in the storage unit on the general-purpose terminal 4 as an immutable file format, or the backup files themselves should not be left on the general-purpose terminal 4. In addition, the performance data file 26 of the storage unit 2 should also be an immutable file as a master file, except for the addition of records during business operations. Although not explicitly stated, signals from door sensors, etc., may be CAN interface signals, and the signals input to the speed data acquisition unit 5 may also be CAN interface signals. In this case, the in-vehicle application on the general-purpose terminal 4 may convert the data appropriately based on the CAN interface and send it to the management server 1. Furthermore, the signal input to the speed data acquisition unit 5 may also be a signal from an ETC onboard unit. Some ETC onboard units currently on the market are equipped with external output terminals, and it is possible that the signal line from such an ETC onboard unit is connected to the speed data acquisition unit 5 and data is acquired. As an example of use, it is conceivable that the data from the ETC onboard unit could be used to determine whether or not a vehicle has entered a highway, and the speed limit value for safety management could be changed accordingly. In addition, the data from the ETC onboard unit can also be used for managing the toll fees (expense management) for toll roads such as highways. Furthermore, in each of the embodiments described above, the contents of the performance data file 26 may be made viewable on the general-purpose terminal 4 inside the vehicle. Specifically, a new viewing mode is provided in the in-vehicle device application, allowing the user to select this mode. In viewing mode, the in-vehicle device application is programmed to display the contents of the three-element data recorded in the performance data file 26, transmitted from the general-purpose terminal 4, in the same way as in the case of the management terminal 3. Drivers can check the status of the three elements of the digital tachograph and the status of eco-evaluation on the general-purpose terminal 4 during their work, enabling them to make a conscious effort to drive more appropriately, resulting in a system that is more suitable for safe and environmentally conscious operation. Furthermore, from the perspective of leaving a record of vehicle operation on the vehicle, a configuration is also conceivable in which the contents of the performance data file 26 are returned to the speed data acquisition unit 5 via the general-purpose terminal 4 for storage, or in which the performance log is stored on the speed data acquisition unit 5. Specifically, the speed data acquisition unit 5 is equipped with a fixed storage unit such as RAM to enable the storage of the performance log. In the latter case, the output processor 53 within the speed data acquisition unit 5 is given a function to store the data from each output port directly as the performance log in the fixed storage unit. For example, in the event of an accident, the record of operation left on a device fixed to the vehicle may be important as evidence. In this case, by analyzing the performance log stored in the fixed storage unit, the speed and acceleration at the time of the accident can be calculated and used as evidence related to the accident. Therefore, this could be a recommended embodiment from a safety management perspective. In the above embodiment, the data included in the performance data file 26 included the three elements of the digital tachograph, but it is possible that the three elements of the digital tachograph may not be included. For example, it is possible that only the instantaneous speed at each time point is stored in the performance data file 26, and only the time and instantaneous speed are viewable. In this case, the time up to a certain time point (driving time) can be calculated and checked separately only when necessary. 1 Management Server 11 Performance Data Registration Program 13 Three-Element Viewing Program 14 Diagnosis / Work Understanding Program 15 Eco Evaluation Program 16 Safety Management Program 2 Storage Unit 26 Performance Data File 3 Management Terminal 4 General Purpose Terminal 43 Data Storage Module 400 Short-Range Wireless Receiver 5 Speed ​​Data Acquisition Unit 51 Input Unit 52 Output Unit 521 USB Terminal 53 Output Processor 54 Short-Range Wireless Transmitter 6 Internet 7 Terminal Holder 76 Connector Terminal 8 Sensor

Claims

1. A vehicle operation management system comprising a tachograph onboard unit, a management server, and a storage unit, wherein the tachograph onboard unit consists of a terminal which is a smartphone or tablet PC and a signal collection unit which collects vehicle information and transmits it to the smartphone or tablet PC terminal, the smartphone or tablet PC terminal is capable of accessing the management server via a packet communication system, the vehicle information collected by the signal collection unit includes a vehicle speed pulse signal, the smartphone or tablet PC terminal transmits the vehicle information to the management server via a packet communication system, the management server has a program implemented which processes the vehicle speed pulse signal included in the vehicle information transmitted from the smartphone or tablet PC terminal and stores the mileage, time, and speed in the storage unit, and the stored mileage, time, and speed are transmitted from the management server to an office terminal via the internet and can be viewed on the office terminal.

2. [Corrected] A vehicle operation management system that manages at least the speed, distance traveled, and time of a vehicle, comprising a tachograph on-board unit mounted on the vehicle, a management server, and a storage unit, wherein the tachograph on-board unit consists of a speed data acquisition unit connected to a speed sensor provided in the vehicle's drive system, and a general-purpose terminal connected to the speed data acquisition unit, the general-purpose terminal is a smartphone or a general-purpose portable computer other than a smartphone that can access the management server via a network, the general-purpose terminal has application software for on-board units installed, which includes a data storage module that transmits speed data at each point in the operation acquired by the speed data acquisition unit to the management server at each transmission cycle and stores it in the storage unit, the management server accepts access from general-purpose terminals via a network and access from management terminals, the management server has vehicle operation management server software implemented, which includes a performance data registration program, and the storage unit stores performance data files, the performance data registration program is a program that records and registers speed data transmitted from the general-purpose terminal by the data storage module in the performance data file, the vehicle operation management server software includes a three-element viewing program, The three-element viewing program is a program for displaying three-element data—distance traveled, travel time, and travel speed at each point in time during a day or a single operation—on a management terminal based on speed data recorded in the performance data file. The vehicle is equipped with a terminal holder that holds a general-purpose terminal, and the terminal holder is designed to hold the general-purpose terminal detachably and to prevent it from falling during operation. The speed data acquisition unit and the general-purpose terminal are connected by a general-purpose interface cable, enabling the transmission and reception of speed data, or the transmission and reception of speed data is enabled by short-range wireless communication.

3. [After correction] The vehicle operation management system according to claim 2, characterized in that the speed data acquisition unit is provided with a general-purpose interface output terminal, the terminal holder is provided with a general-purpose interface connector terminal that contacts the general-purpose interface input terminal of a general-purpose terminal when mounted, and the general-purpose interface connector terminal is connected to the general-purpose interface output terminal of the speed data acquisition unit by a general-purpose interface cable.

4. The vehicle operation management system according to claim 2, characterized in that the general-purpose terminal is equipped with a short-range wireless receiver that receives information by short-range wireless communication using a general-purpose interface standard, and the speed data acquisition unit is equipped with a short-range wireless transmitter that wirelessly transmits speed data using the same general-purpose interface standard as the short-range wireless receiver of the general-purpose terminal.

5. The vehicle operation management system according to claim 4, characterized in that the short-range wireless transmitting unit and the short-range wireless receiving unit are capable of transmitting and receiving without facing each other.

6. The vehicle belongs to a transportation business company that operates vehicles as part of its business, and the transportation business company has multiple vehicles, each vehicle being equipped with the speed data acquisition unit and the general-purpose terminal, and the storage unit stores a vehicle information file that records vehicle information including the vehicle ID of each vehicle belonging to the transportation business company, and a business information file that records information about the business, and the vehicle operation management server software includes a business registration program, and the in-vehicle device application software includes a business start module that is executed when the business is performed, and the business start module is a program module that takes information to identify the vehicle ID of the vehicle to be used in the business for the day or for a single business as input and sends it to the management server, and records the vehicle ID in the business information file by the business registration program, and the three-element viewing program is a program that, when the three-element data is displayed on the management terminal, obtains information about the vehicle that was the data source of the three-element data from the vehicle information file and displays it together, characterized in that the vehicle operation management system according to any one of 2 to 5.

7. The vehicle operation management system according to any one of 2 to 6, characterized in that the speed data acquired by the speed data acquisition unit is a vehicle speed pulse, and the actual data registration program implemented in the management server is a program that converts the vehicle speed pulse to calculate the driving speed.

8. The vehicle operation management system according to any one of claims 2 to 7, characterized in that the speed data acquisition unit has an input section into which signals from other devices attached to the vehicle other than the speed sensor are input, the speed data acquisition unit outputs data based on signals input from other devices along with the speed data to the general-purpose terminal, the data storage module aggregates the data based on signals input from other devices and the speed data and transmits it to the management server, and the performance data registration program is a program that records data based on signals input from other devices together with the speed data in a performance data file.

9. A vehicle operation management system that manages the speed of a vehicle, comprising a tachograph on-board unit mounted on the vehicle, a management server, and a storage unit, wherein the tachograph on-board unit consists of a speed data acquisition unit connected to a sensor provided in the vehicle's drive system and a general-purpose terminal connected to the speed data acquisition unit, the general-purpose terminal is a smartphone or a general-purpose portable computer other than a smartphone that can access the management server via a network, the general-purpose terminal has application software for on-board units installed, which includes a data storage module that transmits speed data acquired by the speed data acquisition unit to the management server and stores it in the storage unit, the management server accepts access from general-purpose terminals and management terminals via a network, the management server has vehicle operation management server software implemented which includes a performance data registration program, and the storage unit stores performance data files, the performance data registration program is a program that records and registers speed data transmitted from the general-purpose terminal by the data storage module in the performance data file, the vehicle operation management server software includes a viewing program, the viewing program is a program for displaying the speed data recorded in the performance data file on the management terminal, A vehicle operation management system characterized in that a terminal holder for holding a general-purpose terminal is fixed to the vehicle, the terminal holder is capable of detachably holding the general-purpose terminal and preventing it from falling off while the vehicle is in motion, and the speed data acquisition unit and the general-purpose terminal are connected by a general-purpose interface cable, enabling the transmission and reception of speed data, or enabling the transmission and reception of speed data by short-range wireless communication.