Ship equipment maintenance support data fusion method and device based on data map, and fault positioning method

Abstract

The invention discloses a ship equipment maintenance support data fusion method and device based on a data map and an equipment fault positioning and solving method. A ship equipment maintenance support field ontology is constructed by adopting the idea of ontology engineering; constructing a ship equipment maintenance support application ontology according to the ship equipment maintenance support field ontology, the equipment configuration and the service type; then analyzing the original data of the ship equipment maintenance support, and establishing a mapping relation between the original data and the ship equipment maintenance support domain ontology; and fusing the original data of the ship equipment maintenance support according to the mapping relation, and supporting informatization decision-making of the ship equipment maintenance support. According to the invention, various types of data in different service systems can be uniformly managed, the data redundancy is reduced, the integrity, accuracy and consistency of the data are improved, high sharing of maintenance support information and knowledge is realized, and the most timely and richer reliable information is provided for ship equipment support decisions.

Description

Technical Field

[0001] The present invention relates to the technical field of ship equipment maintenance and support data fusion, and in particular to a ship equipment maintenance and support data fusion method and device based on a data map, and a fault locating method. Background Art

[0002] In the field of large-scale ship equipment maintenance, the sources of ship equipment maintenance and support data are different. There are both structured data and a large amount of unstructured data, as well as qualitative data and quantitative data. More importantly, the structural levels, time scales and spatial spans reflected by these data are different. However, these data reflect the maintenance rules of equipment from different aspects. In addition, it is difficult to integrate these data because there are differences in application modes and structures between different technical subsystems. For example, different names may be used in different systems for the same equipment; or the same name may have completely different meanings. The software used by each subsystem is also different. Some use file systems, while others use database management systems. Different database software may be used in database management systems, and so on.

[0003] Therefore, the existing technology lacks a method for effectively integrating different types of ship equipment maintenance and support data, and is unable to ensure the integrity and consistency of the data. Summary of the invention

[0004] The present invention provides a method and device for fusing ship equipment maintenance and support data based on a data map, so as to solve or at least partially solve the technical problem that the integrity and consistency of data cannot be achieved in the prior art.

[0005] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0006] The first aspect discloses a method for integrating ship equipment maintenance and support data based on a "data map", including:

[0007] The idea of ​​ontology engineering is adopted to construct the ontology of ship equipment maintenance and support, including the concepts in the field of equipment maintenance and the semantic relations between the concepts.

[0008] According to the ontology of ship equipment maintenance and support domain, equipment configuration and business type, the ship equipment maintenance and support application ontology is constructed, including the concept of a certain type of equipment maintenance and support and the semantic relationship between the business of a certain type of equipment maintenance and support (maintenance, monitoring, evaluation, fault analysis, etc.);

[0009] Analyze the original data during the ship maintenance and support period, and establish a mapping relationship between the original data and the ontology of the ship equipment maintenance and support field;

[0010] According to the mapping relationship between the original data and the ontology of ship equipment maintenance and support, the original data during the ship maintenance and support period is fused.

[0011] In one embodiment, the ship equipment maintenance and support domain ontology includes:

[0012] Ship equipment system analysis ontology domain, used to describe equipment configuration and composition as well as corresponding semantics;

[0013] Fault analysis domain, used to describe the functions implemented by each level of equipment, possible failure modes and failure symptoms;

[0014] Reliability-centered maintenance domain, used to describe relevant information of preventive maintenance and corrective maintenance items at all levels of equipment;

[0015] Maintenance operation domain, used to describe the specific operation procedures, asset requirements and usage of each tool for preventive maintenance and corrective maintenance items at all levels of equipment;

[0016] The maintenance task planning domain is used to describe the triggering, maintenance content and time schedule of the maintenance task level.

[0017] In one implementation, a ship equipment maintenance and support application ontology is constructed based on the ship equipment maintenance and support domain ontology, equipment configuration, and business type, including:

[0018] Conduct equipment analysis in the field of ship equipment maintenance and support, determine the basic configuration of equipment objects, key equipment parts, key technical status parameters and their monitoring methods;

[0019] Conduct functional analysis and fault analysis to obtain functional knowledge and fault knowledge of equipment;

[0020] Conduct restorative work analysis to determine the equipment maintenance strategy and the maintenance system to be followed after the equipment is put into operation;

[0021] Conduct maintenance work analysis to obtain the basic steps and knowledge of various maintenance resources required for various corrective maintenance work, preventive maintenance work and related maintenance work;

[0022] Carry out maintenance level analysis and determine the ship maintenance levels including: daily maintenance, preventive maintenance, level 1 (dock repair), level 2 (minor repair), level 3 (major repair);

[0023] Conduct maintenance task management analysis to obtain maintenance task planning solutions during the actual operation of the equipment;

[0024] The various types of knowledge obtained above are integrated to construct the ship equipment maintenance and support application ontology.

[0025] In one implementation, the original data of ship equipment maintenance and support is analyzed to establish a mapping relationship between the original data and the ship equipment maintenance and support domain ontology, including:

