Parts management system and program for analytical equipment

Abstract

To achieve proper component control for an analysis device.SOLUTION: A component control system for an analysis device includes an analysis device, and a server connected with the analysis device via a network. The analysis device includes a component registration unit that registers information on components mounted to the analysis device, and an information transfer unit that transfers the component information registered in the component registration unit to the server via the network. The server includes a database registration unit that registers the component information transferred by the information transfer unit in a database to create a component control database, and an alarm period setting unit that sets an alarm period promoting replacement work for each component registered in the component control database in a category unit of an organization of a user using the analysis device.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a parts management system and a program for an analytical device. [Background technology]

[0002] Analytical devices such as liquid chromatographs use a large number of parts. These parts include parts that require replacement when they have been used a certain number of times (hereinafter referred to as consumables). These parts also include parts that require replacement when they have been used for a certain period of time (hereinafter referred to as maintenance parts). For the analytical device to operate normally, these consumables and maintenance parts must be replaced appropriately.

[0003] By counting the number of times a consumable item has been used, it is possible to accurately determine when it is time to replace it. On the other hand, managing the usage period of maintenance parts is complicated. The frequency with which an analyzer is used varies from user to user. In order to manage the usage period of maintenance parts, it is necessary to manage the period according to the frequency of use. In Patent Document 1 listed below, parts are managed by calculating the planned replacement date according to the average daily usage. [Patent Document 1] Japanese Patent Application Publication No. 2014-32022 Summary of the Invention [Problem to be solved by the invention]

[0004] As mentioned above, the frequency of use of maintenance parts varies from user to user, making management of their usage periods cumbersome. The method disclosed in Patent Document 1 is one solution for predicting when to replace maintenance parts. However, for users who use multiple analytical devices, managing the parts installed in multiple analytical devices remains a challenge. For example, there are companies that use multiple analytical devices across the country or the world. Such companies desire to more efficiently manage the usage periods of parts for each analytical device.

[0005] An object of the present invention is to provide a system and a program that are capable of appropriately managing parts of an analyzer. [Means for solving the problem]

[0006] An embodiment according to one aspect of the present invention relates to a parts management system for an analytical device, comprising an analytical device and a server connected to the analytical device via a network, wherein the analytical device includes a parts registration unit that registers information about parts attached to the analytical device and an information transfer unit that transfers the parts information registered in the parts registration unit to the server via the network, and the server includes a database registration unit that creates a parts management database by registering the parts information transferred by the information transfer unit in a database, and a warning time setting unit that sets warning times that prompt replacement work for each part registered in the parts management database on a category basis for the organization of a user who uses the analytical device. [Effects of the Invention]

[0007] According to the present invention, parts management of an analyzer can be performed appropriately. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is an overall view of a parts management system for a liquid chromatograph according to an embodiment. [Figure 2] FIG. 2 is a functional block diagram of the liquid chromatograph according to the embodiment. [Figure 3] FIG. 3 is a diagram showing an example of part information registered in the part registration unit. [Figure 4] FIG. 4 is a configuration diagram of a server according to an embodiment. [Figure 5] FIG. 5 is a functional block diagram of the server and the management PC according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of registration in the parts management database. [Figure 7] FIG. 7 shows a parts management screen displayed by executing the parts management program. [Figure 8] FIG. 8 shows the warning days setting screen. [Figure 9] FIG. 9 shows the warning days setting screen. [Figure 10] FIG. 10 is a flowchart showing the parts management method. DETAILED DESCRIPTION OF THE INVENTION

[0009] Next, the configuration of a parts management system for a liquid chromatograph according to an embodiment of the present invention will be described with reference to the accompanying drawings.

[0010] (1) Overall configuration of parts management system FIG. 1 is an overall view showing a parts management system for a liquid chromatograph according to an embodiment. The parts management system includes a liquid chromatograph 1, a registration PC (Personal Computer) 5, a server 7, and a management PC (Personal Computer) 9. The liquid chromatograph 1, the registration PC 5, and the management PC 9 are connected to a LAN (Local Area Network) 4. The LAN 4 is connected to a WAN (Wide Area Network) 8 via a gateway 6. The server 7 is connected to the WAN 8. The WAN 8 is, for example, the Internet.

