Vehicle allocation planning device, vehicle allocation planning method, vehicle allocation system, and computer program

Abstract

To prevent work based on a new request from being allocated to an improper vehicle.SOLUTION: A vehicle allocation planning device according to the disclosure comprises a processing device configured to execute: first generation processing of generating a first vehicle allocation plan for a plurality of vehicles that perform work of at least one of collection and delivery of a cargo; and second generation processing of generating a second vehicle allocation plan added with the work based on a new request when receiving the new request for the work including collection of the cargo. The second generation processing is configured to generate the second vehicle allocation plan by allocating the work based on the request to any of one or the plurality of target vehicles excluding a non-target vehicle for which allocation of the work based on the request is prohibited among the plurality of vehicles.SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present disclosure relates to a vehicle dispatch planning device, a vehicle dispatch planning method, a vehicle dispatch system, and a computer program. [Background technology]

[0002] Patent Document 1 discloses a navigation device that searches for a route suitable for visiting delivery points of a package and guides a driver along the searched route. In Patent Document 1, when a package cannot be delivered because the delivery destination is absent, a route for redelivering the package is searched again. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2016-181043 A Summary of the Invention [Problem to be solved by the invention]

[0004] Vehicles that deliver or collect packages are operated according to a vehicle dispatch plan, as in Patent Document 1. The vehicle dispatch plan indicates the operation schedule of each of a plurality of vehicles during a day. The vehicle dispatch plan is generated, for example, at the start of business for the day. The driver acquires the generated vehicle dispatch plan and departs from the base of the vehicle. The driver collects or delivers packages according to the acquired vehicle dispatch plan.

[0005] The generated vehicle dispatch plan may be updated while the vehicles are in operation. The vehicle dispatch plan is updated based on requests from users who wish to collect or deliver packages. If a new request is received from a user who wishes to collect or deliver packages on the same day after the vehicle dispatch plan is generated, the collection and delivery must be assigned to one of the vehicles.

[0006] The new request should be assigned to an appropriate vehicle based on the current dispatch plan, e.g., a vehicle that can efficiently handle the pickup and delivery of the new request.

[0007] However, even if a vehicle can efficiently handle a task (collection or delivery) based on a new request based on the current vehicle dispatch plan, it is not necessarily appropriate for the vehicle to be assigned the task based on the new request. A vehicle to which the task based on the new request is assigned may be hindered.

[0008] For example, a vehicle carrying a package that could not be delivered due to an absence of the delivery point may need to be redelivered, which is not yet included in the vehicle dispatch plan. If such a vehicle is assigned a task based on a new request, problems such as delays in redelivery may occur. In addition, problems caused by the assignment of a task based on a new request are not limited to delays in redelivery. There may be vehicles that should not be assigned a task based on a new request for other reasons.

[0009] It is therefore desirable to prevent work based on new requests from being assigned to inappropriate vehicles. [Means for solving the problem]

[0010] One aspect of the present disclosure is a vehicle dispatch planning device. The disclosed vehicle dispatch planning device includes a processing device configured to execute a first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a task of collecting and delivering luggage, and a second generation process for generating a second vehicle dispatch plan to which the task based on the request is added when a new request for a task including the task of collecting luggage is received, and the second generation process is configured to generate the second vehicle dispatch plan by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited.

[0011] Another aspect of the present disclosure is a vehicle dispatch planning method, comprising: a step of generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a task of collecting and delivering luggage by a vehicle dispatch planning device; and a step of generating a second vehicle dispatch plan to which the task based on the request is added when the vehicle dispatch planning device receives a new request for a task including the task of collecting luggage, wherein the second vehicle dispatch plan is generated by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited.

[0012] Another aspect of the present disclosure is a vehicle dispatch system. The vehicle dispatch system includes a vehicle dispatch planning device and a plurality of terminals associated with a plurality of vehicles performing at least one of a task of collecting and delivering luggage, the vehicle dispatch planning device includes a processing device configured to execute a first generation process for generating a first vehicle dispatch plan for the plurality of vehicles, and a second generation process for generating a second vehicle dispatch plan to which the task based on the request is added when a new request for a task including a task of collecting luggage is received, the second generation process is configured to generate the second vehicle dispatch plan by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited, and the terminal is configured to receive the first vehicle dispatch plan and the second vehicle dispatch plan from the vehicle dispatch planning device.

[0013] Another aspect of the present disclosure is a computer program, which causes a computer to execute a first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a task of collecting and delivering luggage, and a second generation process for generating a second vehicle dispatch plan to which a task based on the request is added when a new request for a task including the collection of luggage is received, and the second generation process is configured to generate the second vehicle dispatch plan by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited.

[0014] A computer program according to another embodiment of the present disclosure is a computer program for causing a computer configured to receive a vehicle dispatch plan for performing work including the delivery of luggage from a vehicle dispatch planning device to execute an incomplete delivery process, the vehicle dispatch plan being generated so that the weight of luggage to be loaded onto a vehicle corresponding to the computer satisfies the load weight constraint of the vehicle, and the incomplete delivery process includes, when the computer receives an operation from a user indicating that the delivery included in the vehicle dispatch plan could not be completed, displaying on the computer, among the work included in the vehicle dispatch plan, work that does not satisfy the load weight constraint due to the delivery that could not be completed, distinguished from other work included in the vehicle dispatch plan. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a schematic diagram of a vehicle dispatch system. [Diagram 2] FIG. 2 is a configuration diagram of the vehicle allocation planning device and the driver terminal. [Diagram 3] FIG. 3 is a diagram showing the vehicle database. [Figure 4] FIG. 4 is a flowchart showing the first generation process. [Diagram 5] FIG. 5 is a data flow diagram relating to the first generation process. [Figure 6] FIG. 6 is a diagram showing the first vehicle allocation plan. [Figure 7] FIG. 7 is a diagram showing a display screen of a vehicle allocation plan. [Figure 8] FIG. 8 is a flowchart showing absence processing (delivery incompletion processing) in the vehicle allocation planning device. [Figure 9] FIG. 9 is a flowchart showing the redelivery completion process. [Figure 10] FIG. 10 is a flowchart showing the second generation process. [Figure 11] FIG. 11 is a data flow diagram relating to the second generation process. [Figure 12] FIG. 12 is a diagram showing the second vehicle allocation plan. [Figure 13] FIG. 13 is a flowchart showing the constraint determination process. [Figure 14] FIG. 14 is a flowchart showing absence processing (delivery incompletion processing) in the driver terminal. [Figure 15] FIG. 15 is a diagram showing a display screen of a vehicle allocation plan in which points where the loaded weight is exceeded are highlighted. [Figure 16] FIG. 16 is a flowchart showing another example of the constraint determination process. [Figure 17] FIG. 17 is a flowchart showing the redistribution process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] [Description of the embodiments of the present disclosure]

[0017] (1) A vehicle dispatch planning device according to an embodiment includes a processing device. The processing device executes a first generation process and a second generation process. The first generation process generates a first vehicle dispatch plan for a plurality of vehicles performing at least one of the tasks of collecting and delivering luggage. The second generation process generates a second vehicle dispatch plan to which the task based on the request is added when a new request for the task including the task of collecting luggage is received. The second generation process is configured to generate the second vehicle dispatch plan by assigning the task based on the request to any one of one or more target vehicles. The one or more target vehicles are the plurality of vehicles excluding non-target vehicles to which the assignment of the task based on the request is prohibited. In this case, it is possible to prevent the task based on the new request from being assigned to the non-target vehicles.

