Delivery management device and delivery management method

Abstract

To improve delivery efficiency while ensuring continued use at the delivery destinations. [Solution] The delivery management device of the embodiment is a delivery management device that creates a delivery plan for delivering delivery containers containing consumables to one or more delivery destinations based on delivery information and linkage information, wherein the delivery information includes the address of the delivery destination, the delivery container and information on the delivery date, the linkage information includes the predicted consumption date of the consumables in the delivery containers delivered to each delivery destination, and comprises an environmental information acquisition unit that acquires environmental information from an external system that includes at least weather or climate information for the delivery destination, a modification unit that modifies the predicted consumption date based on the environmental information, and a creation unit that creates a delivery plan that includes at least a delivery date based on the delivery information and the modified predicted consumption date.

Description

Technical Field

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

Background Art

[0002] In LPG (Liquefied Petroleum Gas) delivery, a delivery service is provided to replace LP containers before the gas remaining in the LP containers to be delivered runs out. The LP gas filled in the LP containers is purchased by the delivery operator from the wholesaler and delivered to the customers. Since the customers pay the LPG usage fee monthly or based on the usage amount, the increase in the unconsumed gas (hereinafter referred to as residual gas) by the customers affects the business indicators (KPI: Key Performance Indicator) of the delivery operator. Also, the efficiency such as time and distance in delivery affects the business indicators.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The gas remaining in the LP containers used by the customers is measured by the staff who make regular rounds, and is notified to the delivery operator together with the consumption prediction date, and the delivery operator can know the predicted date when the LP gas will be consumed. Note that the notification is also performed via a network or the like. However, due to the sense of mission of the infrastructure provider that the LP gas must not run out, the operator ultimately delivers the gas before the predicted date, and ends up collecting the LP containers in a state where a large amount of residual gas is stored, which affects the business indicators. In addition, when the LPG runs out or the like, it becomes necessary to arrange a vehicle for ad hoc delivery response, etc., and the delivery efficiency deteriorates. Balancing the reduction of residual LPG gas with the avoidance of emergency deliveries is a key performance indicator (KPI) for LPG delivery companies.

[0005] The present invention has been made in view of the above, and its object is to provide a delivery management device and a delivery management method that can suppress deterioration of delivery efficiency while ensuring the continued use of the delivered items at the delivery destination. [Means for solving the problem]

[0006] The delivery management device of the embodiment is a delivery management device that creates a delivery plan for delivering delivery containers containing consumables to one or more delivery destinations based on delivery information and linkage information, wherein the delivery information includes the address of the delivery destination, the delivery container and the delivery date, the linkage information includes the predicted consumption date of the consumables in the delivery containers that have been delivered to each delivery destination, and includes an environmental information acquisition unit that acquires environmental information from an external system that includes at least weather or climate information for each delivery destination, and a modification unit that modifies the predicted consumption date based on the environmental information. The system includes a creation unit that creates a delivery plan, including at least a delivery date, based on the aforementioned delivery information and the revised consumption forecast date. [Effects of the Invention]

[0007] According to this disclosure, it is possible to improve delivery efficiency while ensuring the continued use of the delivered items at the delivery destination. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows an example of the configuration of a delivery management system according to the embodiment. [Figure 2] Figure 2 is an explanatory diagram illustrating an example of the operation of the delivery management system according to the embodiment. [Figure 3] Figure 3 shows an example of the hardware configuration of the management device according to the embodiment. [Figure 4] Figure 4 shows an example of the configuration of a management device according to an embodiment. [Figure 5] Figure 5 is a flowchart showing an example of the flow of delivery management processing performed by the delivery management device according to the embodiment. [Figure 6] Figure 6 is an explanatory diagram of the geographical relationship between the filling station and the delivery destination (customer) within the area managed by the delivery management device 10, as well as the delivery area and delivery route. [Figure 7] Figure 7 shows an example of delivery destination management data corresponding to Figure 6. [Figure 8] Figure 8 is an explanatory diagram of LPG remaining quantity forecasting and revision of the remaining quantity forecasting. [Figure 9] Figure 9 is a flowchart illustrating the process of creating a delivery plan based on whether or not a route change involves a change in service area. [Figure 10] Figure 10 is an explanatory diagram for route changes within the same delivery area. [Figure 11] Figure 11 is an explanatory diagram for route changes that involve changes in the delivery area. [Figure 12] Figure 12 is an explanatory diagram of an example of a delivery plan presentation screen that includes inquiries to the operator when the delivery area is changed. [Figure 13] Figure 13 is an explanatory diagram for using extra services. [Modes for carrying out the invention]

[0009] The embodiments of the delivery management device relating to this disclosure will be described below with reference to the drawings. In this disclosure, components that are identical or substantially identical to those described above in previously shown figures will be denoted by the same reference numerals, and explanations may be omitted as appropriate. Furthermore, even when representing identical or substantially identical parts, the dimensions and proportions may differ between drawings.

[0010] Further, from the perspective of ensuring the visibility of the drawings, for example, in the description of each drawing, only the main components are labeled with reference numerals, and there may be cases where components that are the same or substantially the same as those described in the previous drawings are not labeled with reference numerals.

