Management system, management device, management method and program

The management system addresses the mismatch in resource provision by associating container cleanliness levels with unique identification, ensuring resources are provided according to user needs, thereby optimizing resource utilization and reducing costs through efficient reuse and sharing.

JP7807272B2Active Publication Date: 2026-01-27ORGANO CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2022045791
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-03-22
Publication Date
2026-01-27
Estimated Expiration
2042-03-22

AI Technical Summary

Technical Problem

Existing resource management systems lack the ability to provide resources that meet the specific needs of users, as they rely on a single criterion for determining reusability, leading to a mismatch between available resources and user requirements.

Method used

A management system that includes a first cleaning unit, a liquid quality acquisition unit, a database, and an output unit to associate and manage container cleanliness levels with unique identification information, allowing for targeted selection and provision of resources based on user-defined cleanliness levels.

Benefits of technology

Enables the provision of resources that meet user-specific needs by accurately matching container cleanliness levels with user requests, enhancing resource utilization and reducing costs through efficient reuse and sharing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007807272000001
    Figure 0007807272000001
  • Figure 0007807272000002
    Figure 0007807272000002
  • Figure 0007807272000003
    Figure 0007807272000003
Patent Text Reader

Abstract

To provide a resource corresponding to the needs of a user.SOLUTION: A management device includes a cleaning part 400 for cleaning a container with unique identification information attached, a fluid quality acquisition part 500 for acquiring the fluid quality of a cleaning fluid after the cleaning part 400 cleans the container, a database 600 for associating first cleanliness showing the fluid quality acquired by the fluid quality acquisition part 500 with the identification information attached to the container for storage, and a management device 300 for retrieving the identification information associated with the first cleanliness corresponding to second cleanliness requested from the outside from a database 600, and outputting the retrieved identification information.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a management system, a management device, a management method, and a program. [Background technology]

