Delivery area management method and delivery area management device

Abstract

Correct the automatically generated delivery plan as needed. [Solution] The delivery area management method according to this disclosure includes generating delivery plan information that includes a delivery plan in which a delivery person delivers at least one package by vehicle to at least one delivery area, based on delivery request information that indicates at least one delivery destination and delivery time for delivering at least one package, and vehicle-related information that indicates information about a vehicle used by a delivery person to deliver at least one package to at least one delivery destination; presenting information about a candidate delivery area for revision among the at least one delivery area included in the generated delivery plan, based on the generated delivery plan information and change history information that indicates a history of changes to past delivery plans; and modifying the delivery plan based on a change instruction for a received delivery plan.

Description

Technical Field

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

Background Art

[0002] Conventionally, a technique for optimizing and automatically generating a delivery plan such as a delivery route and order for a vehicle that loads one or more packages and delivers them to one or more delivery destinations is known.

[0003] For example, in Patent Document 1, a delivery execution area is specified based on a centralized delivery center and each specified delivery location candidate, a delivery route passing through all the delivery location candidates within the specified delivery execution area is searched, and based on the predicted delivery time and the scheduled delivery operation time of the searched delivery route, a delivery location and a delivery execution area are determined, and a delivery map is created in which the delivery route and the delivery location are displayed in the delivery execution area so as to be recognizable, thereby creating a delivery map whose size is automatically adjusted such that unnecessary areas are excluded as much as possible and the required areas are displayed as large as possible. The technique is disclosed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, the automated system sometimes generated delivery plans that were unsatisfactory to the operators (managers) or did not align with their sensibilities. In such cases, operators had to manually modify the automatically generated delivery plans. Furthermore, even when operators modified the automatically generated delivery plans, the modified plans were still sometimes inappropriate, such as failing to gain emotional understanding from the delivery personnel or causing them stress.

[0006] The problem this disclosure aims to solve is to appropriately modify automatically generated delivery plans. [Means for solving the problem]

[0007] The delivery area management method relating to this disclosure includes generating delivery plan information that includes a delivery plan in which the delivery person delivers the at least one package using the vehicle, based on delivery request information indicating at least one delivery destination and delivery time for delivering at least one package, and vehicle-related information indicating information about a vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination; presenting information about a candidate delivery area for revision among the at least one delivery area included in the generated delivery plan, based on the generated delivery plan information and change history information indicating a history of changes to past delivery plans; and modifying the delivery plan based on a change instruction received for the delivery plan. [Effects of the Invention]

[0008] According to this disclosure, automatically generated delivery plans can be appropriately modified. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows an example of the configuration of a delivery area management system according to this embodiment. [Figure 2]Figure 2 shows an example of the hardware configuration of each device in the delivery area management system according to the embodiment. [Figure 3] Figure 3 shows an example of the functional configuration of the management device according to this embodiment. [Figure 4] Figure 4 shows an example of delivery request information according to the present invention. [Figure 5] Figure 5 shows an example of vehicle information according to the present invention. [Figure 6] Figure 6 shows an example of area information according to the embodiment. [Figure 7] Figure 7 shows an example of driver information according to the embodiment. [Figure 8] Figure 8 shows an example of delivery plan information including delivery area information according to the embodiment. [Figure 9] Figure 9 is a flowchart showing an example of the flow of the delivery area management process performed by the management device according to the embodiment. [Figure 10] Figure 10 shows an example of the display in the process shown in Figure 9. [Figure 11] Figure 11 shows an example of the display in the process shown in Figure 9. [Figure 12] Figure 12 shows an example of the display in the process shown in Figure 9. [Figure 13] Figure 13 shows an example of the display in the process shown in Figure 9. [Figure 14] Figure 14 shows an example of the display in the delivery area management process related to the first application example. [Figure 15] Figure 15 shows an example of the display in the delivery area management process related to the second application example. [Modes for carrying out the invention]

[0010] The embodiments of the delivery area management device, delivery area management system, delivery area management method, program, and storage medium related to this disclosure will be described below with reference to the drawings.

[0011] In the description of the present disclosure, for components having the same or substantially the same functions as those described above with respect to the previously presented figures, the same reference numerals may be used, and the description may be omitted as appropriate. Also, even when representing the same or substantially the same part, there are cases where the dimensions and ratios are represented differently in the drawings. Further, for example, from the viewpoint of ensuring the visibility of the drawings, only the main components are labeled with reference numerals in the description of each drawing, and there are cases where components having the same or substantially the same functions as those described above in the previously presented figures are not labeled with reference numerals.

[0012] Hereinafter, a case where the technology according to the present disclosure is applied, for example, to the delivery of various kinds of goods such as LP (Liquefied Petroleum) gas and home delivery items, will be described as an example.

[0013] Note that 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 item such as goods or materials from at least one business base such as a business office or a warehouse to at least one delivery destination. Also, the technology according to the present disclosure can be applied not only to goods but also to the transportation of people. For example, the technology according to the present disclosure can be applied to a business support service or a patrol support service, a fleet management service, or a vehicle allocation support service that supports route sales, maintenance, or vehicle allocation of at least one visitor who transports at least one visitor from a business base such as a business office to at least one visit destination such as a customer's business base, home, or a place designated by the customer. In this case, the "delivery" according to the present disclosure may be read as "patrol", "visit", or "vehicle allocation". Further, for example, the technology according to the present disclosure can be applied to a pick-up and drop-off support service that supports a service involving pick-up and drop-off such as home care day care or after-school care that picks up and drops off at least one user between at least one pick-up and drop-off destination such as the user's home and a business office such as a facility or a school. In this case, the "delivery" according to the present disclosure may be read as "pick-up and drop-off".

[0014] Conventionally, there has been known a technique for optimizing and calculating a delivery plan such as a delivery route and order for a vehicle that loads one or more pieces of cargo and delivers them to one or more delivery destinations.

[0015] For example, in Patent Document 1, a delivery execution area is specified based on a centralized delivery center and each candidate delivery location that has been specified, a delivery route passing through all candidate delivery locations within the specified delivery execution area is searched, and based on the predicted delivery time and the scheduled delivery operation time of the searched delivery route, a delivery location and a delivery execution area are determined, and a delivery map is created in which the delivery route and the delivery location are displayed in the delivery execution area in a recognizable manner, so as to create a delivery map whose size is automatically adjusted such that unnecessary areas are excluded as much as possible and necessary areas are displayed as large as possible.

[0016] However, there have been cases where a delivery plan that is not convincing to the operator (administrator) or does not match the operator's sense is automatically generated. In this case, the operator has had to manually correct the automatically generated delivery plan.

[0017] For example, there has been a technique for reducing the workload related to correcting a delivery plan by preparing in advance change target parameters corresponding to improvement items and generating a delivery plan in which the change target parameters are changed in response to receiving improvement items for the presented delivery plan. However, while the working time is shortened, there is a problem that work mistakes can occur due to oversight or lack of skill.

[0018] Also, for example, there has been a technique for formulating a delivery plan by a computer even when sufficient performance data cannot be obtained in a case where there is no experienced planner, by performing machine learning using an instruction from a user for the presented delivery plan as teacher data so as to output an appropriate delivery plan that satisfies the delivery conditions. However, there is a problem that a delivery plan formulated by a computer can be a delivery plan that is not convincing to the operator or does not match the sense.

[0019] Furthermore, even when operators modified automatically generated delivery plans, the modified plans were still sometimes inappropriate, such as failing to gain emotional understanding from the delivery drivers or causing them stress.

[0020] For example, even if an operator modifies an automatically generated delivery plan, if the operator's perspective is not taken into account, such as "I want to be in charge of deliveries to customers with whom I have built a trusting relationship," "I prefer to deliver to areas where I have a high level of expertise in geography and other aspects of delivery," "I want to avoid congestion even if it means taking a longer route," "I don't want to make U-turns, even if it takes longer," "That road is too narrow for me," or "This order and route is better because it's faster even though it's narrow," the plan may not meet the operator's wishes, or in other words, the operator may not feel satisfied.

