Delivery plan generation device and delivery plan generation method

The delivery plan generation device optimizes vehicle allocation by designating reduction priorities and allocating new packages to vehicles with lower priorities, addressing inefficiencies in existing methods and improving operational efficiency and cost-effectiveness.

WO2024241667A1PCT designated stage expired Publication Date: 2024-11-28PANASONIC INTELLECTUAL PROPERTY MANAGEMENT CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/009394
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-03-11
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

Existing delivery plan generation methods do not adequately consider the allocation of new packages to vehicles based on reduction priority, leading to inefficient use of vehicles and increased operational costs, particularly when a mix of assigned and unassigned vehicles is present.

Method used

A delivery plan generation device and method that includes a reception unit for designating vehicles and setting reduction priorities, a generation unit that allocates new packages to vehicles with lower reduction priority values, and a processor to optimize vehicle allocation based on attribute information and delivery planning modes, ensuring efficient vehicle utilization.

Benefits of technology

The solution allows for the reduction and allocation of vehicles according to user specifications, generating an efficient delivery plan that minimizes vehicle usage while ensuring that vehicles with higher reduction priorities are utilized preferentially, thereby improving operational efficiency and reducing costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024009394_28112024_PF_FP_ABST
    Figure JP2024009394_28112024_PF_FP_ABST
Patent Text Reader

Abstract

The purpose of the present invention is to further improve convenience in allocating delivery vehicles when forming a delivery plan. Provided is a delivery plan generation device comprising: a reception unit that receives the designation of both a plurality of vehicles available for a delivery plan and a delivery plan mode for the plurality of vehicles; a setting unit that sets, for each of the plurality of vehicles, a reduction priority, which is an index for performing reduction preferentially on that vehicle, on the basis of attribute information set for each of the plurality of vehicles and the delivery plan mode; and a generation unit that generates a delivery plan by allocating new packages to each of the plurality of vehicles on the basis of the reduction priorities, wherein new packages are allocated more preferentially to vehicles with lower reduction priority values.
Need to check novelty before this filing date? Find Prior Art

Description

Delivery plan generating device and delivery plan generating method

[0001] The present disclosure relates to a delivery plan generation device and a delivery plan generation method that support delivery of multiple parcels that are delivery targets.

[0002] When planning a delivery plan for a package, it is necessary to take into consideration the number of vehicles to be used. For example, Patent Document 1 discloses such a prior art method for creating a delivery plan for a package using a plurality of vehicles to a plurality of delivery destinations, in which a priority for reduction is set and the number of vehicles to be used is reduced based on the priority, thereby improving the delivery plan.

[0003] Japanese Patent Application Laid-Open No. 2002-302257

[0004] The present disclosure has been devised in consideration of the above-described conventional situation, and aims to further improve convenience in allocating delivery vehicles when formulating a delivery plan.

[0005] The present disclosure provides a delivery plan generation device that includes: a reception unit that receives designation of multiple vehicles that can be used for a delivery plan and a delivery plan mode for the multiple vehicles; a setting unit that sets a reduction priority that is an index for prioritizing reductions for each of the multiple vehicles based on attribute information set for each of the multiple vehicles and the delivery plan mode; and a generation unit that generates a delivery plan by allocating new cargo to each of the multiple vehicles based on the reduction priority, wherein the lower the value of the reduction priority is, the higher the priority is for allocating new cargo to a vehicle.

[0006] The present disclosure also provides a delivery plan generation method that includes: a receiving step in which a processor and a memory cooperate to receive designation of multiple vehicles that can be used for a delivery plan and a delivery plan mode for the multiple vehicles; a setting step in which a reduction priority is set as an index for prioritizing reductions for each of the multiple vehicles based on attribute information set for each of the multiple vehicles and the delivery plan mode; and a generation step in which a delivery plan is generated by allocating new cargo to each of the multiple vehicles based on the reduction priority, wherein the lower the reduction priority value of a vehicle, the higher the priority for allocating new cargo.

[0007] According to the present disclosure, vehicle usage in delivery planning can be reduced and allocated according to the situation.

[0008] 1 is a block diagram showing an example of a system configuration according to an embodiment of the present disclosure; 2 is a diagram showing an example of a DB configuration for various information according to an embodiment of the present disclosure; 3 is a diagram showing an example of a DB configuration for various information according to an embodiment of the present disclosure; 4 is a diagram showing an example of a reduction priority setting according to an embodiment of the present disclosure; 5 is a diagram showing an example of a reduction priority setting according to an embodiment of the present disclosure; 6 is a diagram showing an example of an improvement algorithm for a delivery plan according to an embodiment of the present disclosure; 7 is a conceptual diagram for explaining a specific example of transfer according to an embodiment of the present disclosure; 8 is a table showing an example of an extraction rule based on reduction priority according to an embodiment of the present disclosure; 9 is a schematic diagram showing an example of a configuration of a UI screen in a conventional configuration as a comparative example; 10 is a schematic diagram showing an example of a configuration of a UI screen according to an embodiment of the present disclosure; 11 is a diagram showing an example of a configuration of a UI screen according to an embodiment of the present disclosure; 12 is a flowchart of overall processing according to an embodiment of the present disclosure; 13 is a flowchart of a delivery plan calculation process according to an embodiment of the present disclosure

[0009] (Background to the Contents of Each Embodiment) In actual vehicle planning, at a certain point in time, vehicles that have already been assigned cargo and vehicles that have not yet been assigned cargo are mixed. Under such circumstances, it is necessary to assign new cargo. Furthermore, in addition to cases where it is desirable to reduce the number of vehicles used as much as possible, there are various needs where it is not possible to reduce the use of certain vehicles or where it is better not to reduce the use of certain vehicles. For example, when the use of a vehicle is reserved in advance and a usage fee is incurred regardless of whether the vehicle is actually used, this corresponds to a case where it is not possible to reduce the use of a vehicle or where it is better not to reduce the use of a certain vehicle.

[0010] The above-mentioned Patent Document 1 discloses a method for allocating cargo to multiple vehicles to which cargo has not yet been allocated, but does not fully consider methods for allocating cargo to vehicles or reducing the number of vehicles in use in accordance with the above-mentioned situations.

[0011] Therefore, in the following embodiments, an example of a delivery plan generation device and a delivery plan generation method that can generate a delivery plan that meets the requirements at the delivery site by formulating a delivery plan based on the cargo allocation status, vehicle attributes, etc. will be described.

[0012] Hereinafter, with reference to the drawings as appropriate, detailed descriptions of embodiments that specifically disclose a delivery plan generation device and a delivery plan generation method according to the present disclosure will be provided. However, more detailed descriptions than necessary may be omitted. For example, detailed descriptions of well-known matters or redundant descriptions of substantially identical configurations may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art. Note that the accompanying drawings and the following description are provided to enable those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter recited in the claims.