[0011] Hereinafter, as an example, a case where the technology according to the present disclosure is applied to a delivery management system for an LPG (Liquefied Petroleum Gas) cylinder as a consumption target and an LPG cylinder as a delivery container will be described.

[0012] FIG. 1 is a diagram showing an example of the configuration of a delivery management system according to an embodiment. As shown in FIG. 1, the delivery management system 1 includes a delivery management device 10, a backbone data center 20, and an environmental data center 30, which are communicably connected via a network N and a predetermined API (Application Programing Interface) service. As the network N, for example, a telecommunication line such as the Internet can be used.

[0013] FIG. 2 is an explanatory diagram of an example of an operation mode of the delivery management system according to an embodiment. As an example, the delivery management device 10 creates (formulates) a delivery plan for a delivery in which a deliverer delivers at least one LPG cylinder to at least one delivery destination using a delivery vehicle 50, and presents it to an operator such as a deliverer or a manager. Here, the presentation may be made via a paper medium such as a form, via the smartphone of the driver of the delivery vehicle 50, or via the in-vehicle device of the delivery vehicle 50.

[0014] In the delivery management system 1, the delivery management device 10 creates (generates) a delivery plan in cooperation with the backbone data center 20 and the environmental data center 30 of LPG. Thereby, based on the created delivery plan, for example, the delivery vehicle 50, which is a truck, loads an LPG cylinder, which is a storage container filled with LPG as a consumption target, at an LPG filling station 60, and delivers the loaded LPG cylinder to a delivery destination (customer) 70 corresponding to the user terminal 40.

[0015] Now, referring again to Figure 1, we will explain the general configuration of the delivery management system 1. The delivery management device 10 is a device that manages the entire delivery management system 1. The delivery management device 10 is configured to execute the delivery management process according to the embodiment. Here, the delivery management device 10 according to the embodiment is an example of a delivery management device.

[0016] The delivery management device 10 acquires contract information, meter reading data, etc., for each customer at the delivery destination from the core data center 20 via the network N and a predetermined API service. Furthermore, the delivery management device 10 acquires environmental data corresponding to the customer at the delivery destination from the environmental data center 30 via the network N and a predetermined API service. In this case, environmental data includes data representing weather, climate, temperature, etc. Here, weather refers to the state of the atmosphere at a specific time and place, such as sunny, cloudy, rainy, or snowy. Climate refers to the state of the atmosphere over a period of several days. The reason for collecting this kind of environmental data is that LPG consumption is greatly affected by the environment. For example, when the delivery destination is a typical household, if the temperature is low, such as when it is snowing, the use of heating equipment such as gas stoves will increase, the use of gas stoves for cooking hot food will increase, and the time required for heating will also be longer compared to when the temperature is high, thus increasing LPG consumption.

[0017] In the delivery management device 10, the delivery plan is created (generated) for a predetermined number of days, such as a week, and the delivery date is determined based on the predicted LPG consumption date. The delivery plan is managed by the delivery management device 10, and there may be multiple delivery vehicles 50. In that case, a delivery area is predetermined for each delivery vehicle 50. As will be described later, this delivery area is generally fixed, but may be changed as appropriate depending on the delivery situation.

[0018] In this case, the predicted LPG consumption date is calculated based on the gas volume on the delivery date or meter reading date. Therefore, there was a risk that the predicted consumption date would be significantly affected by sudden environmental changes after the delivery date or meter reading date, such as a sharp drop in temperature due to snowfall in mountainous areas, or a sudden surge in usage due to local events like cherry blossom viewing or festivals. Furthermore, on a customer basis, there were cases where the number of family members temporarily increased due to things like children living separately returning home, causing a sharp increase in LPG usage.

[0019] Furthermore, the delivery area is predetermined based on, for example, the location of the filling station 60 where LPG is filled into LPG cylinders, taking into account the number of personnel corresponding to the filling station 60, the number of delivery vehicles 50, the delivery capacity of the delivery vehicles 50, the time required for delivery, the delivery distance, etc. Delivery routes within the delivery area are also determined. Delivery routes are set, for example, as the shortest route that can be drawn in a single continuous line, but routes that cannot necessarily be drawn in a single continuous line may not be possible due to restrictions such as U-turns and avoidance of one-way streets.

[0020] Data transfer from the core data center 20 to the delivery management device 10 can be done via a network using an API, or via a CSV file, among other methods.

[0021] The core data center 20 displays to the delivery management device 10 the predicted LPG consumption date calculated based on customer contract data, meter reading data, and past LPG usage history (including seasonal fluctuations, etc.). Meter reading data is obtained either by staff visually inspecting the customer's LPG cylinders or by automated meter reading. Automated meter reading is performed wirelessly via WiFi or LPWA communication, or via wired connections such as telephone lines or cables.