[0011] In this way, the liquid chromatograph 1 is connected to the server 7 via a network including the LAN 4 and the WAN 8. In addition to the liquid chromatograph 1 shown in FIG. 1 , liquid chromatographs installed at other locations are also connected to the server 7 via the network. For example, another liquid chromatograph connected to the LAN 4 is connected to the server 7 via the network. Alternatively, a liquid chromatograph connected to another LAN at another location is connected to the server 7 via the network.

[0012] For example, a company that is a user uses a large number of liquid chromatographs at its business locations in Japan and other countries. The large number of liquid chromatographs connected to each of the company's business locations in each country are connected to server 7 via a network. As will be described later, server 7 manages information on parts attached to the multiple liquid chromatographs connected via the network. In other words, in this embodiment, information on parts for multiple liquid chromatographs installed in multiple regions is managed by server 7 on the cloud.

[0013] In the following explanation, an example will be given in which the parts management system for a liquid chromatograph of this embodiment manages parts (hereinafter referred to as maintenance parts) that require replacement when their usage period reaches a predetermined period.

[0014] (2) Liquid chromatograph configuration 1, the liquid chromatograph 1 includes a system controller 11 and a plurality of functional units 12. The system controller 11 performs overall control of the liquid chromatograph 1. The system controller 11 is connected to a LAN 4.

[0015] The liquid chromatograph 1 of this embodiment includes four functional units 12. Specifically, the liquid chromatograph 1 includes the following functional units 12: a pump unit 12A, an autosampler unit 12B, a column oven unit 12C, and a detector unit 12D. The pump unit 12A, the autosampler unit 12B, the column oven unit 12C, and the detector unit 12D are connected to a system controller 11 by communication cables. Each functional unit 12 is controlled by the system controller 11.

[0016] 2 is a functional block diagram of the liquid chromatograph 1. The system controller 11 includes a communication unit 111. The communication unit 111 communicates with the registration PC 5 via the LAN 4. The communication unit 111 communicates with the server 7 via the LAN 4, the gateway 6, and the WAN 8. The system controller 11 includes a display and an operation unit (not shown). An operator checks the status of the liquid chromatograph 1 by referring to the display included in the system controller 11, and performs various setting operations for the liquid chromatograph 1 by operating the operation unit.

[0017] The functional unit 12 includes a part registration unit 121 and an information transfer unit 122. As described above, the liquid chromatograph 1 includes the pump unit 12A, the autosampler unit 12B, the column oven unit 12C, and the detector unit 12D as functional units 12. In FIG. 2, one functional unit 12 is shown as a representative of these four functional units 12, and each of these four functional units 12 includes a part registration unit 121 and an information transfer unit 122.

[0018] The part registration unit 121 includes a storage unit, and registers information about parts attached to the functional units 12 in the storage unit. FIG. 3 is a diagram showing an example of part information T1 registered in the part registration unit 121. As described above, each functional unit 12 includes a part registration unit 121. The part registration unit 121 included in each functional unit 12 registers part information T1 about parts attached to that functional unit 12. For example, the part registration unit 121 of the pump unit 12A registers part information T1 about parts attached to the pump unit 12A.

[0019] FIG. 3 shows an example of part information T1 registered in the part registration section 121 of the column oven unit 12C. The part information T1 includes information about the part ID, part name, start date of use, and number of days since replacement for each registered part. By referencing the start date of use for each part registered in the part information T1, the usage period of the installed part can be calculated. As will be explained later, the number of days since replacement is registered is a default number of days since recommended replacement. The number of days since replacement is counted from the start date of use.

[0020] The registration of part information T1 in the part registration unit 121 is performed by the registration PC 5 shown in FIGS. 1 and 2. In the registration PC 5, a user executes part registration processing for each functional unit 12. The registration PC 5 transmits the part registration information to the system controller 11 of the liquid chromatograph 1 via the LAN 4. The system controller 11 provides the received part registration information to the part registration unit 121 of the functional unit 12. The part registration unit 121 registers the received part registration information as part information T1. The date on which the part registration processing was performed by the registration PC is registered as the use start date of the part information T1.

