Rule nesting method and system applied to steam turbine troubleshooting and medium

Abstract

The invention provides a rule nesting method and system applied to steam turbine troubleshooting and a medium, and the method comprises the steps: carrying out the separation based on all rules in a database, and obtaining a main rule flow and a front mixed arrangement rule flow; sorting the preposed mixed arrangement rule flow by utilizing macro editing to obtain an ordered preposed rule flow; based on the main rule flow and the ordered preposed rule flow, carrying out integration to obtain an ordered rule flow; and grouping based on the ordered rule flow to obtain a target rule engine, and carrying out turbine fault maintenance operation based on the target rule engine. According to the method, the difficulty of developing and using the steam turbine troubleshooting rule by business personnel can be reduced, and storage and implementation can be separated according to the metadata translation generation rule, so that the rule is universalized, and when the nested rule is applied, the troubleshooting efficiency can be further improved, and the detection accuracy is guaranteed.

Description

Technical Field

[0001] The invention relates to the technical field of data processing and rule application, and in particular to a rule nesting method, system and medium applied to steam turbine fault inspection and repair. Background Art

[0002] When steam turbine maintenance personnel are repairing steam turbine faults, they will test multiple maintenance measurement point information, as well as basic information such as fault phenomena. The personnel will verify this basic information according to different verification rules. During the verification process, due to the influence of the pre-rules of the rules themselves, the need to apply them repeatedly, and the nesting of multiple rules, the verification efficiency will be low and verification errors will occur. Summary of the invention

[0003] The object of the present invention is to provide a rule nesting method, system and medium applied to steam turbine fault maintenance, so as to solve the problem of rule nesting in steam turbine fault maintenance.

[0004] In a first aspect, the present application provides a rule nesting method applied to steam turbine fault troubleshooting, the method comprising:

[0005] Based on all the rules in the database, the main rule flow and the front mixed rule flow are separated;

[0006] Using macro editing to sort the preceding mixed rule flow to obtain an ordered preceding rule flow;

[0007] Integrate the main rule flow and the ordered preceding rule flow to obtain an ordered rule flow;

[0008] A target rule engine is obtained by grouping based on the ordered rule stream, and a turbine fault maintenance operation is performed based on the target rule engine.

[0009] In a possible implementation of the present application, the separation based on all the rules in the database to obtain the main rule flow and the front shuffle rule flow specifically includes:

[0010] Reading all the rules in the database to obtain a mixed rule flow, wherein the mixed rule flow is a metadata set;

[0011] Performing flag bit judgment based on metadata in the mixed rule stream to filter rule types;

[0012] The metadata set is separated into the main rule flow and the preceding mixed rule flow based on the screening result, wherein the main rule flow is a rule in which preceding rules are nested, and the preceding rules in the preceding mixed rule flow have different priorities.

[0013] In a possible implementation of the present application, the method further includes converting the preceding rule into a byte stream, and acquiring the priority corresponding to each preceding rule based on the byte stream.

[0014] In a possible implementation of the present application, each piece of metadata carries the flag bit, and each piece of metadata corresponds to a rule.

[0015] In a possible implementation of the present application, the method of using macro editing to sort the preceding mixed rule flow to obtain an ordered preceding rule flow specifically includes:

[0016] Identifying a preceding measurement point corresponding to each preceding rule in the preceding shuffling rule stream;

[0017] The identification code of the front measuring point is used as the first determination condition of the front measuring point, and the user input parameter is obtained based on macro editing as the second determination condition, wherein the identification code includes a KKS code;

[0018] The ordered preceding rule flow is obtained by prioritizing the preceding rules based on the first determination condition and the second determination condition.

[0019] In a possible implementation of the present application, the integrating the main rule flow and the ordered preceding rule flow to obtain the ordered rule flow specifically includes:

[0020] Based on the ordered preceding rules, each rule in the main rule flow is nested for integration, wherein:

[0021] The rules are sequentially pushed into the rule stack corresponding to each rule based on the priority, and the number depth of the rule stack is the same as the number of the preceding rules with different priorities.