[0002] In recent years, resource reuse has been practiced in a variety of fields. For example, a technique has been devised in which used adsorbent cartridges are collected, and whether the adsorbent can be regenerated is determined based on the amount of residual moisture in the adsorbent separated from the collected adsorbent cartridge, and the adsorbent determined to be regenerative is filled into a container to reassemble the adsorbent cartridge (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-125396 Summary of the Invention [Problem to be solved by the invention]

[0004] In the technology described in Patent Document 1, there is only one criterion for determining whether or not something is renewable, and the recycled resources do not necessarily meet the needs of users. Therefore, there is a problem in that resources that meet the needs of users may not be provided.

[0005] An object of the present invention is to provide a management system, a management device, a management method, and a program that can provide resources that meet the needs of users. [Means for solving the problem]

[0006] The management system of the present invention comprises: a first cleaning unit that cleans containers to which unique identification information has been assigned; a liquid quality acquisition unit that acquires the liquid quality of the cleaning liquid after the first cleaning unit has cleaned the container; a database that stores a first cleanliness level indicating the liquid quality acquired by the liquid quality acquisition unit and identification information assigned to the container in association with each other; a search unit that searches the database for identification information associated with the first cleanliness level corresponding to a second cleanliness level requested from the outside; and an output unit that outputs the identification information searched by the search unit.

[0007] The management device of the present invention further comprises: an identification information acquisition unit that acquires identification information uniquely assigned to a container; a determination unit that determines a cleaning method for the container from which the filler has been removed, based on a contamination state of a cleaning liquid after the container has been cleaned in a state where the container is filled with the filler; a cleanliness acquisition unit that acquires a first cleanliness level indicating the quality of the cleaning liquid after the container from which the filler has been removed is cleaned using the cleaning method determined by the determination unit, and stores the acquired first cleanliness level and the identification information assigned to the container, which is acquired by the identification information acquisition unit, in a database in association with each other; a search unit that searches the database for identification information associated with the first cleanliness level corresponding to a second cleanliness level requested from the outside; and an output unit that outputs the identification information searched by the search unit.

[0008] Further, the management method of the present invention includes: A process of acquiring identification information uniquely assigned to a container; cleaning the container; A process of acquiring the quality of the cleaning liquid after cleaning the container; a process of storing the first cleanliness level indicating the obtained liquid quality and the obtained identification information assigned to the container in a database in association with each other; a process of searching the database for identification information associated with the first cleanliness level corresponding to the second cleanliness level requested from the outside; The searched identification information is output.

[0009] The program of the present invention also includes: A program to be executed by a computer, A step of obtaining identification information uniquely assigned to the container; cleaning the container; acquiring the quality of the cleaning liquid after cleaning the container; a step of storing the obtained first cleanliness level indicating the liquid quality and the obtained identification information assigned to the container in a database in association with each other; a step of searching the database for identification information associated with the first cleanliness level corresponding to a second cleanliness level requested from the outside; and a procedure for outputting the retrieved identification information. [Effects of the Invention]

[0010] In the present invention, resources can be provided according to the needs of users. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating a first embodiment of a management system according to the present invention. [Figure 2] 2 is a diagram showing an example of a container managed by the management system shown in FIG. 1. FIG. [Figure 3] 1. FIG. 4 is a diagram showing an example of the association between identification information and cleanliness levels stored in the database shown in FIG. [Figure 4] 2 is a diagram illustrating an example of an internal configuration of a management device illustrated in FIG. 1. FIG. [Figure 5] 2 is a flowchart for explaining an example of a cleanliness registration process in the management method in the management system shown in FIG. 1. [Figure 6] 2 is a flowchart for explaining an example of a container search process in the management method in the management system shown in FIG. [Figure 7] FIG. 10 is a diagram illustrating a second embodiment of a management system according to the present invention. [Figure 8]8 is a diagram showing an example of the association between identification information, cleanliness levels, and location information stored in the database shown in FIG. 7. FIG. [Figure 9] FIG. 8 is a diagram illustrating an example of an internal configuration of a management device illustrated in FIG. 7. [Figure 10] 8 is a flowchart illustrating an example of a method for registering container location information in the management system shown in FIG. 7. [Figure 11] FIG. 10 is a diagram illustrating a third embodiment of a management system according to the present invention. [Figure 12] FIG. 12 is a diagram showing an example of a container to which the sensor shown in FIG. 11 is attached. [Figure 13] 12 is a diagram showing an example of the association between identification information, cleanliness levels, and usage information stored in the database shown in FIG. 11. FIG. [Figure 14] 12 is a diagram illustrating an example of an internal configuration of a management device illustrated in FIG. 11. FIG. [Figure 15] 12 is a flowchart illustrating an example of a method for registering container usage information in the management system shown in FIG. 11. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. (First embodiment)

[0013] FIG. 1 is a diagram showing a first embodiment of a management system of the present invention. As shown in FIG. 1, the management system of this embodiment includes cleaning units 100, 400, a detection unit 200, a management device 300, a liquid-quality acquisition unit 500, and a database 600. The object managed by the management system shown in FIG. 1 is a container such as a column filled with (accommodating) a filler for treating a liquid. The container is a cartridge equipped with an inlet through which the liquid flows and an outlet through which the liquid flows out. The filler filled in the container is, for example, an ion-exchange resin, activated carbon, an adsorbent, or a zeolite such as a molecular sieve. This also applies to the following embodiments.

[0014] FIG. 2 is a diagram showing an example of a container managed by the management system shown in FIG. 1. As shown in FIG. 2, a container 10 managed by the management system shown in FIG. 1 is assigned unique identification information 11 that can identify the container 10. The identification information 11 may be represented by a barcode or a two-dimensional code. In this case, the barcode or two-dimensional code indicating the identification information 11 is attached, printed, baked, or the like to the container 10. The identification information 11 indicated by the barcode or two-dimensional code is read using a code reader. The identification information 11 may also be electronically written on an IC tag. In this case, an IC tag on which the identification information 11 is electronically written is attached to the container 10. The identification information 11 written on the IC tag is read using an IC tag reader. The code reader or IC tag reader transmits the read identification information 11 to the management device 300.

[0015] The cleaning unit 100 is a second cleaning unit that cleans the container filled with a filler. The cleaning unit 100 cleans the container while it is filled with a filler. The cleaning unit 100 cleans the container using a liquid such as an organic solvent or pure water. The timing for the cleaning unit 100 to clean the container is after the used container has been returned (collected).

[0016] The detection unit 200 detects the contamination state of the cleaning liquid after the cleaning unit 100 has cleaned the container. The detection unit 200 acquires the properties (hereinafter referred to as "liquid quality") of the cleaning liquid after the cleaning unit 100 has cleaned the container and detects the acquired results as the contamination state. The detection unit 200 transmits information indicating the detected contamination state to the management device 300. The method for detecting the contamination state is not particularly limited. In the case of online measurement, the contamination state can be detected based on the results of measuring pH, conductivity, resistivity, TOC (Total Organic Carbon) concentration, particle count, etc. If the measured conductivity is high or the resistivity is low, or if the TOC concentration is high or the particle count is high, the contamination level is detected as high. In the case of offline measurement, the contamination state can be detected based on the results of chromatography, atomic absorption, ICP-MS, or gel filtration. The contamination state can be determined using information on the treatment liquid used in the container and the contamination state of the filler and container. The contamination state may be a value indicated using a unit that indicates a predetermined liquid quality, or may be an index indicating the contamination level (e.g., a classification from "1" to "5"). This contamination state indicates the level of contamination of the container and filler.

[0017] The cleaning unit 400 is a first cleaning unit that cleans the container from which the filler has been removed. The cleaning unit 400 cleans the container using a cleaning method determined by the management device 300. The timing at which the cleaning unit 400 cleans the container is after the cleaning unit 100 has cleaned the container and the filler has been removed. The cleaning units 100 and 400 may be implemented in a single device.

[0018] The liquid quality acquisition unit 500 acquires the liquid quality of the cleaning liquid used by the cleaning unit 400. In this case, the liquid quality acquisition unit 500 may measure the liquid quality of the cleaning liquid used by the cleaning unit 400 and acquire the measured value, or may have another measuring device measure the liquid quality of the cleaning liquid used by the cleaning unit 400 and acquire the value measured by that measuring device. The liquid quality acquisition unit 500 transmits the acquired result to the management device 300 as cleanliness (first cleanliness). The measurement items and measurement method of the liquid quality are not particularly limited. Measurement items may include items that can be measured online, such as conductivity, resistivity, TOC concentration, and particle count. Furthermore, the measurement method may also include measuring ionic components or elemental components using chromatography, atomic absorption, ICP-MS, or the like.

[0019] The database 600 stores the cleanliness level, which indicates the liquid quality acquired by the liquid-quality acquisition unit 500, in association with the identification information assigned to the container. FIG. 3 is a diagram showing an example of the association between the identification information and the cleanliness level stored in the database 600 shown in FIG. 1. As shown in FIG. 3, the database 600 stores the identification information assigned to each container in association with the cleanliness level. The timing at which the identification information is read from the container is not particularly limited. The timing may be before the cleaning unit 100 cleans the container filled with the filler, or after the cleaning unit 400 cleans the container from which the filler has been removed. The cleanliness level may be a value indicated using a unit indicating a predetermined liquid quality, or may be a value indicating a cleanliness level (e.g., classified into five levels from "1" to "5").

[0020] The management device 300 manages containers to be managed. Fig. 4 is a diagram showing an example of the internal configuration of the management device 300 shown in Fig. 1. As shown in Fig. 4, the management device 300 shown in Fig. 1 has an identification information acquisition unit 310, a determination unit 320, a cleanliness acquisition unit 330, a search unit 340, and an output unit 350. Note that Fig. 4 shows only the main components related to this embodiment among the components included in the management device 300 shown in Fig. 1.

[0021] The identification information acquisition unit 310 acquires the identification information from the container. The identification information acquisition unit 310 acquires the identification information transmitted from a code reader or an IC tag reader. The timing for the identification information acquisition unit 310 to acquire the identification information is preferably when a used container is returned and before the cleaning unit 100 cleans the container. The identification information acquisition unit 310 outputs the acquired identification information to the cleanliness acquisition unit 330.

[0022] The determination unit 320 determines a cleaning method for the container from which the filler has been removed, based on the contamination state detected by the detection unit 200. The determination unit 320 may store in advance a plurality of cleaning methods corresponding to a plurality of contamination states, and select a cleaning method corresponding to the contamination state detected by the detection unit 200. Furthermore, when the contamination state detected by the detection unit 200 is expressed as a numerical value, the determination unit 320 may adopt a cleaning method calculated using the numerical value. The determination unit 320 notifies the cleaning unit 400 of the determined cleaning method, thereby instructing the cleaning unit 400 to use the determined cleaning method to clean the container.

[0023] The cleanliness acquiring unit 330 acquires the cleanliness transmitted from the liquid property acquiring unit 500. The cleanliness acquiring unit 330 associates the acquired cleanliness with the identification information acquired by the identification information acquiring unit 310 and stores them in a database.

[0024] The search unit 340 searches the database 600 for identification information associated with a cleanliness level that satisfies the condition indicated by the request information. Specifically, the search unit 340 uses the condition indicated by the request information as a search key to search for cleanliness levels stored in the database 600 that satisfy the condition. That is, the search unit 340 determines a cleanliness level (second cleanliness level) based on the condition indicated by the request information, searches the database 600 for a first cleanliness level that corresponds to the second cleanliness level, and acquires from the database 600 identification information associated with the searched first cleanliness level. At this time, if the request information includes a value of the second cleanliness level, the search unit 340 searches the database 600 for a first cleanliness level that corresponds to the value of the second cleanliness level included in the request information. If a first cleanliness level having the same value as the second cleanliness level value (or class, grade, range, etc.; the same applies hereinafter) determined by the search unit 340 is stored in the database 600, the search unit 340 acquires identification information associated with the first cleanliness level from the database 600. If a first cleanliness level having the same value as the second cleanliness level value determined by the search unit 340 is not stored in the database 600, the search unit 340 acquires identification information associated with a first cleanliness level having a higher (larger) value than the determined second cleanliness level value from the database 600. At this time, the search unit 340 may acquire identification information associated with a first cleanliness level having a value closer to the second cleanliness level value from the database 600. This request information is information input from outside (for example, an input means operated by a user using the present system). The request information is information indicating a request from a user who wishes to use a container, and includes information indicating the cleanliness level range of the container desired to be used. The request information includes, for example, information on the liquid quality obtained after passing the filler (contained metal concentration, TOC concentration, number of particles, turbidity, resistivity, etc.) and information on the cleanliness of the container (contained metal concentration, TOC concentration, number of particles, turbidity, resistivity, etc.). Furthermore, the condition indicated by the request information may be a value indicated using a unit indicating a predetermined number, or may be an index indicating the cleanliness (e.g., classified into classes from "1" to "5"). The search unit 340 outputs the searched identification information to the output unit 350.

[0025] The output unit 350 outputs the identification information output from the search unit 340. The output unit 350 may display the identification information on a predetermined screen or may transmit it to another device. The output unit 350 may also output the identification information as audio or print it out.

[0026] Database 600 may also store container information and usage history in association with the identification information. Examples of container information and usage history include the container's manufacturing date, the container's serial number and manufacturer, the container's components and materials, the date and location of use, history information about the filler filled in the container (such as the filler's manufacturing date, brand, lot number, warranty expiration date, filling date and time, and disposal date and time), the solvent, delivery data (such as the carrier and delivery time), contamination levels previously detected by detection unit 200, cleaning methods previously used by cleaning unit 400, cleanliness levels previously acquired by liquid quality acquisition unit 500, dates and times of previous cleaning by cleaning units 100 and 400, and test results if other tests have been performed. Search unit 340 may also output this information associated with the retrieved identification information to output unit 350, and output unit 350 may output it. Storing this information in database 600 and managing containers allows the usage status of each container to be understood, enabling prompt action to be taken if a problem occurs with a container. In addition, it is possible to easily plan the usage schedule for each container. Furthermore, various notifications, such as important points to note regarding the use of the container, can be sent to users who use the container. For example, the usage status of the container can be grasped based on the information stored in the database 600 regarding the shipping date of the container and whether or not it has been returned. Furthermore, if a problem occurs, such as a failure to achieve the expected processing performance, information for investigating the cause can be immediately obtained by tracing the usage history and filler information stored in the database 600. Furthermore, it is possible to predict the use of the container and plan the usage schedule based on the information accumulated in the database 600 from shipping to return. Furthermore, if the usage status can be grasped, it is possible to notify users who have not returned the container for a certain period of time of important points, such as the expiration date of the filler warranty and the need to return the container.

