JP7649577B2 - Delivery management system and delivery management method - Google Patents

Description

The present invention relates to a delivery management system and a delivery management method.

Traditionally, portable gas fuels such as LP gas have been filled into gas containers and supplied to users. In particular, in areas where city gas is not widely available, such as Southeast Asian countries, LP gas is essential to users' lives and is a valuable heat source.

In these areas, LP gas is an essential fuel for daily life, used for cooking in homes and restaurants. For this reason, various proposals have been made for a system in which gas cylinders filled with LP gas are delivered to homes, restaurants, etc. before LP gas runs out.

Patent Document 1 discloses a technique for creating a delivery list with the next day as the delivery date based on predicted remaining amount data α days (for example, 2 days) after the scheduled delivery date, rather than predicted remaining amount data 1 day after the scheduled delivery date. This brings the delivery date α-1 days earlier, but eliminates the need for last-minute adjustments to the delivery list.

On the other hand, if the delivery timing is brought forward to avoid running out of gas, the delivery frequency will increase. Therefore, from the perspective of the delivery person, increasing the delivery frequency increases the possibility of collecting gas bottles with a large amount of gas remaining, and delivery costs become more expensive as the number of deliveries increases and the delivery cycle shortens. Furthermore, from the perspective of the user, there may be cases where users are reluctant to replace gas bottles that still have gas remaining. Therefore, Patent Document 2 discloses a technology that predicts the day when gas will run out, calculates the scheduled delivery date, and creates a delivery list based on this, in order to increase delivery efficiency without running out of gas. All of the above prior art technologies are based on the premise that a gas meter is installed at the user's base and that a meter reader reads the meter.

However, because gas meters are relatively expensive, most gas cylinders used in countries in Southeast Asia and other regions where city gas is not widespread do not have gas meters. As a result, in these countries, when users run out of gas, they call to request the delivery of a cylinder filled with LP gas. Because LP gas is essential for life, such requests after running out of gas are highly urgent. If delivery is delayed, there is a risk that users will switch to other providers.

Furthermore, in areas where city gas is not widely available, such as Vietnam, gas cylinders are often installed indoors, and in such cases, it is necessary to enter the house to replace the gas cylinder. Since entry into the house requires the presence or consent of the user, it is necessary to coordinate with the user in advance to decide the date for replacing the gas cylinder (delivery date).

Therefore, in Patent Document 3, the gas pressure of a gas container in use or the weight of the gas container is measured at the user's facility, and the measurement data is automatically sent to a management system periodically or under specified conditions. The predicted replacement date for the gas container is calculated from the gas consumption and remaining gas amount, and the scheduled delivery date for the gas container is set based on the predicted replacement date.

Patent No. 5756157 Patent No. 5802225 WO 2020/115850

Patent Document 3 makes it possible to obtain the amount of gas consumed and the amount of remaining gas at a user's location for gas containers that do not have a gas meter, and to deliver the gas containers efficiently. On the other hand, in the conventional technology, the user locations to which delivery is targeted are selected from the population of contracted users according to the amount of remaining gas fuel.

As a result, a huge number of customer locations may be set as delivery destinations that must be visited in a single day, putting a strain on the delivery person's work hours. Or, two customer locations that are far apart may be set as delivery destinations, increasing travel costs.

From another perspective, there is a need for a system that can efficiently dispatch deliveries when an emergency occurs at a user's location. Because emergencies such as gas leaks occur suddenly, it is necessary not only to streamline delivery and secure the delivery person's working time, but also for the delivery person to be located close to the target user's location. Therefore, if there is a geographical bias in the user locations set as delivery destinations, it will take time to dispatch to the target user location.

In view of the above, the present invention aims to provide a new technology for efficiently delivering gas fuel by making it possible to control delivery areas and delivery quantities.

In order to achieve the above object, the present invention provides a delivery management system for managing the delivery of a gas container to a user who uses a portable gas fuel sealed in the gas container, the delivery management system comprising:
The delivery management system includes:
storing the delivery of the gas container to the user facility in a database in association with the user and the delivery completion date;
Acquire the amount of gas used or the amount of gas used after use in the user facility,
The amount of the refund to the user is calculated based on the amount used or the amount after use.

The present invention also provides a method for managing the delivery of a gas container to a user who uses a portable gas fuel sealed in the gas container, the method comprising the steps of:
The delivery management system includes:
storing the delivery of the gas bottle to the customer facility in a database in association with the customer and the delivery completion date;
A step of acquiring a used amount or a used amount of a gas container used in the user facility;
A step of calculating an amount of refund to the user based on the amount of use or the amount after use is executed.

By adopting such a configuration, the amount of refund to the user can be calculated according to the remaining amount of gas fuel in the collected gas container, and the user's reluctance to replace the gas container even if there is remaining gas can be alleviated. In addition, in the past, delivery was required when the gas container had no remaining gas or when there was almost no remaining gas, but by adopting such a configuration, the timing of replacement due to the remaining amount of gas in the gas container is no longer restricted. Therefore, the degree of freedom in determining the delivery schedule is increased, and a more efficient delivery plan can be created. In addition, for example, the bias in the delivery destination area may be eliminated, which improves the quality of response in an emergency. Furthermore, the frequency of occurrence of high-cost transportation routes is alleviated, and financial and human costs are reduced. From the above, it is possible to provide an environment where users do not run out of gas, and to provide a new technology for efficiently delivering gas fuel through improved safety and understanding of gas usage by gas providers.

In a preferred embodiment of the present invention, the delivery management system includes a measuring device for measuring the amount of use or the amount of use after use, an information processing device, and a deliverer terminal device used by a deliverer,
The measuring device identification information is stored in the database in association with the user identification information;
The measuring device or the deliverer terminal device transmits to the information processing device, the deliverer identification information of the deliverer who replaces the gas container and the measuring device identification information associated with each other,
Based on the received measuring device identification information and deliverer identification information, the information processing device stores the delivery completion date for the target user equipment in the database in association with the user.

This configuration makes it possible to manage the deliverers who made the deliveries and the history of their work.

In a preferred embodiment of the present invention, the measuring device is a weight measuring device capable of measuring a weight as the amount after use,
The delivery management system acquires the weight of the gas container used at the user's facility, and calculates the amount of refund based on the weight, as well as the weight of the gas container alone or the weight of the gas filled in the gas container.

In a preferred embodiment of the present invention, the measurement device is a flow rate measurement device capable of measuring a flow rate as the usage amount,
The delivery management system acquires the flow rate of the gas container used at the user's facility and calculates the refund amount based on the flow rate. The flow rate measuring device shown here may be a device that measures pressure measurement data, and in this case, the information processing device or the flow rate measuring device may calculate the flow rate using a formula based on the pressure measurement data.

With this configuration, the amount of refund can be calculated using a weight sensor, flow sensor, or pressure sensor.

In a preferred embodiment of the present invention, the delivery management system includes a gas leak sensor that is disposed in a user facility and is capable of communicating with the information processing device,
The database stores user information including the location of the user equipment and associated with the user identification information;
The deliverer terminal device transmits its own location to the information processing device,
When the gas leak sensor detects an abnormality, it notifies the information processing device.
The information processing device that has received the notification determines a deliverer to be requested to rush to the site based on the location of the deliverer terminal device.

