Delivery management device and delivery management method

Abstract

To appropriately correct a delivery plan that is automatically generated.SOLUTION: According to this disclosure, a delivery management device includes a plan part, a presentation part and a correction part. The plan part presents delivery plan information showing a delivery plan on the basis of delivery request information and vehicle related information. The delivery plan includes a route and a delivery time of at least one delivery section where a deliverer delivers at least one package by a vehicle. The delivery request information shows at least one delivery destination and delivery time for delivering at least the one package. The vehicle related information shows information about the vehicle used by the deliverer to deliver at least the one package to at least the one delivery destination. The presentation presents a route of a candidate for review among routes of at least the one delivery section included in a generated delivery plan on the basis of the generated delivery plan information and change history information showing a history of past changes to the delivery plan. The correction part corrects the delivery plan on the basis of a change instruction to the received delivery plan.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The present disclosure relates to a delivery management device and a delivery management method. [Background technology]

[0002] Conventionally, there is known a technology that generates a delivery plan (delivery schedule) such as the delivery route and sequence for a vehicle that loads one or more packages and delivers them to one or more delivery destinations through optimization calculation. If a delivery plan automatically generated using optimization calculation or the like is not appropriate, the operator who plans the delivery plan may manually modify the presented delivery plan.

[0003] For example, Patent Document 1 discloses a technology for reducing the workload associated with correcting a delivery plan by preparing parameters to be changed corresponding to improvement items in advance and generating a delivery plan in which the parameters to be changed are changed in response to receiving the improvement items for the presented delivery plan. Also, for example, Patent Document 2 discloses a technology for creating a delivery plan by a computer even when there is no experienced planner and sufficient performance data is not available, by performing machine learning using instructions from a user for a presented delivery plan as training data so as to output an appropriate delivery plan that satisfies delivery conditions. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-086235 [Patent Document 2] JP 2020-030663 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, even when an operator modifies an automatically generated delivery plan, there are cases where the modified delivery plan is still inappropriate, such as not receiving emotional understanding from the deliverer who makes the deliveries, or causing the deliverer stress.

[0006] The problem that the present disclosure aims to solve is to appropriately correct an automatically generated delivery plan. [Means for solving the problem]

[0007] The delivery management device according to the present disclosure includes a planning unit, a presentation unit, and a correction unit. The planning unit presents delivery plan information indicating a delivery plan based on delivery request information and vehicle-related information. The delivery plan includes a route of at least one delivery section in which a deliverer delivers at least one package by vehicle and the delivery time. The delivery request information indicates at least one delivery destination to which the at least one package is delivered and the delivery time. The vehicle-related information indicates information on the vehicle used by the deliverer to deliver the at least one package to the at least one delivery destination. The presentation unit presents a route to be reviewed among the routes of the at least one delivery section included in the generated delivery plan based on the generated delivery plan information and change history information indicating a history of past changes to the delivery plan. The correction unit corrects the delivery plan based on a change instruction for the received delivery plan. Effect of the Invention

[0008] According to the present disclosure, an automatically generated delivery plan can be appropriately corrected. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a delivery management system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a configuration of a vehicle according to the embodiment. [Diagram 3]FIG. 3 is a diagram illustrating an example of a hardware configuration of each device in the delivery management system according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a functional configuration of the delivery management device according to the embodiment. [Diagram 5] FIG. 5 is a diagram illustrating an example of a functional configuration of an environmental information gathering device mounted on a vehicle according to an embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the delivery request information according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of vehicle information according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of area information according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of driver information according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of delivery plan information according to the embodiment. [Figure 11] FIG. 11 is a flowchart showing an example of the flow of the delivery management process executed by the delivery management device according to the embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a display screen displayed in the process of FIG. [Figure 13] FIG. 13 is a diagram showing another example of the display screen displayed in the process of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, with reference to the drawings, embodiments of a delivery management device, a vehicle, a delivery management system, a delivery management method, a program, and a storage medium according to the present disclosure will be described.

[0011] In the description of the present disclosure, components having the same or substantially the same functions as those described above with respect to the previously-mentioned drawings may be given the same reference numerals, and the description may be omitted as appropriate. In addition, even when the same or substantially the same parts are shown, the dimensions and ratios of the components may be different depending on the drawing. In addition, for example, from the viewpoint of ensuring the visibility of the drawings, reference numerals may be given only to the main components in the description of each drawing, and reference numerals may not be given to components having the same or substantially the same functions as those described above with respect to the previously-mentioned drawings.

[0012] Hereinafter, a case will be described in which the technology according to the present disclosure can be applied to the delivery of various packages, such as LP (Liquefied Petroleum) gas and parcels delivered by home delivery service.

[0013] The technology according to the present disclosure can be applied to, for example, a business support service or a patrol support service that delivers at least one package such as goods or materials from a business base such as a sales office or warehouse to at least one delivery destination. The technology according to the present disclosure can also be applied to transporting people, not limited to packages. For example, the technology according to the present disclosure can be applied to a business support service, a patrol support service, a fleet management service, and a vehicle dispatch support service that supports route sales, visiting activities, and vehicle dispatch services that transport at least one visitor who performs route sales, maintenance, and vehicle dispatch from a business base such as a sales office to at least one visiting destination such as a customer's business base, home, or a location designated by the customer. In this case, the "delivery" according to the present disclosure may be read as "patrol," "visit," or "dispatch." In addition, for example, the technology according to the present disclosure may be applied to a transportation support service that supports a service involving transportation such as a nursing care day care center or after-school day care center that transports at least one user between at least one pick-up and drop-off destination such as the user's home and a business base such as a facility or school. In this case, the "delivery" according to the present disclosure may be read as "pick-up and drop-off."

[0014] Conventionally, there is known a technology that generates a delivery plan, such as a delivery route and sequence, by optimizing calculation for a vehicle that loads one or more packages and delivers them to one or more destinations. If a delivery plan automatically generated using optimization calculation or the like is not appropriate, the operator who plans the delivery plan may manually modify the presented delivery plan.

[0015] For example, there was a technique for reducing the workload associated with correcting a delivery plan by preparing parameters to be changed corresponding to improvement items in advance and generating a delivery plan in which the parameters to be changed are changed in response to receiving improvement items for a presented delivery plan. However, while this reduces the work time, there was a problem in that work mistakes may occur due to oversights or lack of skills.