[0027] The following describes the management method in the management system shown in Fig. 1. First, we will explain the cleanliness registration process in the management method in the management system shown in Fig. 1. Fig. 5 is a flowchart for explaining an example of the cleanliness registration process in the management method in the management system shown in Fig. 1.

[0028] First, when a used container is returned, the identification information acquisition unit 310 acquires the container identification information read by the reader (Step S1). Next, the cleaning unit 100 uses a cleaning liquid to clean the container filled with filler (Step S2). The detection unit 200 detects the contamination state of the cleaning liquid after the cleaning unit 100 has cleaned the container (Step S3). The determination unit 320 determines a cleaning method for the container from which the filler has been removed based on the contamination state detected by the detection unit 200 (Step S4). Thereafter, the filler is removed from the container (Step S5), and the cleaning unit 400 cleans the container from which the filler has been removed using the cleaning method determined by the determination unit 320 (Step S6). The liquid property acquisition unit 500 acquires a value indicating the liquid quality of the cleaning liquid used by the cleaning unit 400 (Step S7). The cleanliness acquisition unit 330 associates the cleanliness acquired by the liquid property acquisition unit 500 with the identification information acquired by the identification information acquisition unit 310 and stores them in a database (step S8). Thereafter, the container is dried and stored.

[0029] Next, a description will be given of a container search process in the management method in the management system shown in Fig. 1. Fig. 6 is a flowchart for explaining an example of a container search process in the management method in the management system shown in Fig. 1.

