JP2022158640A - Delivery vehicle operation management system - Google Patents

Abstract

To provide a delivery vehicle operation management system enabling a system manager to easily confirm abnormality information on a delivery vehicle having the abnormality information representing a delay, and to reduce the number of times of ride inspections.SOLUTION: A delivery vehicle operation management system includes: an onboard terminal that is mounted on a delivery vehicle; a management processor that creates and processes an operation history table and a scheduled/actual timeline chart 16; and a base terminal that displays the operation history table and the scheduled/actual timeline chart 16. The base terminal displays the operation history table, and requests a driver to reply to an abnormality reason 152 relating to abnormality information 151 of the operation history table. The scheduled/actual timeline chart 16 describes both of a scheduled operation timeline 161 and an actual operation timeline 162 of a delivery vehicle, and attaches the abnormality information 151 and the abnormality reason 152.SELECTED DRAWING: Figure 9

Description

The technical field of the present specification relates to a delivery vehicle operation management system that manages the operation of each delivery vehicle based on a predetermined operation schedule. The present invention relates to a delivery vehicle operation management system capable of determining the necessity of confirmation.

Conventionally, Patent Document 1 listed below proposes a system for planning delivery of articles from a delivery source to a plurality of delivery destinations. This system creates a route for delivering goods from a delivery source to a plurality of delivery destinations, and also creates an operation schedule. The driver of the delivery vehicle performs the actual delivery work according to the operation schedule, and the system corrects the operation time for each route based on the difference between the operation time of the operation schedule and the actual operation time, and repeats this. Draft a delivery plan.

JP-A-2002-298066

However, when the delivery service is actually carried out based on the operation schedule, it may take longer than expected to load and unload the cargo, or there may be traffic congestion or waiting time to enter the delivery location. , there are cases where the actual operation is not carried out according to the created operation schedule. In such a case, it is necessary to modify the operation schedule. Conventionally, in such cases, the person in charge of management boarded the delivery vehicle together with the driver and carried out a piggyback survey to confirm information on delays and other abnormalities, and to investigate how the actual operation schedule deviated from the planned operation schedule. I had to.

In particular, dozens of delivery vehicles that deliver parts to factories that are engaged in mass production carry out delivery operations based on the operation schedule every day, so many management personnel are conducting piggyback surveys on many delivery vehicles. and spent a lot of time adjusting the difference between the planned operation schedule and the actual operation schedule.

The problem to be solved by the technology of the present specification is that the system administrator can easily check the abnormal information about the operating flights having abnormal information such as delays, and reduce the number of piggyback investigations. To provide a delivery vehicle operation management system capable of

A delivery vehicle operation management system according to the present specification loads and delivers goods from a plurality of delivery sources to a plurality of delivery destinations on a delivery vehicle operated based on predetermined scheduled operation information. A vehicle operation management system,
an in-vehicle terminal mounted on the delivery vehicle for acquiring and transmitting actual operation information such as operation time, position information, and vehicle speed of the delivery vehicle;
The scheduled operation information of the service flight is stored in the scheduled operation information storage unit, and the actual operation information of the delivery vehicle of the operation service transmitted from the vehicle-mounted terminal is captured via the Internet and stored in the actual operation information storage unit. a management processor that stores
It is connected to the Internet and acquires the scheduled operation information and the actual operation information of the operation flight sent from the management processing device, and the scheduled operation time and the scheduled cargo handling time of the scheduled operation information and the execution of the actual operation information. a base terminal that displays an operation history table including operation times and actual cargo handling times on a display unit;
with
When displaying the operation history table on the display unit, the base terminal displays the difference between the scheduled operation time and the actual operation time of the service flight, and the scheduled cargo handling time and the actual operation time in the operation history table. an abnormality information display means for displaying a difference in cargo handling time, and displaying the abnormality information as abnormality information when the difference exceeds a reference value; display an input field for the driver, prompt the driver to input the reason for the abnormality for the abnormality information, and transmit the operation history table in which the reason for the abnormality is entered to the management processing device. have the means to
The management processing device displays the scheduled operation diagram and the actual operation diagram of the service on the same diagram together with the reason for the abnormality based on the information in the operation history table in response to the access from the base terminal. A schedule/actual diagram is created, and information of the schedule/actual diagram is transmitted to the base terminal.