[0021] (3) Server configuration FIG. 4 is a diagram showing the configuration of the server 7. The server 7 includes a CPU (Central Processing Unit) 71, a RAM (Random Access Memory) 72, a storage device 73, and a communication unit 76. The CPU 71, RAM 72, storage device 73, and communication unit 76 are connected via a bus. The storage device 73 may be, for example, a hard disk. The storage device 73 stores a parts management database 75 and a parts management program P1. The communication unit 76 is connected to a WAN 8. The communication unit 76 communicates with the system controller 11 of the liquid chromatograph 1 and the management PC 9 via the WAN 8, the gateway 6, and the LAN 4.

[0022] The parts management database 75 is a database that manages parts information T1 acquired via the network. The parts management program P1 is a program that manages the parts management database 75. The parts management program P1 executes processes such as registering the parts information T1 received from the functional unit 12 in the parts management database 75, updating the information registered in the parts management database 75, and generating viewing data (user interface) that enables the information registered in the parts management database 75 to be viewed on the management PC 9.

[0023] (4) Functional configuration of the server and management PC 5 is a functional block diagram of the server 7 and the management PC 9. The server 7 includes a control unit 77. The control unit 77 includes a database registration unit 771, a warning timing setting unit 772, and an information disclosure unit 773. The control unit 77 is a functional unit realized by the component management program P1 shown in FIG. 4 being executed on the CPU 71 while using the RAM 72 as a work area.

[0024] The database registration unit 771 receives part information T1 from the liquid chromatograph 1. The database registration unit 771 registers the received part information T1 in the part management database 75. As described above, a plurality of liquid chromatographs, including the liquid chromatograph 1 shown in FIG. 1, are connected to the server 7. The database registration unit 771 receives part information T1 from these plurality of liquid chromatographs. The database registration unit 771 then registers the part information T1 related to the parts attached to the plurality of liquid chromatographs in the part management database 75 for centralized management.

[0025] The warning time setting unit 772 sets the "number of warning days" in the information of the part registered in the part management database 75. The operation for setting the number of warning days is performed in the management PC 9. The warning time setting unit 772 registers the "number of warning days" in the part management database 75 based on the setting information for the number of warning days received from the management PC 9.

[0026] The information disclosure unit 773 transmits information about parts registered in the parts management database 75 via the network as information that can be viewed on the management PC 9. The information disclosure unit 773 transmits information about parts registered in the parts management database 75 via the network, for example, by using a WWW server function provided in the server 7.

[0027] (5) Contents of the parts management database 6 is a diagram showing an example of registration in the parts management database 75. The parts management database 75 stores the following as part information: "Area 1" "Region 2" "Department 1" "Department 2" "Device" "Use start date" Number of days for replacement will be registered.

[0028] The name of the country in which the liquid chromatograph 1 is installed is registered in "Region 1." A smaller region (such as a state, prefecture, or region) than the country in which the liquid chromatograph 1 is installed is registered in "Region 2." The names of the departments within the user's organization in which the liquid chromatograph 1 is installed are registered in "Department 1" and "Department 2." The device identification number of the liquid chromatograph 1 is registered in "Device." The "Part Name," "Start Date of Use," and "Number of Days Until Replacement" reflect the information registered in the part information T1 received from the functional unit 12 of the liquid chromatograph 1. The "Start Date of Use," as described above, records the date on which the part registration process was performed by the registration PC 5. The "Number of Days Until Replacement" indicates the number of days after which the part is recommended to be replaced, starting from the "Start Date of Use." The "Number of Days Until Replacement" is, for example, the default number of days until recommended replacement set by the part's manufacturer.

[0029] The "warning days" is the number of days from the "start date of use" that indicates the number of days after which a warning for part replacement is issued to the user. The "replacement days" is the number of days after which replacement is recommended, while the "warning days" is the number of days after which a warning is issued. Because part replacement is a time-consuming and labor-intensive task for users, it is preferable to notify the user of part replacement in advance, taking this time into consideration. Therefore, the "warning days" is set to a number of days shorter than the "replacement days." Furthermore, as described above, the "replacement days" is the default recommended number of days after replacement set by the manufacturer, etc. Users vary in the frequency of use of the liquid chromatograph 1. Therefore, while the "replacement days" is a guideline for replacement based on general usage, the "warning days" is the number of days set according to the actual usage conditions of the user who uses the liquid chromatograph 1. Furthermore, the "warning days" is set by the user of the liquid chromatograph 1 for each category: "Area 1," "Area 2," "Department 1," or "Department 2." Alternatively, the "warning days" is set by the user of the liquid chromatograph 1 on an "apparatus" basis.