[0021] Furthermore, delivery plans were sometimes temporarily changed due to unforeseen circumstances, such as emergency deliveries of LP gas, or for special reasons, such as the need to consider the location of charging facilities when using electric vehicles for delivery. In such cases, if the revised delivery plan was followed even after the original reason had disappeared, delivery personnel may have difficulty feeling satisfied.

[0022] Therefore, this disclosure aims to appropriately modify automatically generated delivery plans. More specifically, this disclosure aims to suppress errors by the person modifying the automatically generated delivery plan. Here, the person modifying the plan is, for example, a delivery person who makes deliveries by vehicle or a manager who manages deliveries. Furthermore, errors by work mean, for example, oversights or omissions in modifying the delivery plan, or modifications that are not necessarily the optimal improvement. Furthermore, modifications that are not necessarily the optimal improvement mean modifications that are not the optimal improvement not only in terms of economic rationality, but also due to the emotional aspects of the delivery person, the lack of experience of the person modifying the plan, or the lack of skills of the person modifying the plan.

[0023] Figure 1 shows an example of the configuration of a delivery area management system 1 according to an embodiment. As shown in Figure 1, the delivery area management system 1 includes a management device 10 and a delivery fleet 20. The management device 10 and the delivery fleet 20 are connected in a way that allows communication, for example, via a network N. As the network N, a telecommunications line such as the Internet can be used.

[0024] The management device 10 is a device that manages the entire delivery area management system 1. The management device 10 is configured to realize the delivery area management method according to the embodiment by executing the delivery area management process according to the embodiment. Here, the management device 10 according to the embodiment is an example of a delivery area management device.

[0025] As an example, the management device 10 formulates a delivery plan, which is a delivery plan in which a delivery person delivers at least one package to at least one delivery destination using a vehicle 30, and presents it to operators such as delivery persons and managers.

[0026] This delivery plan defines the delivery area and the delivery route (delivery path) that passes through at least one destination within that area. In addition to at least one delivery destination, the delivery route of the delivery plan may include points where fuel or electricity is supplied to the vehicle 30, and loading / unloading points where at least one shipment to be delivered is loaded or unloaded. Note that loading / unloading points are not limited to business bases such as offices or warehouses, but may also be places where goods are exchanged between vehicles 30, or may be filling facilities where LP gas is filled into gas cylinders (goods).

[0027] For example, the management device 10 identifies candidate delivery areas for revision from at least one delivery area specified in the delivery plan and presents them to operators such as delivery drivers and managers. For example, the management device 10 identifies a delivery area as a candidate for revision from at least one delivery area indicated in the delivery plan, where part or all of the delivery area or delivery route within the delivery area matches the history of past changes. For example, the management device 10 receives instructions to change the delivery plan from operators (modifiers) such as delivery drivers and managers, and modifies the delivery plan based on the change instructions.

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

[0029] Note that Figure 1 illustrates three vehicles 30-1, 30-2, and 30-3, but is not limited to these. In this disclosure, there may be one or two vehicles 30, or four or more vehicles 30.

[0030] In this disclosure, the vehicle 30 may be, for example, various vehicles that utilize an internal combustion engine, or various vehicles that utilize batteries, such as electric vehicles or hybrid vehicles. In addition, bicycles, motorcycles, three-wheeled or more passenger vehicles, other automobiles such as trucks, and kick scooters can be used as appropriate as the vehicle 30.

[0031] Vehicle 30 is equipped with various sensors (onboard sensors) used for driving and driving assistance. Driving assistance includes, for example, assistance from advanced driving assistance systems (ADAS) such as automatic emergency braking (AEB) processing and sudden acceleration prevention processing. Onboard sensors include, for example, at least one of the following: sonar (Sound Navigation And Ranging), radar, LiDAR (Light Detection And Ranging), all-around camera, steering angle sensor, wheel speed sensor, brake sensor, accelerator sensor, acceleration sensor, gyroscope sensor, GPS (Global Positioning System) sensor, and other Global Navigation Satellite System (GNSS) sensors. Vehicle 30 may also have a camera installed inside the vehicle as an onboard sensor to acquire images of the delivery person, which is used for a driver monitoring function that monitors the driver's (delivery person's) driving posture, gaze, face direction, and eyelid opening / closing state. Furthermore, the camera used as an in-vehicle sensor may be a camera built into the vehicle 30, or it may be a camera from a drive recorder that is retrofitted to the vehicle 30.

[0032] Furthermore, the vehicle 30 may be equipped with a processing device (not shown) to collect environmental information indicating the interior and exterior environment of the vehicle 30. This processing device is connected to other information processing devices and on-board sensors of the vehicle 30 via an on-board network including, for example, CAN (Controller Area Network) or Ethernet (registered trademark). The environmental information may be, for example, an image of the vehicle 30's surroundings obtained by an all-around camera (on-board sensor), or the results of image analysis thereof. The environmental information may also be, for example, images, videos, or audio of delivery persons obtained by a camera installed inside the vehicle, or the results of analysis thereof. The environmental information may also be, for example, information indicating the driving status of the vehicle 30 obtained by a digital tachograph (digital driving recorder) that records the vehicle 30's speed, driving time, and driving distance.

[0033] Environmental information may also include, for example, information indicating the surrounding environment of vehicle 30, such as the time of delivery of vehicle 30, weather, temperature, and atmospheric pressure. Environmental information may also include, for example, images of the surroundings of vehicle 30, or the results of image analysis thereof, collected as information indicating the weather, such as sunny, cloudy, rainy, snowy, or a combination thereof.

[0034] The environmental information may include, for example, information about the emotions of the driver while driving, i.e., the delivery person in the vehicle 30 making deliveries. For example, the information about the delivery person's emotions may indicate the delivery person's emotions regarding the revised (changed) delivery plan. For another example, the information about the delivery person's emotions may indicate the change in the delivery person's emotions (emotional transition) regarding the delivery plan before and after the revision (change). This information about the delivery person's emotions may be information used to evaluate the stress and emotions felt by the delivery person, such as the delivery person's facial expressions, 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 it may be information indicating the degree of emotion estimated by the vehicle 30 or the management device 10 using this information. The information indicating the degree of emotion may be information indicating multiple emotional levels, such as "good," "average," and "bad." For example, the more eye movements and blinks the delivery person makes, the lower the emotional level estimated. For example, if gestures such as scratching the head or face are detected, a low emotional level is estimated. For example, a higher heart rate is estimated to indicate a lower emotional level. Similarly, larger changes in driving conditions, such as vehicle speed and braking frequency, are estimated to indicate a lower emotional level.

[0035] Furthermore, environmental information may be collected not only by the vehicle 30, but also by the management device 10. Environmental information may also be collected from outside the vehicle 30, for example, by the management device 10 or the vehicle 30. For example, environmental information may be collected from various sensors separately provided in the delivery area management system 1, from outside the delivery area management system 1 via the internet, from the management device 10, the vehicle 30's HMI (Human Machine Interface) configured to accept input of environmental information from delivery personnel or managers, or from mobile devices such as smartphones or smartwatches used by delivery personnel or managers, or from health devices such as heart rate sensors worn by delivery personnel. Moreover, environmental information may not be limited to input using the management device 10, the vehicle 30, the delivery personnel's or manager's mobile devices, or the vehicle 30's HMI; it may also be collected based on the results of reading (scanning) questionnaire information completed by the delivery personnel or manager.

[0036] Figure 2 shows an example of the hardware configuration of each device in the delivery area management system 1 according to this embodiment.

[0037] Each device in the delivery area management system 1 (for example, the management device 10 or the processing unit for the vehicle 30) has a processor 41, memory 42, HMI 43, and communication I / F (interface) 46, as shown in Figure 2. The HMI 43 has a display 44 and an input I / F 45.