[0016] In addition, there is a technology for creating a delivery plan by a computer, for example, by performing machine learning using instructions from a user for a presented delivery plan as training data so as to output an appropriate delivery plan that satisfies delivery conditions, even when there is no experienced planner and sufficient performance data is not available. However, there is a problem that the delivery plan created by the computer may be a delivery plan that is not convincing to the operator or does not match the operator's sense.

[0017] Furthermore, even if an operator corrects an automatically generated delivery plan, the corrected delivery plan may still be inappropriate, such as not being understood emotionally by the delivery person who makes the delivery, or causing stress to the delivery person. For example, even if an operator corrects an automatically generated delivery plan, it may not meet the delivery person's wishes, such as "I want to avoid congestion even if it's a long way away," "I don't want to make a U-turn even though it takes time," "That road is narrow for me," or "This order / route is good because it's fast even if it's narrow," in other words, it may be difficult for the delivery person to feel convinced.

[0018] Therefore, the present disclosure aims to appropriately correct an automatically generated delivery plan. More specifically, the present disclosure aims to suppress work errors by a corrector when correcting an automatically generated delivery plan. Here, the corrector is, for example, a deliverer who delivers by vehicle or an administrator who manages delivery. Furthermore, work errors refer to, for example, oversights or corrections made in correcting a delivery plan, and corrections that are not necessarily optimal improvements. Furthermore, corrections that are not necessarily optimal improvements refer to, for example, corrections that are not necessarily optimal improvements due to, not only economic rationality, but also the emotional aspects of the deliverer, the corrector's lack of experience, or the corrector's lack of skill.

[0019] Fig. 1 is a diagram showing an example of the configuration of a delivery management system 1 according to an embodiment. As shown in Fig. 1, the delivery management system 1 includes a management device 10 and a delivery fleet 20. The management device 10 and the delivery fleet 20 are communicatively connected via, for example, a network N. As the network N, for example, a telecommunication line such as the Internet can be used.

[0020] The management device 10 is a device that manages the entire delivery management system 1. The management device 10 is configured to be able to execute a delivery management process according to the embodiment. Here, the management device 10 according to the embodiment is an example of a delivery management device.

[0021] As an example, the management device 10 creates a delivery plan, which is a delivery plan in which a deliverer delivers at least one package to at least one delivery destination using a vehicle 30, and presents it to an operator such as a deliverer or a manager. As an example, the management device 10 extracts a route to be reviewed, which is a route of at least one delivery section among the delivery routes specified in the delivery plan, and presents it to an operator such as a deliverer or a manager. As an example, the management device 10 extracts, as a review candidate, a route that matches a route before or after correction with a history of past changes among the routes of at least one delivery section indicated in the delivery plan. As an example, the management device 10 accepts an instruction to change the delivery plan from an operator (modifier) ​​such as a deliverer or a manager, and modifies the delivery plan based on the change instruction.

[0022] The delivery fleet 20 includes vehicles 30 that perform deliveries in the delivery management system 1. Each of the at least one vehicle 30 is communicatively connected to the management device 10 via a network N, for example.

[0023] 1 illustrates three vehicles 30-1, 30-2, and 30-3, but the present disclosure is not limited to this. The number of vehicles 30 may be one or two, or may be four or more.

[0024] In the present disclosure, the vehicle 30 may be, for example, any vehicle that uses an internal combustion engine, or any vehicle that uses a battery, such as an electric vehicle or a hybrid vehicle. In addition, the vehicle 30 may be, as appropriate, a bicycle, a motorcycle, a vehicle with three or more wheels, a truck, or another automobile, such as a kick scooter.

[0025] Fig. 2 is a diagram showing an example of the configuration of a vehicle 30 according to an embodiment. As shown in Fig. 2, the vehicle 30 has an on-board sensor 31, a driver monitor camera 32, and an environmental information collection device 33. The on-board sensor 31, the driver monitor camera 32, and the environmental information collection device 33 are communicatively connected via an on-board network including, for example, a Controller Area Network (CAN) or Ethernet (registered trademark).

[0026] The on-board sensors 31 include various sensors used for driving assistance such as sonar (Sound Navigation And Ranging) and a panoramic camera, a steering angle sensor, a wheel speed sensor, a brake sensor, an accelerator sensor, an acceleration sensor, a gyro sensor, a Global Positioning System (GPS) sensor, and a Global Navigation Satellite System (GNSS) sensor that outputs position information of the vehicle 30, and an Advanced Driving Assistant System (ADAS) such as an automatic emergency braking (AEB) process and a sudden acceleration prevention process.

[0027] The driver monitor camera 32 is provided, for example, at the front of the interior of the vehicle 30. The driver monitor camera 32 acquires images of the driver of the vehicle 30, i.e., the delivery person, for use in a driver monitor function that monitors the driving posture, line of sight, face direction, and open / closed state of the eyelids of the delivery person.

[0028] The driver monitor camera 32 may be configured to acquire video and audio instead of or in addition to an image. The driver monitor camera 32 may be a camera built into the vehicle 30, or may be a camera of a drive recorder that is retrofitted to the vehicle 30. The driver monitor camera 32 is not an essential component, and may not be installed in the vehicle 30.

[0029] The environmental information collecting device 33 is realized by, for example, a computer such as an ECU (Electronic Control Unit) or an OBU (On Board Unit) provided inside the vehicle 30. Alternatively, the environmental information collecting device 33 may be an external computer installed near the dashboard of the vehicle 30, or may also function as a car navigation device. The environmental information collecting device 33 collects environmental information indicating the inside and outside environments of the driver who is driving the vehicle 30, i.e., the delivery person who is making a delivery using the vehicle 30.

[0030] Here, the environmental information indicating the inside and outside environment of the vehicle during delivery is information for evaluating the stress and emotions felt by the deliverer, such as the facial expression, voice, line of sight, the number and frequency of blinking, gestures such as scratching the head or face, heart rate, and driving conditions such as vehicle speed and number of braking. As an example, the environmental information collecting device 33 collects the captured images of the surroundings of the vehicle 30 obtained by the all-around camera of the on-board sensor 31, or the results of the image analysis, as environmental information indicating the inside and outside environment of the vehicle during delivery, such as the driving conditions of the vehicle 30. As an example, the environmental information collecting device 33 collects the captured images, videos, and voices of the deliverer obtained by the driver monitor camera 32, or the results of the image analysis, video analysis, and voice analysis, as environmental information indicating the inside and outside environment of the vehicle during delivery, such as the facial expression and voice of the deliverer. As an example, the environmental information collecting device 33 is equipped with a digital tachograph (digital driving recorder) that records the speed, driving time, and driving distance of the vehicle 30, and collects the driving conditions of the vehicle 30 obtained by the digital tachograph as environmental information indicating the inside and outside environment of the vehicle during delivery.