[0022] Contract data includes, for each customer, the delivery address, the name of the equipment provided (LPG cylinders, hoses, regulators, supply pipes, gas meters), the number of equipment items, the basic equipment usage fee, and the equipment rental fee (so-called rental fee). Contract data also includes LPG usage fees. Usage fees include a basic fee and a usage fee calculated based on gas meter readings. Since the usage fee is charged based on the LPG used by the customer, if an LPG cylinder is replaced while unused LPG remains, the cost of the remaining gas (recovery fees, etc.) becomes a burden on the delivery company, and it also leads to an increase in the number of deliveries due to a shortened delivery cycle, and worsens the delivery company's KPIs.

[0023] The core data center 20 predicts LPG consumption based on contract data and meter reading data. For example, if there are two contracted LPG cylinders with nL (liters) each, a consumption period of 15 days (for example, consumption start date is September 1st, and today, the meter reading date, is September 15th), and nL has been consumed, then the consumption rate is n ÷ 15 (L / day), the remaining amount is nL, and the predicted consumption date is 30th, 15 days later. With automated meter reading, you can see your daily consumption and remaining amount, improving the accuracy of your consumption forecast. However, in the case of meter readings performed visually by meter readers, the accuracy of consumption forecasts deteriorates as the number of days since the meter reading date increases. Therefore, running out of gas can severely reduce delivery efficiency due to the need for emergency deliveries, etc., so delivery companies deliver new LPG containers and collect used LPG cylinders well in advance of the predicted consumption date. Unused LPG remains as residual gas in the collected LPG cylinders. While the core data center is supposed to hold the meter reading data, in the case of automated meter reading, it is also possible to configure the system to obtain the data from the server of the company operating the automated meter reading service.

[0024] The environmental data center 30 provides data to the delivery management device 10, for example, via a predetermined API service. That is, the delivery management device 10 specifies the service name, district, and customer address using an API command and receives the data as a return value.

[0025] In this case, environmental data includes weather data, pedestrian flow data, and household lifestyle information data from customers' homes. Here, weather data and human movement data are provided, for example, as data for a predetermined district, including the delivery destination. Weather data includes not only weather conditions such as sunny, rainy, and cloudy, but also data such as temperature and humidity. Generally, weather data covers a wider geographical area than pedestrian flow data. For example, weather data covers areas at the city or ward level, while pedestrian flow data covers areas at the district level, such as train station areas, park areas, shopping streets, or even street address levels. Furthermore, household lifestyle information data is at the household level, making it environmental data covering a narrower area than weather or pedestrian flow data.

[0026] Furthermore, pedestrian flow data is data related to people's movement and can be obtained, for example, from public transportation usage history and individual smartphones, as well as from GPS data, sensor and camera image analysis, mobile app location information, and event and store entry data. It may also be generated from location information of in-vehicle devices installed in vehicles.

[0027] One example of environmental data analysis is the finding that rainy weather leads to more people staying indoors, resulting in an increased LPG consumption. Similarly, a sharp drop in temperature (air temperature) is also analyzed to increase LPG consumption.

[0028] The analysis of human movement data allows for the determination of whether or not people are present in a given area (for example, a designated area including the delivery address), and is used to estimate the nighttime and daytime populations. Furthermore, temporary population increases due to events such as marathons, cherry blossom viewing parties, and festivals can also be detected using pedestrian flow data.

[0029] Furthermore, household lifestyle information refers to information about the lifestyle of the customer's home where the products are delivered, and includes at least an estimated number of family members in the household. This could also be an estimated number separated into nighttime and daytime. Household lifestyle information is typically generated by analyzing sensing data from IoT home appliances. Examples of IoT home appliances include televisions, refrigerators, rice cookers, electric kettles, air conditioners, washing machines, toilets, and water heaters (for baths and kitchens). For example, the number of people in a household can be estimated from the frequency of washing machines, toilets, and baths. Furthermore, trends in TV viewing and a sudden increase in the use of home appliances at night can suggest changes in family structure, such as a child returning home from living separately. It is also analyzed that an increase in the number of family members in a household naturally leads to an increase in LPG consumption. For instance, a child returning home might use the bath late at night or early in the morning, at times different from the family's usual bathing schedule, resulting in higher-than-usual LPG consumption. Furthermore, household lifestyle information can include not only data on individual customers but also data on establishments such as restaurants. Specifically, this could include information on the days of the week and times of the year when the establishment receives the most customers (for example, during the New Year holidays), or, in the case of establishments like oden restaurants where customer numbers fluctuate significantly depending on the season, information on seasonal changes in customer numbers.

[0030] The user terminal 40 is, for example, an information device such as the user's personal computer, smartphone, or in-vehicle device that presents the execution details of a cloud application to the user via a web application. The delivery management device 10 is typically built within a cloud server, but it may also be built within the user's information equipment, or it may be built on-premises (a configuration in which servers, network equipment, software, etc., are installed and operated within a facility managed by the user) on a server within the user's local network.

[0031] Figure 3 shows an example of the hardware configuration of the management device according to the embodiment. As shown in Figure 3, the delivery management device 10 includes an MPU 81, memory 82, HMI (Human Machine Interface) 83, external storage device 84, communication I / F (interface) 85, and bus 86.