[0013] <First Embodiment> Hereinafter, as a first embodiment of the present disclosure, an example of formulating (generating) a delivery plan for delivering multiple packages will be described. In this embodiment, the delivery plan is a plan of a delivery route when delivering packages (items) from a base to multiple destinations using at least one delivery vehicle (e.g., a truck) within a predetermined period (e.g., within one day). The delivery route corresponds to the driving order to the multiple destinations.

[0014] In this specification, a parcel that has already been assigned to a delivery vehicle is referred to as an "existing parcel," and a parcel that has not been assigned to a delivery vehicle is referred to as a "new parcel." Furthermore, a delivery vehicle to which an existing parcel has already been assigned is referred to as an "existing vehicle," and a delivery vehicle to which no parcel has been assigned is referred to as a "new vehicle." Typically, in a delivery plan for an existing parcel for an existing vehicle at a certain point in time, the delivery route has already been determined, and the arrangements for the existing vehicle and the delivery person (hereinafter also referred to as the driver) have already been finalized. In this embodiment, it is assumed that the assignment of existing parcels that have already been assigned to existing vehicles will not be changed, and new parcels can be assigned to any vehicle.

[0015] [Device Configuration] The delivery plan generating device 100 according to this embodiment is communicably connected to one or more client terminals 200 via a network 300. The delivery plan generating device 100 may be configured as an on-premise server device at a delivery company's base, or may be configured as a cloud-based server device on a network.

[0016] The delivery plan generation device 100 includes a processing unit 110, a storage unit 120, a UI (User Interface) unit 160, and a communication unit 170. The processing unit 110 may be a processor configured using, for example, a CPU (Central Processing Unit), a GPU (Graphical Processing Unit), an MPU (Micro Processing Unit), a DSP (Digital Signal Processor), or an FPGA (Field-Programmable Gate Array). The processing unit 110 realizes various functions described below, for example, by referencing various databases (hereinafter, referred to as DBs) stored in the storage unit 120 or reading out programs. The storage unit 120 is a storage unit for storing various data, programs, etc., and may be composed of a volatile / non-volatile storage device such as a RAM (Random Access Memory), a ROM (Read Only Memory), or an HDD (Hard Disk Drive).

[0017] The UI unit 160 is a part for accepting operations by a user of the delivery plan generation device 100 and outputting various information. The UI unit 160 may be composed of a display, a mouse, a keyboard, etc. The communication unit 170 is an interface for communicating with external devices via the network 300. There are no particular limitations on the communication standards that can be supported by the communication unit 170, and it does not matter whether it is wired or wireless. In addition, the communication unit 170 may be capable of supporting multiple communication standards.

[0018] The client terminal 200 is a terminal device that can be used by a delivery person during delivery work, and may be, for example, a mobile terminal such as a smartphone, tablet terminal, or POS terminal. The client terminal 200 may also be installed in a delivery vehicle (hereinafter simply referred to as a "vehicle") used during delivery. The client terminal 200 includes a processing unit 201, a storage unit 202, a communication unit 203, a UI unit 204, and a sensor unit 205.

[0019] The processing unit 201 may be configured using, for example, a CPU, a GPU, an MPU, a DSP, or an FPGA. The processing unit 201 realizes various functions described below, for example, by referencing various data stored in the storage unit 202 or reading out programs. The storage unit 202 is a storage unit for storing various data, programs, and the like, and may be configured from, for example, a volatile / non-volatile storage device such as a RAM, a ROM, an HDD, a flash memory, or an SSD (Solid State Drive).

[0020] The communication unit 203 is an interface for wireless communication with external devices via the network 300. There are no particular limitations on the communication standards that can be supported by the communication unit 203. The sensor unit 205 is composed of one or more sensors for detecting status information of the client terminal 200, and may be composed of, for example, a position sensor using a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System), a magnetic sensor, an acceleration sensor, a camera as an imaging device, and the like.

[0021] In this embodiment, the processing unit 110 of the delivery plan generation device 100 is equipped with a distance matrix generation unit 111, a delivery plan calculation unit 112, a priority derivation unit 113, a screen generation unit 114, and a DB management unit 115. Note that the functional block configuration is an example, and the function of one block may be divided into more details, or the functions of multiple blocks may be configured together. Note that this is an example configuration focusing on the functions related to this embodiment, and the delivery plan generation device 100 may also have other functions.

[0022] The distance matrix generation unit 111 generates a matrix (distance matrix) for calculating delivery costs to determine a delivery route based on the network and feature quantities of roads used as delivery routes. A method for calculating delivery costs may be, for example, the method disclosed in Japanese Patent Application Laid-Open No. 2019-082755 by the applicant of the present application, and a similar method is used in this embodiment. The delivery plan calculation unit 112 calculates a delivery plan using the distance matrix and various information described below. The priority derivation unit 113 derives priorities related to reductions for vehicles. Specific examples of priorities and their derivation will be described later. The screen generation unit 114 generates various UI screens to be provided to the delivery plan generation device 100 and the client terminal 200. The DB management unit 115 updates and manages various DBs configured in the storage unit 120.

[0023] In this embodiment, the storage unit 120 of the delivery plan generation device 100 has a vehicle information DB 130, a package information DB 140, and a priority information DB 150. Note that the DB configuration is an example, and one DB may be divided into more detailed DBs, or multiple DBs may be combined into one DB.

[0024] The vehicle information DB 130 is a database for managing information on vehicles used for delivery. Specific examples of vehicle information according to this embodiment will be described later. The package information DB 140 is a database for managing information related to packages. Details of the package information according to this embodiment will be described later. The priority information DB 150 is a database for managing information on priority levels set for each vehicle. Details of the priority information according to this embodiment will be described later.

[0025] The information managed in each DB is an example, and other information such as driver information, road information, etc. may also be managed. Furthermore, the information managed in each DB may be updated as appropriate by communicating with an external device (not shown), or may be newly registered by input by a user or the like.

[0026] When using the delivery plan generation device 100 from the client terminal 200, the delivery plan generation device 100 may be accessed using a web browser (not shown) included in the client terminal 200, or may be used by starting an application corresponding to the delivery plan generation device 100 that is installed on the client terminal 200. Furthermore, the division of functions between the delivery plan generation device 100 and the client terminal 200 is not limited to the configuration in Fig. 1, and a configuration may be adopted in which some of the functions of the delivery plan generation device 100 are implemented on the client terminal 200 side.

[0027] [Data Examples] Figure 2 shows examples of the configuration of various information used in this embodiment. Figure 2A shows an example of the configuration of vehicle information according to this embodiment, which is held and managed, for example, in vehicle information DB 130. Figure 2B shows an example of the configuration of baggage information according to this embodiment, which is held and managed, for example, in baggage information DB 140. Note that each item of information constituting the DB shown below is an example, and items indicating other attribute information may be associated and managed.