[0038] The processor 41, memory 42, display 44, input I / F 45, and communication I / F 46 are interconnected by a bus 49, etc., and the hardware configuration is that of a normal computer. The processing unit of the vehicle 30 may be, for example, an ECU (Electronic Control Unit) or OBU (On Board Unit) computer located inside the vehicle 30, or an external computer installed near the dashboard of the vehicle 30, or it may also serve as the vehicle 30's car navigation system.

[0039] The processor 41 is a processing unit that controls the entire system within each device of the delivery area management system 1. The processor 41 performs the various processes described later by loading programs stored in, for example, the ROM (Read Only Memory) of the memory 42 into the RAM (Random Access Memory) and executing them.

[0040] In this embodiment, the processor 41 can be any of the following types of processors, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), or a dedicated arithmetic circuit implemented using an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

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

[0042] The display 44 is an example of an output interface for the HMI 43. The display 44 is provided so that it is visible to the driver (delivery person), for example, by being placed on the dashboard or console of the vehicle 30. The display 44 is configured to output 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 also be configured as a touch panel display. The display 44 may also be part of a car navigation system installed in the vehicle 30. The display 44 may also be a projection-type display interface such as a HUD (Head Up Display) that projects images (virtual images) onto a display area provided in front of the driver, for example, on the windshield or dashboard (console). The HMI 43 may also include other output interfaces such as a speaker configured to output notification sounds, warning sounds, and voice. Here, the display 44 according to this embodiment is an example of a display unit.

[0043] The input I / F 45 is implemented, for example, as a touch panel of the display 44, which is a touch panel display. The input I / F 45 may also include other input I / Fs such as buttons, dials, switches, and microphones. These input I / F 45s are located, for example, on the dashboard, instrument panel, steering wheel, or console of the vehicle 30. Here, the input I / F 45 according to this embodiment is an example of a reception unit.

[0044] Furthermore, as the HMI43, an operating terminal capable of transmitting or receiving signals to the vehicle 30 from outside the vehicle 30 may be used, such as a tablet device, smartphone, smartwatch, remote controller, or electronic key.

[0045] Communication I / F46 is an interface for sending and receiving data. For example, communication circuits for wired communication, communication circuits for wireless communication, and combinations thereof can be used as appropriate for communication I / F46. For wireless communication circuits, communication circuits compatible with various standards such as 3G, 4G, Wi-Fi®, and Bluetooth® can be used as appropriate. Also, for example, in the processing unit of the vehicle 30, communication I / F46 may send and receive information with in-vehicle sensors and other ECUs via an in-vehicle network.

[0046] Figure 3 shows an example of the functional configuration of the management device 10 according to the embodiment. The management device 10 realizes the functions of a delivery planning unit 11, a review and presentation unit 12, a plan modification unit 13, and a storage unit 14 by executing a program loaded into the memory 42 with the processor 41. Here, the delivery planning unit 11, the review and presentation unit 12, and the plan modification unit 13 according to the embodiment are examples of a planning unit, a presentation unit, and a modification unit, respectively.

[0047] The delivery planning unit 11 generates a delivery plan, including a delivery area, based on the delivery request information and vehicle-related information. Here, the delivery request information is information indicating at least one delivery destination and delivery time for at least one package (see Figure 4). The vehicle-related information is information about the vehicles 30 used by the delivery person to deliver at least one package to at least one delivery destination (see Figures 5 to 7). The delivery plan is information that, for each of the at least one vehicles 30, includes delivery area information indicating the geographical range in which the delivery person will deliver at least one package by the vehicle 30, and information indicating the delivery route to at least one destination, including at least one delivery destination within that delivery area (see Figure 8). The delivery plan may also include information indicating the delivery time (arrival time and / or departure time) to each delivery destination. Details of each piece of information will be described later.

[0048] As an example, the delivery planning unit 11 determines the delivery area based on the delivery request information and vehicle information. Typically, the delivery area is determined based on the number of vehicles and delivery efficiency. The delivery area is also linked to a vehicle 30 (driver). The delivery planning unit 11 then determines a delivery route that visits at least one destination, including at least one delivery destination within the determined delivery area.

[0049] As an example, the delivery planning unit 11 generates a delivery plan that satisfies the conditions defined by the delivery request information and vehicle-related information, using a combinatorial optimization algorithm such as the traveling salesman problem. The delivery plan generation algorithm is arbitrarily applicable, and other combinatorial optimization algorithms may be used.

[0050] Furthermore, the delivery planning unit 11 presents the generated delivery plan information (see Figures 8 and 10) to operators such as delivery drivers and managers by displaying it on, for example, the display 44.

[0051] The revision suggestion unit 12 identifies a candidate delivery area for revision with respect to at least one delivery area of ​​the delivery plan generated by the delivery planning unit 11. Here, a candidate delivery area for revision is a delivery area from at least one delivery area of ​​the delivery plan that is targeted for suggestion to the operator for formulating an optimal delivery plan or for making modifications to improve the delivery plan.

[0052] For example, the identification of delivery areas for review is based on delivery plan information generated by the delivery planning unit 11 and change history information showing the history of past changes to the delivery plan. For instance, a delivery area for review is one of at least one delivery areas included in the delivery plan in which some or all of the delivery plan information and vehicle-related information, including the delivery area, match between the delivery plan before and after past changes.

[0053] Here, change history information refers to information regarding deliveries that followed past delivery plans, indicating whether or not there were any changes to the automatically generated delivery plan, the content of the changes, the reason for the changes, and the person who made the changes (the person who made the modifications).

[0054] The change history information may include both the pre- and post-change delivery plans, or it may include either delivery plan and the changes made. Furthermore, the change history information may include information that underpinned the changes, such as environmental information or work information.

[0055] For example, the change history information may include information indicating whether or not the delivery area has been changed in relation to the previously suggested delivery area for revision. In this case, for example, the delivery area for revision may be at least one delivery area included in the delivery plan, where some or all of the delivery plan information and vehicle-related information, including the delivery area, matches between the delivery plan before and after the previous change, and where the delivery area has been changed in relation to the previously suggested delivery area for revision.

[0056] For example, change history information may include delivery-dependent information that indicates the reasons for changes that depended on the delivery person in past changes.

[0057] For example, delivery person dependency information may also include information indicating the relationship between the delivery person and the customer (delivery destination). Specifically, delivery person dependency information may also include information indicating at least one reason for a past change, such as "the delivery person and the delivery destination have a long (or short) relationship," "the delivery destination holds (or does not hold) the key to the delivery location," "the delivery destination has a high (or low) rating of the delivery person," and "there is a preference for a fuel supply location," such as wanting to use a gas station (destination) that the delivery person has a relationship with.

[0058] Furthermore, for example, the delivery person-dependent information may also include information indicating the delivery person's geographical familiarity with each area. This familiarity information may include evaluation values ​​entered by the delivery person or manager, the number of years of experience delivering to the target area, or the total distance traveled and delivery time for deliveries in the target area.

[0059] Furthermore, the delivery person-dependent information may also include information indicating the reason for at least one past change from among, for example, prioritizing distance, prioritizing time, avoiding U-turns, avoiding narrow roads, avoiding congestion, reducing accident risk, and avoiding right turns. Here, "avoidance" means, for example, prioritizing avoidance. Also, "prioritization" may be treated as an absolute condition or as a condition with relatively high priority. In other words, the delivery person-dependent information may include, for example, a delivery plan that aligns with the delivery person's wishes, such as "I want to avoid congestion even if it means taking a longer route," "It takes longer, but I don't want to make a U-turn," "That road is too narrow for me," or "This order / route is good because it's faster even though it's narrow," or a delivery plan that the delivery person is likely to find acceptable, or information indicating the reason for changing to that delivery plan.