[0031] Furthermore, the environmental information collecting device 33 may collect environmental information indicating the surrounding environment, such as the time of delivery of the vehicle 30, weather, and temperature. As an example, the environmental information collecting device 33 may collect images of the surroundings of the vehicle 30 obtained by the all-around camera of the on-board sensor 31, or the results of image analysis thereof, as environmental information indicating the surrounding environment with respect to weather, such as sunny, cloudy, rainy, snowy, or a combination of these. As an example, the environmental information collecting device 33 may collect environmental information indicating the surrounding environment, such as outside temperature and air pressure, in a case where the on-board sensor 31 includes an outside temperature sensor and an air pressure sensor.

[0032] The environmental information collection device 33 may collect environmental information indicating the inside and outside environment of the vehicle and environmental information indicating the surrounding environment from the outside, or a part or all of the information may be realized by the management device 10. For example, the environmental information according to the embodiment may be collected from various sensors separately provided in the delivery management system 1, or collected from the outside of the delivery management system 1 via the Internet, or collected from the management device 10 configured to be able to accept input of environmental information by a deliverer or manager, the HMI (Human Machine Interface) of the vehicle 30, or a mobile terminal such as a smartphone or smartwatch used by the deliverer or manager, or collected from a health device such as a heart rate sensor worn by the deliverer. For example, the environmental information indicating the inside and outside environment of the vehicle may be collected based on input by the deliverer using the management device 10 or a mobile terminal, the result of reading (scanning) the questionnaire information filled out by the deliverer, or input by the manager to the management device 10 or a mobile terminal with reference to the questionnaire result.

[0033] FIG. 3 is a diagram illustrating an example of a hardware configuration of each device in the delivery management system 1 according to the embodiment.

[0034] Each device of the delivery management system 1 (e.g., the management device 10 and the environmental information collecting device 33) has a processor 41, a memory 42, an HMI 43, and a communication I / F (interface) 46, as shown in Fig. 3. The HMI 43 has a display 44 and an input I / F 45. The processor 41, the memory 42, the display 44, the input I / F 45, and the communication I / F 46 are interconnected by a bus 49 or the like, and have a hardware configuration that utilizes a normal computer.

[0035] The processor 41 is an arithmetic device that controls the entire devices in the delivery management system 1. The processor 41 realizes each process described later, for example, by loading a program stored in a ROM (Read Only Memory) of the memory 42 into a RAM (Random Access Memory) and executing the program.

[0036] As the processor 41 according to the embodiment, various processors such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), a dedicated arithmetic circuit realized by an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array), etc. can be used as appropriate.

[0037] The memory 42 stores programs, parameters, etc. that realize various processes by the processor 41. For example, the memory 42 is a main storage device of each device in the delivery management system 1, and includes a RAM that temporarily stores data necessary for various processes by the processor 41. For example, the memory 42 includes various storage media and storage devices such as a ROM, HDD (Hard Disk Drive), SSD (Solid State Drive), and Flash memory that store various data, programs, etc. used by each device in the delivery management system 1.

[0038] The display 44 is an example of an output I / F of the HMI 43. The display 44 is provided, for example, on a dashboard or console of the vehicle 30 so as to be visible to the driver (delivery person). The display 44 is configured to be capable of outputting images and videos. The display 44 is, for example, a liquid crystal display (LCD) or an organic EL (Electro Luminescence) display. The display 44 may be configured as a touch panel display. The display 44 may also be a part of a car navigation device mounted on the vehicle 30. The display 44 may also be a projection-type display I / F such as a Head Up Display (HUD) that projects an image (virtual image) onto a display area provided in front of the driver, for example, on the windshield or dashboard (console). The HMI 43 may include other output I / Fs such as a speaker configured to output notification sounds, warning sounds, and audio. Here, the display 44 according to the embodiment is an example of a display unit.

[0039] The input I / F 45 is realized, for example, as a touch panel of the display 44 serving as a touch panel display. The input I / F 45 may include other input I / Fs such as buttons, dials, switches, and microphones. These input I / Fs 45 are disposed, for example, on the dashboard, instrument panel, steering wheel, console, and the like of the vehicle 30. Here, the input I / F 45 according to the embodiment is an example of a receiving unit.

[0040] In addition, the HMI 43 may be an operation terminal capable of transmitting or receiving signals to the vehicle 30 from outside the vehicle 30, such as a tablet terminal, a smartphone, a smart watch, a remote controller, or an electronic key.

[0041] The communication I / F 46 is an interface for transmitting and receiving data. For example, a communication circuit for wired communication, a communication circuit for wireless communication, or a combination of these can be appropriately used as the communication I / F 46. As a communication circuit for wireless communication, a communication circuit compatible with various standards such as 3G, 4G, Wi-Fi (registered trademark), Bluetooth (registered trademark), etc. can be appropriately used. In addition, for example, the communication I / F 46 of the environmental information collecting device 33 may transmit and receive information to and from the in-vehicle sensor 31, the driver monitor camera 32, and other ECUs via an in-vehicle network.

[0042] 4 is a diagram showing an example of a functional configuration of the management device 10 according to the embodiment. The management device 10 executes a program loaded in the memory 42 by the processor 41, thereby realizing functions as a delivery plan unit 11, a review presentation unit 12, a plan correction unit 13, and a storage unit 14. Here, the delivery plan unit 11, the review presentation unit 12, and the plan correction unit 13 according to the embodiment are examples of a plan unit, a presentation unit, and a correction unit, respectively.

[0043] The delivery plan unit 11 generates a delivery plan based on the delivery request information and the vehicle-related information. Here, the delivery request information indicates at least one delivery destination and delivery time to which at least one package is delivered (see FIG. 6). Furthermore, the vehicle-related information indicates information related to the vehicle 30 used by the deliverer to deliver at least one package to at least one delivery destination (see FIG. 7, FIG. 8, and FIG. 9). Furthermore, the delivery plan indicates a delivery schedule including a route and delivery time of at least one delivery section in which the deliverer delivers at least one package using the vehicle 30 (see FIG. 10). Details of each piece of information will be described later.

[0044] As an example, the delivery plan unit 11 generates a delivery plan that satisfies the conditions defined by the delivery request information and the vehicle-related information by using an algorithm for a combinatorial optimization problem such as the traveling salesman problem. Note that the delivery plan generation algorithm can be arbitrarily applied, and other algorithms for combinatorial optimization problems may be used.