[0022] In a possible implementation of the present application, ordered rule flows are grouped based on application objects, wherein the grouped target rule engine application objects include fault warning services, fault repair services, thermal services, and shafting services.

[0023] In a second aspect, the present application provides a rule nesting system for steam turbine fault troubleshooting, the system comprising:

[0024] A separation module is used to separate all the rules in the database to obtain a main rule flow and a front mixed rule flow;

[0025] A sorting module, used for sorting the preceding mixed rule flow by using macro editing to obtain an ordered preceding rule flow;

[0026] An integration module, used for integrating the main rule flow and the ordered preceding rule flow to obtain an ordered rule flow;

[0027] A grouping module is used to obtain a target rule engine by grouping based on the ordered rule flow, and to perform a turbine fault inspection and maintenance operation based on the target rule engine.

[0028] In a third aspect, the present application provides a computer-readable storage medium as described above, on which a computer program is stored, and when the program is executed by a processor, the rule nesting method applied to turbine fault troubleshooting is implemented.

[0029] In a fourth aspect, the present application provides an electronic device as mentioned above, comprising: a processor and a memory; wherein the memory is used to store a computer program, and the processor is used to load and execute the computer program so that the electronic device executes the rule nesting method applied to turbine fault maintenance.

[0030] As described above, the rule nesting method, system and medium for steam turbine fault maintenance of the present invention can reduce the difficulty for business personnel to develop and use steam turbine fault maintenance rules, and the storage and implementation can be separated by generating rules according to metadata translation, making the rules universal, and further improving the fault maintenance efficiency and ensuring the accuracy of detection when the nested rules are applied. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 Shown is a schematic diagram of method steps of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0032] Figure 2 Shown is a schematic diagram of method steps of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0033] Figure 3 Shown is a data structure diagram of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0034] Figure 4 Shown is a schematic diagram of method steps of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0035] Figure 5 Shown is a schematic diagram of a macro editing display interface of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0036] Figure 6 Shown is a schematic diagram of method steps of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0037] Figure 7Shown is a schematic diagram of a rule engine structure of a rule nesting method applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0038] Figure 8 Shown is a schematic structural diagram of a rule nesting system applied to steam turbine fault troubleshooting in one embodiment of the present invention;

[0039] Fig. 9 Shown is a schematic structural diagram of an electronic device in one embodiment of the present invention.

[0040] Component number description

[0041] Steps S102 to S108

[0042] Steps S202 to S206

[0043] Steps S402 to S406

[0044] Steps S602 to S604

[0045] 80 Rule-nesting system for steam turbine fault troubleshooting

[0046] 81 Separation Module

[0047] 82 Sorting Module

[0048] 83 Integration Module

[0049] 84 Grouping Module DETAILED DESCRIPTION

[0050] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0051] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0052] The innovation of this technology lies in the use of the characteristics of the rule engine to monitor the rule variables, and the change of the rule variable value will trigger the rule engine to recalculate all rules according to the current rule variable value, turning the flat rules into a rule system with rich levels. Thus, a more accurate description of the laws of the objective world can be achieved. The particularity of the measuring points in the field of steam turbines is used, that is, any measuring point has a KKS number, among which KKS is the most common and promising power plant equipment code in the world. Simply put, the digitization of all power plant equipment can be achieved through KKS, and the unique identification code of the equipment will flow in various management and monitoring systems (such as MIS, SIS, DCS, etc.), all with operators and thresholds. Combined with the placeholder technology of the template, the calculation conclusion of a rule is converted into a measuring point, so that it can be reinserted into a new rule. The nesting of rules is realized, and this nesting can be infinitely expanded, which greatly improves the versatility of the rules. It can not only describe maintenance rules, but also early warning rules, vibration rules, thermal rules, etc., and make the rule engine more universal by using the dynamic results of rules.

[0053] Specifically, by utilizing the rule engine's monitoring feature of rule variable changes and changing the value of the rule variable through the existing rules, the rule engine is triggered to dynamically recalculate all rules, achieve rule nesting, and thus establish a universal rule system. The rule engine technology is applied in various fields of steam turbines and becomes a general technology in the field of steam turbines.

