A fault diagnosis method and system based on equipment maintenance knowledge base

Abstract

The application belongs to the technical field of computers and provides a fault diagnosis method and system based on equipment maintenance knowledge base. The method comprises the following steps: constructing an equipment maintenance knowledge base, wherein the equipment maintenance knowledge base comprises phenomenon events, fault causes and the relationship between the phenomenon events and the fault causes, the relationship is a fault scene, and the fault scene comprises a single cause scene and a combined cause scene; acquiring a last node in a fault diagnosis path as a phenomenon event, retrieving a fault scene of the phenomenon event, and if the retrieval result is empty, the phenomenon event is a fault diagnosis result. The single cause scene can realize the reasoning ability of the traditional decision tree rule, the combined cause scene is combined with the single cause scene, the fault combination condition traversal with exponential complexity can be automatically expanded based on a small amount of structured expression, the knowledge representation is simplified, and the complexity and workload of the construction and maintenance of the knowledge base are reduced.

Description

Technical Field

[0001] This invention belongs to the field of computer technology, and in particular relates to a fault diagnosis method and system based on an equipment maintenance knowledge base. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] Maintenance knowledge bases typically use a QA (Questions and Answers) list to store common faults and their solutions. This method is prone to the problem of brute-force exhaustive search. For example, a device with 20 components might have millions of potential faults. In practical applications, exhaustively listing all faults is extremely difficult.

[0004] Building a device diagnostic knowledge base using expert system technology based on reasoning rules also faces the challenge of brute-force enumeration of diagnostic nodes. For example, for a device consisting of 20 components, the rule base may need to handle a fault analysis decision tree with millions of nodes.

[0005] Fault tree technology provides a mechanism for decomposing the causes of faults, which improves the efficiency of fault diagnosis to some extent. Building a knowledge base based on fault trees requires highly specialized personnel; the construction and maintenance of such a knowledge base are both technically challenging. Furthermore, the complex logic of fault trees is not conducive to building human-computer interaction systems based on natural language.

[0006] In summary, the existing maintenance knowledge base, due to its complex logic, cannot quickly diagnose faults. Summary of the Invention

[0007] To address the technical problems described in the background section, this invention provides a fault diagnosis method and system based on an equipment maintenance knowledge base. This method simplifies knowledge representation, reduces the complexity and workload of knowledge base construction and maintenance, and improves the speed of fault diagnosis. This invention relates to customer service scenarios for product fault consultation and can present service content in the form of WeChat customer service robots, web-based customer service robots, etc.

[0008] To achieve the above objectives, the present invention adopts the following technical solution:

[0009] The first aspect of the present invention provides a fault diagnosis method based on an equipment maintenance knowledge base.

[0010] A fault diagnosis method based on an equipment maintenance knowledge base includes:

[0011] Construct an equipment maintenance knowledge base, which includes phenomena and events, fault causes, and the relationship between phenomena and events and fault causes. The relationship is a fault scenario, which includes single-cause scenarios and combined-cause scenarios.

[0012] The last node in the fault diagnosis path is the phenomenon event. The fault scenario of the phenomenon event is retrieved. If the retrieval result is empty, the phenomenon event is the fault diagnosis result.

[0013] If the retrieved fault scenario is a single-cause scenario, the user is provided with a list of first fault cause events corresponding to the phenomenon event. In response to the instruction to click on the first fault cause event in the list of first fault cause events, the first fault cause event is added to the fault diagnosis path, and the first fault cause event is set to an active state in the context environment. The first fault cause event is also identified as a phenomenon event, and the process of retrieving the fault scenario of the phenomenon event is repeated.

[0014] If the retrieved fault scenario is a combined cause scenario, select the fault cause events with unknown activation states corresponding to the phenomenon event to construct a second fault cause event list for the user to choose from. In response to the skip instruction clicked on the second fault cause event list, the second fault cause event in the second fault cause event list is not activated. Repeat the process of selecting the second fault cause event list until the non-skip instruction of the second fault cause event list is selected, at which point the second fault cause event is activated. Add the second fault cause event to the end of the fault diagnosis path, set the second fault cause event to the active state in the context environment, and identify the second fault cause event as a phenomenon event. Repeat the process of retrieving the fault scenario of the phenomenon event.