[0045] Furthermore, the delivery plan unit 11 displays delivery plan information (see FIGS. 10, 12, and 13) indicating the generated delivery plan on the display 44, for example, to present it to an operator such as a deliverer or a manager.

[0046] The review presentation unit 12 specifies a route to be reviewed among the routes of at least one delivery section for the delivery route of the delivery plan generated by the delivery planning unit 11. That is, the delivery route of the delivery plan generated by the delivery planning unit 11 is defined by at least one delivery section. In other words, the delivery route is a route combining the routes of at least one delivery section. Here, the review candidate route is a route of a delivery section that is a target for proposing to the operator the creation of an optimal delivery plan or a correction for improving the delivery plan among the delivery routes of the delivery plan.

[0047] As an example, the route to be reviewed is specified based on the delivery plan information generated by the delivery plan unit 11 and the change history information indicating the history of past changes to the delivery plan. For example, the route to be reviewed is a route of at least one delivery section indicated by the delivery plan, the route before or after the change matches the history of past changes.

[0048] Here, the change history information is information regarding deliveries according to past delivery plans, such as environmental information indicating the inside and outside of the vehicle collected by the environmental information collection device 33, or various information generated based on the environmental information.

[0049] As an example, the change history information includes at least deliverer-dependent information indicating the reason for a change that depends on a deliverer in a past change. For example, the deliverer-dependent information is information indicating the reason for at least one of the past changes of distance priority, time priority, turning suppression, bottleneck suppression, congestion suppression, accident risk suppression, and right turn suppression. Here, suppression means, for example, prioritizing avoidance. Moreover, priority may be treated as an absolute condition, or may be treated as a condition with a relatively high priority.

[0050] In other words, the delivery user-dependent information is, for example, a delivery plan that meets the delivery user's wishes, such as "I want to avoid congestion even if it means taking a detour," "I don't want to make a U-turn even though it will take time," "That road is narrow for me," "This order / route is good because it is fast even though it is narrow," or a delivery plan that is easy for the delivery user to accept, or information that indicates the reason for changing the delivery plan.

[0051] As an example, the change history information may include administrator-dependent information indicating the reason for past changes that depend on the administrator. For example, the administrator-dependent information includes information indicating a speed level that specifies a short delivery time from the viewpoint of business efficiency. For example, the administrator may specify "fast LV2" for a highly skilled veteran courier, and "fast LV1" for a less skilled courier, thereby setting information indicating the level of required delivery speed.

[0052] As an example, the change history information includes at least modification attribute information indicating the attributes of the instruction subject who gave the change instruction in the past change. For example, the modification attribute information is information indicating at least one of the instruction subjects of the past change, including information indicating whether the instruction subject is a person or a computer that performs inference using a machine learning model, information indicating whether the person is an expert, and information indicating whether the operator (modifier) ​​who made the modification is a delivery person or an administrator who manages delivery.

[0053] The computer as the command subject is not limited to one that performs inference using a machine learning model with causal relationships and causal directions as known, but may also perform a search to estimate relationships with unknown causal relationships using a machine learning model, or a combination of these. The machine learning model may be, for example, CNN (Convolutional Neural Networks), but may also be another machine learning model. Also, instead of the machine learning model, a calculation model that specifies predetermined calculation formulas and conditions may be used.

[0054] Furthermore, the review presentation unit 12 presents the identified review candidate route to an operator such as a deliverer or a manager, for example, by displaying the route on the display 44. The review presentation unit 12 may present the review candidate route on a display screen presenting delivery plan information (see FIG. 12), or may present the review candidate route on another display screen (see FIG. 13).

[0055] The review presentation unit 12 also generates information on the feelings of the delivery person regarding past changes to the delivery plan, and presents the information to an operator such as a delivery person or a manager together with candidate routes for review, for example by displaying the information on the display 44 (see FIG. 13). Here, the information on the feelings of the delivery person is information regarding deliveries according to past delivery plans, such as environmental information indicating the environment inside and outside the vehicle collected by the environmental information collection device 33, or information in which various information generated based on the environmental information is accumulated.

[0056] Furthermore, the review presentation unit 12 generates information on the delivery person's feelings regarding the delivery route after the change in a predetermined manner, and updates the corresponding change history information in the storage unit 14. Here, the predetermined manner refers to a method of collecting information on the delivery person's feelings, for example, environmental information indicating the environment inside and outside the vehicle during delivery, or a method of acquiring collected environmental information indicating the environment inside and outside the vehicle during delivery.

[0057] As an example, the information regarding the feelings of the deliverer is information indicating the feelings of the deliverer regarding the revised (changed) delivery plan.

[0058] As an example, the information regarding the emotions of the deliverer may be information indicating the change in the emotions (emotion transition) of the deliverer regarding the delivery plan before and after the correction (before and after the change).

[0059] The information on the emotions of the deliverer may be information for evaluating the stress or emotions felt by the deliverer, such as the facial expression, voice, gaze, number and frequency of blinks, gestures such as scratching the head or face, heart rate, driving conditions such as vehicle speed and number of brakes, or may be information indicating the degree of emotion estimated by the review presentation unit 12 using such information. The information indicating the degree of emotion may be information indicating a plurality of stages of emotion levels, such as "good", "normal", and "bad". For example, the higher the movement of the gaze of the deliverer and the number and frequency of blinks, the lower the emotion level is estimated. For example, when a gesture such as scratching the head or face is detected, the lower the emotion level is estimated. For example, the higher the heart rate, the lower the emotion level is estimated. For example, the greater the change in driving conditions such as vehicle speed and number of brakes, the lower the emotion level is estimated.

[0060] Further, the review presenting unit 12 estimates information indicating the current condition of the deliverer based on the work information indicating the work situation of the deliverer (see FIG. 9), and presents it to an operator such as the deliverer or manager together with review candidate routes, for example by displaying it on the display 44 (see FIG. 13). Here, the information indicating the current condition of the deliverer may be information indicating the number of consecutive work days registered as work information, information input by the deliverer or the like via the HMI 43, or information indicating the degree of condition estimated based on these pieces of information. The information indicating the degree of condition may be information indicating a number of condition levels, such as "good", "normal", and "bad". For example, the more consecutive work days, the lower the condition level is estimated.

