Cylinder management method and program

Abstract

To provide a technique for surely managing the position of a cylinder.SOLUTION: The cylinder 500 is filled with the gas (liquefied gas) in the filling facility 300, is transferred from the filling facility 300 to the customer 400 in a state of being mounted on the vehicle 200, and is delivered to the customer 400. When the gas in the cylinder 500 is consumed by the customer 400, the cylinder 500 is returned to the filling facility 300. In the filling facility 300, the cylinder 500 is filled with the gas again, and then the cylinder 500 is delivered to the customer 400 again. The gas cylinder 500 is provided with a GPS logger. The GPS logger transmits the position information of the cylinder 500 to the information processing apparatus 100.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to cylinder management. [Background technology]

[0002] Cylinders filled with fluids such as liquefied gas are shipped from the fluid manufacturer to the customer and delivered to the place of use (homes, businesses, factories, construction sites, etc.). Once the fluid in the cylinder is used, the cylinder is collected by the manufacturer and a new cylinder is shipped to the customer. In other words, the cylinder is replaced at the customer's site.

[0003] Various technologies have been disclosed for managing such cylinders. For example, JP 2013-520742 A (Patent Document 1) discloses a method for creating tracking information for a cylinder by attaching a mark to the cylinder (gas cylinder), associating the mark with identification information for the cylinder, reading the mark during a manufacturing process, etc., and identifying each cylinder based on the read mark.

[0004] In addition, Patent Publication No. 2020-056416 (Patent Document 2) discloses a system in which a valve equipped with a transmitter that transmits a signal indicating the current location is attached to a cylinder, and the location of the cylinder is managed by a server that receives the signal from the transmitter.

[0005] In addition, Patent Publication No. 2020-159389 (Patent Document 3) discloses a technology in which a cylinder management device including a positioning unit is attached to a cylinder sold to a user while being locked, and the location of the cylinder is managed using location information from the positioning unit. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Special Publication No. 2013-520742 [Patent Document 2] Japanese Patent Publication No. 2020-056416 [Patent Document 3] Japanese Patent Application Publication No. 2020-159389 Summary of the Invention [Problem to be solved by the invention]

[0007] As described in Patent Document 1, when a mark affixed to a cylinder as an inscription or a sticker is used for managing the cylinder, the mark may become difficult to read due to deterioration of the inscription or dirt on the sticker, making it difficult to track the cylinder. On the other hand, as described in Patent Document 2 or Patent Document 3, when a transmitter or positioning unit attached to the cylinder is used for managing the cylinder, it is expected that tracking the cylinder may become difficult if the valve or positioning unit is removed from the cylinder. Therefore, there is a need for technology that can reliably track cylinders and thereby reliably manage the location of the cylinder.

[0008] The present disclosure has been devised in light of the above circumstances, and its purpose is to provide a technique for reliably managing the location of cylinders. [Means for solving the problem]

[0009] According to another aspect of the present disclosure, there is provided a method for managing cylinders, the method being implemented by a computer and comprising the steps of: acquiring, from a communication device attached to each of one or more cylinders, location information of the cylinder to which the communication device is attached; determining whether the acquired location information is outside the allowable range by accessing a memory that stores an allowable range for the location of each of the one or more cylinders; and outputting an alarm in response to determining that the location information is outside the allowable range.

[0010] The cylinder management method may further include a step of determining whether the scheduled time for obtaining location information from the communication device has arrived, and a step of outputting an alarm if the location information has not been obtained when it is determined that the scheduled time has arrived.

[0011] The step of acquiring the location information of the cylinder may include acquiring unique information of the cylinder. The memory may store a location tolerance range for each of the one or more cylinders in association with the unique information.

[0012] The cylinder management method may further include the steps of acquiring, from a transmitter attached to each of the one or more cylinders, the remaining amount of liquid contained in the cylinder to which the transmitter is attached; determining whether the acquired remaining amount is below a threshold value by accessing a memory that stores a threshold value associated with each of the one or more cylinders; and, upon determining that the remaining amount is below the threshold value, notifying that the cylinder corresponding to the remaining amount needs to be replaced.

[0013] The method may further include the step of providing a delivery route for picking up a cylinder whose remaining amount is determined to be equal to or less than the threshold.

[0014] According to yet another aspect of the present disclosure, there is provided a program that, when executed by a computer, causes the computer to implement the cylinder management method. [Effects of the Invention]

[0015] According to an aspect of the present disclosure, in a method for managing a cylinder, an alarm is output when a cylinder is located outside a tolerance range set for the cylinder, thereby enabling more reliable management of the position of the cylinder. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram for explaining the configuration of a cylinder management system. [Figure 2] FIG. 1 is a diagram for explaining in outline a method for managing the shipping and return of a cylinder 500. [Figure 3] 5A and 5B are diagrams for explaining the structure of a cylinder 500. FIG. [Figure 4]10 is a diagram for explaining a specific example of the position of equipment in a cylinder 500. FIG. [Figure 5] 2A to 2C are diagrams showing a part of the manufacturing process of the cylinder 500. [Figure 6] 10 is a diagram showing an example of a display screen of a delivery route displayed on an information terminal 250. FIG. [Figure 7] 1 is a schematic diagram illustrating an example of a hardware configuration of an information processing device 100. FIG. [Figure 8] FIG. 2 is a schematic diagram showing an example of the hardware configuration of an information terminal 250. [Figure 9] 1 is a diagram illustrating an example of a hardware configuration of an IC (Integrated Circuit) tag reader 350. FIG. [Figure 10] FIG. 5 is a schematic diagram showing an example of the hardware configuration of a GPS (Global Positioning System) logger 510. [Figure 11] FIG. 10 is a schematic diagram showing an example of the hardware configuration of a remaining amount measuring device 530. [Figure 12] 5 is a diagram showing an example of a data structure of information stored in a GPS logger 510. FIG. [Figure 13] 10 is a diagram illustrating an example of a data structure of information stored in a fuel gauge 530. FIG. [Figure 14] 1 is a diagram schematically illustrating an example of a data structure of information stored as a basic information table 121 in information processing device 100. FIG. [Figure 15] 2 is a diagram schematically illustrating an example of a data structure of information stored as cylinder management information 122 in the information processing device 100. FIG. [Figure 16] 1 is a diagram schematically illustrating an example of a data structure of information stored as location management information 123 in information processing device 100. FIG. [Figure 17] 1 is a diagram schematically illustrating an example of a data structure of information stored as remaining amount management information 124 in the information processing device 100. FIG. [Figure 18] 2 is a diagram schematically illustrating an example of a data structure of information stored as customer management information 125 in information processing device 100. FIG. [Figure 19] FIG. 19 is a diagram showing a state in which the remaining amount of one cylinder has changed from the state shown in FIG. 18. [Figure 20] 1 is a diagram schematically illustrating an example of a data structure of a delivery schedule created in an information processing device 100. FIG. [Figure 21] 2 is a diagram schematically illustrating an example of a data structure of a delivery route created in the information processing device 100. FIG. [Figure 22] 10 is a flowchart of a process executed by the information processing device 100 to manage the delivery of cylinders. [Figure 23] 10 is a flowchart of a process executed by the information processing device 100 to manage the return of the cylinder. [Figure 24] 10 is a flowchart of a process executed by the information processing device 100 to manage the location of the cylinder. [Figure 25] 10 is a flowchart of a process executed in the information processing device 100 to manage the remaining amount of gas in the cylinder. [Figure 26] 10 is a flowchart of a process executed by information processing device 100 to create a delivery route for delivering cylinders to customers. [Figure 27] FIG. 10 is a diagram illustrating an example of a display screen of a delivery schedule. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, embodiments according to the present invention will be described with reference to the drawings. In the following description, the same parts and components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated. Note that the embodiments and modifications described below may be selectively combined as appropriate.

