Gas delivery processing method, system, program, server device, and recording medium

Abstract

To achieve planned delivery processing of a gas container while correctly determining a residual gas volume at a gas supply destination.SOLUTION: A gas delivery processing method includes the steps of: acquiring meter information for a gas supply destination (10) via a meter information acquisition unit; calculating gas use information representing a trend of gas consumption in a calculation period (the set number of days x); calculating a predicted gas exhaustion date (tx) by using gas use information and gas volume information for the gas supply destination; setting a delivery segment and a scheduled delivery day on the basis of the predicted gas exhaustion date and delivery condition information; setting a lower-limit gas consumption threshold value representing a lower limit of gas consumption, comparing the gas consumption on each day within the calculation period with the lower-limit consumption threshold value of the gas supply destination, determining that the gas consumption is abnormal if a day with the gas consumption being below the lower-limit gas consumption threshold value is contained in the calculation period, and newly calculating the gas use information; and recalculating the predicted gas exhaustion day with the new gas use information for the gas supply destination that has been determined to be abnormal, and adjusting the delivery segment.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a gas delivery processing technology that adjusts delivery predictions based on indication information of gas meters at gas supply destinations, such as LPG (Liquefied Petroleum Gas), and that adjusts delivery predictions based on abnormal gas usage. [Background technology]

[0002] LPG is generally delivered in cylinders by gas companies to gas supply destinations. Gas usage is managed by the guideline information obtained from the gas meter. Gas companies use the guideline value obtained through regular meter readings, for example once a month, to calculate gas charges and to create a delivery plan for the next gas cylinders. This delivery plan uses a method to predict the amount of gas usage per day, for example, based on past gas usage and this year's gas usage. Conventionally, gas meter readings were done once a month, for example. Gas companies had to set delivery plans based on the limited meter reading information to prevent gas customers from running out of gas. Gas usage is not constant depending on the living conditions of the gas customer, and is greatly affected by factors such as climate change, so there is an error in the predicted gas usage. For this reason, gas companies would take prediction errors into account and set a high threshold for the amount of gas remaining in the gas container when formulating delivery plans to prevent gas customers from running out.

[0003] Regarding such gas usage prediction, it is known that a method is used to receive guideline information from a gas meter, compare each guideline information to calculate gas usage, and calculate the rate of change in past gas usage based on a comparison of multiple gas usage amounts for a specified period prior to the meter reading date of the guideline information, change the gas usage amount according to this rate of change, and predict the changed gas usage amount as the future gas usage amount (Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2013-254414 A Summary of the Invention [Problem to be solved by the invention]

[0005] By the way, with regard to gas meter reading, improvements in the batteries that power gas meters and in communication technology have made it possible to perform meter readings more frequently, making it easy to grasp the amount of gas used and the current amount of remaining gas. However, in gas delivery processing, for example, predicting when gas will run out in accordance with frequent meter readings leads to an increased load on processing capacity and an increase in data storage capacity. Also, if the number of times prediction processing is performed is uniformly reduced in relation to the meter reading frequency to reduce the load on the calculation processing, it becomes impossible to formulate a precise gas container delivery plan that follows fluctuations in gas usage. On the other hand, if a method of gas bottle delivery is adopted in which gas bottle delivery instructions are issued based on frequent meter readings without predicting when gas will run out, the gas company will have to deal with situations such as a sudden increase in the number of deliveries or, conversely, a period of time when no delivery instructions are issued, which means that gas bottle delivery cannot be carried out in a planned manner, which leads to an increased burden on workers. Patent Document 1 does not disclose or suggest such a problem, and the configuration disclosed in Patent Document 1 cannot solve such a problem.

[0006] In view of the above, an object of the present invention is to accurately grasp the remaining gas amount at a gas supply destination and to realize a planned delivery process of gas containers. Another object of the present invention is to reduce the load of gas delivery prediction processing while performing gas meter reading processing frequently. [Means for solving the problem]

[0007] In order to achieve the above-mentioned object, according to one aspect of the gas delivery processing method of the present invention, the method includes a step of a guideline information acquisition unit acquiring guideline information for a gas supply destination, a step of calculating gas usage information indicating a trend in gas usage for a set calculation period, a step of calculating a predicted gas run-out date using the gas usage information and gas capacity information of the gas supply destination, a step of setting a delivery category and a scheduled delivery date based on the predicted gas run-out date and delivery condition information, a step of setting a lower limit gas usage threshold indicating a lower limit of the gas usage, comparing the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, determining that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, and calculating new gas usage information, and a step of recalculating the predicted gas run-out date for the gas supply destination determined to be abnormal based on the newly calculated gas usage information, and adjusting the delivery category.

[0008] This gas delivery processing method may include a step of varying the lower gas usage threshold value based on a gas usage history of the gas supply destination.

[0009] In order to achieve the above-mentioned object, according to one aspect of the gas delivery processing system of the present invention, the system includes a guideline information acquisition unit that acquires guideline information for gas supply destinations, and a server device that calculates gas usage information indicating a trend in gas usage for a set calculation period, calculates a predicted gas run-out date using the gas usage information and gas capacity information for the gas supply destination, sets a delivery category and a scheduled delivery date based on the predicted gas run-out date and delivery condition information, sets a lower limit gas usage threshold indicating a lower limit of the gas usage, compares the daily gas usage within the calculation period acquired based on the guideline information with the lower limit gas usage threshold for the gas supply destination, and determines that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, calculates new gas usage information, and for the gas supply destinations determined to be abnormal, recalculates the predicted gas run-out date using the newly calculated gas usage information and adjusts the delivery category.

[0010] In this distribution processing system, the server device may vary the lower limit gas usage threshold value based on the gas usage history of the gas supply destination.

[0011] In order to achieve the above-mentioned object, according to one aspect of the program of the present invention, the program is implemented by a computer, and includes the following functions: acquiring guideline information for a gas supply destination; calculating gas usage information indicating a trend in gas usage for a set calculation period; calculating a predicted gas run-out date using the gas usage information and gas capacity information for the gas supply destination; setting a delivery category and a scheduled delivery date based on the predicted gas run-out date and delivery condition information; setting a lower limit gas usage threshold indicating the lower limit of the gas usage, comparing the daily gas usage within the calculation period acquired based on the guideline information with the lower limit gas usage threshold for the gas supply destination, determining that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, and calculating new gas usage information; and for the gas supply destination determined to be abnormal, recalculating the predicted gas run-out date based on the newly calculated gas usage information and adjusting the delivery category.

[0012] In this program, the computer may further realize a function of varying the lower limit gas usage threshold based on a gas usage history of the gas supply destination.

[0013] In order to achieve the above-mentioned object, according to one aspect of the server device of the present invention, the server device includes a guideline information acquisition unit that acquires guideline information for a gas supply destination, and a processing unit that calculates gas usage information indicating a trend in gas usage for a set calculation period, calculates a predicted gas run-out date using the gas usage information and gas capacity information of the gas supply destination, sets a delivery category and a scheduled delivery date based on the predicted gas run-out date and delivery condition information, sets a lower limit gas usage threshold indicating a lower limit of the gas usage, compares the daily gas usage within the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, determines that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, calculates new gas usage information, and for the gas supply destination determined to be abnormal, recalculates the predicted gas run-out date using the newly calculated gas usage information and adjusts the delivery category.

[0014] In this server device, the processing unit may vary the lower limit gas usage threshold based on a gas usage history of the gas supply destination.

[0015] In order to achieve the above-mentioned object, according to one aspect of the recording medium of the present invention, a recording medium storing a program for implementation by a computer is stored, and the program for implementation by the computer is stored with a function of acquiring guideline information for a gas supply destination, a function of calculating gas usage information indicating a trend in gas usage for a set calculation period, a function of calculating a predicted gas run-out date using the gas usage information and gas capacity information for the gas supply destination, a function of setting a delivery category and a scheduled delivery date based on the predicted gas run-out date and delivery condition information, a function of setting a lower limit gas usage threshold indicating a lower limit of the gas usage, comparing the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold for the gas supply destination, determining that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, and calculating new gas usage information, and a function of recalculating a predicted gas run-out date for a gas supply destination determined to be abnormal based on the newly calculated gas usage information, and adjusting the delivery category. Effect of the Invention

[0016] According to the present invention, any one of the following effects can be expected. (1) A lower limit gas usage threshold indicating the lower limit of gas usage is set, and the gas usage for each day within a calculation period obtained based on guideline information is compared with the lower limit gas usage threshold of the gas supply destination. If the calculation period includes a day when the gas usage falls below the lower limit threshold, the gas usage can be determined to be abnormal. (2) By periodically monitoring the gas usage status of users, and if the calculation period includes a day when the gas usage falls below the lower limit threshold, the gas usage is determined to be abnormal. Gas shortage predictions and delivery categories can be adjusted only for users who have experienced such gas usage, thereby reducing the burden of calculating gas shortage predictions and delivery schedules. (3) By carrying out delivery processing based on precise management of remaining gas volume using real-time meter reading results and predicting when to replace gas containers by analyzing gas usage status, it is possible to reduce the amount of remaining gas while preventing gas shortages. [Brief description of the drawings]

[0017] [Figure 1] 5 is a flowchart showing an example of a gas delivery management process according to the first embodiment. [Diagram 2] FIG. 1 illustrates an example of a gas management system. [Diagram 3] FIG. 11 is a diagram showing an example of a gas delivery management file. [Figure 4] FIG. 13 is a diagram showing an example of a random meter reading file. [Diagram 5] FIG. 11 is a diagram showing an example of a delivery condition database. [Figure 6] FIG. 11 is a diagram showing an example of a delivery classification table. [Figure 7] 11 is a diagram showing an example of a process for determining and recalculating a predicted date for gas shortage based on a gas usage trend. FIG. [Figure 8] FIG. 11 is a diagram showing an example of a gas usage state monitoring process based on the amount of gas usage. [Figure 9]FIG. 13 is a diagram showing an example of a gas container delivery division process. [Figure 10] 13 is a flowchart showing an example of a gas container delivery management process. [Figure 11] FIG. 11 is a diagram illustrating an example of a gas management system according to a second embodiment. [Figure 12] FIG. 2 is a diagram illustrating an example of a deliverer terminal. [Figure 13] FIG. 13 is a diagram showing an example of a management information screen displayed on the manager terminal. [Figure 14] FIG. 13 is a diagram showing an example of delivery instruction information displayed on a deliverer terminal. [Figure 15] FIG. 13 is a diagram showing an example of an information presentation screen for a gas supply destination. [Figure 16] FIG. 11 is a sequence diagram of a gas delivery management process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] [First embodiment] Fig. 1 shows an example of the process of gas delivery management processing according to the first embodiment. The process contents and process steps shown in Fig. 1 are merely examples, and the present invention is not limited to such a configuration. This gas delivery management processing is an example of a gas delivery processing method or gas delivery processing program of the present invention, and includes, for example, as shown in FIG. 1, identifying gas supply destination 10 (S101), identifying gas delivery management file 22 (S102), obtaining guideline information (S103), storing the guideline information in gas delivery management file 22 (S104), calculating gas usage information (S105), monitoring the timing of gas delivery prediction calculation processing (S106), monitoring abnormalities in gas usage status (S107), recalculating predicted gas shortage date and scheduled delivery date (S108), adjusting gas delivery category (S109), and storing in gas delivery management file 22 (S110).