[0018] (2) The work included in the first vehicle dispatch plan or the second vehicle dispatch plan may include the delivery. The non-target vehicle is preferably a vehicle among the plurality of vehicles that corresponds to a terminal that has sent an incompletion notification indicating that the delivery is incomplete. In this case, a vehicle that needs to re-perform an incomplete delivery becomes a non-target vehicle, thereby reducing the risk of a delay in re-performing the delivery.

[0019] (3) The work included in the first or second vehicle dispatch plan may include the delivery. The non-target vehicle is preferably a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete. The non-target vehicle is preferably a vehicle that has been determined to cause an impediment to the re-execution of the incomplete delivery if the work based on the request is assigned to the vehicle. In this case, a vehicle that causes an impediment to the re-execution of the incomplete delivery becomes a non-target vehicle, so that a delay in the re-execution of the delivery can be reliably prevented.

[0020] (4) The work included in the first vehicle dispatch plan or the second vehicle dispatch plan may include the delivery. The non-target vehicle is preferably a vehicle among the plurality of vehicles that corresponds to a terminal that has sent an incompletion notification indicating that the delivery is incomplete. The non-target vehicle is further preferably a vehicle that corresponds to a terminal that has not sent a completion notification indicating that the incomplete delivery has been completed. In this case, a vehicle for which re-delivery has not been completed becomes a non-target vehicle.

[0021] (5) The work in the first or second vehicle dispatch plan may include the collection and the delivery. The first and second vehicle dispatch plans are preferably generated such that the load weight of each of the plurality of vehicles satisfies the load weight constraint of each of the plurality of vehicles. The processing device is preferably configured to further execute a constraint determination process when receiving the incomplete notification. The constraint determination process determines whether or not there is work in the vehicle corresponding to the terminal that sent the incomplete notification that would cause the load weight constraint to be not satisfied due to the delivery that could not be completed. The constraint determination process preferably includes, when there is work that would cause the load weight constraint to be not satisfied, sending information about the work that would cause the load weight constraint to be not satisfied to the terminal that sent the incomplete notification. In this case, the terminal can grasp that the load weight constraint will not be satisfied.

[0022] (6) The work in the first vehicle dispatch plan or the second vehicle dispatch plan may include the collection and the delivery. The first vehicle dispatch plan and the second vehicle dispatch plan are preferably generated such that the load weight of each of the plurality of vehicles satisfies the load weight constraint of each of the plurality of vehicles. The processing device is preferably configured to further execute a constraint determination process when receiving the incompletion notification. The constraint determination process preferably includes determining whether or not there is work in the vehicle corresponding to the terminal that sent the incompletion notification that would cause the load weight constraint to be not satisfied due to the delivery that could not be completed. The processing device is preferably configured to further execute a third generation process that generates a third vehicle dispatch plan when there is work that would cause the load weight constraint to be not satisfied. The third vehicle dispatch plan is preferably generated such that the vehicle corresponding to the terminal that sent the incompletion notification satisfies the load weight constraint. In this case, even if the load weight constraint is not satisfied, a third vehicle dispatch plan that satisfies the constraint is generated.

[0023] (7) The work included in the first or second dispatch plan preferably includes the delivery. The processing device is preferably configured to, upon receiving a redelivery request for an incomplete delivery, further execute a fourth generation process for generating a fourth dispatch plan to which redelivery based on the redelivery request is added. The redelivery request may include redelivery conditions. The fourth dispatch plan is preferably generated according to the redelivery conditions. The fourth generation process preferably includes, when it is not possible to generate the fourth dispatch plan in accordance with the redelivery conditions, sending a redelivery failure notification to a sender of the redelivery request indicating that redelivery in accordance with the redelivery conditions is not possible. In this case, the sender of the redelivery request can know that redelivery in accordance with the redelivery conditions is not possible.

[0024] (8) The redelivery impossibility notification is preferably configured to prompt the transmission of a redelivery request including other redelivery conditions different from the redelivery conditions. If the fourth generation process is unable to generate the fourth vehicle dispatch plan according to the redelivery conditions, it is preferable to repeat the transmission of the redelivery impossibility notification and the generation of the fourth vehicle dispatch plan according to the other redelivery conditions until the fourth vehicle dispatch plan according to the other redelivery conditions can be generated. In this case, an appropriate fourth vehicle dispatch plan is generated.

[0025] (9) A vehicle dispatch planning method according to an embodiment includes a step of generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a task of collecting and delivering luggage by a vehicle dispatch planning device, and a step of generating a second vehicle dispatch plan to which the task based on the request is added when the vehicle dispatch planning device receives a new request for a task including a task of collecting luggage. The second vehicle dispatch plan is generated by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited. In this case, it is possible to prevent the task based on the new request from being assigned to non-target vehicles.

[0026] (10) A vehicle dispatch system according to an embodiment includes a vehicle dispatch planning device and a plurality of terminals associated with a plurality of vehicles performing at least one of the tasks of collecting and delivering luggage. The vehicle dispatch planning device includes a processing device configured to execute a first generation process for generating a first vehicle dispatch plan for the plurality of vehicles, and a second generation process for generating a second vehicle dispatch plan to which the task based on the request is added when a new request for a task including luggage collection is received. The second generation process is configured to generate the second vehicle dispatch plan by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited. The terminal is configured to receive the first vehicle dispatch plan and the second vehicle dispatch plan from the vehicle dispatch planning device. In this case, it is possible to prevent the task based on the new request from being assigned to a non-target vehicle.

[0027] (11) A computer program according to an embodiment is a computer program for causing a computer to execute a first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of the tasks of collecting and delivering luggage, and a second generation process for generating a second vehicle dispatch plan to which the task based on the request is added when a new request for a task including luggage collection is received. The second generation process is configured to generate the second vehicle dispatch plan by assigning the task based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the task based on the request is prohibited. In this case, it is possible to prevent the task based on the new request from being assigned to non-target vehicles.

[0028] (12) Another computer program according to the embodiment is a computer program for causing a computer configured to receive a vehicle dispatch plan for performing work including delivery of luggage from a vehicle dispatch planning device to execute an incomplete delivery process. The vehicle dispatch plan is generated so that the weight of luggage to be loaded on a vehicle corresponding to the computer satisfies the load weight constraint of the vehicle. The incomplete delivery process includes, when the computer receives from a user an operation indicating that the delivery included in the vehicle dispatch plan could not be completed, displaying on the computer, among the work included in the vehicle dispatch plan, work that does not satisfy the load weight constraint due to the delivery that could not be completed, in distinction from other work included in the vehicle dispatch plan. In this case, it is easy to recognize the work that does not satisfy the load weight constraint.

[0029] Each of the aforementioned computer programs is stored on a computer-readable, non-transitory storage medium.

[0030] [Details of the embodiment of the present disclosure]

[0031] FIG. 1 shows a vehicle dispatch system 1 for vehicles that collect and deliver luggage. A vehicle may perform only one of collection and delivery. Collection means storing luggage. Delivery means delivering luggage to a delivery destination. Collection means loading luggage onto a vehicle. Delivery means unloading luggage from a vehicle. Hereinafter, collection and delivery are collectively referred to as "collection and delivery". The vehicle dispatch system 1 according to the embodiment includes a vehicle dispatch planning device 10 and a plurality of driver terminals 40A, 40B, and 40C. The vehicle dispatch planning device 10 is connected to the driver terminals 40A, 40B, and 40C via a network 70. The network 70 is, for example, a wireless network.