[0015] Furthermore, in the fault diagnosis path, for the fault causes corresponding to the combined cause scenario, fault causes that do not have a logical relationship before and after are placed at the same level of nodes, while fault causes that have a logical relationship before and after are placed at different levels of nodes.

[0016] Furthermore, if the retrieved fault scenario is a combined cause scenario and there are no events with unknown activation states, then this consultation will not yield a fault diagnosis result.

[0017] Furthermore, the equipment maintenance knowledge base also includes fault diagnosis methods, and fault diagnosis methods are assigned according to the causes of faults.

[0018] Furthermore, in the fault diagnosis path, the same node is used to represent the same content, which includes maintenance events and / or fault causes and / or fault inspection methods.

[0019] Furthermore, each phenomenon event and / or fault cause and / or fault checking method includes an active state, an inactive state, and an unknown active state.

[0020] Furthermore, when responding to a click-skip instruction, the skipped phenomenon event and / or fault cause is in an inactive state, and the phenomenon event and / or fault cause is removed from the fault diagnosis path.

[0021] A second aspect of the present invention provides a fault diagnosis system based on an equipment maintenance knowledge base.

[0022] A fault diagnosis system based on an equipment maintenance knowledge base includes:

[0023] The equipment maintenance knowledge base construction module is configured to: construct an equipment maintenance knowledge base, which includes phenomenon events, fault causes, and the relationship between phenomenon events and fault causes. The relationship is a fault scenario, and the fault scenario includes: single cause scenario and combined cause scenario.

[0024] The fault diagnosis module is configured to: obtain the last node in the fault diagnosis path as the phenomenon event, retrieve the fault scenario of the phenomenon event, and if the retrieval result is empty, then the phenomenon event is the fault diagnosis result.

[0025] The single-cause scenario diagnosis path selection module is configured to: if the retrieved fault scenario is a single-cause scenario, provide the user with a list of first fault cause events corresponding to the phenomenon event; in response to the instruction to click on the first fault cause event in the list of first fault cause events, add the first fault cause event to the fault diagnosis path, set the first fault cause event to the active state in the context environment, and identify the first fault cause event as a phenomenon event, and repeat the process of retrieving the fault scenario of the phenomenon event.

[0026] The combined cause scenario diagnosis path selection module is configured as follows: if the retrieved fault scenario is a combined cause scenario, select the fault cause events with unknown activation states corresponding to the phenomenon event to construct a second fault cause event list for user selection. In response to the click of the skip instruction of the second fault cause event list, the second fault cause event in the second fault cause event list is not activated. The process of selecting the second fault cause event list is repeated until the non-skip instruction of the second fault cause event list is selected, then the second fault cause event is activated. The second fault cause event is added to the end of the fault diagnosis path, and the second fault cause event is set to the active state in the context environment. The second fault cause event is also identified as a phenomenon event. The process of retrieving the fault scenario of the phenomenon event is repeated.

[0027] A third aspect of the present invention provides a computer-readable storage medium.

[0028] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the fault diagnosis method based on an equipment maintenance knowledge base as described in the first aspect above.

[0029] A fourth aspect of the present invention provides a computer device.

[0030] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the steps of the fault diagnosis method based on an equipment maintenance knowledge base as described in the first aspect above.

[0031] Compared with the prior art, the beneficial effects of the present invention are:

[0032] The single-cause scenario described in this invention can achieve the reasoning ability of traditional decision tree-based rules. Combining the combined-cause scenario with the single-cause scenario can achieve fault combination condition traversal with exponential complexity based on a small amount of structured expression, which simplifies knowledge representation, reduces the complexity and workload of knowledge base construction and maintenance, and improves the speed of fault diagnosis.