[0061] Furthermore, the review presentation unit 12 presents environmental information indicating the surrounding environment, including at least one of the time, weather, and temperature when the past change was made, to an operator such as a delivery person or a manager together with the review candidate route, for example, by displaying the environmental information on the display 44 (see FIG. 13). Here, the environmental information indicating the surrounding environment is not limited to the time, weather, and temperature, but may be information regarding other factors that affect delivery according to the delivery plan.

[0062] For example, depending on a preset setting, or when no candidate route for review is extracted, the review presentation unit 12 may not present the candidate route for review. That is, in the delivery management system 1 according to the embodiment, at least the delivery plan information of the delivery plan information and the candidate route for review is displayed by the display 44.

[0063] The plan correction unit 13 receives a change instruction from an operator such as a deliverer or a manager through the HMI 43. In addition, the plan correction unit 13 corrects the delivery plan generated by the delivery planning unit 11 based on the received change instruction for the delivery plan. Note that the delivery planning unit 11 and the plan correction unit 13 may be realized as a single function.

[0064] The storage unit 14 is realized by, for example, the memory 42. The storage unit 14 stores various information collected, used, or generated in the delivery management process according to the embodiment. For example, the storage unit 14 stores delivery request information (see FIG. 6) including delivery conditions such as the package, the shipper, the delivery destination, and the delivery time. For example, the storage unit 14 stores vehicle-related information such as vehicle information (see FIG. 7), area information (see FIG. 8), and driver information (see FIG. 9). For example, the storage unit 14 stores past delivery plan information and generated delivery plan information (see FIG. 10). Note that the past delivery plan information may be included in the change history information. For example, the storage unit 14 stores information related to the emotions of the deliverer, such as change reason information including a time stamp and deliverer-dependent information, modified attribute information, and emotion transition information. For example, the storage unit 14 stores environmental information indicating the surrounding environment and the environment inside and outside the vehicle.

[0065] In addition, some of the functions of the management device 10 in the embodiment may be realized outside the management device 10, such as a server device that is provided separately in the delivery management system 1 and communicatively connected to the management device 10 via the network N.

[0066] 5 is a diagram showing an example of a functional configuration of an environmental information collecting device 33 mounted on a vehicle 30 according to an embodiment. The environmental information collecting device 33 realizes functions as an acquiring unit 331 and an output unit 332 by causing a processor 41 to execute a program loaded in a memory 42.

[0067] The acquisition unit 331 collects environmental information indicating the environment inside and outside the vehicle during delivery, which is obtained in a predetermined manner from the in-vehicle sensor 31, the driver monitor camera 32, other ECUs, etc., via, for example, the communication I / F 46. The acquisition unit 331 may also collect environmental information indicating the environment inside and outside the vehicle during delivery input by the deliverer, for example, via the HMI 43. The acquisition unit 331 may also collect environmental information indicating the surrounding environment, such as the time of delivery, weather, and temperature.

[0068] The output unit 332 outputs the environmental information collected by the acquisition unit 331 to the management device 10 via the communication I / F 46, for example.

[0069] In addition, some of the functions of the environmental information collection device 33 in the embodiment may be realized outside the vehicle 30, such as a server device that is separately provided in the management device 10 or the delivery management system 1 and communicatively connected to the management device 10 via the network N.

[0070] Here, various types of information related to the delivery management process according to this embodiment will be described with reference to the drawings.

[0071] FIG. 6 is a diagram showing an example of delivery request information 501 according to an embodiment. The delivery request information 501 is information indicating at least one delivery destination and delivery time to which at least one package is delivered, and is information including delivery conditions such as the package, the shipper, the delivery destination, and the delivery time. In the example of FIG. 6, the delivery request information 501 includes items of delivery destination, delivery item, and delivery lot for each package. The delivery destination item includes information indicating the address and area of ​​the delivery destination. The delivery item item includes information indicating the type, size, capacity, number, and weight of the delivery item. The delivery lot item includes information indicating the delivery time.

[0072] Fig. 7 is a diagram showing an example of vehicle information 502 according to an embodiment. The vehicle information 502 is information about at least one vehicle 30 included in the delivery fleet 20, and is an example of vehicle-related information. In the example of Fig. 7, the vehicle information 502 includes items of area and vehicle type for each vehicle. The vehicle information 502 may also include an item of the load capacity of each vehicle 30.

[0073] Fig. 8 is a diagram showing an example of area information 503 according to the embodiment. The area information 503 is information indicating a part or all of a delivery area in which delivery is performed by the delivery fleet 20, and is an example of vehicle-related information. In the example of Fig. 8, the area information 503 is information indicating the location and division of each area.

[0074] FIG. 9 is a diagram showing an example of driver information 504 according to an embodiment. The driver information 504 is information on at least one delivery person who delivers using a vehicle 30 in the delivery fleet 20, and is an example of vehicle-related information. In the example of FIG. 9, the driver information 504 includes items of attributes, compatible vehicle models, and work information for each delivery person. The attribute items include gender and level information defined by proficiency and experience. For example, the level information can be set based on the range of each delivery person, such as proficiency, experience, speed related to loading and unloading of luggage, and weight that can be handled. Note that the gender attribute is not a required configuration, and may be information that is set, for example, when there is a customer request. The compatible vehicle model item is information indicating the vehicle model of the vehicle 30 that can be driven. The work information item is information indicating the work status of each delivery person, such as the number of consecutive working days.

[0075] FIG. 10 is a diagram showing an example of delivery plan information 505 according to an embodiment. The delivery plan information 505 is information indicating a delivery schedule including a route and delivery time of at least one delivery section in which a deliverer delivers at least one parcel by vehicle 30. In the example of FIG. 10, the delivery plan information 505 includes items of delivery lot, vehicle, delivery information, route, driver, and load (weight) for each delivery. The delivery lot item is information indicating the delivery time of each delivery. The vehicle item is information indicating the vehicle 30 used in each delivery. The delivery information item is information indicating the correspondence with the delivery request information of the parcel delivered in each delivery. The route item is information indicating the delivery route of each delivery. The driver item is information indicating the deliverer in charge of each delivery. The load (weight) item is information indicating the total amount of parcels loaded onto the vehicle 30 in each delivery.

[0076] In addition, in the delivery management system 1 according to the above-described embodiment, communication between the management device 10 and the delivery fleet 20 may be performed by wireless communication such as Wi-Fi (registered trademark), or by wired communication via a standard corresponding to Ethernet (registered trademark) such as a LAN (Local Area Network) cable or a dedicated connection cable.