In a preferred embodiment of the present invention, the delivery management system includes an operator terminal device capable of communicating with the information processing device,
The database stores the telephone number of the deliverer terminal device as the deliverer contact information,
When the information processing device has determined the delivery company to be requested, it transmits to the operator terminal device the location or user identification information of the user equipment in which the gas leak sensor that issued the alert is located, as well as the telephone number or delivery company identification information of the delivery company to be requested.

In a preferred embodiment of the present invention, the database stores a destination for transmitting information to the deliverer terminal device as the deliverer contact information,
When the information processing device has determined the delivery company to be requested, it transmits to the destination the location of the user equipment in which the gas leak sensor that issued the alert is located or user identification information.

In a preferred embodiment of the present invention, the user is stored in a database in association with a delivery company that has made a contract for delivery of the gas container,
The information processing device determines the requested deliverer from among deliverers including those that have no contractual relationship with the user of the express destination.

This configuration allows for efficient dispatch to the scene in the event of an emergency.

In a preferred embodiment of the present invention, the database stores, as the user contact information, a destination or a telephone number for transmitting information to the user terminal device,
The information processing device that has received the notification transmits the user contact information to an operator terminal device, or notifies the user terminal device using the user contact information.

This configuration allows for efficient notification of users in the event of an emergency.

In a preferred embodiment of the present invention, the information processing device is configured to be able to communicate with a user terminal device,
Set the user in a delivery candidate list based on the past delivery completion date stored in association with the user;
presenting a plurality of candidate dates and times to the user terminal device of the user set as the delivery candidate, and accepting a desired delivery date from the user terminal device;
The user is added to a delivery schedule list for delivery on the desired delivery date.

This configuration makes it possible to efficiently obtain the user's consent and presence when replacing a gas container.

In a preferred embodiment of the present invention, a delivery area is set in the database in association with each user,
The information processing device presents a plurality of dates and a plurality of time slots as the plurality of candidate dates and times to a user terminal device of the user who has been added to the delivery candidate list;
accepts a combination of the date and the time zone as the desired delivery date from the user terminal device;
The user is added to a delivery schedule list based on the delivery area associated with the user and the accepted desired delivery date.

This configuration allows you to add items to the list according to area, making delivery more efficient.

In a preferred embodiment of the present invention, a measurement result of the gas container is received from the measurement device,
Among the users added to the delivery candidate list, those users who have a predetermined amount of the gas container remaining are deleted from the delivery candidate list.

This configuration reduces the frequency with which items are added to the list, and reduces the number of deliveries by the courier in the medium to long term.

The present invention provides a new technology for efficiently delivering gas fuel by making it possible to control delivery areas and delivery quantities.

FIG. 1 is a block diagram showing a configuration of a system according to an embodiment. FIG. 2 is a diagram showing a hardware configuration according to an embodiment. FIG. 2 is a schematic diagram of a user facility according to an embodiment. FIG. 1 is a block diagram of a weight measuring device according to an embodiment. FIG. 2 is a schematic diagram of a user facility according to an embodiment. FIG. 1 is a block diagram of a weight measuring device according to an embodiment. 5 is a flowchart for replacing a gas container according to an embodiment. 13 is a flowchart for creating a distribution list according to one embodiment. 13 is a flowchart for creating a distribution list according to one embodiment. FIG. 4 is a data structure diagram relating to a delivery candidate list and a delivery list according to an embodiment. 11 is a process flowchart relating to the creation of emergency information according to an embodiment. 11 is a flowchart for requesting a deliverer to rush to the site according to an embodiment. 4 illustrates an example of a screen display on an operator terminal device according to an embodiment.

Below, with reference to the attached drawings, a delivery management system for continuously supplying LP gas to user facilities that use portable gas fuel such as LP gas (hereinafter referred to as "LP gas"). The drawings show a preferred embodiment. However, the present invention can be embodied in many different forms and is not limited to the embodiment described in this specification.

For example, the configuration, operation, etc. of a delivery management system will be described in this embodiment, but similar effects can be achieved by the executed method, device, computer program, etc. The program in this embodiment may be provided as a non-transient computer-readable recording medium, or may be provided downloadable from an external server, or the program may be started on an external computer to realize its functions on a client terminal (so-called cloud computing).

In addition, in this embodiment, a "unit" may include, for example, a combination of hardware resources implemented by a circuit in the broad sense and software information processing that can be specifically realized by these hardware resources. In this embodiment, "information" is represented by, for example, the physical value of a signal value representing a voltage or current, the high or low of a signal value as a binary bit collection consisting of 0 or 1, or a quantum superposition (so-called quantum bit), and communication and calculations can be performed on a circuit in the broad sense.

In the broad sense, a circuit is a circuit that is realized by appropriately combining a circuit, circuitry, processor, memory, etc. In other words, it includes a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), etc.

<System Configuration>
1 is a block diagram showing the configuration of a system according to an embodiment of the present invention. As shown in FIG 1, a delivery management system 0 includes a plurality of user bases 1, a management system 2, a plurality of delivery bases 3, and a network NW.

The user base 1 is a facility of a user (demanding person) who uses LP gas as fuel, such as a house or a store. The user base 1 is equipped with a measuring device 11 and a communication device 12. A user belonging to each user base uses a user terminal device 10. The measuring device 11 connects to the network NW via a communication device 12 such as a Wi-Fi router. The user terminal device 10 connects to the network NW via the communication device 12 or a mobile network, and can make calls via a public telephone network. Even if a user is an organization or group, each user base 1 is treated as one user. In some cases, a repeater may be installed between the measuring device 11 and the communication device 12. The measuring device 11 transmits the measurement data to the communication device 12, and the communication device 12 transmits the measurement data via the network NW to the management system 2. The measuring device 11 may also transmit the measurement data to the user terminal device 10, and transmit the measurement data directly to the network NW and the management system 2 via the user terminal device 10.

The management system 2 arranges for the delivery of gas cylinders filled with LP gas to continuously provide LP gas, etc. The management system 2 includes an information processing device 20 and one or more operator terminal devices 200 connected to the information processing device 20.

The distribution base 3 is a base that distributes gas bottles to the user base 1 based on instructions from the management system 2. One or more distributors belonging to each distribution base 3 each use a distributor terminal device 30. Here, distribution base 3a and distribution base 3b are, for example, operated by different organizations, and distribute gas bottles to the user base 1 with which each distribution base has a contract. In the illustrated example, distribution base 3a includes a distributor that uses distributor terminal device 3a1, a distributor that uses distributor terminal device 3a2, ... and a distributor that uses distributor terminal device 3an. The distributor terminal device 30 is a terminal carried by each distributor, and is connected to the network NW via a mobile network or a communication device (not shown).

The delivery management system 0 in this embodiment centrally manages delivery bases 3 operated by different organizations, but it may also be directed to a single organization. Each delivery base 3 may also be equipped with an information processing device connected to the management system 2 via the network NW. At this time, for example, the information processing device may be configured to appropriately obtain instructions from the management system 2 or delivery lists and delivery route information for each delivery area, and assign these to the delivery terminal device 30 of the delivery person belonging to the delivery base 3. The delivery base 3 may also be a base operated by a provider of LP gas, etc., or a delivery company with a contract.