According to the delivery vehicle operation management system of the present specification, the driver of the delivery vehicle uses the base terminal to add the cause of the abnormal information to the operation history table having the scheduled operation information and the actual operation information after the operation. The reason for the abnormality can be easily and directly input, and the abnormality information to which the reason for the abnormality is added can be reflected in the operation history table. In addition, based on the information in the operation history table, the management processing device creates a scheduled/actual timetable chart that displays the scheduled operation timetable chart and the actual timetable chart of the service along with the reason for the abnormality on the same chart. The manager can quickly and easily find the flight with the reason for abnormality from among a large number of flights by looking at the display of the scheduled/actual timetable chart, and the status of having the reason for abnormality in the operated flight (operation status, cargo handling status) can be grasped immediately. Therefore, the system administrator can accurately determine the necessity of confirmation of abnormality information (piggyback investigation) for an operating flight having an abnormality reason, and can reduce the number of piggyback investigations.

Further, in the delivery vehicle operation management system, the scheduled operation information includes information on the scheduled operation route of the delivery vehicle, and there is a difference between the trajectory of the position information transmitted from the in-vehicle terminal and the scheduled operation route. At this time, the management processing device can be configured to display a route abnormality as the abnormality information in the operation history table.

According to this, when the trajectory of the location information, which is the actual operation route, differs from the planned operation route, it is displayed as anomaly information. Normal state can be recognized.

Further, in the above delivery vehicle operation management system, the management processing device includes traffic congestion information acquisition means for acquiring traffic congestion information on a road from the Internet, and when the abnormal information and the traffic congestion information match, the The reason for the abnormality may be a congested state, and the reason for the abnormality may be added to the actual operation information.

According to this, it is possible to automatically record the reason for the abnormality due to traffic congestion in the actual operation information.

According to the delivery vehicle operation management system of the present specification, the system administrator can easily and quickly discover an operation flight having an abnormal reason by looking at the display of the scheduled/actual timetable chart, and can A situation with a reason can be immediately grasped. For this reason, the system administrator can accurately and efficiently determine the necessity of confirming abnormal information (piggyback investigation) for a flight with an abnormal reason from among multiple operating flights, and the number of piggyback investigations can be determined. can be reduced.

1 is an overall configuration diagram of a delivery vehicle operation management system according to an embodiment; FIG. It is a block diagram of the vehicle-mounted terminal of the delivery vehicle of the embodiment. 3 is a block diagram of a management processing device of the embodiment; FIG. 3 is a block diagram of a base terminal of the embodiment; FIG. It is a flow chart of actual operation information taking-in processing. 4 is a flowchart of operation history table creation processing; 10 is a flowchart of schedule/actual diagram creation processing. It is a figure which shows an example of an operation history table. It is a figure which shows an example of a schedule / performance operation timetable chart.

An embodiment of the delivery vehicle operation management system 1 will be described below with reference to the drawings. FIG. 1 shows the overall configuration of a delivery vehicle operation management system 1 of the embodiment. The delivery vehicle operation management system 1 is a management processing device that processes an in-vehicle terminal 21 mounted on a delivery vehicle, scheduled operation information 13 and actual operation information 12, and creates and processes an operation history table 15 and a schedule/actual diagram 16. 4, and a base terminal 3 for performing management work at each base such as displaying an operation history table 15 and a schedule/actual diagram 16 and inputting an abnormality reason 152 of the abnormality information 151 of the operation history table 15. ing.

As shown in FIG. 1, the management processing device 4 has a database 5 configured by a server system or the like connected to the Internet 111 . The management processing device 4 stores the scheduled operation information 13 created in advance for each operating flight in the scheduled operation information storage unit 53 of the database 5, and stores the actual operation information 12 collected by the actual operation in the actual operation information storage unit. 52. After the actual operation of each flight, the operation history table 15 and the schedule/actual diagram 16 created by the management processing device 4 are stored in the operation history table storage unit 55 and the schedule/actual diagram storage unit 56, respectively. be. The database 5 can be provided in the memory 43 of the management processing device 4, or can be provided in a separately provided database server.