[0077] In addition, in the delivery management system 1 according to the above embodiment, the transfer of various information according to the embodiment in the communication between the management device 10 and the delivery fleet 20 may be performed via a computer-readable storage medium or a portable external storage device. As the computer-readable storage medium, for example, a CD-ROM, a flexible disk (FD), a CD-R, a DVD (Digital Versatile Disk), etc. can be appropriately used. Furthermore, as the portable external storage device, a HDD, an SSD, a Flash memory, etc. can be appropriately used.

[0078] Furthermore, in the delivery management system 1 according to the embodiment described above, various information according to the embodiment may be transmitted from the management device 10 to the delivery fleet 20, such as when a delivery plan or a revised candidate route is displayed (see Figs. 12 and 13) or a change instruction is received on a mobile terminal used by a vehicle 30 or an operator. Meanwhile, in the delivery management system 1 according to the embodiment described above, some or all of the various information according to the embodiment may not be transmitted from the delivery fleet 20 to the management device 10, such as when environmental information is collected from a sensor separately connected to the management device 10 or from outside the delivery management system 1, or when environmental information is input to the management device 10 by a deliverer or manager.

[0079] Next, a process flow executed in the delivery management system 1 configured as above will be described. Fig. 11 is a flowchart showing an example of the flow of the delivery management process executed by the delivery management device according to the embodiment. Figs. 12 and 13 are diagrams showing examples of display screens 610, 620 displayed in the process of Fig. 11, respectively. The flow of Fig. 11 is executed at the timing when the manager creates a delivery plan, for example, the morning before delivery or the night before.

[0080] The delivery planning unit 11 reads out delivery request information and vehicle information from the storage unit 14, for example, and generates delivery plan information based on the delivery request information and the vehicle information (S101). The delivery planning unit 11 also presents the generated delivery plan information. At this time, if a route to be reviewed is extracted, the review presentation unit 12 further displays information indicating the extracted route to be reviewed (S102).

[0081] FIG. 12 illustrates an example of a case where delivery plan information is presented by displaying the display screen 610. On the display screen 610 in FIG. 12, the generated delivery plan information is presented as an item of delivery plan (current time). The item of delivery plan (current time) illustrates "route 1" to "route 4" as routes for each section of one delivery route of the generated delivery plan information. "Route 1" indicates the section where delivery is made to each delivery destination in the order of W→Z→A. "Route 2" indicates the section where delivery is made to each delivery destination in the order of A→B→C. "Route 3" indicates the section where delivery is made to each delivery destination in the order of C→D→E. "Route 4" indicates the section where delivery is made to each delivery destination in the order of E→F→G.

[0082] In addition, the display screen 610 of FIG. 12 includes the items "Past Modification", "Before Modification", "After Modification" and "Modifier" for each section of the route, that is, the display of change history information. The "Past Modification" item is information indicating whether a modification was made to the route of each section in the past. For a section with the "Past Modification" item set to "Yes", information corresponding to the items "Before Modification", "After Modification" and "Modifier" regarding past modifications of the delivery plan is displayed. For example, the display screen 610 of FIG. 12 indicates that the section of "Route 2" was modified by "Mr. A" in the past from "A→C→B" to "A→B→C". For example, the display screen 610 of FIG. 12 indicates that the section of "Route 3" was modified by "Mr. A" in the past from "B→D→E" to "C→D→E".

[0083] 12 also includes a display 613 of information indicating a route that is a candidate for review among one of the delivery routes in the generated delivery plan information. The information indicating the route that is a candidate for review may be displayed by highlighting the route as in the display 613, or may be realized by the presence or absence of display for the items "Past revision", "Before revision", "After revision" and "Reviser", or by the display content itself.

[0084] 12 also includes a "Change" button 615 and a "Do Not Change" button 617. The "Change" button 615 is a button that instructs the selection of the route candidate for review in order to be modified. The "Do Not Change" button 617 is a button that instructs the selection of the route candidate for review not to be selected, i.e., not to modify the delivery plan.

[0085] The plan correction unit 13 determines whether a route candidate for review has been selected (S103). For example, the plan correction unit 13 determines that a route candidate for review has been selected when the selection of the "Change" button 615 is detected based on the result of the operator's operation input to the HMI 43. For example, the plan correction unit 13 determines that the delivery plan will not be revised when the selection of either of the operation buttons 615, 617 is not detected for a predetermined period of time or longer based on the result of the operator's operation input to the HMI 43, or when the selection of the "Do not change" button 617 is detected.

[0086] When the review candidate route is selected (S103: Yes), the review presentation unit 12 presents information on the review candidate route based on the delivery plan information and the change history information (S104).

[0087] Fig. 13 illustrates a case where information on the selected review candidate route is presented by displaying the display screen 620. On the display screen 620 of Fig. 13, the generated delivery plan information is presented as an item of "current proposal".

[0088] The display screen 620 in Fig. 13 presents information about the deliverer of the target delivery plan. The information about the deliverer includes the name of the deliverer, the delivery area, work information, and information indicating the condition. The display screen 620 in Fig. 13 includes the display of an icon according to the degree of condition as information indicating the condition. Fig. 13 illustrates a case where the condition is "good" as an example.

[0089] The display screen 620 of FIG. 13 presents the past "Dispatch Plan", "Deliver's Feelings Due to Past Modification", "Attributes of the Modifier" and "Reason" items as change history information showing changes to past dispatch plans. The past "Dispatch Plan" item presents the routes of past dispatch plans including the route corresponding to the route "A→B→C" of the review candidate of the current dispatch plan. The "Deliver's Feelings Due to Past Modification" item is information showing the feelings of the deliverer after the past dispatch plan is modified (changed) or about the dispatch plan before and after the change. The display screen 620 of FIG. 13 includes the display of an icon according to the degree of the feelings of the deliverer as information showing the feelings of the deliverer. The "Attributes of the Modifier" item presents modification attribute information showing the attributes of the instruction subject who issued the change instruction in the past change. The "Reason" item presents change reason information including administrator-dependent information and deliverer-dependent information. The change reason information may be input by selection using a pull-down menu or the like, or may be arbitrarily entered by the operator. Fig. 13 shows an example of a case where the administrator-dependent information of "A1 operational efficiency (fast LV1)" and "A2 operational efficiency (fast LV2)" can be selected. Fig. 13 also shows an example of a case where the deliverer-dependent information of "B1 deliverer (avoiding U-turns and bottlenecks)", "B2 deliverer (avoiding congestion, avoiding accident risks)", and "B3 deliverer (restricting right turns, etc.)" can be selected.