The network NW includes, for example, the Internet, a LAN (Local Area Network), and a public telephone network, but there is no limit to the type of communication protocol, and there is no limit to the type or size of the network. The network NW is also considered to be a concept that includes wireless communication stations and relay stations.

The information processing device 20 operates as a server, and the user terminal device 10 and the deliverer terminal device 30 are mobile phones, smartphones, etc. operated by the user and the deliverer. The information processing device 20 and the user terminal device 10, as well as the information processing device 20 and the deliverer terminal device 30, are configured to be able to communicate via the network NW. A general-purpose server computer, personal computer, etc. can be used as the information processing device 20. It is also possible to configure the information processing device 20 using multiple computers.

<Hardware Configuration>
2A is a diagram showing an example of a hardware configuration of the information processing device 20. The information processing device 20 includes a communication unit 21, a storage unit 22, and a control unit 23 as the hardware configuration.

The communication unit 21 controls communication with the network NW, and performs input necessary to operate the information processing device 20 and outputs related to the operation results.

The storage unit 22 is a HDD, ROM, RAM, etc., and stores the delivery management program of the present invention and data used when the control unit 23 executes processing based on the program.

The control unit 23 includes one or more processors such as a CPU, and controls the overall operation and processing of the information processing device 20 by executing the delivery management program of the present invention, the OS, and other applications. The control unit 23 executes processing based on the delivery management program stored in the memory unit 22, thereby realizing the functional configuration described below.

The user terminal device 10, the delivery company terminal device 30, and the operator terminal device 200 are collectively referred to as the terminal device 90. As shown in FIG. 2(b), the terminal device 90 has, as its hardware configuration, a communication unit 91, a memory unit 92, a control unit 93, an input unit 94, and an output unit 95.

The communication unit 91 of the terminal device 90 controls communication with the network. The storage unit 92 of the terminal device 90 is a HDD, ROM, RAM, etc., and stores programs and data used when the control unit 93 executes processing based on the programs. The control unit 93 of the terminal device 90 includes one or more processors such as a CPU, and controls the overall operational processing of the terminal device 90. The input unit 94 of the terminal device 90 is a touch panel, mouse, keyboard, etc., and inputs operation requests from the user to the control unit 93. The output unit 95 of the terminal device 90 is a display, etc., and displays the results of processing by the control unit 93, etc.

<Functional configuration>
2A, the information processing device 20 includes, as its functional configuration, a reception unit 231, a delivery management unit 232, a prediction unit 233, a remaining amount management unit 234, a rebate processing unit 235, an emergency response request unit 236, and a database. This is a specific implementation of information processing by software using hardware (such as a control unit).

<User base>
3 to 6, examples of user equipment installed at the user base 1 will be shown.

<Weight measuring device 11a>
A user equipment for measuring weight will be described with reference to FIG. 3. In the user equipment shown in FIG. 3, the consumption of LP gas at the user base 1 is measured by a weighing scale (weight measuring unit 112) provided in the measuring device 11 (weight measuring device 11a). In the user equipment, a gas bottle GB is placed on the weight measuring device 11a that can measure weight and transmit it as measurement data. In the illustrated example, one gas bottle GB is set, but two or more gas bottles may be installed. In that case, it is possible to measure the total weight of multiple cylinders at once and transmit the total weight data, but in order to accurately manage the remaining gas amount, it is preferable to measure the weight of each gas bottle one by one and transmit the measurement data of each gas bottle. The weight measuring device 11a further includes a gas leak sensor 14 and is configured to be able to communicate with a communication device 12 connected to a network NW. LP gas is supplied to a consumer device such as a gas stove via a regulator 15 and a gas circuit breaker 13.

Figure 4 is a functional block diagram of the weight measuring device 11a. The weight measuring unit 112 measures the weight of the gas bottle GB and passes the measurement data to the control unit 110. The control unit 110 transmits the measurement data to the management system 2 via the communication unit 111. At this time, the control unit 110 transmits the type of measurement data, the measurement date and time, and the measuring device identification information recorded in a memory (not shown) to the management system 2 in association with the measurement data. The measuring device identification information is used as information for identifying the user base 1. Instead of the measuring device identification information, user identification information may be stored in the memory of the measuring device 11 and transmitted to the management system 2 in association with the measurement data. This identification information is displayed on the exterior of the measuring device 11 as a character string or code, and is configured to be available to the delivery person.

LP gas supplied from the gas container GB is supplied to the consumer device via a gas pressure regulator (regulator 15). Because the gas pressure in the gas container is high, it is usually reduced to a predetermined pressure by the regulator 15. A gas pressure gauge 16 may be provided inside the regulator 15 or on the supply path. The gas pressure gauge 16 measures the gas pressure in the gas container 14a. The gas pressure gauge 16 passes the gas pressure measurement data to the control unit 110, and the control unit 110 transmits the measurement data to the management system 2 via the communication unit 111. At this time, as with the transmission of the measurement data, information for identifying the user is added.

When the gas leak sensor 14 detects a gas leak, it transmits a request to the control unit 110 to drive the gas circuit breaker 13, and the control unit 110 drives the gas circuit breaker 13 to cut off the gas. In the illustrated example, the gas leak sensor 14 is connected to the control unit 110, but it may be configured to notify a gas circuit breaker control unit (not shown), which then drives the gas circuit breaker 13. The gas leak sensor 14 may be incorporated into the communication device 12. Furthermore, when the gas leak sensor 14 detects a gas leak, the control unit 110 or the gas circuit breaker control unit may be configured to notify the management system 2. In addition, the control unit 110 or the gas circuit breaker control unit (not shown) may receive a circuit breaker request signal from the management system 2 and drive the gas circuit breaker 13. The circuit breaker request signal may also be transmitted when a signal different from the normal signal of the weight measuring device 11a or the gas pressure measuring device 16 is received and gas is determined to be leaking.

The timing of transmitting the measurement data can be determined by a combination of conditions such as when the weight (remaining amount) falls below a predetermined value or when a predetermined time has passed. The timing of transmitting the measurement data can be controlled by the control unit 110 and the control program. The measurement data is controlled so that it is transmitted when the above-mentioned predetermined conditions are met. The control unit 110 is also configured to be able to receive a request from the management system 2 and transmit the current measurement data.