[0028] The vehicle information is managed in association with vehicle identification information 131, allocation status information 132, allocated cargo information 133, maximum load capacity 134, owner information 135, and reduction priority 136. Vehicle identification information 131 is identification information for uniquely identifying the vehicle. Vehicle identification information 131 may be automatically assigned by the system, for example. Allocation status information 132 indicates whether cargo has already been allocated to the vehicle. In this embodiment, each vehicle is managed as "new" if it is in an unallocated state, and as "existing" if it is in a state where cargo has already been allocated. Allocated cargo information 133 indicates cargo identification information for uniquely identifying cargo that has already been allocated to the vehicle. For a vehicle that has no cargo allocated, i.e., a "new" vehicle, the allocated cargo information 133 indicates "none."

[0029] The maximum load capacity 134 indicates the load capacity of the vehicle, i.e., the amount of cargo that can be loaded. Here, for simplicity, this is shown as an integer value, but it may also be shown as dimensions, number, etc. The owner information 135 indicates the owner of the vehicle. In this embodiment, the vehicle is managed as either a "company" vehicle, which is a vehicle owned by the same company that is always available, or a "other company" vehicle, which is a vehicle owned by another company that is temporarily available through external arrangements, etc. The reduction priority 136 is an index used when allocating cargo to the vehicle, and is set by the system. Specific examples of reduction priority will be described later using FIG. 3.

[0030] The parcel information is managed by associating parcel identification information 141, parcel quantity 142, and designated delivery time information 143. The parcel identification information 141 is identification information for uniquely identifying the parcel. For example, the parcel identification information 141 may be automatically assigned by the system. The parcel quantity 142 indicates the quantity of the parcel in question, corresponding to the vehicle's load capacity (more specifically, the maximum load capacity 134). Here, for simplicity's sake, it is shown as an integer value, but it may also be indicated by dimensions, etc. The designated delivery time information 143 indicates the delivery time designated for the parcel. Note that, although omitted in FIG. 2B , the parcel information may further include information for identifying whether the parcel has already been assigned to a delivery vehicle, i.e., whether it is a "new parcel" or an "existing parcel," in correspondence with the assigned parcel information 113 of the vehicle information.

[0031] In the delivery plan generating device 100 according to this embodiment, vehicle information is generated and managed by the delivery plan generating device 100 based on instructions and input from a user. On the other hand, cargo information is information on various cargo provided from external devices and managed by the delivery plan generating device 100 in response to delivery plan generation. Items of vehicle information that can be arbitrarily input by the user include designation of vehicles from all vehicles that can be used for the delivery plan and designation of cargo to be delivered.

[0032] 3 shows an example of setting reduction priorities according to this embodiment, which are held and managed, for example, in a priority information DB 150. The priority information is managed in association with vehicle identification information 151 and reduction priorities 152. The vehicle identification information 151 is identification information for uniquely identifying a vehicle, and corresponds to the vehicle identification information 131 in FIG. 2A. The reduction priority 152 is an index determined by the delivery plan generation device 100 based on user settings, the contents of package allocation, and the like, and corresponds to the reduction priority 136 in FIG. 2A.