[0019] Identifying gas supply destination 10 (S101): Gas supply destinations 10-1, 10-2, ..., 10-N (Fig. 2, hereinafter simply referred to as "gas supply destination 10") are gas users who have contracts with a gas company, have gas containers installed, for example, on their eaves, and consume LPG from these gas containers. Gas users can be either individuals or corporations (businesses). The amount of LPG used is known from the guideline information of the gas meter. Identifying the gas delivery management file 22 (S102): The gas delivery management file 22 is an example of a management database that manages the gas usage, remaining gas amount, gas usage status, predicted date of gas shortage, etc. of the gas supply destination 10. The management server 4 (FIG. 2) identifies the gas delivery management file 22 of the gas supply destination 10 according to the gas supply destination 10 identified, for example, when obtaining gas meter reading information. Obtaining guideline information (S103): The guideline information may be obtained, for example, from a communication unit 88 (FIG. 11) installed on a gas meter of the gas supply destination 10, or from an external guideline information source 20 (FIG. 2). This guideline information source 20 includes an information collecting means for compiling guideline information collected from, for example, a gas meter and providing it to the management server 4 at a predetermined timing. Storing guideline information in the gas delivery management file 22 (S104): The management server 4 stores the guideline information acquired from the gas meter or guideline information source 20 in a fixed period of time, such as every day or every few days, in the gas delivery management file 22.

[0020] Calculation of gas usage information (S105): The management server 4 uses the acquired guideline information to calculate gas usage information for each gas user registered in the gas supply destination 10. This gas usage information includes gas usage calculated using values ​​from the guideline information, and information indicating the gas usage trend for each gas user. The management server 4 calculates the amount of change in gas usage for each specified period based on the calculated gas usage as the gas usage trend.

[0021] Monitoring the timing of gas delivery forecast calculation process (S106): The management server 4 has a timer function including a calendar function, monitors whether it is time to calculate a gas delivery forecast, and outputs a calculation instruction for a gas delivery forecast for the user under its management. The management server 4 may set a different value for each user as the monitoring timing, for example, or may set the same value for all users. For users for whom it is not yet time for calculation process, the management server 4 continues to obtain guideline information from the gas meter or guideline information source 20. Furthermore, when it is time for calculation process, the management server 4 sets a gas delivery forecast calculation process mode as the process for that user. Abnormal monitoring of gas usage status (S107): The management server 4 monitors the gas usage status within a specified calculation period, for example, by using gas usage information for a user set in the gas delivery forecast calculation processing mode. In this monitoring process, for example, standard information and a gas usage threshold value regarding the gas usage amount or gas usage trend for each day or for the entire specified period are read. Then, if the gas usage amount or gas usage trend falls outside the range of the gas usage threshold value, the management server 4 determines that the gas usage status is abnormal. Also, if the gas usage amount or gas usage trend falls within the range of the gas usage threshold value, the management server 4 determines that the gas usage status is normal. In this gas management system 2, if the gas usage status within a specified period is abnormal, the predicted gas shortage date and scheduled delivery date are recalculated, and if the gas usage status is within the normal range, the previously calculated predicted gas shortage date and scheduled delivery date are maintained. The gas usage threshold may be a value set for each user, or may be a common value for multiple users. The gas usage threshold may be a fixed value or may be a variable value depending on the season or the user's gas usage tendency. In addition, the gas management system 2 may proceed to the calculation process regardless of the gas usage status, for example, when calculating the first predicted gas delivery date after replacing a gas container, or when the previous predicted gas shortage date and scheduled delivery date have not been calculated.