[0032] The MPU81 is a processing unit that controls the entire delivery management device 10. The MPU81 performs the various processes described later by loading programs stored in, for example, the ROM (Read Only Memory) of the memory 82 into the RAM (Random Access Memory) and executing them.

[0033] It is also possible to use various processors such as GPUs (Graphics Processing Units) and DSPs (Digital Signal Processors), or dedicated arithmetic circuits implemented with ASICs (Application Specific Integrated Circuits) and FPGAs (Field Programmable Gate Arrays), instead of the MPU81.

[0034] Memory 82 is the main memory of the delivery management device 10 and, as described above, includes ROM for storing programs and RAM for temporarily storing data necessary for various processes performed by the MPU 81.

[0035] The HMI83 features a display 83A and an input interface 83B. HMI (Human Machine Interface) is sometimes also referred to as a User Interface. Furthermore, HMI83 may include other output interfaces, such as speakers configured to output notification sounds, warning sounds, and voice.

[0036] Display 83A is an example of an output interface for HMI83. The display 83A can be configured, for example, as a liquid crystal display (LCD) or an organic EL (Electro-Luminescence) display.

[0037] The input interface 83B can be implemented as, for example, a keyboard, mouse, or touch panel. The input interface 83B may also include other input interfaces such as buttons, dials, switches, or a microphone.

[0038] Furthermore, the display 83A and input I / F 83B can be integrated and configured as an input / output interface, or as a touch panel display.

[0039] Furthermore, HMI83 can also utilize tablet devices, smartphones, remote controllers, and other devices.

[0040] The external storage device 84 includes various storage media and semiconductor storage devices such as a Hard Disk Drive, SSD (Solid State Drive), Flash memory, and USB memory, which store various data and programs used in the delivery management device.

[0041] Communication I / F85 is an interface for sending and receiving data. For example, communication I / F25 can be a communication circuit for wired communication, a communication circuit for wireless communication, or a combination thereof, as appropriate. For wireless communication circuits, communication circuits compatible with various standards such as 3G, 4G, Wi-Fi (registered trademark), and Bluetooth (registered trademark) can be used as appropriate.

[0042] The aforementioned MPU 81, memory 82, HMI 83, external storage device 84, and communication I / F (interface) 85 are interconnected via bus 86, and the delivery management device 10 has a hardware configuration that utilizes a standard computer.

[0043] Figure 4 shows an example of the configuration of a management device according to an embodiment. The delivery management device 10 executes a program loaded into memory 82 using the MPU 81 and consists of a linkage unit 91, an acquisition unit 92, a modification unit 93, a creation unit 94, a remaining amount calculation unit 95, a proposal unit 96, and a recording unit 97.

[0044] The integration unit 91 collaborates with the core data center 20 to obtain customer contract information and predicted LPG consumption dates for deliveries. This information can be obtained via network N, or by exporting and importing text files, CSV files, etc.

[0045] The acquisition unit 92 acquires environmental data from the environmental data center 30 via the network N and a predetermined API service. In this case, the acquisition unit 92 specifies a predetermined area including the delivery destination (for example, △△ City, 〇〇 Town, etc.) and acquires environmental data as environmental information for a predetermined period (for example, one week from the current day). In this case, the environmental data includes weather data, pedestrian flow data, and lifestyle information. Weather data is at the regional level, pedestrian flow data is at the district level, and lifestyle information is at the household level, such as the customer's home.

[0046] The correction unit 93 corrects the predicted LPG consumption date for delivery customers, which is obtained by the linking unit 91, based on environmental data obtained by the acquisition unit 92, taking into account rapid temperature changes, changes in pedestrian traffic, and changes in the number of people in each household.

[0047] In this case, various correction algorithms are conceivable. One approach is to increase or decrease the percentage change in the predicted LPG consumption date based on the rate of temperature changes, population movement changes, and changes in household composition. Alternatively, one could mechanically advance or postpone the date by a predetermined number of days, such as one or two days. In any case, emergency deliveries due to gas shortages will not disappear. Furthermore, since temperature changes and population movement changes will be judged on a regional or district basis, it is considered more practical and efficient to advance or postpone the date by a predetermined number of days rather than making precise corrections to the forecast.

[0048] The creation unit 94 creates a delivery plan that includes at least the delivery date, based on the delivery information and the revised consumption forecast date. Furthermore, based on the revised consumption forecast date, if there are any delivery destinations that require a change in the delivery date, the creation unit 94 modifies the delivery route to include those destinations in the delivery plan for the modified delivery date and creates a delivery plan. Furthermore, if the delivery plan is created for each predetermined delivery area, the creation unit 94, based on the consumption forecast date corrected by the modification unit 93, will create a delivery plan by including the delivery destination in another delivery area if there is no delivery plan for the changed delivery date in a delivery area that includes a delivery destination for which the delivery date needs to be changed.