[0033] In this embodiment, the reduction priority is set to "0," "1," or "2." A reduction priority of "0" means that the vehicle cannot be reduced, i.e., a new package will always be assigned to the vehicle and used for delivery. As will be described in detail later, for a vehicle with a reduction priority of "0," the delivery plan generation process is repeatedly attempted so that at least one new package will be assigned to the vehicle, regardless of whether the vehicle is a "new vehicle" or an "existing vehicle." A reduction priority of "1" or "2" indicates that a new package can be assigned to the vehicle, in other words, that a new package does not need to be assigned. A higher value indicates a higher priority for allocating new packages. In this embodiment, the reduction priority is specified in three levels, from 0 to 2, but this is not limited to this. For example, more levels may be set depending on the combination of attributes set for the vehicle (e.g., the vehicle's load capacity and function (refrigerated vehicle / freezer vehicle)). Furthermore, the reduction priority may be set according to classifications such as major, medium, and minor categories. For example, if the major classifications of reduction priorities match between certain vehicles, the combination of transfer source / transfer destination, which will be described later, may be determined by referring to the intermediate classifications.

[0034] In addition, in this embodiment, it is possible to set a mode related to reducing the number of vehicles used for the multiple available vehicles. Specifically, the user can specify either reducing the number of vehicles used as much as possible from the multiple available vehicles (hereinafter referred to as the "first delivery plan mode") or using as many vehicles as possible (hereinafter referred to as the "second delivery plan mode"). Note that, when there is a sufficient amount of cargo to use all vehicles, the second delivery plan mode can be said to be a mode in which all vehicles are used, i.e., a mode in which the number of vehicles used is fixed. Furthermore, another mode may be selectable as the delivery plan mode. For example, the second delivery plan mode may be a mode in which, after receiving a specification of multiple available vehicles, the range of the number of vehicles to actually be used is specified.

[0035] 3A shows an example of reduction priorities determined when vehicles A, B, and C are designated as vehicles available for delivery and the second delivery plan mode is designated. In this case, the three designated vehicles are to be used in the delivery plan, and a reduction priority of "1" is determined for vehicle A, a reduction priority of "0" for vehicle B, and a reduction priority of "0" for vehicle C.

[0036] 3B shows an example of reduction priorities determined when vehicles A, B, and C are designated as vehicles available for delivery and the first delivery plan mode is designated. In this case, the three designated vehicles are to be used in the delivery plan, and a reduction priority of "1" is determined for vehicle A, a reduction priority of "2" for vehicle B, and a reduction priority of "0" for vehicle C.

[0037] A specific example of a method for determining reduction priorities will be described later. Note that, although three vehicles, vehicle A, vehicle B, and vehicle C, are given as examples of vehicles that can be used in the delivery plan, more vehicles may be designated as vehicles that can be used in the delivery plan.

[0038] In this embodiment, a delivery plan is determined by deriving an initial solution for the delivery plan and applying three types of improvement methods to the initial solution. Here, the initial solution is a solution in which the number of vehicles used and delivery routes are not efficient. In this embodiment, a delivery plan that enables efficient delivery is determined by improving this initial solution. During the improvement process, the delivery route and number of vehicles used are made more efficient, and the allocation of cargo to each vehicle is adjusted to satisfy other constraints, such as the allocation of cargo requiring temperature control. Therefore, the initial solution does not necessarily have to be an efficient solution, nor does it have to be a solution that satisfies the constraints. Methods for improving the delivery plan according to this embodiment will be described using "replacement," "exchange," and "transfer" as examples. Note that the initial solution for the delivery plan may be derived using, for example, a method described in Japanese Patent Application Laid-Open No. 2019-082755 by the applicant of the present application, and detailed description thereof will be omitted here. In this specification, "improvement" is described as being synonymous with reducing overall delivery costs. In this method, the delivery plan obtained after improvement may change depending on the initial solution that serves as the basis for improvement, so the resulting delivery plan may not necessarily be the most efficient delivery plan among all delivery plans. However, with the current state of technology, the scale at which the most efficient delivery plan can be created in a realistic time is limited, and it is difficult to create the most efficient delivery plan on a practical scale and in a practical time. Therefore, in actual delivery work, it is better to create a reasonably efficient delivery plan that has been improved in a short period of time and then start delivery, rather than spending a long time creating the most efficient delivery plan and then starting delivery. Therefore, in this embodiment, a delivery plan at any point in time obtained by improving the initial solution is adopted.

[0039] Fig. 4 is a diagram showing the concepts of three improvement methods according to this embodiment. Substitution is a process of changing the order of delivery destinations. Exchange is a process of switching delivery destinations between multiple delivery routes. Transfer is a process of moving a delivery destination to another delivery route. Whether or not to apply the above substitution, exchange, and transfer methods is determined based on the cost of delivering the package.

[0040] FIG. 4 shows an example of an improvement to a delivery plan when, for example, replacement, exchange, and transfer are performed on two delivery plans obtained as initial solutions. Note that replacement, exchange, and transfer are not performed solely; by repeatedly applying these methods, the entire delivery plan may be improved. In FIG. 4, a rectangle (□) indicates the delivery origin (base) of a package. A circle (◯) indicates the delivery destination, i.e., the package. Arrows indicate the delivery order. Also, one delivery plan corresponds to one vehicle.

[0041] Of the three options, only the transfer option changes the number of packages assigned to the two delivery plans. In the example of Figure 4, before the change, each of the two delivery plans had four packages assigned to each vehicle, but after the change, the plan has been improved to assign three packages and five packages to each vehicle.

[0042] The method for delivery planning using reduction priorities according to this embodiment is a method that focuses on transfer among the three improvement methods described above. Note that, since the number of packages assigned to each vehicle remains the same between replacement and exchange, if the focus is only on the number of vehicles used, the delivery plan may be determined by applying only transfer. However, if only transfer is applied, there is a risk that the delivery route of each vehicle will become inefficient, so if a delivery plan is created that also includes delivery routes, it is more preferable to apply replacement and exchange as well.

[0043] Fig. 5 shows a specific example of a method for transfer. In Fig. 5, a rectangle indicates the delivery source (base 501) of the package, from which the package is loaded onto a vehicle and delivered to the delivery destination. After delivery of the package is completed, the vehicle returns to base 501, loads the package, and delivers it again.

[0044] FIG. 5 shows delivery plans for two vehicles. This example illustrates the transfer of package 503e, assigned to the lower delivery plan, between package 502b in the upper delivery plan and base station 501. As a result of the transfer, a total of five packages 502a, 502b, 503a, 503b, and 503e are assigned to the vehicle corresponding to the upper delivery plan, and a total of two packages 503c and 503d are assigned to the vehicle corresponding to the lower delivery plan. Note that packages 502a and 502b are packages whose assignment destinations have already been determined and for which it is desirable not to change the assignment destination (i.e., "existing packages"). It is assumed that such existing packages may have fixed delivery routes or limited delivery drivers, for example, and changing the assignment destination would increase delivery costs.

[0045] [Extraction Rule Change Table] Fig. 6 is an example of a change table 600 that defines combinations of vehicles with reduction priorities set, used in a search during transfer according to this embodiment. In the change table 600, an order 601, a priority 602 of the vehicle to be transferred (transfer source vehicle), and a priority 603 of the vehicle to be transferred (transfer destination vehicle) are managed in association with each other. Combinations with the smallest order 601 are referenced first. Specific uses of the change table 600 will be described later together with a flowchart.

[0046] [UI Screen] An example of the configuration of a UI screen related to a delivery plan that can be displayed on the UI unit 160 of the delivery plan generation device 100 according to this embodiment or the UI unit 204 of the client terminal 200 will be described below. First, an example of a conventional UI screen and an example of allocation are shown in Fig. 7 as a comparative example with the UI screen according to this embodiment.

[0047] 7(a) shows an example of the state of an existing vehicle to which two existing packages have already been assigned, and FIG. 7(b) shows an example of the state of a new vehicle to which no packages have been assigned. The configuration examples of the UI screens shown in FIG. 7(a) and FIG. 7(b) are similar.

[0048] The UI screen 700 shown in FIG. 7( a) is configured to include assigned vehicle information 701, assigned driver information 702, available delivery time information 703, and a schedule 704. The assigned vehicle information 701 indicates the identification information of the vehicle assigned as the delivery vehicle. The assigned driver information 702 indicates the identification information of the delivery person assigned as the delivery person. The available delivery time information 703 indicates the working time period during which the delivery person (or vehicle) can make a delivery. Two existing packages ("Package 1" and "Package 2") are assigned to the schedule 704, as indicated by icons 706 and 707. New packages can be assigned to an unassigned area 705 in the schedule 704.

[0049] Consider, for example, the allocation of new packages in the configuration shown in FIG. 7 . In this case, if new packages are allocated to existing vehicles as shown in FIG. 7( a), there is no allocation to new vehicles as shown in FIG. 7( b), and therefore the use of new vehicles can be reduced. On the other hand, if new packages are added to existing vehicles in the schedule table 704 shown in FIG. 7( a), the overall delivery plan may become inefficient. For example, as a result of allocating new packages, existing vehicles may return to the base, load the newly allocated packages, and resume delivery. In such cases, the overall delivery efficiency would be improved by using new vehicles that have not yet been allocated packages. In other words, when allocating new packages while reducing the number of vehicles used, the conditions for the allocation must be considered.

[0050] 8A shows an example of the configuration of a UI screen according to the present embodiment. The UI screen 800 shown in FIG. 8A(a) is configured to include assigned vehicle information 801, assigned driver information 802, available delivery time information 803, reduction priority information 804, and a schedule table 805. The configurations of the assigned vehicle information 801, assigned driver information 802, available delivery time information 803, and schedule table 805 may be similar to the configurations shown in FIG. 7 as the conventional example. The reduction priority information 804 displays the reduction priority determined by the delivery plan generation device 100. The configuration examples of the UI screens shown in FIG. 8A(a) and FIG. 8B(b) are similar.

[0051] FIG. 8A shows an example of a UI screen display when generating a delivery plan using as many vehicles as possible from among a plurality of specified vehicles. FIG. 8A(a) corresponds to an existing vehicle, to which two existing packages ("Package 1" and "Package 2") have already been assigned, as indicated by icons 807 and 808. On the other hand, FIG. 8A(b) corresponds to a new vehicle, to which no packages have been assigned. Now, consider the case where "Package 3" is assigned as a new package. In this case, the new vehicle shown in FIG. 8A(b) has a reduction priority of "0," and therefore its utilization cannot be reduced. In other words, at least one new package must be assigned to a new vehicle with a reduction priority of "0." Therefore, a plan is generated that prioritizes the allocation of packages to utilize the vehicle. As a result, a new package, "Package 3," is assigned, as indicated by icon 817 in FIG. 8A(b).

[0052] At this time, the empty space 806 of the schedule 805 in FIG. 8A(a) may indicate that no new luggage has been added. For example, as shown in FIG. 8A(a), a message "No new luggage added" may be displayed. Similarly, the empty space 816 of the schedule 815 in FIG. 8A(b) may indicate that new luggage has been added. For example, as shown in FIG. 8A(b), a message "New luggage added" may be displayed. By combining such a display with the display of the reduction priority, it is possible to present the allocation status of new luggage to vehicles and the reasons for this on the UI screen. Note that the reduction priority is set for all specified vehicles, regardless of whether they are new vehicles or existing vehicles. At this time, the reduction priority for an existing vehicle is used as an indicator for allocating (or not allocating) new luggage to the existing vehicle, and is not an indicator for reducing the use of the existing vehicle itself. In other words, in this embodiment, existing luggage has already been allocated to the existing vehicle, and the allocation of existing luggage to the existing vehicle is not changed regardless of the set reduction priority.

[0053] FIG. 8B shows an example of a UI screen display when generating a delivery plan by minimizing the number of vehicles to be used among multiple specified vehicles. FIG. 8B(a) corresponds to an existing vehicle, to which existing cargo ("Cargo 1" and "Cargo 2") has already been assigned, as indicated by icons 827 and 828. On the other hand, FIG. 8B(b) corresponds to a new vehicle, to which no cargo has been assigned. Now, consider the case where "Cargo 3" is assigned as a new cargo. In this case, the vehicle shown in FIG. 8B(b) has a reduction priority of "2," which is a higher reduction priority. Therefore, a delivery plan is generated that suppresses the allocation of new cargo and encourages reduction. As a result, as indicated by icon 829 in FIG. 8B(a), new cargo "Cargo 3" is assigned to an existing vehicle with a reduction priority of "1." In this example, the new vehicle corresponding to FIG. 8B(b) has no cargo assigned, so its usage can be reduced. At this time, in addition to the cargo allocation results on the UI screen, information on the vehicles that have been reduced from the specified multiple vehicles (e.g., number of vehicles or a list) may be displayed and presented to the user along with the generated delivery plan.

[0054] FIG. 8C shows another example of a UI screen when generating a delivery plan by reducing the number of vehicles to be used as much as possible from among a plurality of specified vehicles. FIG. 8C(a) corresponds to an existing vehicle, and as shown by icons 847 and 848, two existing packages ("Package 1" and "Package 2") have already been assigned to this existing vehicle. The reduction priority of this existing vehicle is "1." FIG. 8C(b) and FIG. 8C(c) correspond to new vehicles, neither of which has any package assigned to it. In this case, the reduction priority of the new vehicle in FIG. 8C(b) is "2," and the reduction priority of the new vehicle in FIG. 8C(c) is "0."

[0055] In this case, consider allocating new luggage, "Luggage 3." The new vehicle shown in FIG. 8C(c) has a reduction priority of "0," and therefore cannot reduce its usage. In other words, at least one new luggage must be allocated to a new vehicle with a reduction priority of "0." Therefore, "Luggage 3" is allocated to this new vehicle, resulting in a state as shown by icon 867. As a result, the updated status of the allocation of new luggage may be displayed in the free space 846 of the schedule table 845 in FIG. 8C(a), the free space 856 of the schedule table 855 in FIG. 8C(b), and the free space 866 of the schedule table 865 in FIG. 8C(c).

[0056] [Delivery Plan Generation Processing] Figure 9 is a flowchart of the delivery plan generation processing executed by the delivery plan generation device 100 according to this embodiment. This processing flow may be implemented by the processing unit 110 of the delivery plan generation device 100 reading and executing programs and data stored in the storage unit 120. For ease of explanation, the processing entity of each step will be collectively described as the delivery plan generation device 100.

[0057] Note that when this process flow starts, some vehicles may already have cargo assigned to them, i.e., when this process flow starts, existing vehicles and existing cargo may already be set.

[0058] The delivery plan generation device 100 accepts input of vehicle information and cargo information from a user (step S901). The input vehicle information may specify, for example, multiple vehicles for which a delivery plan is to be generated from among the vehicles registered in the vehicle information DB 130. The specified vehicles may include new vehicles and existing vehicles. The input cargo information corresponds to new cargo registered in the cargo information DB 140 that has not yet been assigned to any vehicle. A single new cargo may be specified, or multiple new cargoes may be specified collectively. Furthermore, the delivery plan generation device 100 accepts a mode specification for the specified multiple vehicles: either reducing the number of vehicles used as much as possible (first delivery plan mode) or using all vehicles (second delivery plan mode). The various information may be accepted via a UI screen (not shown) related to the delivery plan that can be displayed on the UI unit 160 of the delivery plan generation device 100 or the UI unit 204 of the client terminal 200.

[0059] The delivery plan generation device 100 determines whether the setting received in step S901 is a vehicle count reduction, i.e., whether the first delivery plan mode is specified (step S902). If a vehicle count reduction is specified (step S902: YES), the processing of the delivery plan generation device 100 proceeds to step S905. On the other hand, if the setting received in step S901 is to use all specified vehicles, i.e., if the second delivery plan mode is specified (step S902: NO), the processing of the delivery plan generation device 100 proceeds to step S903. Note that, since two types of delivery plan modes are assumed in this embodiment, if the setting received in step S901 is not a vehicle count reduction, it is treated as if the second delivery plan mode was specified. If there are other delivery plan modes, such as a third delivery plan mode, the processing proceeds to step S903 if the second delivery plan mode is specified.

[0060] The delivery plan generating device 100 sets reduction priorities for the multiple vehicles specified in step S901 (step S903). Here, the delivery plan generating device 100 sets a reduction priority of "1" for existing vehicles, i.e., vehicles to which at least one package has already been assigned, among the multiple specified vehicles. Note that the delivery plan generating device 100 may be configured to initialize the reduction priorities of the multiple vehicles specified in step S901 to a predetermined value at the start of this process.

[0061] The delivery plan generating device 100 further sets reduction priorities for the multiple vehicles specified in step S901 (step S904). Here, the delivery plan generating device 100 sets a reduction priority of "0" for new vehicles, i.e., vehicles to which no cargo has been assigned, among the multiple specified vehicles. Through the processes of steps S903 and S904, reduction priorities such as those shown in FIG. 3A are set. Thereafter, the processing of the delivery plan generating device 100 proceeds to step S911.

[0062] The delivery plan generation device 100 determines whether there are any fixed vehicles among the multiple vehicles specified in step S901 (step S905). A fixed vehicle here refers to a vehicle whose usage cannot be reduced. Examples of fixed vehicles include vehicles owned by the delivery company itself, vehicles whose allocation cannot be canceled, and vehicles whose usage cannot be reduced even if they are reduced, and vehicles that have been assigned cargo before the delivery plan was created and are difficult to stop using. For example, as shown in FIG. 2A, such information may refer to the owner information 135 of the vehicle information managed in the vehicle information DB 130, and vehicles that are "owned by the company" may be determined to be fixed vehicles. As described above, this embodiment does not anticipate reassigning existing cargo that has been assigned before the delivery plan was created to other vehicles. This is because the assignment of cargo to existing vehicles is arranged by other delivery companies, making it difficult for the user of the delivery plan generation device 100 to transfer cargo to other vehicles at their discretion, and because transferring cargo from existing vehicles to other vehicles is practically difficult for drivers. Therefore, the usage of existing vehicles is not reduced regardless of whether they are fixed vehicles or not. However, if it is permitted to reassign existing cargo assigned to an existing vehicle to another vehicle, the system may be configured to switch whether or not to treat the existing vehicle as a fixed vehicle based on vehicle information, etc. In addition, whether or not the information is fixed may be determined based on other information included in the vehicle information. For example, even if the vehicle information includes information regarding arrangement (not shown) and the owner information 135 is "other company," a vehicle whose arrangement status is arranged (unchangeable) may be treated as a fixed vehicle. If there is a fixed vehicle (step S905: YES), the processing of the delivery plan generation device 100 proceeds to step S908. On the other hand, if there is no fixed vehicle (step S905: NO), the processing of the delivery plan generation device 100 proceeds to step S906.

[0063] The delivery plan generating device 100 sets reduction priorities for the multiple vehicles specified in step S901 (step S906). Here, the delivery plan generating device 100 sets a reduction priority of "1" for existing vehicles among the multiple specified vehicles. Note that the delivery plan generating device 100 may be configured to initialize the reduction priorities of the multiple vehicles specified in step S901 to a predetermined value at the start of this process.

[0064] The delivery plan generating device 100 further sets reduction priorities for the multiple vehicles specified in step S901 (step S907). Here, the delivery plan generating device 100 sets a reduction priority of "2" for new vehicles among the multiple specified vehicles. Thereafter, the processing of the delivery plan generating device 100 proceeds to step S911.

[0065] The delivery plan generating device 100 sets reduction priorities for the multiple vehicles specified in step S901 (step S908). Here, the delivery plan generating device 100 sets a reduction priority of "1" for existing vehicles among the multiple specified vehicles, regardless of whether a fixed vehicle is set. Note that the delivery plan generating device 100 may be configured to initialize the reduction priorities of the multiple vehicles specified in step S901 to a predetermined value at the start of this process.

[0066] The delivery plan generating device 100 further sets a reduction priority for the plurality of vehicles specified in step S901 (step S909). Here, the delivery plan generating device 100 sets a reduction priority of "2" for new vehicles other than fixed vehicles among the plurality of specified vehicles.

[0067] The delivery plan generating device 100 further sets reduction priorities for the multiple vehicles specified in step S901 (step S910). Here, the delivery plan generating device 100 sets a reduction priority of "0" for new vehicles that are fixed vehicles among the multiple specified vehicles. Thereafter, the processing of the delivery plan generating device 100 proceeds to step S911.

[0068] The delivery plan generating device 100 performs a delivery plan calculation process using the set reduction priority (step S911). Details of this process will be described later with reference to Fig. 10. After that, the process of the delivery plan generating device 100 proceeds to step S912.

[0069] The delivery plan generating device 100 outputs the delivery plan calculated in step S911 (step S912). This output may be displayed on a UI screen such as those shown in Figures 8A to 8C. Then, this processing flow ends.

[0070] (Distribution Plan Calculation Processing) FIG. 10 is a flowchart of the delivery plan calculation processing according to this embodiment, which corresponds to step S911 in FIG.

[0071] The delivery plan generation device 100 generates a delivery plan as an initial solution by performing a delivery plan generation process based on a predetermined delivery plan generation algorithm (step S1001). As described above, the delivery plan generation algorithm may be a known method, such as that described in JP 2019-082755 A, and is not particularly limited. Furthermore, the initial solution for the delivery plan may be determined based on road costs based on predefined map information, as well as real-time road congestion conditions. Here, new cargo is assigned to each vehicle regardless of information such as reduction priority. Furthermore, at the time of determining the initial solution, the replacement or exchange improvement method may be applied from the three improvement methods described above.

[0072] The delivery plan generation device 100 references the change table 600 as shown in FIG. 6 and extracts vehicles with a combination of reduction priorities corresponding to the first extraction rule from the specified plurality of vehicles (step S1002). Specifically, when "1" in the order 601 is referenced, a vehicle with a reduction priority of "2" is extracted as the vehicle transferring the package (transfer source), and a vehicle with a reduction priority of "0" is extracted as the vehicle to which the package will be transferred (transfer destination). Note that if there are no vehicles with the combination of reduction priorities indicated in the extraction rule, the next extraction rule is referenced in accordance with the order 601.

[0073] The delivery plan generation device 100 determines the parcels to be transferred that are assigned to the transfer source vehicle among the two extracted vehicles (step S1003). The parcels determined here are parcels that will be newly assigned to the vehicle as new parcels. In other words, existing parcels are excluded from the parcels to be transferred here.

[0074] The delivery plan generation device 100 determines whether the delivery plan can be improved or the number of vehicles used can be reduced before and after the transfer of the determined new package between the two extracted vehicles (step S1004). The condition for whether or not the delivery plan has been improved may be specified in advance. For example, it may be whether or not the total delivery cost of each of the two vehicles has been reduced, or it may be whether or not the delivery time has been shortened. If improvement or reduction is possible (step S1004: YES), the processing of the delivery plan generation device 100 proceeds to step S1005. On the other hand, if neither improvement nor reduction is possible (step S1004: NO), the processing of the delivery plan generation device 100 proceeds to step S1007.

[0075] The delivery plan generating device 100 determines whether, after the transfer of the new parcels, there are zero new parcels assigned to vehicles that cannot be reduced, i.e., vehicles with a reduction priority of "0" (step S1005). That is, it is determined whether at least one new parcel has been assigned to a vehicle with a reduction priority of "0." If there are more than zero new parcels assigned to vehicles that cannot be reduced (step S1005: NO), the processing of the delivery plan generating device 100 proceeds to step S1006. On the other hand, if there are zero new parcels assigned to vehicles that cannot be delivered (step S1005: YES), the processing of the delivery plan generating device 100 proceeds to step S1009. Note that, in addition to the condition that at least one new parcel has been assigned to a vehicle that cannot be reduced, further condition determinations may be made. For example, conditions based on vehicle attributes may be determined. More specifically, a constraint determination may be made, such as that refrigerated parcels are only assigned to refrigerated trucks. If a constraint violation occurs, the delivery plan generating device 100 may be further configured to replace, exchange, or transfer packages to search for a solution in which all constraints are satisfied.

[0076] The delivery plan generating device 100 transfers the determined new shipment and sets the result as the current solution for the delivery plan (step S1006).Then, the processing of the delivery plan generating device 100 returns to step S1002, and further processing is repeated based on the solution at that time.

[0077] The delivery plan generating device 100 determines whether there are any unprocessed new packages among the new packages assigned to the transfer source vehicle (step S1007). If there are any unprocessed new packages (step S1007: YES), the processing of the delivery plan generating device 100 proceeds to step S1008. If there are no unprocessed new packages (step S1007: NO), the processing of the delivery plan generating device 100 proceeds to step S1009.

[0078] The delivery plan generating device 100 determines the new unprocessed package assigned to the transfer source vehicle as the processing target (step S1008).Then, the processing of the delivery plan generating device 100 returns to step S1004 and the processing is repeated.

[0079] The delivery plan generating device 100 determines whether or not processing based on the last extraction rule of the extraction rules defined in the change table 600 shown in Fig. 6 has been completed (step S1009). If processing based on the last extraction rule has been completed (step S1009: YES), the processing of the delivery plan generating device 100 proceeds to step S1010. On the other hand, if processing based on the last extraction rule has not been completed, that is, if there are unprocessed extraction rules (step S1009: NO), the processing of the delivery plan generating device 100 proceeds to step S1011.

[0080] The delivery plan generating device 100 determines the current solution as the solution for the delivery plan (step S1010), then ends this processing flow, and returns to the processing in FIG.

[0081] The delivery plan generation device 100 determines new transfer source and transfer destination vehicles from among the specified multiple vehicles based on the next unprocessed extraction rule among the extraction rules specified in the change table 600 shown in FIG. 6 . For example, if the next unprocessed extraction rule is "2" in the order 601, the transfer source vehicle will be a vehicle with a reduction priority of "2" and the transfer destination vehicle will be a vehicle with a reduction priority of "1." If there are no vehicles with the combination of reduction priorities specified in the extraction rule, the next extraction rule is referenced according to the order 601. Although three values, "0," "1," and "2," are used to set the reduction priorities, two of these values ​​may also be used. In this case, a combination of the two reduction priority values ​​used may be used as an extraction rule, or the reduction priority setting values ​​in the extraction rule definition and each step of the processing flow may be adjusted as appropriate. The delivery plan generation device 100 then proceeds to step S1003 and repeats the process.

[0082] As described above, a delivery plan generation device (e.g., 100) according to the present embodiment includes a receiving unit (e.g., 110, 114, 160) that receives a plurality of vehicles (e.g., 131) available for a delivery plan and a delivery plan mode for the plurality of vehicles; a setting unit (e.g., 110, 113) that sets a reduction priority, which is an index for preferentially reducing loads for each of the plurality of vehicles, based on attribute information and the delivery plan mode set for each of the plurality of vehicles; and a generating unit (e.g., 110, 111, 112) that generates a delivery plan by allocating new loads to each of the plurality of vehicles based on the reduction priority. Vehicles with lower reduction priority values ​​are given priority in the allocation of new loads. This enables vehicle use in a delivery plan to be reduced and allocated according to the situation, based on user specifications. As a result, even when existing vehicles with assigned loads and new vehicles without assigned loads are mixed, an appropriate delivery plan can be generated based on the user's desired reduction setting.

[0083] Furthermore, when a first delivery plan mode in which cargo is assigned to all of the plurality of vehicles is specified, the setting unit sets a higher reduction priority for vehicles among the plurality of vehicles to which cargo has already been assigned than for vehicles to which cargo has not been assigned. Furthermore, when a second delivery plan mode in which the use of a plurality of vehicles is reduced is specified, the setting unit sets a higher reduction priority for vehicles among the plurality of vehicles to which cargo has not been assigned than for vehicles to which cargo has already been assigned. This makes it possible to appropriately switch and set reduction priorities for achieving vehicle reduction and cargo assignment based on user specifications.

[0084] The attribute information also includes information on whether or not a reduction is possible (e.g., 132, 135), and the setting unit sets the reduction priority to be the lowest for vehicles that cannot be reduced. This makes it possible to set a reduction priority that does not allow a reduction in usage when a vehicle has an attribute that cannot be reduced, and to create a delivery plan that gives higher priority to usage.

[0085] The system further includes a display control unit (e.g., 110, 114, 160) that displays the delivery plan generated by the generation unit on a delivery plan screen, and the delivery plan screen displays the results of allocating new cargo to vehicles and the reduction priority set for the vehicles.The delivery plan screen also displays the results of reduction for multiple vehicles due to the allocation of new cargo.This makes it possible to notify the user of the reasons for allocating new cargo to each vehicle and the results of the reduction.

[0086] (Other Modifications) In the above-described embodiment, even when the reduction priority is set to four or more levels, the priority may be set according to at least one of the vehicle attributes and the delivery plan mode. For example, when the reduction priority is set to multiple levels according to the vehicle load, different priorities may be set depending on whether the delivery plan mode is the first delivery plan mode or the second delivery plan mode, even for vehicles with the same load. More specifically, in the first delivery plan mode, retaining vehicles with heavy loads and eliminating vehicles with light loads reduces the total number of vehicles to be used, so a higher reduction priority is set for vehicles with lighter loads. Furthermore, in the second delivery plan mode, vehicles with light loads must also be used, so many vehicles cannot be used, so a higher reduction priority is set for vehicles with heavier loads.

[0087] The present disclosure also applies to programs and storage media that realize the functions of the devices of the above-mentioned embodiments, which are supplied to the device via a network or various storage media and that are read and executed by a computer within the device.

[0088] Although various embodiments have been described above with reference to the drawings, it goes without saying that the present disclosure is not limited to these examples. It is clear to those skilled in the art that various modifications, alterations, substitutions, additions, deletions, and equivalents may be made within the scope of the claims, and it is understood that these also fall within the technical scope of the present disclosure. Furthermore, the components of the various embodiments described above may be combined in any manner without departing from the spirit of the invention.

[0089] (Additional Notes) The above description of the embodiments discloses the following techniques.

[0090] (Technology 1) A delivery plan generation device comprising: a reception unit that receives designation of multiple vehicles that can be used for a delivery plan and a delivery plan mode for the multiple vehicles; a setting unit that sets a reduction priority that is an index for prioritizing reductions for each of the multiple vehicles based on attribute information set for each of the multiple vehicles and the delivery plan mode; and a generation unit that generates a delivery plan by allocating new cargo to each of the multiple vehicles based on the reduction priority, wherein the lower the value of the reduction priority, the higher the priority is for allocating new cargo to a vehicle.

[0091] This configuration allows for the reduction and allocation of vehicles according to the situation based on the user's specifications regarding the use of vehicles in the delivery plan. As a result, even when there is a mixture of existing vehicles with already allocated cargo and new vehicles with no cargo assigned, it is possible to generate an appropriate delivery plan based on the reduction settings desired by the user.

[0092] (Technology 2) The delivery plan generation device according to Technology 1, wherein when a first delivery plan mode is specified in which cargo is assigned to all of the plurality of vehicles, the setting unit sets a reduction priority for vehicles among the plurality of vehicles to which cargo has already been assigned higher than for vehicles to which cargo has not been assigned.

[0093] This configuration makes it possible to appropriately switch and set reduction priorities for realizing vehicle reduction and cargo allocation based on user specifications.

[0094] (Technology 3) The delivery plan generation device according to Technology 1 or Technology 2, wherein when a second delivery plan mode that reduces the use of the plurality of vehicles is specified, the setting unit sets a reduction priority for vehicles among the plurality of vehicles that have not been assigned a load to be higher than for vehicles that have already been assigned a load.

[0095] This configuration makes it possible to appropriately switch and set reduction priorities for realizing vehicle reduction and cargo allocation based on user specifications.

[0096] (Technology 4) The delivery plan generation device according to any one of Technology 1 to Technology 3, wherein the attribute information includes information relating to whether or not reduction is possible, and the setting unit sets the reduction priority to be lowest for a vehicle to which no cargo is assigned and for which reduction is not possible.

[0097] This configuration makes it possible to appropriately switch and set reduction priorities to achieve vehicle reduction and cargo allocation, taking into account fixed vehicles and new vehicles, based on user specifications.

[0098] (Technology 5) The delivery plan generation device according to any one of Technology 1 to Technology 4, further comprising a display control unit that displays the delivery plan generated by the generation unit on a delivery plan screen, and the delivery plan screen displays the results of allocating new cargo to vehicles and the reduction priority set for the vehicles.

[0099] This configuration makes it possible to notify the user of the reasons for the allocation of new cargo to each vehicle and the reduction results.

[0100] (Technology 6) The delivery plan generating device according to Technology 5, wherein the delivery plan screen displays a result of reduction in the number of vehicles due to allocation of new cargo.

[0101] This configuration makes it possible to notify the user of the reasons for the allocation of new cargo to each vehicle and the reduction results.

[0102] (Technology 7) A delivery plan generation method comprising: a receiving step in which a processor and a memory cooperate to receive designation of multiple vehicles available for a delivery plan and delivery plan modes for the multiple vehicles; a setting step in which a reduction priority is set as an index for preferentially reducing loads for each of the multiple vehicles based on attribute information set for each of the multiple vehicles and the delivery plan mode; and a generation step in which a delivery plan is generated by allocating new loads to each of the multiple vehicles based on the reduction priority, wherein the lower the value of the reduction priority, the higher the priority for allocating new loads to a vehicle.

[0103] This configuration allows for the reduction and allocation of vehicles according to the situation based on the user's specifications regarding the use of vehicles in the delivery plan. As a result, even when there is a mixture of existing vehicles with already allocated cargo and new vehicles with no cargo assigned, it is possible to generate an appropriate delivery plan based on the reduction settings desired by the user.

[0104] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2023-083239, filed on May 19, 2023, are incorporated herein by reference in their entirety.

[0105] The present disclosure is useful as a delivery plan generating device and a delivery plan generating method.

[0106] DESCRIPTION OF SYMBOLS 100... Delivery plan generation device 110... Processing unit 111... Distance matrix generation unit 112... Delivery plan calculation unit 113... Priority derivation unit 114... Screen generation unit 115... DB management unit 120... Storage unit 130... Vehicle information DB 140... Package information DB 150... Priority information DB 160... UI unit 170... Communication unit 200... Client terminal 201... Processing unit 202... Storage unit 203... Communication unit 204... UI unit 300... Network

Claims

1. A delivery plan generation device comprising: a reception unit that receives designation of multiple vehicles available for a delivery plan and a delivery plan mode for the multiple vehicles; a setting unit that sets a reduction priority as an index for preferentially reducing loads for each of the multiple vehicles based on attribute information set for each of the multiple vehicles and the delivery plan mode; and a generation unit that generates a delivery plan by allocating new loads to each of the multiple vehicles based on the reduction priority, wherein vehicles with a lower reduction priority value are given priority in allocating new loads.

2. A delivery plan generating device as described in claim 1, wherein when a first delivery plan mode in which cargo is assigned to all of the plurality of vehicles is specified, the setting unit sets a higher reduction priority for vehicles among the plurality of vehicles to which cargo has already been assigned than for vehicles to which cargo has not been assigned.

3. A delivery plan generation device as described in claim 1, wherein when a second delivery plan mode for reducing utilization of the plurality of vehicles is specified, the setting unit sets a higher reduction priority for vehicles among the plurality of vehicles that do not have cargo assigned to them than for vehicles that already have cargo assigned to them.

4. The delivery plan generation device of claim 1, wherein the attribute information includes information regarding whether or not reduction is possible, and the setting unit sets the reduction priority to be the lowest for vehicles to which no cargo is assigned and which cannot be reduced.

5. A delivery plan generating device as described in claim 1, further comprising a display control unit that displays the delivery plan generated by the generation unit on a delivery plan screen, and the delivery plan screen displays the result of allocating new cargo to a vehicle and the reduction priority set for the vehicle.

6. The delivery plan generating device according to claim 5, further comprising a step of displaying the result of reduction in the number of vehicles due to new cargo allocation on the delivery plan screen.

7. A delivery plan generation method comprising: a receiving step in which a processor and a memory cooperate to receive designation of multiple vehicles available for a delivery plan and delivery plan modes for the multiple vehicles; a setting step in which a reduction priority is set for each of the multiple vehicles based on attribute information set for each of the multiple vehicles and the delivery plan mode; and a generation step in which a delivery plan is generated by allocating new cargo to each of the multiple vehicles based on the reduction priority, wherein vehicles with a lower reduction priority value are given priority in the allocation of new cargo.

Citation Information

Patent Citations

  • Delivery planning method and program for executing the same

    JP2002302257A

  • Method and device for generating vehicle allocation plan

    JP2003233896A

  • Vehicle operation plan creation method, apparatus and program

    JP2005122679A

  • Transport control method of circulating packing vessel

    JP2006151684A

  • Information processor, information processing method and computer program

    JP2012053861A