[0022] Recalculation of predicted gas run-out date and scheduled delivery date (S108): The management server 4 calculates the predicted gas run-out date using the calculated gas usage information and gas volume information being supplied to the gas supply destination 10, and transitions to a mode for recalculating the scheduled delivery date using this predicted gas run-out date and delivery condition information. This gas volume information includes, for example, the total volume of the installed gas containers, as well as the volumes of some of the installed gas containers that are currently being supplied with gas. Adjustment of gas delivery category (S109): The management server 4 adjusts the gas delivery category based on the calculated predicted gas run-out date and scheduled delivery date. This gas delivery category is information that classifies the customer users by scheduled delivery date, and includes work instruction information that classifies delivery destination information and delivery order according to the number of delivery personnel and delivery capacity. The management server 4 adjusts the change in delivery date and delivery order for users whose predicted gas run-out date or scheduled delivery date has changed due to recalculation. Store in gas delivery management file (S110): The management server 4 stores the recalculated information on the predicted gas shortage date and scheduled delivery date, and the gas delivery division adjustment information in the gas delivery management file 22. In addition, the management server 4 notifies at least the adjusted gas delivery classification information to a terminal device owned by a gas container deliverer, a management server that manages this deliverer, and the like.

[0023] <Gas management system 2> Fig. 2A shows the gas management system 2. The configuration shown in Fig. 2A is an example, and the present invention is not limited to such a configuration. The gas management system 2 includes a management server 4, an information presentation unit 6, and an information input unit 8, as shown in FIG. The management server 4 is an example of a server device of the present invention that manages the monitoring of gas usage and usage status, gas shortage prediction, and gas container delivery processing, and is installed at a gas supplier that manages LPG supply and gas sales to each gas supply destination 10 (=10-1, 10-2, ..., 10-N), or at a management center that manages multiple gas suppliers. This management server 4 is composed of a computer, and in addition to receiving guideline information from the gas meters installed at each gas supply destination 10 and the guideline information source 20, has a communication function for notifying instruction information to the delivery party terminals 12 (12-1, 12-2, ..., 12-N). The management server 4 also has an information processing function for calculating usage information such as gas usage and usage trends of each gas supply destination 10 from the acquired guideline information. The information processing performed by the management server 4 includes, for example, a) Creation and updating of gas delivery management file 22 b) Management of gas supply destinations 10 c) Obtaining guideline information d) Monitoring the timing of calculation of gas usage e) Calculation of gas usage information, including gas usage amounts and gas usage trends f) Gas usage abnormality monitoring g) Adjustment of shipping categories h) Generation and presentation of instruction information i) Transmission of instruction information etc.

[0024] The information presentation unit 6 is a device having a function of displaying the management information and instruction information generated by the management server 4. The information presentation unit 6 includes, for example, as shown in B of Fig. 2, an administrator terminal 14 connected to the management server 4 by wire or wirelessly, as well as devices capable of sending and receiving information to and from the management server 4 and presenting information including the gas delivery management file 22, such as an LCD (Liquid Crystal Display) that displays a screen under the control of the management server 4. The information input unit 8 is an example of a means for inputting information to the management server 4, and may be, for example, the keyboard 18 of the administrator terminal 14, or a touch panel that integrates input operations with the monitor 16 that displays the screen.

[0025] A deliverer terminal 12 used by a deliverer of gas containers is connected to the gas management system 2. The deliverer terminal 12 is an information processing device such as a mobile phone or a tablet terminal, and may be carried or worn by the deliverer, or may be installed in a vehicle used for delivery. The deliverer terminal 12 is identified for each deliverer, and instruction information including classification information, delivery order, delivery route information, and the like for the gas supply destination 10 in charge on a specific delivery date is transmitted to the deliverer terminal 12. In addition, the deliverer terminal 12 may be connected to the management server 4, for example, constantly or periodically, and may transmit and receive the delivery status of the gas containers in real time. This allows the gas management system 2 to precisely grasp and manage the delivery status, and may notify the gas supply destination 10, which is the user, of the delivery status and delivery results.

[0026] <Gas Delivery Management File 22> FIG. 3 shows an example of the configuration of the gas delivery management file 22. The gas delivery management file 22 is an example of a management information database constituting the gas management system 2, such as gas container supply information, gas usage, and detection information of abnormal gas usage conditions for the gas supply destinations 10. This gas delivery management file 22 includes, for example, a plurality of files 22-1, 22-2, 22-3, ..., 22-N for each gas supply destination 10. This gas delivery management file 22 may be stored, for example, in a storage unit of the management server 4, or may be stored in an external database (DB) or external server (not shown). For example, in the gas container delivery management process, the management server 4 may read all of the information in the gas delivery management file 22, or data for each gas supply destination to be managed, from a database or external server. The gas delivery management file 22 includes, for example, a gas supply destination information section 24, a gas supply information section 26, a guideline information section 28, a gas usage information section 30, an accumulation information section 32, an abnormality information section 34, a recalculation information section 36, a predicted gas shortage date section 38, a gas delivery date section 40, and a delivery conditions section 42. The gas supply destination information unit 24 stores identification information for identifying the gas supply destination 10 who has contracted for the gas supply service. This identification information may include, for example, the name of the user who has contracted and the delivery address, as well as map data showing the area including the address and link information for accessing the map data. In addition, the gas supply destination information unit 24 may store attribute information related to gas supply. This attribute information may include, for example, information on whether the user who has contracted for gas supply has a personal contract or a corporate contract, and information on whether the user is a restaurant that uses a lot of gas. The gas management system 2 may use the attribute information for gas supply processing, for example, to set the priority of gas delivery processing high for a user who is expected to use a lot of gas when it is determined that the gas usage state is abnormal or the remaining gas amount is close to the gas shortage threshold.

[0027] Information such as the supply conditions of the gas containers is stored in the gas supply information section 26. For example, information such as a container installed capacity section 26-1 indicating the supplyable capacity of the gas containers installed in the gas supply destination 10, an installed number section 26-2, an exchange method section 26-3, and an average usage amount section 26-4 is stored in the gas supply information section 26. The indicator information unit 28 stores indicator information acquired from a gas meter or an indicator information source 20. In addition to storing the acquired indicator value itself, the indicator information unit 28 may also store link information to an occasional meter reading file 44 (FIG. 4) in which the indicator value is stored. Gas usage information for a predetermined period calculated based on guideline information is stored in gas usage information unit 30. This gas usage information unit 30 may store, for example, a calculated value of gas usage, or may record link information to an occasional meter reading file 44 (FIG. 4) in which gas usage is stored.

[0028] For example, the acquired guideline information and the calculated integrated value of the gas usage amount are stored in the cumulative information section 32. Here, for example, information such as the guideline information and the gas usage amount since the previous gas container replacement is cumulatively added up. The abnormality information section 34 stores monitoring information on whether or not the gas usage state of the gas supply destination 10 was abnormal within a set calculation period. The abnormality information section 34 may also store information on the number of times abnormality was determined in the past, in addition to the result of an abnormality determination of the gas usage state during the previous calculation period. When it is determined that the gas usage state is abnormal, the predicted gas run-out date and the delivery date of the gas container are stored in the recalculation information section 36. In addition to information indicating whether or not recalculation has been performed, the recalculation information section 36 may also store changes in the predicted gas run-out date and the scheduled delivery date due to recalculation.