[0060] For example, change history information may include provisional reason information indicating the provisional reasons for past changes. In this case, for instance, a delivery area for review may be at least one delivery area included in the delivery plan, where some or all of the delivery plan information and vehicle-related information, including the delivery area, match between the delivery plan before and after the past change, and where the reason for the past change was a reason other than the provisional reason for the change. In other words, a delivery area for review may be identified based on provisional reason information, except in cases where it was changed for a provisional reason.

[0061] For example, provisional reason information may include information indicating that the change was due to an emergency response, such as dealing with an LPG gas shortage.

[0062] For example, the provisional reason information may include information indicating that vehicle 30 was an electric vehicle (EV) that was charged at a charging facility within the delivery area before, during, or after delivery, such as a reduction in the delivery area due to measures to prevent running out of power, or the setting of a delivery area that takes into account stops at charging facilities. Similarly, the provisional reason information may also include information indicating that the vehicle had a short driving range, or information indicating that the vehicle was a vehicle with few fuel supply locations, such as a vehicle that uses LPG or hydrogen as fuel.

[0063] For example, change history information may include administrator-dependent information that indicates the reasons for administrator-dependent changes in past changes. For example, administrator-dependent information may include information indicating the speed level, which specifies the shortness of delivery time from the perspective of operational efficiency. For example, administrator-dependent information may indicate the degree of delivery speed requested (set) by the administrator, such as specifying "Fast LV2" for highly skilled veteran delivery drivers and "Fast LV1," which indicates a lower speed requirement for less skilled delivery drivers.

[0064] For example, change history information may include modification attribute information that indicates the attributes of the entity that issued the change instruction in the past. For instance, the modification attribute information may indicate the entity that issued the change instruction in the past, at least one of the following: information indicating whether it was a human or a computer that performs inference using a machine learning model; information indicating whether it was a veteran or not; and information indicating whether the operator who made the modification (modifier) ​​was a delivery person or a manager who oversees deliveries.

[0065] Furthermore, the computer acting as the instruction provider is not limited to one that uses a machine learning model to perform inference assuming known causal relationships and causal directions; it may also use a machine learning model to perform exploration to estimate relationships when causal relationships are unknown, or a combination of both. Examples of machine learning models include CNNs (Convolutional Neural Networks), but other machine learning models may also be used. Alternatively, a computational model that defines predetermined formulas or conditions may be used instead of a machine learning model.

[0066] Furthermore, the revision presentation unit 12 presents the identified candidate delivery areas to operators such as delivery drivers and managers by displaying them, for example, on the display 44. The revision presentation unit 12 may also present the candidate delivery areas on the display screen that presents the delivery plan information (see Figure 10), or it may present a notification that there are candidate delivery areas on the display screen that presents the delivery plan information (see Figure 10) and also present the candidate delivery areas on another display screen (see Figure 11).

[0067] Furthermore, the review presentation unit 12 may, for example, display 44 to provide notification of the reasons for past changes. This notification of the reasons for changes may be included in the display screen that presents delivery plan information (see Figure 10) or the display screen that presents the delivery area of ​​the revision candidates (see Figure 11), or it may be presented as a pop-up screen for these display screens or as another display screen accessed from these display screens.

[0068] Furthermore, the notification of the reason for the change may also include environmental information such as information indicating the interior and exterior environment of the vehicle 30 and the surrounding environment at the time of past changes, and information regarding the delivery person's feelings. For this reason, if the delivery area is changed, the review presentation unit 12 may generate information regarding the delivery person's feelings about the changed delivery route in a predetermined manner and update the corresponding change history information in the storage unit 14. Here, the predetermined manner means, for example, a method for collecting or acquiring environmental information indicating the interior and exterior environment of the vehicle during delivery. Environmental information regarding the delivery person's feelings may be treated as delivery person-dependent information. The environmental information presented is not limited to the examples described above, and may also include information regarding other factors that affect delivery in accordance with the delivery plan.

[0069] Furthermore, the notification of the reason for the change may also include information indicating the delivery person's condition at the time of past changes. For this reason, the review presentation unit 12 may estimate information indicating the delivery person's current condition based on work information (see Figure 7) that shows the delivery person's work status. Here, the information indicating the delivery person's current condition may be information indicating the number of consecutive working days registered as work information, information entered by the delivery person or others via HMI 43, or information indicating the degree of condition estimated based on this information. The information indicating the degree of condition may be information indicating multiple condition levels, such as "good," "average," and "bad." For example, the more consecutive working days there are, the lower the estimated condition level. Note that the information indicating the delivery person's condition may be treated as delivery person-dependent information.

[0070] Furthermore, depending on the pre-configured settings, or if no candidate delivery areas for revision are identified, the revision suggestion unit 12 does not need to suggest candidate delivery areas for revision. In addition, the revision suggestion unit 12 may suggest a delivery plan based on the candidate delivery areas for revision as part of the delivery plan information. In other words, in the delivery area management system 1 according to this embodiment, it is sufficient for the display 44 to show delivery plan information based on at least one of the delivery areas from the generated delivery plan information and the candidate delivery areas for revision.

[0071] The plan modification unit 13 receives change instructions from operators such as delivery drivers and managers via the HMI 43. The plan modification unit 13 also modifies (changes) the delivery plan generated by the delivery planning unit 11 based on the received change instructions. Note that the delivery planning unit 11 and the plan modification unit 13 may be implemented as a single function.

[0072] The storage unit 14 is implemented, for example, by memory 42. The storage unit 14 stores various types of 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 Figure 4), which includes delivery conditions such as cargo, consignor, delivery destination, and delivery time. For example, the storage unit 14 stores vehicle-related information such as vehicle information (see Figure 5), area information (see Figure 6), and driver information (see Figure 7). For example, the storage unit 14 stores past delivery plan information and generated delivery plan information (see Figure 8). For example, the storage unit 14 stores change reason information, which includes timestamps and delivery person-dependent information, and change history information, which includes modification attribute information. The change history information may include past delivery plan information and information about the delivery person's feelings towards past delivery plans, such as sentiment change information. For example, the storage unit 14 stores environmental information acquired from the vehicle 30 or collected by the management device 10.

[0073] In addition, some of the functions of the management device 10 according to this embodiment may be implemented outside the management device 10, such as a server device that is separately provided in the delivery area management system 1 and connected to the management device 10 via the network N in a manner that enables communication with the management device 10.

[0074] Here, with reference to the drawings, various pieces of information regarding the delivery management process according to this embodiment will be explained.

[0075] Figure 4 shows an example of delivery request information 501 according to the embodiment. Delivery request information 501 is information indicating at least one delivery destination and delivery time for at least one package, and includes information on delivery conditions such as the package, consignor, delivery destination, and delivery time. In the example in Figure 4, the delivery request information 501 includes items for delivery destination, package, and delivery lot for each package. The delivery destination item includes information indicating the address and area of ​​the delivery destination. The package item includes information indicating the type of package, size, volume, quantity, and weight. The delivery lot item includes information indicating the delivery time.

[0076] Figure 5 shows an example of vehicle information 502 according to an embodiment. Vehicle information 502 is information for each of at least one vehicle 30 included in the delivery fleet 20, and is an example of vehicle-related information. In the example in Figure 5, vehicle information 502 includes area and vehicle type items for each vehicle. Vehicle information 502 may also include the load capacity item for each vehicle 30. Vehicle information 502 may also include the type of vehicle based on the power source of each vehicle 30 (e.g., gasoline vehicle, electric vehicle, hybrid vehicle). Vehicle information 502 may also include the type of fuel for each vehicle 30 (e.g., gasoline, diesel, LPG, hydrogen). Vehicle information 502 may also include the fuel supply location for each vehicle 30, such as the presence of a designated refueling station or charging facility.

[0077] Figure 6 shows an example of area information 503 according to the embodiment. Area information 503 is information that indicates part or all of the delivery area where deliveries are made by the delivery fleet 20, and is an example of vehicle-related information. In the example in Figure 6, area information 503 is information that indicates the location and division of each area.