[0026] The semantics and semantic relationship analysis of the original data during the ship equipment maintenance and support period are carried out to establish the first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology, and the second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology.

[0027] In one embodiment, semantics and semantic relationship analysis is performed on the original data during the ship equipment maintenance and support period, and a first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology and a second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology are established, including:

[0028] Analyze the semantics of the original data during the ship equipment maintenance and support period, search for concepts corresponding to the semantics of the original data from the ship equipment maintenance and support domain ontology, and use a first data structure to represent a first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology;

[0029] The semantic relationship of the original data during the ship equipment maintenance and support period is analyzed, and the semantic relationship corresponding to the semantic relationship of the original data is found from the ship equipment maintenance and support domain ontology, and a second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology is represented by a second data structure.

[0030] In one implementation, the original data of ship equipment maintenance and support is integrated according to the mapping relationship between the original data and the ship equipment maintenance and support domain ontology, including:

[0031] According to the first mapping relationship between the semantics in the original data and the concepts in the ontology of the ship equipment maintenance and support domain, a data instance node set is constructed;

[0032] According to the second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ontology of the ship equipment maintenance and support domain, a data relationship node set is constructed;

[0033] Based on the data instance node set and the data relationship node set, a data fusion graph, namely a "data map", is generated.

[0034] In one implementation, a data fusion graph, i.e., a “data map”, is generated based on a data instance node set and a data relationship node set, including:

[0035] The data instances in the data instance node set corresponding to each type of data are used as nodes, and the data relations in the data relation node set are used as edges to generate a semantic graph corresponding to the type of data;

[0036] Treat the semantic graphs corresponding to various types of data as separate layers;

[0037] The separate layers corresponding to various types of data are fused to generate a data fusion map, namely a "data map".

[0038] Based on the same inventive concept, the second aspect of the present invention provides a fault location and solution method, which is implemented based on the method for integrating ship equipment maintenance and support data based on the data map described in the first aspect. The fault location and solution method includes:

[0039] When a fault occurs, the equipment component structure corresponding to the fault phenomenon is found in the data fusion diagram, i.e., the "data map", based on the relationship between the fault phenomenon and the component structure, to locate the equipment fault, find the maintenance manual corresponding to the equipment component, and implement the equipment fault solution.

[0040] Based on the same inventive concept, the third aspect of the present invention provides a device for integrating ship equipment maintenance and support data based on a data map, comprising:

[0041] The domain ontology construction module is used to construct the domain ontology of ship equipment maintenance and support by adopting the idea of ​​ontology engineering, including the concepts in the field of equipment maintenance and the semantic relations between the concepts;

[0042] The application ontology construction module is used to construct the ship equipment maintenance and support application ontology according to the ship equipment maintenance and support domain ontology, equipment configuration and business type, including the concept of a certain type of equipment maintenance and support and the semantic relationship between the business of a certain type of equipment maintenance and support;

[0043] The mapping relationship building module is used to analyze the original data during the ship maintenance and support period and establish the mapping relationship between the original data and the ship equipment maintenance and support domain ontology and application ontology;

[0044] The data fusion module is used to fuse the original data during the ship maintenance and support period according to the maintenance and support business needs based on the mapping relationship between the original data and the ontology and application in the field of ship equipment maintenance and support.

[0045] Based on the same inventive concept, the fourth aspect of the present invention provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method for extracting unstructured information of ship equipment maintenance and support based on a data map as described in the first aspect is implemented.

[0046] Based on the same inventive concept, the fifth aspect of the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method for extracting unstructured information of ship equipment maintenance and support based on a data map as described in the first aspect is implemented.

[0047] Compared with the prior art, the advantages and beneficial technical effects of the present invention are as follows:

[0048] The present invention discloses a method for fusing ship equipment maintenance and support data based on a data map. First, the idea of ​​ontology engineering is adopted to construct a ship equipment maintenance and support domain ontology. Then, a ship equipment maintenance and support application ontology is constructed according to the ship equipment maintenance and support domain ontology, equipment configuration and business type. Then, the original data of ship equipment maintenance and support is analyzed to establish a mapping relationship between the original data and the ship equipment maintenance and support domain ontology. Finally, according to the mapping relationship between the original data and the ship equipment maintenance and support domain ontology, the original data of ship equipment maintenance and support is fused. Through the method of the present invention, a domain ontology is constructed, covering the equipment maintenance field and concepts and relationships related to specific ship model configurations and maintenance support systems; an application ontology is constructed to reflect some concepts of consensus on maintenance and support of a certain profession or type of equipment. The ontology is within the framework of the maintenance domain ontology and is attached to specific equipment and maintenance objects at the same time; and through the mapping relationship between the established original data and the ship equipment maintenance and support domain ontology, different types of original data can be merged, and large-scale equipment maintenance and support data can be given a unified semantics to eliminate ambiguity and format differences. Various types of data in different business systems can be managed in a unified manner, data redundancy can be reduced, data integrity, accuracy and consistency can be improved, and a high degree of information sharing can be achieved, so that the information system can give full play to the maximum advantage of rich data resources and provide the most timely and abundant reliable information for ship equipment support decision-making. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0050] Figure 1 A hierarchical structure diagram of the ontology and data instances in an embodiment of the present invention;