[0029] The predicted gas runout date section 38 stores information on the predicted gas runout date calculated by the gas management system 2. The management server 4 calculates the predicted gas runout date using information such as the number of gas containers or the installed capacity of gas containers at each gas supply destination 10, and gas usage trends calculated from gas usage information. If the gas management system 2 determines that the gas usage state during the calculation period is abnormal, it recalculates the predicted gas runout date and updates the information in the predicted gas runout date section 38. If the gas management system 2 determines that the gas usage state is not abnormal, it only needs to store the predicted gas runout date information that has already been calculated and stored. The gas delivery date section 40 stores gas container replacement instruction information for each gas supply destination 10. The gas delivery date section 40 stores, for example, past gas container delivery dates as well as a scheduled gas delivery date set based on a predicted gas runout date. The scheduled gas delivery date is set using, for example, a predicted gas runout date and delivery condition information. The gas delivery date section 40 may also be associated with a delivery classification table 64 (FIG. 6) that classifies the gas supply destination 10 from other gas supply destinations 10 based on, for example, delivery area and delivery conditions. The delivery condition section 42 stores delivery condition information for each gas supply destination 10. The delivery conditions are associated with, for example, a delivery condition database 54 (FIG. 5), and include information such as the delivery time from other gas supply destinations 10 and the time required for gas container replacement work.

[0030] Gas delivery management file 22 may be created for each user who is a gas supply destination 10, but may be created for multiple users together. In this case, gas delivery management file 22 may group users who have nearby delivery destinations, and record information such as gas guideline information and abnormality information together.

[0031] <Meter Reading File 44> FIG. 4 shows an example of the configuration of a random meter reading file. The occasional meter reading file 44 is an example of an information storage unit in which, for example, the acquired guideline information is stored, and the gas usage calculated based on the guideline information is stored. As shown in FIG. 4, the occasional meter reading file 44 has a plurality of files 44-1, 44-2, 44-3, . . . , 44-N for each of the gas supply destinations 10-1, 10-2, 10-3, . . . , 10-N. The occasional meter reading file 44 includes, for example, a meter reading date and time section 46, a gas meter guide section 48, a gas usage amount since the previous time section 50, and a remaining gas amount information section 52, and some or all of these information sections are linked to the gas delivery management file 22. The occasional meter reading file 44 may be stored in, for example, a memory section of the management server 4, or in an external database outside the management server 4, or in another management server.

[0032] The meter reading date and time unit 46 stores information such as the date when the gas meter reading information was obtained, or the meter reading date stored in the gas meter together with the meter reading value. The calculation process for the predicted gas runout date uses, for example, the date and time information stored in the meter reading date and time unit 46, gas usage trends, remaining gas amount, etc. The gas meter indicator unit 48 stores indicator information acquired from the gas supply destination 10 or the indicator information source 20. This indicator information is basic information for calculating the amount of gas used at the gas supply destination 10, and is read every day or at predetermined intervals. The gas usage amount calculated for each predetermined period using the guideline information is stored in the gas usage amount since the previous time section 50. This period is the timing for executing the calculation process of the gas usage amount, and may be every day if new guideline information is obtained, or the number of days for obtaining several pieces of guideline information may be set. The remaining gas amount information section 52 stores the remaining gas amount in the gas supply destination 10, which is calculated using the integrated value of the gas usage amount calculated from the previous gas container replacement.

[0033] <Shipping Terms Database 54> FIG. 5 shows an example of the delivery terms database. This delivery condition database 54 is an example of a database that records conditions such as the transportation and replacement work of gas containers, information on the time required, etc., and is used for setting the replacement date and delivery category of the gas container. The delivery condition database 54 includes, for example, a gas supply destination section 56, a delivery condition section 58, a required time section 60, and a recorded date and time section 62, as shown in FIG. The gas supply destination section 56 stores identification information for specifying the gas supply destination 10, and may be associated with the gas supply destination information section 24 of the gas delivery management file 22 by a link or the like, for example. The delivery condition section 58 stores past delivery records for each gas supply destination 10. This delivery record may record, for example, delivery route information from the office or delivery base where gas containers are refilled or from other gas supply destinations 10, weather conditions at the time of delivery, information on roads and congestion on the delivery route, the distance to the gas container stock location within the premises of the gas supply destination 10, building information, the size of the work space, and the like. The required time section 60 stores past performance information on the time required for the delivery process of a gas container. Furthermore, by taking into account information on delivery conditions, for example, it is possible to grasp the difference in the time required for the delivery process due to differences in weather in past delivery results to the same gas supply destination 10, and it is possible to estimate the time required for the delivery process of a gas container by referring to the weather conditions on the day of delivery or a weather forecast obtained when the delivery date was set. In the recorded date and time section 62, information on the date and time when a past delivery process was performed or information on the date and time when the delivery performance information was registered is registered.

[0034] <Shipping classification table 64> 6, the delivery classification table 64 is an example of delivery instruction information for delivery groups classified by one or more gas supply destinations 10. This delivery classification table 64 is generated, for example, for each deliverer registered in the gas management system 2, and is periodically notified to the deliverer terminal 12. The delivery classification table 64 has, for example, a gas supply destination section 66, an installation location section 68, a container installation capacity section 70, an installation number section 72, an exchange method section 74, a predicted gas shortage date section 76, and a delivery date section 78 for each delivery group. The gas supply destination section 66 stores identification information for specifying the gas supply destination 10, and may be associated with the gas supply destination information section 24 of the gas delivery management file 22 by a link or the like, for example. The installation location section 68 stores a map of the installation location, installation location information, and the like for each gas supply destination 10. The container installation capacity section 70 stores information on the gas supply capacity of the installed gas container for each gas supply destination 10. This container installation capacity section 70 may be associated with the container installation capacity section 26-1 of the gas delivery management file 22 by a link or the like. The installed number section 72 stores information on the number of gas containers installed at the gas supply destination 10. This installed number section 72 may be associated with the installed number section 26-2 of the gas delivery management file 22 by a link or the like. The replacement method section 74 stores a replacement instruction for a gas container. This replacement instruction includes, for example, instruction information on whether to replace all installed gas containers or only a set number of containers based on a contract with the gas supply destination 10, as well as instruction information for identifying a gas container to be replaced among multiple installed gas containers. This replacement method section 74 may be associated with the replacement method section 26-3 of the gas delivery management file 22 by a link or the like. The predicted gas shortage date section 76 stores a predicted gas shortage date calculated from gas usage information based on the guideline information. In addition to the calculated predicted date information, the predicted gas shortage date section 76 may store priority information (not shown) indicating the urgency of replacement that is set based on the predicted date. The predicted gas shortage date section 76 may be associated with the predicted gas shortage date section 38 of the gas delivery management file 22 by a link or the like. The delivery date section 78 stores a date instruction for executing the delivery process of the gas container. This delivery date instruction may be set, for example, for each group. In addition, for gas supply destinations 10 for which delivery was not completed on the set date due to, for example, weather conditions or delivery route conditions, the management server 4 refers to the information in the predicted gas shortage date section 76 and assigns them to another delivery group.