[0018] [Configuration of cylinder management system] 1 is a diagram for explaining the outline of the configuration of a cylinder management system. The cylinder management system shown in FIG. 1 is a system for managing information such as the location of a cylinder 500.

[0019] Cylinder 500 is filled with gas (liquefied gas) at filling facility 300. Cylinder 500 is then shipped from filling facility 300 and transported from filling facility 300 to customer 400 while loaded onto vehicle 200, and then delivered to customer 400. When the gas in cylinder 500 is consumed at customer 400, cylinder 500 is returned to filling facility 300. At filling facility 300, cylinder 500 is filled with gas again, and then cylinder 500 is delivered to customer 400 again.

[0020] The cylinder management system includes an information processing device 100 that manages information such as the location of cylinders. The information processing device 100 may be a general-purpose computer, and manages information related to cylinders 500 at a filling facility 300 (such as filling of gas into cylinders 500, shipping to customers 400, etc.). The information processing device 100 is managed, for example, by a party that provides customers with gas filled into cylinders 500 (such as a gas manufacturer). The information processing device 100 may display various information on a display 150.

[0021] An information terminal 250 is mounted on the vehicle 200. The information terminal 250 may be an on-board general-purpose computer or an information terminal such as a smartphone carried by the driver.

[0022] When the vehicle 200 delivers the cylinders 500 to two or more customers 400, the information processing device 100 may create a delivery route and transmit it to the information terminal 250. The information terminal 250 may display the transmitted delivery route. This allows the driver of the vehicle 200 to deliver the cylinders 500 to each of the two or more customers 400 in the order according to the displayed delivery route.

[0023] As will be described later with reference to FIG. 3 etc., the cylinder 500 may be embedded with a device that transmits location information of the cylinder 500 and a device that manages the remaining amount of gas in the cylinder 500. After the cylinder 500 is delivered to the customer 400, the cylinder 500 may transmit the location information and remaining amount of gas of the cylinder 500 to the information processing device 100. In this way, the information processing device 100 can manage the location information and remaining amount of gas of the cylinder 500 even when the cylinder 500 is located on the premises of the customer 400.

[0024] Furthermore, when the information processing device 100 detects that the cylinder 500 has been delivered to the premises of the customer 400 using the location information of the cylinder 500 , it may create a delivery note for the cylinder 500 to the customer 400 .

[0025] Fig. 2 is a diagram for explaining a method for managing the shipping and return of a cylinder 500. An IC (Integrated Circuit) tag that stores the ID of the cylinder 500 may be embedded in the cylinder 500. As shown in Fig. 2, an IC tag reader 350 may be installed at each of the shipping gate and the return gate in the filling facility 300.

[0026] The shipment of each cylinder 500 can be managed as follows: When the vehicle 200 passes through the shipping gate, an IC tag (an IC tag 520, described later) embedded in the cylinder 500 mounted on the vehicle 200 approaches the IC tag reader 350, which causes the IC tag reader 350 to read the ID of the cylinder 500 from the IC tag of the cylinder 500. The IC tag reader transmits the read ID to the information processing device 100. The information processing device 100 recognizes that the cylinder 500 corresponding to the received ID is to be shipped.

[0027] The return of each cylinder 500 can be managed as follows: When the vehicle 200 carrying the cylinder 500 passes through the return gate, the IC tag embedded in the cylinder 500 approaches the IC tag reader 350, which causes the IC tag reader 350 to read the ID of the cylinder 500 from the IC tag of the cylinder 500. The IC tag reader 350 transmits the read ID to the information processing device 100. The information processing device 100 recognizes that the cylinder 500 corresponding to the received ID has been returned.

[0028] [Cylinder configuration] The configuration of the cylinder 500 will be described with reference to Figures 3 to 5. Figure 3 is a diagram for explaining the structure of the cylinder 500.

[0029] 3 shows a tank 501 that stores gas (liquefied gas). As will be described later with reference to FIG. 5, fibers (glass fibers, carbon fibers, etc.) are spirally wound around the surface of tank 501. The fibers are then impregnated with synthetic resin and dried to form cylinder 500. That is, cylinder 500 is formed by forming an FRP (fiber reinforced plastic) layer on the surface of tank 501.

[0030] When shipped, cylinder 500 has valve 590 attached to the top thereof, and cover 591 attached to the outer periphery thereof to reduce shocks during transportation, etc. Cover 591 is made of, for example, synthetic resin.

[0031] FIG. 4 is a diagram illustrating a specific example of the positions of various devices in a cylinder 500. FIG. 4 shows a shoulder 500X, a body 500Y, and a bottom 500Z in the cylinder 500. The body 500Y is located in the center of the cylinder 500, and the diameter of the cylinder 500 is constant at the body 500Y. The shoulder 500X is located above the body 500Y, and the diameter of the cylinder 500 at the shoulder 500X changes so that it becomes shorter the higher it is. The bottom 500Z is located below the body 500Y, and the bottom surface of the bottom 500Z is formed by a curved surface.

[0032] 4, a GPS logger 510, an IC tag 520, and a fuel level measuring device 530 are disposed on the shoulder 500X. When multiple cylinders 500 are disposed adjacent to each other, the body 500Y may come into contact with the body 500Y of an adjacent cylinder 500, but the shoulder 500X does not come into contact with the shoulder 500X of an adjacent cylinder 500. By disposing the GPS logger 510, the IC tag 520, and the fuel level measuring device 530 on the shoulder 500X, damage due to contact with an adjacent cylinder 500 can be avoided even when multiple cylinders 500 are disposed adjacent to each other.

[0033] 5 is a diagram schematically showing a part of the manufacturing process for the cylinder 500. An example of the procedure for embedding the GPS logger 510, IC tag 520, and fuel gauge 530 in the cylinder 500 will be described with reference to FIG.

[0034] As shown in Figure 5, fiber 502 is wrapped around tank 501. At this time, GPS logger 510, IC tag 520, and remaining amount meter 530 are placed on the part of tank 501 that corresponds to shoulder 500X, and fiber 502 is wrapped around GPS logger 510, IC tag 520, and remaining amount meter 530. Thereafter, fiber 502 is impregnated with synthetic resin and dried. As a result, GPS logger 510, IC tag 520, and remaining amount meter 530 are embedded in the FRP layer of cylinder 500.

[0035] The bottom portion 500Z houses an ultrasonic sensor 536. The ultrasonic sensor 536 is a component of the remaining amount measuring device 530, as will be described later with reference to FIG.