[0030] First, the management device 300 receives request information (step S11). Here, the method by which the management device 300 receives the request information is not particularly limited. For example, the management device 300 may receive the request information transmitted from a communication device capable of communicating with the management device 300, or the request information may be directly input to the management device 300. The search unit 340 searches the database 600 for a cleanliness level that satisfies the conditions indicated by the request information (step S12). Next, the search unit 340 reads out identification information associated with the searched cleanliness level from the database 600 (step S13). Then, the output unit 350 outputs the identification information read out by the search unit 340 (step S14). Thereafter, the container to which the output identification information is assigned is filled with a filler based on the request information. The container filled with the filler is washed and shipped.

[0031] In step S13, the management device 300 performs the following procedure so that the search unit 340 can search for identification information of containers that satisfy the conditions indicated by the request information. First, the management device 300 classifies the washed containers into multiple classes according to their cleanliness. These multiple classes may be, for example, "water grade (lower quality than pure water or ultrapure water)," "pure water grade," "ultrapure water grade," etc., or may be multiple grades expressed using numerical values ​​according to the liquid quality, such as "Grade 1" to "Grade 5." At this time, the management device 300 compares the cleanliness with a preset threshold and classifies the containers into multiple classes based on the comparison results. When the management device 300 receives the request information, the search unit 340 searches for containers of a class that satisfies the conditions indicated by the request information. At this time, if the received request information includes cleanliness, the search unit 340 selects (searches for) containers of a class that satisfies the cleanliness level included in the request information. On the other hand, if the received request information does not include cleanliness but includes conditions other than cleanliness, such as TOC concentration or particle count, the management device 300 first determines a cleanliness level that satisfies the conditions included in the request information. This determination method may involve the management device 300 determining the cleanliness level based on information that previously associates TOC concentration, particle count, etc. with cleanliness levels. Alternatively, this determination method may involve determining (calculating) the cleanliness level from TOC concentration, particle count, etc. using a predetermined calculation. Next, based on the determined cleanliness level, the search unit 340 selects a container of a class that satisfies the cleanliness level.