[0035] <Gas distribution management processing> 7 shows an example of a process for determining and recalculating a predicted date for gas shortage based on a gas usage trend. The process contents and determination criteria shown in FIG. 7 are merely examples, and the present invention is not limited to such process contents and process procedures. The management server 4 transitions to a gas usage status monitoring processing mode and monitors whether the gas usage status is abnormal. The management server 4 recalculates the predicted gas runout date tx based on the monitoring results, and adjusts the scheduled gas delivery date according to this predicted gas runout date tx. The management server 4 compares, for example, the gas usage LG1, LG2, ..., LGn between monitoring days t1, t2, ..., tn for each set number of days x with the set gas usage threshold LGX to determine whether the gas usage is abnormal or not (Figure 8). 7A, on monitoring date t2, the management server 4 calculates a predicted gas run-out date tx1 based on the gas usage LG1 from monitoring date t1 to monitoring date t2. Next, when the management server 4 determines on monitoring date t3 that the gas usage LG2 from monitoring date t2 to monitoring date t3 satisfies the condition set by the gas usage threshold LGX, it determines that the gas usage state is normal and adopts the predicted gas run-out date tx1 calculated earlier. In response to this, the management server 4 determines that the gas usage state is abnormal if it determines on monitoring date t3 that the gas usage amount LG2 from monitoring date t2 to monitoring date t3 does not satisfy the condition based on the gas usage amount threshold LGX, for example as shown in B of Fig. 7. The management server 4 then recalculates a new predicted gas runout date tx2 using the gas usage amount LG2 as a gas usage trend, and stores the calculated predicted gas runout date tx2 in the recalculation information section 36 or the predicted gas runout date section 38 of the gas delivery management file 22. The management server 4 makes adjustments, such as advancing or delaying the gas delivery date, depending on the variation value between the recalculated predicted gas runout date tx2 and the original predicted gas runout date tx1.

[0036] For example, the management server 4 may use the predicted gas shortage dates tx1 and tx2 as a basis for adjusting the gas delivery date and set the gas delivery date several days before those dates. The management server 4 may also set a remaining gas amount threshold LGE for the remaining gas amount LGr in the gas container, and may set the gas delivery date by predicting the day when the remaining gas amount LGr will be equal to or less than the remaining gas amount threshold LGE based on the predicted gas shortage dates tx1 and tx2. The remaining gas amount LGr can be calculated, for example, by the following formula. The management server 4 calculates the remaining gas amount LGr from the gas usage amount LG calculated based on the change in the guideline value of the gas meter or the guideline information source 20 and the gas volume information LM of the gas supply destination 10. If the monitoring date t1 is immediately after the gas container is replaced, the remaining gas amounts LGr1, LGr2, ...LGrn at the monitoring dates t1, t2, ..., tn are expressed as follows: LGr1 = LM (1) LGr2 = LM - LG1 (2) LGr3 = LGr2 - LG2 (3) LGrn=(LGr(n-1))-(LG(n-1)) ···(4) It becomes.

[0037] <Gas usage status monitoring process> FIG. 8 shows an example of a process for monitoring the gas usage state based on the gas usage amount of a gas supply destination. The management server 4 calculates the amount of gas used for the gas supply destination 10 from the acquired guideline information, for example, and stores the amount of gas used LG in the gas delivery management file 22. In FIG. 8, for example, the horizontal axis represents the date of measurement, and the vertical axis represents the daily gas usage amount LG. The monitoring dates t1, t2, t3, ..., tn are examples of gas delivery prediction calculation processing timings, and the set number of days x is set to, for example, 5 days. The set number of days x may be set to, for example, the same number of days for all gas supply destinations 10, or may be different for each gas supply destination 10. In the gas delivery management processing, the total value of the gas usage LG from monitoring dates t1 to t2 may be used as the gas usage LG1, and the total value of the gas usage LG from monitoring dates t2 to t3 may be used as the gas usage LG2 to calculate the remaining gas amount LGr.

[0038] In monitoring the gas usage status, for example, the gas usage LG calculated from the guideline value is used as a condition based on the gas usage threshold LGX to make a judgment. That is, the management server 4 judges, for example, as the calculation processing timing, whether or not there is a day on which the gas usage LG exceeds the gas usage threshold LGX among the monitoring days t1, t2, t3, ... tn. For example, as shown in FIG. 8, there is no day between monitoring date t1 and monitoring date t2 on which the gas usage amount LG exceeds the gas usage amount threshold LGX, so the management server 4 determines that the gas usage state is normal. In addition, the management server 4 determines that the gas usage state is abnormal because, for example, between monitoring date t2 and monitoring date t3, the gas usage amount LG exceeds the gas usage amount threshold LGX on one day. As a result, the management server 4 transitions to a recalculation processing mode in which the predicted gas runout date is recalculated and the delivery classification is adjusted.

[0039] The gas usage threshold LGX may be a fixed value, or may be a variable value depending on the time of determination, the past gas usage state, and the like.

[0040] <About shipping categories> FIG. 9 shows an example of a process for sorting gas bottle deliveries. The management server 4 classifies the gas supply destinations 10 (here, 16 users, No. 01 to No. 16) into a plurality of groups based on conditions such as the address of the gas supply destinations 10 and the distance from the base that supplies gas containers, together with the calculated predicted date of gas shortage. The same gas delivery date is set for these groups. Furthermore, the management server 4 performs a process of changing the delivery category in response to an adjustment of the delivery date for the gas supply destination 10 for which the predicted gas run-out date has been recalculated by the gas usage status monitoring process. This process of changing the delivery category may involve, for example, adding or deleting a gas supply destination 10 based on the delivery date. In addition, in the change process, gas supply destinations 10 may be swapped between groups in order not to increase the number of registered gas supply destinations 10, for example, depending on the delivery capacity of the delivery person in charge of the group. In swapping the delivery category, for example, a gas supply destination 10 whose delivery date has some margin relative to the predicted gas run-out date may be selected.

[0041] The management server 4 may then update the delivery category table 64 for the gas supply destination 10 whose delivery category has been changed, and may also output a change notification to the deliverer and the gas supply destination 10 whose delivery category has been changed.

[0042] <Delivery management process> Fig. 10 shows an example of a gas container delivery management process. The process shown in Fig. 10 is an example of a gas delivery processing method and program of the present invention, and the present invention is not limited to such process contents and process procedures. In this delivery management process, the management server 4 acquires guideline information (S201), calculates the gas usage amount LG (S202), and stores the guideline information and the gas usage amount LG in the gas delivery management file 22 (S203). If the monitoring day t has not arrived (NO in S204), the management server 4 returns to S201 and continues gas meter reading. If the monitoring day t has arrived (YES in S204), the management server 4 reads the gas usage amount threshold LGX (S205), and determines whether there has been a day on which the gas usage amount LG exceeded the gas usage amount threshold LGX (S206). If there is a day when the gas usage threshold LGX is exceeded (YES in S206), the management server 4 calculates the gas usage trend for the set number of days x (S207), and uses the calculated value to calculate the predicted gas run-out date (S208). The gas usage trend may be, for example, the total value of the gas usage LG for x days, or the average gas usage per day. In the process of calculating the predicted gas run-out date, for example, the gas usage amount as well as information such as the gas capacity information LM of the gas supply destination 10 and the number of installed gas containers may be referenced to calculate the number of days when the remaining gas amount LGr in the gas container will be 0 or less than the remaining gas amount threshold LGE.