[0054] See also Figure 1 In one embodiment of the invention, the rule nesting method for steam turbine fault troubleshooting of the present invention comprises the following steps:

[0055] Step S102, separating all the rules in the database to obtain a main rule flow and a front mixed rule flow;

[0056] Step S104, using macro editing to sort the preceding mixed rule flow to obtain an ordered preceding rule flow;

[0057] Step S106, integrating the main rule flow and the ordered preceding rule flow to obtain an ordered rule flow;

[0058] Step S108, grouping is performed based on the ordered rule stream to obtain a target rule engine, and a turbine fault maintenance operation is performed based on the target rule engine.

[0059] It should be noted that the main rule flow and the front mixed rule flow are obtained by separating all the rules in the database, such as Figure 2 As shown, the specific steps include:

[0060] Step S202, reading all the rules in the database to obtain a mixed rule flow, wherein the mixed rule flow is a metadata set;

[0061] Step S204, performing flag bit judgment based on the metadata in the mixed rule stream to filter the rule type;

[0062] Step S206 , separating the metadata set into the main rule flow and the preceding mixed rule flow based on the screening result, wherein the main rule flow is a rule in which preceding rules are nested, and the preceding rules in the preceding mixed rule flow have different priorities.

[0063] Specifically, it should be noted that the database in this embodiment is specifically the data stored in the fault decision tree constructed by the mind map, and the mind map is automatically exported after the construction is completed. Figure 3 The data structure is stored in the database for permanent preservation. Specifically, the decision tree data generated by the mind map is filled into the Velocity template to generate a byte stream of fault decision rules, and then the byte stream is imported into the rule engine of the actual application described above, so as to realize the function of automatic fault judgment.

[0064] Furthermore, in this embodiment, in the rule nesting method in the rule engine, it is necessary to first separate all the rules in the database to obtain the main rule flow and the preceding mixed rule flow. Specifically, the metadata of each rule contains a flag bit for indicating the rule type of the current rule, and each of the metadata corresponds to a rule, that is, whether it is a preceding rule or a main rule. Therefore, all the rules in the data are read to obtain the mixed rule flow. Accordingly, the mixed rule flow is a metadata set, and the flag bit judgment is performed based on the metadata in the mixed rule flow to filter and obtain the rule type, so that the metadata set is separated from the rule data based on the filtering result to obtain the main rule flow and the preceding mixed rule flow, wherein the main rule flow is a rule in which the preceding rule is nested, and the preceding rules in the preceding mixed rule flow have different priorities.

[0065] Furthermore, in an embodiment of the invention, the method further includes converting the preceding rule into a byte stream, and acquiring the priority corresponding to each preceding rule based on the byte stream.

[0066] It should be noted that the essence of the main rule stream, or the mixed stream of the preceding rules, is a byte stream. Therefore, for byte streams, computer systems generally use interpretation rather than compilation to execute them. However, since the rules are not ordinary byte streams, the correctness of the reasoning cannot be guaranteed by relying solely on the order in which the rules appear. Therefore, using the priority of the rules to ensure the execution order of the rules becomes an inevitable choice. This is also to utilize the dynamic results of the rules to achieve the guarantee of the rules. Since the preceding rules need to be judged first, they are given a higher priority. Based on general cognition, the rules with stronger versatility are designed as the underlying rules, that is, the preceding rules with priority judgment.

[0067] Therefore, it is necessary to sort the pre-shuffle rule flow, specifically, Figure 4 The steps shown include:

[0068] Step S402, identifying a preceding measurement point corresponding to each preceding rule in the preceding shuffling rule flow;

[0069] Step S404, using the identification code of the front measuring point as the first determination condition of the front measuring point and obtaining the user input parameter based on macro editing as the second determination condition, wherein the identification code includes a KKS code;

[0070] Step S406: Prioritize the preceding rules based on the first determination condition and the second determination condition to obtain the ordered preceding rule flow.