[0032] In this manner, in this embodiment, the quality of the cleaning liquid after cleaning a container filled with a filler used in liquid processing is measured, and the cleanliness level indicating the measured liquid quality is stored in a database in association with identification information uniquely assigned to the container. When a user requests the use of a container, the database is searched for and outputted with identification information associated with the cleanliness level that meets the conditions of the request. This makes it possible to provide resources according to the user's needs. Furthermore, if the conditions indicated by the request information are met, it becomes possible to reuse (re-provision) not only the specific container used by the user, but also other containers. This allows for the sharing of containers, thereby reducing costs and equipment. (Second embodiment)

[0033] Fig. 7 is a diagram showing a second embodiment of the management system of the present invention. As shown in Fig. 7, the management system in this embodiment has cleaning units 100, 400, a detection unit 200, a management device 301, a liquid property acquisition unit 500, and a database 601. The cleaning units 100, 400, the detection unit 200, and the liquid property acquisition unit 500 are the same as those in the first embodiment.

[0034] The database 601 stores location information indicating the location of a container in addition to the information stored in the database 600 in the first embodiment. FIG. 8 is a diagram showing an example of the association between identification information, cleanliness levels, and location information stored in the database 601 shown in FIG. 7. As shown in FIG. 8, the database 601 stores identification information assigned to each container, cleanliness levels, and location information in association with each other. The identification information and cleanliness levels are the same as those in the first embodiment. The location information is information indicating the location of a container and is information obtained using any means. The location of this container is the location after the container is shipped or the location before it is shipped (for example, the location of a warehouse where the container is stored or the storage location within the warehouse).