[0043] The management server 4 adjusts the delivery date to the gas supply destination 10 based on the new predicted gas run-out date (S209). The delivery date can be adjusted, for example, by setting it several days before the predicted gas run-out date based on the calculated gas usage trend. Furthermore, the management server 4 generates or adjusts a delivery group with other gas supply destinations 10 based on the set delivery date.

[0044] Furthermore, if there is no day on which the gas usage threshold LGX is exceeded (NO in S206), the management server 4 maintains the preset predicted gas shortage date and returns to the guideline information acquisition process (S210).

[0045] <Advantages of the First Embodiment> Such a configuration provides the following effects. (1) By frequently reading the gas meter, monitoring the gas usage status and gas shortage at specified time periods, and adjusting the gas delivery process, it is possible to grasp the gas usage status in detail and reduce the load on the management server caused by the monitoring process. (2) By monitoring gas usage through frequent meter reading, it is possible to set delivery dates for gas cylinders with a low remaining gas rate, thereby reducing the burden on workers. (3) By adding delivery conditions for the gas supply destination 10 and performing setting and adjustment processing of delivery categories, it is possible to formulate delivery instructions that reduce the time and burden required for delivery.

[0046] Second Embodiment Fig. 11 is a diagram showing a gas management system 2 according to a second embodiment. In Fig. 11, the same parts as in Fig. 2 are denoted by the same reference numerals. Each gas supply destination 10 is provided with a plurality of gas containers 80-1, 80-2 provided by a gas company, or a bulk container that is larger than a gas container and is fixed to the eaves of a user's house, etc. The gas containers 80-1, 80-2 are connected to a gas appliance 84 via a gas meter 82. A switch 86 is also installed between the gas containers 80-1, 80-2 and the gas meter 82, and LPG is supplied to the gas appliance 84 from either the gas container 80-1 or 80-2. The gas appliance 84 is a device that consumes gas, such as a gas water heater or a gas stove.

[0047] The gas meter 82 is, for example, a microcomputer meter, and measures the amount of LPG passing through. This passing amount is the guideline information. The communication unit 88 is connected to the gas meter 82, and transmits the guideline information provided from the gas meter 82 to the relay unit 90. The relay unit 90 is connected to a network 92 such as the Internet by wired or wireless connection. The guideline information is provided to the guideline information source 20 through the relay unit 90. The management server 4 can acquire guideline information from the gas supply destination 10 through the relay unit 90 , or can be provided with guideline information from the guideline information source 20 .

[0048] The management server 4 is configured as a computer equipped with a communication function. The management server 4 is equipped with a processor 94, a storage unit 96, an input / output unit (I / O) 98, a timer 100, and a communication unit 102. The processor 94 performs the above-mentioned information processing using a gas management program and the like, using an OS (Operating System) in the storage unit 96. In addition to the OS, the storage unit 96 stores a gas management program and a database including the gas delivery management file 22. The storage unit 96 is provided with memory elements such as a ROM (Read-Only Memory) and a RAM (Random-Access Memory) as storage means for various pieces of information. The timer 100 has a calendar function and a clock function controlled by the processor 94, and provides the processor 94 with date and time information for counting the set number of days x, which is the interval between monitoring dates t. The communication unit 102 is controlled by the processor 94 and is capable of communicating with the communication unit 88 of the gas supply destination 10, the relay unit 90, the distributor terminal 12, the manager terminal 14, and the guideline information source 20 via wired or wireless connection.

[0049] <Delivery person terminal 12> 12 shows the hardware of the deliverer terminal 12 that outputs instructions for delivering gas containers, etc. As described above, a smartphone or tablet terminal can be used as a computer equipped with a communication function for this deliverer terminal 12. This deliverer terminal 12 includes, for example, a processor 104, a memory unit 106, an I / O 108, a communication unit 110, an information presentation unit 112, and an operation input unit 114. Processor 104 is an example of a processing unit that processes gas management information, and transmits and receives information to and from management server 4 and administrator terminal 14 in order to process information such as a gas management program based on the OS in memory unit 106. Memory unit 106 stores various programs such as the gas management program in addition to the OS. Memory unit 106 uses memory elements such as ROM and RAM. The I / O 108 is used for sending and receiving information between the processor 104 and the communication unit 110, the information presentation unit 112, or the operation input unit 114. The communication unit 110 is capable of communicating with the management server 4 and the manager terminal 14 using public lines, as well as with the communication unit 88 on the gas meter side. The information presentation unit 112 is used to present information such as the gas delivery management file 22 provided by the management server 4 and delivery instruction information for gas containers. The operation input unit 114 is used for inputting identification information of the gas supply destination 10, requesting delivery instruction information, requesting location information of the gas supply destination 10, inputting gas container delivery progress information, and the like.

[0050] <Providing information on gas distribution management> FIG. 13 shows an example of information presentation for gas delivery management. 13, the management server 4 generates a management information screen 120 related to gas delivery management and displays it on the information presentation unit 6. This information presentation unit 6 is composed of, for example, a monitor of the management server 4, as well as a monitor 16 of an administrator terminal 14 connected to the management server 4 by wire or wirelessly. On this management information screen 120, for example, a gas management information display section 122, a guideline information display section 124, and a delivery management information display section 126 are set. The gas management information presentation unit 122 presents the above-mentioned gas delivery management file 22 for each gas supply destination 10 . The guideline information presentation unit 124 presents, for example, the meter reading file 44 at any time, which includes the guideline value acquired by the management server 4, as well as the calculated gas usage amount, remaining gas amount information, and the like. The delivery management information presentation unit 126 presents, for example, a part or all of the delivery category table 64 including information such as delivery group category information, delivery date, and predicted date of gas shortage for the gas supply destination 10 to be managed.

[0051] <Information presentation to the deliverer terminal 12> FIG. 14 shows an example of a delivery instruction screen displayed on the deliverer terminal 12. The information presentation unit 112 of the deliverer terminal 12 displays a delivery instruction screen 128 including information on the gas supply destinations 10 for which each deliverer is responsible. This delivery instruction screen 128 includes one or more groups included in the delivery classification table 64, such as gas supply destination information, number of containers information, and replacement method. Priority information 129 may also be set for the gas supply destinations 10 on the delivery instruction screen 128. This priority information 129 is an example of instruction information set by the management server 4, and indicates, for example, the urgency of gas container delivery among the grouped gas supply destinations 10. As a result, in the delivery process, for example, delivery to gas supply destinations 10 with high priority may be given priority based on an instruction from the management server 4, and the delivery order may also be set based on the gas supply destinations 10 with high priority and by combining gas supply destinations 10 that are close along the delivery route.

[0052] In addition, the delivery instruction screen 128 may allow the user to input, for example, using the operation input unit 114 of the delivery person terminal 12, work reports such as delivery completion or delivery failure, as well as progress information such as delays in the delivery schedule due to changes in weather or road conditions.