[0051] Figure 2 A schematic diagram of a ship equipment maintenance and support domain ontology constructed in an embodiment of the present invention;

[0052] Figure 3 A flowchart of constructing a ship equipment maintenance and support application ontology in an embodiment of the present invention;

[0053] Figure 4 This is a basic composition diagram of ship system maintenance and support structured data in an embodiment of the present invention;

[0054] Figure 5 This is a flow chart of data fusion conversion in an embodiment of the present invention;

[0055] Figure 6 This is a hierarchical relationship diagram of a certain type of diesel engine structure in an embodiment of the present invention;

[0056] Figure 7 A semantic graph for checking before use in an embodiment of the present invention;

[0057] Figure 8 This is the overall effect of semantic data fusion of a certain type of diesel engine in an embodiment of the present invention. DETAILED DESCRIPTION

[0058] The purpose of the present invention is to integrate the data of the entire life cycle of ship equipment, unify the management of various types of data in different business systems, reduce data redundancy, improve data integrity, accuracy and consistency, realize high-level information sharing, enable the information system to give full play to the maximum advantage of rich data resources, and provide the most timely and abundant reliable information for ship equipment support decision-making.

[0059] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0060] Embodiment 1

[0061] The present invention discloses a method for integrating ship equipment maintenance and support data based on a data map, comprising:

[0062] S1: Adopt the idea of ​​ontology engineering to construct the ontology of ship equipment maintenance and support, including the concepts in the field of equipment maintenance and the semantic relations between the concepts;

[0063] S2: Construct the ship equipment maintenance and support application ontology according to the ship equipment maintenance and support domain ontology, equipment configuration and business type, including the concept of a certain type of equipment maintenance and support and the semantic relationship between the concepts of a certain type of equipment maintenance and support;

[0064] S3: Analyze the original data of ship equipment maintenance and support, and establish a mapping relationship between the original data and the ontology of ship equipment maintenance and support;

[0065] S4: Based on the mapping relationship between the original data and the ontology of the ship equipment maintenance and support field, the original data of ship equipment maintenance and support are integrated.

[0066] See also Figure 1 , is a hierarchical structure diagram of the ontology and data instance in the embodiment of the present invention. In the figure, "0.05" is specific maintenance and support data, and its data (semantics) is the man-hours consumed by "determining the fault location", and the semantics of "determining the fault location" is "maintenance operation procedure". It can be seen that the ship equipment maintenance and support data is meaningless without the semantics of the data, and the data semantics are hierarchical.

[0067] By studying and analyzing the semantic hierarchical relationship above, we can find that the top-level semantics actually corresponds to some concepts and terms that are unique to the field of ship equipment maintenance and support. These concepts and terms are irrelevant to specific equipment configurations and businesses and can be called domain ontology. The second-level semantics has a direct correspondence with specific data. This part of the semantic concepts is related to specific equipment configurations and businesses and is called application ontology.

[0068] Through Figure 1 By analyzing the support data and its semantic model shown in the figure, it can be found that the domain ontology and application ontology of equipment maintenance support are essentially static. Once the equipment design is finalized, it is difficult to undergo major changes. In other words, this part of semantic data usually comes from the design and finalization stage of the equipment. Actual maintenance data such as "0.05" is dynamic data generated during the equipment maintenance support tasks and business processing. Therefore, according to the above model, the fusion of equipment maintenance support data is essentially to establish the necessary connection between dynamic data and static data. In other words, it is to mark the actual maintenance data one by one and insert semantic tags. It can also be understood as depicting dynamic data one by one on the framework formed by semantic data. In the end, the results of the two are consistent, that is, to form a data network with clear semantics and mutual consistency.

[0069] The above process is similar to the geographic information system (GIS) and the mapping operation performed thereon. The semantic data of ship equipment maintenance constitutes the basic geographic information of the geographic information system, and the dynamic maintenance data is equivalent to various information tags on different layers of GIS. Therefore, the method of GIS information fusion can be used to achieve the integration and fusion of maintenance support information. The present invention calls this "map" a "data map".

[0070] In summary, the entire technical route can be summarized as follows:

[0071] The first step is to construct the ontology of ship equipment maintenance and support. The idea of ​​"ontology engineering" proposed by information and knowledge processing technology in recent years is adopted to construct the semantic data of ship equipment maintenance and support, including some concepts and terms related to the equipment maintenance field and specific ship models and configurations as well as the maintenance and support system.

[0072] The second step is to construct the ship equipment maintenance and support application ontology. The ship equipment maintenance and support application ontology reflects some common concepts of maintenance and support for a certain profession or type of equipment. This ontology is within the framework of the maintenance field ontology and is attached to specific equipment and maintenance objects.

[0073] The third step is to propose a method for extracting, converting and fusing heterogeneous data attributes. Ship equipment maintenance and support data are scattered in a variety of documents such as equipment technical manuals, maintenance process cards, equipment management information systems, resume cards, maintenance work records, etc. In order to fuse these maintenance and support data from different sources, it is necessary to propose corresponding data conversion methods for business systems established with different technologies, application modes, and database structures.