[0036] [Delivery route] 6 is a diagram showing an example of a delivery route display screen displayed on information terminal 250. Display screen 600 shows icons 611, 612, 613, 614, and 620 on a map. Icon 620 represents the location of the vehicle on which information terminal 250 is mounted. Icons 611, 612, 613, and 614 represent the locations of four customers to whom the cylinders are to be delivered. Display screen 600 also shows the names of the respective customers (CL(1), CL(2), CL(3), and CL(4)) attached to icons 611, 612, 613, and 614, respectively.

[0037] The display screen 600 further shows a route 610. The route 610 represents a delivery route created by the information processing device 100. In the example of Fig. 6, the route 610 represents a route that starts from the icon 620, passes through the icons 611, 612, and 613 in this order, and reaches the icon 614.

[0038] [Hardware Configuration: Information Processing Device 100] Fig. 7 is a schematic diagram showing an example of a hardware configuration of information processing device 100. Referring to Fig. 7, information processing device 100 includes a control device 101, a read only memory (ROM) 102, a random access memory (RAM) 103, a communication interface 104, a display interface 105, an input interface 107, and a storage device 120. These components are connected to a bus 110.

[0039] The control device 101 is configured, for example, by at least one integrated circuit. The integrated circuit may be configured, for example, by at least one central processing unit (CPU), at least one graphics processing unit (GPU), at least one application specific integrated circuit (ASIC), at least one field programmable gate array (FPGA), or a combination thereof.

[0040] The control device 101 controls the operation of the information processing device 100 by executing programs. In one implementation example, these programs are stored in the storage device 120. At least one of these programs may be stored in an external server, and the control device 101 may execute these programs using an API (Application Programming Interface).

[0041] A LAN (Local Area Network), an antenna, etc. are connected to the communication interface 104. The information processing device 100 exchanges data with external devices via the communication interface 104. The information processing device 100 may be configured to be able to download various programs from a server via the communication interface 104.

[0042] A display 150 is connected to the display interface 105. The display interface 105 sends an image signal for displaying an image to the display 150 in accordance with a command from the control device 101 or the like. The display 150 is, for example, a liquid crystal display, an organic EL (Electro Luminescence) display, or other display device. The display 150 may be configured integrally with the information processing device 100 or may be configured separately from the information processing device 100.

[0043] An input device 108 is connected to the input interface 107. The input device 108 is, for example, a mouse, a keyboard, a touch panel, or any other device capable of receiving user operations. The input device 108 may be configured integrally with the information processing device 100, or may be configured separately from the information processing device 100.

[0044] The storage device 120 is a storage medium such as a hard disk or flash memory. The storage device 120 stores various programs and data used to execute the programs. The storage location of these programs and / or data is not limited to the storage device 120, but may be a storage area of ​​the control device 101 (for example, a cache memory), the ROM 102, the RAM 103, or an external device (for example, a server).

[0045] 7, the storage device 120 stores basic information table 121, cylinder management information 122, location management information 123, remaining amount management information 124, and customer management information 125 as data for managing the cylinder management system. The contents of this information will be described later with reference to Figures 14 to 18, etc. The storage device 120 also stores a program 126 and various data such as variables used in executing the program.

[0046] [Hardware configuration: Information terminal 250] Fig. 8 is a schematic diagram showing an example of the hardware configuration of information terminal 250. Referring to Fig. 8, information terminal 250 includes a control device 201, a ROM 202, a RAM 203, a communication interface 204, a display interface 205, an input interface 207, and a storage device 220. These components are connected to bus 220.

[0047] The control device 201 is configured, for example, by at least one integrated circuit. The integrated circuit may be configured, for example, by at least one CPU, at least one GPU, at least one ASIC, at least one FPGA, or a combination thereof.

[0048] The control device 201 controls the operation of the information terminal 250 by executing programs. In one implementation example, these programs are stored in the storage device 220. At least one of these programs may be stored in an external server, and the control device 201 may execute these programs using an API.

[0049] A LAN, an antenna, etc. are connected to the communication interface 204. The information terminal 250 exchanges data with external devices via the communication interface 204. The information terminal 250 may be configured to be able to download various programs from a server via the communication interface 204.

[0050] A display 206 is connected to the display interface 205. The display interface 205 sends an image signal for displaying an image to the display 206 in accordance with a command from the control device 201 or the like. The display 206 is, for example, a liquid crystal display, an organic EL display, or other display device.

[0051] An input device 208 is connected to the input interface 207. The input device 208 is a device capable of receiving user operations, such as a touch panel.

[0052] The storage device 220 is a storage medium such as a hard disk, a flash memory, etc. The storage device 220 stores various programs and data used to execute the programs.

[0053] [Hardware configuration: IC tag reader 350] Fig. 9 is a diagram showing an example of the hardware configuration of the IC tag reader 350. For reference, Fig. 9 also shows an IC tag 520 that is the communication partner of the IC tag reader 350. The IC tag 520 may be a passive tag, an active tag, or a semi-active tag.

[0054] 9, IC tag reader 350 includes controller 351 and antenna 352. In IC tag reader 350, controller 351 reads out the ID of cylinder 500 stored in IC tag 520 when IC tag 520 is located within a predetermined distance from antenna 352. Controller 351 transmits the read ID to information processing device 100 via antenna 352 or by using a communication device of IC tag reader 350 (not shown).

[0055] 9 , the IC tag reader 350 transmits the ID acquired from the IC tag 520 to the information processing device 100, which is merely one specific example of the information processing device 100 acquiring the ID of the cylinder 500 passing through the installation location of the IC tag reader 350 in the cylinder management system. In the cylinder management system, the ID of the cylinder 500 may be acquired in other ways, such as by reading a barcode from the cylinder 500 itself or from an element attached to the cylinder 500.

[0056] [Hardware configuration: GPS Logger 510] Fig. 10 is a schematic diagram showing an example of the hardware configuration of a GPS logger 510. Referring to Fig. 10, the GPS logger 510 includes a control device 511, a battery 510A, a communication interface 514, a storage device 515, a GPS unit 516, an input interface 517, and a display interface 518. These components are connected to a bus.

[0057] The battery 510A supplies power to each element of the GPS logger 510. The charging facility 300 may be provided with a charging device that charges the battery 510A contactlessly. The GPS logger 510 may be provided with a coil for wireless charging, and the battery 510A may be charged by the charging device using the coil. The GPS logger 510 may include a solar panel, and the battery 510A may be charged by electromotive force generated in the solar panel. Furthermore, in the GPS logger 510, each element (such as the control device 511) other than the battery 510A may also be connected to the solar panel, and the electromotive force generated in the solar panel may be directly consumed by each element.

[0058] The control device 511 may be configured with at least one integrated circuit (at least one CPU, at least one GPU, at least one ASIC, at least one FPGA, or a combination thereof). The control device 511 controls the operation of the GPS logger 510 by executing programs. These programs may be stored in the storage device 515 or may be stored in an external server. The control device 511 may execute these programs using an API.

[0059] A LAN, an antenna, etc. are connected to the communication interface 514. The GPS logger 510 exchanges data with external devices via the communication interface 514.

[0060] The storage device 515 is a storage medium such as a flash memory, etc. The storage device 515 stores various programs and data used to execute the programs.

[0061] The GPS unit 516 creates position information of the GPS logger 510 from signals received from GPS satellites via the communication interface 514 .

