Delivery plan generation device, and delivery plan generation method
Patent Information
- Application Number
- JP2023083239
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-19
- Publication Date
- 2024-11-29
AI Technical Summary
【0007】 本開示によれば、配送計画における車両の利用について、状況に応じた車両の削減および割り当てが可能となる。
Smart Images

Figure 2024166854000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a delivery plan generating device and a delivery plan generating method that support delivery of multiple packages that are targets for delivery. [Background technology]
[0002] When planning a package delivery plan, it is necessary to take into account the number of vehicles to be used. For example, Patent Document 1 discloses such a prior art method for planning package delivery plans 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. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2002-302257 A Summary of the Invention [Problem to be solved by the invention]
[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. [Means for solving the problem]
[0005] The present disclosure provides 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 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 vehicles with a lower reduction priority value are given priority in allocating new cargo.
[0006] The present disclosure also provides a delivery plan generation method comprising: a receiving step in which a processor and a memory work together to receive designation of multiple vehicles available 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 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 vehicles with lower reduction priority values are given priority in allocating new loads. Effect of the Invention
[0007] According to the present disclosure, vehicle usage in a delivery plan can be reduced and allocated according to the situation. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is a block diagram showing an example of a system configuration according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a diagram showing an example of a DB configuration of various types of information according to an embodiment of the present invention. [Diagram 3] FIG. 13 is a diagram showing an example of setting reduction priorities according to an embodiment of the present invention; [Figure 4] FIG. 1 is a diagram showing an example of an improvement algorithm for a delivery plan according to an embodiment of the present invention. [Diagram 5]FIG. 1 is a conceptual diagram for explaining a specific example of transfer according to an embodiment of the present invention. [Figure 6] FIG. 1 is a table showing an example of an extraction rule based on reduction priorities according to an embodiment of the present invention. [Figure 7] FIG. 1 is a schematic diagram showing an example of a UI screen configuration in a conventional configuration as a comparative example. [Figure 8A] FIG. 2 is a schematic diagram showing an example of a configuration of a UI screen according to an embodiment of the present invention; [Figure 8B] FIG. 2 is a schematic diagram showing an example of a configuration of a UI screen according to an embodiment of the present invention; [Figure 8C] FIG. 2 is a schematic diagram showing an example of a configuration of a UI screen according to an embodiment of the present invention; [Figure 9] 1 is a flowchart of an overall process according to an embodiment of the present invention; [Figure 10] 1 is a flowchart of a delivery plan calculation process according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] (Background to the content 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. In addition to cases where it is desirable to reduce the number of vehicles used as much as possible, there are various needs in which it is not possible to reduce the use of a certain vehicle or it is better not to reduce it. For example, cases in which it is not possible to reduce the use of a vehicle or it is better not to reduce it include cases where the use of a vehicle is reserved in advance and a usage fee is incurred regardless of whether it is actually used or not.
[0010] The above-mentioned Patent Document 1 discloses a method for allocating luggage to multiple vehicles to which luggage has not yet been allocated, but does not fully consider methods for allocating luggage to vehicles or reducing the number of vehicles in use in accordance with the above-mentioned situations.
[0011] Therefore, in the following embodiment, 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, each embodiment specifically disclosing the delivery plan generation device and delivery plan generation method according to the present disclosure will be described in detail. However, more detailed explanation than necessary may be omitted. For example, detailed explanation of already well-known matters and duplicate explanation of substantially the same configuration may be omitted. This is to avoid the following explanation becoming unnecessarily redundant and to facilitate understanding by those skilled in the art. Note that the attached drawings and the following explanation are provided to enable those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims.
[0013] <Embodiment 1> Hereinafter, as a first embodiment of the present invention, an example of formulating (generating) a delivery plan for delivering multiple packages will be described. In this embodiment, the delivery plan is a delivery route plan for delivering packages (items) from a base to multiple delivery destinations using at least one delivery vehicle (e.g., truck) within a predetermined period (e.g., within a single day). The delivery route corresponds to the driving sequence to multiple delivery 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." 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." Normally, 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 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 base of a delivery company, or may be configured as a cloud-type device on a network.
[0016] The delivery plan generating 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 referring to various databases (hereinafter, DB) stored in the storage unit 120 or reading out programs. The storage unit 120 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 (Random Access Memory), a ROM (Read Only Memory), or a HDD (Hard Disk Drive).
[0017] The UI unit 160 is a part for accepting operations by a user of the delivery plan generating device 100 and outputting various information. The UI unit 160 may be composed of a display, a mouse, a keyboard, and the like. The communication unit 170 is an interface for communicating with an external device via the network 300. There is no particular limitation on the communication standard that the communication unit 170 can support, and it does not matter whether it is wired or wireless. In addition, it 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, a tablet terminal, or a 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 referring to various data stored in the storage unit 202 and 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 an external device 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 Global Navigation Satellite System (GNSS) such as a Global Positioning System (GPS), 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 generating device 100 implements a distance matrix generating unit 111, a delivery plan calculating unit 112, a priority derivation unit 113, a screen generating unit 114, and a DB management unit 115. Note that the configuration of the functional blocks is an example, and the function of one block may be divided in more detail, or the functions of multiple blocks may be configured together. Note that here, a configuration example focusing on the functions according to this embodiment is shown, and the delivery plan generating device 100 may further include other functions.
[0022] The distance matrix generating unit 111 generates a matrix (distance matrix) for calculating the delivery cost for determining the delivery route based on the network and features of the roads used as the delivery route. For example, the method of JP 2019-082755 A by the applicant of the present application can be used as the method for the delivery cost, and the same method is used in the present embodiment. The delivery plan calculating unit 112 calculates the delivery plan using the distance matrix and various information described later. The priority derivation unit 113 derives the priority related to the reduction for the vehicle. A specific example of the priority and the derivation thereof will be described later. The screen generating unit 114 generates various UI screens to be provided to the delivery plan generating 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 generating 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 details, or multiple DBs may be combined to form a single DB.
[0024] Vehicle information DB130 is a database for managing information on vehicles used for delivery. Specific examples of vehicle information according to this embodiment will be described later. Parcel information DB140 is a database for managing information related to parcels. Details of parcel information according to this embodiment will be described later. Priority information DB150 is a database for managing information on priority levels set for each vehicle. Details of 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 be further 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 inputting information by a user, etc.
[0026] When using the delivery plan generating device 100 from the client terminal 200, the delivery plan generating 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 generating device 100 installed in the client terminal 200. Furthermore, the division of functions between the delivery plan generating device 100 and the client terminal 200 is not limited to the configuration in Fig. 1, and a configuration in which some of the functions of the delivery plan generating device 100 are implemented on the client terminal 200 side may also be used.
[0027] [Example data] Fig. 2 shows an example of the configuration of various information used in this embodiment. Fig. 2(a) 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. Fig. 2(b) 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 baggage information 133, maximum load capacity 134, owner information 135, and reduction priority 136. The vehicle identification information 131 is identification information for uniquely identifying the vehicle. The vehicle identification information 131 may be automatically assigned by the system, for example. The allocation status information 132 indicates whether or not baggage has already been allocated to the vehicle. In this embodiment, each vehicle is managed as "new" when it is not allocated, and as "existing" when it is already allocated. The allocated baggage information 133 indicates identification information of the baggage for uniquely identifying the baggage already allocated to the vehicle. For a vehicle that is not allocated baggage, i.e., a "new" vehicle, "none" is indicated in the allocated baggage information 133.
[0029] The maximum load capacity 134 indicates the load capacity of the vehicle, that is, the amount of cargo that can be loaded. Here, for ease of explanation, it is indicated by an integer value, but it may be indicated by 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 owned by the company that is always available, or a "other company" vehicle owned by another company that is temporarily available by arranging with an external party, etc. The reduction priority 136 is an index for allocating cargo to the vehicle, and is set on the system side. A specific example of the reduction priority will be described later with reference to FIG. 3.
[0030] The luggage information is managed by associating luggage identification information 141, luggage amount 142, and designated delivery time information 143. The luggage identification information 141 is identification information for uniquely identifying the luggage. For example, the luggage identification information 141 may be automatically assigned by the system. The luggage amount 142 indicates the amount of the luggage in question, corresponding to the vehicle's load capacity (more specifically, the maximum load capacity 134). Here, it is indicated by an integer value for simplicity of explanation, but it may be indicated by dimensions, etc. The designated delivery time information 143 indicates the delivery time designated for the luggage. Although omitted in FIG. 2(b), the luggage information may further include information for identifying whether the luggage has already been assigned to any delivery vehicle, i.e., whether it is a "new luggage" or an "existing luggage", in correspondence with the assigned luggage 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. Meanwhile, as for cargo information, information on various cargo provided from external devices is 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 that can be used in the delivery plan out of all vehicles, 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. Priority information is managed in association with vehicle identification information 151 and reduction priority 152. Vehicle identification information 151 is identification information for uniquely identifying a vehicle, and corresponds to vehicle identification information 131 in FIG. 2(a). Reduction priority 152 is an index determined by the delivery plan generating device 100 based on user settings, contents of package allocation, and the like, and corresponds to reduction priority 136 in FIG. 2(a).
[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, that is, a new package is always assigned to the vehicle and used for delivery. Although details will be described later, for a vehicle with a reduction priority of "0", whether the vehicle is a "new vehicle" or an "existing vehicle", a delivery plan generation process is repeatedly attempted so that at least one new package is assigned to the 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, and a higher value indicates that a new package is assigned with higher priority. In this embodiment, the reduction priority is specified in three stages from 0 to 2, but is not limited to this. For example, more stages may be set according to a combination of attributes set for the vehicle (for example, the vehicle's load capacity and function (refrigerated vehicle / freezer vehicle), etc.). The reduction priority may also be set by classification such as major classification, medium classification, and minor classification. For example, when 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 medium classifications.
[0034] In addition, in this embodiment, it is assumed that a mode setting related to reduction in the number of vehicles to be used can be performed for a plurality of available vehicles. Specifically, the user can specify either reducing the number of vehicles to be used as much as possible among the plurality of 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"). When there is a sufficient amount of cargo to use all of the vehicles, the second delivery plan mode may be a mode in which all of the vehicles are used, that is, a mode in which the number of vehicles to be used is fixed. In addition, another mode may be selectable as the delivery plan mode. For example, the mode may be a mode in which, after receiving the specification of a plurality of available vehicles, the range of the number of vehicles to be actually used among them is specified.
[0035] 3(a) shows an example of reduction priorities determined when vehicles A, B, and C are specified as vehicles available for delivery and the second delivery plan mode is specified. In this case, the three specified vehicles are 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] 3(b) shows an example of reduction priorities determined when vehicles A, B, and C are specified as vehicles available for delivery and the first delivery plan mode is specified. In this case, the three specified vehicles are 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 a delivery plan, more vehicles may be specified as vehicles that can be used in a delivery plan.
[0038] In this embodiment, an initial solution of the delivery plan is derived, and three types of improvement methods are applied to the initial solution to determine the delivery plan. Here, the initial solution is a solution in which the number of vehicles used and the delivery route are not efficient. In this embodiment, a delivery plan that can perform efficient delivery is determined by improving this initial solution. In the process of improvement, the delivery route and the number of vehicles used are made efficient, and the allocation of luggage to each vehicle is adjusted so that other constraints such as the allocation of luggage that requires temperature control are satisfied, so the initial solution does not necessarily have to be an efficient solution, and it does not have to be a solution that satisfies the constraints. As an improvement method for the delivery plan according to this embodiment, "replacement", "exchange", and "transfer" are given as examples. Note that the derivation of the initial solution of the delivery plan may use, for example, a method described in JP 2019-082755 A by the applicant of the present application, and a detailed description here will be omitted. In this specification, "improvement" is explained as being synonymous with a reduction in the overall delivery cost. In this method, the delivery plan obtained after improvement may change depending on the initial solution that is the basis for improvement, so the delivery plan obtained is not necessarily the most efficient delivery plan among all delivery plans. However, with the current state of the art, 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 relatively efficient delivery plan that has been improved in a short time and start delivery, rather than spending a long time creating the most efficient delivery plan and then starting delivery. Therefore, in this embodiment, a configuration is adopted in which a delivery plan at any time point 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. For the above substitution, exchange, and transfer, it is determined whether or not to apply one of the methods based on the cost of delivering the package.
[0040] FIG. 4 shows an example of an improvement to a delivery plan when replacement, exchange, and transfer are respectively performed on two delivery plans obtained as initial solutions. Note that replacement, exchange, and transfer are not limited to one of them, and these methods may be repeatedly applied to improve the entire delivery plan. 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 actions, replacement, exchange, and transfer, only transfer changes the number of packages assigned in the two delivery plans. In the example in Figure 4, before the change, both 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 the delivery plan using reduction priority according to the present embodiment is a method that focuses on transfer among the above three improvement methods. Since the number of packages assigned to each vehicle does not change between replacement and exchange, when focusing only on the number of vehicles used, the delivery plan may be determined by applying only transfer. However, when only transfer is applied, there is a risk that the delivery route of each vehicle will become inefficient, so when creating a delivery plan that includes the delivery route, it is more preferable to also apply replacement and exchange.
[0043] Fig. 5 shows a specific example of a method for transfer. In Fig. 5, a rectangle indicates the delivery origin (base 501) of the package, and the package is loaded onto a vehicle from the base 501 and delivered to the delivery destination. After delivery of the package is completed, the vehicle returns to the base 501, loads the package again, and delivers it again.
[0044] FIG. 5 shows delivery plans for two vehicles. In this example, the example shows the transfer of the parcel 503e allocated to the lower delivery plan between the parcel 502b in the upper delivery plan and the base 501. As a result of the transfer, a total of five parcels 502a, 502b, 503a, 503b, and 503e are allocated to the vehicle corresponding to the upper delivery plan, and a total of two parcels 503c and 503d are allocated to the vehicle corresponding to the lower delivery plan. Note that the parcels 502a and 502b are parcels whose allocation destinations have already been determined and whose allocation destinations are desirably not changed (i.e., "existing parcels"). For such existing parcels, for example, the delivery route has already been fixed, the delivery driver is limited, and so on, and it is assumed that the delivery cost will increase by changing the allocation destination.
[0045] [Extraction rule change table] 6 is an example of a change table 600 that defines combinations between vehicles for which reduction priorities are set, used in a search at the time of 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 numbers are referenced. Specific uses of the change table 600 will be described later together with a flowchart.
[0046] [UI screen] Hereinafter, a configuration example of a UI screen related to a delivery plan that can be displayed on the UI unit 160 of the delivery plan generating device 100 according to this embodiment and the UI unit 204 of the client terminal 200 will be described. First, as a comparative example with the UI screen according to this embodiment, an example of a conventional UI screen and an allocation example are shown in FIG.
[0047] Fig. 7(a) shows an example of the state of an existing vehicle that already has two existing loads assigned to it, and Fig. 7(b) shows an example of the state of a new vehicle that has no loads assigned to it. 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 table 704. The assigned vehicle information 701 indicates identification information of a vehicle assigned as a delivery vehicle. The assigned driver information 702 indicates identification information of a delivery person assigned as a delivery person. The available delivery time information 703 indicates a work time period during which delivery is possible by a delivery person (or vehicle). Two existing packages ("Package 1" and "Package 2") are assigned to the schedule table 704, as shown by icons 706 and 707. New packages can be additionally assigned to an unassigned area 705 of the schedule table 704.
[0049] Consider, for example, allocating new cargo in the configuration shown in FIG. 7. In this case, for example, when new cargo is allocated to an existing vehicle as shown in FIG. 7(a), there is no allocation to a new vehicle as shown in FIG. 7(b), so the use of new vehicles can be reduced. On the other hand, when new cargo is added to an existing vehicle in the schedule table 704 shown in FIG. 7(a), it may result in a delivery plan that is inefficient overall. For example, as a result of allocating new cargo, the existing vehicle may return to the base once, load the newly allocated cargo, and resume delivery. In such a case, the efficiency of the entire delivery is improved by using a new vehicle to which cargo has not been allocated. In other words, when allocating new cargo and reducing the number of vehicles to be used, the conditions at the time of the allocation must be considered.
[0050] Fig. 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 of Fig. 7 shown as a conventional example. The reduction priority information 804 displays the reduction priority determined by the delivery plan generating 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 among a plurality of specified vehicles. FIG. 8A(a) corresponds to an existing vehicle, and two existing packages ("Package 1" and "Package 2") have already been assigned as shown in icons 807 and 808. On the other hand, FIG. 8A(b) corresponds to a new vehicle, and no package has been assigned. Consider the case of assigning "Package 3" as a new package. In this case, the new vehicle shown in FIG. 8A(b) has a reduction priority of "0", so the use 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 in which the vehicle is used by preferentially allocating packages. As a result, a new package, "Package 3", is assigned as shown in icon 817 of FIG. 8A(b).
[0052] At this time, the free space 806 of the schedule table 805 of FIG. 8A(a) may display that no new luggage has been added. For example, as shown in FIG. 8A(a), a message of "no new luggage added" may be displayed. Similarly, the free space 816 of the schedule table 815 of FIG. 8A(b) may display that new luggage has been added. For example, as shown in FIG. 8A(b), a message of "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 reason for it on the UI screen. 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 existing vehicles is used as an index for allocating (or not allocating) new luggage to the existing vehicle, and is not an index for reducing the use of the existing vehicle itself. That is, 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 reduction priority set.
[0053] FIG. 8B shows an example of a UI screen display when generating a delivery plan by reducing vehicles to be used as much as possible among the multiple specified vehicles. FIG. 8B(a) corresponds to an existing vehicle, and existing luggage ("Luggage 1" and "Luggage 2") have already been assigned as shown in icons 827 and 828. On the other hand, FIG. 8B(b) corresponds to a new vehicle, and luggage has not been assigned. Then, consider a case where "Luggage 3" is assigned as a new luggage. In this case, the vehicle shown in FIG. 8B(b) has a reduction priority of "2", and therefore a higher reduction priority is set, so a delivery plan is generated that suppresses the allocation of new luggage and promotes reduction. As a result, as shown in icon 829 of FIG. 8B(a), new luggage "Luggage 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 luggage assigned, so its use can be reduced. At this time, in addition to the luggage allocation result on the UI screen, information on the reduced vehicles (for example, the number of vehicles and a list) among the multiple specified vehicles may be displayed and presented to the user together 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 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 it. 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. At this time, 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 update status of the allocation of the 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] [Distribution plan generation process] 9 is a flowchart of a delivery plan generation process executed by the delivery plan generation device 100 according to this embodiment. This process flow may be realized 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 is started, some vehicles may already have cargo assigned to them, i.e., when this process flow is started, existing vehicles and existing cargo may be set.
[0058] The delivery plan generating device 100 accepts input of vehicle information and parcel information from a user (step S901). For example, the input vehicle information may specify a plurality of vehicles to be the targets of generating a delivery plan from among the vehicles registered in the vehicle information DB 130. The specified vehicles may include new vehicles and existing vehicles. The input parcel information corresponds to new parcels that are not assigned to any vehicle among the parcels registered in the parcel information DB 140. One new parcel may be specified, or multiple new parcels may be specified collectively. Furthermore, the delivery plan generating device 100 accepts the specification of a mode for the specified multiple vehicles, either reducing the number of vehicles to be used as much as possible (first delivery plan mode) or using all vehicles (second delivery plan mode). The various information here 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 generating device 100 or the UI unit 204 of the client terminal 200.
[0059] The delivery plan generating device 100 determines whether the setting accepted in step S901 is a reduction in the number of vehicles, i.e., whether the first delivery plan mode is specified (step S902). If a reduction in the number of vehicles is specified (step S902: YES), the process of the delivery plan generating device 100 proceeds to step S905. On the other hand, if the setting accepted in step S901 is to use all the specified vehicles, i.e., if the second delivery plan mode is specified (step S902: NO), the process of the delivery plan generating device 100 proceeds to step S903. Note that, since two types of delivery plan modes are assumed in this embodiment, if the setting accepted in step S901 is not a reduction in the number of vehicles, it is treated as if the second delivery plan mode was specified. If there are further delivery plan modes such as a third delivery plan mode, the process 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 vehicles specified. 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 vehicles specified. Through the processes of steps S903 and S904, reduction priorities such as those shown in FIG. 3(a) are set. After that, the process of the delivery plan generating device 100 proceeds to step S911.
[0062] The delivery plan generating device 100 determines whether there is a fixed vehicle among the multiple vehicles specified in step S901 (step S905). A fixed vehicle here is a vehicle whose use cannot be reduced. Examples of fixed vehicles include vehicles owned by the delivery company itself and vehicles whose arrangement cannot be canceled, which cannot reduce operating costs even if they are reduced, and vehicles to which cargo is assigned before the delivery plan is created and whose use is difficult to stop. For example, as shown in FIG. 2(a), such information may refer to the owner information 135 of the vehicle information managed in the vehicle information DB 130 and determine a vehicle that is "our company" as a fixed vehicle. As described above, in this embodiment, it is not assumed that existing cargo that has been assigned before the delivery plan is created will be reassigned to another vehicle. This is because the assignment of cargo to an existing vehicle is arranged by another delivery company, etc., so that it is difficult for the user of the delivery plan generating device 100 to transfer the cargo to another vehicle at his / her discretion, or it is practically difficult for the driver to transfer the cargo from an existing vehicle to another vehicle. Therefore, the use of existing vehicles is not reduced regardless of whether they are fixed vehicles or not. However, if it is permitted to reallocate existing cargo allocated to existing vehicles to other vehicles, it may be possible to switch whether to treat existing vehicles as fixed vehicles or not based on vehicle information, etc. In addition, it may be determined whether the information is fixed or not 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 status regarding arrangement is arranged (cannot be changed) may be treated as a fixed vehicle. If there is a fixed vehicle (step S905: YES), the process of the delivery plan generating device 100 proceeds to step S908. On the other hand, if there is no fixed vehicle (step S905: NO), the process of the delivery plan generating 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 vehicles specified. 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 vehicles specified. After that, the process 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 multiple 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 multiple 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 vehicles specified. After that, the process 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). The output here may be displayed on a UI screen such as those shown in Fig. 8A to Fig. 8C. Then, this processing flow ends.
[0070] (Distribution plan calculation process) FIG. 10 is a flowchart of the delivery plan calculation process according to this embodiment, and corresponds to step S911 in FIG.
[0071] The delivery plan generating 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 use a known method described in, for example, JP 2019-082755 A, and is not particularly limited. In addition, an initial solution for the delivery plan may be obtained based on the real-time road congestion status, etc., in addition to the road cost based on predefined map information. Here, new cargo is assigned to each vehicle regardless of information such as reduction priority. In addition, at the time of obtaining the initial solution, the replacement or exchange improvement method may be applied among the three improvement methods described above.
[0072] The delivery plan generating device 100 refers to 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 among the specified multiple vehicles (step S1002). Specifically, when "1" in the sequence 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 is transferred (transfer destination). Note that if there is no vehicle with the combination of reduction priorities indicated in the extraction rule, the next extraction rule is referenced according to the sequence 601.
[0073] The delivery plan generating device 100 determines the cargo to be transferred that is assigned to the vehicle from which the transfer is to be made among the two extracted vehicles (step S1003). The cargo determined here is the cargo to be newly assigned to the vehicle as a new cargo. In other words, existing cargo is excluded from the cargo to be transferred here.
[0074] The delivery plan generating 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 there has been an improvement may be predefined. 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 that the delivery time has been shortened. If improvement or reduction is possible (step S1004: YES), the processing of the delivery plan generating 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 generating device 100 proceeds to step S1007.
[0075] The delivery plan generating device 100 judges whether or not the number of new packages assigned to the non-reducible vehicle, i.e., the vehicle with the reduction priority of "0", is 0 after the transfer of the new package (step S1005). That is, it is judged whether or not at least one new package is assigned to the vehicle with the reduction priority of "0". If the number of new packages assigned to the non-reducible vehicle is not 0 (step S1005: NO), the process of the delivery plan generating device 100 proceeds to step S1006. On the other hand, if the number of new packages assigned to the non-delivery vehicle is 0 (step S1005: YES), the process of the delivery plan generating device 100 proceeds to step S1009. In addition to the condition that at least one new package is assigned to the non-reducible vehicle, further condition judgment may be performed. For example, a condition based on the vehicle attribute may be judged. More specifically, a constraint judgment may be performed, such as that refrigerated packages are assigned only to refrigerated cars. In addition, if there is a constraint violation, the delivery plan generation device 100 may be configured to further substitute, exchange, or transfer parcels 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 process of the delivery plan generating device 100 returns to step S1002, and further repeats the process based on the solution at that time.
[0077] The delivery plan generating device 100 determines whether there is any unprocessed new package among the new packages assigned to the source vehicle (step S1007). If there is any unprocessed new package (step S1007: YES), the delivery plan generating device 100 proceeds to step S1008. If there is no unprocessed new package (step S1007: NO), the delivery plan generating device 100 proceeds to step S1009.
[0078] The delivery plan generating device 100 determines the new unprocessed cargo assigned to the source vehicle as a processing target (step S1008). Then, the process of the delivery plan generating device 100 returns to step S1004 and the process is repeated.
[0079] The delivery plan generating device 100 determines whether or not the process based on the last extraction rule among the extraction rules defined in the change table 600 shown in Fig. 6 has been completed (step S1009). If the process based on the last extraction rule has been completed (step S1009: YES), the process of the delivery plan generating device 100 proceeds to step S1010. On the other hand, if the process based on the last extraction rule has not been completed, that is, if there is an unprocessed extraction rule (step S1009: NO), the process 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 of the delivery plan (step S1010), and then ends this processing flow, and returns to the processing of FIG.
[0081] The delivery plan generating device 100 determines new transfer source and transfer destination vehicles from among the specified 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 is a vehicle with a reduction priority of "2", and the transfer destination vehicle is a vehicle with a reduction priority of "1". If there is no vehicle with the combination of reduction priorities indicated in the extraction rule, the next extraction rule is further referenced according to the order 601. Although three values, "0", "1", and "2", are used in setting the reduction priorities, two of these may be used. In that case, the combination of the two reduction priorities used may be used as the extraction rule, or the setting value of the reduction priority in each step of the definition of the extraction rule or the processing flow may be appropriately adjusted. Then, the processing of the delivery plan generating device 100 proceeds to step S1003, and the processing is repeated.
[0082] As described above, the delivery plan generating 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) that can be used in the 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 performing reduction preferentially for each of the plurality of vehicles based on the 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 cargo to each of the plurality of vehicles based on the reduction priority, and the lower the reduction priority value of the vehicle, the higher the priority of the new cargo is allocated. This makes it possible to reduce and allocate vehicles according to the situation based on the user's designation regarding the use of vehicles in the delivery plan. As a result, even if existing vehicles to which cargo has been allocated and new vehicles to which cargo has not been allocated are mixed, it becomes possible to generate an appropriate delivery plan based on the reduction setting desired by the user.
[0083] Furthermore, when a first delivery plan mode in which cargo is allocated to all of the multiple vehicles is specified, the setting unit sets the reduction priority of the multiple vehicles to which cargo has already been allocated higher than that of the vehicles to which cargo has not been allocated. Furthermore, when a second delivery plan mode in which the use of multiple vehicles is reduced is specified, the setting unit sets the reduction priority of the multiple vehicles to which cargo has not been allocated higher than that of the vehicles to which cargo has already been allocated. This makes it possible to appropriately switch and set the reduction priority for reducing the number of vehicles and allocating cargo based on the user's designation.
[0084] The attribute information also includes information on the possibility of reduction (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 reduction in the use of a vehicle that has an attribute that cannot be reduced, and to create a delivery plan that gives the vehicle higher priority in use.
[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 result of the allocation of new cargo to a vehicle and the reduction priority set for the vehicle. The delivery plan screen also displays the result of reduction for multiple vehicles due to the allocation of new cargo. This makes it possible to notify the user of the reason for the allocation of new cargo to each vehicle and the reduction result.
[0086] (Other variations) In the above-described embodiment, even when the reduction priority is set to four or more stages, 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 stages according to the vehicle load, different priorities may be set according to 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, the total number of vehicles to be used is reduced by leaving vehicles with a large load and reducing vehicles with a small load, so the lower the vehicle's load, the higher the reduction priority is set. In addition, in the second delivery plan mode, vehicles with a small load must also be used, so many vehicles cannot be used, so the higher the reduction priority is set for vehicles with a large load.
[0087] The present disclosure also covers programs and storage media that realize the functions of the apparatus of the above-mentioned embodiments and that are supplied to the apparatus via a network or various storage media and that are read and executed by a computer within the apparatus.
[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 the examples. It is clear to a person skilled in the art that various modifications, corrections, substitutions, additions, deletions, and equivalents may be made within the scope of the claims, and it is understood that these also naturally belong to the technical scope of the present disclosure. In addition, the components in the various embodiments described above may be arbitrarily combined within the scope of the invention.
[0089] (Additional Note) The above description of the embodiments discloses the following techniques. (Technology 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 that is 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. This configuration enables 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 if there is a mixture of existing vehicles to which cargo has already been allocated and new vehicles to which cargo has not yet been allocated, it is possible to generate an appropriate delivery plan based on the reduction settings desired by the user.
[0090] (Technology 2) 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 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. With this configuration, it becomes possible to appropriately switch and set reduction priorities for realizing reduction in vehicles and allocation of cargo based on user specifications.
[0091] (Technology 3) When a second delivery plan mode for reducing utilization of the plurality of vehicles is specified, the setting unit sets a reduction priority for vehicles among the plurality of vehicles to which no cargo is assigned, higher than a reduction priority for vehicles to which cargo is already assigned. With this configuration, it becomes possible to appropriately switch and set reduction priorities for realizing reduction in vehicles and allocation of cargo based on user specifications.
[0092] (Technology 4) The attribute information includes information regarding whether or not reduction is possible, and the setting unit sets a reduction priority to be the lowest for a vehicle that is not assigned cargo and cannot be reduced. With this configuration, it becomes possible to appropriately switch and set reduction priorities for achieving vehicle reduction and cargo allocation, taking into account fixed vehicles and new vehicles, based on user specifications.
[0093] (Technology 5) The delivery plan generating 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 a result of allocation of new cargo to a vehicle and a reduction priority set for the vehicle. 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.
[0094] (Technology 6) The delivery plan generating device according to technology 5 displays the result of reduction in the number of vehicles due to the allocation of new cargo on the delivery plan screen. 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.
[0095] (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 a delivery plan mode 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 the lower the reduction priority value of a vehicle, the higher the priority for allocating new cargo. This configuration enables 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 if there is a mixture of existing vehicles to which cargo has already been allocated and new vehicles to which cargo has not yet been allocated, it is possible to generate an appropriate delivery plan based on the reduction settings desired by the user. [Industrial Applicability]
[0096] The present disclosure is useful as a delivery plan generating device and a delivery plan generating method. [Explanation of symbols]
[0097] 100...Dispatch plan generating device 110... Processing section 111...Distance matrix generation unit 112...Distribution plan calculation section 113...Priority derivation part 114...Screen generation section 115...DB management department 120...Storage section 130…Vehicle information DB 140...Baggage information DB 150...Priority information DB 160...UI section 170…Communications Department 200: Client terminal 201... Processing section 202...Storage section 203…Communications Department 204...UI section 300…Network
Claims
1. A reception unit that receives a designation of a plurality of vehicles available for a delivery plan and a delivery plan mode for the plurality of vehicles; a setting unit that sets a reduction priority as an index for preferentially performing reduction for each of the plurality of vehicles based on attribute information set for each of the plurality of vehicles and the delivery plan mode; A generation unit that generates a delivery plan by allocating new packages to each of the plurality of vehicles based on the reduction priority; having A vehicle with a lower reduction priority value is given priority in allocating new cargo. Dispatch plan generator.
2. 2. The delivery plan generating device according to 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 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.
3. 2. The delivery plan generating device according to claim 1, wherein when a second delivery plan mode for reducing utilization of the plurality of vehicles is specified, the setting unit sets a reduction priority for vehicles among the plurality of vehicles to which no cargo is assigned, higher than a reduction priority for vehicles to which cargo is already assigned.
4. The attribute information includes information regarding whether or not the reduction is possible, The delivery plan generating device according to claim 1 , wherein the setting unit sets the reduction priority to be the lowest for a vehicle to which no cargo is assigned and for which reduction is not possible.
5. A display control unit that displays the delivery plan generated by the generation unit on a delivery plan screen, The delivery plan generating device according to claim 1 , wherein the delivery plan screen displays a result of allocation of new cargo to a vehicle and a reduction priority set for the vehicle.
6. The delivery plan generating device according to claim 5 , wherein the delivery plan screen displays a result of reduction in the number of vehicles due to new cargo allocation.
7. The processor and memory work together to a receiving step of receiving a designation of a plurality of vehicles available for a delivery plan and a delivery plan mode for the plurality of vehicles; a setting step of setting a reduction priority as an index for preferentially performing reduction for each of the plurality of vehicles based on attribute information set for each of the plurality of vehicles and the delivery plan mode; generating a delivery plan by allocating new packages to each of the plurality of vehicles based on the reduction priority; having A vehicle with a lower reduction priority value is given priority in allocating new cargo. How to generate a delivery plan.
Citation Information
Patent Citations
Delivery planning method and program for executing the same
JP2002302257A