As shown in FIG. 2, an in-vehicle terminal 21 installed in each delivery vehicle includes an in-vehicle communication unit 23 capable of communicating with the mobile phone communication network 112 of the communication network 11, and an operation information unit 23 for acquiring actual operation information 12 of the delivery vehicle. and an acquisition unit 22 . As shown in FIG. 1, the in-vehicle terminal 21 can be connected to the management processing device 4 and the base terminal 3 via the mobile phone communication network 112 and the Internet 111 .

As shown in FIG. 2, the operation information acquisition unit 22 includes a time acquisition unit 221 that acquires the operation time of the actual operation information 12, a GPS (Global Positioning System) reception unit 222 that acquires the position information of the delivery vehicle, and a delivery vehicle. and a vehicle speed sensor 223 for detecting the vehicle speed.

The time acquisition unit 221 acquires the operating time from the GPS reception unit 222 in the embodiment. The GPS receiving unit 222 receives radio waves from a plurality of GPS satellites, calculates the positional information of the delivery vehicle from the difference in reception time of each radio wave, and displays the position of the delivery vehicle on the map displayed on the display unit 24. indicate. The vehicle speed sensor 223 detects the rotation speed of the axle of the delivery vehicle, and calculates the vehicle speed of the delivery vehicle from the rotation speed of the axle.

The in-vehicle communication unit 23 transmits actual operation information 12 (operation time, position information, vehicle speed, etc.) of the delivery vehicle to the management processing device 4 through the mobile phone communication network 112 and the Internet 111 at predetermined time intervals.

The management processing device 4 stores the scheduled operation information 13 created in advance for each service in the scheduled service information storage unit 53, and stores the actual service information 12 sent from each service service in the actual service information storage unit 52. memorize to Based on the actual operation information 12 and the scheduled operation information 13, the management processing device 4 creates an operation history table 15 and a schedule/actual diagram chart 16, and stores an operation history table storage unit 55 and a schedule/actual diagram storage unit 56, respectively. memorize to Anomaly information 151 and anomaly reason 152 are added to the operation history table 15 and the scheduled/actual timetable chart 16 .

As shown in FIG. 3, the management processing device 4 includes a processor 41, a memory 43, an interface 42, a communication control section 421, an operation section 422, and a display section 423, and is composed of a server system or the like. The memory 43 is provided with an actual operation information storage unit 52 , a scheduled operation information storage unit 53 , an operation history table storage unit 55 , and a planned/actual diagram storage unit 56 as the database 5 .

The communication control unit 421 is connected to the base terminal 3 via the Internet 111, is connected to the in-vehicle terminal 21 via the mobile phone communication network 112 of the communication network 11 and the Internet 111, and captures the actual operation information 12 from the in-vehicle terminal 21. . The communication control unit 421 also includes traffic congestion information acquisition means for acquiring road traffic congestion information from the Internet 111 .

The database 5 stores information on all operating flights, such as operating flight names, operating route Nos., transportation company names, driver names, and the like. The database 5 includes an actual operation information storage unit 52 for storing the actual operation information 12 of each operating flight transmitted from the on-vehicle terminal 21, and a scheduled operation information 13 for storing the scheduled operation information 13 previously created and input for each operating flight. An information storage unit 53, an operation history table storage unit 55 that stores an operation history table 15 created by the management processing device 4 based on the actual operation information 12 of each service, and a schedule/actual diagram 16 similarly created. A scheduled/actual diagram storage unit 56 is provided.

The scheduled operation information 13 stored in the scheduled operation information storage unit 53 includes position information and scheduled departure time of the departure point of each service, position information of each cargo handling point, estimated time of arrival at each cargo handling point, and scheduled departure time. , the estimated time of arrival at the delivery vehicle base (departure point) as the final arrival point, and the scheduled operation route of the delivery vehicle. These scheduled operation information 13 are created in advance by the management processing device 4, input, and stored.

When creating the scheduled operation information 13, for example, using route guidance software using road map information, the departure point, each cargo handling point, and the arrival point are set on the map (scheduled operation route), and normal roads are set. The route proceeds from the departure point to each cargo-handling point, and in consideration of the cargo-handling time required at each cargo-handling point, the arrival time and departure time are set there, and scheduled operation information 13 including information on a scheduled operation time table is created. .