[0049] In the creation unit 94, the delivery plan is created as a plan spanning a predetermined number of days, for example, generated on a weekly basis for each day of the week. When generating the delivery plan, the plan is created based on the predicted LPG consumption date, with the condition that the LPG is delivered before it runs out, and with delivery efficiency also taken into consideration. In other words, the creation unit 94 of the delivery management device 10 will create one or more proposed delivery plans based on delivery efficiency and cost reduction information based on the distance or time required for delivery. The generated delivery plan includes the driver assigned to each of the 50 delivery vehicles, the delivery area, the 60 LPG loading stations at the starting point, the delivery destinations, and the delivery route. Furthermore, the delivery plan is created to span a predetermined number of days, and the delivery management device has a remaining quantity calculation unit 95 that calculates reduction information corresponding to the amount of reduction in the remaining quantity of the consumables in the delivery container based on the delivery plan based on the revised consumption forecast dates, and a creation unit 94 creates a delivery plan based on the delivery efficiency and reduction information based on the distance or time required for delivery. In this case, delivery efficiency refers to factors such as delivery time and distance, and the traveling salesman problem is a well-known algorithm for generating delivery routes.

[0050] The remaining amount calculation unit 95 calculates the total amount of remaining LPG consumed when LPG is delivered and collected based on the delivery plan created by the creation unit 94. In other words, the remaining amount calculation unit 95 calculates the total amount of remaining LPG consumed as suppression information corresponding to the amount of suppression of the remaining amount of the consuming material. As mentioned above, delivery plans are created based on predicted LPG consumption dates. However, not all LPG at delivery and collection destinations reaches their consumption forecast on those delivery and collection dates. From the perspective of delivery efficiency, some LPG at certain delivery destinations (customers) is collected before reaching its consumption forecast.

[0051] From a delivery efficiency standpoint, it is desirable to deliver and collect LPG cylinders for many customers in a single delivery. However, since the amount of LPG consumed in each customer's cylinder does not change in the same way, delivering and collecting many customers' LPG cylinders in a single delivery increases the amount of consumed LPG, thus reducing the efficiency of residual gas reduction. In other words, there is a trade-off between delivery efficiency and residual gas reduction efficiency. Therefore, if there are multiple delivery plan options, the total amount of residual gas (consumed amount) in the LPG cylinders delivered and collected by each plan (= reduction information) will differ.

[0052] The proposal unit 96 proposes to the user the delivery plan generated by the creation unit 94 and the total amount of remaining LPG consumption calculated by the remaining amount calculation unit 95 as restraint information. In this case, when accepting a proposal, the applicant can select the environmental information to be used (weather, pedestrian traffic, lifestyle, etc.).

[0053] By proposing multiple delivery routes and suppression information—the sum of remaining LPG consumption for each delivery route—as evaluation values, users can determine their desired delivery plan while considering the trade-offs between the two. In this case, multiple delivery plan proposals may be offered, and the user may be allowed to choose. Furthermore, since the combination of environmental data to be used, such as weather, climate, pedestrian traffic, and lifestyle, can be selected, the combination can be modified based on the experience and know-how of the administrator. For example, weather or climate environmental data may be used during seasonal changes, pedestrian traffic environmental data may be used during local festival seasons, or pedestrian traffic environmental data may be used during the year-end and New Year holidays when there is a high volume of people returning home.

[0054] The recording unit 97 records various types of information in an updatable format. Recorded information includes delivery destination information, environmental information, and delivery plan information. More specifically, delivery information includes the delivery address, the items to be delivered, and the estimated consumption date (initial and updated). Environmental information includes weather, pedestrian traffic, and lifestyle. Delivery plan information includes delivery date, delivery area, delivery vehicle, driver, delivery route, and delivery items (cargo).

[0055] Next, the operation of the embodiment will be described. Figure 5 is a flowchart showing an example of the flow of delivery management processing performed by the delivery management device according to the embodiment. First, the delivery management device 10's linkage unit 91 acquires delivery destination information, including the predicted LPG consumption date, from the core data center 20 (step S11). Here, the predicted LPG consumption date is the date on which the remaining amount of LPG in the LPG cylinder falls below a predetermined amount.

[0056] Next, the acquisition unit 92 of the delivery management device 10 acquires API information, including weather data and pedestrian flow data for the delivery area as environmental data, from the environmental data center 30 via the API service (step S12). Next, the acquisition unit 92 of the delivery management device 10 acquires environmental data, including household lifestyle information of the customer's home at the delivery destination, from the environmental data center 30 via an API service (step S13).

[0057] Next, the delivery management device 10 calculates the correction date for the predicted LPG consumption date at the delivery destination based on the acquired weather data, pedestrian flow data, and household lifestyle information (step S14). Next, the delivery management device 10 determines whether a change in the delivery date is necessary based on the correction date of the calculated LEG consumption forecast date (step S15). If the correction date differs from the forecast date by a predetermined number of days (for example, 3 days), it determines that a change in the delivery date is necessary.

[0058] In the determination in step S15, if it is determined that a change in the delivery date is not necessary (step S15; No), the creation unit 94 of the delivery management device 10 creates a delivery plan based on the LPG consumption forecast date, which has already been set (step S16). Then, the created delivery plan is presented to the operator, and the process is completed (step S17).