[0032] The driver terminals 40A, 40B, and 40C are held by the drivers of the multiple vehicles 31, 32, and 33. The driver terminals 40A, 40B, and 40C are configured, for example, by smartphones or tablet terminals. The driver terminals 40A, 40B, and 40C receive a vehicle allocation plan from the vehicle allocation planning device 10 and display the received vehicle allocation plan.

[0033] In the vehicle allocation planning device 10, the driver terminals 40A, 40B, and 40C are each associated with one of the vehicles 31, 32, and 33. In the embodiment, the multiple vehicles 31, 32, and 33 include a first vehicle 31, a second vehicle 32, and a third vehicle 33. The first driver terminal 40A is held by the driver of the first vehicle 31 and is associated with the first vehicle 31. Similarly, the second driver terminal 40B is held by the driver of the second vehicle 32 and is associated with the second vehicle 32. The third driver terminal 40C is held by the driver of the third vehicle 33 and is associated with the third vehicle 33. The driver terminals 40A, 40B, and 40C may be in-vehicle terminals mounted on the vehicles 31, 32, and 33. The number of driver terminals and vehicles included in the vehicle allocation system 1 is not particularly limited.

[0034] The vehicle dispatch system 1 of the embodiment further includes a plurality of user terminals 60A, 60B, and 60C. The users are, for example, customers who request collection or delivery of luggage. The user terminals 60A, 60B, and 60C transmit requests for collection or delivery of luggage to the vehicle dispatch planning device 10.

[0035] In the embodiment, the multiple user terminals 60A, 60B, 60C include a first user terminal 60A owned by a first user 51, a second user terminal 60B owned by a second user 52, and a third user terminal 60C owned by a third user 53. Each of the multiple user terminals 60A, 60B, 60C is connected to the vehicle allocation planning device 10 via a network 70. The number of user terminals included in the vehicle allocation system 1 is not particularly limited.

[0036] 2, the vehicle allocation planning device 10 is configured by a computer including a processing device 11 and a storage device 12 connected to the processing device 11. The computer configuring the vehicle allocation planning device 10 further includes a communication interface 15.

[0037] The processing device 11 includes, for example, a CPU. The storage device 12 includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, a RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The communication interface 15 is used for communication with an external device. The external device is, for example, a driver terminal 40A, 40B, or 40C or a user terminal 60A, 60B, or 60C.

[0038] The processing device 11 is configured to execute a vehicle dispatch management process 100. The processing device 11 is also configured to function as a vehicle dispatch planning engine 110. The storage device 12 stores a computer program 14 for causing a computer to operate as the vehicle dispatch planning device 10. The computer program 14 comprises program code for causing the processing device 11 to execute the vehicle dispatch management process 100. The computer program 14 comprises program code for causing the processing device 11 to execute operations as the vehicle dispatch planning engine 110. The processing device 11 reads out the computer program 14 from the storage device 12 and executes it.

[0039] The vehicle dispatch management process 100 includes a first generation process 101, a second generation process 102, a non-attendance process 103, a redelivery completion process 104, and a redelivery process 105. These processes 101, 102, 103, 104, and 105 will be described later. The vehicle dispatch management process 100 also functions as an application programming interface (API) for the driver terminals 40A, 40B, and 40C and the user terminals 60A, 60B, and 60C. That is, the vehicle dispatch management process 100 is responsible for communication between the driver terminals 40A, 40B, and 40C and the user terminals 60A, 60B, and 60C.

[0040] The vehicle dispatch planning engine 110 is used in the vehicle dispatch management process 100. The vehicle dispatch planning engine 110 is a software module that generates a vehicle dispatch plan. The vehicle dispatch planning engine 110 generates a vehicle dispatch plan based on one or more collection and delivery requests. The vehicle dispatch plan is generated by searching for a route that satisfies predetermined constraint conditions and allows each vehicle to travel efficiently. The predetermined constraint conditions are, for example, vehicle load weight constraints, the time when the vehicle departs from the vehicle base, the time when the vehicle returns to the vehicle base, the desired collection time of the package specified in the collection and delivery request, and the desired delivery time specified in the collection and delivery request.

[0041] In the vehicle dispatch plan, each of a number of vehicles is assigned a package to be collected or delivered. The vehicle dispatch plan also determines the order in which the vehicles will travel to collect and deliver the packages. The vehicle dispatch plan can be said to be a collection and delivery plan for each of a number of vehicles. The vehicle dispatch plan includes information such as the scheduled arrival time at the collection and delivery point, the scheduled departure time, and the vehicle's load weight at the time of departure (see Figure 6). The details of the vehicle dispatch plan will be described later.

[0042] The vehicle allocation management process 100 may be executed by a first computer, and the vehicle allocation planning engine 110 may be connected to a second computer connected to the first computer via a network. In other words, the vehicle allocation planning device 10 may be composed of multiple computers.

[0043] The storage device 12 of the vehicle allocation planning device 10 has a vehicle database 210 in which vehicle data relating to a plurality of vehicles 31, 32, 33 used for collecting or delivering packages is registered. The vehicle data included in the vehicle database 210 is used to generate a vehicle allocation plan.

[0044] FIG. 3 shows an example of the vehicle database 210. The vehicle database 210 has, for example, a vehicle ID, a vehicle name, a load weight constraint, and a target vehicle flag for each vehicle. The vehicle ID indicates an identifier for each vehicle. The vehicle name indicates the name of the vehicle. The load weight constraint indicates the maximum weight of luggage that can be loaded on the vehicle. The target vehicle flag indicates whether each vehicle is a target vehicle or not. The target vehicle flag is used to determine a vehicle to which a task is assigned in the second generation process 102 described later, etc. A "target vehicle" refers to a vehicle to which a collection or delivery task can be assigned in the generation of a vehicle dispatch plan. In the vehicle database 210, the target vehicle flag is set for the target vehicle. Here, "set" refers to the target vehicle flag being assigned a value of "1". In addition, in the vehicle database 210, the target vehicle flag is reset for the non-target vehicle. Here, "reset" refers to the target vehicle flag being assigned a value of "0". For example, new tasks are prohibited from being assigned to the non-target vehicle. In this embodiment, the initial value of the target vehicle flag is set to "1".

[0045] For example, in the vehicle database 210 of Fig. 3, the first vehicle 31 has a vehicle ID of C0001 and a vehicle name of V1. The first vehicle 31 has a load weight constraint (maximum load capacity) of 350 kg and can carry up to 350 kg of luggage. The first vehicle 31 is a target vehicle because the target vehicle flag is set. The second vehicle 32 has a vehicle ID of C0002 and a vehicle name of V2. The second vehicle 32 is a non-target vehicle because the load weight constraint is 350 kg and the target vehicle flag is reset.

[0046] Returning to Fig. 2, the storage device 12 has a request database 220. The request database 220 stores a plurality of requests received by the vehicle allocation planning device 10 from a plurality of user terminals 60A, 60B, 60C. The requests are, for example, a collection / delivery request from a user who wishes to collect a package and deliver it to a delivery destination, a delivery request from a user who is to be the delivery destination, or a redelivery request from a delivery destination user who was absent.

[0047] The collection request includes information such as the weight of the package, the collection point, the desired collection time, the contact information for the collection point, the delivery point, the desired delivery time, and the contact information for the delivery point. The delivery request includes information such as the delivery point, the desired delivery time, and the contact information for the delivery point. The redelivery request includes information such as the delivery point, the desired redelivery time, and the contact information for the delivery point.