The base terminal 3 is composed of a personal computer or the like installed at a delivery vehicle base or a package collection and delivery base, and as shown in FIG. A display unit 323 is provided. As shown in FIG. 1, the base terminal 3 is connected to the Internet 111, has application software for operation management, browser software, etc., and has an operation history table 15 and a scheduled/actual diagram created by the management processing device 4. 16 etc. are taken in and displayed. After the operation, the base terminal 3 displays the operation history table 15 shown in FIG. Ask. The reason for abnormality 152 is displayed as, for example, a pop-up menu 153 so that an operator such as a driver can easily input the reason for abnormality 152 .

As shown in FIG. 8, the operation history table 15 displays the scheduled time Te (scheduled arrival time and scheduled departure time) from the scheduled operation information 13 of the database 5 in chronological order, and is transmitted from the delivery vehicle of the service. From the actual operation information 12, the corresponding actual times Tr (actual arrival time and actual departure time) are displayed side by side with the scheduled time Te. The arrival time also serves as the cargo handling start time, and the departure time also serves as the cargo handling completion time. As a result, the number of display items in the operation history table 15 can be reduced, and operators such as drivers and system administrators can easily grasp the operation history table 15 .

In the operation history table 15, the scheduled operation time Tre (scheduled operation time and scheduled cargo handling time) and the actual required time Trr (actual operation time and actual cargo handling time) for each state (operation or service) are stored in the scheduled operation information 13 and the actual operation. It is calculated from the information 12 and displayed. The difference between the actual required time Trr and the scheduled required time Tre is displayed in the operation history table 15 as the time lag Tl. Then, as the time lag Tl, the actual required time Trr exceeds the reference value of 20% of the allowable deviation from the scheduled required time Tre (Abs (Trr−Tre)≧Tre×20%), and the actual required time Trr and the scheduled required time If the difference in time Tre exceeds 10 minutes (Abs (Trr-Tre) ≥ 10 minutes) (exceeds the allowable value), it is regarded as abnormal information 151, and its numerical value is colored or bold and displayed in the operation history table 15. be. If there is abnormality information 151 in the operation history table 15, a pop-up menu 153 is displayed on the display screen, and the driver of the delivery vehicle for the service or the like inputs the abnormality reason 152 at the base terminal 3.

Incidentally, in the operation history table 15, there is anomaly information 151 in which the scheduled required time Tre of the operation state exceeds the allowable value. The abnormality information 151 is stored in the operation history table storage unit 55 of the database 5 as an abnormality reason 152 for causing the traffic congestion. As a result, the reason 152 for abnormality due to congestion can be automatically stored in the operation history table storage unit 55 .

Further, in the operation history table 15, when the ratio of the route different from the trajectory of the position information transmitted from the on-vehicle terminal 21 and the planned operation route exceeds 50% as a reference value, it is set as abnormality information 151 of route abnormality, and the base terminal In 3, the driver of the delivery vehicle for the service is requested to input the reason for abnormality 152 . As a result, when the trajectory of the position information, which is the actual route, differs from the planned route, it is displayed as the route fault abnormality information 151. Therefore, the system administrator can easily, on the screen of the base terminal, Abnormalities and normal states of routes can be recognized. In addition, since the driver of the delivery vehicle for the service is requested to input the route abnormality reason 152, the system administrator can confirm the route abnormality reason.

An abnormality reason 152 in the pop-up menu 153 displays a delay reason during operation, a reason for early arrival during operation, a reason for delay during cargo handling, a reason for early arrival during cargo handling, natural congestion, accidental congestion, waiting at a terminal, rest, and the like. be. A driver or the like of a delivery vehicle for an operating service selects and inputs an abnormality reason 152 from among these.

The operation history table 15 to which the input reason for abnormality 152 is added is transmitted to the management processing device 4 , and the management processing device 4 stores it in the operation history table storage unit 55 of the database 5 .

The management processing device 4 prepares a scheduled flight schedule 161 and an actual flight schedule 162 on the same chart as shown in FIG. It is stored in the chart storage unit 56 .

The scheduled operation diagram 161 is displayed in black, the actual operation diagram 162 is displayed in blue, and the abnormal information 151 portion of the actual operation diagram 162 is displayed in red. In FIG. 9, the scheduled operation schedule 161 is indicated by a solid line, the actual operation schedule 162 is indicated by a broken line, and the abnormal information 151 portion is indicated by a thick two-dot chain line.