[0053] <Information provided to gas supplier 10> FIG. 15 shows an example of an information display screen for a gas supply destination. Display units 130A, 130B of an information terminal used by a user of gas supply destination 10 display user gas capacity management screens 132A, 132B, for example, as shown in Fig. 15. These gas capacity management screens 132A, 132B are notified, for example, periodically, or presented when the user requests or accesses management server 4. The information terminal used by the user of gas supply destination 10 may be a PC, mobile phone, mobile information terminal, or the like, which is capable of connecting to management server 4 or other information presentation servers via communication. Gas volume management screen 132A shows information about gas supply destination 10, where multiple gas containers are installed, as shown in A of Fig. 15. Gas volume management screen 132B shows information about gas supply destination 10, where gas is filled into a large gas container installed on the eaves of gas supply destination 10, as shown in B of Fig. 15. These gas volume management screens 132A, 132B include remaining gas amount display sections 134A, 134B in the gas container, gas container delivery date information 136A, refill date information 136B, and predicted gas shortage date information 138A, 138B.

[0054] <Gas distribution management processing> 16 shows a processing sequence of gas delivery management using the gas management system 2. This gas delivery management processing is an example of the gas delivery processing method and program of the present invention, and the present invention is not limited to such processing contents and processing procedures. Guideline information for the gas supply destination 10 is transmitted from the communication unit 88 or the guideline information source 20 (S301) and provided to the management server 4. When the management server 4 is provided with the guideline information, it identifies the gas supply destination 10 (S302), and identifies the gas delivery management file 22 related to the identified gas supply destination 10 (S303). When the management server 4 acquires the guideline information (S304), it periodically calculates the gas usage amount LG and gas usage information based on the guideline information (S305), and stores them in the gas delivery management file 22.

[0055] The management server 4 calculates the gas usage trend of the gas supply destination 10 based on the gas usage amount LG and the like during the interval of the set number of days x, and also calculates the remaining gas amount LGr by referring to information such as the gas capacity of the gas supply destination 10, and monitors whether the remaining gas amount LGr is equal to or less than the set remaining gas amount threshold value LGE (S306). If the remaining gas amount LGr has not reached the threshold value LGE (NO in S306), the management server 4 judges whether it is time to process the gas delivery forecast calculation (S307). If it is time to process the gas delivery forecast calculation (YES in S307), the management server 4 transitions to abnormality monitoring of the gas usage state (S308), and if it is not time to process the gas delivery forecast calculation (NO in S307), it returns to obtaining the guideline information (S304) and repeats the calculation of the gas usage amount LG. In the abnormality monitoring of the gas usage state, as described above, the daily gas usage amount LG or the calculated average gas usage amount is compared with the gas usage amount threshold value LGX, and the judgment may be made using the amount of change in the daily gas usage amount LG, etc.

[0056] When the management server 4 determines that the gas usage status is abnormal (YES in S308), it recalculates the predicted gas shortage date and delivery date (S309), and adjusts the gas delivery category by classifying each gas supply destination 10 according to predetermined conditions (S310). The conditions for the delivery category of the gas supply destination 10 may be determined based on delivery conditions such as the delivery destination address and delivery route as well as the delivery date. Then, the management server 4 creates a gas delivery instruction and transmits it to the deliverer terminal 12 (S311). When the management server 4 determines that the gas usage status is not abnormal (NO in S308), it creates a gas delivery instruction while maintaining the predicted gas shortage date and delivery date that have already been set, and sends it to the deliverer (S311).

[0057] Furthermore, when the management server 4 determines that the remaining gas amount LGr in the gas container is equal to or less than the threshold value LGE (YES in S306), it transitions to a gas delivery section adjustment process (S310) and adjusts the gas delivery section so that the gas container is delivered with priority without calculating the predicted gas run-out date or delivery date, and creates and transmits a gas delivery instruction to the deliverer (S311). In adjusting the gas delivery section when it is determined that the amount is equal to or less than the threshold value LGE, for example, a gas supply destination that is likely to run out of gas is inserted into the delivery section on the day of the determination or in the immediate future.

[0058] When the deliverer terminal 12 receives the gas delivery instruction from the management server 4 (S312), it starts the delivery and replacement process of the gas container according to the instruction. In addition, the delivery person terminal 12 can receive the management information screen 120, the delivery instruction screen 128, the gas capacity management screens 132A and 132B, etc. by accessing the management server 4 or requesting the progress of gas delivery management and management information from the management server 4.

[0059] <Advantages of the second embodiment> According to this configuration, the following effects can be expected. (1) The same effects as in the first embodiment can be obtained. (2) The accuracy of gas shortage prediction based on gas usage trends can be improved, and gas delivery processing can be performed even when the remaining gas amount is small. (3) By combining gas delivery management based on gas usage with monitoring of remaining gas, the risk of running out of gas can be reduced even if there is a sudden increase in gas consumption.

[0060] [Modifications]

[0061] Modifications of the embodiment described above are listed below.

[0062] (1) In the above embodiment, the gas management system 2 performs a gas usage monitoring process to determine whether the gas usage is abnormal based on whether there is a day on which the gas usage LG exceeds the gas usage threshold LGX within the set number of days x, but this is not limited to the above. In this monitoring process, for example, if there are multiple days on which the gas usage LG exceeds the gas usage threshold LGX, the gas usage may be determined to be abnormal, or the total value of the gas usage LG calculated within the set number of days x or the average value for each day may be used to determine whether the gas usage is abnormal. In this way, the gas usage for several days and its average value are obtained, and the gas usage is understood based on the gas usage trend within the monitoring period, thereby reducing the impact of temporary increases and decreases in gas usage, and reducing the load of recalculating the predicted gas run-out date and adjusting the delivery date.

[0063] (2) In the above embodiment, the management server 4 sets an upper limit gas usage threshold LGX as abnormality monitoring, and determines that the gas usage LG is greater than this value as abnormality, but this is not limited to the above. In determining abnormality, for example, a lower limit gas usage threshold LGX may be set, and a case where the gas usage LG is less than the gas usage threshold LGX may be determined as abnormal. The management server 4 may also set at least two gas usage thresholds LGX, an upper limit and a lower limit, and determine that the gas usage LG is outside the range of these thresholds LGX as abnormal. That is, in gas delivery management, for example, when gas usage is reduced, if the previously set delivery date is maintained, the remaining gas amount will increase, which will increase the burden on the operator. Therefore, in gas delivery management, a gas usage that causes a discrepancy between the previously calculated gas shortage forecast date and the set delivery date may be determined as an abnormality in the gas usage state.

[0064] (3) In the above embodiment, the set number of days x is a fixed value as the period for the timing of the gas delivery forecast calculation process for monitoring the gas usage state, but this is not limited to the above. The set number of days x may be a variable value that takes into consideration, for example, the past gas usage record of the gas supply destination 10. In other words, if the number or frequency of times that the gas usage state of the gas supply destination 10 to be monitored has been determined to be abnormal in the past is low, the management server 4 determines that there is little possibility of abnormal gas usage occurring and sets the set number of days x to a large value, thereby reducing the load of recalculating the predicted gas run-out date and delivery date. In addition, the management server 4 may vary the set number of days x by season or month, for example, based on the past gas usage history of the gas supply destination 10.

[0065] Furthermore, the management server 4 may vary the set number of days x, which is the monitoring period of the gas usage state, so as to decrease as the remaining gas amount LGr decreases immediately after the gas container is replaced. In this way, by setting the set number of days x to be longer when the risk of running out of gas is low, such as immediately after the gas container is replaced, the frequency of the monitoring process of the gas usage state and the recalculation of the predicted date of running out of gas can be reduced, thereby reducing the processing load. In addition, when gas usage progresses and the remaining gas amount LGr becomes small, the management server 4 may monitor the gas usage state more frequently by decreasing the set number of days x, thereby improving the accuracy of the predicted date of running out of gas even when the gas usage amount increases suddenly, and reducing the risk of running out of gas. In addition, the set number of days x may be set in consideration of, for example, differences in the gas usage pattern at the gas supply destination 10. For example, the set number of days x may be different for a dining point where gas usage is high and for a company or office where gas usage is low, to determine an abnormal state of gas usage.