[0059] If, in the determination in step S15, a change in the delivery date is necessary (step S15; Yes), the creation unit 94 of the delivery management device 10 creates a delivery plan based on the changed LPG consumption forecast date (step S18). Then, the created delivery plan is presented to the operator, and the process is completed (step S17).

[0060] Next, the operation of the embodiment will be described in more detail. Figure 6 is an explanatory diagram of the geographical relationship between the filling station and the delivery destination (customer) within the area managed by the delivery management device 10, as well as the delivery area and delivery route. Figures 6(A), (B), and (C) show the managed area AR. Within the managed area AR, there are two filling stations S1 and S2, and six delivery destinations A through F.

[0061] Figure 7 shows an example of delivery destination management data corresponding to Figure 6. The managed area AR is divided into two delivery areas, AX and BX. As shown in Figures 6(B) and 6(C), delivery area AX is the area where LPG cylinders filled at filling station S1 are delivered. Delivery days are Monday, Wednesday, Friday, and Saturday mornings. The delivery vehicle is M1, and the delivery destinations (customers) it is responsible for are destinations A, B, E, and F.

[0062] In this case, as shown in Figure 6(C), the LPG filled at the filling station S1 will, in principle, be delivered by the delivery vehicle M1 in the order of destination A → destination B → destination E → destination F.

[0063] As shown in Figures 6(B) and 6(C), delivery area BX is the area where LPG cylinders filled at filling station S2 are delivered. Delivery days are Tuesday, Thursday, and Saturday afternoons, and the delivery vehicle is M2. The delivery destinations (customers) it is responsible for are destinations C and D.

[0064] In this case, as shown in Figure 6(C), the LPG filled at the filling station S2 will, in principle, be delivered by the delivery vehicle M2 in the order of destination C → destination D.

[0065] In the above explanation, the delivery days and delivery order are determined by the fact that deliveries are made when necessary, and deliveries are not made to all destinations on a given delivery day. For example, in delivery area AX, if only destinations B and E require delivery on Wednesday, then LPG will be filled at filling station S1 and delivered only to destinations B and E by delivery vehicle M1.

[0066] Here, we will explain LPG remaining quantity forecasting and its correction. Figure 8 is an explanatory diagram of LPG remaining quantity forecasting and revision of the remaining quantity forecasting. In Figure 8, the vertical axis represents the remaining amount of LPG, and the horizontal axis represents the number of days elapsed since the delivery date. Furthermore, the delivery destination (customer) A is a restaurant, and it is assumed that the number of customers increases when the temperature drops.

[0067] Figure 8(A) shows, for example, a prediction of the remaining LPG quantity at the time of delivery for delivery destination (customer) A. It is predicted that on the fourth day, the remaining LPG quantity will reach a predetermined gas level TH, and that delivery of an LPG cylinder will be necessary.

[0068] Figure 8(B) shows an LPG remaining amount forecast for delivery destination (customer) A, for example, when the temperature drops or when a festival or other event is held around the store, causing a sudden increase in foot traffic. Compared to the forecast in Figure 8(A), a revised forecast was made on the 3rd day, one day prior, indicating that the LPG remaining amount reached a predetermined gas remaining amount TH, and that LPG cylinder delivery was necessary.

[0069] Figure 9 is a flowchart illustrating the process of creating a delivery plan based on whether or not a route change involves a change in service area. In the following explanation, we will use the example of the situation where an emergency delivery to destination (customer) F is required, even though no delivery to destination (customer) F is scheduled (foreseen) in Figure 6.

[0070] The delivery management device 10 determines whether or not a route change is necessary within the same area (step S21). If the determination in step S21 is that the route change is within the same delivery area (step S21; Yes), the route change is carried out without any restrictions (step S25), and the creation unit 94 of the delivery management device 10 creates a delivery plan (step S24).

[0071] Figure 10 is an explanatory diagram for route changes within the same delivery area. In this case, the creation unit 94 of the delivery management device 10 will create the delivery plan by modifying the delivery route to include the delivery destination in the delivery plan for the revised delivery date, based on the consumption forecast date modified by the modification unit 93, if a delivery destination requires a change in the delivery date. Figure 10(A) is an explanatory diagram illustrating a scenario where, in the delivery area AX, an emergency delivery to delivery destination F is required, even though a delivery plan has already been established to deliver LPG cylinders filled at filling station S1 to delivery destinations A, B, and E in the order of delivery destination A → delivery destination B → delivery destination E.

[0072] In this case, either the delivery vehicle M1 is unable to carry the urgent delivery to destination F due to its limited load capacity, or an urgent delivery to destination F becomes necessary while the vehicle is en route to destinations A, B, and E.

[0073] In this case, the suggestion unit 96 of the delivery management device 10 displays a message to the delivery destination (customer) F indicating that urgent delivery is required, as shown in Figure 10(A). Furthermore, as shown in Figure 10(B), the delivery plan generates a plan in which deliveries are completed in the order of destination A → destination B → destination E, then the system returns to filling station S1 and delivers to destination F. The operator is then asked whether it is acceptable to proceed with this route change.

[0074] If the determination in step S21 is not a change of route within the same delivery area (step S21; No), the creation unit 94 of the delivery management device 10 determines whether or not a change of delivery area is necessary (step S22).

