Information processing device and automatic analysis system
The expanded FMEA database in the automatic analysis system quickly identifies failure modes by associating check targets with failure effects and antecedent events, enhancing maintenance efficiency and enabling predictive diagnostics.
Patent Information
- Application Number
- JP2021154440
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-09-22
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-09-22
AI Technical Summary
Existing automatic analysis systems face challenges in quickly identifying failure modes due to the reliance on sensors that detect structural issues rather than functional failures, leading to inefficiencies in maintenance processes, especially for inexperienced users.
An expanded FMEA database is utilized to associate check targets with failure effects and antecedent events, enabling the calculation of score values to quickly identify failure modes through a processor-based analysis.
This approach allows for rapid identification of failure modes, facilitating efficient maintenance by prioritizing and presenting failure modes based on relevance and temporal context, reducing diagnostic time and enabling predictive maintenance.
Smart Images

Figure 0007590300000001 
Figure 0007590300000002 
Figure 0007590300000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to an information processing device and an automatic analysis system. [Background technology]
[0002] For example, when a malfunction occurs in an automatic analysis system, the check targets (contents of system alerts, sensor log data, etc.) are inspected to identify the nature of the malfunction. However, if the inspector has little experience, he or she will not know which inspection targets to check, and if abnormalities are found in multiple check targets at the same time, it will take a long time to identify the malfunction.
[0003] To solve such problems, for example, Patent Document 1 discloses a fault diagnosis device for a vehicle electronic system in which the points that must be monitored for each fault symptom are determined at the time of design, and an operator can select appropriate inspection items by selecting a specific symptom from a list of various fault symptoms displayed.
[0004] Moreover, Patent Document 2 discloses a maintenance work support system that uses a fault knowledge database in which fault knowledge data is recorded to set priorities for presenting investigation procedures to maintenance workers, and presents the investigation procedures to a diagnostic interface unit based on the priorities.
[0005] Furthermore, Patent Document 3 discloses an equipment status monitoring method in which, based on an event signal output from the equipment, modes are divided according to the operating state, a normal model is created for each mode, the sufficiency of learning data for each mode is checked, and an abnormality is identified using a threshold value set according to the results.
[0006] Moreover, Patent Document 4 discloses an equipment maintenance method and device which includes a database for storing inspection records and failure records, compares records of ongoing failures with records of past failures, and sequentially displays countermeasure items corresponding to failure records with high similarity, starting with those corresponding to failure records with high similarity. [Prior art documents] [Patent documents]
[0007] [Patent Document 1] Japanese Patent Application Publication No. 10-78376 [Patent Document 2] JP 2019-204302 A [Patent Document 3] JP 2014-59910 A [Patent Document 4] JP 2019-191705 A Summary of the Invention [Problem to be solved by the invention]
[0008] In Patent Documents 1 to 4, various sensors are used for failure detection, but most of the sensors detect changes in the state of the device (failure effect or functional failure effect) caused by the occurrence of a functional failure (a functional disorder caused by a failure mode of a part) rather than the occurrence of a failure mode itself (disconnection, short circuit, breakage, wear, deterioration of characteristics, and other structural destruction of parts or components). For this reason, when the sensors output an abnormal value, it is not possible to quickly identify the failure mode, and it is not possible to improve the efficiency of maintenance work. Therefore, the situation in which it takes a long time for inexperienced users to identify a failure has not been improved. In view of such circumstances, the present disclosure proposes a technique that enables rapid identification of a failure mode. [Means for solving the problem]
[0009] In order to solve the above problems, the present disclosure proposes an information processing device that includes an extended FMEA database including, for each failure effect, information on a check target, information on the degree of association between the check target and the failure effect, and information on antecedent events of the check target, and a processor that acquires information on check targets confirmed as events and identifies a failure mode corresponding to the failure effect based on the acquired check targets, wherein the processor executes a first process of extracting information on the failure effect related to the check target from the extended FMEA database, a second process of calculating a score value of the failure effect extracted in the first process by referring to the information on the degree of association between the check target and the failure effect, and a third process of presenting a failure mode corresponding to the failure effect extracted in the first process based on the score value.
[0010] Further features related to the present disclosure will become apparent from the description of the present specification and the accompanying drawings. Also, aspects of the present disclosure may be realized and realized by the elements and combinations of various elements and aspects of the following detailed description and the appended claims. The descriptions herein are exemplary and illustrative only and are not intended to limit the scope or application of the present disclosure in any way. Effect of the Invention
[0011] According to the technology of the present disclosure, it is possible to quickly narrow down the failure mode. [Brief description of the drawings]
[0012] [Figure 1] 1 is a diagram showing an example of a schematic configuration of a maintenance support device (an information processing device having a system maintenance support function) 10 according to an embodiment of the present invention. [Diagram 2] 1 is a diagram showing an example of the internal software configuration of a maintenance support related processing unit 101 and an extended FMEA database 141. FIG. [Diagram 3] FIG. 1 is a diagram showing the concept of each state in FMEA (the relationship between each state: especially the causal relationship). [Figure 4]FIG. 13 is a diagram showing the relationship between the effect of a failure and check information (including information on a check target, relevance, and antecedent event). [Diagram 5] FIG. 13 is a diagram illustrating an example of a definition of a degree of association. [Figure 6] 4 is a flowchart for explaining details of a failure mode estimation process in the maintenance support device 10. [Figure 7] FIG. 7 is a diagram showing an example of a GUI configuration of a failure effect selection screen 700. [Figure 8] FIG. 13 is a diagram showing an example of a GUI that displays candidates for functional failures and failure modes that match an input failure effect. [Figure 9] FIG. 13 is a diagram showing an example of a screen configuration of a check information input GUI for inputting check information. [Figure 10] FIG. 13 is a diagram showing an example of a score value of a failure effect associated with selected check information. [Figure 11] FIG. 1 is a diagram for explaining prioritization of failure effects taking into account preceding events. [Figure 12] FIG. 12 is a diagram showing an example of a failure mode estimation result (in order of priority) display 1200. [Figure 13] FIG. 13 is a diagram illustrating an example of a schematic configuration of an automatic analysis system 1300 incorporating a failure mode estimation process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] This embodiment describes a technology that supports the identification of failure modes when a functional failure occurs, based on FMEA (Failure Mode and Effects Analysis). In this embodiment, focusing on the fact that the check target effective for identifying the cause differs depending on the type of functional failure, a "check target", "relevance between the check target and the functional failure impact", and "preceding event of the check target" are defined for each impact of the functional failure, and using them, the degree of agreement between the failure event and the check result is calculated to narrow down the failure mode.
[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. In the accompanying drawings, functionally identical elements may be indicated by the same numbers. Note that the accompanying drawings show specific embodiments and implementation examples according to the principles of the present disclosure, but these are for understanding the present disclosure and are by no means used to interpret the present disclosure in a limiting manner.
[0015] In the present embodiment, the description is given in sufficient detail for a person skilled in the art to implement the present disclosure, but it should be understood that other implementations and forms are possible, and that changes in configuration and structure and substitutions of various elements are possible without departing from the scope and spirit of the technical ideas of the present disclosure. Therefore, the following description should not be interpreted as being limited thereto.
[0016] Furthermore, as described below, embodiments of the present disclosure may be implemented in software running on a general-purpose computer, in dedicated hardware, or in a combination of software and hardware.
[0017] In the following explanation, each piece of information in the present disclosure may be described in a "table" format, but this information does not necessarily have to be expressed in a table data structure, and may be expressed in a data structure such as a list, DB, queue, or other structure. Therefore, to indicate that it does not depend on the data structure, "table," "list," "DB," "queue," etc. may be simply referred to as "information."
[0018] In addition, when describing the content of each piece of information, the expressions "identification information," "identifier," "name," "ID," and "other" can be used, and these are interchangeable.
[0019] In the following, each process in the embodiments of the present disclosure will be described with the "program (each processing unit)" as the subject (operating entity). However, since the program performs the processes defined by being executed by the processor while using the memory and the communication port (communication control device), it may also be described with the processor as the subject. Further, the processes disclosed with the program as the subject may also be the processes performed by a computer such as a management server or an information processing device. Part or all of the program may be realized by dedicated hardware and may also be modularized. The various programs may be installed on each computer by a program distribution server or a storage medium.
[0020] (1) First Embodiment <Definition of Terms in FMEA> In this embodiment, failure analysis is performed using each failure state in FMEA. First, the definition of each failure state in FMEA will be described. As described above, in FMEA, the failure states include failure mode, functional failure, and failure effect. Regarding these FMEA states, there is a causal relationship in the order of failure mode → functional failure → failure effect.
[0021] (i) Explanation of Terms The failure mode refers to physical damage such as parts or components that have occurred in the device or system to be maintained. It is a state where the damaged parts or the like must be replaced.
[0022] The functional failure refers to the operation (phenomena or symptoms) of the device or system caused by the damage of the above parts. It is a phenomenon or symptom (for example, the occurrence of liquid leakage) caused by the device or system to be maintained not performing its original operation.
[0023] The failure effect refers to an event observed as a result of a functional failure. For example, a measurement failure is an example. The check target refers to an event that the user can observe and confirm, or an event that can be confirmed from a sensor log, for example, a pressure rise. It is not about directly checking what is broken (part or part), but about inspecting what is broken to see what is happening. In other words, it is easier for a user to recognize whether an unusual event is occurring in the system than which part or part is broken. For this reason, the event that is occurring is the check target, and the related fault location (failure mode) is identified from there. In other words, it is based on the idea that, for example, whether a gear of a motor, which is a part, is missing or not can only be determined by disassembling the device or system, but the impact caused by a missing gear can be easily observed (recognized).
[0024] (ii) Specific examples For example, consider the case where the failure mode of an automatic analyzer is a failure of the plunger. In this case, the functional failure is a state in which the appropriate volume of liquid cannot be pumped out. If the appropriate volume of liquid cannot be pumped out, poor measurement results will occur, or poor liquid delivery by the cleaning pump will occur (failure effect). In reality, the means for detecting the occurrence of this failure effect are pressure sensors and position sensors, and if there is an abnormality in the numerical values from these sensors, this will become the subject of the check. In other words, there is a direct link between the subject of the check and the failure effect. Then, it is possible to extract candidates for failure effects from the subject of the check, and each functional failure and each failure mode can be identified from each candidate for failure effect.
[0025] <Example of maintenance support device configuration> Fig. 1 is a diagram showing a schematic configuration example of a maintenance support device (information processing device having a system maintenance support function) 10 according to this embodiment. The maintenance support device 10 can be realized by implementing a system maintenance support function in a normal computer. Fig. 1 shows a state in which various programs are stored in a processor. The maintenance support device 10 includes a processor 100, a communication device 110, an input device 120, an output device 130, and a storage device 140.
[0026] The communication device 110 is configured to be able to execute communication with devices and systems connected to the maintenance support device 10, and communication with computers (such as a user terminal) connected via a network. The input device 120 is configured, for example, by devices such as a keyboard and a mouse, and is configured to enable a user to input data and instructions to the maintenance support device 10. The output device 130 is configured, for example, by a display device, and is configured to enable processed information and data to be displayed on a display screen.
[0027] The storage device 140 is configured with a storage device such as a memory or a HDD, and stores various parameters and processed data. The storage device 140 also holds an extended FMEA database 141, which will be described later. The extended FMEA database 141 stores information required to realize a system maintenance support function. Details will be described later.
[0028] The processor 100 executes predetermined processing in accordance with various programs. The processor 100 reads various programs from the storage device 140 and loads them into an internal memory (not shown), thereby generating at least a maintenance support related processing unit 101, an input / output control unit 102, and a communication control unit 103 in the internal memory.
[0029] The maintenance support related processing unit 101 has a function of prioritizing and presenting failure modes in a device or system to be checked to a user, and a function of automatically recovering from functional failures. The former is a function of presenting information to a user by GUI processing, and the latter is a function of recovering from functional failures by batch processing (non-GUI processing: see the second embodiment). The detailed functional configuration and operation of the maintenance support related processing unit 101 will be described later.
[0030] The input / output control unit 102 controls the output device 130, for example, to transfer information or data input from the input device 120 to the maintenance support related processing unit 101, or to output (display) information or data processed by the maintenance support related processing unit 101.
[0031] The maintenance support device 10 may be connected directly or via a network to a device or system to be checked (maintained) to execute the system maintenance function, or the maintenance support related processing unit 101 and the extended FMEA database 141 may be implemented in the device or system to be checked.
[0032] <Details of the maintenance support related processing unit 101 and the extended FMEA database 141> FIG. 2 is a diagram showing an example of the internal software configuration of the maintenance support related processing unit 101 and the extended FMEA database 141. As shown in FIG.
[0033] The maintenance support related processing unit 101 includes a functional failure effect input processing unit 1011 , a failure mode candidate display processing unit 1012 , a check information input processing unit 1013 , a failure effect relevance score calculation unit 1014 , and a check target antecedent event evaluation unit 1015 .
[0034] The extended FMEA database 141 holds, in addition to the information held in a normal FMEA database (information on the functions of devices and parts, information on functional failures, information on failure effects, information on failure modes, and information on failure risks), information on the objects to be checked, information on the degree of association between the objects to be checked and the functional failure effects, and information on the antecedent events of the objects to be checked.
[0035] A functional failure effect input processing unit 1011 receives information on failure effects designated by a user or information on failure effects from a system or the like, and passes it to a failure mode candidate display processing unit 1012. Details will be described later.
[0036] The check information input processing unit 1013 generates a GUI (Graphical User Interface) for the user to input information of the check target, displays it on the display screen, and also accepts the designation of the check target from the user and passes it to the failure mode candidate display processing unit 1012 and the failure effect relevance score calculation unit 1014. Details will be described later.
[0037] The failure effect relevance score calculation unit 1014 acquires information on the relevance between the check target and the functional failure effect from the extended FMEA database 141, and calculates a failure effect relevance score for each failure effect. Details will be described later.
[0038] The check target antecedent event evaluation unit 1015 evaluates whether the input antecedent event matches or does not match the related antecedent event in each failure effect, and in the case of a mismatch, notifies the failure mode candidate display processing unit 1012 to lower the display priority. Details will be described later.
[0039] The failure mode candidate display processing unit 1012 searches the extended FMEA database 141 based on the information of functional failures acquired from the functional failure effect input processing unit 1011, and acquires information of related failure modes. The failure mode candidate display processing unit 1012 also executes a process of displaying each functional failure and its corresponding failure mode in order of priority based on each failure effect related to the check target input by the user, its relevance score (acquired from the failure effect relevance score calculation unit 1014), and information on the preceding event. Details will be described later.
[0040] In the extended FMEA database 141, the information to be checked varies depending on the type of the system to be maintained. The information on the degree of relevance between the information to be checked and the functional failure impact is information obtained by quantifying the depth of the relevance of the result (failure impact) caused corresponding to the event (information to be checked) that has occurred. This is, for example, a numerical value (score) assigned based on the degree of occurrence of the event of check information A in the failure impact 1. The failure mode candidate display processing unit 1012 acquires this information from the extended FMEA database 141 and assigns information on the degree of relevance to the information to be checked in each failure mode (assigns the score obtained from the database). Further, when there is an event (preceding check information that occurs earlier) preceding each information to be checked, a preceding event is defined for the information to be checked.
[0041] <Concept of FMEA> FIG. 3 is a diagram showing the concept of each state in FMEA (the relationship of each state: especially the causal relationship). FMEA is a technique called Failure Mode and Effects Analysis, which defines a method for evaluating the risks of products and processes mainly in the product design stage and the process design stage and eliminating or reducing those risks as much as possible. Although the details of the method of implementing FMEA are omitted, this embodiment utilizes the fact that by paying attention to the relationship of each state of FMEA, failure modes can be comprehensively extracted.
[0042] From Figure 3, we can see that when failure mode 1 occurs, functional failures 1 and 2 occur in functions 1 and 2 of part 1, and functional failure 1 causes failure effects 1 and 2, and functional failure 2 causes failure effect 3, respectively. It can also be seen that when failure mode 2 occurs, failure function 3 occurs in function 2 of part 1, which causes failure effects 4 and 5. It can also be seen that when failure mode 3 occurs, functional failure 4 occurs in function 3 of part 2, which causes failure effects 6 and 7. In other words, there is an association (link) where failure mode 1 causes functional failure 2 and functional failure 3 to occur, and functional failure 301 (functional failures 1 and 2) is a functional failure linked to failure mode 1, functional failure 302 (functional failure 3) is a functional failure linked to failure mode 2, and functional failure 303 (functional failure 3) is a functional failure linked to failure mode 3. Links from failure modes to functional failures are only made within the same part. In this way, a causal relationship exists between failure modes and functional failures, and also between functional failures and failure effects. Therefore, it is possible to identify the failure mode by tracing back from the failure effects.
[0043] The structure shown in Figure 3 can be expressed in a way that is easy for humans to see using a general table creation tool, and does not need to be created with software processing in mind. There are no identical part names and failure modes, but there are identical functions, functional failures, and failure effects (functional failure 1 and functional failure 3 are the same, failure effect 2 and failure effect 5 are the same, etc.). For example, if the same transmission failure occurs whether gear A or gear B fails, the failure effect will be the same, but the failure modes will be different.
[0044] <Relationship between failure impact and check information> 4 is a diagram showing the relationship between failure effects and check information (including information on check targets, relevance, and antecedent events). In FIG. 4, check information 401 to 404 associated with failure effects 1 to 4 are shown.
[0045] In this embodiment, based on FMEA (systematic analysis of functions, functional failures, failure effects, failure modes, failure risks, etc. of devices and parts), a check target 405, a relevance 406 between the check target and the failure effect, and a preceding event 407 are newly provided for each failure effect. That is, in this embodiment, as described above, failure effects 1 to 4 and check information 401 to 4 are associated with each other and stored in the extended FMEA database 141. For example, when a user recognizes (confirms) failure effect 1, check targets 405 (check targets A to C) associated with the failure effect 1, corresponding relevance 406 (5 points, 3 points, 1 point), and preceding event (preceding event 408: the preceding event of check target "B" is "A") are extracted.
[0046] Here is some additional information about what is checked. Generally, functional failures (unstable pump delivery, inability to remove dissolved gas, etc.) are difficult to detect themselves, so the behavior of the equipment when a failure occurs (failure impact) is detected. Check targets such as system alerts and log data obtained from various sensors (those related to the occurrence of the failure impact, and in which outputs or states that differ from normal times are observed when a failure occurs) are extracted for each failure impact.
[0047] <Definition of relevance (example)> Fig. 5 is a diagram showing the definition of the relevance. The relevance between the check target and the failure impact is defined as shown in Fig. 5, and under the condition that a failure impact occurs due to a certain functional failure, the relevance is set for each check target of the failure impact and is stored in a database. When constructing the extended FMEA database 141, the relevance is set for all check targets for all failure impacts. Regarding the preceding event, when there is a chronological relationship between the occurrence of a change in the check target, the check target in which the change occurs first is set as the preceding event.
[0048] <Failure mode estimation process> Fig. 6 is a flowchart for explaining the details of the failure mode estimation process in the maintenance support device 10. Fig. 7 to Fig. 12 are diagrams showing examples of GUI screen displays in each step of the failure mode estimation process, or diagrams for supplementary explanation of the processing contents. The subject of operation of each step is each of the processing units 1011 to 1015 included in the maintenance support related processing unit 101, but since these are realized by expanding program codes in the internal memory of the processor 100, the processor 100 may be the subject of operation.
[0049] (i) Step 601 The functional failure effect input processing unit 1011 displays a failure effect selection screen 700 shown in FIG. 7 on the display screen (output device 130) of the maintenance support device 10. On the failure effect selection screen 700, the user selects a failure effect (an abnormal state occurring in the device) from a pull-down list. The failure effects include an effect on service 701 and an effect on system 702. Examples of the effect on service include "device unusable," "unable to measure," and "poor measurement results." Examples of the effect on the system include "reduced separation ability," "poor liquid transfer," "poor cleaning," and "liquid leakage."
[0050] When a failure impact (impact on service 701 and / or impact on system 702) is selected by the user, the functional failure impact input processing unit 1011 processes the input failure impact and passes information on the failure impact to the failure mode candidate display processing unit 1012.
[0051] (ii) Step 602 The failure mode candidate display processing unit 1012 searches for functional failure candidates (see FIG. 3) that match (are linked to) the failure effect acquired in step 601 from the extended FMEA database 141. Fig. 8 is a diagram showing an example of a GUI that displays functional failure and failure mode candidates that match the input failure effect. In other words, at least one pair of functional failure and failure mode linked to the input (selected) condition (failure effect) is searched for.
[0052] 8 displays functional failures 801 related to the failure effects and failure modes 802 that are the causes of the functional failures. At this stage, an initial value (e.g., zero value) is displayed for a score 803 based on the degree of association between the check target and the failure effects.
[0053] (iii) Step 603 The failure mode candidate display processing unit 1012 obtains information on the check targets related to the failure effects obtained in step 601 from the extended FMEA database 141, passes the information to the check information input processing unit 1013, and instructs it to generate and display a check information input GUI.
[0054] In response to an instruction from the failure mode candidate display processing unit 1012, the check information input processing unit 1013 generates a check information input GUI for selecting the received check target, and displays it on the display screen.
[0055] 9 is a diagram showing an example of the screen configuration of a check information input GUI for inputting check information. The check information input GUI 900 includes check information 901 related to the failure effect selected (specified) by the user, radio buttons 902 for the user to select from the displayed check targets, and a pull-down menu 903 for selecting antecedent events. The check information input GUI 900 is used to narrow down functional failure candidates from the user's selection results.
[0056] Check information input GUI 900 displays check targets (e.g., check targets A to D) 901 related to the input failure effect. The user selects a check target with radio button 902 for which an operation, state, or sensor value different from that under normal conditions can be confirmed. In addition, if any of the check targets has a preceding event (for example, if the preceding event can be visually confirmed by the user or can be identified from the measurement result log data), the user selects the preceding event of the corresponding check target from pull-down 903. The contents of the preceding event pull-down list are all check targets related to the currently selected failure effect.
[0057] The example in Fig. 9 shows an input example in which unusual events are observed in check targets A, B, and D (a situation in which no abnormality is observed in check target C), and A is observed as a preceding event of inspection target B. It is not necessary to input all check targets from the beginning; it is sufficient to start by inputting check targets that can be easily confirmed and narrow down the candidates for failure modes.
[0058] (iv) Step 604 The failure effect relevance score calculation unit 1014 acquires information (e.g., failure effects 1 to 3) of failure effects related to the selected check targets (e.g., check targets A, B, and D) from the extended FMEA database 141. Since multiple failure effects related to the check targets selected by the user (e.g., failure effects including two or more selected check targets) are extracted, in Fig. 10, failure effects not selected by the user in step 601 are also subject to score value calculation. This makes it possible to present to the user failure modes related to failure effects that the user does not intend (cannot recognize).
[0059] Next, the failure effect relevance score calculation unit 1014 calculates a score indicating the degree of agreement with the check result for each failure effect (failure effects 1 to 3) based on the relevance between the check target and each failure effect.
[0060] Fig. 10 is a diagram showing an example of the score value of the failure effect related to the selected check information. GUI 1001 is a display showing only the check target portion of Fig. 9, and displays a state in which A, B, and D of check target 1002 are marked (selected state). Fig. 10 also shows relevance values 1007 to 1010 corresponding to check target 1002 selected from check information 1003, 1004, 1005, and 1006 in failure effects 1 to 4. The relevance value corresponding to the check target 1002 is used to calculate the score value.
[0061] For ease of explanation, the score value is calculated simply by the sum of the relevance. As shown in the relevance 1007 of the check information 1003 of the failure effect 1, the check targets of the failure effect 1 are A, B, and C, and A and B match the check target selected by the user (matching check target 1007). In this case, the relevance of the check target A is "5" and the relevance of the check target B is "3", so the total score value is "8" obtained by adding them together. Similarly, for the failure effect 2, the check targets A, B, and D match (matching check target 1008), so the total score value is "9", for the failure effect 3, the check targets A, B, and D match (matching check target 1009), so the total score value is "9", and for the failure effect 4, the check targets B and D match (matching check target 1010), so the total score value is "8".
[0062] (v) Step 605 The failure mode candidate display processing unit 1012 receives the score value of each failure effect (e.g., failure effects 1 to 4) from the failure effect relevance score calculation unit 1014, and searches for failure effects whose antecedent events do not match (in the example of Figure 10, the antecedent event of failure effect 2 is A, which matches, but the antecedent event of failure effect 3 is D, which does not match).
[0063] FIG. 11 is a diagram for explaining the prioritization of failure effects taking into account antecedent events. The check information display 1101 shown in FIG. 11 is the same display as the check information input GUI 900 shown in FIG. 9. The check information display 1101 shows a state in which antecedent event A is selected for check target B (see antecedent event 1102). In this example, the targets of prioritization are failure effects 1 to 4, and the priority is determined based on the check target associated with failure effect 2, the check target associated with failure effect 3, the check information associated with failure effect 1, and the check target associated with failure effect 4, their total score values, and the presence or absence / match of antecedent events. The check target of failure effect 2_1103 is a case in which the check target B selected by the user matches its antecedent event A, and the check targets of failure effects 1, 3, and 4_1104 show an example in which the antecedent events do not match (when the antecedent events are different or not defined).
[0064] The failure mode candidate display processing unit 1012 lowers the priority when the antecedent events do not match even if the score values of the relevance of the check targets (score values calculated in step 604) are the same. In the example shown in Fig. 11, the failure mode candidate display processing unit 1012 sets a higher priority for failure effect 2, which is the same as antecedent event A selected by the user, among failure effects 2 and 3, which have the same score values.
[0065] (vi) Step 606 The failure mode candidate display processing unit 1012 displays the functional failures and failure modes corresponding to the failure modes whose priorities have been determined in step 605, and the scores, on the display screen in order of priority. For example, the failure mode candidate display processing unit 1012 identifies the functional failures and failure modes corresponding to each failure effect by referring to the relationship (causal relationship) of each state in the FMEA shown in FIG. 3. Specifically, referring to FIG. 3, the functional failure corresponding to the failure effect 2 with the highest priority is identified as functional failure 1 (FF1), and the failure mode corresponding to the functional failure 1 is identified as failure mode 1 (FM1). Furthermore, the functional failure corresponding to the failure effect 3 with the next highest priority is identified as functional failure 2 (FF2), and the failure mode corresponding to the functional failure 2 is identified as failure mode 1 (FF1). The functional failure corresponding to the failure effect 1 with the next highest priority is identified as functional failure 1 (FF1), and the failure mode corresponding to the functional failure 1 is identified as failure mode 1. Furthermore, the functional failure corresponding to the failure effect 4 with the lowest priority is identified as functional failure 3 (FF3), and the failure mode corresponding to the functional failure 3 is identified as failure mode 2.
[0066] FIG. 12 is a diagram showing a failure mode estimation result (order of priority) display 1200 (one example). As shown in FIG. 12, the failure mode candidate display processing unit 1012 outputs functional failures 1201 and failure modes 1202 by sorting them in descending order of score value 1203. If a functional failure has multiple failure effects, the largest score is adopted. Note that those with unmatched antecedent events (for example, functional failure 2 & failure mode 1, functional failure 1 & failure mode 1, and functional failure 3 & failure mode 2, which correspond to the above-mentioned failure effect 3, failure effect 1, and failure effect 4) may be excluded from the list display, but since the fact that the check targets match is important information, those with unmatched antecedent events (including those without antecedent events) may be displayed with a gray background instead of being excluded (display 1204).
[0067] (vii) Step 607 The failure mode candidate display processing unit 1012 judges whether the user has changed the check information and retried the failure mode estimation process. For example, when the user sees the failure mode estimation result display 1200 in Fig. 12, the user judges whether to change the check information (see Fig. 9) and re-execute the failure mode estimation process (the process from step 603 to step 606). If the user wants to re-execute the process, he / she presses the retry button 1206, and if the presented failure mode estimation result is OK, he / she presses the complete button 1205. The failure mode candidate display processing unit 1012 accepts the instruction from the user and judges whether to repeat the process from step 603.
[0068] (2) Second embodiment In the first embodiment, a GUI for fault diagnosis is provided, but in the second embodiment, an example in which the failure mode estimation technique according to the first embodiment is incorporated into an automatic analyzer is described. Also, in the second embodiment, it is shown that the failure mode is estimated by batch processing without requiring user input (input of check information and input of fault effect).
[0069] <Example of the configuration of an automatic analysis system incorporating failure mode estimation processing> 13 is a diagram showing a schematic configuration example of an automatic analysis system 1300 incorporating failure mode transition processing. The automatic analysis system 1300 includes an automatic analysis device 1301, a maintenance support related processing unit (meaning that it does not perform processing that displays a GUI and prompts a user to input; it is also called a batch processing unit) 1302, an extended FMEA database 1303, a threshold information database 1304, and a recovery action definition database 1305. Note that FIG. 13 shows only components necessary for batch processing of the above-mentioned failure mode estimation processing in the automatic analysis system 1300. Also, the maintenance support related processing unit 1302 and each of the databases 1303 to 1305 may be configured to be incorporated in the automatic analysis device 1301, or may be installed as a device (computer) separate from the automatic analysis device 1301.
[0070] The automatic analyzer 1301 outputs information on check targets (for example, included in an automatic analysis log), such as system alert information and log data of sensors, to a batch processor 1302. The maintenance support related processor (batch processor) 1302 is a component that takes in the check targets of the automatic analyzer 1301 and automatically estimates a failure mode, and includes a check information take-in unit 13021, a check information abnormality determination unit 13022, a failure effect relevance score calculation unit 13023, a failure mode display command unit 13024, and a response action execution unit 13025. The maintenance support related processor 1302 can be constructed by a processor (not shown) reading a program for realizing the maintenance support related processor 1302 from a storage device such as a memory and expanding the program in an internal memory of the processor. The extended FMEA database 1303 is configured by adding information on a response method for recovering from a functional failure to the extended FMEA database 141 of FIG. 2.
[0071] In the maintenance support related processing section (batch processing section) 1302, a check information import section 13021 imports a plurality of pieces of check information from the automatic analysis device 1301 using a communication means with the automatic analysis device 1301.
[0072] The check information abnormality determination unit 13022 automatically determines whether an abnormality is observed in the multiple pieces of imported check information (including event data and sensor log data in the automatic analyzer). For example, the check information abnormality determination unit 13022 can be configured to determine normality / abnormality by defining a sensor threshold (normal value range) for each operation event of the automatic analyzer 1301 (defined in the threshold information database 1304) and synchronizing the event data of the automatic analyzer 1301 with time-series sensor data. Alternatively, the check information abnormality determination unit 13022 may be configured to perform data analysis of time-series fluctuations (trends) of the analysis results of the automatic analyzer 1301 to predict, for example, the degree of deterioration of a reagent, and thereby determine that an abnormal value is approaching.
[0073] The failure effect relevance score calculation unit 13023 has the same function as the failure effect relevance score calculation unit 1014 shown in the first embodiment. The failure mode display command unit 13024 issues a command to display a failure mode on a display unit (not shown) of the automatic analysis device 1301 or a display unit (not shown) of a terminal or the like connected thereto.
[0074] In the automatic analysis system 1300, not only is the estimated failure mode displayed (in order of priority), but also control for recovering from the functional failure can be performed on the automatic analysis device 1301 (corresponding action execution unit 13025). Specifically, the corresponding action execution unit 13025 acquires information on a response method for recovering from the functional failure stored in the extended FMEA database 1303 based on the failure mode estimation result, and executes the failure recovery action accordingly. For example, if the failure mode is estimated to be "poor liquid transfer due to clogging of piping", the corresponding action execution unit 13025 issues an instruction to the automatic analysis device 1301 to "forced cleaning of piping" to recover from the functional failure.
[0075] <Specific processing> A more specific process will now be described. As an example, a liquid chromatograph (LC) device, which is a component of the automatic analyzer 1301, will be taken up. Also, reagent input, analysis, and line cleaning are assumed as multiple operational events of the LC device.
[0076] The threshold information database 1304 for determining whether the object to be checked is normal / abnormal stores the normal range of the syringe pressure sensor during each event of reagent injection, analysis, and line cleaning as, for example, xMpa or less when reagent is injected, yMpa or less when analysis, and zMpa or less when line cleaning. The syringe pressure sensor outputs pressure data in chronological order to a log file at specific intervals. Operation events are also output in chronological order to a log file so that it can be determined which operation event was executed during a certain period of time.
[0077] The check information abnormality determination unit 13022 in the maintenance support related processing unit 1302 compares these two time series data to check whether the syringe pressure data is out of the normal range within a certain time from the present. If it is out of the normal range, the check information abnormality determination unit 13022 treats the syringe pressure sensor as a "check target in which an unusual event is observed" like the check target in which an abnormality is detected in the interactive processing shown in the first embodiment. Next, the failure effect relevance score calculation unit 13023 ranks and estimates the failure modes that may have occurred. Then, the failure mode display command unit 13024 displays the parts / areas that are assumed to have a malfunction on the console of the automatic analysis device 1301, etc. The recovery action definition database 1305 is a database that defines recovery actions for functional failures, and stores the definition of a sequence for recovering from a functional failure for each functional failure. If an action for restoring a functional failure that is likely to have occurred is defined in the restoration action definition database 1305, the corresponding action execution unit 13025 automatically executes that restoration action.
[0078] (3) Summary (i) According to conventional technology, when a system malfunction occurs, the check target (contents of system alerts, log data of sensors, etc.) is inspected to identify the malfunction, but it takes time to identify the malfunction, especially when abnormalities are found in multiple check targets at the same time, and shortening the maintenance time is an issue. In addition, it is desirable to predict malfunctions in the equipment to be maintained in advance and automatically perform recovery control to extend the maintenance cycle.
[0079] In order to address such issues, the technology disclosed herein provides an extended FMEA database to assist in identifying failure modes when functional failures occur. In the extended FMEA database, the effective check targets for identifying the causes of functional failures differ depending on the type of functional failure, and a "check target" and a "degree of association between the check target and the functional failure impact" are defined for each impact of the functional failure. The maintenance support device disclosed herein calculates the degree of agreement between the change in the check target corresponding to the failure event recorded in the extended FMEA database and the check result actually observed, thereby narrowing down the failure modes. The maintenance support device then facilitates the diagnosis work (makes user input intuitive and easy to understand) and prioritizes the failure modes by calculating scores.
[0080] As described above, the present disclosure not only presents failure modes that match the check target, but also takes into consideration the temporal context of events that occur in the check target, and preferentially displays failure modes that are likely to cause abnormalities in the check target. This allows for rapid narrowing down of failure modes. It is also applicable to predictive diagnosis before a fatal malfunction occurs in the device to be maintained. Furthermore, by linking with sensor information and system alerts in the device body and providing a means for determining whether or not there is an abnormality in the sensor information, it becomes possible to directly output failure mode candidates from the device body.
[0081] (ii) The functions of the embodiments of the present disclosure can also be realized by software program code. In this case, a storage medium on which the program code is recorded is provided to a system or device, and the computer (or CPU or MPU) of the system or device reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium on which it is stored constitute the present disclosure. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, and ROMs.
[0082] Also, an operating system (OS) running on a computer may perform all or a part of the actual processing based on the instructions of the program code, and the functions of the above-mentioned embodiments may be realized by the processing. Furthermore, after the program code read from a storage medium is written into a memory on a computer, a CPU of the computer may perform all or a part of the actual processing based on the instructions of the program code, and the functions of the above-mentioned embodiments may be realized by the processing.
[0083] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed over a network and stored in a storage means such as a hard disk or memory of the system or device, or in a storage medium such as a CD-RW or CD-R, so that when used, the computer (or CPU or MPU) of the system or device reads out and executes the program code stored in the storage means or storage medium.
[0084] Finally, it should be understood that the processes and techniques described herein are not inherently related to any particular apparatus, but may be implemented by any suitable combination of components. Moreover, various types of general purpose devices may be used in accordance with the teachings described herein. It may prove beneficial to construct specialized apparatus to perform the steps of the methods described herein. Also, various inventions may be formed by suitable combinations of multiple components disclosed in the embodiments. For example, some components may be omitted from all components shown in the embodiments. Furthermore, components across different embodiments may be combined as appropriate. Although the present disclosure has been described with reference to specific examples, these are intended to be illustrative and not limiting in all respects. Those skilled in the art will recognize that there are numerous combinations of hardware, software, and firmware suitable for implementing the present disclosure. For example, the described software may be implemented in a wide variety of programming or scripting languages, such as assembler, C / C++, perl, Shell, PHP, Java, and the like.
[0085] Furthermore, in the above-described embodiment, the control lines and information lines are those that are considered necessary for the explanation, and not all of the control lines and information lines in the product are necessarily shown. All of the components may be connected to each other. [Explanation of symbols]
[0086] 10 Maintenance support equipment 100 processors 110 Communication equipment 120 Input Device 130 Output Device 140 Storage device 141 Expanded FMEA Database 101 Maintenance support related processing section (GUI processing section) 102 Input / Output Control Unit 103 Communication control section 1011 Functional failure effect input processing section 1012 Failure mode candidate display processing unit 1013 Check information input processing unit 1014 Failure effect relevance score calculation unit 1015 Check target antecedent event evaluation section 1300 Automated Analysis System 1301 Automatic analyzer 1302 Maintenance support related processing section (non-GUI processing section (batch processing section)) 1303 Expanded FMEA database 1304 Threshold Information Database 1305 Recovery Action Definition Database 13021 Check information import unit 13022 Check information abnormality judgment part 13023 Failure effect relevance score calculation unit 13024 Failure mode display command unit 13025 Response Action Execution Department
Claims
1. An extended FMEA database including, for each failure effect, information on a check target, information on a degree of association between the check target and the failure effect, and information on a preceding event of the check target; A processor that acquires information on a check target confirmed as an event, and identifies a failure mode corresponding to the failure effect based on the acquired check target, The FMEA database further defines a causal relationship between the failure effect and a failure mode corresponding to the failure effect; The processor, a first process for extracting from the extended FMEA database information on failure effects related to the check object; a second process of calculating a score value of the failure effect extracted in the first process by referring to information on the degree of association between the check target and the failure effect, so that the score value increases as the degree of association increases; a third process of presenting a failure mode corresponding to the failure effect extracted in the first process based on the causal relationship and presenting the score value; Run The processor executes the third process so as to give a higher priority to a failure mode corresponding to a failure effect having a high score value; The processor further executes a process of extracting the antecedent event in the check target by referring to the extended FMEA database; When there is a failure effect having the same score value among the failure effects extracted in the first process, the processor increases the priority of the failure effect having the same antecedent event as an antecedent event designated by a user, and executes the third process. Information processing device.
2. In claim 1, An information processing apparatus, wherein the check target confirmed as the event is a check target selected by a user.
3. In claim 1, The check target confirmed as the event is a check target identified from event data and sensor log data output from an apparatus that is a maintenance support target.
4. an extended FMEA database including, for each failure effect of the automatic analysis device, check information, information on the degree of association between the check information and the failure effect, and information on antecedent events of the check information; a processor that acquires event data and sensor log data from the automatic analyzer as the check information, and identifies a failure mode corresponding to the failure effect based on the acquired check information; The FMEA database further defines a causal relationship between the failure effect and a failure mode corresponding to the failure effect; The processor, a first process for determining whether or not there is an abnormality in the sensor log data; A second process of extracting information on a fault effect related to the abnormal sensor log data that is determined to have an abnormality from the extended FMEA database; A third process of calculating a score value of the failure effect extracted in the second process by referring to check information corresponding to the abnormal sensor log data and information on the degree of association of the failure effect; a fourth process of estimating and presenting a failure mode corresponding to the failure effect extracted in the second process based on the causal relationship, and presenting the score value; Run The processor executes the fourth process so as to give a higher priority to a failure mode corresponding to a failure effect having a high score value; The processor further performs a process of extracting the antecedent event in the check information by referring to the extended FMEA database; When there is a failure effect having the same score value among the failure effects extracted in the second process, the processor increases the priority of the failure effect having the same antecedent event as an antecedent event designated by a user, and executes the fourth process. Automated analysis system.
5. In claim 4, Further, a threshold information database is provided for storing information on a sensor threshold that defines a normal range of sensor data for each operation event of the automatic analyzer, In the first process, the processor acquires a sensor threshold corresponding to the sensor that detected the acquired sensor log data from the threshold information database, and determines whether or not there is an abnormality in the sensor log data by comparing the sensor log data with the sensor threshold.
6. In claim 4, The expanded FMEA database further includes countermeasure information for recovering from a functional failure corresponding to the failure effect, The processor acquires the countermeasure information corresponding to the estimated failure mode from the extended FMEA database, and restores the automatic analysis device based on the countermeasure information.
Citation Information
Patent Citations
Establishment method and system of power equipment fault management system and computer equipment
CN111915192A
Failure diagnostic device of vehicular electronic system
JP1998078376A
Failure handling support maintenance DB device
JP2004178059A
Quality improvement system
JP2008257700A
Method for monitoring state of facility
JP2014059910A