[0048] The storage device 12 has a vehicle dispatch plan database 230. The vehicle dispatch plan database 230 stores a vehicle dispatch plan generated by the vehicle dispatch plan engine 110 of the vehicle dispatch planning device 10.

[0049] The first driver terminal 40A is configured by a computer including a processing device 41 and a storage device 42 connected to the processing device 41. The computer configuring the driver terminal 40A further includes a communication interface 45 and a display 46. The configurations of the other driver terminals 40B and 40C are similar to the configuration of the first driver terminal 40A. As described above, the computers configuring the driver terminals 40A, 40B, and 40C are, for example, smartphones or tablet terminals.

[0050] The processing device 41 has, for example, a CPU. The storage device 42 has, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, a RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The communication interface 45 is used for communication with an external device. The external device is, for example, the vehicle allocation planning device 10 or user terminals 60A, 60B, 60C.

[0051] The processing device 41 is configured to acquire a vehicle dispatch plan from the vehicle dispatch planning device 10 and execute a process of displaying the acquired vehicle dispatch plan. The processes executed by the processing device 41 include a non-delivery process 400 (delivery incomplete process) described below. The storage device 42 stores a computer program 44 for operating a computer as the driver terminal 40A. The computer program 44 includes program code for causing the processing device 41 to execute necessary processes. The processing device 41 reads out the computer program 44 from the storage device 42 and executes it.

[0052] The first user terminal 60A is configured by a computer such as a smartphone or a tablet terminal, similar to the driver terminals 40A, 40B, and 40C. The first user terminal 60A has a dedicated application program used in connection to the vehicle allocation planning device 10, or a browser for connecting to the vehicle allocation planning device 10. The dedicated application program or browser provides the user with an environment for realizing necessary display and operation, as well as communication with the vehicle allocation planning device 10. The configurations of the other user terminals 60B and 60C are similar to the configuration of the first user terminal 60A.

[0053] 4 and 5 show a first generation process 101 executed by the vehicle allocation planning device 10. In the first generation process 101, the vehicle allocation planning engine 110 is used to generate, for example, a first vehicle allocation plan 230A as shown in FIG.

[0054] 4, in the first generation process 101, when a predetermined time T arrives (step S11), a first vehicle allocation plan is generated. The predetermined time T is, for example, a time before the start of business for the day, for example, 8:30. In the first vehicle allocation plan, for example, a route order for collection and delivery to be performed by each of the multiple vehicles 31, 32, 33 during the day is determined.

[0055] When a predetermined time T arrives, the processing device 11 executing the first generation process 101 acquires requests such as collection and delivery requests that have been collected by the vehicle dispatch planning device 10 by the predetermined time T from the request database 220 (step S12). The requests that have been collected by the predetermined time T are provided from the first generation process 101 to the vehicle dispatch planning engine 110. In addition, all vehicle data included in the vehicle database 210 is provided to the vehicle dispatch planning engine 110 as target vehicle data to which a collection and delivery operation is assigned. In addition, the vehicle dispatch planning engine 110 is provided with constraint conditions other than the constraint conditions included in the requests.

[0056] The vehicle allocation plan engine 110 generates a vehicle allocation plan to satisfy predetermined constraints (step S12). The vehicle allocation plan engine 110 generates a first vehicle allocation plan for handling requests received by a predetermined time T, with all vehicles as target vehicles for allocation. Collection and delivery work based on requests received by the predetermined time T is assigned to one of multiple target vehicles. The generated first vehicle allocation plan is stored in the vehicle allocation plan database 230.

[0057] As described above, the constraint conditions when generating a vehicle dispatch plan include the vehicle load constraint, the time when the vehicle departs from the vehicle base, the time when the vehicle returns to the vehicle base, the desired pickup time of the package specified in the collection / delivery request, and the desired delivery time specified in the collection / delivery request. Of these constraint conditions, the vehicle load constraint is included in the target vehicle data. In addition, the desired pickup time and the desired delivery time are included in the collection / delivery request. The time when the vehicle departs from the vehicle base and the time when the vehicle returns to the vehicle base are provided to the vehicle dispatch plan engine 110 from the first generation process 101 as other constraint conditions.

[0058] Around the start of business hours of the day, each driver operates the driver terminal 40A, 40B, 40C to transmit a plan acquisition request and acquires a first vehicle allocation plan, which is an initial plan for the day, from the vehicle allocation planning device 10. When the processing device 11 receives the plan acquisition request from the driver terminal 40A, 40B, 40C, it transmits the first vehicle allocation plan to the driver terminal 40A, 40B, 40C (step S14).

[0059] FIG. 6 shows an example of the generated first vehicle allocation plan 230A. The first vehicle allocation plan 230A shown in FIG. 6 includes plans for the first vehicle 31 (vehicle name: V1) and the second vehicle 32 (vehicle name: V2). The first vehicle allocation plan 230A may include plans for other vehicles. The processing device 11 transmits data indicating the plan for the first vehicle 31 (vehicle name: V1) from the first vehicle allocation plan to the driver terminal 40A corresponding to the first vehicle 31. In addition, the processing device 11 transmits data indicating the plan for the second vehicle 32 (vehicle name: V2) from the first vehicle allocation plan to the driver terminal 40B corresponding to the second vehicle 32.

[0060] In the plan for the first vehicle 31 (vehicle name: V1) shown in Fig. 6, the first vehicle 31 is assigned to collect and deliver packages B1, B2, and B3. In this plan, the first vehicle 31 is scheduled to depart from point P0, which is the vehicle base, at 9:00, visit points P1, P2, P3, P4, P5, and P6 in that order, and then return to point P0, which is the vehicle base. The scheduled return time is 11:40. The scheduled arrival and departure times for each of points P1, P2, P3, and P4 are as shown in Fig. 6.

[0061] In the first vehicle dispatch plan 230A, the load weight of the first vehicle 31 when departing from point P0, which is the vehicle base, is 0 kg. At point P1, 100 kg of luggage B1 is collected. Therefore, the load weight when departing from point P1 is 100 kg. At point P2, 100 kg of luggage B2 is collected. Therefore, the load weight when departing from point P2 is 200 kg. At point P3, 100 kg of luggage B1 is delivered. Therefore, the load weight when departing from point P3 is 100 kg. At point P4, 100 kg of luggage B3 is collected. Therefore, the load weight when departing from point P4 is 200 kg. At point P5, 100 kg of luggage B3 is delivered. Therefore, the load weight when departing from point P5 is 100 kg. At point P6, 100 kg of luggage is delivered. Therefore, the load weight when departing from point P6 is 0 kg.

[0062] In the plan for the second vehicle 32 (vehicle name: V2) shown in Fig. 6, the second vehicle 32 is assigned to collect and deliver packages B4 and B5. In this plan, the second vehicle 32 is scheduled to depart from point P0, which is the vehicle base, at 9:00, visit points P7, P8, P9, and P10 in that order, and then return to point P0, which is the vehicle base. The scheduled return time is 12:00. The scheduled arrival and departure times for each of points P7, P8, P9, and P10 are as shown in Fig. 6.

[0063] In the first vehicle allocation plan 230A, the load weight of the second vehicle 32 when departing from point P0, which is the vehicle base, is 0 kg. At point P7, 150 kg of luggage B4 is collected. Therefore, the load weight when departing from point P7 is 150 kg. At point P8, 150 kg of luggage B5 is collected. Therefore, the load weight when departing from point P8 is 300 kg. At point P9, 150 kg of luggage B4 is delivered. Therefore, the load weight when departing from point P9 is 150 kg. At point P10, 150 kg of luggage is delivered. Therefore, the load weight when departing from point P10 is 0 kg.