[0075] In the decision made in step S22, if the delivery area is to be changed (step S22; Yes), the delivery area is changed, the delivery destination is incorporated into the delivery area, and the route is modified (step S26), and the creation unit 94 of the delivery management device 10 creates a delivery plan (step S24).

[0076] Figure 11 is an explanatory diagram for route changes that involve changes in the delivery area. In this case, the delivery plan is created for each predetermined delivery area, and the creation unit 94 of the delivery management device 10, based on the consumption forecast date corrected by the modification unit 93, will create the delivery plan by including the delivery destination in another delivery area if there is no delivery plan for the changed delivery date in a delivery area that includes the delivery destination for which the delivery date needs to be changed. Figure 11(A) is an explanatory diagram illustrating a situation where an urgent delivery to destination F is required on a day when no deliveries are made in delivery area AX. In this case, it is assumed that there is a delivery plan in which delivery vehicle M2 will deliver to delivery area BX.

[0077] In this case, the creation unit 94 of the delivery management device 10 displays, as shown in Figure 11(A), that an urgent delivery is required to the delivery destination (customer) F, but that there is no delivery plan for the delivery area AX corresponding to the delivery destination (customer) F on this day. Furthermore, the delivery management device 10 will display a message to the operator asking whether it is acceptable to change the area.

[0078] Then, if the operator gives instructions that it is acceptable to handle the situation by changing the delivery area, the creation unit 94 of the delivery management device 10 changes the delivery destination (customer) F to temporarily include it in the delivery area BX, as shown in Figure 11(B), and asks the operator whether it is acceptable to handle the situation by changing the delivery area.

[0079] Then, once the operator gives instructions that it is acceptable to proceed with the delivery in that delivery area, as shown in Figure 11(C), a delivery plan is generated in which deliveries are completed in the order of destination A → destination B → destination E, then the system returns to filling station S1 and delivers to destination F. The operator is then asked whether it is acceptable to proceed with this route change.

[0080] Figure 12 is an explanatory diagram of an example of a delivery plan presentation screen that includes inquiries to the operator when the delivery area is changed. The delivery plan presentation screen GD includes a delivery area information display area AR1, a delivery plan display area AR2, a usage environment information selection status display area AR3, a remaining gas amount prediction display area AR4 for the refurbished container at the selected delivery destination, and a delivery plan approval instruction area AR5.

[0081] In this embodiment, the delivery area information display area AR1 displays the delivery settings (delivery days, delivery vehicles, and filling stations) for delivery areas AX and BX. The delivery plan display area AR2 shows the delivery area, the filling station corresponding to the delivery area, and the delivery route.

[0082] The AR3 display area for the selected environment information shows the environment information selected for use in creating the delivery plan. The remaining gas amount prediction display area AR4 displays the statistically predicted remaining gas amount.

[0083] The delivery plan approval instruction area AR5 is where the operator can give instructions to approve the delivery plan displayed in the delivery plan display area AR2 or to display alternative delivery plans, after confirming the contents of the delivery area information display area AR1, the delivery plan display area AR2, the usage environment information selection status display area AR3, and the remaining gas amount prediction display area AR4 of the refurbished container at the selected delivery destination.

[0084] In the example shown in Figure 12, clicking the "Yes" button constitutes approval, and the delivery management device 10 makes arrangements (notifications, etc.) to carry out the actual delivery.

[0085] If the operator gives instructions that it is acceptable to proceed with the delivery in that delivery area, the system will generate a delivery plan in which deliveries are completed in the order of destination C → destination D, then the system will return to filling station S2 and deliver to destination F, and will then ask the operator whether it is acceptable to proceed with this route change.

[0086] If, in the decision made in step S22, the delivery area is not changed (step S22; No), then delivery will be made using an emergency delivery service to the delivery destination (step S23), and the creation unit 94 of the delivery management device 10 will create a delivery plan (step S24).

[0087] Figure 13 is an explanatory diagram for using extra services. Figure 13(A) is an explanatory diagram illustrating a situation where an urgent delivery to destination F is required on a day when no deliveries are made in delivery area AX. In this case, the creation unit 94 of the delivery management device 10 displays, as shown in Figure 13(A), that an urgent delivery is required to the delivery destination (customer) F, but that there is no delivery plan for the delivery area AX corresponding to the delivery destination (customer) F on this day. Furthermore, the delivery management device 10 will display a delivery plan using an extra delivery service on its display and ask the operator whether or not it is acceptable to use the extra delivery service. Specifically, as shown in Figure 13(B), a delivery plan is presented to the operator for delivery from filling station S2 to destination (customer) F via an unscheduled delivery, and they are asked if it is acceptable to handle the delivery via an unscheduled delivery.

[0088] If the operator gives instructions that it is acceptable to use an extra delivery, the delivery plan will be to deliver from filling station S2 to delivery destination F.

[0089] As described above, according to this embodiment, delivery is made in such a way that the remaining quantity of the delivered product does not run out due to use, thus ensuring continuous use of the product at the delivery destination. Furthermore, when planning the delivery route, a plan is made that maintains delivery efficiency as much as possible, thereby improving delivery efficiency.

