JP2023178799A - Operation management system and operation management server - Google Patents

Abstract

To provide an operation management system useful for reducing the cargo waiting time in each vehicle which transports cargo.SOLUTION: There are provided: an on-vehicle unit 11 that can be mounted on a vehicle 10; a server 20 which manages operation states of vehicles; an office PC 31 that can be used by a transportation business operator: and a cargo owner PC 41 that can be used by a cargo owner. The server 20 detects, from a notification from the on-vehicle unit 11, that a vehicle has arrived at a cargo owner area and has shifted to a cargo waiting state, and notifies each of the office PC 31 and the cargo owner PC 41 about information 21 on the cargo waiting state. When the server 20 receives cargo waiting release information from the on-vehicle unit 11, the server notifies each of the office PC 31 and the cargo owner PC 41 about the cargo waiting release. When the server 20 receives cargo waiting release information from the cargo owner PC 41, the server notifies each of the on-vehicle unit 11 and the office PC 31 about the cargo waiting release.SELECTED DRAWING: Figure 1

Description

The present invention relates to a traffic management system and a traffic management server that can be used by transportation companies to manage vehicles that transport customers' luggage.

A transportation company that uses trucks and other vehicles to transport cargo for various customers loads the cargo onto the vehicle at a certain loading point according to the instructions of the customer, drives the vehicle to a designated unloading point, and unloads the cargo. When the vehicle arrives at the destination, the cargo is unloaded from the vehicle and handled as if it were to be handed over to the shipper.

In reality, each driver in charge of driving each vehicle generally drives the vehicle, loads the vehicle, and unloads the vehicle according to an operation plan created in advance.

On the other hand, even if the vehicle arrives at the designated loading point, if the customer is not yet ready, the driver will not be able to start loading immediately and will be left waiting. . The same applies when the vehicle arrives at a designated unloading point. Further, when a large number of trucks waiting for cargo are lined up near a loading point or unloading point, causing a traffic jam, each vehicle is placed in a waiting state.

For example, Patent Document 1 discloses an arrival time notification system that aims to reduce the waiting time near the destination by notifying passengers and managers of the arrival time in consideration of the waiting time near the destination. ing. This arrival time notification system includes an onboard device, a receiving terminal, a management device, and a server. In addition, the on-vehicle device acquires the position information of the own vehicle, measures the waiting time of the own vehicle and the waiting time of surrounding vehicles, and sends the position information of the own vehicle and the waiting times of the own vehicle and surrounding vehicles to the server. It has the function to send to. The server has a function of transmitting a corrected arrival time obtained by adding the area waiting time within the specified area to the arrival time to at least one of the receiving terminal or the management device.

JP 2021-15456 Publication

By the way, at present, the work hours of a truck driver who works for a transportation company, etc. include work hours such as loading and unloading in addition to driving time. Further, the time when the vehicle being driven by the driver is waiting for cargo is also included in the truck driver's work hours. Additionally, if the work hours increase due to waiting for cargo, there is a concern that each driver's overtime hours will increase more than previously expected. In addition, if the cost caused by the waiting state is not clarified when the shipping company claims the cost from the shipper, there is a concern that problems will arise between the parties as to how to bear this cost. .

On the other hand, in the technology disclosed in Patent Document 1, the onboard device measures the waiting time of the own vehicle and the waiting times of surrounding vehicles, and transmits the position information of the own vehicle and the waiting times of the own vehicle and the surrounding vehicles to the server. can. However, a manager on the transport company side or a manager on the shipper side cannot know the status of each vehicle in real time even if the vehicle is actually in a waiting state.

Therefore, it has not been possible for the manager of the shipper or the transport company to take any action in real time with respect to the vehicle in the waiting state to quickly resolve the waiting state. In addition, even if data such as conventional daily reports on vehicle operation performance are statistically analyzed, it is difficult for both the transport company and the shipper to accurately understand the actual situation and causes of waiting for cargo. This was difficult, and no fundamental measures could be taken to reduce the amount of time each vehicle was waiting for cargo.

The present invention has been made in view of the above-mentioned circumstances, and its purpose is to provide a traffic management system and a traffic management server that are useful for reducing the waiting time of each vehicle that transports luggage.

The above object according to the present invention is achieved by the following configuration.

An on-vehicle device that can be mounted on a vehicle that transports cargo;
a server capable of managing at least the operating status of the vehicle;
a company terminal that can be used by a transportation company that manages the vehicle;
a shipper terminal that can be used by a shipper of cargo transported by the vehicle;
Equipped with
The server is
Detects that the vehicle to be managed has arrived at the loading or unloading location specified by the shipper and has entered a waiting state, and sends information representing the waiting state to the vendor terminal and the shipper's terminal. a waiting notification section that notifies each person;
When waiting release information is received from the on-vehicle device, the on-vehicle device notifies the above-mentioned vendor terminal and the above-mentioned shipper terminal of cargo-waiting release, respectively, and when receiving the cargo-waiting release information from the above-mentioned shipper terminal, the on-vehicle a cargo waiting release notification unit that notifies the cargo container and the aforementioned vendor terminal of cancellation of the cargo waiting list, respectively;
A traffic management system with

