Monitoring device and method

Abstract

In the present application, device determination information for determining a device for analysis, i.e., a subject device, and designation of an analysis item to be analyzed for the subject device are received, data of a kind required for analysis of the received analysis item is acquired, a current device state of the subject device is decided based on the acquired data, a diagnosis score obtained by scoring the current state of the subject device is calculated based on the decided device state of the subject device, and a diagnosis result of the subject device is decided based on the calculated diagnosis score, and the decided diagnosis result of the subject device is visualized.

Description

Technical Field

[0001] The present invention relates to monitoring devices and methods, such as monitoring devices suitable for use in monitoring the status of equipment such as industrial equipment. Background Technology

[0002] In recent years, the maintenance methods for industrial equipment have been shifting from time-based maintenance performed on a regular basis to condition-based maintenance performed in accordance with the condition of each piece of equipment. To perform condition-based maintenance, it is necessary to monitor the equipment at all times; consequently, the widespread adoption of remote monitoring services using IoT (Internet of Things) cloud platforms is progressing.

[0003] Previously, as a monitoring device for monitoring equipment and detecting signs of malfunction, the technology disclosed in Patent Document 1 is known. Patent Document 1 discloses a method for classifying and storing monitoring data of a monitored system during periods when no abnormalities are detected by the system by day of the week, time period, date, or week number in a storage unit. An allowable range is set based on the distribution of the stored monitoring data by day of the week, time period, date, or week number. The method compares the currently acquired monitoring data from the monitored system with the allowable range of the distribution of monitoring data based on the current date and time, and detects signs of malfunction in the monitored system if the acquired monitoring data exceeds the upper or lower limit of the allowable range.

[0004] Existing technical documents

[0005] Patent documents

[0006] Patent Document 1: Japanese Patent Application Publication No. 2014-153736 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] However, Patent Document 1 only discloses a technique for detecting fault symptoms using an appropriate threshold corresponding to the operating status of the computer system being monitored. That is, Patent Document 1 only determines fault symptoms based on whether the monitoring results of the monitored equipment exceed a threshold, without considering a method for determining the equipment's status within an acceptable range. However, for condition-based maintenance of industrial equipment, it is necessary not only to determine whether a fault has occurred but also to determine the current status of the equipment.

[0009] The present invention is derived with consideration of the above aspects, and aims to provide a monitoring device and method that can easily and understandably prompt the user about the current status of the device.

[0010] Technical solutions for solving the problem

[0011] To address this issue, the present invention provides a monitoring device for monitoring a monitored object, comprising: an input unit that receives device determination information and a specified analysis item to be analyzed for the object device, wherein the device determination information is used to determine the object device to be analyzed; a device status determination unit that acquires data on the types of data required for the analysis of the analysis item received by the input unit, and determines the current device status of the object device based on the acquired data; a diagnostic result determination unit that calculates a diagnostic score based on the device status of the object device determined by the device status determination unit, and determines a diagnostic result of the object device based on the calculated diagnostic score; and a visualization unit that visually displays the diagnostic result of the object device determined by the diagnostic result determination unit.

[0012] Furthermore, in this invention, the monitoring method executed by a monitoring device that monitors a monitored object includes: a first step of receiving device identification information and a specification of analysis items to be analyzed for the object device, wherein the device identification information is used to identify the device to be analyzed, i.e., the object device; a second step of acquiring data on the types of data required for the analysis of the received analysis items, and determining the current device status of the object device based on the acquired data; a third step of calculating a diagnostic score based on the determined device status of the object device to score the current status of the object device, and determining a diagnostic result of the object device based on the calculated diagnostic score; and a fourth step of visualizing the determined diagnostic result of the object device.

[0013] According to the analysis apparatus and method of the present invention, the current status of the target device can be visually indicated to the user using diagnostic scores.

[0014] The effects of the invention

[0015] According to the present invention, a monitoring device and method can be implemented that can easily and understandably prompt the user about the current state of the device. Attached Figure Description

[0016] Figure 1 This is a block diagram showing the overall structure of the monitoring system in this embodiment.

[0017] Figure 2 This is a block diagram representing the structure of the analysis server.

[0018] Figure 3 This is a diagram illustrating the structure of a database containing device identification information.

[0019] Figure 4It is a diagram that represents an example of the structure of the database of the analysis project.

[0020] Figure 5 This is a block diagram representing an example of the structure of a device information database.

[0021] Figure 6 This is a diagram showing an example of the structure of the alarm / fault information management table.

[0022] Figure 7 It is a diagram representing the structure of the operational data management table.

[0023] Figure 8 It is a diagram representing an example of the structure of a status / category management database.

[0024] Figure 9 It is a diagram representing the structure of a database of past historical information.

[0025] Figure 10 It is a diagram representing the structure of a diagnostic results table.

[0026] Figure 11 It is a block diagram used to illustrate the various programs running on the analysis server.

[0027] Figure 12 This is a diagram showing an example of the output from the sorting processing unit.

[0028] Figure 13 This is a diagram showing a variation of the output example of the sorting processing unit.

[0029] Figure 14 This is a diagram illustrating the screen structure of the analysis results display.

[0030] Figure 15 This is a diagram used to illustrate the device's search screen.

[0031] Figure 16 This is a diagram used to illustrate the device's search screen.

[0032] Figure 17 This is a flowchart illustrating the process flow for equipment status diagnosis and treatment.

[0033] Figure 18 It is a flowchart that represents the processing flow that determines the processing based on the device's status.

[0034] Figure 19 This is a flowchart representing the processing flow of historical comparisons.

[0035] Figure 20 These are diagrams used to illustrate equipment status diagnostics and processing. Detailed Implementation

[0036] The following describes one embodiment of the present invention in detail with reference to the accompanying drawings.

[0037] (1) Structure of the monitoring system in this embodiment

[0038] Figure 1 In this embodiment, 1 represents the overall monitoring system. The monitoring system 1 is a system that monitors the status of multiple monitoring target devices such as air compressors. It is composed of one or more monitoring target devices 3 set up at one or more service sites such as factories 2, and an analysis server 5 set up at the monitoring center 4, connected via a network 6 such as the Internet.

[0039] Each device 3 transmits information such as internal temperature and pressure, ambient temperature, and accumulated operating time as operational data to the analysis server 5 periodically or irregularly via network 6. Additionally, when a measured value exceeds a threshold, a malfunction occurs, or repairs or inspections are performed, the device 3 sends corresponding alarms or notifications to the analysis server 5 via network 6.

[0040] Analysis server 5 is a server device with the function of monitoring the device status of each device 3, such as... Figure 2 As shown, it includes a CPU (Central Processing Unit) 10, a memory 11, an auxiliary storage device 12, a network interface 13, an input device 14, and an output device 15.

[0041] CPU 10 is a processor that centrally controls the operations of the analysis server 5. The memory 11 consists of ROM (Read Only Memory) (not shown), which is composed of non-volatile storage elements, and RAM (Random Access Memory) (not shown), which is composed of volatile storage elements. The ROM stores immutable programs such as the BIOS (Basic Input Output System). The RAM, composed of DRAM (Dynamic RAM) and the like, is used as the working memory of CPU 10.

[0042] The auxiliary storage device 12 is composed of a high-capacity, non-volatile storage device such as a hard disk drive or an SSD (Solid State Drive). Various programs and data to be stored long-term are stored in the auxiliary storage device 12. The programs and data stored in the auxiliary storage device 12 are loaded into the memory 11 when the analysis server starts up and when necessary. The CPU 10 executes the programs loaded into the memory 11, thereby performing the various overall processes of the analysis server 5 as described later.