[0033] Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0034] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0035] Figure 1 This is a flowchart illustrating the fault diagnosis method based on an equipment maintenance knowledge base as shown in this invention;

[0036] Figure 2 This is an example diagram illustrating the fault diagnosis method based on an equipment maintenance knowledge base as shown in this invention;

[0037] In the diagram, = represents a single-cause scenario, 》 represents a combined-cause scenario, and / / represents an inactive state. Detailed Implementation

[0038] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0039] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0040] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0041] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of methods and systems according to various embodiments of this disclosure. It should be noted that each block in a flowchart or block diagram may represent a module, segment, or portion of code, which may include one or more executable instructions for implementing the logical functions specified in the various embodiments. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that shown in the drawings. For example, two consecutively represented blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, may be implemented using a dedicated hardware-based system that performs the specified functions or operations, or using a combination of dedicated hardware and computer instructions.

[0042] Example 1

[0043] like Figure 1As shown, this embodiment provides a fault diagnosis method based on an equipment maintenance knowledge base. This embodiment uses the application of this method to a server as an example for illustration. It is understood that this method can also be applied to terminals, and can also be applied to systems including terminals, servers, and other components, and can be implemented through interaction between the terminal and the server. The server can be an independent physical server, a server cluster composed of multiple physical servers, or a distributed system. It can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network servers, cloud communication, middleware services, domain name services, CDN security services, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited herein. In this embodiment, the method includes the following steps:

[0044] Construct an equipment maintenance knowledge base, which includes phenomena and events, fault causes, and the relationship between phenomena and events and fault causes. The relationship is a fault scenario, which includes single-cause scenarios and combined-cause scenarios.

[0045] The last node in the fault diagnosis path is the phenomenon event. The fault scenario of the phenomenon event is retrieved. If the retrieval result is empty, the phenomenon event is the fault diagnosis result.

[0046] If the retrieved fault scenario is a single-cause scenario, the user is provided with a list of first fault cause events corresponding to the phenomenon event. In response to the instruction to click on the first fault cause event in the list of first fault cause events, the first fault cause event is added to the fault diagnosis path, and the first fault cause event is set to an active state in the context environment. The first fault cause event is also identified as a phenomenon event, and the process of retrieving the fault scenario of the phenomenon event is repeated.

[0047] If the retrieved fault scenario is a combined cause scenario, select the fault cause events with unknown activation states corresponding to the phenomenon event to construct a second fault cause event list for the user to choose from. In response to the skip instruction clicked on the second fault cause event list, the second fault cause event in the second fault cause event list is not activated. Repeat the process of selecting the second fault cause event list until the non-skip instruction of the second fault cause event list is selected, at which point the second fault cause event is activated. Add the second fault cause event to the end of the fault diagnosis path, set the second fault cause event to the active state in the context environment, and identify the second fault cause event as a phenomenon event. Repeat the process of retrieving the fault scenario of the phenomenon event.

[0048] In this embodiment, the equipment maintenance knowledge base consists of a set of "phenomenal events" and a set of "fault scenarios". "Phenomenal events" describe fault phenomena, fault causes, fault inspection methods, etc. "Fault scenarios" are divided into two types: "single-cause scenarios" and "combined-cause scenarios". A "fault scenario" defines the relationship between a fault phenomenon event and other fault cause events; the relationship is determined by the fault scenario type, i.e., "single-cause scenarios" and "combined-cause scenarios".

[0049] At the start of the diagnosis, the knowledge base automatically activates the fault phenomenon events of the root scenario and uses the root node as the starting point of the fault diagnosis path. If an event is activated by the system or a user, the event and its activation state are added to the context environment. Then, the knowledge base selects the last node of the fault diagnosis path and identifies the fault scenario with this node as the phenomenon event. The user then activates the appropriate fault cause event from this scenario based on the actual situation.