[0035] The management device 301 manages containers to be managed. FIG. 9 is a diagram showing an example of the internal configuration of the management device 301 shown in FIG. 7. As shown in FIG. 9, the management device 301 shown in FIG. 7 has an identification information acquisition unit 310, a determination unit 320, a cleanliness acquisition unit 330, a search unit 340, an output unit 350, and a position information acquisition unit 361. Note that FIG. 9 shows only the main components related to this embodiment among the components included in the management device 301 shown in FIG. 7. The identification information acquisition unit 310, the determination unit 320, the cleanliness acquisition unit 330, the search unit 340, and the output unit 350 are the same as those in the first embodiment.

[0036] The location information acquisition unit 361 acquires location information indicating the location of a container. The location information acquisition unit 361 stores the acquired location information in the database 601. At this time, the location information acquisition unit 361 associates the acquired location information with identification information of a container located at the location indicated by the acquired location information and stores the location information in the database 601. The method by which the location information acquisition unit 361 acquires the location information is not particularly limited. For example, if the container is equipped with a function for acquiring location information, such as a GPS (Global Positioning System) function, the method may be a method of acquiring the location information using the function. The method may also be a method of calculating and acquiring the location information based on the delivery route and delivery time of the container. Note that when acquiring the location information of a container, the location information acquisition unit 361 also acquires the identification information of the container along with the location information. The method of acquiring the identification information is also not particularly limited. For example, the acquisition method may be a method of acquiring the identification information transmitted from the container along with the location information. Alternatively, the method may involve acquiring identification information associated with the delivery route and delivery time stored in database 601 when calculating location information based on the delivery route and delivery time of the container.

[0037] The following describes a method for registering container position information in the management system shown in Fig. 7. Fig. 10 is a flowchart for explaining an example of a method for registering container position information in the management system shown in Fig. 7.

[0038] When the location information acquisition unit 361 acquires the location information and identification information of a container (step S31), the location information acquisition unit 361 searches the database 601 for the acquired identification information (step S32). The location information acquisition unit 361 stores the location information in the database 601 in association with the retrieved identification information (step S33).

[0039] In this way, in this embodiment, location information indicating the location of a container is acquired and associated with the identification information and registered in a database. This makes it possible to manage the current location of the container. By knowing the current location of the container, it is possible to easily plan the use of the container. (Third embodiment)

[0040] Fig. 11 is a diagram showing a third embodiment of the management system of the present invention. As shown in Fig. 11, the management system in this embodiment has cleaning units 100, 400, a detection unit 200, a management device 302, a liquid property acquisition unit 500, a database 602, and a sensor 12. The cleaning units 100, 400, the detection unit 200, and the liquid property acquisition unit 500 are the same as those in the first embodiment.