[0074] In one embodiment, the ship equipment maintenance and support domain ontology includes:

[0075] Ship equipment system analysis ontology domain, used to describe equipment configuration and composition as well as corresponding semantics;

[0076] Fault analysis domain, used to describe the functions implemented by each level of equipment, possible failure modes and failure symptoms;

[0077] Reliability-centered maintenance domain, used to describe relevant information of preventive maintenance and corrective maintenance items at all levels of equipment;

[0078] Maintenance operation domain, used to describe the specific operation procedures, asset requirements and usage of each tool for preventive maintenance and corrective maintenance items at all levels of equipment;

[0079] The maintenance task planning domain is used to describe the triggering, maintenance content and time schedule of the maintenance task level.

[0080] Specifically, the ontology (semantic data) of the ship equipment maintenance and support domain contains some concepts and terms related to the equipment maintenance field and the configuration and maintenance support system of specific equipment models. To construct these data, this implementation adopts the idea of ​​"ontology engineering". The so-called ontology is a clear formal specification of a shared concept model, which is mainly composed of elements such as concept sets, concept attribute sets, concept relationship sets, case sets and axioms. The key to constructing a domain ontology is to identify domain concepts, clarify the relationship between concepts, generate unambiguous natural language definitions, and specify terms to identify these concepts and relationships. In order to strive for the integrity of the conceptual system, the ontology construction methods are different for different fields. At present, there is no complete set of standards to standardize the construction of all ontology models. After conducting a large amount of ship equipment maintenance and support work and comprehensive collation of knowledge, this implementation proposes an ontology model for the ship equipment maintenance and support field, such as Figure 2 shown.

[0081] The following ontology domains are included:

[0082] (1) Ship equipment system analysis ontology domain. It mainly describes the equipment configuration and composition and its related semantics, including the hierarchical relationship between equipment (Equipment), subsystems and components, the standard technical status (Condition) and parameters of each level of equipment, and the status monitoring (detection) methods and sensors (Sensor) of each level.

[0083] (2) Failure analysis domain. It mainly describes the functions (Function) implemented by each level of equipment, possible failure modes (Failure), and failure symptoms (Failure Symptom) and their semantic relationships.

[0084] (3) Reliability-centered maintenance (RCM) domain. This domain mainly describes the relevant information and semantics of preventive maintenance and corrective maintenance items at all levels of equipment, such as maintenance, routine inspection, and periodic replacement maintenance. It also includes information such as maintenance level and related semantics.

[0085] (4) Maintenance operation domain. It mainly describes the specific operation procedures of preventive maintenance and corrective maintenance items at all levels of equipment, as well as the asset requirements and usage of each tool and other information and related semantics.

[0086] (5) Maintenance task planning domain. Mainly describes the information such as maintenance task triggering and time scheduling and related semantics.

[0087] In one implementation, a ship equipment maintenance and support application ontology is constructed based on the ship equipment maintenance and support domain ontology, equipment configuration, and business type, including:

[0088] Conduct equipment analysis in the field of ship equipment maintenance and support, determine the basic configuration of equipment objects, key equipment parts, key technical status parameters and their monitoring methods;

[0089] Conduct functional analysis and fault analysis to obtain functional knowledge and fault knowledge of equipment;

[0090] Conduct restorative work analysis to determine the equipment maintenance strategy and the maintenance system to be followed after the equipment is put into operation;

[0091] Conduct maintenance work analysis to obtain the basic steps and knowledge of various maintenance resources required for various corrective maintenance work, preventive maintenance work and related maintenance work;

[0092] Carry out maintenance level analysis and determine the ship maintenance levels including: daily maintenance, preventive maintenance, level 1 (dock repair), level 2 (minor repair), level 3 (major repair);

[0093] Conduct maintenance task management analysis to obtain maintenance task planning solutions during the actual operation of the equipment;

[0094] The various types of knowledge obtained above are integrated to construct the ship equipment maintenance and support application ontology.

[0095] Specifically, the maintenance support application ontology reflects some common concepts of maintenance support for a certain profession or type of equipment. This ontology is within the framework of the maintenance field ontology and is attached to specific equipment and maintenance objects.

[0096] This implementation adopts the maintenance engineering analysis method to construct the maintenance application ontology. The specific construction process is as follows: Figure 3 shown.

[0097] The main process includes the following:

[0098] (1) Equipment analysis. The purpose of equipment analysis is to determine the basic configuration of the equipment object, key parts of the equipment, key technical status parameters and their monitoring methods. The ontology knowledge is generally carried out from top to bottom according to the physical structure of the equipment object, generally starting from the system level and decomposing step by step to the level where fault location, replacement of key parts, repair or adjustment can be performed. Equipment analysis can be carried out with reference to the structure of the equipment itself, but it does not need to be decomposed to the lowest level, only to replaceable parts or standard parts.