[0043] Network interface 13, for example, is composed of a NIC (Network Interface Card), which functions as a means of communication via network 6 ( Figure 1 The function of the interface when communicating with each device 3 of the monitored object.

[0044] Input device 14, for example, a mouse or keyboard, is used for users to input various operations on the analysis server 5. Output device 15, for example, a liquid crystal panel, an organic EL (Electro-Luminescence) display, and / or a printer, is used to output necessary information via display or printing. Alternatively, input device 14 and output device 15 can be integrated into a single unit, such as a touch panel.

[0045] (2) Device analysis function in this embodiment

[0046] Next, the device analysis function mounted on the analysis server 5 will be described. This device analysis function performs analysis processing on the target device 3 (hereinafter referred to as the target device) 3 and provides analysis execution instructions for the analysis items when the user specifies the device to be analyzed (hereinafter referred to as the target device) 3 and the analysis items, and visually displays the analysis results to the user. In this embodiment, the "analysis items" may include, for example, "device status diagnosis" which diagnoses the current device status of the target device 3, and "maintenance period" which diagnoses the period of the next maintenance.

[0047] In fact, when the analysis server 5 is given the analysis execution instruction, it determines the data types of all the data required for the specified object device 3 and the analysis of the specified analysis project (hereinafter appropriately referred to as necessary data types), and retrieves the data of each determined necessary data type from the database stored in the memory 11 (described later).

[0048] Then, the analysis server 5 performs analysis processing based on the acquired data, corresponding to the analysis items specified by the user, such as "device status diagnosis" and "maintenance period". The following explanation focuses on the case where the user-specified analysis item is "device status diagnosis".

[0049] In this analysis process, the analysis server 5 first detects various abnormal states that have occurred or are occurring in the target device 3 based on the necessary data types acquired as described above. These abnormal states include "long-term shutdown" (the device is in a state of prolonged shutdown due to maintenance, etc.), "high device temperature" (the device temperature is higher than the upper limit threshold), "low device temperature" (the device temperature is lower than the lower limit threshold), "high device pressure" (the device pressure is higher than the upper limit threshold), "low device pressure" (the device pressure is lower than the lower limit threshold), and "alarm / fault occurred" (an alarm / fault has occurred in the past). The analysis server 5 detects all abnormal states that match the current state of the target device 3 and defines them as the device state of the target device 3.

[0050] Subsequently, the analysis server 5 will classify the device states of the object device 3 detected as described above into the corresponding diagnostic categories (i.e., the diagnostic categories corresponding to the causes of the device state) of the four categories (hereinafter referred to as diagnostic categories) that correspond to the four causes of the abnormal state: “operating method”, “setting environment”, “incomplete inspection” and “component wear”.

[0051] In addition, for each diagnostic category, the analysis server 5 multiplies the number of device states of the object device 3 classified into that diagnostic category with the pre-set score for that diagnostic category to calculate the total score for each diagnostic category, and then calculates the sum of the total scores of each diagnostic category as the diagnostic score representing the current device state of the object device 3.

[0052] In this case, the score for each diagnostic category is set to be higher than the severity of the device state (abnormal state) classified into that diagnostic category, with higher scores for more severe states. Therefore, the diagnostic score for the object device 3, calculated as described above, is higher when the current state of the object device 3 is worse. That is, the diagnostic score can be considered an indicator of the severity of the current state of the object device 3.

[0053] Subsequently, the analysis server 5, based on the diagnostic score of the object device 3 calculated as described above, ranks the severity of the object device 3's condition among all devices in a certain classification group. In this embodiment, three classification groups are predefined as such: a classification group consisting of devices of the same model, a classification group consisting of devices existing in the same region (e.g., a prefecture), and a classification group consisting of devices with similar cumulative operating time. For each of these classification groups, the analysis server 5 ranks the severity of the object device 3's condition among all devices 3 in that classification group. However, other classification groups may be defined instead of these classification groups or additionally.

[0054] Furthermore, based on the data of each necessary data type acquired as described above, the analysis server 5 performs a diagnosis on the target device for several predetermined or user-specified items (hereinafter referred to as diagnostic items), such as "device internal temperature", "number of alarms / faults" and "filter clogging status".

[0055] Then, the analysis server 5 visualizes the ranking results of each such classification group and the diagnostic results corresponding to each diagnostic item as text or graphs, displays the ranking results if the output device 15 is a monitor, and prints the ranking results if the output device 15 is a printer.

[0056] As a solution for implementing the device analysis function as described above, in the memory 11 of the analysis server 5, such as Figure 2 As shown, the databases 20 (equipment determination information), 21 (analysis project), 22 (equipment information), 23 (status / category management), 24 (past historical information), and 25 (diagnostic results) are stored as databases, while the data input unit 30, 31 (equipment status determination), 32 (diagnostic results determination), 33 (data output), and 34 (data visualization) are stored as programs.

[0057] The device identification information database 20 is a database that stores various information about the devices 3 monitored by the analysis server 5, such as... Figure 3 As shown, it has a table structure including a device name field 20A, a manufacturing number field 20B, a model field 20C, a setting location address field 20D, and a setting date field 20E. Figure 3 In the device identification information database 20, one record (row) corresponds to one monitored device 3.

[0058] The device name of the corresponding device 3 is stored in the device name field 20A. Additionally, the manufacturing number of the device 3 is stored in the manufacturing number field 20B, and the model number of the device 3 is stored in the model number field 20C. Furthermore, the address of the device 3's setting location is stored in the setting location address field 20D, and the date the device 3 was set at that address is stored in the setting date field 20E.

[0059] thereby, Figure 3 For example, device 3, model A, with the device name "device 1" and the manufacturing number "XXX1234", was installed in "XX County, ○○ City" on "2015 / 8 / 15".

[0060] Analysis Project Database 21 is a table that defines the necessary data types for each analysis project, specifying the types of data required when performing analysis processing for a user-specified analysis project. Figure 4 As shown, the table has a structure that includes an analysis item column 21A and multiple necessary data categories column 21B. Figure 4 In the analysis project database 21, one record (row) corresponds to one analysis project.

[0061] Then, the name of the analysis project that the user can specify is stored in the analysis project column 21A, and one necessary data type is stored in each necessary data type column 21B for the analysis processing required for that analysis project. The number of necessary data types in the necessary data type column 21B for each record is equivalent to the number of necessary data types required to perform the analysis processing corresponding to that record.

[0062] thereby, Figure 4 In an example, where a user specifies a device 3 and instructs an analysis item called "Device Status Diagnosis" for that device 3, the following three data types are necessary for performing this analysis: "Alarm / Fault Information", "Operational Data", and "Repair History Information" for that device 3.

[0063] Device information database 22 is a database used to store and maintain various information obtained by analysis server 5 from each device 3 and various information about each device 3, such as... Figure 5 As shown, it consists of various tables such as Alarm / Fault Information Management Table 26, Operation Data Management Table 27, Repair History Management Table 28, and Maintenance History Management Table 29.

[0064] Among them, the alarm / fault information management table 26 is a table used to manage alarms or fault notifications (hereinafter referred to as fault notifications) previously issued from each device 3 of the monitored object, such as Figure 6As shown, it includes the date and time field 26A, the manufacturing number field 26B, the model field 26C, and the alarm / fault content field 26D. Figure 6 In the alarm / fault information management table 26, one record (row) corresponds to one alarm or fault notification received by the analysis server 5.

[0065] The date on which the analysis server 5 received the corresponding alarm or fault notification is stored in the Date / Time field 26A, and the manufacturing number of the device 3 that sent the alarm or fault notification is stored in the Manufacturing Number field 26B. Additionally, the model number of the device 3 is stored in the Model field 26C, and the specific content of the corresponding alarm or fault notification is stored in the Alarm / Fault Content field 26D.

[0066] thereby, Figure 6 For example, on August 15, 2018, a notification was sent from device 3 of model A with manufacturing number "XXX1234" to indicate "XX malfunction (XX has malfunctioned)".

[0067] Additionally, the operation data management table 27 is used to manage operation data indicating the operating status of each device 3, which is sent periodically or irregularly from each device 3. Figure 7 As shown, the group includes the manufacturing number column 27A, the acquisition date and time column 27B, the multiple items column 27C, and the value column 27D. Figure 7 In the operation data management table 27, one record (row) corresponds to the operation data sent from one device 3 at a time.

[0068] The manufacturing number of device 3, which sent the corresponding operation data, is stored in the manufacturing number column 27A, and the date and time of obtaining the operation data is stored in the acquisition date and time column 27B. In addition, the types of information such as "internal temperature of equipment", "internal pressure of equipment", "ambient temperature" or "running time" are stored in each item column 27C, and the measured or actual values ​​of the corresponding types of information are stored in the numerical value column 27D that is paired with item column 27C.

[0069] thereby, Figure 7 For example, in the case of equipment 3 with manufacturing number "XXX1234", the operating data sent at "2019 / 5 / 13 9:00" shows that the "Internal Temperature 1" of equipment 3 is "85 [°C]", the "Internal Pressure 1" is "0.63 [MPa]", the "Ambient Temperature" is "18 [°C]", and the cumulative "Running Time" is "1050 [hours]". Furthermore, each equipment 3 measures the internal temperature and internal pressure at multiple locations; "Internal Temperature 1" and "Internal Pressure 1" indicate that they represent the internal temperature and internal pressure data at one of these locations.

[0070] Repair History Management Table 28 is used to manage the repair history information (repair history information) of each piece of equipment 3, and Maintenance History Management Table 29 is used to manage the maintenance history information (maintenance history information) of each piece of equipment 3. The specific structure of Repair History Management Table 28 and Maintenance History Management Table 29 is omitted.

[0071] The status / category management database 23 is used to manage diagnostic categories, representative device statuses belonging to these diagnostic categories, and the correspondence between these categories and pre-defined scores for each diagnostic category. Figure 8 As shown, it has a table structure including a device status bar 23A, a diagnostic category bar 23B, and a score bar 23C. Figure 8 In the status / category management database 23, one record (row) corresponds to one diagnostic category.

[0072] The diagnostic category column 23B stores the name of the corresponding diagnostic category ("Operating Method", "Setup Environment", "Incomplete Check" or "Component Wear"), and the equipment status column 23A stores several representative equipment states (abnormal states) belonging to the corresponding diagnostic category. Additionally, the score column 23C stores a pre-set score for the corresponding diagnostic category. In this embodiment, as described above, a higher score is set for the diagnostic category corresponding to the cause of the more severe the equipment state (abnormal state).

[0073] thereby, Figure 8 In the example case, the device status (abnormal status) such as "AA long-term stop", "BB long-term stop" and "no data received" are shown to belong to the diagnostic category of "operation method", and a score of "1" is set as the score corresponding to the diagnostic category of "operation method".

[0074] The historical information database 24 is the device status determination unit 31B described later, used to manage the status / category management database 23. Figure 8 Unregistered matters previously implemented in [the relevant context] Figure 17 The database used later to determine the correspondence between the device status and diagnostic category obtained during the processing is the historical information database 24, as described below. Figure 9 As shown, it includes the device status bar 24A, the diagnostic category bar 24B, the analysis item bar 24C, and multiple necessary data types bar 24D.

[0075] The Device Status column 24A stores the device status and diagnostic category obtained during the previously executed device status determination process. The Diagnostic Category column 24B stores the device status and diagnostic category. Additionally, the Analysis Item column 24C stores the analysis item specified by the user at this time, and the Required Data Types column 24D stores the data types (required data types) of the data required to perform the analysis item.

[0076] thereby, Figure 9 In the example shown, the device status "A Long-Term Stop" corresponds to the diagnostic category "Operating Method" in the device status decision process executed in the past. Additionally, Figure 9 The diagram shows that this correspondence was performed during the "Equipment Status Diagnosis" analysis project. In order to detect the equipment status "A Long-Term Stoppage", data types "Alarm / Fault Information" and "Operation Data" are required respectively.

[0077] The diagnostic results database 25 is a table used to store and manage the diagnostic scores calculated for each device 3. The description here indicates that the analysis item is "Device Status Diagnosis," therefore, each time a "Device Status Diagnosis" is performed for one device 3, a database like this is generated. Figure 10 The diagnostic results table 25A shown is stored in the diagnostic results database 25, corresponding to the manufacturing number of the device 3.

[0078] The diagnostic results are shown in Table 25A. Figure 10 As shown, it includes the device status bar 25AA, the diagnostic category bar 25AB, the number of conforming items bar 25AC, the score bar 25AD, and the diagnostic score bar 25AE.

[0079] Then, in the Diagnostic Category column 25AB, save the names of each diagnostic category ("Operating Method", "Setup Environment", "Incomplete Check", and "Component Wear"). Additionally, in the Equipment Status column 25AA, save all equipment statuses belonging to the corresponding diagnostic categories for each equipment status of the target equipment 3 detected through analysis.

[0080] Furthermore, the number of device states belonging to the corresponding diagnostic category detected for the target device 3 is stored in the "Number of Items" column 25AC, and the score set for the corresponding diagnostic category is stored in the "Score" column 25AD. The diagnostic score for the corresponding diagnostic category is then stored in the "Diagnostic Score" column 25AE, calculated by multiplying the number of device states belonging to the corresponding diagnostic category by the score for that diagnostic category. Additionally, the diagnostic score for the target device 3, representing the severity of its condition, is stored in the "Diagnostic Score" column 25AE at the bottom of the diagnostic results table 25A.

[0081] thereby, Figure 10 In the example shown, in the equipment status diagnosis of object equipment 3 with manufacturing number "XXX1234", no equipment status belonging to the "operation method" diagnostic category was detected. One equipment status of "low ambient temperature" was detected as belonging to the "setting environment" diagnostic category. A total of four equipment statuses, including "alarm / fault occurred", were detected as belonging to the "incomplete inspection" diagnostic category. A total of three equipment statuses, including "component abnormality", were detected as belonging to the "component wear" diagnostic category.

[0082] in addition, Figure 10 As shown in the above results, the diagnostic scores for the diagnostic category "Operation Method" are "0 points", "Setup Environment" is "2 points", "Incomplete Inspection" is "12 points", "Component Wear" is also "12 points", and the diagnostic score for object device 3 is "26 points".

[0083] On the other hand, data input unit 30 ( Figure 2 It is a database 20 that accepts user input for identifying device 3, including device identification information (manufacturer number) and analysis items. Based on the accepted manufacturer number and analysis items, it retrieves information from the device identification information database 20. Figure 3 ) and analysis project database 21 ( Figure 4 ) Obtain necessary information and determine the equipment status (31) Figure 2 The program provides a notification function. The data input section 30, for example... Figure 11 As shown, the device is configured to have a monitoring object device determination information input unit 30A and an analysis item input unit 30B as functional units.

[0084] The monitored object device determination information input unit 30A inputs the device determination information into the device determination information database 20 ( Figure 3 In each record (row) of the equipment identification information database 20, the record with the user-specified manufacturing number stored in the manufacturing number column 20B is retrieved, and the information about the record detected by the retrieval is read from the equipment identification information database 20. Figure 3 The device name, model, setting location address, and setting date of the object device 3 are stored in the device name field 20A, model field 20C, setting location address field 20D, and setting date field 20E as described above, and are notified to the device status determination unit 31 and the diagnostic result determination unit 32.

[0085] For example, Figure 3In the example, if the manufacturing number of the target device specified by the user is "XXX1234", the device determination information database 20 is used to retrieve information such as "Device 1" as the device name, "Model A" as the model number, "XX County ○○ City" as the setting location, and "2015 / 8 / 15" as the setting date, and the device status determination unit 31 and the diagnosis result determination unit 32 are notified of this information respectively.

[0086] In addition, the analysis project input section 30B analyzes the project database 21 ( Figure 4 In the records of ), retrieve the data in the analysis item column 21A ( Figure 4 The database 21 stores records of user-specified analysis items, and reads the necessary data categories 21B from the records detected by the retrieval. Figure 4 The device status determination unit 31 is notified of all data types stored in the device status determination unit 31, along with the data types and user-specified analysis items.

[0087] For example, Figure 4 In the example where the user-specified analysis item is "equipment status diagnosis", the system retrieves various data types such as "alarm / fault information", "operation data" and "repair history information" from the analysis item database 21 as necessary data, and notifies the equipment status determination unit 31 of this information.

[0088] The device status determination unit 31 is a program that determines the status of the target device 3 based on the device name, model, installation location address, and installation date of the target device 3 notified by the monitoring target device determination information input unit 30A of the data input unit 30, and the analysis project specified by the user and the types of data required to perform the analysis project notified by the analysis project input unit 30B. The device status determination unit 31 is configured to have an analysis project determination unit 31A and a device status determination unit 31B as functional units.

[0089] The analysis project decision unit 31A determines the analysis project to be performed at this time from the analysis project input unit 30B notified by the user from the data input unit 30. Then, the analysis project decision unit 31A notifies the equipment status decision unit 31B of the determined analysis project, the data types (necessary data types) of each data required for the analysis of the analysis project notified by the analysis project input unit 30B, and the manufacturing number of the object equipment 3 notified by the monitored object equipment determination information input unit 30A.

[0090] Thus, in the example above, the analysis project decision unit 31A determines the analysis project as "equipment status diagnosis" and notifies the equipment status decision unit 31B of the decision result. It also informs the equipment status decision unit 31B that the data types (necessary data types) required for the analysis of this analysis project are "alarm / fault information", "operation data" and "repair history information".

[0091] The equipment status determination unit 31B uses the equipment number notified from the analysis project determination unit 31A as the search keyword to retrieve data related to the target equipment 3 from the corresponding management table in the equipment information database 22, obtaining the data detected through this search. Furthermore, based on the obtained data, the equipment status determination unit 31B determines the equipment status of the target equipment 3 and the diagnostic category to which each equipment status belongs, and notifies the diagnostic result determination unit 32 of the determined equipment status and diagnostic category of the target equipment 3. Then, the equipment status determination unit 31B retrieves data from the operation data management table 27 (… Figure 7 The system reads the cumulative running time of the target device 3 and notifies the diagnostic result decision unit 32, and also notifies the diagnostic result decision unit 32 of the data related to the target device 3 obtained from the device information database 22 as described above.

[0092] Therefore, in the above example, the equipment status determination unit 31B stores the alarm / fault information management table 26 (which contains "alarm / fault information") Figure 6 Retrieve data related to object device 3 (device 3 with manufacturing number "XXX1234") in the operation data management table 27 (which stores the "operation data"). Figure 7 Retrieve data related to object device 3 from the repair history management table 28, which stores "repair history information". Figure 5 The device status determination unit 31B retrieves data related to the target device 3 from the data retrieved through these searches. Furthermore, based on the data detected through these searches, the device status determination unit 31B determines the device status of the target device 3 and the diagnostic category to which each device status belongs, and notifies the diagnostic result determination unit 32 of the determination results. More specific processing details of the device status determination unit 31 will be described later.

[0093] The diagnostic result determination unit 32 is a program that scores the current equipment status of the target equipment 3 and sorts the target equipment 3 within each category group (here, each category group is "model", "region", and "operating time"). The diagnostic result determination unit 32 is configured to have a diagnostic score determination unit 32A, a classification processing unit 32B, a sorting processing unit 32C, and a diagnostic processing unit 32D as functional units.

[0094] The diagnostic score determination unit 32A, based on the device status of the target device 3 notified from the device status determination unit 31B and the diagnostic category of each of these device statuses, refers to the status / category management database 23. Figure 8 ) and historical information database 24 ( Figure 9 ), to score the current status of object device 3.

[0095] In practice, for each diagnostic category, the diagnostic score determination unit 32A counts the number of device states belonging to that diagnostic category, and multiplies the count result by a pre-set score for that diagnostic category to calculate the diagnostic score for that category. Furthermore, the diagnostic score determination unit 32A sums the diagnostic scores for each diagnostic category and scores the current device state of the object device 3. Then, the diagnostic score determination unit 32A notifies the sorting processing unit 32C of the calculated diagnostic scores for each diagnostic category and their sum, i.e., the diagnostic score of the object device 3, and... Figure 10 The diagnostic results described above are recorded in Table 25A and stored in the diagnostic results database 25.

[0096] The classification processing unit 32B determines which classification group the object device 3 belongs to in terms of "model", "region" of the installation location and "cumulative operating time" based on the model and installation location address of the object device 3 notified by the monitoring object device determination information input unit 30A of the data input unit 30, and the cumulative operating time of the object device 3 notified by the device status determination unit 31B of the device status determination unit 31.

[0097] In practice, for the "model," the classification processing unit 32B determines the model classification group to which the object device 3 belongs based on the model of the object device 3 notified by the monitored object device determination information input unit 30A. Furthermore, for the "region" of the installation location, the classification processing unit 32B determines the region classification group to which the object device 3 belongs based on the installation location address of the object device 3 notified by the monitored object device determination information input unit 30A. Moreover, for the accumulated "running time," the classification processing unit 32B determines which of several classification groups of running times, such as "0-100 hours," "100-500 hours," "500-1000 hours," etc., the running time notified by the device status determination unit 31B belongs.

[0098] Then, the classification processing unit 32B notifies the sorting processing unit 32C of the "model", the "region" of the setting location, and the cumulative "running time" of the object equipment being judged.

[0099] The sorting processing unit 32C sorts the target device 3 based on the diagnostic results of the target device 3 notified by the diagnostic score determination unit 32A and the diagnostic results (diagnostic scores) of other monitored target devices 3 registered in the diagnostic result database 25, ranking them according to their severity within each category group based on "model," "region," and "operating time." This sorting can be performed by sorting each device 3 belonging to that category group according to its diagnostic score, starting with the device with the highest diagnostic score. Then, the sorting processing unit 3 displays this sorting result as... Figure 12 The format shown is output to the data output unit 33. In addition, the sorting processing unit 32C reads the past (e.g., 6 months ago or 1 year ago) diagnostic scores stored in the diagnostic results database 25, and outputs the read past diagnostic scores along with the sorting results to the data output unit 33.

[0100] in addition, Figure 12 The diagram shows that the diagnostic score of device "1" one year ago was "15 points", and the current diagnostic score is "26 points". The model, the region where it is installed, and the operating time are classified into the classification groups "Model 1", "Region A" and "100-500 [h]" respectively. The severity of the condition of device 3 of the same model is ranked "first", the severity of the condition of device 3 installed in the same region is ranked "second", and the severity of the condition of device 3 with the same operating time of "100-500 [h]" is ranked "first".

[0101] However, for example, it can also be like Figure 13 As shown, the sorting processing unit 32C calculates the degree of degradation of the object device 3 over the years by comparing the difference between the diagnostic score of the object device 3 calculated this time and the diagnostic score of the object device 3 from one year ago (or several months or several years ago) with the score from one year ago (or several months or several years ago). Based on the calculated degree of degradation, the unit sorts the object devices 3 within each category group. In this case, the device 3 is sorted according to the degree of degradation within each category group, starting with the device 3 with the higher degree of degradation, and the order of the object devices 3 within that category group is calculated accordingly.

[0102] The diagnostic processing unit 32D receives notification from the device status determination unit 31B of the device status determination unit 31, and the device information database 22 (…). Figure 5The diagnostic processing unit 32D acquires data from the target device and performs diagnostic processing on several predetermined diagnostic items, such as "device temperature," "number of alarms / faults," and "blockage status." The specific details of the diagnostic processing performed by this diagnostic processing unit 32D will be described later. The diagnostic processing unit 32D notifies the data output unit 33 of the processing results.

[0103] The data output unit 33 outputs the sorting results of the object device 3 notified by the sorting processing unit 32C and the diagnostic results for each diagnostic item notified by the diagnostic processing unit 32D in text or other formats to the data visualization unit 34. Furthermore, the data visualization unit 34 visually displays (or prints) the sorting results of the sorting processing unit 32C and the diagnostic results of the diagnostic processing unit 32D output by the data output unit 33 in the form of reports or graphs in a prescribed format.

[0104] In addition, the data visualization unit 34 can also be based on the user's input device 14 ( Figure 2 The search criteria set are used to determine the information database 20 (for devices). Figure 3 ) and equipment information database 22 ( Figure 5 The system performs a search, detects devices that meet the search criteria, and visualizes their information.

[0105] (3) The structure of various images.

[0106] Figure 14 This describes an example of the structure of an analysis result display screen 40 displayed on and / or printed from the output device 15 of the analysis server 5 after the analysis processing based on the aforementioned device analysis function (here, device status diagnostic processing) is completed. This analysis result display screen 40 is a screen used to display the processing results of the analysis processing, including an object device name field 41, an alarm / fault history field 42, a maintenance history field 43, a diagnostic result display field 44, and a comment field 45.

[0107] Then, the device name of the object device 3 is displayed in the object device name field 41, and the alarm / fault history field 42 shows the information retrieved from the device information database 22 during the analysis process. Figure 5 Alarm / Fault Information Management Table 26 Figure 6 The system retrieves historical information on alarms and malfunctions of the target device 3. Additionally, the maintenance history column 43 displays data retrieved from maintenance history management table 29 during the analysis process. Figure 5 The information obtained is the execution history of maintenance operations for the object device 3 (maintenance history information).

[0108] The diagnostic results display bar 44 displays the diagnostic results of the target device 3 obtained through the device status diagnostic process. In fact, the diagnostic results display bar 44 is provided with a diagnostic score / deterioration display area 50, one or more sequential display areas 51, one or more diagnostic object display areas 52, and judgment result display areas 53 corresponding to these diagnostic object display areas 52.

[0109] Then, in the diagnostic score / years-old degradation display area 50, the diagnostic score of the object device 3 calculated as described above, and the degree of years-old degradation compared to its state 1 year ago and 6 months ago are displayed. As described above, the degree of years-old degradation is the value obtained by subtracting the diagnostic scores calculated 1 year ago and 6 months ago from the current diagnostic score of the object device 3. Figure 14 In the example, the annual degradation score is "-5" when compared with 6 months ago, so it can be seen that the condition of the object device 3 has improved compared with 6 months ago. In contrast, the annual degradation score is "5" when compared with 1 year ago, so it can be seen that the condition of the object device 3 has deteriorated over the years compared with 1 year ago.

[0110] Additionally, in the sequence display area 51, the order of the object device 3 within each category group, as calculated as described above, is displayed. Figure 14 The text shows that, within the region of "County A," the severity of the condition of device 3 is "second highest." However, it could also be as follows... Figure 14 The image does not show the order of object device 3 within the category group, but rather shows the percentage of the severity of the state of object device 3 within the corresponding category group. Figure 14 The text shows that the severity of the condition of object device 3 in all devices 3 within the "same model" classification group is "top 10%".

[0111] In the diagnostic object display area 52, the information is displayed as... Figure 11 The diagnostic processing unit 32D of the diagnostic result determination unit 32 described above includes the diagnostic object and information about the diagnostic object in the corresponding diagnostic items of the judgment object among several diagnostic items. Figure 14 The diagram shows that the diagnostic object of "Diagnostic Item A" is "Temperature". Related to this "Temperature", the highest value of the internal temperature of the object device 3 is "89" and the average value is "67".

[0112] in addition, Figure 14 The diagram shows that the diagnostic targets for "Diagnostic Item B" are the number of alarms issued and the number of malfunctions ("Number of Occurrences"). Related to this "Number of Occurrences," the target device 3 has issued "10" alarms and experienced "6" malfunctions. Furthermore, Figure 14The diagnostic object of "Diagnostic Item C" is "Blockage Condition", and related to this "Blockage Condition", the suction pressure of the object device 3 is "0.6".

[0113] However, other diagnostic items can be used as the diagnostic item. Alternatively, the user can specify the diagnostic item.

[0114] Furthermore, in the judgment result display area 53, the diagnostic object displayed in the corresponding diagnostic object display area 52 (the diagnostic object display area 52 provided to the left of the judgment result display area 53) and the diagnostic result determination unit 32 are displayed. Figure 11 ) diagnostic processing unit 32D ( Figure 11 The judgment results are obtained by judging (evaluating) according to the four levels "A" to "D". Figure 14 The text shows that the judgment result for "Diagnosis Item A" is "D", the judgment result for "Diagnosis Item B" is "C", and the judgment result for "Diagnosis Item C" is "B".

[0115] Furthermore, the judgment performed by the diagnostic processing unit 32D is made by comparing a value representing the device status with ranges set for each of the "A," "B," "C," and "D" levels. At this time, the range for each level is set separately for each device status being judged. For example, Figure 14 In the example, it is shown that, assuming that for "diagnostic item A", the range of "A" level corresponding to the highest temperature is set to "0~50℃", the range of "B" level is set to "51~60℃", the range of "C" level is set to "70~80℃", and the range of "D" level is set to "81℃~", the equipment status of object device 3 is judged as "D".

[0116] Furthermore, in the annotation column 45, annotations are displayed based on the diagnostic results of the above-mentioned device status diagnosis for the target device 3.

[0117] on the other hand, Figure 15 This describes an example of the structure of a device search screen 60 that can be displayed on the output device 15 of the analysis server 5 through a specified operation performed using the input device 14. This device search screen 60 is used to enable the analysis server 5 to search for devices 3 that meet the required search criteria.

[0118] The device's search screen 60 includes a search criteria setting area 61 and a search results display area 62. Furthermore, the search criteria setting area 61 includes one or more search criteria setting buttons 70, search criteria addition buttons 71, and search buttons 72.

[0119] Then, on the device search screen 60, a drop-down menu 73 (73A) containing multiple search criteria that the user can specify, such as "model", "running time" and "setting date", can be displayed by clicking or tapping the search criteria setting button 70.

[0120] Furthermore, in the device search screen 60, by pressing the string representing a search condition that has a lower-level search condition than the search conditions displayed in the drop-down menu 73 (73A) (for example, specific regions such as each "prefecture" corresponding to the search condition "Setup Location"), a drop-down menu 73 (73B) containing multiple search conditions of the lower level can be displayed. Similarly, in the device search screen 60, for search conditions with lower-level search conditions, drop-down menus 73 containing the lower-level search conditions can be displayed sequentially.

[0121] In this way, as described above, the user displays the bottom-level drop-down menu 73 containing the desired search criteria, and selects the desired search criteria from the drop-down menu 73 by pressing it. This allows the user to assign the search criteria as the search key when searching device 3. Furthermore, the user can then press the search button 72 to activate the analysis server 5 in the device determination information database 20. Figure 3 The search is performed using the search criteria (the search criteria used in the last press operation) as the search key.

[0122] Then, in the device search screen 60, the search results display area 62 displays in table form the installation location, manufacturing number, and installation date of each device 3 that meets the search criteria and was detected by the search processing performed by the analysis server 5. At this time, in the search results display area 62, the operation data management table 27 is also displayed for each device 3 detected by the search. Figure 7 The cumulative running time obtained.

[0123] Additionally, multiple search criteria can be set on the device search screen 60. For example, such as... Figure 16As shown, when two search criteria are set, pressing the search criterion setting button 70, which is labeled "Search Criterion 1," displays the top-level drop-down menu 73 (73A), and then setting the first search criterion as described above. Next, pressing the search criterion setting button 70, which is labeled "Search Criterion 2," displays the top-level drop-down menu 73 (73A), and then setting the second search criterion as described above, followed by pressing the search button 72. As a result, the device 3 that satisfies both of these search criteria displays the search result in the search result display area 62.

[0124] Additionally, in the device search screen 60, a new search condition setting button 70 can be displayed each time the search condition addition button 71 is pressed. This allows the user to set a desired number of search conditions in the device's information database 20. Figure 3 ) retrieve devices that meet all of these search criteria 3.

[0125] (4) Process flow of various processing functions related to equipment analysis

[0126] Next, the specific processing flow of various processes performed in the analysis server 5 related to the analysis function of this device will be explained. Furthermore, the following explanations will be based on the processing entity of each process being a "program (...section)" or a part of the function of that program (functional section), but in reality, the CPU 10 of the analysis server 5 (... Figure 2 This process is performed based on the program.

[0127] (4-1) Equipment status diagnosis and processing

[0128] Figure 17 This is a flowchart illustrating the process of a series of processes executed in the analysis server 5 when the user provides the manufacturing number of the object device 3 and the execution instructions for the device status diagnostic process of the analysis item.

[0129] When the execution instruction is received in the analysis server 5, firstly, the monitored object device determination information input unit 30A of the data input unit 30 ( Figure 11 Based on the manufacturing number of object device 3 specified by the user at this time, the information is determined from the device database 20. Figure 3 The device name, model, setting location address, and setting date of the target device 3 are read from the device status determination unit 31. Figure 11 Notification. Additionally, at the same time, the analysis item input section 30B of the data input section 30... Figure 11 )Analyze the project database 21 ( Figure 4The system reads the data types required for the analysis of the analysis project specified by the user and notifies the device status determination unit 31 (S1).

[0130] The equipment status determination unit 31B of the equipment status determination unit 31 executes equipment status determination processing (S2) based on the analysis item (here, "equipment status diagnosis") notified from the analysis item input unit 30B, to determine the equipment status of the target equipment 3. The specific content of the equipment status determination processing will be described later. Through this equipment status determination processing, each equipment status of the target equipment 3 and the diagnosis category to which each equipment status belongs are determined, and the diagnosis result is then processed by the diagnosis result determination unit 32. Figure 11 Notify this information (S2).

[0131] Next, the diagnostic score determination unit 32A of the diagnostic result determination unit 32 ( Figure 11 Based on the device states of the target device 3 notified from the device state determination unit 31B and the diagnostic categories to which these device states belong, a diagnostic score for each diagnostic category is calculated, and the calculated diagnostic scores for each diagnostic category are summed to calculate the diagnostic score of the target device representing the severity of the current state of the target device 3 (S3).

[0132] Next, the classification processing unit 32B of the diagnosis result determination unit 32 ( Figure 11 Based on the information such as the device name, model, installation location address, and installation date of the object device 3 notified by the monitoring object device determination information input unit 30A from the data input unit 30, and the operating time of the object device 3 notified by the device status determination unit 31B from the device status determination unit 31, the object device 3 is classified into the corresponding classification group for "model", "region" and "operating time" respectively (S4).

[0133] Furthermore, the sorting processing unit 32C of the diagnosis result determination unit 32 ( Figure 11 The severity of the condition is ranked according to its position within each category group of "model", "region", and "operating time" (S5). Subsequently, or concurrently, the diagnostic processing unit 32D of the diagnostic result determination unit 32 performs judgment processing on the target device 3 for each pre-set diagnostic item (S6).

[0134] Subsequently, the data visualization department 34, for example, regarding... Figure 14 The analysis results described above are displayed together on screen 40, showing the processing results of both the sorting processing unit 32C and the diagnostic processing unit 32D of the diagnostic result determination unit 32 (S7). Based on the above, the device status diagnostic process is completed.

[0135] (4-2) Equipment Status Determination Processing

[0136] Figure 18 It means about Figure 17 In step S2 of the equipment status diagnosis process described above, the equipment status determination unit 31 ( Figure 11 The flowchart shows how the specific processing content is determined by the device status.

[0137] In fact, regarding Figure 17 When the device status diagnosis process described above proceeds to step S2, the Figure 18 The equipment status determination process begins as shown. First, the analysis item determination unit 31A of the equipment status determination unit 31 ( Figure 11 Based on the data input unit 30 ( Figure 11 ) Analysis item input section 30B ( Figure 11 The user-specified analysis item (here, equipment status diagnosis) is notified, and the analysis item to be performed at this time is determined to be equipment status diagnosis. Furthermore, the analysis item determination unit 31A notifies the equipment status determination unit 31B of the determined analysis item, i.e., equipment status diagnosis, and the data types (here, "alarm / fault information," "operation data," and "repair history information") required for performing the equipment status diagnosis notified by the analysis item input unit 30B, as well as the monitored equipment determination information input unit 30A (from the data input unit 30). Figure 11 The manufacturing number (S10) of the equipment to which the notification is received.

[0138] Based on the information provided by the analysis project decision unit 31A, the equipment status determination unit 31B retrieves data from the equipment information database 22. Figure 5 Alarm / Fault Information Management Table 26 Figure 6 ), Operational Data Management Table 27 ( Figure 7 ) or Repair History Management Form 28 ( Figure 5 (S11) Acquire the necessary data for each of the following data types required for equipment status diagnosis: "Alarm / Fault Occurrence", "Operation Data" and "Repair History".

[0139] Next, the equipment status determination unit 31B determines whether, in step S11, data of at least one of the necessary data types, namely "alarm / fault occurred", "operation data" and "repair history", has been acquired (S12).

[0140] A negative result in this judgment indicates that there is no device state matching the target device 3 (i.e., no abnormal state has occurred in the target device 3). In this case, the device state determination unit 31B ends the device state determination process and returns to the device state diagnosis process. Furthermore, because there is no device state matching the target device 3 in this situation, the diagnostic score for the target device is calculated as "0" in the next step S3 of the device state diagnosis process.

[0141] In contrast, when the equipment status determination unit 31B obtains a positive result in the determination in step S12, it uses the data obtained from the alarm / fault information management table 26 and the repair history management table 28 in the data obtained in step S11 as the past or current equipment status of the target equipment 3 to determine whether an equipment status indicating that an alarm has been issued or a fault has occurred, or an equipment status that has been repaired, is detected (S13).

[0142] In addition, the equipment status determination unit 31B determines whether an abnormal status is detected as the past or current equipment status of the target equipment 3 based on the operation data obtained from the operation data management table 27 in the data obtained in step S11 (S14).

[0143] For example, if the internal temperature of the equipment determined based on the operating data obtained from the operating data management table 27 in step S11 is above the upper limit threshold preset for the internal temperature of the equipment, or below the lower limit threshold preset for the internal temperature of the equipment, the operating data indicates an abnormal state. Therefore, the equipment state determination unit 31B determines that an abnormal state has been detected in such cases.

[0144] Furthermore, based on the operation data obtained from the operation data management table 27 in step S11, if the temperature difference between the equipment's internal temperature and the ambient temperature is above a pre-set upper limit threshold for the temperature difference, or below a pre-set lower limit threshold for the temperature difference, the operation data indicates an abnormal state. Therefore, the equipment state determination unit 31B determines that an abnormal state has been detected in such cases.

[0145] Furthermore, based on the operating data obtained from the operating data management table 27 in step S11, if the internal pressure of the equipment is above the upper limit threshold preset for the internal pressure of the equipment, or below the lower limit threshold preset for the internal pressure of the equipment, the operating data indicates an abnormal state. Therefore, the equipment state determination unit 31B determines that an abnormal state has been detected in such cases.

[0146] Next, the equipment status determination unit 31B selects a device status (S15) from the equipment statuses detected in step S13 or S14 (equipment statuses related to alarms / faults or repairs, or abnormal statuses) that have not undergone processing after step S16, and determines whether the selected device status (hereinafter referred to as the selected device status) has been registered in the status / category management database 23. Figure 8 (S16)

[0147] Then, when the device status determination unit 31B obtains a positive result in the determination, it stores the selected device status and the combination of the diagnostic category corresponding to the selected device status in the status / category management database 23 (S17), and then proceeds to step S19.

[0148] In contrast, when the device status determination unit 31B obtains a negative result through the judgment in step S16, it retrieves information from the historical information database 24. Figure 9 Extract the device state that is closest to the selected device state from the device states registered in the database, and store the combination of the extracted device state and the diagnostic category corresponding to the device state in the historical information database 24 (S18).

[0149] Next, the device state determination unit 31B determines whether the processing of steps S16 to S18 (S19) has been completed for all device states detected in step S13 or step S14. Then, if the device state determination unit 31B receives a negative result in this determination, it returns to step S15, and then sequentially switches the device state selected in step S15 to other corresponding device states that have not undergone the processing after step S16, and repeats the processing of steps S15 to S19.

[0150] Then, when the device status determination unit 31B obtains a positive result in step S19 after completing the processing of steps S16 to S18 for all device statuses detected in step S13 or step S14, it determines the device status of the target device 3 and the diagnostic category to which the device status belongs (S20) as all the device statuses and diagnostic categories that were previously stored in step S18.

[0151] Furthermore, in the correspondence between the device states of the target device 3 determined by the device state determination unit 31B in step S20 and the diagnostic categories of those device states, there exists a state / category management database 23. Figure 8 If there is no registered correspondence between the device status and the diagnostic category in the database, the correspondence between the device status and the diagnostic category will be registered in the historical information database 24. Figure 9 (S21). Then, the device status determination unit 31B ends the device status determination process thereafter.

[0152] (4-3) Historical Comparison Processing

[0153] Figure 19 Indicates about Figure 18 The specific processing content of the device state determination unit 31B in step S17 of the device state determination process described above. When the device state determination unit 31B proceeds to step S17 of the device state determination process, it begins... Figure 19The historical comparison process shown first determines the processing based on the device status. Figure 18 In step S15, has the selected device status (select device status) already been registered in the historical information database 24? Figure 9 ) in (S30).

[0154] When the device status determination unit 31B obtains a positive result in the determination, it associates the selected device status with the diagnostic category corresponding to the selected device status in the past history information database 24 (S38). Then, the device status determination unit 31B ends the past history comparison process and returns to the device status determination process. Therefore, in this case, the combination of the selected device status and diagnostic category that is associated at this time is stored in the subsequent step S18. The same applies below.

[0155] In contrast, when the device status determination unit 31B receives a negative result in step S30, it retrieves the status / category management database 23 through the following steps S31 to S37. Figure 8 ) or historical information database 24 ( Figure 9 The device status that is closest in content to the selected device status among the registered device statuses.

[0156] Specifically, the equipment status determination unit 31B first determines whether the selected equipment status is related to an alarm / fault or repair (S31). Then, if the equipment status determination unit 31B obtains an affirmative result in this determination, it confirms the specific content of the selected equipment status (alarm / fault / repair content) (S32) and extracts the equipment status whose status is closest to the selected equipment status from the equipment status registered in the status / category management database 23 or the past history information database 24 (S37). Furthermore, the equipment status determination unit 31B associates the diagnostic category corresponding to the equipment status extracted in step S37 in the past history information database 24 as the diagnostic category for extracting the equipment status (S38), and then ends the past history comparison process and returns to the equipment status determination process.

[0157] For example, such as Figure 20 As shown in the example in the first row, if the selected device status is "A Long-term Stop" and the device status closest to "A Long-term Stop" in the historical information database 24 is "B Long-term Stop", the device status determination unit 31B associates the selected device status "A Long-term Stop" with the diagnostic category "Operation Method" in the historical information database 24 that corresponds to the device status "B Long-term Stop".

[0158] In contrast, when the device status determination unit 31B receives a negative result in step S31, it determines whether the selected device status is related to temperature (S33). Then, when the device status determination unit 31B receives a positive result in this determination, it confirms the specific content of the selected device status (the specific abnormal temperature condition) (S34) and extracts the device status that is closest in content to the selected device status from the device status registered in the status / category management database 23 or the past history information database 24 (S37). Furthermore, the device status determination unit 31B associates the diagnostic category corresponding to the device status extracted in step S37 in the past history information database 24 as the diagnostic category for extracting the device status (S38), and then ends the past history comparison process and returns to the device status determination process.

[0159] For example, such as Figure 20 As shown in the example in the second row, if the selected device status is "high ejection temperature" and the closest device status to "high ejection temperature" in the historical information database 24 is "low ejection temperature", the device status determination unit 31B associates the selected device status "high ejection temperature" with the diagnostic category "setting environment" in the historical information database 24 that corresponds to the device status "low ejection temperature".

[0160] In addition, such as Figure 20 As shown in the example in the third row, when the extracted device status is "Device internal temperature 2 fault" and the device status closest to "Device internal temperature 2 fault" in the historical information database 24 is "Device internal temperature 1 alarm", the device status determination unit 31B associates the selected device status "Device internal temperature 2 fault" with the diagnostic category "incomplete inspection" corresponding to "Device internal temperature 1 alarm" in the historical information database 24.

[0161] On the other hand, when the equipment status determination unit 31B receives a negative result in the judgment of step S33, it determines whether the selected equipment status is related to the pressure equipment status (S35). Then, when the equipment status determination unit 31B receives a positive result in the judgment, it confirms the specific content of the selected equipment status (the specific abnormal state of pressure) (S36) and extracts the equipment status that is closest in content to the selected equipment status from the equipment status registered in the status / category management database 23 or the past history information database 24 (S37). Furthermore, the equipment status determination unit 31B associates the diagnostic category corresponding to the equipment status extracted in step S37 in the past history information database 24 as the diagnostic category for extracting the equipment status (S38), and then ends the past history comparison process and returns to the equipment status determination process.

[0162] For example, such as Figure 20 As shown in the example in the fourth line, if the extracted equipment status is "equipment internal pressure 1 decreased" and the equipment status registered in the past historical information database 24 that is closest to "equipment internal pressure 1 decreased" is "equipment internal pressure decreased", the equipment status determination unit 31B associates the selected equipment status "equipment internal pressure 1 decreased" with the diagnostic category "component wear" that corresponds to "equipment internal pressure decreased" in the past historical information database 24.

[0163] In contrast, when the device status determination unit 31B receives a negative result in step S35, it extracts the device status that is closest in content to the selected device status from the device status registered in the status / category management database 23 or the past history information database 24 (S37). Then, the device status determination unit 31B associates the diagnostic category corresponding to the device status extracted in step S37 in the status / category management database 23 or the past history information database 24 as the diagnostic category of the selected device status (S38), and then ends the past history comparison process and returns to the device status determination process.

[0164] (5) Effects of this implementation method

[0165] As described above, in the monitoring system 1 of this embodiment, the current status of the object device 3 is scored as a diagnostic score and visualized, so the current status of the object device 3 can be easily and understandably displayed to the user based on the diagnostic score.

[0166] In addition, this monitoring system 1 also displays the order of the object device 3 in the classification group based on the diagnostic score, so that the user can objectively know the status of the object device 3 obtained by comparing it with other devices 3.

[0167] (6) Other implementation methods

[0168] Furthermore, the above embodiments describe the application of the present invention to a monitoring system 1 that monitors industrial equipment, but the present invention is not limited thereto and can be widely applied to various monitoring systems that monitor equipment other than industrial equipment.

[0169] Furthermore, the above embodiments describe the case where the device analysis function of this embodiment is mounted on one analysis server 5, but the present invention is not limited thereto. The device analysis function may also be distributed among multiple computer devices interconnected via a network, and these computer devices may cooperate to implement the device analysis function of this embodiment.

[0170] Industrial availability

[0171] This invention can be applied to monitoring devices for monitoring the status of equipment such as industrial equipment.

[0172] Explanation of reference numerals in the attached figures

[0173] 1…Monitoring system, 3…Equipment, 5…Analysis server, 10…CPU, 20…Equipment determination information database, 21…Analysis project database, 22…Equipment information database, 23…Status / category management database, 24…Past historical information database, 25…Diagnostic result database, 26…Alarm / fault information management table, 27…Operational data management table, 28…Repair history management table, 29…Maintenance history management table, 30…Data input unit, 30A…Monitored object equipment determination information input unit, 30B…Analysis project input unit, 31…Equipment status determination unit, 31A…Analysis project determination unit, 31B…Equipment status determination unit, 32…Diagnostic result determination unit, 32A…Diagnostic score determination unit, 32B…Classification processing unit, 32C…Sorting processing unit, 33…Data output unit, 34…Data visualization unit, 40…Equipment retrieval screen, 60…Analysis result display screen.

Claims

1. A monitoring device for monitoring equipment of a monitored object, characterized in that, include: The input unit receives device determination information and the specification of analysis items, wherein the device determination information is used to determine the object device as the object of analysis, and the analysis items are the items to be analyzed for the object device; The device status determination unit acquires data on the types of data required for the analysis of the analysis item received by the input unit, and determines the current device status of the target device based on the acquired data. The diagnostic result determination unit calculates a diagnostic score based on the device state of the target device determined by the device state determination unit, and determines the diagnostic result of the target device based on the calculated diagnostic score. A visualization unit that visually displays the diagnostic results of the target device determined by the diagnostic result determination unit; and A database that stores the correspondence between the device status and the reasons for that device status. For each of the stated causes, a score corresponding to the severity of the device state associated with that cause is assigned. The device state determination unit determines all the device states that the target device conforms to as the device state of the target device. The diagnostic result determination unit, for each cause, calculates a total score by multiplying the number of device states corresponding to that cause by the score set for that cause. It then sums the total scores for each cause to calculate the diagnostic score for the target device. Based on the calculated diagnostic scores, it sorts the current states of the target devices in each of the various classification groups consisting of devices from multiple monitored objects, according to each classification group. The visualization unit displays the order of the object device in each of the classification groups after being sorted by the diagnostic results determination unit, or the percentage of the object device's order within that classification group.

2. The monitoring device as described in claim 1, characterized in that: When the device status determination unit determines a device status that is not registered in the database as the device status of the target device, it calculates the reason for the device status based on the correspondence between the device status and the reason registered in the database.

3. The monitoring device as described in claim 1, characterized in that: The diagnostic result determination unit calculates the degree of annual degradation of the target device as the annual degradation degree based on a diagnostic score obtained by scoring the current state of the target device and a diagnostic score obtained by scoring the past state of the target device. The visualization unit makes the degree of degradation of the target device over the years, calculated by the diagnostic result determination unit, visible.

4. A monitoring method performed by a monitoring device that monitors the equipment being monitored, characterized in that, include: The first step is to receive device identification information and the specification of analysis items, wherein the device identification information is used to identify the object device as the object of analysis, and the analysis items are the items to be analyzed for the object device; The second step is to obtain the data types required for the analysis of the received analysis project, and to determine the current device status of the target device based on the obtained data. The third step involves calculating a diagnostic score based on the determined device state of the target device, evaluating its current state, and determining the diagnostic result for the target device based on the calculated diagnostic score. The fourth step is to visualize the diagnostic results of the determined target device. The monitoring device includes a database that stores the correspondence between the device status and the reasons for the device status. For each of the stated causes, a score corresponding to the severity of the device state associated with that cause is assigned. In the second step, all the device states that the target device conforms to are determined as the device state of the target device. In the third step, for each cause, the number of device states corresponding to that cause is multiplied by the score assigned to that cause to calculate a total score. The total scores for each cause are summed to calculate the diagnostic score for the object device. Based on the calculated diagnostic scores, the current states of the object devices in each of the various classification groups consisting of multiple monitored objects are sorted according to each classification group. In the fourth step, the sorted object device is displayed in the order of each of the classification groups, or the percentage of the object device's order within that classification group.

5. The monitoring method as described in claim 4, characterized in that: In the second step, when a device state that is not registered in the database is determined as the device state of the target device, the reason for the device state is calculated based on the correspondence between the device states and the reasons registered in the database.

6. The monitoring method as described in claim 4, characterized in that: In the third step, the degree of degradation over the years of the object device is calculated as the degradation degree based on the diagnostic score obtained by scoring the current state of the object device and the diagnostic score obtained by scoring the past state of the object device. In the fourth step, the calculated annual degradation of the object device is visualized.

Images