[0030] (6) Processing flow of parts management system Next, the processing flow of the parts management system will be explained. First, an operator operates the registration PC 5 to register parts attached to each functional unit 12 of the liquid chromatograph 1. A program for registering parts is enabled in the registration PC 5. When the operator registers parts on the registration PC 5, the registration information for the parts is sent to the liquid chromatograph 1.

[0031] When the system controller 11 of the liquid chromatograph 1 receives the part registration information from the registration PC 5, it provides the part registration information to the functional unit 12 to which it should be registered. Each functional unit 12 receives the registration information of the part attached to its own functional unit 12 and registers it as part information T1 in the part registration unit 121. At this time, the date on which the part information T1 was registered in the part registration unit 121 is registered as the "use start date" in the part information T1. Through the above operations, each functional unit 12 registers part information T1 for the part attached to its own functional unit 12. The above operations are performed, for example, at a manufacturing plant for the liquid chromatograph 1. Alternatively, the above operations may be performed within the business premises of the user company.

[0032] Next, the liquid chromatograph 1 is installed at the location where it will actually be used. For example, the liquid chromatograph 1 is delivered from a manufacturing plant and installed on the floor of the relevant department of the user company. Once the liquid chromatograph 1 is installed at the location where it will actually be used to perform analytical processing, the system controller 11 is connected to the LAN 4. This enables the system controller 11 to communicate with the server 7 via the LAN 4, the gateway 6, and the WAN 8.

[0033] Once the system controller 11 is able to communicate with the server 7, the information transfer unit 122 of the functional unit 12 then transmits the part information T1 to the server 7. When the server 7 receives the part information T1 from the functional unit 12, the database registration unit 771 registers the part information T1 in the part management database 75. This operation is performed in all functional units 12. The part information T1 of all functional units 12 is registered in the part management database 75.

[0034] When the liquid chromatograph 1 is installed at the location of use in the department of the user company, the user may update the start date of use registered in the part information T1 to the date of installation at the location of use. For example, if a considerable number of days have passed between the time the part information T1 was registered at the manufacturing plant and the time it was installed at the location of use, updating the start date of use allows for more accurate calculation of the usage period. The start date of use may be updated via the network in the registration PC 5, or by operating the operation unit of the system controller 11. The information transfer unit 122 transfers the information again after the start date of use is updated. As a result, the updated start date of use is registered in the part management database 75 of the server 7.

[0035] When the part information T1 is registered in the part management database 75, the information disclosure unit 773 makes the information registered in the part management database 75 available for viewing. A manager in charge of part management at the user company operates the management PC 9 to access the server 7 via the network. This causes the information disclosure unit 773 to transmit viewing data (user interface) for viewing the part management database 75 to the management PC 9. The communication unit 91 of the management PC 9 provides the viewing data received via the network to the viewing management unit 92. The viewing management unit 92 displays the received viewing data on a display (not shown) provided in the management PC 9. As described above, when the information disclosure unit 773 transmits the viewing data using a WWW server, a web browser can be used as the viewing management unit 92.

[0036] FIG. 7 shows a parts management screen D1 displayed on the display of the management PC 9. The parts management screen D1 is a screen generated based on the viewing data received from the information disclosure unit 773. The parts management screen D1 displays information on all parts of liquid chromatographs used by the user company nationwide or worldwide. The manager can refer to information on the parts to be managed by selecting a country or region.

[0037] The administrator sets the number of warning days for each part while referring to the parts management screen D1. As mentioned above, the number of warning days can be freely set within the four-level categories of "Area 1," "Area 2," "Department 1," and "Department 2." Alternatively, the number of warning days can be set for each "Device."

[0038] FIG. 8 illustrates a warning days setting screen D2 displayed on the display of the management PC. The warning days setting screen D2 is a screen generated based on the browsing data received from the information disclosure unit 773. The warning days setting screen D2 includes an input field for setting the number of warning days for part replacement. The administrator can set the number of warning days for part replacement by category. FIG. 8 illustrates a state in which JP (Japan) is set as “Area 1,” Kyoto as “Area 2,” and development as “Department 1,” and air filter is set as the part name. The warning days are also illustrated as being set to 180 days. With the above information set, the administrator selects the OK button on the warning days setting screen D2, which transmits the warning days setting information to the server 7. When the server 7 receives the warning days setting information, the warning time setting unit 772 registers the warning days information in the part management database 75.