[0099] (2) Fault analysis. The purpose of fault analysis is to obtain knowledge about equipment faults. It includes two basic processes. The first is functional analysis, which clarifies the functions performed by each subsystem and component of the equipment and the cause-and-effect relationship between the functions. This can be done from top to bottom in conjunction with the equipment analysis process. Functional knowledge is knowledge determined by the characteristics of the equipment itself. It is static and generally does not need to be collected. However, functional knowledge is a bridge to communicate other knowledge, especially fault knowledge, and must also be considered when constructing the application ontology. The second is fault analysis, which is used to obtain knowledge about possible equipment faults, including fault phenomena and fault impacts. Fault analysis is generally performed after the functional analysis is completed, and the FMEA (failure mode and effects analysis) method can be used.

[0100] (3) Restorative work and RCM (reliability-centered maintenance) analysis. The purpose is to determine the maintenance strategy of the equipment and the maintenance system to be followed after the equipment is put into operation, so as to take appropriate repair or preventive measures for the failure. This can be carried out according to the basic process of RCM analysis.

[0101] (4) Maintenance work analysis. The purpose of maintenance work analysis is to obtain knowledge about the basic steps of various corrective maintenance work, preventive maintenance work and related maintenance work, as well as the required maintenance resources. This can be done by referring to the basic process of MTA (Maintenance Task Analysis and Action) analysis.

[0102] (5) Maintenance level analysis. Maintenance level analysis is used to determine the work content and occasions of each maintenance level. It can be determined based on the depth and scope of equipment maintenance and the actual operation management situation. This is different from the maintenance system's division of grassroots maintenance, relay maintenance, and base maintenance.

[0103] (6) Maintenance task management analysis. The construction of the application ontology is directly related to specific maintenance tasks, and it is essential to analyze the management methods of maintenance tasks. Maintenance task management analysis is mainly used to obtain knowledge such as maintenance task planning during the actual operation of equipment.

[0104] (7) Ontology knowledge fusion. Acquiring equipment maintenance application ontology knowledge requires the participation of different personnel. In order to overcome the possible differences in terms used when constructing the ontology, a synonym dictionary needs to be constructed to integrate the ontology knowledge.

[0105] In one implementation, the original data during the ship equipment maintenance and support period is analyzed to establish a mapping relationship between the original data and the ship equipment maintenance and support domain ontology, including:

[0106] The semantics and semantic relationship analysis of the original data during the ship equipment maintenance and support period are carried out to establish the first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology, and the second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology.

[0107] In one embodiment, semantics and semantic relationship analysis is performed on the original data during the ship equipment maintenance and support period, and a first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology and a second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology are established, including:

[0108] Analyze the semantics of the original data during the ship equipment maintenance and support period, search for concepts corresponding to the semantics of the original data from the ship equipment maintenance and support domain ontology, and use a first data structure to represent a first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology;

[0109] The semantic relationship of the original data during the ship equipment maintenance and support period is analyzed, and the semantic relationship corresponding to the semantic relationship of the original data is found from the ship equipment maintenance and support domain ontology, and a second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology is represented by a second data structure.

[0110] Specifically, Figure 4 Taking the diagram of the basic structure of the ship system maintenance and support structured data in the 2013 Shipbuilding Industry Corporation as an example, the structured data described in the form of a table also contains relatively clear semantics and semantic relationship information. Usually, the header describes the semantic information of the data, while the encoding information indicates the semantic relationship information between the data.

[0111] The structure of data fusion is represented by the maintenance support data fusion data graph, which is usually a typical graph structure composed of "nodes" and "edges". Each node corresponds to a data instance, and the "edge" corresponds to the semantic relationship between data instances. In principle, a node can be uniquely identified by an ID code and descriptive information "Label", but if this method is used to describe equipment support data, it is easy to lose the semantics and other information defined in the header. In order to maintain this information, each node in the data fusion graph is defined as the following data structure:

[0112] Node{Id, Label, Class, supplementary information i, ...}

[0113] Id is the node number, and the original data source number can usually be retained. In the case of multiple data sources, unified encoding is required and then encoding mapping is performed. Label is the node name, retaining the original data instance, and Class is the data type, corresponding to Figure 2 The ship equipment maintenance and support domain ontology shown needs to semantically annotate the data and supplement the information according to the data instance situation to retain the original data table information.

[0114] In addition to node information, another important aspect of data fusion transformation is the edges of the graph, that is, the semantic relationship between data needs to be determined. Figure 2 From the given domain ontology, we can see that the semantic relationship between data entities has been clarified, that is, the type of edge between data instance nodes has been determined. The specific conversion work is to establish a corresponding relationship between different instance nodes and mark them as corresponding semantic types.

[0115] In one implementation, the original data during the ship equipment maintenance and support period is fused according to the mapping relationship between the original data and the ship equipment maintenance and support domain ontology, including:

[0116] According to the first mapping relationship between the semantics in the original data and the concepts in the ontology of the ship equipment maintenance and support domain, a data instance node set is constructed;

[0117] According to the second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ontology of the ship equipment maintenance and support domain, a data relationship node set is constructed;

[0118] Based on the data instance node set and the data relationship node set, a data fusion graph, namely a "data map", is generated.