a vehicle management unit that acquires information on the current position of a vehicle transporting cargo and information representing a cargo waiting state of the vehicle from an on-board device mounted on the vehicle;
a customer identification unit that identifies a customer based on information acquired from the on-vehicle device;
a release instruction receiving unit capable of receiving an external signal instructing release of the cargo waiting state;
a cargo waiting time measurement unit that records the cargo waiting time from when the vehicle enters the cargo waiting state until the vehicle is released from the cargo waiting state;
an information storage unit that stores information on the measured waiting time in a state where it is linked to a corresponding customer;
an aggregation unit that aggregates and outputs the information stored in the information storage unit for each customer;
An operation management server equipped with

According to the traffic management system and traffic management server of the present invention, it is possible to reduce the waiting time of each vehicle that transports luggage. In other words, the server of the transportation management system notifies the carrier terminal and the shipper terminal of the information on the waiting state, so the administrator of the transport company and the shipper can check the occurrence of the waiting state in real time. This will enable accurate understanding and take necessary measures to quickly resolve the backlog.

In addition, the operation management server of the present invention aggregates and outputs the results of measuring the waiting time actually occurring in each vehicle for each customer, so that the administrator of the transportation company and the administrator of the shipper can It is now possible to accurately analyze the trends and causes of backorders, reduce the frequency and duration of backorders, and take necessary measures to prevent backorders from occurring. Become.

The present invention has been briefly described above. Furthermore, the details of the present invention will be further clarified by reading the mode for carrying out the invention (hereinafter referred to as "embodiment") described below with reference to the accompanying drawings. .

FIG. 1 is a block diagram showing a configuration example of a traffic management system according to an embodiment of the present invention. FIG. 2 is a block diagram showing an example of the configuration of the on-vehicle device. FIG. 3 is a block diagram showing an example of the configuration of a server. FIG. 4 is a sequence diagram showing a part of an example of the operation of the traffic management system. FIG. 5 is a sequence diagram showing a portion of an example of the operation of the traffic management system. FIG. 6 is a sequence diagram showing a part of an example of the operation of the traffic management system. FIG. 7 is a front view showing an example of the structure of the daily attendance report.

Specific embodiments of the present invention will be described below with reference to each figure.

<System overview>
FIG. 1 is a block diagram showing a configuration example of a traffic management system 100 according to an embodiment of the present invention.

When a transport company uses a truck vehicle 10 to transport cargo requested by a shipper's business office 40, the truck driver first drives the truck vehicle 10 from the parking lot of the transport company's business office to the location specified by the shipper. The vehicle will be operated to the shipper's business location at the loading point. Next, the cargo entrusted by the cargo owner is loaded onto the truck vehicle 10 at the cargo owner's office. When the loading work is completed, the driver drives the truck vehicle 10 to the shipper's business location as the destination. When the cargo arrives at the destination shipper's office, the cargo is unloaded from the truck vehicle 10 and delivered to the shipper.