[0090] A display screen 620 in Fig. 13 illustrates an example of environmental information indicating the surrounding environment for each delivery plan. Fig. 13 illustrates an example of a case where the time is presented as environmental information indicating the surrounding environment.

[0091] For example, the display screen 620 of FIG. 13 includes change history information for "past revision 1", "past revision 2" and "past revision 3" as information about the route "A→B→C" that is a candidate for review of the currently proposed delivery plan to be implemented in "winter 2023". The change history information for "past revision 1" illustrates a case where a revision is made in "winter 2022" by "Mr. A", an "administrator" with "experience (LV0)", for the administrator-dependent change reason of "operational efficiency (fast LV2)", and the delivery person's sentiment for the changed route "A→B→C" is "very bad". The change history information for "past revision 2" illustrates a case where a revision is made in "summer 2021" by "Mr. B", an "experience (LV5)", for the delivery person-dependent change reason of "B1 delivery person (U-turn, avoidance of bottlenecks)", and the delivery person's sentiment for the changed route "A→C→B" is "good". The change history information for "Past Revision 3" illustrates an example in which a revision was made in "Summer 2022" by "Mr. C," a "delivery person" with "Experience (LV2)," for an administrator-dependent change reason of "A1 Business Efficiency (Fast LV1)," and the delivery person's feelings about the revised route "C → B → A" are "bad." Note that, as illustrated as "Past Revision 3," the delivery person of the delivery plan or another delivery person of the delivery person may set an administrator-dependent change reason and make the revision as an operator.

[0092] In addition, the display screen 620 in Fig. 13 illustrates an example in which the information indicating the condition and the delivery person's emotion based on the past correction are displayed using the same type of icon, but this is not limited to this. Different types of icons may be used for each.

[0093] 13 also includes a "Change" button 625 and a "Do Not Change" button 627. The "Change" button 625 is a button for instructing a change to the delivery plan to modify the route of the selected section. The "Do Not Change" button 627 is a button for instructing not to modify the delivery plan for the selected section.

[0094] The plan correction unit 13 determines whether, for example, a change in the delivery plan has been instructed (S105). For example, based on the result of the operator's operation input to the HMI 43, when the selection of the "Change" button 625 is detected with any route selected as shown in the display 623, the plan correction unit 13 determines that a change in the delivery plan has been instructed. For example, based on the result of the operator's operation input to the HMI 43, when the selection of any of the operation buttons 625, 627 is not detected for a predetermined time or longer, or when the selection of the "Do not change" button 627 is detected, the plan correction unit 13 determines that the delivery plan will not be modified.

[0095] If a change to the delivery plan is instructed (S105: Yes), the plan correction unit 13 acquires the change contents together with the reason for the change and the information of the person who made the change, and changes the delivery plan information (S106). In addition, the plan correction unit 13 generates change history information based on the change contents, the reason for the change, and the information of the person who made the change, and records the generated change history information, for example, in the storage unit 14 (S107).

[0096] On the other hand, if a candidate route for review is not selected (S103: No), or if a change to the delivery plan is not instructed (S105: No), the flow in FIG. 11 proceeds to the process of S108. If a change to the delivery plan is not instructed (S105: No), the flow in FIG. 11 may return to the process of S103. In this case, the display screen 620 transitions to the display screen 610.

[0097] After that, the delivery plan unit 11 notifies the delivery person of the generated or modified delivery plan information (S108). In addition, the review presentation unit 12 generates information on the delivery person's emotions, such as emotion transition information regarding the delivery person's changed delivery route, in a predetermined manner, and updates the corresponding change history information (S109). After that, the flow of FIG. 11 ends.

[0098] Thus, in the delivery management system 1 according to the embodiment, the management device 10 is configured to generate a delivery plan and present the contents of past delivery plans before and after changes. Specifically, the management device 10 compares the generated delivery plan with past versions and identifies candidate routes for review by referring to change history information. With this configuration, it is possible to suppress operational errors such as operator oversights when correcting an automatically generated delivery plan, and to realize appropriate corrections.

[0099] In addition, in the delivery management system 1 according to the embodiment, the change history information includes deliverer-dependent information indicating at least the reasons for dependency on the deliverer, which are based on the emotions or preferences of the deliverer. This configuration makes it possible to revise the delivery plan based on the reasons for dependency on the deliverer, and to make revisions that the deliverer feels satisfied with.

[0100] In addition, in the delivery management system 1 according to the embodiment, the change history information includes modification attribute information indicating the attributes of the person who made the modification instruction, such as the name, veteran level, and type of deliverer and manager. With this configuration, the attributes of the person who made the modification previously can be compared with the operator himself (the person who made the modification this time), and it is possible to determine whether to adopt the modification and realize an appropriate modification.

[0101] In addition, in the delivery management system 1 according to the embodiment, the management device 10 is configured to further present information indicating the emotions of the deliverer after the change when presenting candidate routes for review. With this configuration, the operator can determine whether the past changes contributed to the change in the emotions of the deliverer and then make a revision that the deliverer feels satisfied with.

[0102] In each of the above-mentioned embodiments, "determining whether it is A" may mean determining that it is A, determining that it is not A, or determining whether it is A or not.

[0103] Each program executed by each device of the delivery management system 1 in each of the above-mentioned embodiments is provided by being recorded on a computer-readable storage medium such as a CD-ROM, FD, CD-R, DVD, etc. in a file in an installable or executable format.

[0104] Also, each program executed by each device of the delivery management system 1 according to each of the above-mentioned embodiments may be stored on a computer connected to a network such as the Internet and provided by downloading via the network. Also, each program executed by each device of the delivery management system 1 according to each of the above-mentioned embodiments may be provided or distributed via a network such as the Internet.

[0105] Furthermore, each program executed by each device of the delivery management system 1 according to each embodiment described above may be provided by being pre-installed in a ROM or the like.

[0106] In addition, the programs executed by each device of the delivery management system 1 in each of the above-mentioned embodiments have a modular structure including each of the above-mentioned functional units, and in terms of actual hardware, a processor 41 such as a CPU reads out and executes the program from a memory 42 such as a ROM or HDD, thereby loading each of the above-mentioned functional units into the RAM of the memory 42, and each of the above-mentioned functional units is generated in the RAM of the memory 42.

[0107] According to at least one of the embodiments described above, an automatically generated delivery plan can be appropriately corrected.

[0108] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents described in the claims, as well as in the scope and spirit of the invention.