[0041] The sensor 12 is attached to a container and detects that the container has been used. FIG. 12 is a diagram showing an example of a container to which the sensor 12 shown in FIG. 11 has been attached. As shown in FIG. 12, the sensor 12 is attached to a container 10 to which identification information 11 has been attached. The identification information 11 is the same as that in the first embodiment. The sensor 12 detects that the container 10 has been used. There are no particular limitations on the mechanism by which the sensor 12 detects that the container 10 has been used. When the sensor 12 detects that the container 10 has been used, it transmits the identification information 11 attached to the container 10 in a predetermined signal to the management device 302. This predetermined signal may be any signal that can recognize that the container 10 to which the sensor 12 has been attached has been used.

[0042] In addition to the information stored in the database 600 in the first embodiment, the database 602 stores usage information indicating whether a container has been used. FIG. 13 is a diagram showing an example of the association between identification information, cleanliness levels, and usage information stored in the database 602 shown in FIG. 11. As shown in FIG. 13, the database 602 stores identification information assigned to each container, cleanliness levels, and usage information in association with each other. The identification information and cleanliness levels are the same as those in the first embodiment. The usage information is information indicating whether a container has been used (whether it is used or unused). The usage information is information based on a signal transmitted from the sensor 12.

[0043] The management device 302 manages containers to be managed. FIG. 14 is a diagram showing an example of the internal configuration of the management device 302 shown in FIG. 11. As shown in FIG. 14, the management device 302 shown in FIG. 11 has an identification information acquisition unit 310, a determination unit 320, a cleanliness acquisition unit 330, a search unit 340, an output unit 350, and a usage information writing unit 372. Note that FIG. 14 shows only the main components related to this embodiment among the components included in the management device 302 shown in FIG. 11. The identification information acquisition unit 310, the determination unit 320, the cleanliness acquisition unit 330, the search unit 340, and the output unit 350 are the same as those in the first embodiment.

[0044] The usage information writing unit 372 stores the usage information of the container in the database 602 based on the information indicated by the signal transmitted from the sensor 12. When the container is shipped, the usage information writing unit 372 stores the usage information associated with the identification information assigned to the container as "unused," and rewrites the usage information to "used" when a predetermined signal is transmitted from the sensor 12. The sensor 12 may also have a function that indicates the time it has been in use (operating time).

[0045] The following describes a method for registering container usage information in the management system shown in Fig. 11. Fig. 15 is a flowchart for explaining an example of a method for registering container usage information in the management system shown in Fig. 11.

[0046] When the sensor 12 transmits a predetermined signal indicating that the container has been used and the usage information writing unit 372 receives the signal (step S41), the usage information writing unit 372 searches the database 602 for the identification information included in the signal (step S42). The usage information writing unit 372 rewrites the usage information associated with the searched identification information from "unused" to "used" (step S43).

[0047] In this manner, in this embodiment, when a sensor attached to a container receives a signal indicating that the container has been used, the usage information stored in the database in association with the identification information contained in the signal is rewritten to information indicating that the container has been used. This allows the current usage status of the container to be managed. By being able to recognize the usage status, if the warranty period of the filler filled in the container in an unused state is approaching, the user who owns the container can be notified of the approaching warranty period. In addition, the container rotation cycle can be automatically calculated based on information such as the usage status and usage period obtained from sensor 12 and the order, shipping, and return history stored in database 600, and a container shipping schedule can be created.

[0048] Although the above description has been given with each component being assigned a respective function (process), this allocation is not limited to the above. Furthermore, the configuration of the components is also not limited to the above-described configuration, and the above-described embodiments are merely examples. Furthermore, the management devices 300-302 and databases 600-602 may be connected to other components via a communication network, or may be located on a cloud.

[0049] The processes performed by each of the management devices 300-302 may be performed by a logic circuit individually designed for each purpose. Alternatively, a computer program (hereinafter referred to as a program) describing the process procedures may be recorded on a recording medium readable by each of the management devices 300-302, and the program recorded on the recording medium may be read and executed by each of the management devices 300-302. Examples of recording media readable by each of the management devices 300-302 include removable recording media such as magneto-optical disks, DVDs (Digital Versatile Discs), CDs (Compact Discs), Blu-ray (registered trademark) Discs, and USB (Universal Serial Bus) memories, as well as memories such as ROMs (Read Only Memory), RAMs (Random Access Memory), HDDs (Hard Disc Drives), and SSDs (Solid State Drives) built into each of the management devices 300-302. The programs recorded on the recording media are read by a CPU provided in each of the management devices 300-302, and the same processes as those described above are performed under the control of the CPU. Here, the CPU operates as a computer that executes a program read from a recording medium on which the program is recorded. [Explanation of symbols]