[0064] As shown in Fig. 3, the load weight constraint of each of the first vehicle 31 (vehicle name: V1) and the second vehicle 32 (vehicle name: V2) is 350 kg. In the first vehicle allocation plan 230A, the load weight at the time of departure at any point does not exceed the load weight constraint. Therefore, the first vehicle allocation plan 230A is generated so as to satisfy the load weight constraint of each of the first vehicle 31 and the second vehicle 32.

[0065] 7 shows a display screen of the first vehicle dispatch plan transmitted to the first driver terminal 40A. When the first driver terminal 40A receives the first vehicle dispatch plan from the vehicle dispatch planning device 10, the display screen displays the first vehicle dispatch plan on the display 46 of the driver terminal 40A. The driver who owns the first driver terminal 40A collects and delivers packages according to the vehicle dispatch plan displayed on the display 46. The vehicle dispatch plan is similarly displayed on the other driver terminals 40B and 40C.

[0066] The vehicle dispatch plan display screen shown in FIG. 7 displays the location and its address, type, baggage, arrival time, departure time, loaded weight at departure, and status. The location and its address, type, baggage, arrival time, departure time, and loaded weight at departure are displayed according to the information included in the vehicle dispatch plan received by the driver terminal 40A. The "status" included in the vehicle dispatch plan display screen indicates whether the work at each location has been completed. In FIG. 7, the "status" for the locations P0, P1, and P2 is "completed," which indicates that the departure from the location P0 to the collection at the location P2 has been completed according to the vehicle dispatch plan. It also indicates that the collection and delivery work after the location P4 is not completed. The "status" for each time point is updated by the driver's operation of the driver terminal 40A. When the completion of the work at each location is input by the operation of the driver terminal 40A, the "status" of the location is updated to a display indicating "completed." In addition, a notification that the work at each location has been completed is transmitted from the driver terminal 40A to the vehicle dispatch plan device 10.

[0067] When the delivery destination is absent at a certain location, the "status" is updated to "absent" by the driver's operation of the driver terminal 40A. Furthermore, absence information indicating that the delivery destination was absent at that location is transmitted from the driver terminal 40A to the vehicle allocation planning device 10. The absence information is also a delivery incomplete notification indicating that the package could not be delivered to that location. The process executed by the driver terminal 40A when the delivery destination is absent (absent process 400; delivery incomplete process) will be described later.

[0068] When redelivery to the absent location is completed, the "status" is updated from "absent" to "completed" by the driver's operation of the driver terminal 40A. Also, a redelivery completion notice indicating that redelivery has been completed is transmitted from the driver terminal 40A to the vehicle allocation planning device 10.

[0069] 8 shows absence processing 103 (delivery incompletion processing) executed in the vehicle allocation planning device 10. The processing device 11 of the vehicle allocation planning device 10 receives absence information (delivery incompletion notification) from any of the multiple driver terminals 40A, 40B, 40C (step S21). Here, it is assumed that the processing device 11 receives absence information from the second driver terminal 40B corresponding to the second vehicle 32.

[0070] When the processing device 11 executing the absence process 103 receives absence information from the second driver terminal 40B, it resets the target vehicle flag of the second vehicle 32 (vehicle name: V2) corresponding to the second driver terminal 40B in the vehicle database 210 (step S22). The vehicle database 210 shown in FIG. 3 shows a state in which the target vehicle flag of the second vehicle 32 (vehicle name: V2) is reset. By resetting the target vehicle flag, the second vehicle 32 is treated as a non-target vehicle in the generation process of the vehicle dispatch plan executed thereafter. The allocation of work based on a new request to the non-target vehicle is prohibited. This point will be described in detail later.

[0071] Next, the processing device 11 executes the constraint determination process 103A. The constraint determination process 103A is a process for determining whether or not the current vehicle dispatch plan satisfies the load weight constraint when the package cannot be delivered due to absence. The details of the constraint determination process 103A will be described later.

[0072] The processing device 11 transmits an absence notification to the contact information of the delivery point where the user was absent (for example, a user terminal owned by the user of the delivery point) (step S24). The user who receives the absence notification can understand that the package was not delivered. The absence notification preferably prompts the user to transmit a redelivery request including a desired time period for redelivery.

[0073] 9 shows the redelivery completion process 104 executed in the vehicle allocation planning device 10. As described above, when redelivery to the absent delivery destination is completed, a redelivery completion notice is transmitted from the driver terminal 40B to the vehicle allocation planning device 10.

[0074] The processing device 11 executing the redelivery completion process 104 receives a redelivery completion notification from the second driver terminal 40B (step S31). Then, the processing device 11 sets a target vehicle flag for the second vehicle 32 (vehicle name: V2) corresponding to the second driver terminal 40B in the vehicle database 210 (step S32). By setting the target vehicle flag, the second vehicle 32 is treated as a target vehicle in the vehicle allocation plan generation process executed thereafter. The target vehicle becomes a candidate for work allocation based on a new request. This point will be described in detail later.

[0075] 10 and 11 show a second generation process 102 executed by the vehicle allocation planning device 10. In the second generation process 102, a second vehicle allocation plan is generated. The second vehicle allocation plan is generated when a request such as a collection / delivery request from a user occurs after the first vehicle allocation plan 230A is generated. The second vehicle allocation plan is generated by updating the first vehicle allocation plan so that an operation based on the new request is added.

[0076] 10 and 11, the processing device 11 executing the second generation process 102 receives a new parcel collection / delivery request from, for example, the third user terminal 60C (step S41). In this case, a vehicle currently performing collection / delivery or a vehicle that is not currently in operation is assigned the collection or delivery based on the new collection / delivery request. However, in this embodiment, a non-target vehicle whose target vehicle flag in the vehicle database 210 has been reset is not assigned the collection or delivery based on the new collection / delivery request.

[0077] Specifically, the processing device 11 refers to the target vehicle flag in the vehicle database 210 and determines whether each of the multiple vehicles is a target vehicle or a non-target vehicle (step S42). Here, a target vehicle is a vehicle whose target vehicle flag is set, and a non-target vehicle is a vehicle whose target vehicle flag is reset. In the vehicle database 210 shown in Fig. 3, as an example, the second vehicle (vehicle name: V2) is a non-target vehicle, and all other vehicles are target vehicles.

[0078] Next, the processing device 11 uses the vehicle dispatch plan engine 110 to generate a second vehicle dispatch plan that assigns the new collection / delivery request to any of the vehicles (target vehicles) excluding the second vehicle 32, which is a non-target vehicle (step S43). That is, the first vehicle dispatch plan is updated so that a collection / delivery operation based on the new collection / delivery request is added. The generated second vehicle dispatch plan is stored in the vehicle dispatch plan database 230.

[0079] In the second generation process 102, the new collection / delivery request and target vehicle data excluding the second vehicle 32, which is a non-target vehicle, are provided to the vehicle dispatch planning engine 110. The vehicle dispatch planning engine 110 assigns the collection / delivery work based on the new collection / delivery request to, for example, a vehicle among the multiple target vehicles that can most efficiently perform the collection / delivery work based on the new collection / delivery request. In this embodiment, the work based on the new request is assigned to target vehicles excluding the non-target vehicles. The work based on the new request is assigned, for example, to the first vehicle 31, which is a target vehicle.