[0050] When a phenomenon event is activated in a "single-cause scenario" type of fault scenario, the user can only activate one fault cause event in the fault scenario definition. When a phenomenon event is activated in a "combined-cause scenario" type of fault scenario, the user needs to activate each fault cause event in the fault scenario definition one by one until one of the events is confirmed by the user as the correct fault cause, at which point the diagnostic process ends.

[0051] When a user activates a fault cause event marked as "skipped" in a fault scenario, the phenomenon event in that scenario is set to an inactive state, and the event and its subsequent events in the fault diagnosis path are removed from the fault diagnosis path.

[0052] If a maintenance event has never been defined as a symptom event in a specific failure scenario, then that maintenance event is the final cause event in the equipment failure analysis. For example, the event "the main inlet valve is rusted" only appears as a cause event in the failure scenario of "all radiators are cold," and no scenario has ever defined it as a further cause event. Therefore, when the reasoning process activates the "the main inlet valve is rusted" event, it means the reasoning process ends. This indicates that in the reasoning decision tree, "the main inlet valve is rusted" is a leaf at the bottom layer.

[0053] The combined effect of the above processes allows "single-cause scenario" type fault scenarios to achieve the reasoning capabilities of traditional decision tree-based rules; the combination of "combined-cause scenario" type fault scenarios and "single-cause scenario" type fault scenarios can achieve fault combination condition traversal with exponential complexity based on a small amount of structured expression, simplifying knowledge representation and reducing the complexity and workload of knowledge base construction and maintenance.

[0054] During the diagnostic dialogue, the knowledge base generates a contextual environment, which includes: a set of maintenance event states, recording the state of each maintenance event in the knowledge base, with states including three possibilities: active, inactive, and unknown.

[0055] The fault scenario definition includes natural language text prompts for phenomenon events and fault cause events, which are used to provide prompt information to users during human-computer interaction dialogues.

[0056] Combined with appendix Figure 2 The fault diagnosis method described in this embodiment includes the following steps:

[0057] (1) Take the last node in the fault diagnosis path as the phenomenon event (A), retrieve the fault scenario definition with this event as the phenomenon event, if the search result is empty, it can be determined that the current event is the final fault cause event, and this consultation ends.

[0058] (2) If the scenario is a single-cause scenario (A+), provide the user with the list of fault cause events defined in the scenario so that the user can provide feedback on the specific cause, add the fault cause event (B) to the fault diagnosis path, and set the event (B) to the active state (B+) in the context environment, and then continue to repeat step (1).

[0059] (3) If the scenario is a combined cause scenario F, select an event (G, H, I) in an unknown active state from the fault cause event list, obtain the fault scenario definition of the event phenomenon, and read the fault cause event list for the user to select. If the user selects a fault cause event (G) with the attribute "skip", the current fault phenomenon event status is set to inactive (G1-, G2-), and proceed to step (3) to repeat; if the user selects a fault cause event (H2) with the attribute "not skipped", the current fault cause event status is set to active (H2+), and the event is added to the end of the fault diagnosis path, and proceed to step (1). If there is no event in an unknown active state in the combined fault cause list, the consultation cannot obtain a definite diagnosis result.

[0060] Figure 2 The logic in can be expressed as:

[0061] A(A+)

[0062] AB(A+, B+)

[0063] ABF(A+, B+, F+)

[0064] ABFG(A+, B+, F+)

[0065] ABFG-G1(A+, B+, F+, G-, G1-)

[0066] ABFG-G1-H(A+, B+, F+, G-, G1-)

[0067] ABFG-G1-H (A+, B+, F+, G-, G1-, H+)

[0068] ABFG-G1-H-H2 (End)

[0069] Where + indicates an active state and - indicates an inactive state, that is... Figure 2 The cause of the fault is H2.