[0109] (Additional Note) The above description of the embodiments discloses the following techniques. (1) delivery request information indicating at least one delivery destination and delivery time for at least one package; Vehicle-related information indicating information regarding a vehicle used by a deliverer to deliver the at least one package to the at least one delivery destination, A planning unit that presents delivery plan information indicating a delivery plan including a route of at least one delivery section and the delivery time in which the deliverer delivers the at least one package by the vehicle; A presentation unit that presents a route to be reviewed among the routes of the at least one delivery section included in the generated delivery plan based on the generated delivery plan information and change history information indicating a history of past changes to the delivery plan; A modification unit that modifies the delivery plan based on a received change instruction for the delivery plan. Delivery management device. (2) The presentation unit presents, as the review candidate route, a route that matches a route before or after the revision with the history of the past revision among the routes of at least one delivery section included in the delivery plan. A delivery management device as described in (1) above. (3) The change history information includes at least deliverer-dependent information indicating the reason for the change that is dependent on the deliverer in the past change. A delivery management device as described in (1) above. (4) The delivery company dependent information is information indicating the reason for the past change of at least one of distance priority, time priority, turning restriction, bottleneck restriction, congestion restriction, accident risk restriction, and right turn restriction. The delivery management device according to (3) above. (5) The change history information includes at least modification attribute information indicating attributes of an instruction subject that issued the change instruction in the past change. A delivery management device according to any one of (1) to (4) above. (6) The modification attribute information is at least one of information indicating the subject of instruction of the past modification, including information indicating whether the subject is a human being or a computer that performs inference using a machine learning model, information indicating whether the subject is an expert, and information indicating whether the subject is the delivery person or an administrator that manages the delivery. The delivery management device according to (5) above. (7) The presentation unit presents information regarding the delivery person's feelings regarding the delivery plan in the past change together with the review candidate route. A delivery management device according to any one of (1) to (6) above. (8) The presentation unit estimates a current condition of the delivery person based on work information indicating a work situation of the delivery person, and presents information indicating the estimated condition together with the review candidate route. A delivery management device according to any one of (1) to (7) above. (9) The presentation unit presents information indicating at least one of a time period, a weather, and a temperature when the past change was made together with the review candidate route. A delivery management device according to any one of (1) to (8) above. (10) a storage unit that stores the delivery request information, the vehicle-related information, the delivery plan information, and the change history information; A reception unit that receives the change instruction for the delivery plan; A display unit that displays at least the delivery plan information and the review candidate route. A delivery management device according to any one of (1) to (9) above. (11) delivery request information indicating at least one delivery destination and delivery time for at least one package; Vehicle-related information indicating information regarding a vehicle used by a deliverer to deliver the at least one package to the at least one delivery destination, Presenting delivery plan information indicating a delivery plan including a route of at least one delivery section and the delivery time along which the deliverer delivers the at least one package by the vehicle; Presenting a route to be reviewed among the routes of the at least one delivery section included in the generated delivery plan based on the generated delivery plan information and change history information indicating a history of past changes to the delivery plan; and modifying the delivery plan based on the received change instruction for the delivery plan. Delivery management method. (12) A program for causing a computer to execute the information processing method described in (11) above. (13) A storage medium (Computer Program Product) having recorded thereon the program described in (12) above, which is executed by a computer. [Explanation of symbols]

[0110] 1. Delivery management system 10 Management device 11 Delivery Planning Department 12 Review Presentation Section 13. Plan Revision Section 14 Storage section 20 Delivery Fleet 30 Vehicles 31 In-vehicle sensors 32 Driver monitor camera 33 Environmental information collection device 331 Acquisition Department 332 Output section N Network

Claims

1. delivery request information indicating at least one delivery destination and delivery time for at least one package; Vehicle-related information indicating information regarding a vehicle used by a deliverer to deliver the at least one package to the at least one delivery destination, A planning unit that presents delivery plan information indicating a delivery plan including a route of at least one delivery section and the delivery time in which the deliverer delivers the at least one package by the vehicle; A presentation unit that presents a route to be reviewed among the routes of the at least one delivery section included in the generated delivery plan based on the generated delivery plan information and change history information indicating a history of past changes to the delivery plan; A modification unit that modifies the delivery plan based on a received change instruction for the delivery plan. Delivery management device.

2. The presentation unit presents, as the review candidate route, a route that matches a route before or after the revision with the history of the past revision among the routes of at least one delivery section included in the delivery plan. The delivery management device according to claim 1 .

3. The change history information includes at least deliverer-dependent information indicating the reason for the change that is dependent on the deliverer in the past change. The delivery management device according to claim 1 .

4. The delivery company dependent information is information indicating the reason for the past change of at least one of distance priority, time priority, turning restriction, bottleneck restriction, congestion restriction, accident risk restriction, and right turn restriction. The delivery management device according to claim 3.

5. The change history information includes at least modification attribute information indicating attributes of an instruction subject that issued the change instruction in the past change. The delivery management device according to claim 1 .

6. The modification attribute information is at least one of information indicating the subject of instruction of the past change, including information indicating whether the subject is a human or a computer that performs inference using a machine learning model, information indicating whether the subject is an expert, and information indicating whether the subject is the delivery person or an administrator that manages the delivery. The delivery management device according to claim 5 .

7. The presentation unit presents information regarding the delivery person's feelings regarding the delivery plan in the past change together with the review candidate route. The delivery management device according to any one of claims 1 to 6.

8. The presentation unit estimates a current condition of the delivery person based on work information indicating a work situation of the delivery person, and presents information indicating the estimated condition together with the review candidate route. The delivery management device according to any one of claims 1 to 6.

9. The presentation unit presents information indicating at least one of a time period, a weather, and a temperature when the past change was made together with the review candidate route. The delivery management device according to any one of claims 1 to 6.

10. a storage unit that stores the delivery request information, the vehicle-related information, the delivery plan information, and the change history information; A reception unit that receives the change instruction for the delivery plan; A display unit that displays at least the delivery plan information and the review candidate route. The delivery management device according to any one of claims 1 to 6.

11. delivery request information indicating at least one delivery destination and delivery time for at least one package; Vehicle-related information indicating information regarding a vehicle used by a deliverer to deliver the at least one package to the at least one delivery destination, Presenting delivery plan information indicating a delivery plan including a route of at least one delivery section and the delivery time along which the deliverer delivers the at least one package by the vehicle; Presenting a route to be reviewed among the routes of the at least one delivery section included in the generated delivery plan based on the generated delivery plan information and change history information indicating a history of past changes to the delivery plan; and modifying the delivery plan based on the received change instruction for the delivery plan. Delivery management method.

Images