[0062] An input device 517A is connected to the input interface 517. The input device 517A is a device capable of receiving user operations, such as a touch panel.

[0063] A display 518A is connected to the display interface 518. The display interface 518 sends an image signal for displaying an image to the display 518A in accordance with a command from the control device 511 or the like. The display 518A is a display device such as an organic EL display.

[0064] The storage device 515 stores the ID of the GPS logger 510. The control device 511 transmits the ID stored in the storage device 515 and the position information created by the GPS unit 516 via the communication interface 514.

[0065] [Hardware configuration: Fuel Gauge 530] Fig. 11 is a schematic diagram showing an example of the hardware configuration of fuel gauge 530. Referring to Fig. 11, fuel gauge 530 includes a control device 531, a battery 530A, a communication interface 534, a storage device 535, an ultrasonic sensor 536, an input interface 537, and a display interface 538. These components are connected to a bus.

[0066] Battery 530A supplies power to each element of fuel gauge 530. Charging facility 300 may be provided with a charging device that charges battery 530A contactlessly. Fuel gauge 530 may be provided with a coil for wireless charging, and battery 530A may be charged by the charging device using the coil. Fuel gauge 530 may include a solar panel, and battery 530A may be charged by electromotive force generated in the solar panel. Furthermore, in fuel gauge 530, each element (such as control device 531) other than battery 530A may also be connected to the solar panel, and the electromotive force generated in the solar panel may be directly consumed by each element.

[0067] The control device 531 may be configured by at least one integrated circuit (at least one CPU, at least one GPU, at least one ASIC, at least one FPGA, or a combination thereof). The control device 531 controls the operation of the fuel gauge 530 by executing programs. These programs may be stored in the storage device 535 or may be stored on an external server. The control device 531 may execute these programs using an API.

[0068] A LAN, an antenna, etc. are connected to communication interface 534. Fuel gauge 530 exchanges data with external devices via communication interface 534.

[0069] The storage device 535 is a storage medium such as a flash memory, etc. The storage device 535 stores various programs and data used to execute the programs.

[0070] The ultrasonic sensor 536 is disposed at the bottom 500Z of the cylinder 500, as described with reference to Figure 4. More specifically, the ultrasonic sensor 536 is disposed at the bottom of the tank 501 within the cylinder 500.

[0071] An input device 537A is connected to the input interface 537. The input device 537A is a device capable of receiving user operations, such as a touch panel.

[0072] Display 538A is connected to display interface 538. Display interface 538 sends an image signal for displaying an image to display 538A in accordance with a command from control device 531 or the like. Display 538A is a display device, and is realized by, for example, but is not limited to, an organic EL display.

[0073] Ultrasonic sensor 536 emits ultrasonic waves toward the gas (liquefied gas) contained in tank 501. Control device 531 derives the remaining amount of gas based on the length of time from when ultrasonic sensor 536 emits the ultrasonic waves until ultrasonic sensor 536 receives the reflected waves from the liquid surface of the liquefied gas. Storage device 535 stores the ID of remaining amount meter 530. Control device 531 transmits the ID stored in storage device 535 and the remaining amount derived as described above via communication interface 534. Control device 531 may display the remaining amount on display 538A. The value displayed on display 538A may be the "remaining amount" value itself, an image such as a pictogram corresponding to the "remaining amount" value, a value of the amount used calculated from the "remaining amount" value and the filling mass value, or a combination of these.

[0074] [Data configuration: (GPS logger) location information] Fig. 12 is a diagram schematically illustrating an example of the data structure of information stored in the GPS logger 510. As shown in Fig. 12, the storage device 515 of the GPS logger 510 stores a history of the position information of the GPS logger 510 detected by the GPS logger 510. More specifically, the storage device 515 stores the ID (GPS_ID) of the GPS logger 510, as well as the detected position and the time when the position was detected.

[0075] The example in FIG. 12 includes "GP(1)" as the ID of the GPS logger 510, and "PS(1)" and "2020 / 9 / 16 10:30" as a combination of location and time. PS(1) may be a combination of latitude and longitude values. "2020 / 9 / 16 10:30" represents 10:30 on September 16, 2020.

[0076] [Data stored in IC tag 520] The IC tag 520 stores information (tag ID) that identifies the IC tag 520. When the IC tag 520 approaches, the IC tag reader 350 reads the tag ID stored in the IC tag 520.

[0077] [Data structure: (remaining amount meter) remaining amount information] Fig. 13 is a diagram showing a schematic example of the data structure of information stored in remaining gas meter 530. As shown in Fig. 13, storage device 535 of remaining gas meter 530 stores a history of the remaining amount of gas (liquefied gas) detected by remaining gas meter 530. More specifically, storage device 535 stores the ID (measuring device ID) of remaining gas meter 530, the date the remaining amount was measured, and the measured remaining amount.

[0078] The example in FIG. 13 includes "MT(1)" as the ID of the gas gauge 530, and "2020 / 9 / 14" and "RQ(11)" as the combination of date and remaining amount. "RQ(11)" may be a specific numerical value of the remaining amount of gas (volume, etc.). In one implementation example, the gas gauge 530 detects the remaining amount at a predetermined time each day (for example, 4:00 PM), and the remaining amount detected at that time is stored as the remaining amount for that day. Note that the timing of detecting the remaining amount does not need to be once a day, and detection may be performed more frequently or less frequently. The detected remaining amount may be stored in the storage device 535 each time it is detected.

[0079] [Data structure: (information processing device) basic information table] 14 is a diagram schematically illustrating an example of the data structure of information stored as a basic information table 121 in the information processing device 100. The basic information table 121 associates, for one cylinder 500, the GPS logger 510, the IC tag 520, and the fuel level measuring device 530 embedded in the cylinder 500.

[0080] More specifically, as shown in Fig. 14, the basic information table 121 associates data of four items (cylinder ID, tag ID, GPS_ID, and meter ID) with one another. In the example of Fig. 14, for example, a cylinder 500 specified by a cylinder ID of "CY(1)" is associated with an IC tag 520 specified by a tag ID of "TG(1)", a GPS logger 510 specified by a GPS_ID of "GP(1)", and a remaining amount meter 530 specified by a meter ID of "MT(1)".

[0081] [Data configuration: (information processing device) cylinder management information] 15 is a diagram showing an example of a data structure of information stored as the cylinder management information 122 in the information processing device 100. The cylinder management information 122 includes information about each cylinder 500.

[0082] More specifically, the cylinder management information 122 associates data for 11 items (cylinder ID, manufacturing date, filling date, gas type, filling facility, filling pressure, filling mass, shipping date / time / location, delivery date / time / location, collection date / time / location, and return date / time / location). "Shipping" may mean that a cylinder is sent out from a filling facility for delivery to a customer. "Delivery" may mean that a cylinder is handed over to the customer at the delivery destination. "Collection" may mean that a cylinder is handed over from a customer for return. "Return" may mean that a cylinder is returned to the filling facility.

[0083] In the cylinder management information, the cylinder ID identifies each cylinder 500. The manufacturing date specifies the date on which each cylinder 500 was manufactured. The filling date specifies the date on which the cylinder 500 was filled with gas. The gas type specifies the type of gas filled into the cylinder 500. The filling facility specifies the location (filling facility) where the gas was filled into the cylinder 500. The filling pressure and filling mass specify the pressure and mass of the gas filled into the cylinder 500, respectively.