[0090] In the above explanation, the configuration was such that consumption forecasting is performed by the core data center 20, but it is also possible to configure the system so that consumption forecasting is performed by the delivery management device 10. In the above explanation, LPG stored in an LPG cylinder was used as an example of the consumable substance, but the same principles can be applied to consumable substances such as liquid nitrogen, carbon dioxide, and beer, which are contained in delivery containers such as cylinders and tanks.

[0091] While embodiments of this disclosure have been described above, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel 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 novel embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0092] Furthermore, the effects described in the embodiments of this specification are merely illustrative and not limiting, and other effects may also occur. [Explanation of Symbols]

[0093] 1. Delivery Management System 10 Delivery management device 20 Core Data Centers 30 Environmental Data Centers 40 User terminals 50 Delivery Vehicles 60 Filling Stations 81 MPU 82 memory 83 HMI 83A Display 83B Input Interface 84 External storage device 86 Bus 91 Liaison Department 92 Acquisition Department 93 Correction section 94 Creation Section 95 Remaining amount calculation unit 96 Proposal Department 97 Records Department A~F Delivery destination AR Management Area AR1 Delivery Area Information Display Area AR2 Delivery Plan Display Area AR3 Usage Environment Information Selection Status Display Area AR4 Remaining gas amount prediction display area AR5 Delivery Plan Approval Instruction Area AX, BX delivery area GD Delivery Plan Presentation Screen M1, M2 delivery vehicles N Network S1, S2 Filling Station

Claims

1. A delivery management device that creates a delivery plan for delivering delivery containers containing consumables to one or more delivery destinations based on delivery information and linked information, The aforementioned delivery information includes the delivery address, the delivery container, and the delivery date. The aforementioned linked information includes the predicted consumption date of the consumables in the delivered containers for each delivery destination, An environmental information acquisition unit that acquires environmental information, including at least weather or weather-related information, from an external system for the aforementioned delivery destination, A correction unit that corrects the predicted consumption date based on the aforementioned environmental information, A creation unit creates a delivery plan that includes at least a delivery date, based on the aforementioned delivery information and the revised consumption forecast date. A delivery management device equipped with this device.

2. The system includes a linking unit that acquires linked information, including the aforementioned consumption forecast date, from an external system. The delivery management device according to claim 1.

3. The creation unit creates the delivery plan with the delivery route changed based on the revised consumption forecast date. The delivery management device according to claim 1.

4. The creation unit, based on the revised consumption forecast date, creates the delivery plan by modifying the delivery route to include the delivery destination in the delivery plan for the revised delivery date if a delivery destination requires a change in the delivery date. The delivery management device according to claim 1.

5. The aforementioned delivery plan is created for each designated delivery area. The creation unit, based on the revised consumption forecast date, creates the delivery plan by including the delivery destination in another delivery area if there is no delivery plan for the changed delivery date in the delivery area that includes the delivery destination for which the delivery date needs to be changed. The delivery management device according to claim 1.

6. The environmental information acquisition unit selects a predetermined area including the delivery destination and acquires environmental information for a predetermined period. The delivery management device according to claim 1.

7. The environmental information acquisition unit acquires the environmental information via an API (Application Programming Interface) service. The delivery management device according to claim 1.

8. The aforementioned delivery plan was created to cover a predetermined number of days. The delivery management device has a calculation unit that calculates suppression information corresponding to the amount of suppression of the remaining amount of the object to be consumed in the delivery container based on a delivery plan based on a revised consumption forecast date, The creation unit creates a delivery plan based on the delivery efficiency, which is determined by the distance or time required for delivery, and the aforementioned reduction information. The delivery management device according to claim 1.

9. Based on the aforementioned suppression information, the delivery area of ​​the delivery plan is changed. The delivery management device according to claim 8.

10. The delivery management device has a proposal unit that proposes multiple delivery plans created using the suppression information as evaluation values. The delivery management device according to claim 8.

11. The modification unit modifies the predicted consumption date for each delivery destination based on lifestyle information, including at least the number of people at the delivery destination. The delivery management device according to claim 1.

12. The modification unit analyzes information obtained from IoT home appliances to acquire the lifestyle information. The delivery management device according to claim 11.

13. The aforementioned consumption target is one of the following: LPG, liquid nitrogen, carbon dioxide, or beer. The delivery management device according to claim 1.

14. A delivery management method that creates a delivery plan for delivering delivery containers containing consumables to one or more delivery destinations based on delivery information and linked information, The aforementioned delivery information includes the delivery address, the delivery container, and the delivery date. The aforementioned linked information includes the predicted consumption date of the consumables in the delivered containers for each delivery destination, The process of obtaining environmental information, including at least weather or weather-related information, from an external system for the aforementioned delivery destination, The process of correcting the consumption forecast date based on the aforementioned environmental information, The process of creating a delivery plan that includes at least the delivery date, based on the aforementioned delivery information and the revised consumption forecast date. Delivery management methods.

Images