[0071] It should be noted that when the preceding mixed rule stream is sorted, the preceding measurement points are specifically identified. Since each judgment condition of the main rule is a preceding measurement point object, when translating a rule metadata into a rule, the KKS code of the current measurement point is used as the first judgment condition for the preceding measurement point judgment, and the operating parameter value and the judgment threshold input by the user interface are used as the second judgment condition of this measurement point based on macro editing. The above two judgment conditions constitute the conditional part of the rule. Therefore, the preceding rule embedded in the main rule still needs to meet such formal requirements to construct a special measurement point object of "preceding measurement point", and the name of the preceding rule is used as the KKS number of this measurement point. The "true value" of whether the preceding rule is established, that is, "true" for success and "false" for failure, is used as the operating parameter of the "preceding measurement point", and "true" and "false" are used as thresholds to form a judgment condition of the main rule, which participates in the decision operation of the main rule, thereby realizing the rule of rules, which makes the rule group more general, more expressive, and applicable to more modules. Specifically, a template for a rule internal object needs to be defined on the translation template to satisfy the above design.

[0072] declare MidConclusion

[0073] checkPointType: int;

[0074] kksCode:String;

[0075] value:double;

[0076] end

[0077] Use the following station statement in the template to set the front rule name to the KKS code of the "front measurement point".

[0078] \$cp_$mesDecisionRule.kksCode:MidConclusion.

[0079] Furthermore, it should be noted that in actual application, macro editing is to use the rule engine to dynamically insert objects without changing the overall system structure, thereby changing the characteristics of the "dynamic rule" technology of the existing rule judgment logic and realizing the function of nesting rules. The specific display interface is as follows: Figure 5 As shown in the figure, since macro editing is a nested rule, the nested rule is regarded as an intermediate conclusion obtained by first judging, and the intermediate conclusion is added to the larger rule to achieve the nesting of rules. Therefore, it is necessary to add a structure that defines the internal object in the rule template, as follows:

[0080] declare MidConclusion

[0081] checkPointType: int;

[0082] kksCode:String;

[0083] value:double;

[0084] end

[0085] Secondly, add the translation statement for the macro module to the template of the original translation condition node content, the content is as follows:

[0086] \$cp_$mesDecisionRule.kksCode:MidConclusion

[0087] After the above two modifications, the entire translation template is adjusted into two template files, one for translating the overall rules framework, the content of which is as follows:

[0088]

[0089]

[0090] The other one is used to translate a single rule. After modification, the file template is:

[0091]

[0092]

[0093] When the user selects a macro in the drop-down box, the current macro will be automatically inserted into the decision tree, and the corresponding metadata will be recorded by adding a constant MACO in the original nodetype field to represent a macro node. Correspondingly, kks macro = threshold information = result. By modifying the above two modules (mind map module and engine module), the application of macro editing in actual production can be realized.

[0094] Further, in one embodiment of the invention, if Figure 6 As shown, the ordered rule flow is obtained by integrating the main rule flow and the ordered preceding rule flow, which specifically includes the following steps:

[0095] Step S602, nesting the ordered preceding rules into the rules in the main rule flow for integration;

[0096] Step S604: Push the rules into the rule stack corresponding to each rule in sequence based on the priority, and the depth of the rule stack is the same as the number of the preceding rules of different priorities.

[0097] It should be noted that when the ordered rule flow is integrated, the ordered preceding rule flow is sequentially placed in each rule file in the main rule flow, and the rule sequence number of the preceding rule is used to find the internally nested rules one by one by using a recursive method until it is impossible to continue searching forward, and these rules are sequentially pushed into the rule stack, the number depth of the rule stack is counted, and then the corresponding priorities are set in sequence to ensure the order of the preceding rules. Accordingly, the number depth of the rule stack is the same as the number value of the preceding rules of different priorities, and in the process of sequential placement, the UUID (Universally Unique Identifier) ​​of the rule is created, and the priority of the rule is set, the preceding rule is first placed in the rule file, and the main rule file is placed in the rule file later, and the placeholder of the main rule file is returned with the rule UUID, thereby realizing multi-level nesting of rules.