[0050] 10 containers 11 Identification Information 12 sensors 100,400 Cleaning section 200 Detector 300~302 Management device 310 Identification information acquisition unit 320 Decision Section 330 Cleanliness Acquisition Department 340 Search Department 350 Output Section 361 Location information acquisition unit 372 Usage information writing section 500 Liquid quality acquisition section 600~602 Database

Claims

1. a first cleaning unit that cleans containers to which unique identification information has been assigned; a liquid quality acquiring unit that acquires the liquid quality of the cleaning liquid after the first cleaning unit has cleaned the container; a database that stores a first cleanliness level indicating the liquid quality acquired by the liquid quality acquisition unit and identification information assigned to the container in association with each other; a search unit that searches the database for identification information associated with the first cleanliness level corresponding to a second cleanliness level requested from the outside; an output unit that outputs the identification information searched by the search unit.

2. 2. The management system according to claim 1, determining the second cleanliness level based on the received conditions; The search unit searches the database for identification information associated with the first cleanliness level corresponding to the determined second cleanliness level.

3. 3. The management system according to claim 1, a second cleaning unit that cleans the container while the container is filled with the filler; a detection unit that detects a contamination state of the cleaning liquid after the second cleaning unit has cleaned the container; a determination unit that determines a cleaning method for the container from which the filler has been removed based on the contamination state detected by the detection unit, The first cleaning unit cleans the container from which the filler has been removed using the cleaning method determined by the determination unit.

4. 4. The management system according to claim 1, The database is a management system that stores the usage history of the container in association with the identification information assigned to the container.

5. 5. The management system according to claim 1, a position information acquisition unit that acquires position information indicating the position of the container; The database is a management system that stores the container location information acquired by the location information acquisition unit and the identification information assigned to the container in association with each other.

6. 6. The management system according to claim 1, a sensor for detecting when the container has been used; The database is a management system that stores the results detected by the sensor and the identification information assigned to the container in association with each other.

7. 7. The management system according to claim 1, The container is a cartridge having an inlet through which the liquid flows and an outlet through which the liquid flows out.

8. an identification information acquisition unit that acquires identification information uniquely assigned to a container; a determination unit that determines a cleaning method for the container from which the filler has been removed, based on a contamination state of a cleaning liquid after the container has been cleaned in a state where the container is filled with the filler; a cleanliness acquisition unit that acquires a first cleanliness level indicating the quality of the cleaning liquid after the container from which the filler has been removed is cleaned using the cleaning method determined by the determination unit, and associates the acquired first cleanliness level with the identification information assigned to the container obtained by the identification information acquisition unit and stores them in a database; a search unit that searches the database for identification information associated with the first cleanliness level corresponding to a second cleanliness level requested from the outside; an output unit that outputs the identification information searched by the search unit;

9. A process of acquiring identification information uniquely assigned to the container; cleaning the container; A process of acquiring the quality of the cleaning liquid after cleaning the container; a process of storing the first cleanliness level indicating the obtained liquid quality and the obtained identification information assigned to the container in a database in association with each other; a process of searching the database for identification information associated with the first cleanliness level corresponding to the second cleanliness level requested from the outside; and outputting the searched identification information.

10. On the computer, A step of obtaining identification information uniquely assigned to the container; cleaning the container; acquiring the quality of the cleaning liquid after cleaning the container; a step of storing the obtained first cleanliness level, which indicates the liquid quality, in a database in association with the obtained identification information assigned to the container; a step of searching the database for identification information associated with the first cleanliness level corresponding to a second cleanliness level requested from the outside; and a program for executing a procedure for outputting the searched identification information.

Citation Information

Patent Citations

  • Method of recycling adsorbent cartridge

    JP2010125396A

  • Container management system, container information reading device, and rack information reading device

    JP2014190864A

  • Production method of resist composition

    JP2015072418A

  • Liquid purification cartridge, and method of purifying liquid

    JP2019195763A

  • Industrial cleanliness measurement methodology

    US20170066020A1