[0039] With this setting, the warning days for air filters are set to 180 days in the development division in Kyoto, Japan, which is the user company. This allows the administrator to set the warning days for air filters in all development divisions located in Kyoto at once. The number of days until replacement is displayed next to the input field for the warning days. In this example, for air filters whose default recommended replacement days are 365 days, the setting is such that a warning is issued in the Kyoto development division when the filter has been in use for 180 days. In other words, because the air filter replacement interval is short in the usage environment of liquid chromatograph 1 in the Kyoto development division, the setting is such that a warning is issued to prompt replacement every 180 days, which is about half the default recommended replacement days.

[0040] FIG. 9 is a diagram showing another example of the warning days setting screen D2. In FIG. 9, US (United States) is set as "Region 1," Ca (California) is set as "Region 2," and an air filter is set as the part name. The screen also shows a state in which 305 days is set as the warning days. With this setting, the number of warning days for air filters is set to 305 days in the state of California, where the user company is located. This allows the administrator to set the number of warning days for air filters in California, all at once. In this example, for an air filter whose default recommended replacement period is 365 days, a warning is set to be issued in California when the filter has been in use for 305 days. In other words, since the air filter replacement interval is normal in the usage environment of the liquid chromatograph 1 in California, a warning is set to be issued two months before the default recommended replacement period.

[0041] Parts for which the warning period has elapsed are highlighted on the part management screen D1 shown in FIG. 7 . For example, the row of the part for which the warning period has elapsed is displayed in red. Alternatively, the part name or the like of the part for which the warning period has elapsed may be displayed in flashing. Alternatively, if there is a part registered in the part management database 75 for which the warning period has elapsed, a program running on the server 7 may notify a message to the liquid chromatograph 1 in which the part is installed. In the liquid chromatograph 1, for example, a part replacement message is displayed on the display of the system controller 11. This allows the user to know the appropriate time to replace the part. Alternatively, if there is a part for which the warning period has elapsed, a program running on the server 7 may send an email to the user and a field engineer. The user and the field engineer can be notified that the warning period has elapsed by receiving the email.

[0042] As described above, the parts management system of this embodiment allows the number of warning days for parts attached to the liquid chromatograph 1 to be set on a category-by-category basis within the user's organization. This allows the user, even if the user is a large company and needs to manage the replacement dates of a large number of parts, to set the number of warning days on a category-by-category basis, improving convenience. As described above, the parts management system of this embodiment has been described using an example of managing maintenance parts that require replacement according to their usage period. Even within a user company, the frequency of use of the liquid chromatograph 1 varies by country, region, and department, making maintenance part management extremely complicated. However, by using the parts management system of this embodiment, a manager within the user company can use the management PC 9 to appropriately manage the replacement dates of a large number of parts located over a wide area.

[0043] Furthermore, since the number of warning days can be set on a regional basis, parts management can be performed taking into account regional conditions. For example, the number of usable days of an air filter varies depending on the environment of the location where the liquid chromatograph 1 is installed. Even in such cases, parts management can be performed according to the region by using the warning days setting screen D2 shown in Figure 8.

[0044] In the above embodiment, a case has been described in which new part information T1 is registered when a new liquid chromatograph 1 is installed at a location where analysis work is to be performed. The same operation is performed when a part is replaced when the liquid chromatograph 1 is already installed and being used at the location. When a part is replaced, the registration PC 5 registers the new replaced part. As a result, new part information T1 for the replaced part is registered in the part registration unit 121 of the functional unit 12. The information transfer unit 122 transfers the registered part information T1 to the server 7 via the network. The database registration unit 771 of the server 7 registers the part information T1 for the new replaced part in the part management database 75. The subsequent processing is the same as that described above.

[0045] When a part is replaced and part information T1 about the new part is transferred to the server 7, the information transfer unit 122 may also transfer usage information about the removed, used part to the server 7. The usage information about the removed part may be, for example, final information about the number of times or period of use of the part. The database registration unit 771 of the server 7 registers the usage information of the removed part in the part management database 75, and can provide the user with the final usage information of the part so that it can be viewed.

[0046] (7) Parts management method Fig. 10 is a flowchart showing the parts management method, which is carried out by the CPU 71 of Fig. 4 executing the parts management program P1 stored in the storage device 73.