The scheduled/actual timetable chart 16 displays a scheduled timetable 161 and an actual timetable 162 of an operating flight on the same chart, and an abnormality reason 152 is attached. Therefore, in addition to the reason for abnormality 152, the administrator of the system can compare the scheduled operation diagram 161 and the actual operation diagram 162 displayed on the same chart to obtain the abnormality information 151, the abnormality reason 152, and the abnormality information. 151 (operating state, cargo handling state) can be easily recognized. Therefore, the system administrator can accurately determine the necessity of checking the abnormality information 151 (piggyback investigation), and can reduce the number of piggyback investigations.

Next, the operation of the delivery vehicle operation management system 1 will be described with reference to the flow charts of FIGS. 5 to 7. FIG.

First, the process of acquiring the actual operation information 12 of delivery vehicles will be described based on the flowchart of FIG.

When the operation of the delivery vehicle is started and the delivery vehicle operation management system 1 is activated, in step S101, the vehicle-mounted terminal 21 transmits the actual operation information 12 including the vehicle position information and the operation time, and the management processing device 4 starts the actual operation. The information 12 is acquired and stored in the actual operation information storage unit 52 (step S102). The actual operation information 12 is transmitted from the in-vehicle communication unit 23 of the in-vehicle terminal 21 every minute, for example.

Next, in step S103, the management processing device 4 determines whether or not the position information of the actual operation information 12 of the delivery vehicle is the departure point. The departure time is stored in the actual operation information storage unit 52 (step S104).

The regularly transmitted actual operation information 12 is input to the communication control unit 421 of the management processing device 4 through the mobile phone communication network 112 and the Internet 111 (step S105), and stored in the actual operation information storage unit 52 ( step S106). The storage of the actual operation information 12 in the actual operation information storage unit 52 continues until the delivery vehicle reaches the delivery vehicle base (departure point) as the final arrival point through each cargo handling point (step S107).

Next, in step S108, the management processing device 4 determines whether or not the position information of the actual operation information 12 of the delivery vehicle is the cargo handling point. The operation time of the hour is stored in the actual operation information storage unit 52 as the cargo handling point arrival time and cargo handling start time.

Next, in step S110, the management processing device 4 determines whether the position information of the actual operation information 12 of the delivery vehicle is the cargo handling point, and determines whether the actual operation information 12 when the position information is away from the cargo handling point. The operation time is stored in the actual operation information storage unit 52 as the cargo handling point departure time and the cargo handling end time (step S111).

Thereafter, steps S105 to S111 are repeated until reaching the delivery vehicle base (departure point) as the final arrival point (step S107).

When the delivery vehicle returns to the delivery vehicle base (departure point) (step S107), the operation time of the actual operation information 12 at that time is stored in the actual operation information storage unit 52 as the end time (step S112). The processing from step S101 to step S112 is executed for all delivery vehicles, and the information is stored in the actual operation information storage unit 52. FIG.

Next, the process of creating the operation history table 15 from the captured actual operation information 12 of the delivery vehicle will be described based on the flowchart of FIG.

First, in step S201, the management processing device 4 determines whether or not to create the operation history table 15, and according to an instruction from the base terminal 3, or when the delivery vehicle arrives at the delivery vehicle base (departure point). Triggered by the end of the process, creation of the operation history table 15 is started.

The actual operation information 12 of the delivery vehicle of the relevant service is read from the actual operation information storage unit 52, the scheduled operation information 13 is read from the scheduled operation information storage unit 53, and the operation history table 15 as shown in FIG. 8 is created. (Step S202).

Next, in steps S203 and S204, the presence or absence of the abnormality information 151 is determined from the magnitude of the difference between the planned required time and the actual required time in the operation history table 15. FIG. In step S203, the abnormality information 151 indicates that the actual required time Trr (actual operation time, actual cargo handling time) exceeds the allowable reference value of deviation of 20% from the scheduled required time Tre (scheduled operation time, scheduled cargo handling time). (Abs (Trr-Tre) ≥ Tre x 20%), and in step S204, whether the difference between the actual required time Trr and the scheduled required time Tre exceeds 10 minutes (Abs (Trr-Tre) ≥ 10 minutes) judge. Then, when the actual required time Trr exceeds the allowable value (20% of the scheduled required time Tre and 10 minutes), it is added to the operation history table 15 as the abnormality information 151 (step S205).