However, even if the truck vehicle 10 arrives near the loading point (shipper's area), it may not be possible to start the loading work immediately due to the circumstances of the shipper or due to traffic congestion of other vehicles waiting for work. This is a "waiting for cargo" situation, and the driver has to wait until the cargo is ready to be loaded, which places a heavy labor burden on the driver. The same applies to unloading.

In the traffic management system 100 shown in FIG. 1, each truck vehicle 10 is equipped with an on-vehicle device 11. This on-vehicle device 11 has a function of detecting the state of cargo waiting in the truck vehicle 10, a function 12 of recording the waiting time of cargo, and the like. Further, the on-vehicle device 11 can communicate with the server 20 by wireless communication.

An office PC (personal computer) 31 having a function for managing the operation of each truck vehicle 10 is arranged in the office 30 of the transportation company. Further, a shipper's PC 41 having a function for the shipper to manage the transportation status of the cargo is disposed within the shipper's office 40. The office PC 31 and the shipper's PC 41 can each communicate with the server 20 via the Internet, for example.

The server 20 has a function of transmitting a notification 21 of the waiting state to each of the office PC 31 and the shipper's PC 41 when it is detected that the truck vehicle 10 is in a waiting state through communication with the onboard device 11. have.

Further, when the cargo waiting release notification 22 is transmitted from the consignor PC 41, the server 20 transmits the cargo waiting cancellation notification 22 to the on-vehicle device 11 and the office PC 31, respectively. Furthermore, when the on-vehicle device 11 transmits the notice 22 of release of cargo waiting due to detecting the running of the own vehicle, the server 20 transmits the notice 22 of release of cargo waiting to the office PC 31 and the consignor PC 41, respectively.

The notification 21 of the waiting state and the notification 22 of cancellation of the waiting state are reflected on the screen display of the office PC 31 by the waiting vehicle display function 32. Therefore, the manager of the office 30 of the transportation company can grasp the waiting status of each truck vehicle 10 in real time from the screen display of the office PC 31.

Further, the notification 21 of the waiting state is reflected on the screen display of the consignor's PC 41 by the waiting vehicle display function 42. Therefore, the manager of the shipper's office 40 can grasp the waiting status of each truck vehicle 10 in real time from the screen display of the shipper's PC 41. Further, the manager of the shipper's office 40 can issue an instruction to cancel the cargo waiting state by inputting information on the screen of the shipper's PC 41. This instruction is sent via the server 20 to the office PC 31 and the on-vehicle device 11 as a notice 22 of cancellation of the waiting list.

Therefore, the manager of the transportation company's office 30 and the manager of the shipper's office 40 can have a common understanding of the waiting status of the truck vehicle 10 by using the common screen display on the office PC 31 and the shipper's PC 41. can.

The daily report output function 33 of the office PC 31 outputs a daily report in which "waiting information" is written by aggregating data recorded by the waiting time recording function 12 or data recorded on the server 20. I can do it. This daily report allows each manager to obtain more accurate information regarding the waiting state occurring in each truck vehicle 10. This makes it easier for managers to investigate the cause and take fundamental measures to reduce truck drivers' waiting time.

Note that the cargo waiting time recording function 12 may be implemented in at least one of the on-vehicle device 11 and the server 20. Further, the function of counting the waiting time may be placed on the server 20 or on the office PC 31.

The on-vehicle device 11 necessary to configure the traffic management system 100 can be realized by adding special functions to a driving recorder such as a digital tachograph that is generally mounted on truck vehicles. Of course, it is also possible to use an on-vehicle device other than the digital tachograph.

FIG. 2 is a block diagram showing an example of the configuration of the on-vehicle device 11. As shown in FIG.
The onboard device 11 shown in FIG. 2 includes a vehicle speed detection section 11a, a GPS receiver 11b, a display section 11c, an operation section 11d, an RTC 11e, a control section 11f, a nonvolatile memory 11g, a volatile memory 11h, a memory card IF 11i, and a wireless communication 11j, and a memory card 15.

The vehicle speed detection section 11a inputs a vehicle speed pulse signal output from the vehicle side, and converts it into a signal suitable for processing of vehicle speed detection in the control section 11f.
The GPS (Global Positioning System) receiver 11b can receive radio waves from a plurality of GPS satellites and calculate the latitude/longitude representing the current position of the host vehicle based on the time of the received signals.

The display unit 11c is disposed at a position that is easily visible to the driver, and has the ability to display information such as guidance information, numerical values, and time necessary for input operations by the driver.

The operation unit 11d is arranged at a position that is easy for the driver to operate, and has a large number of buttons that can accept input operations from the driver. These buttons include a cargo waiting button that is operated by the driver when the own vehicle is in a "load waiting" state.

The RTC (Real Time Clock) 11e is composed of a semiconductor integrated circuit (IC) and has a clock function to generate information on the current date, day of the week, and time (hours, minutes, and seconds) and to measure time. ing.

The control unit 11f is constituted by an electronic circuit mainly including a microcomputer, and executes various controls for realizing the functions required for the on-vehicle device 11 by executing a program installed in advance. Specifically, it includes the following functions (1) to (6).

(1) Function to periodically acquire and record operation information of own vehicle, including current position, current time, vehicle speed, etc. (2) Function to detect "waiting for cargo" status (3) Function to monitor the state of own vehicle Function to detect release of "waiting for cargo" (4) Function to notify server 20 of "waiting for cargo" status (5) Function to receive from server 20 an instruction to release "waiting for cargo" (6) Status of "waiting for cargo" A function to measure and record the start and end times, or the length of time in the "waiting for cargo" state.

The nonvolatile memory 11g holds programs executable by the computer of the control unit 11f and various constant data necessary for realizing various functions of the on-vehicle device 11. Additionally, various data that needs to be saved can be written and registered.

The volatile memory 11h is used to temporarily hold various data generated by the control unit 11f during operation.
The memory card IF (interface) 11i has a pseudo slot that can removably hold the memory card 15, and can connect the memory card 15 to the microcomputer of the control unit 11f.

The wireless communication unit 11j has a wireless communication function compatible with communication standards such as LTE (Long Term Evolution), and establishes a wireless communication line between the own vehicle and a wireless base station provided by a mobile communication carrier. can be established.

The memory card 15 has a built-in nonvolatile memory, and can register and hold information identifying the driver operating the own vehicle, information identifying the vehicle, driving record data generated by the onboard device 11, and the like.

FIG. 3 is a block diagram showing a configuration example of the server 20. As shown in FIG.
The server 20 is configured by a computer system installed, for example, in a predetermined data center. The server 20 of this embodiment includes various functions shown in FIG. 3 necessary for controlling the entire operation management system 100.

As shown in FIG. 3, the server 20 includes a communication section 20a, a vehicle management section 20b, an operation record DB 20c, a waiting management section 20d, a waiting time measuring section 20e, a waiting notification section 20f, a waiting cancellation notification section 20g, and an administrative section. It has the functions of a warehouse management section 20h, a shipper management section 20i, and a data aggregation section 20j.

The communication unit 20a is connected to a communication network 23. The server 20 can be connected to a public communication network such as the Internet via the communication unit 20a and the communication network 23, and can communicate with the onboard equipment 11 mounted on each truck vehicle 10, the office PC 31, and the shipper's PC 41. Communication lines can be connected between each.

The vehicle management section 20b performs data communication with the onboard equipment 11 mounted on each truck vehicle 10 via the communication section 20a, and can acquire operation data representing the operation status of each truck vehicle 10 at each point in time. This operation data includes information such as an ID that identifies the vehicle and the onboard device 11, date and time, the current location of the vehicle, the current vehicle speed, and the current state ascertained by the onboard device 11.

The operation record DB (database) 20c has a function of storing and storing the operation data acquired from each vehicle by the vehicle management section 20b, distinguishing each vehicle and each shipper.
The cargo waiting management unit 20d has a function of grasping whether each truck vehicle 10 is in a waiting state and managing it.

The cargo waiting time measuring unit 20e has a function of detecting and recording the start time and end time when each truck vehicle 10 enters the cargo waiting state, or measuring the length of time in the cargo waiting state. are doing. Information on the waiting time measured by the waiting time measuring unit 20e is written to the operation record DB 20c for each vehicle. In that case, the operation record DB 20c stores information on the time of the cargo waiting state in association with the shipper, together with the positional information of the place where the cargo waiting occurred.

When the cargo waiting management section 20d detects that the cargo is in a waiting state based on the information transmitted from the onboard device 11 of each truck vehicle 10, the cargo waiting notification unit 20f sends a notification 21 of the cargo waiting state to the office PC 31 and the shipper. It is transmitted to both PCs 41 respectively.

The cargo waiting release notification unit 20g transmits a notification 22 of cargo waiting cancellation when the cargo waiting state known to the cargo waiting management unit 20d is released. When the cargo waiting state is canceled based on the information received from the onboard device 11 of each truck vehicle 10, the cargo waiting release notification unit 20g sends the notification 22 of cargo waiting cancellation to both the office PC 31 and the consignor PC 41 as destinations. A notification 22 of release of cargo waiting is sent. Further, when the cargo waiting state is canceled by an instruction to cancel the cargo waiting from the shipper's PC 41, the cargo waiting cancellation notification section 20g sends the notification 22 of the cargo waiting cancellation to both the on-vehicle device 11 and the office PC 31 as destinations. Send each.

The office management unit 20h holds and manages information on web pages to be displayed on the screen of the office PC 31, information necessary for the office PC 31 to access, and information representing destinations of messages and the like. There is.

The shipper management unit 20i holds and manages information on each shipper who is a customer of the transportation company. Specifically, information representing the point of each business office designated by each shipper as a loading and unloading place and the range of its area, information on the web page to be displayed on the screen of the shipper's PC 41, and It maintains and manages the information necessary for access by users and information indicating the destination of messages, etc.

The data aggregation unit 20j divides the information accumulated in the operation record DB 20c for each shipper, totalizes the waiting time, and stores the results. The tally result of the waiting time stored by the data tallying unit 20j can be outputted upon request from the office PC 31. Further, the data aggregation unit 20j can also aggregate and output the waiting time in a predetermined daily report format.

Examples of the operation of the traffic management system 100 are shown in FIGS. 4, 5, and 6. FIG. 4 shows the operation when the cargo waiting state is canceled by an instruction from the shipper, and FIG. 5 shows the operation when the onboard device automatically cancels the waiting state.

<Operation when canceling the waiting status according to instructions from the shipper>
The operation shown in FIG. 4 will be explained below.

For example, when a truck vehicle 10 arrives at a shipper's area as shown in FIG. The arrival is detected by comparison (S10).

Here, if there are other trucks lining up and causing a traffic jam, loading or unloading operations cannot be started immediately, so the truck vehicle 10 is in a waiting state. When the driver of the truck vehicle 10 confirms that the truck is waiting for cargo and operates the "waiting for cargo button" on the operation section 11d of the onboard device 11, the onboard device 11 enters the waiting for cargo detection state in S11. If the product is not waiting for cargo, the process advances to S51 in FIG.

When the vehicle-mounted device 11 enters the cargo waiting detection state, it transmits a notification i01 of the cargo waiting state to the server 20. Further, the onboard device 11 uses the time measurement function of the RTC 11e to start recording and measuring the cargo waiting time in S12.

On the other hand, the server 20 receives the notification i01 of the waiting state from the onboard device 11 and recognizes that the corresponding truck vehicle 10 has entered the waiting state. In this case, the waiting notification unit 20f of the server 20 transmits the waiting notification i02 to each of the office PC 31 and the consignor PC 41 in S13. Further, the waiting time measuring unit 20e of the server 20 starts recording and measuring the waiting time in S14.

Upon receiving the cargo waiting notification i02 transmitted from the server 20, the shipper PC 41 displays on the screen in S15 so that it can be seen that the truck vehicle 10 to be managed is in a waiting state. Actually, a web page representing the cargo waiting state is displayed by the browser on the screen of the consignor's PC 41.

Similarly, upon receiving the waiting notification i02 transmitted from the server 20, the office PC 31 displays on the screen in S16 so that it can be seen that the managed truck vehicle 10 is in a waiting state. Actually, a web page representing the waiting state is displayed by the browser on the screen of the office PC 31.

Further, the Web page displayed by the shipper's PC 41 includes a "cancel cargo waiting" button. The shipper's administrator who operates the shipper's PC 41 can use a mouse or the like to operate the "Cancel cargo waiting" button on the screen of the web page.

When the manager on the shipper's side confirms that the cause of the cargo waiting in the corresponding truck vehicle 10 has been resolved and then operates the "Cancel cargo waiting" button, the cargo owner's PC 41 detects in S17 that there has been a cancellation input. Then, a cargo waiting release notification i03 is sent to the server 20 in S18.

When the cargo waiting release notification unit 20g of the server 20 receives the cargo waiting cancellation notification i03 from the shipper's PC 41, it transmits the cargo waiting cancellation notification i04 to each of the onboard device 11 and the office PC 31 in S19.

When the onboard device 11 receives the cargo waiting release notification i04 from the server 20, it detects it in S21 and proceeds to the process of S22. Then, in S22, the measurement of the waiting time is finished and the time is stored, and the waiting state is canceled in S23.

Furthermore, upon receiving the cargo waiting release notification i03, the server 20 proceeds to the processing from S24 to S25. Then, the waiting time measuring section 20e finishes measuring the waiting time, stores the time in the operation record DB 20c, and releases the waiting state of the corresponding truck 10 in S26.

Further, on the screen of the consignor PC 41, it is displayed in S27 that the cargo waiting state of the corresponding truck vehicle 10 has been released.
Further, upon receiving the cargo waiting release notification i04 from the server 20, the office PC 31 proceeds to the processing from S28 to S29. Then, on the screen of the office PC 31, it is displayed in S29 that the waiting state of the corresponding truck vehicle 10 has been released.

<Operation when automatically canceling the cargo waiting state by detecting vehicle movement>
The operation shown in FIG. 5 will be explained below. Note that each step S10 to S16 shown in FIG. 5 is the same as that in FIG. 4, so a description thereof will be omitted.

Since the control unit 11f of the on-vehicle device 11 constantly or periodically monitors the vehicle speed based on the vehicle speed pulse output from the truck vehicle 10 side, it can identify whether or not the own vehicle is traveling. When the vehicle-mounted device 11 detects the running of the own vehicle in S31 while the own vehicle is in the waiting state, it proceeds to the next step S32 and transmits the waiting release notification i11 to the server 20.

When the cargo waiting release notification unit 20g of the server 20 receives the cargo waiting cancellation notification i11 from the onboard device 11, it transmits the cargo waiting cancellation notification i12 to each of the shipper PC 41 and the office PC 31 in S19A.

Further, upon receiving the cargo waiting release notification i11, the server 20 proceeds to the processing from S35 to S36. Then, the measurement of the waiting time in the waiting time measuring section 20e is finished, the time is stored in the operation record DB 20c, and the waiting state of the corresponding truck vehicle 10 is released in S37.

Further, upon receiving the cargo waiting release notification i12 from the server 20, the shipper PC 41 proceeds to the processing from S38 to S39. Then, on the screen of the shipper's PC 41, a message indicating that the cargo waiting state of the corresponding truck vehicle 10 has been released is displayed in S39.

Further, upon receiving the cargo waiting release notification i12 from the server 20, the office PC 31 proceeds to the processing from S40 to S41. Then, on the screen of the office PC 31, it is displayed in S41 that the waiting state of the corresponding truck vehicle 10 has been released.

<Operations other than waiting for cargo>
The operation shown in FIG. 6 will be explained below.

The driver of the truck vehicle 10 that has arrived at the shipper's area starts loading or unloading at that location (S51). For example, when the driver operates the work start button on the operation section 11d of the onboard device 11, the onboard device 11 recognizes the start of work, and stores information such as the work start time on the memory card on the onboard device 11 along with operation record data. It can be recorded as 15 mag.

When the loading or unloading work is completed, for example, when the driver operates the work end button on the operation unit 11d, the onboard equipment 11 recognizes the end of the work in S52. Thereby, information such as the work end time can be recorded in the memory card 15 or the like on the on-vehicle device 11 together with the operation record data.

When the driver drives the truck vehicle 10 and leaves the consignor area, the onboard device 11 can recognize the departure in S53 based on the traveling speed of the own vehicle.

When the day's operation of the truck vehicle 10 is completed, the truck vehicle 10 is returned to the transportation company's office 30 by the driver. The onboard device 11 recognizes this in S54. Further, the driver performs a warehousing procedure for a predetermined on-vehicle device 11 in S55.

For example, the driver removes the memory card 15 from the onboard device 11 and reads the driving record data recorded on the memory card 15 using the office PC 31. Further, since data equivalent to the contents of the memory card 15 exists on the server 20, it is also possible to transfer the operation record data from the server 20 to the office PC 31.

The office PC 31 checks the contents of the operation record data read from the memory card 15 of the onboard device 11 or the operation record data read from the server 20 in S61, and indicates "waiting for cargo" in the operation record data of the day. Identify whether information is included. If the information indicating "waiting for cargo" is not included, the office PC 31 aggregates the operation record data, creates a normal format daily report in S62, and executes output such as printing on paper.

On the other hand, if the operation record data for the day includes information indicating "waiting for cargo," the office PC 31 will issue a normal daily report and a special daily report for waiting for cargo (daily attendance report 70 in FIG. 7). Both are created in S63 based on the operation record data, and output such as printing on paper is executed.

In S64, the office PC 31 sends an e-mail containing information on the created daily cargo waiting report and a message indicating that the cargo waiting has occurred to the person in charge on the shipper's side. Alternatively, using the server 20, the office PC 31 sends a message to reflect a message indicating that a backlog has occurred or the content of a daily report on the backlog on the web page displayed on the screen of the consignor's PC 41. do.

<Example of structure of daily attendance report>
FIG. 7 is a front view showing an example of the structure of the daily attendance report 70. A daily attendance report 70 including cargo waiting information as shown in FIG. 7 is generated and output in S63 of FIG.

The daily attendance report 70 shown in FIG. 6 includes an operation classification display column 71, a work time display column 72, a waiting time display column 73, an operation chart display column 74, a daily report information display column 75, and a waiting time display column 76 for each shipper. It is structured as a list of various information categorized into various categories.

The operation category display column 71 of the daily attendance report 70 has items for inputting information such as daily report number, crew name, vehicle name, travel time, departure date and time, arrival date and time, travel distance, operating time, and continuous operation time. ing.

In addition, in the work time display column 72 of the daily attendance report 70, each piece of information such as work type, shipper name, arrival date and time, departure date and time, and work time is entered for each work item such as loading, break, and unloading on the day. It has items to do.

In addition, the cargo waiting time display column 73 of the daily attendance report 70 displays the name of the shipper, the cargo owner's specified arrival time, the arrival time, the start date and time of the "waiting" for each location where "waiting" occurred during the vehicle operation on that day. It has items for inputting information such as the end date and time of the "waiting for cargo" and the waiting time.

In addition, the operation chart display column 74 of the daily attendance report 70 displays a chart showing the operating status of the vehicle on the day in chronological order, and a chart showing changes in status for each category such as work, rest, overtime, continuous driving, etc. in chronological order. Each has a display area.

In addition, the daily report information display column 75 of the daily attendance report 70 displays loading time, unloading time, total waiting time, break time, overtime time, late night overtime, restraint time, cumulative monthly overtime, and cumulative monthly restraint time. It has items for inputting each information.

In addition, in the cargo waiting time display column 76 for each consignor in the daily attendance report 70, the cumulative time of "waiting for cargo" that has occurred during vehicle operation on the same day or for a certain period of time is divided into categories for each consignor, and each item is entered in association with the consignor's name. It has items to do.

The information to be input into each item of the daily attendance report 70 shown in FIG. 7 may be the operation record data recorded in the memory card 15 by the onboard device 11, or the data managed by the server 20 in the operation record DB 20c or the data aggregation unit 20j. It can be generated based on
Note that the daily attendance report 70 may include temperature management information such as refrigeration/freezing in the cargo compartment of the truck vehicle 10.

Note that the present invention is not limited to the embodiments described above, and can be modified, improved, etc. as appropriate. In addition, the material, shape, size, number, arrangement location, etc. of each component in the above-described embodiments are arbitrary as long as the present invention can be achieved, and are not limited.

For example, in the operation example shown in FIG. 5, when the on-vehicle device 11 detects that the own vehicle is running in S31, it immediately cancels the "waiting for cargo" state. On the other hand, in a driving state in which it is detected in S31 that the own vehicle has moved at a speed below a certain speed within a predetermined area, the on-vehicle device 11 may be changed so as not to release the "waiting for cargo" state.

Alternatively, the state of "waiting for cargo" may be temporarily canceled by detecting the movement of the own vehicle, and if the own vehicle does not leave the predetermined area within a predetermined period of time, processing may be performed such that the state of "waiting for cargo" is returned to the state of waiting for cargo. For example, such processing is appropriate in a situation where trucks are waiting for cargo and there is a traffic jam inside the shipper's business premises.

By using the above-mentioned operation management system 100, the manager on the shipper's side and the manager on the transport company's side can grasp the actual waiting situation of the truck vehicle 10 in real time. This makes it possible to take measures to quickly eliminate the problem. As a result, the waiting time for cargo will be reduced, and the labor conditions for truck drivers can be expected to improve.

Moreover, the manager on the shipper's side and the manager on the transport company's side can have a common understanding of the actual waiting time of the truck vehicle 10. As a result, a situation is realized in which there is no problem even if the transport company charges the shipper a special charge for waiting as compensation for the waiting time that has occurred. This can be expected to reduce waiting time.

In addition, the operation management system 100 divides the results of aggregating operation record data including waiting time for each shipper and issues them in a format such as a daily attendance report 70. This makes it easier to identify the causes of backlogs and to implement fundamental measures to reduce backlogs.

Here, the features of the traffic management system and traffic management server according to the embodiments of the present invention described above are summarized and listed below in [1] to [5], respectively.
[1] An on-vehicle device (11) that can be mounted on a vehicle that transports luggage;
a server (20) capable of managing at least the operating status of the vehicle;
a company terminal (office PC 31) that can be used by a transportation company that manages the vehicle;
a shipper terminal (shipper PC 41) that can be used by the shipper of the cargo transported by the vehicle;
Equipped with
The server is
Detects that the vehicle to be managed has arrived at the loading or unloading location specified by the shipper and has entered a waiting state, and sends information representing the waiting state to the vendor terminal and the shipper's terminal. A waiting notification unit (20f, S13) that notifies each of the
When waiting release information is received from the on-vehicle device, the on-vehicle device notifies the above-mentioned vendor terminal and the above-mentioned shipper terminal of cargo-waiting release, respectively, and when receiving the cargo-waiting release information from the above-mentioned shipper terminal, the on-vehicle a waiting list release notification unit (20g, S19, S19A) that notifies the container and the vendor terminal of the release of the waiting list, respectively;
A traffic management system (100) having:

According to the operation management system configured as described in [1] above, when a vehicle is waiting for cargo, the transportation company and the shipper can check the situation on the company's terminal and the shipper's terminal, respectively. In addition, when the onboard device detects that the cargo waiting list has been released, the transportation business operator and the shipper can confirm that the cargo waiting list has been released from the carrier terminal and the shipper terminal, respectively. Further, when the shipper instructs to release the cargo waiting list through an input operation on the cargo owner terminal, the server, the on-vehicle device, and the operator terminal can recognize the release of the cargo waiting list. Therefore, the manager on the transport company's side and the manager on the shipper's side can grasp the actual waiting situation in real time, and can take measures to quickly resolve the waiting situation. As a result, the waiting time for cargo will be reduced, and the labor conditions for truck drivers can be expected to improve. Further, the manager on the shipper's side and the manager on the transport company's side can have a common understanding of the actual waiting time for vehicles. As a result, a situation is realized in which there is no problem even if the transport company charges the shipper a special charge for waiting as compensation for the waiting time that has occurred. This can be expected to reduce waiting time.

[2] When the vehicle to be managed shifts to the waiting state, the shipper terminal displays visible information representing the vehicle in the waiting state on the screen, and also inputs an input for instructing release of the waiting state. It has a user interface (shipper management unit 20i, S13, S15, S17) that displays operation buttons that can accept operations,
The traffic management system according to [1] above.

According to the operation management system having the configuration [2] above, the manager on the shipper's side can confirm on the screen of the shipper's terminal that the vehicle to be managed is in a waiting state. Further, after confirming that the cause of the cargo waiting state has been resolved, the manager on the shipper's side can instruct cancellation of the cargo waiting state by operating an operation button on the user interface.

[3] The on-vehicle device includes a load-waiting release detection unit ( S31, S32),
The traffic management system according to [1] above.

According to the operation management system configured as described in [3] above, after the state of the onboard equipment shifts to the waiting state, if the cause of the waiting state is resolved, the driver does not need to perform any special operation. , the onboard equipment can be automatically released from the waiting state. In addition, the entire system can know that the waiting list has been lifted.

[4] A vehicle management unit (20b) that acquires information on the current position of a vehicle transporting cargo and information representing a cargo waiting state of the vehicle from an onboard device mounted on the vehicle;
a customer identification unit (shipping management unit 20d, shipper management unit 20i) that identifies the customer based on the information acquired from the on-vehicle device;
a release instruction receiving unit (wait-wait management unit 20d) capable of receiving a signal from the outside instructing cancellation of the cargo-waiting state;
a cargo waiting time measurement unit (20e) that records the cargo waiting time from when the vehicle enters the cargo waiting state until the vehicle is released from the cargo waiting state;
an information storage unit (operation record DB 20c) that stores information on the measured cargo waiting time in a state where it is linked to the corresponding customer;
an aggregation unit (data aggregation unit 20j) that aggregates and outputs the information stored in the information storage unit for each customer;
An operation management server (server 20) comprising:

According to the operation management server configured as described in [4] above, information on the waiting time actually occurring in a vehicle can be accurately recorded for each shipper. In addition, by aggregating and outputting the recorded information for each shipper, information useful for reducing the time and frequency of waiting for cargo that will occur in the future can be obtained.

[5] The aggregation unit aggregates the information stored in the information storage unit for each customer, automatically edits the aggregation results into daily report format data (daily attendance report 70), and then outputs the data.
The operation management server described in [4] above.

According to the operation management server configured as described in [5] above, by outputting the aggregation results as a daily report, it is easy to investigate the root cause of the backlog and take measures to eliminate the backlog. become. Additionally, it becomes easier for the transportation company to bill the shipper for the compensation for the backlog that has occurred, leading to a reduction in backlog. This will also improve the labor conditions for drivers.

10 Truck vehicle 11 On-vehicle device 11a Vehicle speed detection section 11b GPS receiver 11c Display section 11d Operation section 11e RTC
11f Control unit 11g Non-volatile memory 11h Volatile memory 11i Memory card IF
11j Wireless communication section 12 Load waiting time recording function 15 Memory card 20 Server 20a Communication section 20b Vehicle management section 20c Operation record DB
20d Waiting management unit 20e Waiting time measurement unit 20f Waiting notification unit 20g Waiting release notification unit 20h Office management unit 20i Shipper management unit 20j Data aggregation unit 21 Waiting status notification 22 Waiting release notification 23 Communication network 30 Transportation company office 31 Office PC
32 Waiting vehicle display function 33 Daily report output function 40 Shipper's office 41 Shipper's PC
42 Waiting vehicle display function 70 Daily attendance report 71 Operation classification display field 72 Working time display field 73 Load waiting time display field 74 Operation chart display field 75 Daily report information display field 76 Load waiting time display field for each shipper 100 Operation management system i01 Cargo Waiting state notification i02 Waiting notification i03, i04, i11, i12 Waiting release notification

Claims (5)

An on-vehicle device that can be mounted on a vehicle that transports cargo;
a server capable of managing at least the operating status of the vehicle;
a company terminal that can be used by a transportation company that manages the vehicle;
a shipper terminal that can be used by a shipper of cargo transported by the vehicle;
Equipped with
The server is
Detects that the vehicle to be managed has arrived at the loading or unloading location specified by the shipper and has entered a waiting state, and sends information representing the waiting state to the vendor terminal and the shipper's terminal. a waiting notification section that notifies each person;
When waiting release information is received from the on-vehicle device, the on-vehicle device notifies the above-mentioned vendor terminal and the above-mentioned shipper terminal of cargo-waiting release, respectively, and when receiving the cargo-waiting release information from the above-mentioned shipper terminal, the on-vehicle a cargo waiting release notification unit that notifies the cargo container and the aforementioned vendor terminal of cancellation of the cargo waiting list, respectively;
A traffic management system with When the vehicle to be managed shifts to the waiting state, the shipper terminal displays visible information representing the vehicle in the waiting state on the screen, and accepts an input operation for instructing release of the waiting state. having a user interface displaying possible operation buttons;
The traffic management system according to claim 1. The on-vehicle device includes a load-waiting release detection unit that automatically transmits the load-waiting release information to the server when detecting the start of travel of the own vehicle while the own vehicle is in the load-waiting state.
The traffic management system according to claim 1. a vehicle management unit that acquires information on the current position of a vehicle transporting cargo and information representing a cargo waiting state of the vehicle from an on-board device mounted on the vehicle;
a customer identification unit that identifies a customer based on information acquired from the on-vehicle device;
a release instruction receiving unit capable of receiving an external signal instructing release of the cargo waiting state;
a cargo waiting time measurement unit that records the cargo waiting time from when the vehicle enters the cargo waiting state until the vehicle is released from the cargo waiting state;
an information storage unit that stores information on the measured waiting time in a state where it is linked to a corresponding customer;
an aggregation unit that aggregates and outputs the information stored in the information storage unit for each customer;
An operation management server equipped with The aggregation unit aggregates the information stored in the information storage unit for each customer, automatically edits the aggregation results into daily report format data, and then outputs the data.
The traffic management server according to claim 4.

Images