[0119] See also Figure 5 The figure is a flow chart of data fusion transformation in an embodiment of the present invention.

[0120] In one implementation, generating a data fusion graph based on a data instance node set and a data relationship node set includes:

[0121] The data instances in the data instance node set corresponding to each type of data are used as nodes, and the data relations in the data relation node set are used as edges to generate a semantic graph corresponding to the type of data;

[0122] Treat the semantic graphs corresponding to various types of data as separate layers;

[0123] The separate layers corresponding to various types of data are fused to generate a data fusion map, namely a "data map".

[0124] Specifically, ship equipment maintenance and support data are scattered in various documents such as equipment technical manuals, maintenance process cards, equipment management information systems, resume cards, maintenance work records, etc.

[0125] The following is a specific example of integrating the maintenance and support data of a certain type of diesel engine oil equipment.

[0126] This implementation method uses a certain type of marine diesel engine as the object for verification test, integrating three types of data: one is the diesel engine structure data; the second is the diesel engine pre-use inspection process card data; the third is the inspection record data. For the convenience of description, only part of the data is listed, and detailed data can be found in the maintenance manual of this type of equipment. Among them, Table 1 is a part of the equipment composition table of a certain type of diesel engine; Table 2 is a part of the diesel engine pre-use inspection process card, and Table 3 is the pre-use inspection fault record table. When the equipment was inspected before use, two faults, leakage and looseness, were found.

[0127] Table 1 Structure of a certain type of diesel engine (partial)

[0128]

[0129]

[0130] Referring to Table 1, a semantic graph corresponding to this type of data can be generated, specifically a configuration hierarchy graph of a certain type of diesel engine, such as Figure 6 As shown in the figure, the hierarchy between a certain type of diesel engine configuration constitutes semantics, where circles are nodes, representing various concepts (such as parts) of a certain type of diesel engine configuration, and edges are semantic relationships between concepts, which can effectively express the aggregation and dependency relationship of different parts of the equipment.

[0131] Table 2 Preparation and inspection before using diesel engine (partial)

[0132]

[0133]

[0134] Similarly, the data in Table 2 can be converted into a semantic graph, such as Figure 7 As shown in the figure, the red nodes represent diesel engines, the green nodes represent repair steps and processes, and the purple nodes represent mechanical majors and reducer debugging. Nodes and edges can be flexibly defined according to the content of Table 2 and distinguished by layers.

[0135] Table 3 Fault record table for inspection before use

[0136]

[0137] Specifically, by observing the original data, it can be found that the "Name" field in Table 1 describes the subsystems of a certain type of diesel engine at each level and their corresponding components, corresponding to the description of Figure 2 Therefore, the first mapping relationship between the semantics in the original data and the concepts in the ontology of the ship equipment maintenance and support field is established, that is, the mapping relationship between the "name" field and Equipment, specifically:

[0138] "Name"{Data Instance}→Node{Label"Data Instance", Class"Equipment"}

[0139] Keeping other information in the data table, we can construct the node list of Table 4:

[0140] Table 4 Diesel engine structure node list

[0141] Id Label Figure No. Remark Class 00 TBD diesel engine Equipment 01 Body 01 Equipment 0101 Cylinder head See 01 Equipment 0102 Strong studs (for cylinder heads) See 01 Equipment

[0142] The composition codes in Table 2 represent the semantics of the configuration relationships at each level of the diesel engine. By observing the rules, we can find that the highest two digits of the code represent the subsystems of the diesel engine, and the following two digits represent the lower-level components or subsystems, and so on. Figure 2 The domain ontology shown describes the "hasSubsystem" semantics of equipment construction, and can construct a second mapping relationship between the semantic relationship in the data in Table 2 and the semantic relationship in the ship equipment maintenance and support domain ontology, as follows:

[0143] id

id1****

[0144] Using the above mapping relationship, a semantic relationship table shown in Table 5 can be formed.

[0145] Table 5 Diesel engine structure semantic relationship table

[0146]

[0147]

[0148] In Table 5, “Source” and “Target” represent the constructed hierarchical relationship, the corresponding data are the component and subsystem IDs of the diesel engine, Class corresponds to the semantics in the domain ontology, and Weight is the artificially set weight representing the relationship hierarchy.

[0149] According to the above method, the result after fusing the three types of data is as follows: Figure 8As shown (the result of merging the three tables (Tables 1, 2 and 3) of diesel engine structure, etc., and removing the labels). It can be seen that the display of data has a more intuitive form. After being integrated into this intuitive form, the above maintenance and support data can be mined using relational databases and graph databases to form their own subject databases. Various algorithms are used to extract and generate various maintenance and support decision indicator data, and the method of the present invention is used for iteration again, thereby providing data support for intelligent decision-making applications, such as maintenance operation guidance for various equipment failures, intelligent question and answer, and technical status evaluation during equipment management and use.