The data of the operation history table 15 is transmitted to the base terminal 3 (step S206), and the operation history table 15 including the abnormality information 151 is displayed on the base terminal 3. are displayed in bold or in a different color. The processing at this time is the function of displaying the abnormality information 151, that is, the abnormality information display means.

Furthermore, as shown in FIG. 8, when there is abnormality information 151 in the operation history table 15, a pop-up menu 153 is displayed in the column of "abnormal reason selection". 3 operators, etc., the abnormal reasons 152 are displayed so as to be selectable. The pop-up menu 153 displays "cargo waiting", "station waiting", "set time (small)", "rest", etc. when the actual cargo handling time is delayed, and "congestion" when the actual operation time is delayed. , “closed”, “route change”, “set time (small)”, “rest”, etc. are displayed. If the actual cargo handling time is shortened, "Cargo amount (smaller)", "Set time (longer)", etc. will be displayed. large)” is displayed. In the case of a route abnormality, "bypass", "traffic avoidance", "traffic closure avoidance", "stopping for lunch", etc. are displayed.

For the abnormality information 151, the driver, the operator of the base terminal 3, or the like clicks the corresponding abnormality reason 152 from the pop-up menu 153 and inputs (step S207). The entered abnormality reason 152 is added to the data in the operation history table 15 (step S208). The abnormality information 151 to which the traffic congestion information is added is automatically added with the abnormality reason 152 of traffic congestion.

The operation history table 15 to which the abnormality information 151 and the abnormality reason 152 are added is stored in the operation history table storage unit 55 (step S209).

Next, the processing for creating the scheduled/actual diagram 16 will be described with reference to the flowchart of FIG.

First, in step S301, it is determined whether or not to create the scheduled/actual timetable chart 16, and it is completed by an instruction from the base terminal 3 or when the service arrives at the delivery vehicle base (departure point). as a trigger to start creating.

When an instruction to create the schedule/actual diagram 16 is received from the base terminal 3 (step S301), the process of creating the schedule/actual diagram 16 is started.

The management processing unit 4 reads out the scheduled departure time, arrival time at the scheduled cargo handling point, departure time from the scheduled cargo handling point, and scheduled end time from the scheduled operation information storage unit 53, and creates a chart of the scheduled operation schedule 161 (step S302). .

Furthermore, the management processing device 4 reads out the actual departure time, the actual cargo handling point arrival time, the actual cargo handling point departure time, and the actual end time from the actual operation information storage unit 52, and creates a chart of the actual operation schedule 162 (step S303).

Next, in step S304, it is determined whether or not there is abnormality information 151 in the operation history table 15 of the operation history table storage unit 55. If there is, the abnormality information 151 is added to the chart of the actual operation schedule 162 ( step S305). Furthermore, in step S306, it is determined whether or not there is an abnormality reason 152 in the operation history table 15 of the operation history table storage unit 55. If there is an abnormality reason 152, the abnormality reason 152 is added to the chart of the actual operation schedule 162 (step S306). S307).

Next, in step S308, the scheduled/actual timetable chart 16 is created by adding the data of the scheduled timetable 161 and the data of the actual timetable 162 into one chart, and is stored in the scheduled/actual timetable chart storage unit 56. . The stored schedule/actual diagram 16 is read from the schedule/actual diagram storage unit 56 and transmitted to the base terminal 3 in response to access from the base terminal 3 .

As shown in FIG. 9, the scheduled/actual timetable chart 16 transmitted to and displayed on the base terminal 3 includes, for example, a scheduled timetable 161 of an operating flight with a solid line, an actual timetable 162 with a broken line, and an abnormal information 151 portion. It is displayed on the same chart with a thick two-dot chain line or with a different color. Furthermore, when the actual operation schedule 162 has the abnormality information 151 and the abnormality reason 152 displayed in the operation history table 15 of FIG. The scheduled/actual diagram 16 can display the scheduled operation diagram 161 in black, the actual operation diagram 162 in blue, and the abnormal information 151 portion of the actual operation diagram 162 in red. When the system administrator checks the operation of a service flight, he/she operates the base terminal 3 to specify the service flight name, implementation date, etc., and downloads the scheduled/actual timetable chart 16 from the management processing device 4 . The system administrator can see the display of the scheduled/actual timetable chart 16 and can quickly and easily find an operating flight having the reason for abnormality 152 even among a large number of operating flights. It is possible to immediately grasp the status (operating status, cargo handling status) that has a reason. Therefore, the administrator can accurately determine the necessity of confirming the abnormality information 151 (piggyback investigation) for the operating flight having the abnormality reason 152, and can reduce the number of piggyback investigations.