[0084] In the cylinder management system, when a new cylinder 500 is introduced, an operator registers the cylinder ID and manufacturing date of the cylinder 500 in the information processing device 100. Each time a gas is filled into a cylinder 500, the operator also registers the filling date, gas type, filling facility, filling pressure, and filled mass. In other words, the cylinder management information 122 includes information like a "resume" for each cylinder 500.

[0085] In the example of Figure 15, the cylinder specified by the cylinder ID "CY(1)" was manufactured on December 3, 2018 (2018 / 12 / 3). This cylinder was filled with oxygen on June 29, 2020, at a filling facility specified by "ST(1)." The filling pressure at this time was P(11) and the filling mass was M(11). This cylinder was also filled with oxygen on August 3, 2020, at a filling facility specified by "ST(1)." The filling pressure at this time was P(12) and the filling mass was M(12). This cylinder was also filled with oxygen on September 1, 2020, at a filling facility specified by "ST(1)." The filling pressure at this time was P(13) and the filling mass was M(13).

[0086] In the cylinder management information, the shipping date / time / location specifies the date and location at which the cylinder 500 was shipped. The delivery date / time / location, collection date / time / location, and return date / time / location specify the date and location at which the cylinder 500 was delivered, collected, and returned, respectively.

[0087] The shipping date / time / place is registered when the cylinder 500 passes through the IC tag reader 350 at the shipping gate. More specifically, when the IC tag reader 350 reads the tag ID, it notifies the information processing device 100 of the tag ID. When the information processing device 100 receives the tag ID from the IC tag reader 350 at the shipping gate, it registers the date and time of reception and the shipping place that identifies the IC tag reader 350 that sent the tag ID in the cylinder management information 122 as the shipping date / time / place.

[0088] The delivery date / time / location is registered when the shipped cylinder 500 is located at the customer's delivery location. More specifically, for a cylinder 500 whose shipping date / time / location is registered, the information processing device 100 periodically compares the location information transmitted from the GPS logger 510 embedded in the cylinder 500 with the location information of the customer's delivery location where the cylinder 500 is to be delivered. When the information processing device 100 detects that the location information from the GPS logger 510 corresponds to the customer's delivery location where the cylinder 500 is to be delivered (matches, the location information is included in the delivery location, etc.), it registers the date / time when such location information was received and the delivery location in the cylinder management information 122 as the delivery date / time / location.

[0089] The collection date / time / location is registered when the cylinder 500 is delivered to a customer and the cylinder 500 is located at the customer's delivery location. More specifically, for a cylinder 500 whose delivery date / location / location has been registered, the information processing device 100 periodically compares the location information transmitted from the GPS logger 510 embedded in the cylinder 500 with the location information of the customer's delivery location where the cylinder 500 was delivered. When the information processing device 100 detects that the location information from the GPS logger 510 corresponds to the customer's delivery location where the cylinder 500 is to be delivered (matches, the location information is included in the delivery location, etc.), it registers the date / time when such location information was received and the delivery location in the cylinder management information 122 as the delivery date / time / location.

[0090] The return date / time / location is registered when the cylinder 500 passes through the IC tag reader 350 at the return gate. When the information processing device 100 receives the tag ID from the IC tag reader 350 at the return gate, it registers the date and time of reception and the return location that identifies the IC tag reader 350 that sent the tag ID in the cylinder management information 122 as the return date / time / location.

[0091] For example, the example in Figure 15 shows that cylinder ID "CY(1)" was shipped from the filling facility specified by "ST(1)" at 14:00 on July 1, 2020, delivered to the customer specified by "PL(1)" at 14:10 on the same day, collected from the customer specified by "PL(1)" at 10:15 on July 21, 2020, and returned to the filling facility specified by "ST(1)" at 10:26 on the same day.

[0092] The above-described procedures for registering the date and time / location of shipment, delivery, collection, and return are merely examples. This information may be registered by detecting the shipment, delivery, collection, and return of the cylinder in other ways.

[0093] [Data configuration: (information processing device) location management information] 16 is a diagram showing an example of a data structure of information stored as the location management information 123 in the information processing device 100. The location management information 123 includes location information of each cylinder 500.

[0094] More specifically, the location management information 123 associates data of three items (GPS_ID, location, and time). When the information processing device 100 receives location information from the GPS logger 510 embedded in each cylinder 500, the information processing device 100 registers the ID (GPS_ID) of the GPS logger 510, the received location information, and the time when the location information was received in the location management information 123. In one example, only the latest location information of each cylinder 500 is registered in the location management information 123.

[0095] The example in Figure 16 includes the location "PS(14)" at 11:30 on September 16, 2020 as the latest location information received from GPS_ID "GP(1)".

[0096] [Data configuration: (information processing device) remaining amount management information] 17 is a diagram showing an example of a data structure of information stored as remaining amount management information 124 in information processing device 100. Remaining amount management information 124 includes the remaining amount of each cylinder 500.

[0097] More specifically, the remaining amount management information 124 associates data for three items (meter ID, remaining amount, and time). When the information processing device 100 receives the remaining amount from the remaining amount meter 530 embedded in each cylinder 500, it registers the ID (meter ID) of the IC tag 520, the received remaining amount, and the time when the remaining amount was received in the remaining amount management information 124. In one example, only the latest remaining amount of each cylinder 500 is registered in the remaining amount management information 124.

[0098] The example in Figure 17 includes the remaining amount "RQ(12)" at 16:00 on September 15, 2020 as the latest remaining amount received from the measuring device ID "MT(1)".

[0099] [Data configuration: (information processing device) customer management information] 18 is a diagram showing an example of a data structure of information stored as customer management information 125 in information processing device 100. Customer management information 125 manages the delivery of cylinders 500 to each customer 400.

[0100] More specifically, the customer management information 125 associates data for seven items (customer ID, location, threshold, shipped cylinder, replacement flag, tolerance range, and scheduled shipping cylinder) with each other.

[0101] The customer ID identifies each customer 400. The location specifies a predetermined delivery location for each customer 400. The threshold indicates the threshold for the remaining amount of the cylinder 500 delivered to that customer for replacement. The shipped cylinder identifies each of the cylinders 500 that have been shipped (delivered) to each customer 400. The replacement flag indicates whether or not each of the shipped (delivered) cylinders 500 needs to be replaced. If replacement is required, the value of the replacement flag is set to ON, and if replacement is not yet required, the value of the replacement flag is set to OFF.

[0102] The tolerance range represents the range in which the cylinder 500 is permitted to be located. The tolerance range may be agreed upon between the shipper of the cylinder 500 (such as a liquefied gas manufacturer) and the customer, and may be registered by an operator. The tolerance range may be set for each cylinder 500. For example, if, of 10 cylinders delivered to the same customer, six are permitted to be used only in one laboratory of the customer, and the remaining four are permitted to be used in two laboratories, the tolerance range for the six cylinders may be a range corresponding to only the one laboratory, and the tolerance range for the four cylinders may be a range corresponding to the two laboratories.