[0150] In general, the present invention proposes a data fusion method for equipment maintenance and support based on "data map" around the maintenance and support information of the entire life cycle of ship equipment, covering five ontological domains, namely system analysis, status monitoring, fault analysis, preventive maintenance (RCM) analysis domain, maintenance work analysis and maintenance operation domain, to achieve effective fusion of the inherent configuration information of the equipment system and the dynamic information recorded and managed by each business system, and support the fusion and integration of maintenance and support data from more than three sources. Fusion test cases show that this method can express the rich semantics between data in a graphical way, laying a good foundation for the analysis of equipment maintenance and support decision-making data.

[0151] Embodiment 2

[0152] Based on the same inventive concept, this embodiment discloses a fault location method, which is implemented based on the method for integrating ship equipment maintenance and support data described in Embodiment 1. The fault location method includes:

[0153] When a fault occurs, the component structure corresponding to the fault phenomenon is searched in the data fusion diagram according to the relationship between the fault phenomenon and the component structure to locate the fault.

[0154] Specifically, a map base point is formed according to the structural hierarchy of a component, and then the maintenance method, process and fault phenomenon are superimposed on the map base point to form a data fusion diagram, namely the "data map". When a fault occurs, the faulty component is judged according to the structural hierarchy of the "data map" to find the corresponding solution.

[0155] In the specific implementation process, if it is a diesel engine, a map base point (base layer) is formed according to the structure of the diesel engine, and then a fault layer and a layer of the maintenance method corresponding to the fault are superimposed on this basis, so as to obtain a data map of the diesel engine. When a fault occurs, the fault component is determined according to the data map to achieve fault location. Furthermore, the corresponding maintenance method can be further found as a solution according to the fault component.

[0156] For example, for a diesel engine data map, when a leakage occurs, the faulty component is found to be a strong bolt based on the leakage phenomenon, and then a solution is formed based on the repair method of the leakage phenomenon corresponding to the strong bolt.

[0157] By constructing a data map, the component's structural information, fault phenomenon, maintenance method, process, etc. are integrated together, making it easier to locate the fault and search for and find corresponding solutions.

[0158] Embodiment 3

[0159] Based on the same inventive concept, this embodiment discloses a device for fusing ship equipment maintenance and support data based on a data map, comprising:

[0160] The domain ontology construction module is used to construct the domain ontology of ship equipment maintenance and support by adopting the idea of ​​ontology engineering, including the concepts in the field of equipment maintenance and the semantic relations between the concepts;

[0161] The application ontology construction module is used to construct the ship equipment maintenance and support application ontology according to the ship equipment maintenance and support domain ontology, equipment configuration and business type, including the concept of a certain type of equipment maintenance and support and the semantic relationship between the concepts of a certain type of equipment maintenance and support;

[0162] The mapping relationship building module is used to analyze the original data of ship equipment maintenance and support and establish the mapping relationship between the original data and the ontology of the ship equipment maintenance and support field;

[0163] The data fusion module is used to fuse the original data of ship equipment maintenance and support according to the mapping relationship between the original data and the ontology of the ship equipment maintenance and support field.

[0164] Since the device introduced in the third embodiment of the present invention is a device used to implement the method for extracting unstructured information of ship equipment maintenance and support in the first embodiment of the present invention, based on the method introduced in the first embodiment of the present invention, the person skilled in the art can understand the specific structure and deformation of the device, so it is not repeated here. All devices used in the method in the first embodiment of the present invention belong to the scope of protection of the present invention.

[0165] Embodiment 4

[0166] Based on the same inventive concept, the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed, the method described in the first embodiment is implemented.

[0167] Since the computer-readable storage medium introduced in the fourth embodiment of the present invention is the computer-readable storage medium used to implement the method for extracting unstructured information of ship equipment maintenance and support based on data maps in the first embodiment of the present invention, based on the method introduced in the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the computer-readable storage medium, so it is not repeated here. All computer-readable storage media used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0168] Embodiment 5

[0169] Based on the same inventive concept, the present application also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the method in Embodiment 1 is implemented when the processor executes the above program.

[0170] Since the computer device introduced in the fifth embodiment of the present invention is a computer device used to implement the method for extracting unstructured information of ship equipment maintenance and support based on data maps in the first embodiment of the present invention, based on the method introduced in the first embodiment of the present invention, the person skilled in the art can understand the specific structure and deformation of the computer device, so it is not repeated here. All computer devices used in the method in the first embodiment of the present invention belong to the scope of protection of the present invention.

[0171] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0172] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0173] Although preferred embodiments of the present invention have been described, additional changes and modifications may be made to these embodiments by those skilled in the art once the basic creative concepts are known. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present invention. Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present invention without departing from the spirit and scope of the embodiments of the present invention. Thus, if these modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for integrating ship equipment maintenance and support data based on data maps, characterized in that: include: The idea of ​​ontology engineering is adopted to construct the ontology of ship equipment maintenance and support, including the concepts in the field of equipment maintenance and the semantic relations between the concepts. According to the ontology of ship equipment maintenance and support domain, equipment configuration and business type, the ship equipment maintenance and support application ontology is constructed, including the concept of a certain type of equipment maintenance and support and the semantic relationship between the concepts of a certain type of equipment maintenance and support; Analyze the original data during the ship equipment maintenance and support period, and establish a mapping relationship between the original data and the ship equipment maintenance and support domain ontology; According to the mapping relationship between the original data and the ontology of ship equipment maintenance and support, the original data of ship equipment maintenance and support are fused.