[0078] Figure 7 shows an example of driver information 504 according to the embodiment. Driver information 504 is information of at least one delivery person who makes deliveries using vehicle 30 in the delivery fleet 20, and is an example of vehicle-related information. In the example in Figure 7, driver information 504 includes attribute, applicable vehicle type, and work information items for each delivery person. The attribute item includes gender and level information defined by proficiency and experience. For example, the level information may be set based on proficiency and experience, the range of each delivery person's capabilities such as speed in loading and unloading cargo and the weight they can handle. Note that the gender attribute is not a mandatory component and may be set only if requested by a customer, for example. The applicable vehicle type item is information indicating the types of vehicles 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.

[0079] Figure 8 shows an example of delivery plan information 505 including delivery area information according to an embodiment. The delivery plan information 505 includes, for each of at least one vehicle 30, delivery area information indicating the delivery area in which the delivery person will deliver at least one package by vehicle 30, and information indicating the delivery route to at least one delivery destination within that delivery area. This delivery route is a route that goes around at least one destination, including at least one delivery destination. In the example in Figure 8, the delivery plan information 505 includes the following items for each delivery: delivery lot, vehicle, delivery information, delivery area, delivery route, driver, and load (weight). The delivery lot item is information indicating the delivery time for each delivery. The vehicle item is information indicating the vehicle 30 used for each delivery. The delivery information item is information indicating the correspondence with the delivery request information for the package delivered in each delivery. The delivery area item is information indicating at least one area in which the vehicle 30 moves in each delivery (delivery area information). The delivery route item is information indicating the delivery route within the delivery area for each delivery. The "Driver" field indicates the delivery person responsible for each delivery. The "Load (Weight)" field indicates the total amount of cargo loaded onto vehicle 30 for each delivery.

[0080] In the delivery area management system 1 according to the above embodiment, communication between the management device 10 and the delivery fleet 20 may be performed by wireless communication such as Wi-Fi®, or by wired communication via a LAN (Local Area Network) cable or other Ethernet®-compatible standard or dedicated connection cable.

[0081] Furthermore, in the delivery area management system 1 according to the above embodiment, the exchange of various types of information according to the embodiment in 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 computer-readable storage mediums, for example, CD-ROMs, flexible disks (FDs), CD-Rs, DVDs (Digital Versatile Disks), etc., can be used as appropriate. As portable external storage devices, HDDs, SSDs, Flash memory, etc., can be used as appropriate.

[0082] Furthermore, in the delivery area management system 1 according to the above-described embodiment, there are cases where various types of information according to the embodiment are transmitted from the management device 10 to the delivery fleet 20, such as when delivery plans and delivery areas for revision candidates are displayed on mobile terminals used by vehicles 30, operators (managers), or drivers (delivery personnel) (see Figures 10 to 13), or when change instructions are received. On the other hand, in the delivery area management system 1 according to the above-described embodiment, there are cases where some or all of the various types of information according to the embodiment are not transmitted from the delivery fleet 20 to the management device 10, such as when environmental information is collected from sensors separately connected to the management device 10 or from outside the delivery area management system 1, or when environmental information is input to mobile terminals or the management device 10 by delivery personnel or managers. Also, in the delivery area management system 1 according to the above-described embodiment, there are cases where some or all of the various types of information according to the embodiment in the management device 10 are acquired via other devices, such as when change reason information or information of the person who made the change is input to mobile terminals or vehicles 30 by delivery personnel or managers.

[0083] Next, we will explain the processing flow executed by the delivery area management system 1 configured as described above.

[0084] Figure 9 is a flowchart showing an example of the flow of the delivery area management process executed by the management device 10 according to the embodiment. The flow in Figure 9 is executed at the time when the administrator plans the delivery, such as in the morning before delivery or the night before, but is not limited to this. It can be started at any time in response to an operation by an operator such as an administrator, and may be executed multiple times a day or once every few days. Figures 10 to 13 are diagrams showing examples of displays in the delivery area management process.

[0085] The delivery planning unit 11 reads delivery request information and vehicle information from, for example, the storage unit 14, and generates delivery plan information including delivery area information based on the delivery request information and vehicle information (S101). The delivery planning unit 11 also presents the generated delivery plan information (S102). When presenting the delivery plan information, if a delivery area for revision candidates has been extracted, the revision presentation unit 12 further displays information regarding the extracted delivery area for revision candidates.

[0086] Figure 10 illustrates how the generated delivery plan information is presented on the display screen 610. The display screen 610 in Figure 10 shows delivery plan information for each of the vehicles 30 of "Vehicle 1" and "Vehicle 2". Specifically, the delivery plan information for vehicle 30 of "Vehicle 1" shows the delivery area, "Vehicle 1 Area," and the delivery route within "Vehicle 1 Area" that delivers to each destination via the destination in the order of "A→B→E→F→I". Similarly, the delivery plan information for vehicle 30 of "Vehicle 2" shows the delivery area, "Vehicle 2 Area," and the delivery route within "Vehicle 2 Area" that delivers to each destination via the destination in the order of "C→D→H→G".

[0087] Each delivery route may consist of two or more sections. For example, the delivery route of vehicle 30 of "vehicle 1" may consist of a section that delivers to each delivery destination via the destination in the order "A→B→E", and a section that delivers to each delivery destination via the destination in the order "E→F→I".

[0088] The revision suggestion unit 12 determines whether the generated delivery plan information includes the delivery area of ​​the revision candidate (S103). Specifically, the revision suggestion unit 12 identifies at least one delivery area of ​​the revision candidate from at least one delivery area of ​​the delivery plan generated by the delivery plan unit 11, based on the delivery plan information and change history information. Then, the revision suggestion unit 12 determines whether the delivery area of ​​the revision candidate has been identified from at least one delivery area of ​​the delivery plan generated by the delivery plan unit 11.

[0089] If the generated delivery plan information does not include the delivery area that is a candidate for review (S103: No), the process in Figure 10 proceeds to S108.

[0090] On the other hand, if the generated delivery plan information includes a delivery area that is a candidate for revision (S103: Yes), the revision suggestion unit 12 presents information regarding the delivery area that is a candidate for revision (S104).

[0091] The display screen 610 in Figure 10 includes a notification 615 indicating that the generated delivery plan information includes a delivery area that is a candidate for revision. This notification 615 is an example of information regarding the delivery area that is a candidate for revision. Figure 10 illustrates a case where the message "Previous area change occurred" is displayed as notification 615.

[0092] Notification 615 may display the change history as a list, or the list of change history may expand upon selection. This list display may present the change history along with environmental information and work information, such as the season in which past changes were made.

[0093] Figure 11 illustrates a case where, as information regarding the delivery area of ​​candidates for review, delivery plan information for past revised delivery areas is presented on display screen 620. Display screen 620 in Figure 11 may be displayed, for example, when a user operation is performed on display screen 610 in Figure 10 in response to notification 615. Note that display screen 620 in Figure 11 may be the destination screen of display screen 610 in Figure 10, or part or all of it may be a pop-up display for display screen 610 in Figure 10. Furthermore, the generated delivery plan information and the delivery plan information for past revised delivery areas may be displayed on a single screen for comparison.

[0094] In the display screen 620 of Figure 11, the delivery plan information for vehicle 30 of "vehicle 1" shows the "vehicle 1 area," which is the delivery area of ​​a past delivery plan, and the delivery route within that "vehicle 1 area" that goes through the destination in the order of "A→B→C→D→E→F→I" to each delivery destination. Similarly, the delivery plan information for vehicle 30 of "vehicle 2" shows the "vehicle 2 area," which is the delivery area of ​​a past delivery plan, and the delivery route within that "vehicle 2 area" that goes through the destination in the order of "H→G" to each delivery destination. In this case, the delivery area that has been changed from the "vehicle 2 area" of "vehicle 2" to the "vehicle 1 area" of "vehicle 1" may be highlighted, for example, as illustrated in Figure 11. Note that the display method may differ, and may include colors or shading.