[0066] (4) In the above embodiment, the same gas usage threshold value LGX is used for all gas supply destinations 10 to determine whether or not there is an abnormality in the gas usage state. However, this is not limited to the above. The gas usage threshold value LGX may be varied based on, for example, the past gas usage history of the gas supply destinations 10.

[0067] As described above, the most preferred embodiment of the present invention has been described. The present invention is not limited to the above description. Various modifications and changes are possible for those skilled in the art based on the gist of the invention described in the claims or disclosed in the description for carrying out the invention. It goes without saying that such modifications and changes are included in the scope of the present invention. [Industrial Applicability]

[0068] The present invention is useful because it monitors the gas usage status of a gas supply destination over a specified period of time and recalculates the predicted gas shortage date and delivery date if the usage status is abnormal, thereby reducing the processing load of recalculation while reducing the risk of gas shortage. [Explanation of symbols]

[0069] 2 Gas management system 4 Management Server 6 Information presentation section 8 Information input section 10, 10-1, 10-2, 10-3, ..., 10-N Gas supply destination 12, 12-1, 12-2, 12-3, ..., 12-N Delivery terminal 14 Administrator terminal 20 Guidance sources 22, 22-1, 22-2, 22-3, . . ., 22-N Gas distribution management file 24 Gas Supply Information Department 26 Gas Supply Information Department 28 Guidelines Information Department 30 Gas Usage Information Section 32 Estimation Information Department 34 Anomaly Information Department 36 Recalculation Information Department 38, 76 Gas shortage forecast 40 Gas Delivery Service 42 Delivery conditions section 44, 44-1, 44-2, 44-3, 4-N Meter Reading File 46 Meter Reading Date and Time Section 48 Gas meter pointer 50 Gas usage from last time 52 Remaining gas amount information section 54 Shipping Terms Database 56, 66 Gas supply destination 58 Delivery conditions section 60 Time Required 62 Recording date and time section 64 Shipping Category Table 68 Installation Location Section 70 Container installation capacity section 72 Number of units installed 74 Replacement method section 78 Delivery date section 80-1, 80-2 Gas bottles 82 Gas meter 84 Gas appliances 86 Switch 88 Communications Department 90 Relay Section 92 Network 112 Information Presentation Department 114 Operation input section 120 Management information screen 122 Gas Management Information Presentation Section 124 Guideline Information Presentation Department 126 Delivery management information presentation section 128 Delivery instruction screen 129 Priority information 130A, 130B display section 132A, 132B Gas Capacity Management Screen 134A, 134B Remaining gas amount display section 136A Delivery Date Information 136B Filling date information 138A, 138B Information on predicted gas shortage dates

Claims

1. A guideline information acquisition unit acquires guideline information of a gas supply destination; calculating gas usage information that indicates a trend of gas usage during a set calculation period; Calculating a predicted date of gas shortage using the gas usage information and the gas volume information of the gas supply destination; setting a delivery category and a scheduled delivery date based on the predicted date of gas shortage and the delivery condition information; setting a lower limit gas usage threshold representing a lower limit of the gas usage, comparing the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, determining that the gas usage is abnormal if the calculation period includes a day when the gas usage falls below the lower limit gas usage threshold, and calculating new gas usage information; a step of recalculating a predicted date of gas shortage based on the newly calculated gas usage information for the gas supply destination determined to be abnormal, and adjusting the delivery category; 13. A method of gas distribution processing comprising:

2. 2. The gas distribution processing method according to claim 1, further comprising a step of varying the lower limit gas usage threshold based on a gas usage history of the gas supply destination.

3. A guideline information acquisition unit that acquires guideline information of a gas supply destination; a server device which calculates gas usage information indicating a trend in gas usage during a set calculation period, calculates a predicted gas run-out date using the gas usage information and gas capacity information of the gas supply destination, sets a delivery category and a scheduled delivery date according to the predicted gas run-out date and delivery condition information, sets a lower limit gas usage threshold indicating a lower limit of the gas usage, compares the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, and determines that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, calculates new gas usage information, and for the gas supply destination determined to be abnormal, recalculates the predicted gas run-out date using the newly calculated gas usage information, and adjusts the delivery category; 16. A gas distribution and processing system comprising:

4. 4. The gas distribution processing system according to claim 3, wherein the server device varies the lower limit gas usage threshold value according to a gas usage history of the gas supply destination.

5. A program for realizing the program by a computer, comprising: a function for acquiring guideline information of a gas supply destination; A function for calculating gas usage information that shows the trend of gas usage during a set calculation period; A function of calculating a predicted date of gas shortage using the gas usage information and the gas capacity information of the gas supply destination; A function of setting a delivery category and a scheduled delivery date based on the predicted gas runout date and the delivery condition information; a function of setting a lower limit gas usage threshold that indicates a lower limit of the gas usage, comparing the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, determining that the gas usage is abnormal if the calculation period includes a day when the gas usage falls below the lower limit gas usage threshold, and calculating new gas usage information; A function of recalculating a predicted date of gas shortage based on the newly calculated gas usage information for the gas supply destination determined to be abnormal, and adjusting the delivery category; A program for causing the computer to realize the above.

6. The program according to claim 5, further comprising causing the computer to realize a function of varying the lower limit gas usage threshold based on a gas usage history of a gas supply destination.

7. A guideline information acquisition unit that acquires guideline information of a gas supply destination; a processing unit that calculates gas usage information indicating a trend in gas usage during a set calculation period, calculates a predicted gas run-out date using the gas usage information and gas capacity information of the gas supply destination, sets a delivery category and a scheduled delivery date based on the predicted gas run-out date and delivery condition information, sets a lower limit gas usage threshold indicating a lower limit of the gas usage, compares the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, and determines that the gas usage is abnormal if the calculation period includes a day when the gas usage is below the lower limit gas usage threshold, calculates new gas usage information, and for the gas supply destination determined to be abnormal, recalculates the predicted gas run-out date using the newly calculated gas usage information, and adjusts the delivery category; A server device comprising:

8. The server device according to claim 7 , wherein the processing unit varies the lower limit gas usage threshold value based on a gas usage history of the gas supply destination.

9. A recording medium storing a program for realizing the program by a computer, A function to obtain guideline information for gas supply destinations; A function for calculating gas usage information that shows the trend of gas usage during a set calculation period; A function of calculating a predicted date of gas shortage using the gas usage information and the gas capacity information of the gas supply destination; A function of setting a delivery category and a scheduled delivery date based on the predicted gas runout date and the delivery condition information; a function of setting a lower limit gas usage threshold that indicates a lower limit of the gas usage, comparing the daily gas usage during the calculation period acquired based on the guideline information with the lower limit gas usage threshold of the gas supply destination, determining that the gas usage is abnormal if the calculation period includes a day when the gas usage falls below the lower limit gas usage threshold, and calculating new gas usage information; A function of recalculating a predicted date of gas shortage based on the newly calculated gas usage information for the gas supply destination determined to be abnormal, and adjusting the delivery category; A recording medium storing a program for causing the computer to realize the above.

Images