2. The method for integrating ship equipment maintenance and support data based on data maps according to claim 1, characterized in that: The ship equipment maintenance and support application ontology is constructed according to the ship equipment maintenance and support domain ontology, equipment configuration and business type, including: Conduct equipment analysis in the field of ship equipment maintenance and support, determine the basic configuration of equipment objects, key equipment parts, key technical status parameters and their monitoring methods; Conduct functional analysis and fault analysis to obtain functional knowledge and fault knowledge of equipment; Conduct restorative work analysis to determine the equipment maintenance strategy and the maintenance system to be followed after the equipment is put into operation; Conduct maintenance work analysis to obtain the basic steps and knowledge of various maintenance resources required for various corrective maintenance work, preventive maintenance work and related maintenance work; Conduct maintenance level analysis and determine the ship maintenance levels including: daily maintenance, preventive maintenance, level 1, level 2, and level 3; Conduct maintenance task management analysis to obtain maintenance task planning solutions during the actual operation of the equipment; The various types of knowledge obtained above are integrated to construct the ship equipment maintenance and support application ontology.

3. The method for integrating ship equipment maintenance and support data based on data maps according to claim 1, characterized in that: Analyze the original data during the ship equipment maintenance and support period, and establish a mapping relationship between the original data and the ship equipment maintenance and support domain ontology, including: The semantics and semantic relationship analysis of the original data during the ship equipment maintenance and support period are carried out to establish the first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology, and the second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology.

4. The method for integrating ship equipment maintenance and support data based on data maps according to claim 2, characterized in that: Perform semantic and semantic relationship analysis on the original data, establish a first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology, and a second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology, including: Analyze the semantics of the original data during the ship equipment maintenance and support period, search for concepts corresponding to the semantics of the original data from the ship equipment maintenance and support domain ontology, and use a first data structure to represent a first mapping relationship between the semantics in the original data and the concepts in the ship equipment maintenance and support domain ontology; The semantic relationship of the original data during the ship equipment maintenance and support period is analyzed, and the semantic relationship corresponding to the semantic relationship of the original data is found from the ship equipment maintenance and support domain ontology, and a second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ship equipment maintenance and support domain ontology is represented by a second data structure.

5. The method for integrating ship equipment maintenance and support data based on data maps according to claim 3, characterized in that: According to the mapping relationship between the original data and the ontology of the ship equipment maintenance and support field, the original data during the ship equipment maintenance and support period is integrated, including: According to the first mapping relationship between the semantics in the original data and the concepts in the ontology of the ship equipment maintenance and support domain, a data instance node set is constructed; According to the second mapping relationship between the semantic relationship in the original data and the semantic relationship in the ontology of the ship equipment maintenance and support domain, a data relationship node set is constructed; Based on the data instance node set and the data relationship node set, a data fusion graph, namely a data map, is generated.

6. The method for integrating ship equipment maintenance and support data based on data maps according to claim 5, characterized in that: Based on the data instance node set and the data relationship node set, a data fusion graph is generated, including: The data instances in the data instance node set corresponding to each type of data are used as nodes, and the data relations in the data relation node set are used as edges to generate a semantic graph corresponding to the type of data; Treat the semantic graphs corresponding to various types of data as separate layers; The separate layers corresponding to various types of data are fused to generate a data fusion map, that is, a data map.

7. A fault location method, characterized in that: Based on the method for integrating ship equipment maintenance and support data based on the data map according to claim 6, the fault location method includes: When a fault occurs, the equipment component structure corresponding to the fault phenomenon is searched in the data map according to the relationship between the fault phenomenon and the component structure, the equipment fault is located, the maintenance manual corresponding to the equipment component is searched, and the equipment fault solution is implemented.

8. A device for integrating ship equipment maintenance and support data based on a data map, characterized in that: include: The domain ontology construction module is used to construct the domain ontology of ship equipment maintenance and support by adopting the idea of ​​ontology engineering, including the concepts in the field of equipment maintenance and the semantic relations between the concepts; The application ontology construction module is used to construct the ship equipment maintenance and support application ontology according to the ship equipment maintenance and support domain ontology, equipment configuration and business type, including the concept of a certain type of equipment maintenance and support and the semantic relationship between the business of a certain type of equipment maintenance and support; The mapping relationship building module is used to analyze the original data during the ship maintenance and support period and establish the mapping relationship between the original data and the ship equipment maintenance and support domain ontology and application ontology; The data fusion module is used to fuse the original data during the ship maintenance and support period according to the maintenance and support business needs based on the mapping relationship between the original data and the ontology and application in the field of ship equipment maintenance and support.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method for fusing ship equipment maintenance and support data based on a data map as described in any one of claims 1 to 7 is implemented.

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, the method for fusing ship equipment maintenance and support data based on a data map as described in any one of claims 1 to 7 is implemented.

Images