[0095] Figure 12 illustrates an example where past reasons for changes are presented on display screen 630 as information regarding delivery areas under review. Possible examples of past reasons for changes include messages such as "trust relationship between driver and customer," "driver's geographical familiarity," "urgent delivery (LPG gas out)," and "EV vehicle, charging stop required." Display screen 630 in Figure 12 may be displayed, for example, when an operator performs an action on display screen 620 in Figure 11 regarding each delivery area or changes to the delivery area. Alternatively, for example, an operation button to instruct the display of the reason for change may be provided on display screen 620 in Figure 11, and the display may be displayed when an operator performs an action on that button.

[0096] Furthermore, it is sufficient to provide the operator with the reason for the change, and an AI agent that uses natural language processing to enable dialogue with the operator may convey the reason for the change to the operator. In this case, the information provided may also include advice on whether or not to proceed with the change. For example, this information could be: "Last time, the area was changed due to an emergency delivery (LPG gas out). This time it is not an emergency delivery, so there is no need to change the area. Would you like to change the area?"

[0097] Figure 13 illustrates a case where a message is displayed on screen 640 to confirm with the user whether to reflect the previous changes presented as information regarding the delivery area of ​​the candidate for revision in the current delivery plan (change confirmation). In the example of Figure 13, screen 640 includes operation buttons such as "Yes" and "No" to accept operator input indicating whether to reflect the previous changes presented in the current delivery plan. Screen 640 in Figure 13 may be displayed after, or together with, screen 630 in Figure 12 when, for example, an operator operation is performed on each delivery area or the changes to the delivery area in screen 620 in Figure 11.

[0098] Furthermore, it is sufficient for the operator to confirm the change, and the AI ​​agent may decide whether or not to make the change through conversation with the operator.

[0099] Furthermore, display screens 630 and 640 may be pop-up screens or destination screens for at least one of display screens 610 and 620, or they may be implemented as part of at least one of display screens 610 and 620.

[0100] The content displayed on screens 630 and 640 may also be the output of an AI agent that uses natural language processing to facilitate interaction with an operator.

[0101] The plan modification unit 13 determines, for example, whether a change to the delivery plan has been instructed based on the results of the operator's input to the HMI 43, etc. (S105). For example, the plan modification unit 13 determines that a change to the delivery plan has been instructed if the selection of the "Yes" button is detected on the display screen 640. For example, the plan modification unit 13 determines that the delivery plan will not be modified if the selection of the "No" button is detected on the display screen 640, or if no selection of any operation button is detected for a predetermined period of time or longer.

[0102] If a change to the delivery plan is instructed (S105: Yes), the plan modification unit 13 acquires the details of the change along with the reason for the change and the information of the person making the change, and modifies the delivery plan information (S106). The plan modification unit 13 also generates change history information based on the details of the change, the reason for the change, and the information of the person making the change, and records the generated change history information, for example, in the storage unit 14 (S107).

[0103] On the other hand, if no change to the delivery plan is instructed (S105: No), the flow in Figure 9 proceeds to process S108. Alternatively, if no change to the delivery plan is instructed (S105: No), the flow in Figure 9 may return to process S103.

[0104] Subsequently, the delivery planning unit 11 notifies the delivery person of the generated or modified delivery plan information (S108). After processing S108, the flow shown in Figure 11 is completed.

[0105] The following describes an example of the application of the delivery area management system 1 according to the above embodiment, with reference to the drawings.

[0106] (First application example) This application example illustrates a case where, in the previous delivery plan, the delivery area was changed due to the delivery day of the week, as a temporary change reason for "urgent delivery," but in the current delivery plan, changing the delivery area is not essential. Figure 14 shows an example of the display in the delivery area management process related to the first application example.

[0107] Figure 14 illustrates a display screen 610a that presents automatically generated delivery plan information for this delivery plan. Display screen 610a corresponds to the display screen 610 according to the embodiment described above. Display screen 610a shows the "Vehicle 1 Area" of "Vehicle 1" which makes deliveries on Tuesdays and Thursdays, and the delivery route in the "Vehicle 1 Area" that delivers to each delivery destination via the destination in the order of "C→D→H→G". Similarly, display screen 610a shows the "Vehicle 2 Area" of "Vehicle 2" which makes deliveries on Mondays, Wednesdays, and Fridays, and the delivery route in the "Vehicle 2 Area" that delivers to each delivery destination via the destination in the order of "A→B→E→F→I".

[0108] Furthermore, the display screen 610a includes a notification 615 indicating that, due to the change in the delivery area in the previous delivery plan due to the delivery day of the week, there are delivery areas that could be reviewed. This allows the operator to easily understand that a change in the delivery area was made in the previous delivery plan and to begin deciding whether or not the change is necessary.

[0109] Figure 14 also illustrates a display screen 620a that presents delivery plan information for the previously changed delivery area as information regarding the delivery area of ​​the candidate for review. Display screen 620a corresponds to display screen 620 according to the embodiment described above. Display screen 620a shows the "Vehicle 1 area" of "Vehicle 1" which makes deliveries on Tuesdays and Thursdays, and the delivery route in "Vehicle 1 area" that delivers to each delivery destination via the destination in the order of "C→D→H→G→C→F→I". Display screen 620a also shows the "Vehicle 2 area" of "Vehicle 2" which makes deliveries on Mondays, Wednesdays, and Fridays, and the delivery route in "Vehicle 2 area" that delivers to each delivery destination via the destination in the order of "A→B→E". This allows the operator to see that the delivery route included point "I", which was the destination (delivery destination) for the emergency delivery. Furthermore, the operator can see that the delivery route involved passing through the starting point "C" twice, as vehicle 30 of "Vehicle 1" could not be transported in one go due to the amount of cargo. In this way, the operator can easily understand the changes made to the delivery area in the previous delivery plan and determine whether or not those changes need to be applied to the current delivery plan.

[0110] Furthermore, Figure 14 illustrates a display screen 630a that presents the reason for past changes as information regarding delivery areas that are candidates for review. Display screen 630a corresponds to display screen 630 according to the embodiment described above. Display screen 630a displays a message indicating that the reason for the change in the delivery area made in the previous delivery plan was "urgent delivery". This allows the operator to easily understand the reason for the change in the delivery area made in the previous delivery plan and use it as a basis for deciding whether or not to apply that change to the current delivery plan. Specifically, in the example of Figure 14, the operator can easily understand that the previous change was made for the provisional reason of "urgent delivery", and therefore can decide that it is unnecessary to apply it to the current delivery plan.

[0111] Furthermore, Figure 14 illustrates a display screen 640a that confirms with the user whether to reflect the previously presented changes (recommended delivery areas) in the current delivery plan, as information regarding the delivery areas to be reviewed. Display screen 640a corresponds to the display screen 640 according to the embodiment described above. This allows the operator to easily indicate whether or not to apply the changes to the delivery area made in the previous delivery plan to the current delivery plan.

[0112] (Second application example) This application example illustrates a case where, in the previous delivery plan, the delivery area was changed due to restrictions related to the vehicle type 30 being an "EV (electric vehicle)," but in the current delivery plan, a change in the delivery area is not necessary because a "non-EV" vehicle 30 will be used. Figure 15 shows an example of the display in the delivery area management process related to the second application example.

[0113] Figure 15 illustrates a display screen 610b that presents automatically generated delivery plan information for this delivery plan. Display screen 610b corresponds to the display screen 610 according to the embodiment described above. Display screen 610b shows the "Vehicle 1 Area" of "Vehicle 1" which makes deliveries using the "non-EV" vehicle 30, and the delivery route that delivers to each delivery destination via the destination in the order of "C→D→H→G" within the "Vehicle 1 Area". Similarly, display screen 610b shows the "Vehicle 2 Area" of "Vehicle 2" which makes deliveries using the "non-EV" vehicle 30, and the delivery route that delivers to each delivery destination via the destination in the order of "A→B→E→F→I" within the "Vehicle 2 Area". Here, the starting point "A" of the delivery route in Vehicle 2 Area is assumed to be a charging facility or a delivery base with an attached charging facility.