[0047] First, the database registration unit 771 registers the part information T1 transferred from the liquid chromatograph 1 via the LAN 4, gateway 6, and WAN 8 in the part management database (step S1). Next, the warning time setting unit 772 sets a warning time to prompt replacement work for each part registered in the part management database 75 for each category of the organization of the user who uses the liquid chromatograph 1 (step S2). The warning time setting unit 772 executes step S2 based on the setting information related to the warning time received from the management PC 9.

[0048] (8) Correspondence between each element of the claims and each element of the embodiment Below, we will explain examples of the correspondence between each component of the claims and each element of the embodiments, but the present invention is not limited to the following examples. In the above embodiments, liquid chromatograph 1 is an example of an analytical device, and LAN 4 and WAN 8 are examples of networks. Also, in the above embodiments, area 1 and area 2 registered in parts management database 75 are examples of areas, and department 1 and department 2 registered in parts management database 75 are examples of departments.

[0049] As each component of a claim, various elements having the configuration or function described in the claim may be used.

[0050] (9) Other embodiments In the above embodiment, the parts management system has been described as being used as a system for managing parts attached to a liquid chromatograph 1. The parts management system of this embodiment can also be used for other analytical devices, such as gas chromatographs and mass spectrometers, in addition to liquid chromatographs. As with liquid chromatographs, the frequency of use of other analytical devices varies depending on the category within the user's organization. The parts management system of this embodiment centrally manages analytical device parts using the parts management database 75 and sets part replacement warning times for each category, so that it can appropriately manage part replacement times even when the frequency of use of analytical devices varies.

[0051] In the above embodiment, the registration PC 5 and the management PC 9 are both connected to the LAN 4 to which the liquid chromatograph 1 is connected. The registration PC 5 or the management PC 9 may be connected to a network different from the LAN 4. In addition, in the above embodiment, the server 7 is connected to the WAN 8. In other words, the parts management system uses the server 7 on the cloud. This configuration is one example, and the server 7 may be installed on a network within the user company.

[0052] In the above embodiment, the information disclosure unit 773, which is implemented by the component management program P1, transmits browsing data to the management PC 9 using a WWW server function. That is, the component management program P1 is a web application program, but this configuration is merely an example. The component management program P1 may also be a client-server program that transmits and receives data to and from the management PC 9.

[0053] The specific configuration of the present invention is not limited to the above-described embodiment, and various changes and modifications are possible without departing from the gist of the invention.

[0054] (10) Mode It will be appreciated by those skilled in the art that the exemplary embodiments described above are examples of the following aspects. (Item 1) A parts management system for an analytical device according to one aspect includes: an analytical device; a server connected to the analysis device via a network; Equipped with The analysis device a part registration unit that registers information about parts attached to the analysis device; an information transfer unit that transfers the part information registered in the part registration unit to the server via the network; Including, The server a database registration unit that creates a parts management database by registering the parts information transferred by the information transfer unit in a database; The analysis device may further include a warning timing setting unit that sets a warning timing for prompting replacement of each part registered in the parts management database for each category of an organization of users who use the analysis device.

[0055] Parts information registered in the analytical device is managed on a server. The server then sets the warning timing for prompting replacement of each part for each category of the user's organization. If the frequency of use of analytical devices varies by category within the user's organization, an appropriate warning timing can be set for each category. This reduces the risk of missing a part replacement timing. Appropriate part replacement reduces downtime of the analytical device. Furthermore, by replacing parts at the appropriate time rather than earlier than necessary, maintenance costs for the analytical device are reduced.

[0056] (Item 2) In the parts management system for the analytical device described in item 1, The warning time setting unit may set the warning time for each part for each region where the user's organization is located.

[0057] Even if the frequency of use of the analyzer by users varies from region to region, appropriate part replacement can be performed on a region-by-region basis.

[0058] (Item 3) In the parts management system for the analytical device described in item 1, The warning timing setting unit may set the warning timing for each part for each department in the user's organization.

[0059] Even if the frequency of use of the analyzer by users varies from department to department, appropriate part replacement can be performed on a departmental basis.

[0060] (Item 4) In the parts management system for the analytical device according to any one of items 1 to 3, The part registration unit may store the part information inside the analysis device when the analysis device is not connected to the server, and after the analysis device is connected to the server, the part information may be transferred to the server by the information transfer unit.