[0103] The cylinder to be shipped identifies the cylinder that is to be shipped in place of the cylinder that needs to be replaced (the cylinder for which the replacement flag is set ON).

[0104] In the example of Figure 18, three cylinders (CY(11), CY(12), and CY(13)) are shipped (delivered) to a customer identified by "CL(1)." For this customer, when the remaining amount of gas in a cylinder falls to "TH1 or less," it is determined that replacement is necessary. The replacement flag value for all three cylinders is OFF. An area represented by AR(11) is defined as the allowable range for the three cylinders.

[0105] FIG. 19 is a diagram showing a state in which the remaining amount of one cylinder has changed from the state shown in FIG. 18. When the remaining amount of the cylinder identified by "CY(11)" in FIG. 18 falls below TH1, the customer management information 125 is updated to the state shown in FIG. 19. In the state of FIG. 19, the value of the exchange flag for "CY(11)" has been changed to ON. In addition, a cylinder identified by "CY(15)" is registered as a cylinder scheduled for shipment. In the state of FIG. 19, the customer identified by "CL(1)" is the "customer to whom the cylinder "CY(15)" should be delivered."

[0106] [Data structure: Delivery schedule] 20 is a diagram schematically illustrating an example of the data structure of a delivery schedule created by information processing device 100. As shown in FIG. 20, the delivery schedule associates data for three items (delivery date, customer, and content) with each other. More specifically, the delivery schedule specifies, for each day, the customers to whom cylinders are to be delivered, and further specifies the IDs of the cylinders to be picked up and the IDs of the cylinders to be handed over as the work content for each customer.

[0107] The example in Figure 20 specifies work for four customers (CL(1), CL(4), CL(5), and CL(8)) on October 14, 2020. Of these, the work content for the customer identified by CL(1) specifies the collection of a cylinder identified by CY(11) and the delivery of a cylinder identified by CY(15).

[0108] [Data structure: Delivery route] FIG. 21 is a diagram schematically illustrating an example of the data structure of a delivery route created by the information processing device 100. As shown in FIG. 21, in the delivery route, the customers included in the delivery schedule shown in FIG. 20 are arranged in the order in which they should be visited. For example, in the delivery route for October 14, 2020, the four customers specified as delivery destinations for that day in the delivery schedule are arranged in the order CL(1), CL(8), CL(4), and CL(5). Although not shown in FIG. 21, the delivery route further includes a delivery route specified based on map information, etc.

[0109] [Processing flow: Delivery management] 22 is a flowchart of a process executed by the information processing device 100 to manage the delivery of cylinders. The process of FIG. 22 is realized, for example, by the control device 101 executing a given program.

[0110] 22, in step S102, information processing device 100 determines whether or not a tag ID has been received from IC tag reader 350 at the shipping gate. Information processing device 100 repeats the control of step S102 at predetermined time intervals until it determines that a tag ID has been received (NO in step S102), and when it determines that a tag ID has been received (YES in step S102), it proceeds to step S104.

[0111] In step S104, the information processing device 100 refers to the basic information table 121 and converts the received tag ID into a cylinder ID.

[0112] In step S106, the information processing device 100 registers the shipping date / time / location for the cylinder ID acquired in step S104 in the cylinder management information 122. As a result, the date and time when the tag ID was acquired is registered as the shipping date / time, and the filling facility 300 associated with the IC tag reader 350 that transmitted the tag ID is registered as the shipping location.

[0113] In step S108, the information processing device 100 determines whether the cylinder 500, for which the shipping date / time / location has been registered but the delivery date / time / location has not been registered, is located at a location corresponding to the customer in the cylinder management information 122. If the location information received from the GPS logger 510 embedded in the cylinder 500 indicates a location corresponding to the "location" (FIG. 19) specified for the customer to whom the cylinder 500 is to be delivered, the information processing device 100 determines that the cylinder 500 is located at a location corresponding to the customer; otherwise, it determines that the cylinder 500 is not located at a location corresponding to the customer to whom the cylinder 500 is to be delivered.

[0114] The information processing device 100 repeats the control of step S108 at predetermined time intervals until it determines that the cylinder 500 is located at a location corresponding to the customer to whom it is to be delivered (NO in step S108), and when it determines that the cylinder 500 is located at a location corresponding to the customer to whom it is to be delivered (YES in step S108), it proceeds to control step S110.

[0115] In step S110, the information processing device 100 registers the delivery date / time / location for the cylinder 500 that was the target of processing in step S108 in the cylinder management information 122. As a result, the time when the information processing device 100 received the location information that was the basis for the YES determination in step S108 is registered as the delivery date / time, and the location associated with the customer to which the cylinder 500 is to be delivered (for example, "Location" in FIG. 18) is registered as the delivery location.

[0116] In step S112, the information processing device 100 creates an invoice for the cylinder 500 for which the delivery date / place was registered in step S110.

[0117] In step S114, information processing device 100 transmits the data of the delivery note created in step S112 to the customer.

[0118] In the process described above with reference to FIG. 22, the information processing device 100 detects each of the shipments and deliveries of the cylinder 500 and registers the dates, times, and locations thereof in the cylinder management information 122.

[0119] Furthermore, upon detecting the delivery of a cylinder 500, the information processing device 100 creates a delivery note for the cylinder 500 and transmits data on the created delivery note to the customer. This eliminates the need for a worker to hand over the delivery note to the customer. The information processing device 100 may also create delivery notes for two or more deliveries of cylinders 500 in a batch in accordance with given conditions. For example, in step S112, the information processing device 100 may set a flag indicating that a delivery note can be created for the cylinder 500 for which the delivery date / location was registered in step S110 to ON. Then, the information processing device 100 may create delivery notes for each cylinder for which the flag indicating that a delivery note can be created is ON at a specific time each day, for each customer.

[0120] [Processing flow: Return management] Fig. 23 is a flowchart of the process executed by the information processing device 100 to manage the return of the cylinders. The process of Fig. 23 is realized, for example, by the control device 101 executing a given program.

[0121] 23, in step S202, the information processing device 100 determines whether or not a cylinder 500 for which the delivery date / time / place is registered but the collection date / time / place is not yet registered in the cylinder management information 122 is located at a location corresponding to the customer to whom the cylinder 500 is to be delivered. For example, the information processing device 100 compares the location information acquired from the GPS logger 510 embedded in the cylinder 500 with the location information specified by the location corresponding to the customer ("Location" in FIG. 18), and if the two are the same or the former is included in the latter, it determines that the cylinder 500 is located at a location corresponding to the customer; otherwise, it determines that the cylinder 500 is not located at a location corresponding to the customer.

[0122] The information processing device 100 repeats the control of step S202 at predetermined time intervals until it determines that the cylinder 500 is located at a location corresponding to the customer (NO in step S202), and when it determines that the cylinder 500 is located at a location corresponding to the customer (YES in step S202), it proceeds to control step S204.

[0123] In step S204, the information processing device 100 registers the collection date and time / location for the cylinder 500 that was determined in step S202 to be located at a location corresponding to the customer in the cylinder management information 122. As a result, the time when the information processing device 100 received the location information that was determined in step S202 to be the location corresponding to the customer is registered as the collection date and time. In addition, the location associated with the customer (for example, "Location" in FIG. 18) is registered as the collection location.