[0070] Taking the maintenance scenario of heating equipment as an example, for a maintenance event in a heating assistance request where "all rooms are cold", the existing solution would sequentially determine the heating status, the impact condition, filter inspection, air blockage inspection, and other situations. However, the solution adopted in this embodiment allows the user to select the heating status, the impact condition, the filter inspection, the air blockage inspection, or other situations. Since the multiple fault causes of the same maintenance event are selected by the user in parallel, it can simplify the knowledge representation and reduce the complexity and workload of knowledge base construction and maintenance.

[0071] Example 2

[0072] This embodiment provides a fault diagnosis system based on an equipment maintenance knowledge base.

[0073] A fault diagnosis system based on an equipment maintenance knowledge base includes:

[0074] The equipment maintenance knowledge base construction module is configured to: construct an equipment maintenance knowledge base, which includes phenomenon events, fault causes, and the relationship between phenomenon events and fault causes. The relationship is a fault scenario, and the fault scenario includes: single cause scenario and combined cause scenario.

[0075] The fault diagnosis module is configured to: obtain the last node in the fault diagnosis path as the phenomenon event, retrieve the fault scenario of the phenomenon event, and if the retrieval result is empty, then the phenomenon event is the fault diagnosis result.

[0076] The single-cause scenario diagnosis path selection module is configured to: if the retrieved fault scenario is a single-cause scenario, provide the user with a list of first fault cause events corresponding to the phenomenon event; in response to the instruction to click on the first fault cause event in the list of first fault cause events, add the first fault cause event to the fault diagnosis path, set the first fault cause event to the active state in the context environment, and identify the first fault cause event as a phenomenon event, and repeat the process of retrieving the fault scenario of the phenomenon event.

[0077] The combined cause scenario diagnosis path selection module is configured as follows: if the retrieved fault scenario is a combined cause scenario, select the fault cause events with unknown activation states corresponding to the phenomenon event to construct a second fault cause event list for user selection. In response to the click of the skip instruction of the second fault cause event list, the second fault cause event in the second fault cause event list is not activated. The process of selecting the second fault cause event list is repeated until the non-skip instruction of the second fault cause event list is selected, then the second fault cause event is activated. The second fault cause event is added to the end of the fault diagnosis path, and the second fault cause event is set to the active state in the context environment. The second fault cause event is also identified as a phenomenon event. The process of retrieving the fault scenario of the phenomenon event is repeated.

[0078] It should be noted that the above-mentioned equipment maintenance knowledge base construction module, fault diagnosis module, single-cause scenario diagnosis path selection module, and combined-cause scenario diagnosis path selection module are the same examples and application scenarios implemented in the steps of Embodiment 1, but are not limited to the content disclosed in Embodiment 1. It should also be noted that the above modules, as part of the system, can be executed in a computer system such as a set of computer-executable instructions.

[0079] Example 3

[0080] This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps in the fault diagnosis method based on an equipment maintenance knowledge base as described in Embodiment 1 above.

[0081] Example 4

[0082] This embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps in the fault diagnosis method based on the equipment maintenance knowledge base as described in Embodiment 1 above.

[0083] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0084] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0085] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0086] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0087] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0088] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A fault diagnosis method based on an equipment maintenance knowledge base, characterized in that, include: Construct an equipment maintenance knowledge base, which includes phenomena and events, fault causes, and the relationship between phenomena and events and fault causes. The relationship is a fault scenario, which includes single-cause scenarios and combined-cause scenarios. The last node in the fault diagnosis path is the phenomenon event. The fault scenario of the phenomenon event is retrieved. If the retrieval result is empty, the phenomenon event is the fault diagnosis result. If the retrieved fault scenario is a single-cause scenario, the user is provided with a list of first fault cause events corresponding to the phenomenon event. In response to the instruction to click on the first fault cause event in the list of first fault cause events, the first fault cause event is added to the fault diagnosis path, and the first fault cause event is set to an active state in the context environment. The first fault cause event is also identified as a phenomenon event, and the process of retrieving the fault scenario of the phenomenon event is repeated. If the retrieved fault scenario is a combined cause scenario, select the fault cause events with unknown activation states corresponding to the phenomenon event to construct a second fault cause event list for the user to choose from. In response to the skip instruction of clicking the second fault cause event list, if the second fault cause event in the second fault cause event list is not activated, repeat the process of selecting the second fault cause event list until the non-skip instruction of the second fault cause event list is selected. If the second fault cause event is activated, add the second fault cause event to the end of the fault diagnosis path, set the second fault cause event to the active state in the context environment, and identify the second fault cause event as a phenomenon event, and repeat the process of retrieving the fault scenario of the phenomenon event.