[0061] By having the user individually register component information for each analytical device, the component information can be centrally managed on the server.

[0062] (Item 5) In the parts management system for the analytical device according to any one of items 1 to 4, The part registration unit may record the time when information about each part was registered in the part registration unit as the time when use of each part began.

[0063] When a user registers part information in each analytical device, the usage period of each part begins to be counted. The server can grasp the usage period of each part by acquiring the part information from the analytical device.

[0064] (Item 6) In the parts management system for the analytical device described in item 5, When the analytical device is installed at a place where the analytical device is used for analysis work, the start time of use may be updated to the time when the analytical device is installed at the place of use.

[0065] In some cases, a considerable number of days may pass between the time when the part information is registered in the analytical device and the time when the device is installed at the location where it will be used for analysis. In such cases, the start date of use is updated so that the correct usage period can be managed on the server.

[0066] (Item 7) In the parts management system for the analytical device according to any one of items 1 to 6, The server may notify interested parties by email that the warning period has passed.

[0067] Users, field engineers, and other related parties can be notified by email that the warning period for a part has passed.

[0068] (Item 8) In the parts management system for the analytical device according to any one of items 1 to 7, The analytical device may include a liquid chromatograph.

[0069] The server manages information about parts installed in each functional unit of the liquid chromatograph. The server can set warning times to prompt replacement of parts installed in each functional unit of the liquid chromatograph for each category of the user's organization.

[0070] (Item 9) A component management program for an analytical device according to one aspect includes: A program executed on a server connected to the analytical device via a network, a database registration process for creating a parts management database by registering information on the parts attached to the analysis device, which information is transferred from the analysis device via the network, in a database; a warning time setting process for setting a warning time for prompting replacement of each part registered in the parts management database for each category of an organization of users who use the analysis device; may be executed by a computer.

Claims

1. an analytical device; a server connected to the analysis device via a network; Equipped with The analysis device a part registration unit that registers information about parts attached to the analyzer, including the number of days until replacement; an information transfer unit that transfers the part information registered in the part registration unit to the server via the network; Including, The server a database registration unit that creates a parts management database by registering the part information transferred by the information transfer unit in a database, the database including the category of the organization of the user who uses the analysis device, the part information, and the number of warning days for urging replacement of each part; a warning time setting unit that collectively sets the number of warning days registered in the parts management database for each set of the user's organization category and the parts information; Including, The number of days for replacement is the number of days counted from the start date of use of the part, and is the number of days for which part replacement is recommended, the warning number of days is the number of days counted from the start date of use of the part, the number of days for which a warning to replace the part is notified to the user, and is shorter than the replacement number of days; A parts management system for an analytical device, in which the parts information registered in the parts management database is managed in association with the category of the organization of the user who uses the analytical device, based on the setting by the warning timing setting unit.

2. the parts management database includes a plurality of categories for the user's organization; The parts management system for an analytical device according to claim 1 , wherein the warning time setting unit collectively sets the number of days for warning for a plurality of categories of the user's organization and a set of the part information.

3. The parts management system for an analyzer according to claim 1 , wherein the warning time setting unit collectively sets the number of warning days for each part for each region where the user's organization is located and / or for each department within the user's organization.

4. a viewing management unit that displays information registered in the parts management database on a display; The parts management system for an analytical device according to claim 1 , wherein the viewing management unit selects and displays information about parts corresponding to a category set by a user operation.

5. A program executed on a server connected to the analytical device via a network, a database registration process for creating a parts management database including the category of the organization of the user who uses the analytical device, parts information, and the number of warning days for urging replacement work for each part, by registering information on the parts attached to the analytical device transferred from the analytical device via the network in the database; a warning time setting process for collectively setting the number of warning days registered in the parts management database for each set of the user's organization category and the parts information; on the computer, The number of days for replacement is the number of days counted from the start date of use of the part, and is the number of days for which part replacement is recommended, the warning number of days is the number of days counted from the start date of use of the part, the number of days for which a warning to replace the part is notified to the user, and is shorter than the replacement number of days; A parts management program for an analytical device, in which the parts information registered in the parts management database is managed in association with the category of the organization of the user who uses the analytical device, based on the setting made by the warning timing setting process.

Images