[0124] In step S206, the information processing device 100 determines whether or not the tag ID of the IC tag embedded in the cylinder 500 for which the collection date / time / location was registered in step S204 has been received from the IC tag reader 350 at the return side gate. The information processing device 100 repeats the control of step S206 at predetermined time intervals until it determines that the tag ID of the IC tag has been received (NO in step S206), and when it determines that the tag ID of the IC tag has been received (YES in step S206), it proceeds to step S208.

[0125] In step S208, the information processing device 100 registers the return date / time / location for the cylinder 500 whose collection date / time / location was registered in step S204 in the cylinder management information 122. As a result, the date / time when the information processing device 100 acquired the tag ID in step S206 is registered as the return date / time, and the filling facility 300 associated with the IC tag reader 350 that transmitted the tag ID is registered as the shipping location.

[0126] In the process described above with reference to FIG. 23, the information processing device 100 detects each collection and return of the cylinder 500 and registers the date, time, and place in the cylinder management information 122.

[0127] [Processing flow: Location management] Fig. 24 is a flowchart of the process executed by the information processing device 100 to manage the positions of the cylinders. The process of Fig. 24 is realized, for example, by the control device 101 executing a given program.

[0128] 24, in step S302, information processing device 100 sets the cylinder ID to be targeted in the processing of Fig. 24. Information processing device 100 may execute the processing of Fig. 25 in order for each cylinder 500 delivered to a customer. That is, information processing device 100 may select and set the cylinder ID to be set in step S302 from among cylinder IDs for which the delivery date / time / place has been registered but the collection date / time / place has not yet been registered, each time the control of step S302 is executed.

[0129] In step S304, the information processing device 100 determines whether or not the time has come when the location information of the cylinder 500 set in step S302 is scheduled to be received.

[0130] In the cylinder management system, the timing at which location information is scheduled to be received may be set for each cylinder, such as every 10 minutes, every hour, etc. The timing at which location information is scheduled to be received may be set for each cylinder, or may be set uniformly for all cylinders.

[0131] If information processing device 100 determines that the timing has arrived (YES in step S304), it proceeds to step S306, and if not (NO in step S306), it returns control to step S302.

[0132] In step S306, the information processing device 100 determines whether or not it has received location information associated with the cylinder ID set in step S302 from the GPS logger 510. If the information processing device 100 determines that it has received the location information (YES in step S306), it proceeds to step S310; otherwise (NO in step S306), it proceeds to step S308.

[0133] In step S308, the information processing device 100 notifies the user that it is unable to receive the location information of the cylinder 500 that has been set as the processing target, and returns control to step S302. The notification may be a display on the display 150, a sound output, or a combination of these.

[0134] In step S310, the information processing device 100 reads out the allowable range (FIG. 18) associated with the cylinder 500 set as the processing target.

[0135] In step S312, information processing device 100 determines whether the location information determined to have been received in step S306 is within the allowable range read in step S310. If information processing device 100 determines that the location information is within the allowable range (YES in step S312), control proceeds to step S316; otherwise (NO in step S312), control proceeds to step S314.

[0136] In step S314, the information processing device 100 notifies that the cylinder 500 set as the processing target is located in an unauthorized location, and returns control to step S302.

[0137] In step S316, the information processing device 100 updates the location management information (FIG. 16) for the cylinder 500 that has been set as the processing target, and returns control to step S302.

[0138] 24, when the information processing device 100 is unable to acquire location information for a certain cylinder 500 at the timing when the location information of the cylinder 500 should be acquired, it notifies the worker of this in step S308. This allows the worker to recognize that the GPS logger 510 embedded in the cylinder 500 is in a state where it cannot transmit location information, and the worker can take action such as confirming the location of the cylinder 500 with the customer to whom the cylinder 500 is delivered. Therefore, it is possible to avoid, as much as possible, a situation in which the location of the cylinder 500 becomes unknown and the situation is left unresolved for a long period of time, making it difficult to search for the cylinder 500.

[0139] Furthermore, if the information processing device 100 detects that a certain cylinder 500 is located in an unauthorized location, it notifies the fact in step S314. This allows the worker to recognize that the cylinder 500 is located in an unauthorized location and to take action such as requesting the customer to whom the cylinder 500 is delivered to return the cylinder 500 to an authorized location. Therefore, even if a situation arises in which the cylinder 500 is about to be taken away by the customer, the worker can take action to resolve the situation as quickly as possible, thereby making it possible to avoid, as much as possible, a situation in which the situation is left unattended for a long period of time and the cylinder 500 goes missing.

[0140] [Processing flow: Remaining amount management] 25 is a flowchart of a process executed by the information processing device 100 to manage the remaining amount of gas in the cylinder. The process of FIG. 25 is realized, for example, by the control device 101 executing a given program.

[0141] 25, in step S402, information processing device 100 sets the cylinder ID to be targeted in the processing of Fig. 25. Information processing device 100 may execute the processing of Fig. 25 in order for each of the cylinders 500 delivered to the customer. That is, information processing device 100 may select and set the cylinder ID to be set in step S402 from among cylinder IDs for which the delivery date / time / place has been registered but the collection date / time / place has not yet been registered, each time the control of step S402 is executed.

[0142] In step S404, information processing device 100 determines whether the time has come to receive the remaining amount for cylinder 500 set in step S402. If information processing device 100 determines that the time has come (YES in step S404), it proceeds to step S406, and if not (NO in step S404), it returns control to step S402.

[0143] In the cylinder management system, the timing for receiving the remaining amount may be set for each cylinder, such as a specific time of day, every hour, etc. The timing for receiving the remaining amount may be set for each cylinder, or may be set uniformly for all cylinders.

[0144] In step S406, the information processing device 100 determines whether or not it has received the remaining amount from the remaining amount measuring device 530 identified by the measuring device ID associated with the cylinder ID set in step S402. If the information processing device 100 determines that it has received the remaining amount (YES in step S406), it proceeds to control step S410; otherwise (NO in step S406), it proceeds to control step S408.

[0145] In step S408, the information processing device 100 notifies the operator that the remaining amount cannot be received for the cylinder ID set in step S402. This allows the operator to recognize that the remaining amount of gas cannot be obtained for the cylinder 500 to be processed, and enables the operator to provide a service such as proactively inquiring with the customer about the need to replace the cylinder 500. Thereafter, the information processing device 100 returns control to step S402.

[0146] In step S410, information processing device 100 determines whether the remaining amount determined to be received in step S406 is equal to or less than a threshold value (FIG. 18). If information processing device 100 determines that the remaining amount is equal to or less than the threshold value (YES in step S410), control proceeds to step S414; otherwise (NO in step S410), control proceeds to step S412.

[0147] In step S412, the information processing device 100 updates the remaining amount of the measuring device ID corresponding to the cylinder ID being processed in the remaining amount management information 124 to the received remaining amount, and further registers the time at which it was determined in step S406 that the remaining amount was received as the time corresponding to the updated remaining amount, and returns control to step S402.