[0080] Fig. 12 shows an example of the second vehicle allocation plan 230B for the first vehicle 31. In Fig. 12, a new collection operation of package B6 at point P11 has been added between points P4 and P5 in the first vehicle allocation plan. Also, in Fig. 12, a new delivery operation of package B6 at point P12 has been added between points P6 and P0 in the first vehicle allocation plan. Also, with the addition of the collection and delivery operation of package B6, the arrival times and departure times from point P5 onwards following point P11 have been changed from those in the first vehicle allocation plan.

[0081] According to this embodiment, it is possible to prevent a task based on a new request from being assigned to a non-target vehicle such as the second vehicle 32. In other words, in this embodiment, it is possible to control whether or not a task based on a new request is assigned to each vehicle. As a result, it is possible to prevent a task from being assigned to a vehicle that would cause a problem if the task based on a new request is assigned to the vehicle.

[0082] For example, according to the original first vehicle dispatch plan, it may be more efficient to assign collection and delivery work based on a new collection and delivery request to the second vehicle 32 rather than the first vehicle 31. In this case, if it is not possible to control whether or not work based on a new request is assigned to each vehicle, the vehicle dispatch plan engine 110 may assign collection and delivery work based on the new collection and delivery request to the second vehicle 32. However, the second vehicle 32 has a package that could not be delivered due to an absence, and is in a situation where redelivery is required. In this way, the second vehicle 32 is in a situation where work different from the original first vehicle dispatch plan is required. If work based on a new request is assigned to such a second vehicle 32, problems such as a delay in redelivery may occur.

[0083] Another case in which a problem occurs when a task based on a new request is assigned is when the actual vehicle operation is delayed from the original vehicle dispatch plan due to traffic congestion. In such a case, the vehicle operation may be further delayed when a task based on a new request is assigned. The vehicle dispatch planning device 10 can also treat such vehicles as non-target vehicles.

[0084] In the vehicle database 210 of this embodiment, the target vehicle flag is reset when redelivery is completed. Therefore, in this embodiment, even if a vehicle corresponds to a driver terminal that has transmitted absence information (delivery incomplete notice) to the vehicle allocation planning device 10, a vehicle corresponding to a driver terminal that has transmitted a redelivery completion notice to the vehicle allocation planning device 10 returns from a non-target vehicle to a target vehicle.

[0085] Therefore, in this embodiment, a non-target vehicle is a vehicle, among the multiple vehicles 31, 32, 33, that corresponds to a driver terminal that has transmitted absence information (delivery incomplete notice) to the vehicle dispatch planning device 10. Moreover, a non-target vehicle is a vehicle that corresponds to a driver terminal that has not transmitted a redelivery completion notice, indicating that an uncompleted delivery has been completed, to the vehicle dispatch planning device 10. In other words, in this embodiment, each vehicle is a non-target vehicle from the time the driver terminal corresponding to the vehicle transmits absence information to the time it transmits a redelivery completion notice.

[0086] Furthermore, the non-target vehicles may be, but are not limited to, all of one or more vehicles for which the target vehicle flag is reset in the vehicle database 210. That is, even if the target vehicle flag is reset in the vehicle database 210, a vehicle that satisfies a predetermined condition may be excluded from the non-target vehicles. For example, the vehicle allocation planning device 10 tentatively assigns a collection and delivery task based on a new collection and delivery request to a vehicle for which the target vehicle flag is reset. Then, the vehicle allocation planning device 10 can treat a vehicle that is determined to cause a hindrance to redelivery (re-execution of a delivery that could not be completed due to absence) when a new collection and delivery task is assigned as a non-target vehicle. The criterion for determining whether or not a hindrance will occur in redelivery is, for example, whether or not the redelivery will be delayed from a predetermined time.

[0087] Now, when the processing device 11 generates the second vehicle allocation plan 230B including the work based on the new request, it transmits the second vehicle allocation plan 230B to the first driver terminal 40A corresponding to the first vehicle 31 to which the work based on the new request is assigned (step S44). The driver of the first vehicle 31 carries out collection and delivery according to the new second vehicle allocation plan 230B.

[0088] Fig. 13 shows the procedure of the constraint determination process 103A shown in Fig. 8. As described above, the constraint determination process 103A is executed when the vehicle dispatch planning device 10 receives absence information (notification of incomplete delivery). The absence information is transmitted from the driver terminal to the vehicle dispatch planning device 10 when a package cannot be delivered because the driver is absent from a delivery point while the driver is performing a delivery operation according to a vehicle dispatch plan. The absence information includes the time when the absence information was transmitted, the point where the driver was absent, and information on the package that could not be delivered because of the driver's absence.

[0089] If a delivery point is not available, the package that should have been removed from the vehicle for delivery remains on the vehicle. Therefore, even if the original vehicle dispatch plan (first vehicle dispatch plan) satisfies the vehicle load weight constraint, once an unattended delivery point occurs, there is no guarantee that the load weight constraint will be satisfied. The constraint determination process 103A determines whether the load weight constraint is satisfied when an unattended delivery point occurs.

[0090] The processing device 11 executing the constraint determination process 103A determines whether or not there is any work (a location where the work is performed) that will not satisfy the load weight constraint due to absence (step S51). If there is any work that will not satisfy the load weight constraint, the processing device 11 generates a reply including information (constraint information) regarding the work that will not satisfy the load weight constraint (step S52). The constraint information indicates, for example, among the work included in the dispatch plan, the work that will not satisfy the load weight constraint. The reply here is a reply to the absence information (delivery incomplete notice) sent from the driver terminal. If there is no work that will not satisfy the load weight constraint, the processing device 11 generates a normal reply (step S53). The normal reply is a reply to the absence information (delivery incomplete notice) sent from the driver terminal, and does not include the above-mentioned constraint information.

[0091] Then, the processor 11 transmits the reply generated in step S52 or step S53 to the driver terminal that transmitted the absence information.

[0092] FIG. 14 shows the procedure of absence processing 400 (delivery incomplete processing) in the driver terminal 40A, 40B, 40C. The absence processing 400 is started by the absence operation of the driver when the driver is absent from the delivery point and cannot deliver the parcel during the delivery work according to the vehicle dispatch plan. When the driver performs the absence operation on the driver terminal 40A, 40B, 40C (step S61), the driver terminal 40A, 40B, 40C accepts the absence operation. The driver terminal 40A, 40B, 40C to which the absence operation is applied transmits absence information (delivery incomplete notification) to the vehicle dispatch planning device 10 (step S62). The vehicle dispatch planning device 10 that receives the absence information generates and transmits a reply to the driver terminal 40A, 40B, 40C in the constraint determination process 103A (see FIG. 13).

[0093] The driver terminal 40A, 40B, 40C that transmitted the absence information receives a reply from the vehicle dispatch planning device 10 (step S63). When the received reply includes constraint information related to the work that does not satisfy the load weight constraint (step S64), the driver terminal 40A, 40B, 40C that received the reply displays the work in a predetermined highlighted manner (step S65). The predetermined highlighted manner is to display the work that does not satisfy the load weight constraint among the works included in the vehicle dispatch plan displayed on the display 46 so as to be distinguished from other works. In the above description, the vehicle dispatch planning device 10 determines whether the vehicle corresponding to the driver terminal 40A, 40B, 40C that transmitted the absence information satisfies the load weight constraint, but the driver terminal 40A, 40B, 40C may perform the determination.