[0098] Furthermore, in one embodiment of the invention, the ordered rule flows are grouped based on application objects, wherein the grouped target rule engine application objects include fault warning services, fault repair services, thermal services, and shafting services.

[0099] It should be noted that if Figure 7As shown, it is a composition diagram of the rule engine proposed in this application, wherein the mixed rule flow in the database is divided into a front mixed rule flow and a main rule flow, and then an ordered rule flow is obtained through sorting and integration, so that the ordered rule flow can be grouped to solve different maintenance needs in a targeted manner. Accordingly, the target rule engine application objects after grouping include fault warning service, fault repair service, thermal service and shaft system service.

[0100] An embodiment of the present application also provides a rule nesting system applied to turbine fault maintenance. The rule nesting system applied to turbine fault maintenance can implement the rule nesting method applied to turbine fault maintenance described in the present application. However, the implementation device of the rule nesting method applied to turbine fault maintenance described in the present application includes but is not limited to the structure of the rule nesting system applied to turbine fault maintenance listed in the present embodiment. All structural deformations and replacements of the prior art made according to the principles of the present application are included in the protection scope of the present application.

[0101] See also Figure 8 In one embodiment, this embodiment provides a rule nesting system 80 for steam turbine fault troubleshooting, the system comprising:

[0102] A separation module 81, used for separating all the rules in the database to obtain a main rule flow and a front mixed rule flow;

[0103] A sorting module 82, used to sort the preceding mixed rule flow by using macro editing to obtain an ordered preceding rule flow;

[0104] An integration module 83, configured to integrate the main rule flow and the ordered preceding rule flow to obtain an ordered rule flow;

[0105] The grouping module 84 is used to obtain a target rule engine by grouping based on the ordered rule flow, and perform a turbine fault inspection and maintenance operation based on the target rule engine.

[0106] Since the specific implementation of this embodiment corresponds to the aforementioned method embodiment, the same details will not be repeated here, and those skilled in the art should also understand that Figure 8 The division of the modules in the embodiment is merely a division of logical functions, and in actual implementation, all or part of them can be integrated into one or more physical entities, and these modules can be implemented entirely in the form of software called by processing elements, or entirely in the form of hardware, or some modules can be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware.

[0107] See also Fig. 9This embodiment provides an electronic device. In detail, the electronic device includes at least: a memory and a processor connected via a bus, wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory to execute all or part of the steps in the aforementioned method embodiment.

[0108] In summary, the present invention can reduce the difficulty for business personnel to develop and use turbine fault inspection and repair rules, and can separate storage and implementation by generating rules according to metadata translation, making the rules universal, and further improving the fault inspection and repair efficiency when the nested rules are applied, thereby ensuring the accuracy of detection.

[0109] In the several embodiments provided in the present application, it should be understood that the disclosed system, device or method can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules / units is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or units can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules or units, which can be electrical, mechanical or other forms.

[0110] The modules / units described as separate components may or may not be physically separated, and the components displayed as modules / units may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules / units may be selected according to actual needs to achieve the purpose of the embodiments of the present application. For example, the functional modules / units in the various embodiments of the present application may be integrated into one processing module, or each module / unit may exist physically separately, or two or more modules / units may be integrated into one module / unit.

[0111] Those of ordinary skill in the art should further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0112] The present application embodiment also provides a computer-readable storage medium. A person of ordinary skill in the art can understand that all or part of the steps in the method for implementing the above embodiment can be completed by a program to instruct the processor, and the program can be stored in a computer-readable storage medium, and the storage medium is a non-transitory medium, such as a random access memory, a read-only memory, a flash memory, a hard disk, a solid-state hard disk, a magnetic tape, a floppy disk, an optical disc, and any combination thereof. The above storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state hard disk (SSD)), etc.

[0113] The present application embodiment may also provide a computer program product, the computer program product including one or more computer instructions. When the computer instructions are loaded and executed on a computing device, the process or function described in the embodiment of the present application is generated in whole or in part. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer or data center.

