Knowledge management method and system, electronic equipment and storage medium
By importing FEMA data into the graph database and integrating it with the open source framework, the target FEMA knowledge graph is generated, and the problem of inefficiency of traditional systems is solved, and automated analysis and efficient knowledge graph processing are achieved.
Patent Information
- Application Number
- CN202410846599.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-06-27
- Publication Date
- 2024-11-12
AI Technical Summary
The traditional FEMA knowledge management system is inefficient in analyzing knowledge graphs, requires a lot of manual intervention, and cannot realize automated construction and analysis.
Use graph database to import FEMA related data, node model and edge model, and integrate the graph database with object relationship mapping framework into open source framework applications, generate target FEMA knowledge graphs based on user requests, and use shortest path algorithm, association analysis algorithm or increase Delete, modify and check algorithms for analysis and operation.
It realizes the automatic map construction and analysis of FEMA data, improves processing efficiency, and can generate corresponding maps according to user needs, meeting users' real-time and intelligent needs.
Smart Images

Figure CN118939808A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information processing technology, and in particular to a knowledge management method, system, electronic device and storage medium. Background Art
[0002] With the rapid development of intelligent manufacturing industry, enterprises have increasingly demanded the real-time, accuracy and intelligence of FEMA (Failure mode and effects analysis) process, and the scale of FEMA data generated is also getting larger and larger. At present, traditional FEMA knowledge management systems usually use relational databases when performing graph analysis on FEMA data. However, relational databases cannot realize the automatic construction and analysis of knowledge graphs, which requires a lot of manual intervention and is inefficient.
[0003] It can be seen that the existing technology has the problem of low efficiency when analyzing knowledge graphs. Summary of the invention
[0004] In view of the above problems, the present application provides a knowledge management method, system, electronic device and storage medium to solve the problem of low efficiency in knowledge graph analysis existing in the prior art.
[0005] According to a first aspect of an embodiment of the present application, a knowledge management method is provided, the method comprising: importing first FEMA related data, a node model and an edge model into a graph database to obtain a FEMA knowledge graph; integrating the graph database and an object-relational mapping framework into an open source framework application; accessing the graph database through the object-relational mapping framework based on the open source framework application according to a user's request; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0006] In an optional manner, the open source framework application includes: a shortest path algorithm; the target FEMA knowledge graph includes: a most direct fault cause graph; generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes: obtaining the most direct fault cause graph of the target node from the FEMA knowledge graph in the graph database based on the shortest path algorithm according to the user's request.
[0007] In an optional manner, the open source framework application includes: an association analysis algorithm; the target FEMA knowledge graph includes: a fault cause graph related to the target node; generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further including: obtaining the fault cause graph related to the target node from the FEMA knowledge graph in the graph database based on the association analysis algorithm according to the user's request.
[0008] In an optional manner, the open source framework application includes: a CRUD algorithm; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes: performing CRUD operations on the FEMA knowledge graph in the graph database based on the CRUD algorithm according to the user's request.
[0009] In an optional manner, before importing the first FEMA-related data, node model and edge model into the graph database to obtain the FEMA knowledge graph, it further includes: automatically acquiring second FEMA-related data from an external data source system; performing data cleaning on the second FEMA-related data to obtain third FEMA-related data; standardizing the third FEMA-related data to obtain fourth FEMA-related data; performing format conversion on the fourth FEMA-related data to obtain first FEMA-related data; wherein the format of the first FEMA-related data matches the storage format of the graph database.
[0010] In an optional manner, after generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, it further includes: using ECharts or D3.js to establish a knowledge graph visualization interface; obtaining the FEMA knowledge graph and / or the target FEMA knowledge graph from the graph database through the visualization interface and displaying them; wherein the FEMA knowledge graph and / or the target FEMA knowledge graph are stored in the graph database.
[0011] In an optional manner, after generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, the method further includes: orchestrating multiple containers to containerize the open source framework application.
[0012] According to the second aspect provided by the embodiment of the present application, a knowledge management system is provided, which includes: a graph generation module, which is used to import the first FEMA related data, node model and edge model into the graph database to obtain a FEMA knowledge graph; an integration module, which is used to integrate the graph database and the object relationship mapping framework into the open source framework application; an access module, which accesses the graph database through the object relationship mapping framework based on the open source framework application according to the user's request; and a graph acquisition module, which is used to generate a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0013] According to the third aspect provided by the embodiment of the present application, there is provided an electronic device, comprising: a controller; a memory for storing one or more programs, wherein when the one or more programs are executed by the controller, the controller implements the following operations of the knowledge management method: importing first FEMA related data, node model and edge model into a graph database to obtain a FEMA knowledge graph; integrating the graph database and the object-relational mapping framework into an open source framework application; accessing the graph database through the object-relational mapping framework based on the open source framework application according to a user's request; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0014] According to the third aspect provided by the embodiment of the present application, a computer-readable storage medium is provided, wherein at least one executable instruction is stored in the storage medium. When the executable instruction is executed on the knowledge management apparatus / device, the knowledge management apparatus / device performs the following operations of the knowledge management method: importing the first FEMA-related data, node model and edge model into a graph database to obtain a FEMA knowledge graph; integrating the graph database and the object-relational mapping framework into an open source framework application; accessing the graph database through the object-relational mapping framework based on the open source framework application according to a user's request; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0015] A FEMA knowledge graph is obtained by importing first FEMA related data, node models and edge models into a graph database, and the graph database and object relationship mapping framework are integrated into an open source framework application, so as to access the graph database through the object relationship mapping framework based on the open source framework application according to a user's request; a target FEMA knowledge graph is generated based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database; compared with the prior art using traditional databases, the present application uses a graph database, which can realize automatic construction of graphs for FEMA related data, node models and edge models, and can improve data processing efficiency. Moreover, through the open source framework application, the stored FEMA knowledge graph can be used for analysis according to the user's request to obtain a graph corresponding to the user's needs, which can better meet the user's needs.
[0016] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the embodiment of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present application. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:
[0018] Figure 1 A schematic diagram showing a flow chart of a first embodiment of a knowledge management method provided by the present application;
[0019] Figure 2 A schematic diagram of a FEMA knowledge graph provided by the present application is shown;
[0020] Figure 3 A schematic diagram showing a flow chart of a second embodiment of a knowledge management method provided by the present application;
[0021] Figure 4 A schematic diagram showing a structure of an embodiment of a knowledge management system provided by the present application
[0022] Figure 5 A schematic structural diagram of an embodiment of the electronic device of the present application is shown. DETAILED DESCRIPTION
[0023] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.
[0024] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0025] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0026] The term "multiple" as used in this application refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.
[0027] Figure 1 The flowchart of the first embodiment of a knowledge management method provided by the present application is shown, and the method is executed by an electronic device. Figure 1 As shown, the method comprises the following steps:
[0028] Step S110: Import the first FEMA related data, node model and edge model into the graph database to obtain a FEMA knowledge graph;
[0029] Among them, the first FEMA (Failure mode and effects analysis) related data, that is, failure related data. Specifically, the first FEMA related data can be parts information data, sensor data, historical failure records, maintenance reports, parts data provided by suppliers, problem records, problem classification and problem tracking data. Nodes usually represent entities (such as places, events, people, etc.), while edges represent the relationship between entities (such as "occurred in", "affected by", etc.). For example, the node model: defines the node type in the graph, which may include failure mode nodes, impact nodes, component nodes, risk level nodes, etc. Edge model: defines the relationship between nodes, for example, a failure mode may cause one or more effects, a component may have multiple failure modes, etc.
[0030] For example, the parts information data can be obtained by the following procedure:
[0031]
[0032] The sensor data can be obtained by the following procedure:
[0033]
[0034]
[0035] The historical fault record data can be obtained by the following procedure:
[0036] Maintenance report data can be obtained by the following procedures:
[0037] The parts data provided by the supplier can be obtained by the following procedures:
[0038] The problem record data can be obtained by the following procedures:
[0039]
[0040] The problem classification data can be obtained by the following procedure:
[0041] The problem solution data can be obtained by the following procedures:
[0042]
[0043] The issue tracking data can be obtained by the following procedures:
[0044] 1.|Question number|Tracker|Tracking time|Tracking content|Tracking result|
[0045] 2.|---------|--------|-------------------|-------------------|----------------|
[0046] 3.|001|Wang Wu|2024-05-22 10:00|Check the brake system|The brake system is normal|
[0047] 4.|002|Zhao Liu|2024-05-22 12:00|Check the ignition system|The ignition system is normal|
[0048] 5.|003|Zhang San|2024-05-22 14:00|Check the cooling effect of the air conditioner|The cooling effect of the air conditioner is normal|
[0049] Specifically, the node type and the edge model are established according to the attributes of the first FEMA-related data. By establishing the node model and the edge model, the first FEMA-related data are connected through nodes and edges, and stored in the graph database, and finally a FEMA knowledge graph is formed. It should be noted that the graph data can specifically adopt the NebulaGraph database. Figure 2 A schematic diagram of a FEMA knowledge graph provided by this application is shown, see Figure 2 As shown in the figure, circles represent nodes, and the lines between nodes represent edges.
[0050] Specifically, batch import tools such as Nebula Importer can be used to import the first FEMA related data, node models and edge models into the graph database. The import process can be implemented using the following program:
[0051] 1. Pseudo code (using ngBatis to interact with NebulaGraph):
[0052] 2. ```java
[0053] 3.@Mapper
[0054] 4.public interface FMEAMapper{
[0055] 5.@Insert("INSERT VERTEX FaultMode(name,description)VALUES{id}:{name},{description}")
[0056] 6.void insertFaultMode(@Param("id")String id,@Param("name")Stringname,@Param("description")String description); 7.
[0058] 8.@Insert("INSERT EDGE Causes(description)VALUES{from}->{to}:{description}")
[0059] 9.void insertCause(@Param("from")String from,@Param("to")String to,@Param("description")String description);
[0060] 10.}
[0061] Step S120: Integrate the graph database and object relationship mapping framework into an open source framework application;
[0062] Among them, the graph database and the object-relational mapping framework are integrated into the open source framework application, and the graph database and the open source framework application are connected through the corresponding relationship framework, so that the program in the open source framework application can process the FEMA knowledge graph data in the graph database accordingly. It should be noted that the object-relational mapping framework can specifically use ngBatis, and using ngBatis can realize the interaction between NebulaGraph and Spring Boot.
[0063] Specifically, the above integration process can be implemented by the following procedures:
[0064] 1. Dockerfile
[0065] 2.FROM openjdk:11-jre-slim
[0066] 3.COPY target / fmea-knowledge-graph.jar / app.jar
[0067] 4.ENTRYPOINT["java","-jar"," / app.jar"]
[0068] Step S130: accessing the graph database through the object relational mapping framework based on the open source framework application according to the user's request;
[0069] Among them, the user's request is obtained, for example, the request can be that the user retrieves the relevant knowledge graph of a certain component through a search window, and the open source framework application is provided with an application related to the user's request. After receiving the user's request, the open source framework application accesses the graph database through the object-relational mapping framework to obtain the graph data corresponding to the user's request. It should be noted that the open source framework application can specifically be Spring Boot.
[0070] Step S140: Generate a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0071] Among them, after receiving the user's request, the open source framework application parses the user's request and calls the program related to the user's request in the open source framework application to perform corresponding processing on the FEMA knowledge graph or obtain the corresponding FEMA knowledge graph to obtain the FEMA knowledge graph.
[0072] A FEMA knowledge graph is obtained by importing first FEMA related data, node models and edge models into a graph database, and the graph database and object relationship mapping framework are integrated into an open source framework application, so as to access the graph database through the object relationship mapping framework based on the open source framework application according to a user's request; a target FEMA knowledge graph is generated based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database; compared with the prior art using traditional databases, the present application uses a graph database, which can realize automatic construction of graphs for FEMA related data, node models and edge models, and can improve data processing efficiency. Moreover, through the open source framework application, the stored FEMA knowledge graph can be used for analysis according to the user's request to obtain a graph corresponding to the user's needs, which can better meet the user's needs.
[0073] In another embodiment of the present application, the open source framework application includes: a shortest path algorithm; the target FEMA knowledge graph includes: a most direct fault cause graph; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes:
[0074] According to the user's request, based on the shortest path algorithm, the most direct fault cause graph of the target node is obtained from the FEMA knowledge graph in the graph database.
[0075] In this embodiment, for example, when a component fails, the relevant first FEMA-related data obtained includes the most direct cause of the component, but the same graph will be generated with other matters. The most direct cause of the failure is located at a node in the same graph. When a user request is received, the most direct request is parsed to obtain the most direct cause of the failure of the component, and the shortest path algorithm is called to obtain the most direct cause of the failure of the component, i.e., the target node, from the graph database for corresponding display to indicate the most direct cause of the failure. The display in the form of a graph is more intuitive and brings a better experience to users.
[0076] Specifically, the shortest path algorithm can be implemented in the following ways:
[0077] 1. Pseudo code (intelligent analysis module):
[0078] 2. ```java
[0079]
[0080] In another embodiment of the present application, the open source framework application includes: an association analysis algorithm; the target FEMA knowledge graph includes: a fault cause graph related to the target node; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes:
[0081] According to the user's request, based on the association analysis algorithm, a fault cause graph related to the target node is obtained from the FEMA knowledge graph in the graph database.
[0082] In this embodiment, for example, when a component fails, the relevant first FEMA-related data obtained includes all relevant causes of the component, but the same graph will be generated with other matters. All the most direct relevant causes are located in multiple nodes in the same graph. When a user request is received, the most direct request is parsed to obtain the relevant cause of the failure of the component, and the association analysis algorithm is called to obtain the nodes of all relevant causes of the component, i.e., the target node, from the graph database, and obtain the relevant fault cause graph for corresponding display to indicate all relevant causes of the failure. The display in the form of a graph is more intuitive and brings a better experience to users.
[0083] In another embodiment of the present application, the open source framework application includes: a CRUD algorithm; the generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database further includes:
[0084] According to the user's request, the FEMA knowledge graph in the graph database is added, deleted, modified and checked based on the addition, deletion, modification and query algorithm.
[0085] In this embodiment, when the user's request is received and parsed to be for modifying the graph database, the FEMA knowledge graph in the graph database is added, deleted or modified according to the addition, deletion, modification and query algorithm to meet the user's needs.
[0086] Specifically, the addition, deletion, modification and query operations of the FEMA knowledge graph can be implemented through the following procedures:
[0087] 1. Pseudo code (management module):
[0088] 2. ```java
[0089] 3.@Service
[0090] 4.public class KnowledgeGraphService{
[0091] 5. @Autowired
[0092] 6.private FMEAMapper fmeaMapper; 7.
[0094] 8.public void addFaultMode(String id,String name,String description){
[0095]
[0096] Figure 3 The flowchart of the second embodiment of a knowledge management method provided by the present application is shown, and the method is executed by an electronic device. Figure 3 As shown, before importing the first FEMA related data, the node model and the edge model into the graph database to obtain the FEMA knowledge graph, the following steps are further included:
[0097] Step S210: Automatically obtain the second FEMA related data from the external data source system;
[0098] Among them, the second FEMA related data is automatically obtained from the external data source system. Compared with the prior art of manually importing each FEMA related data, this method can improve the efficiency of obtaining the second FEMA related data.
[0099] Step S220: Cleaning the second FEMA-related data to obtain third FEMA-related data;
[0100] The data cleaning specifically includes removing duplicate, erroneous and incomplete records from the second FEMA-related data to obtain the third FEMA-related data.
[0101] Step S230: Standardizing the third FEMA-related data to obtain fourth FEMA-related data;
[0102] The third FEMA-related data includes data obtained from different systems, and the formats of the data may be different. The data in different formats are unified in format and unit to obtain the fourth FEMA-related data.
[0103] Step S240: converting the format of the fourth FEMA-related data to obtain the first FEMA-related data;
[0104] The format of the first FEMA-related data matches the storage format of the atlas database. The data type of the fourth FEMA-related data is different from the data type that the atlas database can process, and the data type of the fourth FEMA-related data is converted into a data type that can be adapted to be stored and processed by the atlas database, that is, the second FEMA-related data.
[0105] The above steps S210 to S240 can be implemented by the following procedure:
[0106]
[0107]
[0108] In another embodiment of the present application, after generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further comprising:
[0109] ECharts or D3.js is used to establish a knowledge graph visualization interface; the FEMA knowledge graph and / or the target FEMA knowledge graph is obtained from the graph database through the visualization interface and displayed; wherein the FEMA knowledge graph and / or the target FEMA knowledge graph is stored in the graph database.
[0110] In this embodiment, a knowledge graph visualization interface is established through ECharts or D3.js, so that users can enter the graph database through the interface, obtain the stored FEMA knowledge graph or the generated target FEMA knowledge graph for display through the visualization interface, and can input user search requests through the visualization interface.
[0111] Specifically, the following procedures can be used to achieve this:
[0112] 1. Pseudo code (front-end display):
[0113] 2. ```javascript
[0114] 3.var chart=echarts.init(document.getElementById('main'));
[0115] 4.var option={
[0116]
[0117] In another embodiment of the present application, after generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, it further includes: orchestrating multiple containers to containerize the open source framework application.
[0118] Specifically, Docker Compose is used to orchestrate multiple containers to containerize the open source framework application, and various application programs in the open source framework are configured, such as the shortest path algorithm, the association analysis algorithm and other algorithms are configured with each other to ensure the collaborative work between services, thereby ensuring the high availability and scalability of the system.
[0119] Specifically, the above containerization process can be implemented using the following procedures:
[0120] 1. Example docker-compose.yml:
[0121] 2. ```yaml
[0122] 3.version:'3.8'
[0123] 4.services:
[0124] 5.nebula-graph:
[0125] 6.image:vesoft / nebula-graphd:latest
[0126] 7.ports:
[0127] 8.-"3699:3699"
[0128] 9.environment:
[0129] 10.USER:root
[0130] 11.PASSWORD:nebula
[0131] 12.fmea-app:
[0132] 13.build:.
[0133] 14.ports:
[0134] 15.-"8080:8080"
[0135] 16.depends_on:
[0136] 17.-nebula-graph
[0137] Figure 4 A schematic diagram of the structure of an embodiment of a knowledge management system provided by the present application is shown. Figure 4 As shown, the system 400 includes: a graph generation module 410, an integration module 420, an access module 430 and a graph acquisition module 440.
[0138] A graph generation module 410, for importing the first FEMA related data, the node model and the edge model into the graph database to obtain a FEMA knowledge graph;
[0139] Integration module 420, used to integrate the graph database and object relationship mapping framework into an open source framework application;
[0140] Access module 430, accessing the graph database through the object relational mapping framework based on the open source framework application according to the user's request;
[0141] The graph acquisition module 440 is used to generate a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0142] It should be noted that the knowledge management system provided in the above embodiment and the knowledge management method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here.
[0143] Figure 5 A schematic diagram of the structure of an embodiment of the electronic device of the present application is shown, which shows a schematic diagram of the structure of a computer system suitable for implementing the electronic device of the embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device.
[0144] See also Figure 5As shown, the electronic device includes: a controller; a memory for storing one or more programs, and when the one or more programs are executed by the controller, the above-mentioned knowledge management method is executed.
[0145] Please continue reading Figure 5 As shown, the computer system 500 of the electronic device includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 502 or the program loaded from the storage part 508 to the random access memory (RAM) 503, such as executing the method in the above embodiment. In RAM 503, various programs and data required for system operation are also stored. CPU 501, ROM 502 and RAM 503 are connected to each other through bus 504. Input / output (I / O) interface 505 is also connected to bus 504.
[0146] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.
[0147] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 509, and / or installed from a removable medium 511. When the computer program is executed by a central processing unit (CPU) 501, various functions defined in the system of the present application are executed.
[0148] Another aspect of the present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the knowledge management method described above is implemented. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.
[0149] Another aspect of the present application provides a computer program product or a computer program, which includes at least one executable instruction. When the executable instruction is executed on a knowledge management system / electronic device, the knowledge management system / electronic device executes the knowledge management method as described above.
[0150] The executable instructions may be specifically used to enable the knowledge management system / electronic device to perform the following operations:
[0151] Import the first FEMA related data, node model and edge model into the graph database to obtain the FEMA knowledge graph;
[0152] Integrate the graph database and object-relational mapping framework into an open source framework application;
[0153] Accessing the graph database through the object relational mapping framework based on the open source framework application according to a user's request;
[0154] Generate a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
[0155] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ErasableProgrammable Read Only Memory, EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as a part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0156] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0157] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0158] According to one aspect of an embodiment of the present application, a computer system is also provided, including a central processing unit (CPU), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage portion into a random access memory (RAM), such as executing the method in the above embodiment. In RAM, various programs and data required for system operation are also stored. CPU, ROM and RAM are connected to each other via a bus. An input / output (I / O) interface is also connected to the bus.
[0159] The following components are connected to the I / O interface: an input part including a keyboard, a mouse, etc.; an output part including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage part including a hard disk, etc.; and a communication part including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication part performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface as needed. Removable media, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., are installed on the drive as needed so that the computer program read therefrom is installed into the storage part as needed.
[0160] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.
Claims
1. A knowledge management method, It is characterized in that The method comprises: Import the first FEMA related data, node model and edge model into the graph database to obtain the FEMA knowledge graph; Integrate the graph database and object-relational mapping framework into an open source framework application; Accessing the graph database through the object relational mapping framework based on the open source framework application according to a user's request; Generate a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
2. The knowledge management method according to claim 1, It is characterized in that The open source framework application includes: a shortest path algorithm; the target FEMA knowledge graph includes: a most direct fault cause graph; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes: According to the user's request, based on the shortest path algorithm, the most direct fault cause graph of the target node is obtained from the FEMA knowledge graph in the graph database.
3. The knowledge management method according to claim 1, It is characterized in that The open source framework application includes: an association analysis algorithm; the target FEMA knowledge graph includes: a fault cause graph related to the target node; generating a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes: According to the user's request, based on the association analysis algorithm, a fault cause graph related to the target node is obtained from the FEMA knowledge graph in the graph database.
4. The knowledge management method according to claim 1, It is characterized in that The open source framework application includes: a CRUD algorithm; the generating of a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further includes: According to the user's request, the FEMA knowledge graph in the graph database is added, deleted, modified and checked based on the addition, deletion, modification and query algorithm.
5. The knowledge management method according to claim 1, It is characterized in that Before importing the first FEMA related data, the node model and the edge model into the graph database to obtain the FEMA knowledge graph, the method further includes: Automatically obtain the second FEMA related data from the external data source system; Cleaning the second FEMA related data to obtain third FEMA related data; Standardizing the third FEMA-related data to obtain fourth FEMA-related data; Converting the fourth FEMA-related data into a first FEMA-related data; Among them, the format of the first FEMA related data matches the storage format of the atlas database.
6. The knowledge management method according to claim 1, It is characterized in that After generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further comprising: Use ECharts or D3.js to build a knowledge graph visualization interface; Obtain the FEMA knowledge graph and / or the target FEMA knowledge graph from the graph database through the visualization interface and display them; Wherein, the FEMA knowledge graph and / or the target FEMA knowledge graph are stored in the graph database.
7. The knowledge management method according to claim 1, It is characterized in that After generating the target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database, further comprising: The open source framework is applied by orchestrating a plurality of containers.
8. A knowledge management system, It is characterized in that The system comprises: A graph generation module, used for importing the first FEMA related data, node model and edge model into the graph database to obtain a FEMA knowledge graph; An integration module, used to integrate the graph database and object-relational mapping framework into an open source framework application; An access module, which accesses the graph database through the object relational mapping framework based on the open source framework application according to a user's request; A graph acquisition module is used to generate a target FEMA knowledge graph based on the open source framework application according to the user's request and the FEMA knowledge graph in the graph database.
9. An electronic device, It is characterized in that include: Controller; The memory is used to store one or more programs. When the one or more programs are executed by the controller, the controller implements the operation of the knowledge management method described in any one of claims 1 to 7.
10. A computer-readable storage medium, It is characterized in that The storage medium stores at least one executable instruction, and when the executable instruction is executed on the knowledge management apparatus / device, the knowledge management apparatus / device executes the operation of the knowledge management method as described in any one of claims 1-7.
Citation Information
Patent Citations
Method and device for processing maintenance case by using knowledge graph and electronic device
CN110727804A
Knowledge graph construction method based on fault mode and influence analysis information
CN114169521A
Management method and device of operation and maintenance data
CN117131929A
Cited By
Power transformer winding turn-to-turn short circuit fault detection method
CN119125969A
A method for detecting short-circuit faults in power transformer windings
CN119125969B