[0114] Furthermore, the display screen 610b includes a notification 615 indicating that there are potential delivery areas for review due to a change in the delivery area, which was tentatively changed because the vehicle type 30 used in the previous delivery plan was "EV". This allows the operator to easily understand that a change in the delivery area was made in the previous delivery plan and to begin determining whether or not the change is necessary.

[0115] Figure 15 also illustrates a display screen 620b that presents delivery plan information for the previously modified delivery area as information regarding the delivery area of ​​the candidate for review. Display screen 620b corresponds to display screen 620 according to the embodiment described above. Display screen 620b shows the "Vehicle 1 area" where deliveries were made by "Vehicle 1", which is a "non-EV" vehicle, and the delivery route in that "Vehicle 1 area" where deliveries were made via the destination in the order of "C→D→H→G→F→I". Display screen 620b also shows the "Vehicle 2 area" where deliveries were made by "Vehicle 2", which is an "EV" vehicle, and the delivery route in that "Vehicle 2 area" where deliveries were made via the destination in the order of "A→B→E→A". From this, it can be seen that the operator's delivery route involved visiting each delivery destination while charging at charging facility point "A" before and after deliveries. Furthermore, the operator can see that the delivery area for "Vehicle 2," an "EV" that requires charging, has been reduced, while the delivery area for "Vehicle 1," a "non-EV" that does not require charging, has been expanded. The operator can also see that the total distance traveled by "Vehicle 1" and "Vehicle 2" has increased compared to before the revision. In this way, the operator can easily understand the changes made to the delivery area in the previous delivery plan and determine whether or not those changes need to be applied to the current delivery plan.

[0116] Furthermore, Figure 15 illustrates a display screen 630b that presents the reasons for past changes as information regarding the delivery area of ​​candidates for review. Display screen 630b corresponds to the display screen 630 according to the embodiment described above. Display screen 630b displays a message indicating that the reason for the change in the delivery area made in the previous delivery plan was that the vehicle type of vehicle 30 was "EV" and the vehicle type for the current plan is "non-EV". This allows the operator to easily understand the reason for the change in the delivery area made in the previous delivery plan and use it as a basis for deciding whether or not to apply that change to the current delivery plan. Specifically, in the example of Figure 15, the operator can easily understand that the previous change was made for the provisional reason of using an "EV" vehicle type, and therefore can decide that it is unnecessary to apply it to the current delivery plan.

[0117] Furthermore, Figure 14 illustrates a display screen 640b that confirms with the user whether to reflect the previously presented changes (recommended delivery areas) in the current delivery plan, as information regarding the delivery areas to be reviewed. Display screen 640b corresponds to the display screen 640 according to the embodiment described above. This allows the operator to easily indicate whether or not to apply the changes to the delivery area made in the previous delivery plan to the current delivery plan.

[0118] As described above, in the delivery area management system 1 according to the embodiment, the management device 10 is configured to compare the automatically generated delivery plan (e.g., delivery area) with past versions, identify delivery areas that are candidates for revision based on change history information, and present them along with information on past changes. This configuration, which presents delivery areas that are candidates for revision, helps to suppress operational errors such as operator oversights when it comes to correcting the automatically generated delivery plan, and enables appropriate corrections.

[0119] Furthermore, in the delivery area management system 1 according to this embodiment, the information on past changes presented along with the delivery area candidates for review includes at least one of the following: whether or not the delivery area was manually changed in the past, the content of the change, and the reason for the change. This configuration provides operators with information to help them decide whether or not to reflect the delivery area candidates for review in the current delivery plan. In other words, with the above configuration, it is possible to decide whether or not to revise the delivery plan based on the reasons for past changes, thereby realizing a delivery plan that is satisfactory to both managers and delivery personnel.

[0120] In the embodiments described above, a configuration for presenting candidate delivery areas for revision was illustrated, but the invention is not limited thereto. The delivery area management system 1 according to this disclosure may be configured to identify and present, instead of, or in addition to, a part (delivery section) or all of at least one delivery route (delivery path) of the delivery plan information as a candidate delivery section or delivery route for revision.

[0121] For example, a delivery section or delivery route that is a candidate for revision can be identified or presented in the same way as a delivery area that is a candidate for revision. As an example, the revision presentation unit 12 may present as a candidate route for revision a route in which the pre-revision or post-revision route matches the pre-revision or post-revision route in the history of past changes, among the routes of at least one delivery section included in the created delivery plan.

[0122] For example, in the embodiment described above, the delivery area to be reviewed may be a delivery area that includes delivery sections that have been changed in the past.

[0123] In each of the embodiments described above, "determining whether it is A" may mean determining whether it is A, determining whether it is not A, or determining whether or not it is A.

[0124] Each program executed by each device of the delivery area management system 1 according to the above-described embodiment is provided as a file in an installable or executable format, recorded on a computer-readable storage medium such as a CD-ROM, floppy disk, CD-R, or DVD.

[0125] Furthermore, the programs executed by each device of the delivery area management system 1 according to each embodiment described above may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Alternatively, the programs executed by each device of the delivery area management system 1 according to each embodiment described above may be provided or distributed via a network such as the Internet.

[0126] Furthermore, the programs executed by each device of the delivery area management system 1 according to each embodiment described above may be pre-installed and provided in ROM or the like.

[0127] Furthermore, the programs executed by each device of the delivery area management system 1 according to each embodiment described above are configured as modules including the functional units described above. In actual hardware, a processor 41 such as a CPU reads and executes the program from memory 42 such as ROM or HDD, thereby loading the functional units onto the RAM of memory 42 and generating the functional units on the RAM of memory 42.

[0128] According to at least one embodiment described above, the automatically generated delivery plan can be appropriately modified.