2. The fault diagnosis method based on an equipment maintenance knowledge base according to claim 1, characterized in that, In the fault diagnosis path, for the fault causes corresponding to the combined cause scenario, fault causes that do not have a logical relationship before and after are placed at the same level of nodes, while fault causes that have a logical relationship before and after are placed at different levels of nodes.

3. The fault diagnosis method based on an equipment maintenance knowledge base according to claim 1, characterized in that, If the retrieved fault scenario is a combined cause scenario and there are no events with unknown activation states, then this consultation will not yield a fault diagnosis result.

4. The fault diagnosis method based on an equipment maintenance knowledge base according to claim 1, characterized in that, The equipment maintenance knowledge base also includes fault diagnosis methods, and fault diagnosis methods are assigned according to the causes of faults.

5. The fault diagnosis method based on an equipment maintenance knowledge base according to claim 1, characterized in that, In the fault diagnosis path, the same node is used to represent the same content, which includes maintenance events and / or fault causes and / or fault inspection methods.

6. The fault diagnosis method based on an equipment maintenance knowledge base according to claim 1, characterized in that, Each phenomenon event and / or fault cause and / or fault diagnosis method includes an active state, an inactive state, and an unknown active state.

7. The fault diagnosis method based on an equipment maintenance knowledge base according to claim 1, characterized in that, When a click to skip command is executed, the skipped phenomenon event and / or fault cause is in an inactive state, and the phenomenon event and / or fault cause is removed from the fault diagnosis path.

8. A fault diagnosis system based on an equipment maintenance knowledge base, characterized in that, include: The equipment maintenance knowledge base construction module is configured to: construct an equipment maintenance knowledge base, which includes phenomenon events, fault causes, and the relationship between phenomenon events and fault causes. The relationship is a fault scenario, and the fault scenario includes: single cause scenario and combined cause scenario. The fault diagnosis module is configured to: obtain the last node in the fault diagnosis path as the phenomenon event, retrieve the fault scenario of the phenomenon event, and if the retrieval result is empty, then the phenomenon event is the fault diagnosis result. The single-cause scenario diagnosis path selection module is configured to: if the retrieved fault scenario is a single-cause scenario, provide the user with a list of first fault cause events corresponding to the phenomenon event; in response to the instruction to click on the first fault cause event in the list of first fault cause events, add the first fault cause event to the fault diagnosis path, set the first fault cause event to the active state in the context environment, and identify the first fault cause event as a phenomenon event, and repeat the process of retrieving the fault scenario of the phenomenon event. The combined cause scenario diagnosis path selection module is configured as follows: if the retrieved fault scenario is a combined cause scenario, select the fault cause events with unknown activation states corresponding to the phenomenon event to construct a second fault cause event list for the user to select. In response to the skip instruction of clicking the second fault cause event list, if the second fault cause event in the second fault cause event list is not activated, repeat the process of selecting the second fault cause event list until the non-skip instruction of the second fault cause event list is selected. If the second fault cause event is activated, add the second fault cause event to the end of the fault diagnosis path, set the second fault cause event to the active state in the context environment, and identify the second fault cause event as a phenomenon event, and repeat the process of retrieving the fault scenario of the phenomenon event.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the fault diagnosis method based on the equipment maintenance knowledge base as described in any one of claims 1-7.

10. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the fault diagnosis method based on the equipment maintenance knowledge base as described in any one of claims 1-7.

Images