[0148] In step S414, the information processing device 100 changes the value of the exchange flag for the cylinder ID of the processing target from OFF to ON in the customer management information 125. Furthermore, the information processing device 100 may register the cylinder ID of a cylinder to be exchanged for the cylinder 500 of the processing target cylinder ID and delivered to the customer as a cylinder scheduled for shipping (FIG. 19). For example, the information processing device 100 selects a cylinder ID to register as a cylinder scheduled for shipping from among cylinder IDs in the cylinder management information 122 for which the shipping date / time / location has not been registered after filling has been completed and which are filled with the same type of gas as the cylinder ID of the processing target cylinder.

[0149] In step S416, the information processing device 100 updates the remaining amount of the measuring device ID corresponding to the cylinder ID being processed in the remaining amount management information 124 to the received remaining amount, and further registers the time at which it was determined in step S406 that the remaining amount was received as the time corresponding to the updated remaining amount, and returns control to step S402.

[0150] In the processing described above with reference to Figure 25, the information processing device 100 manages the remaining amount of gas in the cylinder 500 that has been delivered to the customer for delivery, and when the remaining amount falls below a threshold, it can perform control to replace the cylinder 500 (turning off the replacement flag, registering the cylinder scheduled for shipment, etc.).

[0151] [Process flow: Create a delivery route] 26 is a flowchart of a process executed by the information processing device 100 to create a delivery route for delivering a cylinder to a customer. The process of FIG. 26 is realized, for example, by the control device 101 executing a given program.

[0152] 26, in step S502, information processing device 100 determines whether a request for creating a delivery schedule has been acquired. Information processing device 100 acquires the request for creating a delivery schedule via input interface 107 or communication interface 104.

[0153] When starting the delivery of the cylinder to the customer, the worker may operate a specific button displayed on the information terminal 250, and in response to the operation of the specific button, the information terminal 250 may send a request to the information processing device 100 to create a delivery schedule.

[0154] The information processing device 100 may set a creation request flag for a delivery schedule for the next day to ON at a given time each day, and may determine in step S502 that the request has been acquired based on the creation request flag being set to ON. The value of the creation request flag may be reset to OFF when a delivery schedule is created in step S504, which will be described later.

[0155] The information processing device 100 repeats the control of step S502 at regular intervals until it determines that a request to create a delivery schedule has been received (NO in step S502), and when it determines that the request has been received (YES in step S502), it proceeds to step S504.

[0156] In step S504, the information processing device 100 creates a delivery schedule. The delivery schedule may be a list of cylinders to be delivered in one delivery operation by a worker.

[0157] In step S506, information processing device 100 outputs the delivery schedule created in step S504. The delivery schedule may be output by being transmitted to information terminal 250, may be output by being displayed on display 150, or may be output by being printed on paper. Information terminal 250 may display the received delivery schedule on display 206.

[0158] FIG. 27 is a diagram showing an example of a delivery schedule display screen. Screen 2700 in FIG. 27 shows a delivery schedule for October 14, 2020. Screen 2700 includes a table showing customers who are delivery destinations. The table shows four customers (CL(1), CL(4), CL(5), and CL(8)), and for each customer, the cylinder IDs of the cylinders to be picked up and delivered are also shown.

[0159] The information processing device 100 may create a delivery schedule based on the customer management information 125 (FIG. 19). More specifically, for a customer whose exchange flag has an ON value, the information processing device 100 may create a delivery schedule by setting shipped cylinders whose exchange flag has an ON value as "cylinders to be picked up" and setting cylinders scheduled for shipping as "cylinders to be delivered."

[0160] In step S508, information processing device 100 determines whether the delivery schedule output in step S506 has been confirmed. If information processing device 100 determines that the delivery schedule has been confirmed (YES in step S508), it proceeds to step S510, and if not (NO in step S508), it returns control to step S504.

[0161] The worker may inquire of each customer whether or not they agree to the collection / delivery of the cylinders as described in the delivery schedule output in step S506. If a customer wishes to change the collection / delivery of the cylinders described in the delivery schedule, the worker inputs the changes into information processing device 100. As a result, information processing device 100 returns control from step S508 to step S504 and recreates a delivery schedule in accordance with the input changes.

[0162] Once consent is obtained from all customers, the worker inputs information indicating that the delivery schedule is finalized into the information processing device 100. Upon receiving the input of this information, the information processing device 100 determines that the delivery schedule has been finalized. As a result, control proceeds to step S510.

[0163] In step S510, the information processing device 100 acquires delivery routes for the (two or more) customers included in the delivery schedule. More specifically, the information processing device 100 inputs the (two or more) customers registered in the delivery schedule into a map application for route creation. In response to this, the map application creates a route for the vehicle 200 to travel by passing through the customers (locations corresponding to each of the customers). The information processing device 100 acquires, from the map application, the route created by the map application as the delivery route. The map application may be installed in the information processing device 100 or may be installed in another device on the network.

[0164] In step S512, information processing device 100 transmits the delivery route acquired in step S510 to information terminal 250. Thereafter, information processing device 100 returns control to step S502.

[0165] In response to the transmission of the delivery route from information processing device 100, information terminal 250 may display the delivery route transmitted from information processing device 100 on display 206 as described with reference to Fig. 6. The transmission of the delivery route from information processing device 100 to information terminal 250 is an example of providing a delivery route for picking up a cylinder whose remaining amount is determined to be equal to or less than a threshold.

[0166] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0167] 100 Information processing device, 121 Basic information table, 122 Cylinder management information, 123 Location management information, 124 Remaining amount management information, 125 Customer management information, 200 Vehicle, 250 Information terminal, 300 Filling facility, 350 IC tag reader, 400 Customer, 500 Cylinder, 500X Shoulder, 500Y Body, 500Z Bottom, 501 Tank, 530 Remaining amount meter, 536 Ultrasonic sensor, 590 Valve, 591 Cover, 600 Display screen.

Claims

1. 1. A computer-implemented method comprising: acquiring, from a communication device attached to each of the one or more cylinders, location information of the cylinder to which the communication device is attached; determining whether the acquired position information is outside an acceptable range by accessing a memory that stores an acceptable range for the position of each of the one or more cylinders; and outputting an alarm in response to determining that the location information is outside the allowable range.

2. determining whether a scheduled time for acquiring location information from the communication device has arrived; 2. The method for managing cylinders according to claim 1, further comprising the step of outputting an alarm in response to the fact that the location information has not been acquired when it is determined that the scheduled time has arrived.

3. the step of acquiring location information of the cylinder includes acquiring unique information of the cylinder; 3. The method for managing cylinders according to claim 1, wherein the memory stores an allowable range for the position of each of the one or more cylinders in association with the unique information.

4. acquiring, from a transmitter attached to each of the one or more cylinders, the amount of liquid remaining in the cylinder to which the transmitter is attached; determining whether the acquired remaining amount is equal to or less than a threshold value by accessing a memory that stores a threshold value associated with each of the one or more cylinders; A cylinder management method as described in any one of claims 1 to 3, further comprising a step of notifying that the cylinder corresponding to the remaining amount needs to be replaced in response to determining that the remaining amount is below the threshold.

5. The method for managing cylinders according to claim 4 , further comprising the step of providing a delivery route for picking up a cylinder whose remaining amount is determined to be equal to or less than the threshold value.

6. A program that, when executed by a computer, causes the computer to carry out the method according to any one of claims 1 to 5.

Images