Note that the delivery vehicle operation management system 1 of the embodiment can also be implemented in the following forms as other embodiments.

In the delivery vehicle operation management system 1 of the embodiment, the acquisition (transmission) frequency of the actual operation information 12 is set to every minute, but any frequency from 1 second to 10 minutes can be used as the actual operation information 12 . If the acquisition frequency of the actual operation information 12 is less than 1 second, the amount of data of the actual operation information 12 increases, and the process of creating the operation history table 15 and the schedule/actual diagram 16 may become complicated. On the other hand, if the time exceeds 10 minutes, there is a risk that the error between the operation history table 15 and the scheduled/actual timetable chart 16 will increase. However, in another embodiment, it can be from 5 seconds to 2 minutes.

1... delivery vehicle operation management system, 3... base terminal, 4... management processing device, 5... database, 11... communication network, 12... actual operation information, 13... scheduled operation information, 15... operation history table, 16... schedule/ Performance diagram 21 In-vehicle terminal 22 Operation information acquisition unit 23 In-vehicle communication unit 24 Display unit 31 Processor 32 Interface 33 Memory 41 Processor 42 Interface 43 Memory , 52... Actual operation information storage unit, 53... Planned operation information storage unit, 55... Operation history table storage unit, 56... Schedule/actual diagram storage unit, 111... Internet, 112... Mobile phone communication network, 151... Abnormal information , 152... Abnormal reason 153... Pop-up menu 161... Scheduled operation schedule 162... Actual operation schedule 221... Time acquisition unit 222... GPS receiver 223... Vehicle speed sensor 321... Communication control unit 322... Operation unit , 323... display unit, 421... communication control unit, 422... operation unit, 423... display unit, Te... scheduled time, Tl... time lag, Tr... actual time, Tre... scheduled required time, Trr... actual required time.

Claims (3)

A delivery vehicle operation management system for loading and delivering goods from a plurality of delivery sources to a plurality of delivery destinations on a delivery vehicle operated on the basis of predetermined scheduled operation information,
an in-vehicle terminal mounted on the delivery vehicle for acquiring and transmitting actual operation information such as operation time, position information, and vehicle speed of the delivery vehicle;
The scheduled operation information of the service flight is stored in the scheduled operation information storage unit, and the actual operation information of the delivery vehicle of the operation service transmitted from the vehicle-mounted terminal is captured via the Internet and stored in the actual operation information storage unit. a management processor that stores
It is connected to the Internet and acquires the scheduled operation information and the actual operation information of the operation flight sent from the management processing device, and the scheduled operation time and the scheduled cargo handling time of the scheduled operation information and the execution of the actual operation information. a base terminal that displays an operation history table including operation times and actual cargo handling times on a display unit;
with
When displaying the operation history table on the display unit, the base terminal displays the difference between the scheduled operation time and the actual operation time of the service flight, and the scheduled cargo handling time and the actual operation time in the operation history table. an abnormality information display means for displaying a difference in cargo handling time, and displaying the abnormality information as abnormality information when the difference exceeds a reference value; display an input field for the driver, prompt the driver to input the reason for the abnormality for the abnormality information, and transmit the operation history table in which the reason for the abnormality is entered to the management processing device. have the means to
The management processing device displays the scheduled operation diagram and the actual operation diagram of the service on the same diagram together with the reason for the abnormality based on the information in the operation history table in response to the access from the base terminal. A delivery vehicle operation management system characterized by creating a schedule/actual diagram and transmitting information of the schedule/actual diagram to a base terminal. The scheduled operation information includes information on the scheduled operation route of the delivery vehicle. 2. The delivery vehicle operation management system according to claim 1, wherein a route abnormality is displayed as the abnormality information in the history table. The management processing device includes traffic congestion information acquisition means for acquiring traffic congestion information on a road from the Internet, and when the abnormality information and the traffic congestion information match, the abnormality reason is regarded as a traffic congestion state, and the abnormality 3. The delivery vehicle operation management system according to claim 1, wherein a reason is added to the actual operation information.

Images