[0094] FIG. 15 shows an example of a dispatch plan display screen displayed on the display 46 of the first driver terminal 40A corresponding to the first vehicle 31 when the first vehicle 31 is unable to perform delivery at the point P3 due to the absence of the driver. Here, it is assumed that the driver terminal 40A corresponding to the first vehicle 31 has received the second dispatch plan 230B shown in FIG. 12. FIG. 15 shows that the driver of the first vehicle 31 performed collection and delivery work according to the second dispatch plan, but was absent at the point P3. Since the driver was absent at the point P3, the cargo to be unloaded at the point P3 remains loaded on the first vehicle 31. Therefore, the load weight at the time of departure from the point P3 is updated to 200 kg, not 100 kg in the second dispatch plan (or the first dispatch plan). In addition, the load weight at the time of departure from the point P3 onwards is also increased by 100 kg each. Therefore, the load weight at the time of departure at the point P11 is 400 kg, which exceeds the load weight constraint of 350 kg (see FIG. 3) of the first vehicle 31. In FIG. 15, the portion showing the collection work at the point P11 is highlighted. The highlighting is, for example, a display that is shown in a different color from the work at other points.

[0095] A display such as that shown in FIG. 15 is useful for alerting the driver to the load weight.

[0096] Fig. 16 shows another example of the constraint determination process 103A shown in Fig. 8. In the constraint determination process 103A shown in Fig. 16, when there is an inappropriate work that does not satisfy the load weight constraint due to absence, a third vehicle allocation plan is generated so as to satisfy the load weight constraint.

[0097] The processing device 11, which executes the constraint determination process 103A shown in Fig. 16, determines whether there is any inappropriate work (a location where the work is performed) that will not satisfy the load weight constraint due to absence (step S81). If there is any inappropriate work that will not satisfy the load weight constraint, the processing device 11 refers to the target vehicle flag in the vehicle database 210 and determines whether each of the multiple vehicles is a target vehicle or a non-target vehicle (step S82).

[0098] Next, the processing device 11 uses the vehicle allocation plan engine 110 to generate a third vehicle allocation plan that assigns the unsuitable work to one of a plurality of vehicles (target vehicles) excluding the second vehicle 32, which is a non-target vehicle, and the first vehicle 31, which does not meet the load weight requirement (step S83). That is, the third vehicle allocation plan is generated by updating the current vehicle allocation plan (first vehicle allocation plan or second vehicle allocation plan) so that the unsuitable work is assigned to one of the target vehicles. Step S83 corresponds to the third generation process 103B shown in FIG. 1. The generated third vehicle allocation plan is stored in the vehicle allocation plan database 230. The unsuitable work is assigned to, for example, the third vehicle 33.

[0099] The processing device 11 transmits the third dispatch plan to the third driver terminal 40C corresponding to the third vehicle 33 (step S84). In addition, the processing device 11 transmits a reply of the absence information to the first driver terminal 40A that transmitted the absence information (step S85).

[0100] FIG. 17 shows a redelivery process 105 (see FIG. 1) executed in the vehicle dispatch planning device 10. In the redelivery process 105, a fourth vehicle dispatch plan is generated for redelivery of a parcel that could not be delivered due to absence. The processing device 11 that executes the redelivery process 105 receives a redelivery request from the user terminals 60A, 60B, and 60C of the delivery destination users who were absent (step S71). Then, the processing device 11 generates a fourth vehicle dispatch plan in which redelivery is assigned to a vehicle carrying the parcel to be redelivered (step S72). The redelivery request is transmitted from the user terminals 60A, 60B, and 60C to the vehicle dispatch planning device 10 in response to the absence notification transmitted from the vehicle dispatch planning device 10 (see step S24 in FIG. 8). The redelivery request includes information that identifies the parcel to be redelivered, and may include redelivery conditions such as a redelivery point and a desired redelivery time zone. The redelivery point may be different from the original delivery point.

[0101] The fourth vehicle dispatch plan is generated by allocating the re-dispatch task to a current vehicle dispatch plan for a vehicle carrying the cargo to be re-dispatched. The fourth vehicle dispatch plan is generated using the vehicle dispatch plan engine 110 according to the re-dispatch conditions.

[0102] The vehicle dispatching plan engine 110 generates a fourth vehicle dispatching plan so that the vehicle to be redelivered visits the redelivery point between the point to be visited next and the return point. The vehicle dispatching plan engine 110 generates a fourth vehicle dispatching plan to visit the redelivery point so as to satisfy the constraint conditions of the desired redelivery time zone, the desired time zones of unexecuted collection and delivery, and the return time to the vehicle base, included in the redelivery request (step S72). That is, the current vehicle dispatching plan (the first vehicle dispatching plan, the second vehicle dispatching plan, or the third vehicle dispatching plan) is updated so that redelivery is assigned, thereby generating the fourth vehicle dispatching plan. When multiple candidates for the fourth vehicle dispatching plan that satisfy the constraint conditions are generated, the plan with the earliest return time of the vehicle is output as the fourth vehicle dispatching plan. Note that step S72 corresponds to the fourth generation process 105A shown in FIG. 1. The generated fourth vehicle dispatching plan is stored in the vehicle dispatching plan database 230.

[0103] However, depending on the desired redelivery time slot, there are cases where a fourth vehicle allocation plan that satisfies the constraint conditions including the redelivery conditions cannot be generated. Therefore, in step S73, the processing device 11 judges whether or not a fourth vehicle allocation plan that satisfies the constraint conditions has been generated. If the fourth vehicle allocation plan cannot be generated, the processing device 11 transmits a redelivery impossible notice to the user terminal that is the sender of the redelivery request (step S74). The redelivery impossible notice is a notice to inform the user that redelivery according to the redelivery conditions is not possible. The redelivery impossible notice may be a notice that prompts the user to input or select another desired redelivery time slot. The redelivery impossible notice may include one or more redelivery possible time slots that the user can select.

[0104] A user who receives the notification that redelivery is not possible can operate the user terminal to send a redelivery request again including other redelivery conditions, such as a different desired redelivery time period.

[0105] The vehicle allocation planning device 10 according to the embodiment is configured to repeat step S74 and step S72 when the fourth vehicle allocation plan according to the redelivery condition cannot be generated, until the fourth vehicle allocation plan according to the other redelivery condition can be generated. Step S74 is to transmit a notification that redelivery is not possible, and step S72 is to generate a fourth vehicle allocation plan according to the other redelivery condition. Therefore, the generation of the fourth vehicle allocation plan is repeated until redelivery according to the user's desire becomes possible.

[0106] When the processing device 11 can generate a fourth dispatch plan according to the redelivery conditions, the processing device 11 transmits the fourth dispatch plan to the driver terminal corresponding to the vehicle responsible for redelivery (step S75). According to this embodiment, the redelivery request is prevented from being directly transmitted to the driver terminal. Instead, when the fourth dispatch plan according to the redelivery conditions is generated, the fourth dispatch plan is transmitted to the driver terminal. The generated fourth dispatch plan satisfies the constraints of the desired time slots for unexecuted collection and delivery, and the return time to the vehicle base, and is therefore easily executable by the driver. Thus, according to this embodiment, it is possible to prevent a redelivery request including redelivery conditions that are difficult for the driver to execute from being transmitted to the driver terminal.

[0107] It should be noted that the embodiments disclosed herein are illustrative and not restrictive in all respects. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include the equivalent meaning of the claims and all modifications within the scope. [Explanation of symbols]