[0114] When the computer program product is executed by a computer, the computer executes the method described in the above method embodiment. The computer program product may be a software installation package, and when the above method is required, the computer program product may be downloaded and executed on a computer.

[0115] The descriptions of the processes or structures corresponding to the above-mentioned figures have different emphases. For parts that are not described in detail in a certain process or structure, please refer to the relevant descriptions of other processes or structures.

[0116] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A rule nesting method for steam turbine fault troubleshooting, characterized in that: include: Based on all the rules in the database, the main rule flow and the front mixed rule flow are separated; Using macro editing to sort the preceding mixed rule flow to obtain an ordered preceding rule flow; Integrate the main rule flow and the ordered preceding rule flow to obtain an ordered rule flow; A target rule engine is obtained by grouping based on the ordered rule stream, and a turbine fault maintenance operation is performed based on the target rule engine.

2. The rule nesting method for steam turbine fault troubleshooting according to claim 1 is characterized in that: The separation based on all the rules in the database to obtain the main rule flow and the front mixed rule flow specifically includes: Reading all the rules in the database to obtain a mixed rule flow, wherein the mixed rule flow is a metadata set; Performing flag bit judgment based on metadata in the mixed rule stream to filter rule types; The metadata set is separated into the main rule flow and the preceding mixed rule flow based on the screening result, wherein the main rule flow is a rule in which preceding rules are nested, and the preceding rules in the preceding mixed rule flow have different priorities.

3. The rule nesting method for steam turbine fault troubleshooting according to claim 2 is characterized in that: The method further includes converting the preceding rule into a byte stream, and acquiring the priority corresponding to each preceding rule based on the byte stream.

4. The rule nesting method for steam turbine fault troubleshooting according to claim 2 is characterized in that: Each piece of metadata carries the flag bit, and each piece of metadata corresponds to a rule.

5. The rule nesting method for steam turbine fault troubleshooting according to claim 2 is characterized in that: The method of using macro editing to sort the preceding mixed rule flow to obtain an ordered preceding rule flow specifically includes: Identifying a preceding measurement point corresponding to each preceding rule in the preceding shuffling rule stream; The identification code of the front measuring point is used as the first determination condition of the front measuring point, and the user input parameter is obtained based on macro editing as the second determination condition, wherein the identification code includes a KKS code; The ordered preceding rule flow is obtained by prioritizing the preceding rules based on the first determination condition and the second determination condition.

6. The rule nesting method for steam turbine fault troubleshooting according to claim 5, characterized in that: The step of integrating the main rule flow and the ordered preceding rule flow to obtain the ordered rule flow specifically includes: The ordered preceding rules are nested into each rule in the main rule flow for integration, wherein the rules are sequentially pushed into the rule stack corresponding to each rule based on the priority, and the depth of the rule stack is the same as the number of preceding rules of different priorities.

7. The rule nesting method for steam turbine fault troubleshooting according to claim 6 is characterized in that: The ordered rule flows are grouped based on application objects, wherein the grouped target rule engine application objects include fault warning service, fault repair service, thermal service and shafting service.

8. A rule nesting system applied to steam turbine fault maintenance, characterized in that: A rule nesting method for steam turbine fault troubleshooting as described in any one of claims 1 to 7, wherein the system comprises: A separation module is used to separate all the rules in the database to obtain a main rule flow and a front mixed rule flow; A sorting module, used for sorting the preceding mixed rule flow by using macro editing to obtain an ordered preceding rule flow; An integration module, used for integrating the main rule flow and the ordered preceding rule flow to obtain an ordered rule flow; A grouping module is used to obtain a target rule engine by grouping based on the ordered rule flow, and to perform a turbine fault inspection and maintenance operation based on the target rule engine.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the rule nesting method for steam turbine fault inspection and maintenance as described in any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: The electronic device comprises: a processor and a memory; wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, so that the electronic device executes the rule nesting method applied to turbine fault maintenance as described in any one of claims 1 to 7.

Images