[0129] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0130] (Note) Based on the above description of embodiments, the following technologies are disclosed. (A1) Delivery request information indicating at least one delivery destination and delivery time for at least one package, Based on vehicle-related information indicating information about the vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination, To generate delivery plan information that shows a delivery plan including at least one delivery area in which the delivery person delivers at least one of the aforementioned packages using the vehicle, Based on the generated delivery plan information and the change history information showing the history of changes to past delivery plans, information is presented regarding the delivery area of ​​the candidate for review among the at least one delivery area included in the generated delivery plan. This includes modifying the delivery plan based on the change instructions received for the delivery plan, Delivery area management method (information processing method). (A2) The information regarding the proposed delivery areas for review includes information indicating the reason for the change regarding at least one delivery area that has been previously changed among the at least one delivery area included in the generated delivery plan. The delivery area management method described in (A1) above. (A3) The information indicating the reason for the aforementioned change includes delivery-dependent information indicating the reason for the previous change in the delivery person, The delivery area management method described in (A2) above. (A4) The aforementioned delivery person dependency information includes information indicating the relationship between the delivery person and the customer at the delivery destination. The delivery area management method described in (A3) above. (A5) The delivery person dependency information includes information indicating the delivery person's geographical familiarity with at least one area where at least one delivery destination exists. The delivery area management method described in (A3) or (A4) above. (A6) The information indicating the reason for the aforementioned change includes provisional reason information indicating the provisional reasons for the aforementioned past change. A delivery area management method as described in any one of the above items (A2) to (A5). (A7) The aforementioned provisional reason information includes information indicating that the change was due to an emergency response. The delivery area management method described in (A6) above. (A8) The aforementioned provisional reason information includes information indicating that the vehicle was an electric vehicle that was being charged at a charging facility within the delivery area. The delivery area management method described in (A6) or (A7) above. (A9) The information regarding the delivery areas of the aforementioned revision candidates includes information indicating that the generated delivery plan includes delivery areas that have been changed in the past. A delivery area management method as described in any one of the above items (A1) to (A8). (A10) The information regarding the proposed delivery areas for revision includes information indicating at least one delivery area that has been previously changed from the at least one delivery area included in the generated delivery plan. A delivery area management method as described in any one of the above items (A1) to (A9). (A11) The aforementioned revised delivery area includes a delivery area that partially or completely matches at least one previously modified delivery area among the at least one delivery area included in the generated delivery plan. A delivery area management method described in any one of the above items (A1) to (A10). (A12) The aforementioned candidate delivery areas for revision include delivery areas where part or all of the delivery route used by the delivery person to deliver at least one package from the at least one delivery area included in the generated delivery plan has been changed in the past. A delivery area management method described in any one of the above items (A1) to (A11). (A13) Delivery request information indicating at least one delivery destination and delivery time for at least one package, Based on vehicle-related information indicating information about the vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination, A planning unit that generates delivery plan information indicating a delivery plan that includes at least one delivery area in which the delivery person delivers at least one package using the vehicle, A presentation unit presents information regarding a candidate delivery area for review among the at least one delivery area included in the generated delivery plan, based on the generated delivery plan information and change history information showing a history of changes to past delivery plans. A modification unit that modifies the delivery plan based on a change instruction received for the delivery plan, Delivery area management device (information processing device). (B1) Delivery request information indicating at least one delivery destination and delivery time for at least one package, Based on vehicle-related information indicating information about the vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination, A planning unit that presents delivery plan information, including the route of at least one delivery section and the delivery time, for which the delivery person delivers at least one package using the vehicle, A presentation unit presents candidate routes for revision among the routes of at least one delivery section included in the generated delivery plan, based on the generated delivery plan information and change history information showing a history of past changes to the delivery plan. A modification unit that modifies the delivery plan based on a change instruction received for the delivery plan, Delivery management device (information processing device). (B2) The presentation unit presents, as the candidate route for revision, a route among the routes of at least one delivery section included in the delivery plan, where the pre-revision or revised route matches the history of past changes. The delivery management device described in (B1) above. (B3) The change history information includes at least delivery-dependent information indicating the reasons for the changes that depend on the delivery person in the past changes. The delivery management device described in (B1) above. (B4) The aforementioned delivery driver-dependent information is information indicating at least one reason for the aforementioned past change, among distance priority, time priority, U-turn prevention, narrow road prevention, congestion prevention, accident risk prevention, and right turn prevention. The delivery management device described in (B3) above. (B5) The change history information includes at least modification attribute information indicating the attributes of the issuing entity that issued the change instruction in the past change, A delivery management device as described in any one of the above items (B1) to (B4). (B6) The modification attribute information is information indicating the entity that instructed the past change, which is at least one of the following: information indicating whether it is a person or a computer that performs inference using a machine learning model; information indicating whether it is a veteran or not; and information indicating whether it is the delivery person or the manager who manages the delivery. The delivery management device described above (B5). (B7) The display unit presents information regarding the delivery person's feelings towards the delivery plan in the past changes, along with the proposed revised routes. A delivery management device as described in any one of the above items (B1) to (B6). (B8) The display unit estimates the current condition of the delivery person based on work information indicating the delivery person's work status, and presents information indicating the estimated condition along with the proposed revised routes. A delivery management device as described in any one of the above items (B1) to (B7). (B9) The display unit presents information indicating at least one of the following: the time, weather, and temperature when the past change was made, along with the proposed route for the revision. A delivery management device as described in any one of the above items (B1) to (B8). (B10) 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 aforementioned change instructions for the delivery plan, The system further includes a display unit that displays at least the delivery plan information from among the delivery plan information and the proposed revised routes, A delivery management device as described in any one of the above items (B1) to (B9). (B11) Delivery request information indicating at least one delivery destination and delivery time for at least one package, Based on vehicle-related information indicating information about the vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination, To provide delivery plan information that includes the route of at least one delivery section and the delivery time for the delivery of at least one package by the delivery person using the vehicle, Based on the generated delivery plan information and the change history information showing the history of past changes to the delivery plan, the system presents candidate routes for revision among the routes of at least one delivery section included in the generated delivery plan. This includes modifying the delivery plan based on the change instructions received for the delivery plan, Delivery management method (information processing method). (C1) A program for causing a computer to execute any one of the information processing methods described in (A1) through (A12) and (B11) above. (C2) A computer program that is executed by a computer, and on which the program described in (C1) above is recorded, is a non-transient computer-readable storage medium (Computer Program Product). [Explanation of Symbols]

[0131] 1. Delivery Area Management System 10 Management device 11. Delivery Planning Department 12 Review Presentation Section 13. Plan Revision Department 14 Storage section 20 Delivery Fleet 30 vehicles 41 processors 42 memory 43 HMI 44 displays 45 Input Interfaces 46 Communication I / F N Network

Claims

1. Delivery request information indicating at least one delivery destination and delivery time for at least one package, Based on vehicle-related information indicating information about the vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination, To generate delivery plan information that shows a delivery plan including at least one delivery area in which the delivery person delivers at least one of the aforementioned packages using the vehicle, Based on the generated delivery plan information and the change history information showing the history of changes to past delivery plans, information is presented regarding the delivery area of ​​the candidate for review among the at least one delivery area included in the generated delivery plan. This includes modifying the delivery plan based on the change instructions received for the delivery plan, Delivery area management method.

2. The information regarding the proposed delivery areas for review includes information indicating the reason for the change regarding at least one delivery area that has been previously changed among the at least one delivery area included in the generated delivery plan. The delivery area management method according to claim 1.

3. The information indicating the reason for the aforementioned change includes delivery-dependent information indicating the reason for the previous change in the delivery person, The delivery area management method according to claim 2.

4. The aforementioned delivery person dependency information includes information indicating the relationship between the delivery person and the customer at the delivery destination. The delivery area management method according to claim 3.

5. The delivery person dependency information includes information indicating the delivery person's geographical familiarity with at least one area where at least one delivery destination exists. The delivery area management method according to claim 3.

6. The information indicating the reason for the aforementioned change includes provisional reason information indicating the provisional reasons for the aforementioned past change. The delivery area management method according to claim 2.

7. The aforementioned provisional reason information includes information indicating that the change was due to an emergency response. The delivery area management method according to claim 6.

8. The aforementioned provisional reason information includes information indicating that the vehicle was an electric vehicle that was being charged at a charging facility within the delivery area. The delivery area management method according to claim 6.

9. The information regarding the delivery areas of the aforementioned revision candidates includes information indicating that the generated delivery plan includes delivery areas that have been changed in the past. The delivery area management method according to claim 1.

10. The information regarding the proposed delivery areas for revision includes information indicating at least one delivery area that has been previously changed from the at least one delivery area included in the generated delivery plan. The delivery area management method according to claim 1.

11. The aforementioned revised delivery area includes a delivery area that partially or completely matches at least one previously modified delivery area among the at least one delivery area included in the generated delivery plan. The delivery area management method according to claim 1.

12. The aforementioned candidate delivery areas for revision include delivery areas where part or all of the delivery route used by the delivery person to deliver at least one package from the at least one delivery area included in the generated delivery plan has been changed in the past. The delivery area management method according to claim 1.

13. Delivery request information indicating at least one delivery destination and delivery time for at least one package, Based on vehicle-related information indicating information about the vehicle used by the delivery person to deliver the at least one package to the at least one delivery destination, A planning unit that generates delivery plan information indicating a delivery plan that includes at least one delivery area in which the delivery person delivers at least one package using the vehicle, A presentation unit presents information regarding a candidate delivery area for review among the at least one delivery area included in the generated delivery plan, based on the generated delivery plan information and change history information showing a history of changes to past delivery plans. A modification unit that modifies the delivery plan based on a change instruction received for the delivery plan, Delivery area management device.

Images