[0108] 1: Vehicle dispatch system 10: Vehicle dispatch planning device 11: Processing device 12:Storage device 14: Computer Programs 15: Communication interface 31: First car 32: Second car 33: Third car 40A: First driver terminal 40B: Second driver terminal 40C: 3rd driver terminal 41: Processing equipment 42: Storage device 44: Computer Programs 45: Communication interface 46: Display 51: First user 52: Second user 53: Third user 60A: First user terminal 60B: Second user terminal 60C: Third user terminal 70: Network 100: Vehicle dispatch management processing 101: First generation process 102: Second generation process 103: Absence processing 103A: Constraint Judgment Processing 103B: Third generation process 104: Redelivery completion process 105: Redelivery process 105A: 4th generation process 110: Vehicle dispatching engine 210: Vehicle database 220: Request Database 230: Vehicle allocation plan database 230A: First dispatch plan 230B: Second dispatch plan 400: Absence Processing B1: Luggage B2: Luggage B3: Luggage B4: Luggage B5: Luggage B6: Luggage P0 :Point P1: Point P10: Point P11: Point P12: Point P2: Point P3: Location P4 : Location P5 : Location P6 : Location P7 : Location P8 : Location P9 : Location

Claims

1. A first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a collection operation and a delivery operation of a package; a second generation process for generating a second vehicle dispatch plan to which the operation based on a new request for the operation including a package pickup is added when a new request for the operation including a package pickup is received; a processor configured to execute The second generation process includes: the second vehicle allocation plan is generated by allocating the work based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the allocation of the work based on the request is prohibited; The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, The non-target vehicle is a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete. Vehicle dispatch planning device.

2. A first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a collection operation and a delivery operation of a package; a second generation process for generating a second vehicle dispatch plan to which the operation based on a new request for the operation including a package pickup is added when a new request for the operation including a package pickup is received; a processor configured to execute The second generation process includes: the second vehicle allocation plan is generated by allocating the work based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the allocation of the work based on the request is prohibited; The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, The non-target vehicle is a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete, and is a vehicle that has been determined to cause an impediment to re-executing the incomplete delivery if the work based on the request is assigned to the vehicle. Vehicle dispatch planning device.

3. A first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a collection operation and a delivery operation of a package; a second generation process for generating a second vehicle dispatch plan to which the operation based on a new request for the operation including a package pickup is added when a new request for the operation including a package pickup is received; a processor configured to execute The second generation process includes: the second vehicle allocation plan is generated by allocating the work based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the allocation of the work based on the request is prohibited; The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, The non-target vehicle is a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete, and a vehicle that corresponds to a terminal that has not transmitted a completion notification indicating that the incomplete delivery has been completed. Vehicle dispatch planning device.

4. The operation in the first vehicle dispatch plan or the second vehicle dispatch plan includes the collection and the delivery, the first vehicle dispatch plan and the second vehicle dispatch plan are generated such that a load weight of each of the plurality of vehicles satisfies a load weight constraint of each of the plurality of vehicles; the processing device is configured to further execute a constraint determination process when the processing device receives the incompletion notification; The constraint determination process includes: determining whether or not there is any work that would result in the load weight constraint not being satisfied due to the delivery that could not be completed in the vehicle corresponding to the terminal that transmitted the incompletion notification; and when there is an operation that does not satisfy the load weight constraint, transmitting information about the operation that does not satisfy the load weight constraint to the terminal that transmitted the incompletion notification. The vehicle allocation planning device according to any one of claims 1 to 3.

5. The operation in the first vehicle dispatch plan or the second vehicle dispatch plan includes the collection and the delivery, the first vehicle dispatch plan and the second vehicle dispatch plan are generated such that a load weight of each of the plurality of vehicles satisfies a load weight constraint of each of the plurality of vehicles; the processing device is configured to further execute a constraint determination process when the processing device receives the incompletion notification; the constraint determination process includes determining whether or not there is any work that does not satisfy the load weight constraint due to the presence of the delivery that could not be completed in the vehicle corresponding to the terminal that transmitted the incompletion notification; the processing device is configured to further execute a third generation process of generating a third vehicle dispatch plan when the work does not satisfy the load weight constraint; The third vehicle dispatch plan is generated so that the vehicle corresponding to the terminal that has transmitted the incompletion notification satisfies the loading weight constraint. The vehicle allocation planning device according to any one of claims 1 to 3.

6. The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, The processing device is configured to further execute a fourth generation process of generating a fourth vehicle dispatch plan to which a redelivery based on the redelivery request is added when the processing device receives a redelivery request for the incomplete delivery, The redelivery request includes redelivery conditions; The fourth vehicle dispatch plan is generated according to the redelivery condition, The fourth generation process includes, when the fourth vehicle dispatch plan in accordance with the redelivery conditions cannot be generated, transmitting a redelivery impossibility notice indicating that redelivery in accordance with the redelivery conditions cannot be performed to a source of the redelivery request. The vehicle allocation planning device according to any one of claims 1 to 5.

7. The notification of non-redistribution is configured to prompt the sending of a redelivery request including a redelivery condition different from the redelivery condition; The fourth generation process is configured to, when the fourth vehicle dispatch plan according to the redelivery condition cannot be generated, repeat the transmission of the redelivery impossibility notification and the generation of the fourth vehicle dispatch plan according to the other redelivery condition until the fourth vehicle dispatch plan according to the other redelivery condition can be generated. The vehicle allocation planning device according to claim 6.

8. A step in which a vehicle dispatch planning device generates a first vehicle dispatch plan for a plurality of vehicles that perform at least one of a collection operation and a delivery operation of a package; a step of generating a second vehicle dispatch plan to which the operation based on the request is added when the vehicle dispatch planning device receives a new request for the operation including a pickup of luggage; Equipped with the second vehicle dispatch plan is generated by allocating the work based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the allocation of the work based on the request is prohibited; The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, The non-target vehicle is a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete. Vehicle dispatch planning method.

9. A vehicle dispatch planning device; A plurality of terminals each associated with a plurality of vehicles that perform at least one of a collection and delivery of packages; Equipped with The vehicle allocation planning device includes: a first generation process for generating a first vehicle dispatch plan for the plurality of vehicles; a second generation process for generating a second vehicle dispatch plan to which the operation based on a new request for the operation including a package pickup is added when a new request for the operation including a package pickup is received; a processor configured to execute The second generation process includes: the second vehicle dispatch plan is generated by assigning the work based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the assignment of the work based on the request is prohibited; The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, the terminal is configured to receive the first vehicle dispatch plan and the second vehicle dispatch plan from the vehicle dispatch planning device; The non-target vehicle is a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete. Delivery system.

10. On the computer, A first generation process for generating a first vehicle dispatch plan for a plurality of vehicles performing at least one of a collection operation and a delivery operation of a package; a second generation process for generating a second vehicle dispatch plan to which the operation based on a new request for the operation including a package pickup is added when a new request for the operation including a package pickup is received; A computer program for executing The second generation process includes: the second vehicle allocation plan is generated by allocating the work based on the request to one or more target vehicles among the plurality of vehicles, excluding non-target vehicles to which the allocation of the work based on the request is prohibited; The work included in the first vehicle dispatch plan or the second vehicle dispatch plan includes the delivery, The non-target vehicle is a vehicle among the plurality of vehicles that corresponds to a terminal that has transmitted an incompletion notification indicating that the delivery is incomplete. Computer program.

Images