The measuring device 11 may transmit a replacement signal to the management system 2 when the measurement data falls below a predetermined threshold value indicating that the remaining amount of gas in the gas container GB is low. Here, in the case where the user facility has one gas container GB, it is preferable to set the threshold value to a state where there is a small amount of gas remaining (for example, a state where about six days' worth of gas remains calculated from the average consumption amount), and in the case of a user base 1 equipped with two or more gas containers, it is preferable to set the threshold value to the measurement data value at which the remaining amount of gas in one of the gas containers GB is considered to be zero. The threshold value may be set in advance for each measuring device 11, or may be transmitted to the measuring device 11 based on the gas container data when the gas container GB is installed.

<Flow rate measuring device 11b>
Next, a user equipment that measures the flow rate and transmits the measurement data will be described. In the user equipment shown in FIG. 5, the consumption of LP gas at the user base 1 is measured by a flowmeter (flow rate measurement unit 113) provided in the flow rate measurement device 11b. LP gas is supplied to a consumer device such as a gas stove via the flow rate measurement device 11b, a gas pressure measurement device 16, a regulator 15, and a gas circuit breaker 13. In addition, a gas leak sensor 14 is provided at the user base 1. In addition, the flow rate measurement device 11b is configured to be able to communicate with a communication device 12 connected to the network NW. The flow rate measurement device 11b may measure pressure with the gas pressure measurement device 16 instead of the flow rate measurement unit 113, and calculate the gas flow rate by calculation. This calculation may be performed by the control unit 110 of the flow rate measurement device 11b, or may be performed by the information processing device 20 or another processing device constituting the management system 2.

Figure 6 is a functional block diagram of the flow meter device 11b. The flow meter 113 measures the gas flow rate and records the measurement results in a memory (not shown). The total flow rate is then passed to the control unit 110 as measurement data. The control unit 110 transmits the measurement data to the management system 2 via the communication unit 111. At this time, the control unit 110 associates the measurement data with information for identifying the user recorded in a memory (not shown) and the measurement date and time, and transmits the measurement data to the management system 2. The timing of transmitting the measurement data can be determined by a combination of conditions such as when the total flow rate (consumption amount) reaches or exceeds a predetermined value, or when a predetermined time has passed.

As with the user equipment shown in Figures 3 and 4, a gas pressure gauge 16 may be provided inside the regulator 15 or on the supply path. The gas pressure gauge 16 passes gas pressure measurement data to the control unit 110, and the control unit 110 transmits the measurement data to the management system 2 via the communication unit 111. At this time, as with the transmission of the measurement data, information for identifying the user is added.

The user equipment shown in FIG. 5 is equipped with two gas containers as gas containers GB. In this case, it is preferable that the gas pressure regulator (regulator 15) is an automatic switching regulator. In addition to the gas pressure regulation function, the automatic switching regulator has a function of automatically switching to the other gas container when a gas container becomes empty. The two gas containers are used one at a time, and when one becomes empty, switching to the other gas container is performed manually or by the automatic switching regulator (regulator 15).

In a user base 1 equipped with two gas containers GB as shown in FIG. 4, even if one gas container becomes empty, the LP gas supply will not be interrupted until the next gas container becomes empty, so the urgency of replacing the gas container is low. Therefore, when two or more gas containers are equipped, even if one gas container becomes empty, efficient delivery is possible by simultaneously delivering gas to another nearby user base 1 when its container becomes empty. This type of delivery is possible by managing delivery route management and gas shortage management in a combined manner.

With reference to Figures 7 to 13, we will explain the delivery management method using the delivery management system and the processing content of each functional component.

<Database>
The database includes user information, measurement information, gas container information, delivery base information, delivery person information, delivery person location information, a delivery candidate list, and a delivery list. In the present embodiment, the storage unit 22 functions as a database, but some or all of the information stored in the database may be stored in one or more separate storage devices.

The user information includes the user's name, user contact information (telephone number and destination for sending information), address of the user base 1, measuring device identification information, address location information, and distribution base identification information of the contractual distribution base 3, and is associated with user identification information that uniquely identifies the user. Here, the destination for sending information is, for example, the user's email address, a telephone number for sending SMS, an ID for push notifications, an ID for sending messages from a messaging platform (for example, a messaging function of an SNS or a laptop/mobile messaging application) via an API (Application Programming Interface), etc.

The reception unit 231 receives information via the communication unit 21 and stores it in the database. In the following, the involvement of the reception unit 231 will be omitted to the extent that it is not unclear, and the explanation will be given assuming that the "information processing device 20" receives the information and stores it in the database.

<Receiving measurement data>
The information processing device 20 receives the measurement data from the user base 1 and stores it in a database as measurement information. At this time, the measurement data is stored in association with the reception date and time.

The measurement information includes the measurement device identification information of the measurement device that sent the measurement data, the measurement data, the measurement type indicating the type of measurement data (weight, gas pressure, flow rate), the measurement date and time, and the reception date and time of the management system 2, and is associated with a user.

<Replacing the gas cylinder GB>
7 is a flow chart for replacing a gas container. The deliverer goes to the user's base 1 and replaces the gas container GB. The measuring device 11 or the deliverer terminal device 30 transmits to the information processing device 20 the deliverer identification information of the deliverer who replaces the gas container GB and the measuring device identification information in association with each other, and the information processing device 20 registers the replacement of the gas container GB.

In this embodiment, in step S701, the deliverer who has gone to the user base 1 uses the deliverer terminal device 30 to display a gas container replacement screen and inputs measuring device identification information on the gas container replacement screen. Then, in step S702, the deliverer terminal device 30 associates the deliverer identification information with the measuring device identification information as a request to start replacement and transmits the request to the information processing device 20. At this time, the gas container type of the replaced gas container GB is also registered.

In this embodiment, the measuring device identification information is displayed on the exterior of the measuring device 11 as a two-dimensional code, and the delivery person executes a code reading means that can be activated on the gas container replacement screen to read the measuring device identification information from the two-dimensional code and enter it into the gas container replacement screen.

In this embodiment, the deliverer terminal device 30 obtains the measuring device identification information from the code, but for example, the measuring device 11 and the deliverer terminal device 30 may communicate with each other via Bluetooth (registered trademark) or NFC (Near Field Communication), thereby transferring the measuring device identification information to the deliverer terminal device 30. Also, the exchange start request is sent from the deliverer terminal device 30, but the exchange start request may be sent from the measuring device 11. By transferring the deliverer identification information from the deliverer terminal device 30 to the measuring device using any of the above methods, the measuring device 11 may send an exchange start request to the management system 2 (information processing device 20).

In step S703, the information processing device 20, which has received the request to start the exchange, requests the measuring device 11 to send measurement data. If the measuring device 11 is a weight measuring device 11a, the information processing device 20 requests the current weight of the gas container to be sent as measurement data for the amount after use. If the measuring device 11 is a flow rate measuring device 11b, the information processing device 20 requests the total flow rate to date to be sent as measurement data for the amount used.

In step S704, the measuring device 11 acquires the measurement data, and in step S705, transmits the measurement data to the information processing device 20. In step S706, the information processing device 20 stores the received measurement data. In step S707, the information processing device 20 notifies the deliverer terminal device 30 that sent the exchange start request that acquisition of the measurement data is complete. At this time, if the weight has increased or the flow rate has decreased compared to the measurement data acquired so far, the information processing device 20 may notify the deliverer terminal device 30 of the possibility of measurement error, fraud, malfunction, etc.

In step S708, the delivery person replaces the used gas container GB that was installed with a new gas container GB. Then, the delivery person transmits an exchange request to the information processing device 20 in association with the delivery person identification information and the measuring device identification information. Note that, like the exchange start request, the exchange request may also be transmitted from the measuring device 11.

Here, when the measuring device 11 is the weight measuring device 11a,
Proceeding to step S710, the information processing device 20 requests transmission of measurement data for the new replaced gas container GB. In step S711, the weight measuring device 11a measures the weight as the initial amount, and in step S712, transmits the measurement data to the information processing device 20. In step S713, the information processing device 20 registers the gas container data in the database, using the received measurement data as the initial amount of the replaced gas container GB.

Here, when the measuring device 11 is the flow rate measuring device 11b,
In step S714, the information processing device 20 transmits a request to reset the total flow rate to the flow rate measurement device 11b. In step S715, the flow rate measurement device 11b resets the total flow rate recorded in a memory (not shown), and in step S716, transmits a reset completion notification to the information processing device 20.
Then, in step S717, the information processing device 20 notifies the deliverer terminal device 30 of the completion of the replacement, and the replacement of the gas container GB is completed.

<Gas cylinder data registration>
When the gas container GB is replaced by the delivery person, the gas container data is registered in the database. The gas container data is data associated with the user by the user identification information or the measurement device identification information, and includes gas container data identification information, the initial amount of the gas container GB, the gas container type, the gas container data identification information before replacement, the delivery person identification information who installed the gas container, the installation date and time, the remaining amount, the delivery person identification information who collected the gas container, and the collection date and time. Since the initial amount is information for calculating the refund amount described later, it is not necessary to store the initial amount for each user as in this embodiment. For example, the type of the gas container GB delivered to the user base 1 may be stored in association with the user, and further, the weight or capacity corresponding to the initial amount may be recorded for each type of gas container. Alternatively, the initial amount is not necessary even when the remaining amount of the gas container GB installed at the user base 1 can be directly obtained from the measurement data. In other words, the initial amount is not necessary when the remaining amount of LP gas can be calculated or estimated from the gas pressure and weight received as the measurement data. For example, if the weight of the gas bottle GB alone is stored in the database, the remaining amount may be calculated from the weight of the gas bottle GB at the time of collection and the weight of the bottle alone.

<Gas cylinder data for installed gas cylinders>
In this embodiment, when the information processing device 20 receives a request to start replacement in step S702, it issues new gas container data identification information and registers in the database the initial amount of gas container GB, the gas container type, the gas container data identification information before replacement, the identification information of the delivery person who installed the gas container, and the installation date and time (delivery completion date).

The database stores gas container master data. For each type of gas container GB, the gas container master data includes the weight and capacity of the gas container GB when it is filled with LP gas, the weight of the gas container when it is empty of LP gas, and the usage fee for the gas container GB. In this embodiment, the usage fee includes installation and collection costs, but these may be determined based on other data.

Here, the initial amount is the weight obtained in step S711 when the measuring device 11 is a weight measuring device 11a. When the measuring device 11 is a flow rate measuring device 11b, the initial amount of content is determined from the gas container master and the gas container type of the gas container GB to be replaced transmitted from the delivery company terminal device 30 in step S702. When the measuring device 11 is a weight measuring device 11a, the weight as the initial amount may be determined based on the gas container master and the gas container type of the gas container GB to be installed.

As the pre-replacement gas container data identification information, for example, the identification information of gas container data for the user stored in the database (in this embodiment, determined by the user identification information and the measuring device identification information) in which the "delivery company identification information that collected the gas container" or the "collection date and time" etc. have not been entered may be entered. The delivery company identification information that installed the gas container is the delivery company identification information transmitted in step S702 etc.

The remaining amount management unit 234 calculates the remaining amount of LP gas in the gas container GB based on the initial amount and the amount used or the amount after use, and registers it in the gas container data. This amount used and the amount after use are calculated at least based on the measurement data sent by the measuring device 11 after a request to start replacement is made. Preferably, the remaining amount may be calculated and registered in the gas container data each time the measuring device 11 sends measurement data at a specified transmission timing. This makes it possible to grasp the remaining amount of LP gas at the user base 1 at a certain point in time, and can be used when adding to the delivery list described below, etc.

<Gas cylinder data for collected gas cylinders>
Furthermore, for the gas container data of the collected gas container, the remaining amount (collected amount), "identification information of the delivery company that collected the gas container" and collection date and time are input. The remaining amount (collected amount) is calculated by the remaining amount management unit 234 in step S702 based on the measurement data transmitted from the measuring device 11 after the exchange start request. The "identification information of the delivery company that collected the gas container" is the delivery company identification information transmitted in step S702, etc.

In this embodiment, the remaining amount management unit 234 determines the remaining amount of LP gas based on the initial amount of gas container data for the gas container GB before replacement and the measurement data acquired in step S706 (weight or total flow rate of the gas container GB before replacement), and registers it in the collected gas container data.

More specifically, when calculating the remaining amount based on weight, the remaining amount management unit 234 acquires the weight of the gas container used in the user's equipment from the weight measuring device 11a, and calculates the amount of LP gas consumed based on the initial amount and the acquired weight. Furthermore, the consumed amount is subtracted from the weight of gas filled in the gas container stored in the gas container master to calculate the remaining amount, which is the weight of unused LP gas. Alternatively, the remaining amount may be calculated from the acquired weight and the weight of the gas container when empty stored in the gas container master.

When calculating the remaining amount based on the flow rate, the remaining amount management unit 234 obtains the total flow rate of the gas container used at the user's equipment from the flow rate measurement device 11b, and calculates the remaining amount of LP gas based on the initial amount and the obtained total flow rate.

<Determining the amount of rebate to users>
The refund processing unit 235 calculates the refund amount to the user based on the initial amount and the used amount or the used amount. In this embodiment, the refund processing unit 235 calculates the refund amount based on the remaining amount calculated by the remaining amount management unit 234 when the gas container GB is collected. The calculated refund amount is recorded as refund amount data in association with the user, and when the refund amount is used (applied to payment), what it was used for and the date and time of use may be associated. The refund amount data in this embodiment has refund amount data identification information, user identification information (or metering device identification information), the refund amount, and the refund amount based on the refund amount.

In this embodiment, the rebate amount is a monetary rebate amount for the purchase cost of a newly installed gas container or the usage fee for a collected gas container. Alternatively, the rebate amount may be given to the user as electronic money or points. Alternatively, the rebate amount may be an amount rebated based on an increase in the capacity of the next gas container purchased.

The rebate processing unit 235 stores payment information for each user in a database. When a certain type of gas container GB is installed at the user base 1, payment information for the user is generated. The payment information includes, for example, the usage fee for the gas container GB determined according to the installed gas container GB, the rebate amount used for the usage fee, the billing amount calculated from the usage fee and the rebate amount, and payment data specifying the payment for this billing amount. In this embodiment, the payment information includes payment identification information, gas container data identification information, rebate amount data identification information, the billing amount obtained by subtracting the rebate amount from the usage fee, and payment data. The rebate processing unit 235 determines the billing amount, which is the payment amount for cashless settlement for the user, based on the usage fee and the rebate amount.

It is assumed that the rebate amount and payment of the usage fee will be made cashlessly based on the calculation of this rebate amount, but methods other than cashless payment may be used depending on the user's situation. However, cashless payment reduces the need for complicated fee transactions and also contributes greatly to delivery efficiency by shortening exchange times, etc. In this embodiment, information related to cashless payment or payment by other methods is recorded as payment data. Payment data is information that is generated based on payment processing by a payment system included in the delivery management system 0 or an external payment system, and is passed to the information processing device 20.

<Delivery Management>
The database stores the delivery base information.
The distribution base information includes distribution base identification information that uniquely identifies the distribution base 3, the base name, telephone number, address, and address location information of the distribution base 3.
In addition, the deliverer information includes deliverer identification information, the deliverer's name, and deliverer contact information (telephone number and destination for sending information), and is associated with delivery base identification information that uniquely identifies the delivery base 3 to which the deliverer belongs.

Figures 8 and 9 are flowcharts for creating a delivery list. The information processing device 20 calculates the replacement threshold date (hereinafter referred to as the processing date) for each user base 1 based on the delivery completion date and measurement data for each user base 1, and executes various processes to deliver a new gas bottle GB before the LP gas runs out completely.

The prediction unit 233 predicts the processing date for the gas container GB at each user base 1 based on the delivery completion date stored in the database. Then, the corresponding user is added to the delivery candidate list. In this embodiment, the prediction unit 233 analyzes the consumption trend of LP gas at each user facility based on the delivery completion date, initial amount, and measurement data and/or remaining amount, and predicts the processing date for each user. Then, the user is added to the delivery candidate list.

<Delivery candidate list>
Fig. 10(a) is a diagram showing an example of setting information of a delivery candidate list. Fig. 10(b) is a diagram showing an example of detailed information of a delivery candidate list. The setting information includes identification information of the delivery candidate list, a processing date, a desired confirmation date, a desired confirmation flag (received/not yet), and a start date and an end date of the desired delivery date. The detailed information includes identification information of the delivery candidate list, user identification information, delivery base identification information, a response flag (received/not yet), the responded desired delivery date, the desired time zone, and the date and time of receipt of the response.

In this embodiment, the delivery candidate list is a list created for each processing date, as shown in the setting information, and the desired delivery date and time is presented to the user on the desired confirmation date, which is set based on the processing date and the like. The desired delivery date and time is presented as a selection from multiple dates within the period specified as the start and end dates. Time periods are also presented. For example, multiple time periods are presented as candidates for the desired time period, such as (1) 8:00-12:00, (2) 1:00-3:00, (3) 3:00-5:00, and (4) 5:00-8:00, and the user can select the desired time period from these.

The delivery candidate list may include multiple delivery candidates (users). As shown in the detailed information, the delivery candidate list includes the user, the delivery base contracted by the user, the response status and response content for the desired delivery date, etc.

In step S801 of FIG. 8, the prediction unit 233 calculates the processing date for a user whose remaining amount of LP gas satisfies a predetermined condition. For example, the remaining amount of LP gas satisfies the predetermined condition when the expected usable period is within N days, or when the remaining amount falls below a predetermined percentage of the initial amount.

In step S802, the prediction unit 233 predicts the consumption rate of LP gas from the initial amount of gas container data searched in step S801 and the received measurement data, etc., and calculates the processing date when the remaining amount of LP gas will reach a predetermined replacement threshold from the current remaining amount. Then, each user is added to the delivery candidate list for each processing date. When the prediction unit 233 has finished processing all the searched gas container data (YES in step S803), proceed to step S804.

Here, the user who uses the gas container GB that received the replacement signal (YES in step S804) has a high priority for replacement, and is therefore added to the delivery candidate list that is the first to be added (for example, a delivery candidate list for which confirmation of preference is to be made today or the next day) and that includes the same delivery base and delivery area (step S805). If the user of the user equipment that received the replacement signal has already been added to another delivery candidate list, the user is removed from the other delivery candidate list. Note that in step S803, when the addition to the delivery candidate list is completed, users with the same attributes (same delivery base identification information and delivery area) may be configured to be aggregated into one or more sheets based on the delivery base and delivery area associated with the user added to the delivery candidate list. This may result in users with a common area being added to the same delivery candidate list, making delivery more efficient.

For example, the prediction unit 233 adds users to the delivery candidate list based on the processing date, but among the users who have been added to the delivery candidate list or who are to be added to the delivery candidate list, those users who have a predetermined amount of gas remaining in their gas container GB, i.e., users who have consumed less LP gas than expected, may be deleted from the delivery candidate list or may not be added.

In Southeast Asian countries, the gas container GB may be installed indoors, such as in the kitchen (for example, under the sink). Therefore, entry into the room is required to replace the gas container, and the user's presence or consent may be required. In step S806, the delivery management unit 232 presents candidate dates and times for the desired confirmation date to the user who is a delivery candidate.

The delivery management unit 232 presents a number of candidate dates and times when the user is available to be present to the user terminal device 10 of the user set as a delivery candidate, and the reception unit 231 accepts a combination of date and time from the user terminal device 10 as the desired delivery date and time. The presentation and reception of the candidate dates and times may be performed by sending a URL (Uniform Resource Locator) of a form for inputting the candidate dates and times to a destination for sending information. Alternatively, the candidate dates and times may be sent using SMS addressed to a telephone number. Alternatively, the candidate dates and times may be sent by sending and receiving messages via a messaging platform. Alternatively, the candidate dates and times may be presented verbally by an operator or by an automated voice over the telephone. When the reception unit 231 accepts the candidate dates and times, it sets the response flag in the detailed information of the delivery candidate list to "answered" and adds the desired delivery date, desired time zone, and response reception date and time.

<Creating a shipping list>
Fig. 10(c) is a diagram showing an example of setting information for a delivery list. Fig. 10(d) is a diagram showing an example of detailed information for a delivery list. The setting information includes identification information for the delivery list, identification information for the delivery base in charge of delivery, and the delivery date. The detailed information includes identification information for the delivery list, user identification information, desired time period for delivery, delivery area, delivery status, and the processing date and time when the delivery status was changed.

The delivery management unit 232 generates a delivery list and adds the user to the scheduled delivery list for delivery on the desired delivery date. The user is added to the detailed information of the unconfirmed delivery list (scheduled delivery list) based on the delivery area associated with the user and the received desired delivery date. According to the setting information of this embodiment, a delivery list is generated for each combination of delivery date, delivery base, and delivery area. Note that, for example, a shipping list may be generated for each delivery date and delivery base.

In step S901, the user who has received the response regarding the desired delivery date and time (YES in step S901) adds the desired delivery date and time to a delivery list with the delivery date as the delivery date (step S902). Here, the delivery list is finalized (step S903), such as the day before the delivery date, and may be configured such that it is not possible to add a delivery destination (user base 1) to the delivery list after finalization.

On the other hand, in step S904, if a user does not respond with a desired delivery date and time by the response deadline (YES in step S904), the delivery date will be set to, for example, the next day, and the user will be added to the delivery list of delivery bases (step S905). Here, for example, a user with no response (delivery area ID: 4, delivery base: 3000001) may be added to the unconfirmed delivery list, with delivery base 3 (3000001) being the delivery list for delivery area ID (4). Alternatively, a user with no response may be configured to be added again to the delivery candidate list.

The database stores the geographical layout of the delivery areas, and the delivery management unit 232 may consolidate multiple delivery lists. Alternatively, if the delivery lists are not distinguished by delivery area, the delivery lists may be divided according to the delivery areas of the user bases 1 included in the delivery lists. Alternatively, in addition to or instead of the delivery areas, location information of the user bases 1 may be used to move users included in one delivery list to another delivery list, or to divide the delivery lists.

In step S906, the delivery management unit 232 creates delivery route information based on the delivery list. The delivery management unit 232 determines a delivery route using existing calculation methods for delivery plan problems or machine learning based on the number of user bases 1 included in the delivery list, the desired time period, and the location information of the user bases 1. Then, in step S907, the delivery management unit 232 transmits the created delivery list and delivery route to at least one deliverer terminal device 30 belonging to each delivery base 3.

The delivery staff at the distribution base 3 sequentially delivers gas bottles GB filled with LP gas to each user base 1 based on the delivery list and delivery route. If the delivery management unit 232 does not generate a delivery route, the delivery person determines the delivery route based on the delivery list sent to each distribution base 3. The delivery list may be divided or merged at the distribution base 3, or the user may be moved.

At each delivery base 3, the delivery person terminal device 30 is used to associate the delivery person identification information with each user base 1 that is the delivery destination, or with each delivery list. It is also possible to register the work schedule of the delivery person in the database, and the delivery management unit 232 can add the delivery person identification information to the setting information of the delivery list, thereby generating a delivery list for each delivery person.

When the deliverer identification information is associated, the delivery list for which the individual deliverer is responsible is displayed on the deliverer terminal device 30 of each deliverer, and the delivery status for each customer base 1 included in the list can be input. Delivery statuses are, for example, "before delivery," "delivery completed," "absent," etc. When the delivery status is input on the deliverer terminal device 30, the reception unit 231 changes the delivery status in the detailed information of the delivery list and adds the processing date and time to the detailed information.

<Emergency response>
The deliverer terminal device 30 is configured to be able to upload its own location to the information processing device 20 at predetermined time intervals, etc. When the reception unit 231 receives location information from the deliverer terminal device 30, it associates the deliverer identification information, the location information, and the time of reception thereof, and stores them in the database as deliverer location information.

<Creating emergency information>
A flowchart relating to the creation of emergency information will be described with reference to Fig. 11. Steps S1101 to S1106 are the processing procedures when the measuring device 11 at the user base 1 detects an abnormality, and steps S1111 to S1116 are the processing procedures when the information processing device 20 detects an abnormality.

When the measuring device 11 in FIG. 11 detects an abnormality, first, in step S1101, if the gas leak sensor 14 at the user base 1 detects an abnormality, in step S1102, the control unit 110 drives the gas circuit breaker 13 to cut off the gas. In addition, in step S1103, an alarm sound is issued from the measuring device 11. In step S1104, the gas leak sensor 14 that detected the abnormality issues an alert to the information processing device 20. Specifically, the control unit 110 or the gas leak sensor 14 of the measuring device 11 transmits an alert signal to the information processing device 20. At this time, the alert signal is associated with measuring device identification information, making it possible to determine which user base 1 the alert is from.

In step S1105, the emergency response request unit 236 generates emergency information and registers it in the database. The emergency information includes emergency identification information, user identification information (or measuring device identification information), the date and time of occurrence, operator identification information, emergency status, delivery person identification information of the rushed delivery person, and the date and time of response. In step S1105, at least the emergency identification information, user identification information (or measuring device identification information), and the date and time of occurrence are input. The emergency status is set to a state such as "not responded to," "delivery person dispatched," or "work completed."

In step S1106, the emergency response request unit 236 notifies the user terminal device 10 of the abnormal situation. The notification may be made by sending a message or the like to the address in the user information. The notification may also be sent using SMS addressed to a telephone number. The notification may also be made by sending a message via a messaging platform. Alternatively or in addition to this, a call may be made by an operator or an automated voice, and the notification may be made verbally by an operator or by an automated voice over the telephone.

On the other hand, when detecting an abnormality in the information processing device 20, first, in step S1111, the emergency response request unit 236 detects the abnormality. When detecting an abnormality, for example, the measurement data received from the measuring device 11 indicates an abnormal value. More specifically, the emergency response request unit 236 detects an abnormality when the gas pressure received as the measurement data exceeds a threshold value or when the weight received as the measurement data exceeds a threshold value (for example, when the weight becomes 0, etc.).

When the emergency response request unit 236 detects an abnormality in step S1111, in step S1112, the emergency response request unit 236 generates emergency information and registers it in the database. Then, in step S1113, a gas shutoff request signal is sent to the measurement device 11 at the user base 1 based on the measurement device identification information of the measurement device 11 that detected the abnormality.

When the measuring device 11 receives the gas shutoff request signal, in step S1114, the control unit 110 drives the gas circuit breaker 13 to shut off the gas. In step S1115, the measuring device 11 issues an alarm. In step S1116, the emergency response request unit 236 notifies the user terminal device 10 of the abnormal situation.

<Arrangements for emergency delivery personnel>
12 is a flow chart for requesting a deliverer to rush to the site. The emergency response request unit 236 determines a deliverer to be requested to rush to the site based on the location of the deliverer terminal device 30.

In step S1201, when unaddressed emergency information is registered, information is displayed on the operator terminal device 200 based on the emergency information. In this embodiment, whether the emergency information has not been addressed is determined based on the emergency status. In step S1202, the emergency response request unit 236 acquires the location of the user base 1 that is the rush destination. In this embodiment, the address and/or location information included in the user information is acquired from information identifying the user associated with the emergency information (user identification information).

In step S1203, the emergency response request unit 236 searches for a deliverer (delivery terminal device 30) near the user base 1 based on the location of the user base 1 acquired in step S1202 and the deliverer location information stored in the database. At this time, the search targets not only deliverers belonging to the distribution base 3 contracted by the user, but also deliverers belonging to distribution bases other than the distribution base 3 contracted by the user. Here, for example, deliverers who are within a specified distance from the location of the user base 1 are searched for, and the search results may be prioritized in order of the distance to the user base 1. Note that the priority order may be determined simply by comparing the distances, or, for example, the distance may be multiplied by a distance coefficient, and in the case of a deliverer belonging to a distribution base 3 contracted by the user, the affiliation coefficient may be further multiplied to calculate a score, and the ranking may be determined based on the score.

When the emergency response request unit 236 determines the delivery company to be requested, it transmits the location or user identification information of the user's equipment, and the telephone number or delivery company identification information of the delivery company to the operator terminal device 200. In this embodiment, in step S1204, the emergency response request unit 236 transmits one or more of the nearby delivery companies obtained as a result of the search to the operator terminal device 200 as candidates for delivery companies to be requested to rush to the site. At this time, the location information, name, affiliation, telephone number, etc. of the delivery company are also transmitted to the operator terminal device 200. Note that the user identification information and delivery company identification information may be transmitted to the operator terminal device 200, and the operator terminal device 200 may request information such as the telephone number from a database. Then, in step S1205, the operator calls the delivery company based on the information received by the operator terminal device 200 and requests that the delivery company rush to the site.

Figure 13 is an example of a screen display on the operator terminal device 200. The operator screen W13 includes a user information display section W131, a deliverer information display section W132, a request completion button W133, a map display section W134, a next page button W135, and a previous page button W136. The user information display section W131 displays the user's name, address, telephone number, etc. as information about the user (user base 1). The deliverer information display section W132 displays the deliverer's name, telephone number, etc. as information about the deliverer received from the emergency response request section 236. The operator calls the deliverer based on the information displayed in the deliverer information display section W132 and requests that the deliverer rush to the site. If the request to rush to the site is successful, the operator presses the request completion button W133, which causes the emergency response request section 236 to associate the deliverer identification information with the emergency information and change the emergency status to "delivery dispatch."

The map display section W134 displays the location information of the deliverer displayed in the deliverer information display section W132 and the user base 1 on a map. In addition, the next page button W135 and previous page button W136 are used to switch between lists when there are multiple deliverers who can be contacted.

In this embodiment, the operator calls the delivery company to request that they rush to the site, but this may be done, for example, by calling using an IP phone function configured to be available from the operator terminal device 200. Alternatively, the system may be configured to make calls in order of priority to the delivery companies searched for by the automated voice.

In addition to or instead of making a phone call, information may be sent to the delivery person terminal device 30 of one or more delivery persons searched for in step S1203 to request that the delivery person be rushed to the site. At this time, when the emergency response request unit 236 determines the delivery person to be requested, it transmits the location of the user base 1 to be the rush destination or user identification information to the delivery person's address. The delivery person terminal device 30 that receives the user identification information may request and receive information regarding the location of the user base 1 from the information processing device 20 based on the user identification information. The emergency response request unit 236 may be configured to be able to accept a request to rush to the site from the delivery person terminal device 30 of the delivery person, and by accepting this, it may associate the delivery person identification information with the emergency information and change the emergency status to "delivery person dispatched". The information sent may include the address of the rush destination, the user's name, telephone number, and other information on the user base 1 and/or the user that is the rush destination.

In addition, the gas circuit breaker 13 and gas leak sensor 14 have been mentioned above as components of this system, but even if they are not included in this system, the system still performs basic functions such as preventing gas shortages and providing fee refunds according to the amount of gas used. Therefore, although the gas circuit breaker 13 and gas leak sensor 14 are not essential components, it is desirable to include them in the system from a safety standpoint.

0: Delivery management system 1: User base 2: Management system 3, 3a, 3b: Delivery bases 3a1, 3a2, 3an: Delivery person terminal device 10: User terminal device 11: Measuring device 11a: Weight measuring device 11b: Flow rate measuring device 12: Communication device 13: Gas circuit breaker 14: Sensor 14a: Gas container 15: Regulator 16: Gas pressure measuring device 20: Information processing device 21: Communication unit 22: Memory unit 23: Control unit 30: Delivery person terminal device 90: Terminal device 91: Communication unit 92: Memory unit 93: Control unit 94: Input unit 95: Output unit 110: Control unit 111: Communication unit 112: Weight measuring unit 113: Flow rate measuring unit 200: Operator terminal device 231: Reception unit 232: Delivery management unit 233: Prediction unit 234: Remaining amount management unit 235 : Rebate processing section 236 : Emergency response request section GB : Gas bottle NW : Network W13 : Operator screen W131 : User information display section W132 : Deliverer information display section W133 : Request completion button W134 : Map display section W135 : Next page button W136 : Previous page button

Claims (5)

A delivery management system that delivers and manages a gas container to a user who uses a portable gas fuel sealed in the gas container, the delivery management system comprising:
The delivery management system includes an information processing device, a measuring device that is disposed in a user facility and acquires measurement data of the gas container, a deliverer terminal device used by a deliverer who replaces the gas container, and an operator terminal device used by an operator who contacts the deliverer,
The database stores the location of the user equipment associated with the user identification information, and the deliverer contact information associated with the deliverer identification information,
The information processing device receives the change in location of the deliverer transmitted from the deliverer terminal device, and when it detects that the measurement data received from the measurement device shows an abnormal value, determines that an emergency has occurred , and determines multiple deliverers who are candidates for requesting an on-site rush based on the change in location of the deliverer,
The information processing device further transmits to the operator terminal device the location of the user equipment in which the measuring device in which the abnormal value was detected is located or the user identification information for acquiring the location, as well as the deliverer contact information or the deliverer identification information of multiple deliverers who are candidates for requesting on-site dispatch ,
The information processing device further displays the location of the user equipment where the measuring device where the abnormal value was detected is located, the changed locations of the multiple deliverers who are candidates for requesting a rush to the site, and the deliverer contact information or the deliverer identification information of the deliverers together with map information on the same screen of the operator terminal device used by the operator, the map information showing the location of the user equipment, the changed locations and priorities of the multiple deliverers who are candidates for requesting a rush to the site, and the deliverer contact information or the deliverer identification information being displayed in order of priority.
Delivery management system. The database stores a destination for transmitting information to the deliverer terminal device as the deliverer contact information,
When the information processing device determines a plurality of candidate delivery persons to be requested to rush to the site, the information processing device transmits to the destination the location of the user equipment in which the measuring device in which the abnormal value was detected is installed or user identification information for acquiring the location.
The delivery management system according to claim 1 . The database stores, as user contact information, a destination or telephone number for transmitting information to a user terminal device,
When measurement data indicating an abnormal value is received from the measurement device, the information processing device transmits the user contact information to the operator terminal device, or notifies the user terminal device using the user contact information.
The delivery management system according to claim 1 . The database stores the user and a delivery company that has made a contract for delivery of the gas container in association with each other,
When measurement data indicating an abnormal value is received from the measuring device, the information processing device determines a plurality of candidate deliverers to be requested to rush to the site from among deliverers including those that have no contractual relationship with the user of the rush destination.
The delivery management system according to claim 1 . A method for managing the delivery of a gas container to a user who uses a portable gas fuel sealed in the gas container, the method comprising the steps of:
The delivery management system includes an information processing device, a measuring device that is disposed in a user facility and acquires measurement data of the gas container, a deliverer terminal device used by a deliverer who replaces the gas container, and an operator terminal device used by an operator who contacts the deliverer,
The database stores the location of the user equipment associated with the user identification information, and the deliverer contact information associated with the deliverer identification information,
The information processing device receives the change in location of the deliverer transmitted from the deliverer terminal device, and when it detects that the measurement data received from the measurement device shows an abnormal value, determines that an emergency has occurred , and determines multiple deliverers who are candidates for requesting an on-site rush based on the change in location of the deliverer,
The information processing device further transmits to the operator terminal device the location of the user equipment in which the measuring device in which the abnormal value was detected is located or the user identification information for acquiring the location, as well as the deliverer contact information or the deliverer identification information of multiple deliverers who are candidates for requesting on-site dispatch ,
The information processing device further displays the location of the user equipment where the measuring device where the abnormal value was detected is located, the changed locations of the multiple deliverers who are candidates for requesting a rush to the site, and the deliverer contact information or the deliverer identification information of the deliverers together with map information on the same screen of the operator terminal device used by the operator, the map information showing the location of the user equipment, the changed locations and priorities of the multiple deliverers who are candidates for requesting a rush to the site, and the deliverer contact information or the deliverer identification information being displayed in order of priority.
How to manage delivery.