Ship technical state data management method and device, equipment and storage medium

Abstract

The invention relates to a ship technical state data management method and device, equipment and a storage medium. By adopting the method and the device, the multi-source ship technical state data can be directly bound with each level node by refining the ship configuration structure tree, penetrating query is realized by relying on the flattened index, and meanwhile, the multi-dimensional data is automatically pushed through the association rule, so that the method and the device can be directly used for precise management and control, efficient retrieval and cross-field data linkage verification of the technical state, and the efficiency and the reliability of the system are improved. And the ship technical state knowledge graph is constructed by extracting the ship technical state data of the ship core equipment and the nodes corresponding to the core equipment, so that the problem of fragmentation of traditional process data is solved.

Description

Technical Field

[0001] This application relates to the field of ship technology, and in particular to a method, apparatus, equipment and storage medium for managing ship technical status data. Background Technology

[0002] As complex large-scale equipment, ships involve multiple stages throughout their lifecycle, including ship design, equipment procurement, construction, maintenance, and modification, generating massive amounts of technical status data. This data includes ship design parameters, equipment development documents, maintenance records, lifecycle wear and tear data, and repair regulations and standards. This technical status data is the core foundation for comprehensive ship support, visualized resource scheduling, and simulation evaluation, and its management efficiency directly impacts the ship's operational and maintenance level. Currently, the solution for managing ship technical status data relies on existing equipment quality supervision information system platforms, using process module control and phased data classification and storage methods to achieve basic control over technical status data. Summary of the Invention

[0003] Based on this, a method, apparatus, equipment, and storage medium for managing ship technical status data are provided to solve the technical problems of current ship technical status data management methods, which do not consider the correlation of cross-stage data, are limited by the storage logic of module splitting, require switching between different functional modules for data retrieval, cannot automatically link multi-source related data, and are difficult to assess the integrity of technical status data.

[0004] On the one hand, a method for managing ship technical status data is provided, the method comprising: Collect and classify ship technical condition data; Construct a ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; The basic data on ship type development and equipment development in the ship technical status data are associated with the corresponding hierarchical nodes to generate an initial ship configuration structure tree. The initial ship configuration structure tree is flattened and a node index table is generated; The system iterates through each node according to the node index table, obtains the ship technical status data associated with each node, performs data cleaning and standardization, extracts the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and constructs a ship technical status knowledge graph.

[0005] In one embodiment, the collection and classification of ship technical condition data includes: Collect ship technical status data, which includes ship type development data, equipment development data, ship maintenance data, ship full life cycle technical status data, equipment supplier information, repair regulation information, repair standard information, and quality system information; The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

[0006] In one embodiment, constructing the ship configuration structure tree, which involves setting up the nodes at each level of the ship configuration structure tree according to the ownership relationships of equipment within the ship, includes: The data associated with each level is determined according to the type of the ship technical status data classification. The ship as a whole is taken as the root node. The nodes of each level of the ship configuration structure tree are set according to the equipment affiliation relationship of "ship as a whole-system-subsystem-equipment". The attributes of each level node are defined according to the equipment information. The equipment information includes system parameters and equipment models in the ship type development data. The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

[0007] In one embodiment, acquiring the ship technical status data associated with each node includes: Obtain the type of the ship's technical condition data classification; When receiving data classified as unstructured documents, the data is categorized according to "document type - generation time". At the same time, document keywords are extracted to build a retrieval index library. The documents are then encrypted and stored, and the stored documents are associated with the retrieval index library. When receiving data classified as structured relational data, the entities and relationships in the structured relational data are extracted and converted into triple data in the form of "subject-predicate-object". The relational database data containing the generated triple data is virtualized into RDF format. The milliohm names in the ship milliohm table are mapped to RDF predicates and the table values ​​are mapped to RDF objects to form RDF format linked data.

[0008] In one embodiment, the method further includes: Query or modify access permissions are assigned to the stored documents and RDF format linked data according to user roles, and user operation logs of the stored documents and RDF format linked data are recorded. Incremental backups and full backups of the stored documents and RDF format linked data are performed regularly.

[0009] In one embodiment, the method further includes: In response to acquiring the technical status data of a target node, the target node is located through the node index table, and the ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are identified through the ship technical status knowledge graph. The identified ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are then output.

[0010] In one embodiment, the flattening of the initial ship configuration structure tree and the generation of a node index table includes: Obtain the basic data associated with each node in the node index table, integrate the historical maintenance records and technical parameter change data of each node according to the time dimension, generate "time-technical status" associated data, and present the node's technical status evolution information throughout its entire life cycle in list form.

[0011] On the other hand, a ship technical status data management device is provided, the device comprising: The data acquisition and classification module is used to collect and classify ship technical status data; The configuration structure tree construction module is used to construct the ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; The configuration tree generation module is used to associate the basic data of ship type development and equipment development in the ship technical status data with the corresponding hierarchical nodes to generate an initial ship configuration tree structure. The node index generation module is used to flatten the initial ship configuration structure tree and generate a node index table. The knowledge graph construction module is used to traverse each node according to the node index table, obtain the ship technical status data associated with each node, perform data cleaning and standardization processing, extract the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and construct a ship technical status knowledge graph.

[0012] In another aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of a ship technical status data management method.

[0013] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of a method for managing ship technical status data.

[0014] The aforementioned ship technical status data management method, device, equipment, and storage medium directly bind multi-source ship technical status data to nodes at each level through a refined ship configuration structure tree. It achieves penetrating query based on a flat index and automatically pushes multi-dimensional data through association rules. It can be directly used for precise control, efficient retrieval, and cross-domain data linkage verification of technical status. Furthermore, by extracting ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, it constructs a ship technical status knowledge graph, thus solving the problem of fragmented data in traditional processes. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is a flowchart illustrating a ship technical status data management method in one embodiment of this application; Figure 2 This is a knowledge graph management principle diagram of a ship technical status data management method in one embodiment of this application; Figure 3 This is an implementation logic diagram of a ship technical status data management method in one embodiment of this application; Figure 4 This is a structural block diagram of a ship technical status data management device in one embodiment of this application; Figure 5 This is an internal structural diagram of a computer device in one embodiment of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0018] In one embodiment, such as Figure 1 , Figure 2 As shown, a method for managing ship technical status data is provided, including the following steps: Step S1: Collect and classify the ship's technical condition data; Step S2: Construct a ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; Step S3: Associate the basic data of ship type development and equipment development in the ship technical status data with the corresponding level nodes to generate an initial ship configuration structure tree. Step S4: Flatten the initial ship configuration structure tree and generate a node index table; Step S5: Traverse each node according to the node index table, obtain the ship technical status data associated with each node, perform data cleaning and standardization, extract the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and construct a ship technical status knowledge graph.

[0019] Specifically, by refining the ship configuration structure tree, multi-source ship technical status data is directly bound to nodes at each level. A flat index enables penetrating queries, while multi-dimensional data is automatically pushed through association rules. This data can be directly used for precise control of technical status, efficient retrieval, and cross-domain data linkage verification. Furthermore, by extracting ship technical status data from the ship's core equipment and the corresponding nodes, a ship technical status knowledge graph is constructed, solving the problem of fragmented data in traditional processes.

[0020] like Figure 2 As shown, the process involves traversing each node according to the node index table, obtaining the ship's technical status data associated with each node, performing data cleaning and standardization, extracting the ship's core equipment and the ship's technical status data of the corresponding nodes, and constructing a ship's technical status knowledge graph, including: The nodes in the node index table are traversed sequentially from top to bottom to obtain the ship technical status data associated with each node. The acquired ship technical status data is cleaned and standardized to form standard data, and knowledge is constructed from the standard data to form a support data knowledge base; Based on the equipment association relationships, the standard data in the support data knowledge base are associated to form a ship technical status knowledge graph.

[0021] In this embodiment, the collection and classification of ship technical condition data includes: Collect ship technical status data, which includes ship type development data, equipment development data, ship maintenance data, ship full life cycle technical status data, equipment supplier information, repair regulation information, repair standard information, and quality system information; The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

[0022] In this embodiment, constructing the ship configuration structure tree, which involves setting up nodes at each level of the ship configuration structure tree according to the ownership relationships of equipment within the ship, includes: The data associated with each level is determined according to the type of the ship technical status data classification. The ship as a whole is taken as the root node. The nodes of each level of the ship configuration structure tree are set according to the equipment affiliation relationship of "ship as a whole-system-subsystem-equipment". The attributes of each level node are defined according to the equipment information. The equipment information includes system parameters and equipment models in the ship type development data. The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

[0023] In this embodiment, obtaining the ship technical status data associated with each node includes: Obtain the type of the ship's technical condition data classification; When receiving data classified as unstructured documents, the data is categorized according to "document type - generation time". At the same time, document keywords are extracted to build a retrieval index library. The documents are then encrypted and stored, and the stored documents are associated with the retrieval index library. When receiving data classified as structured relational data, the entities and relationships in the structured relational data are extracted and converted into triple data in the form of "subject-predicate-object". The relational database data containing the generated triple data is virtualized into RDF format. The milliohm names in the ship milliohm table are mapped to RDF predicates and the table values ​​are mapped to RDF objects to form RDF format linked data.

[0024] In this embodiment, the method further includes: Query or modify access permissions are assigned to the stored documents and RDF format linked data according to user roles, and user operation logs of the stored documents and RDF format linked data are recorded. Incremental backups and full backups of the stored documents and RDF format linked data are performed regularly.

[0025] In this embodiment, the method further includes: In response to acquiring the technical status data of a target node, the target node is located through the node index table, and the ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are identified through the ship technical status knowledge graph. The identified ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are then output.

[0026] In this embodiment, the flattening of the initial ship configuration structure tree and the generation of a node index table includes: Obtain the basic data associated with each node in the node index table, integrate the historical maintenance records and technical parameter change data of each node according to the time dimension, generate "time-technical status" associated data, and present the node's technical status evolution information throughout its entire life cycle in list form.

[0027] like Figure 2 As shown, the implementation of the ship technical condition data management method includes: Step A1: Collect source data on the technical status of the ship. The source data includes ship type development data, equipment development data, ship maintenance data, ship life cycle technical status data, equipment supplier information, repair regulations information, repair standards information, and quality system information. The source data is classified into hierarchical related data, unstructured document data, and structured relational data according to type. Step A2: Through the ship configuration structure tree construction module, receive the hierarchical association data divided in Step A1, take the ship as the root node, and preliminarily define the attributes of each level node according to the rule of "ship as a whole - system - subsystem - equipment". Step A3: The configuration structure tree construction module performs attribute binding on the initial nodes, associating basic information such as system parameters in the ship type development data and equipment models in the equipment development data with the corresponding level nodes to generate the initial ship configuration structure tree. Step A4: Flatten the configuration tree to generate a node index table, supporting fast positioning and rendering; Step A5: Receive the unstructured document data divided in Step A1, classify it according to "document type-generation time", extract document keywords to build a retrieval index, and complete the encrypted storage and index association of documents; Step A6: Receive the structured relational data divided in Step A1, extract the entities and relations in the data, and convert them into triplet data in the form of "subject-predicate-object"; In step A7, the structured data processing module calls the D2RServer tool and, in conjunction with the preset D2RQ Mapping file, virtualizes the relational database data containing the triple data generated in step A6 into RDF format. In this format, the "ZB name" of the ship milliohm (ZB) table is mapped to an RDF predicate, and the table value is mapped to an RDF object, forming RDF format linked data. Step A8: Receive the index table, document index, and RDF data; clean and standardize them; extract key entities and relationships; and construct a knowledge graph of the ship's technical status. Step A9: Quickly locate nodes based on the index table and return results in conjunction with the document and structured data; Step A10: Based on the node association data in step A4, integrate the historical maintenance records and technical parameter changes of the target node according to the time dimension to generate "time-technical status" association data, and present the node's technical status evolution information throughout its entire life cycle in a list format; Step A11: When a user retrieves data from a node through step A9, this module automatically identifies related nodes and pushes the core data of the related nodes based on the knowledge graph in step A8. Step A12: Set access permissions for the electronic documents in Step A5 and the structured data in Step A7 (assign query or modification permissions according to user roles), and record the user operation logs in Steps A9-A11. Perform incremental and full backups of all data regularly to ensure data security and recoverability.

[0028] Steps A1, A2, and A3 in this invention are preparation steps, and step A12 is a follow-up step.

[0029] The core of this application lies in the construction of the ship configuration tree structure. The optimal process adds steps A2, A3, A8, and A11. Step A4 generates a node index table through a "space-for-time" strategy, enabling rapid location and rendering of configuration tree nodes. Step A3 binds basic information such as system parameters from ship development data and equipment models from equipment development data with the nodes defined in step A2, generating an initial ship configuration tree structure. Step A8 extracts core entities and relationships for ship support based on the index table, document index, and RDF data, and constructs a knowledge graph, solving the problem of data fragmentation in traditional processes. Step A11 automatically identifies associated nodes and pushes core data based on the knowledge graph.

[0030] Step A3 constructs a ship configuration tree structure based on the hierarchical rule of "ship as a whole - system - subsystem - equipment," and associates basic data such as ship design and equipment development with nodes through node attribute binding, forming a data association benchmark that runs through the entire process. Step A4 flattens the initial configuration tree and generates an index table to achieve rapid node location and rendering. Step A9 locates nodes based on the index table and returns the results in conjunction with the linked data.

[0031] Steps A3, A5, and A6 of this invention bind all source data to nodes at the "ship as a whole - system - subsystem - equipment" hierarchical level, giving dispersed data a unified correlation benchmark and ultimately achieving unified management and control of multi-source data. Step A10 of this invention, based on node-related data, integrates historical maintenance records and technical parameter changes along the time dimension to generate a "time-technical status" correlation list. Users can intuitively view the technical status of equipment at different points in time, analyze status evolution patterns, and predict potential failure risks in advance. Step A12 of this invention assigns query / modification permissions for documents and structured data according to user roles, records operation logs, and backs them up regularly. This ensures that personnel in different positions can only access data within their authorized access range, operation behaviors are traceable, and data is prevented from being lost through incremental and full backup methods, ensuring data security and reliability.

[0032] The aforementioned ship technical status data management method directly binds multi-source ship technical status data to nodes at each level through a refined ship configuration structure tree. It achieves penetrating queries by relying on a flat index and automatically pushes multi-dimensional data through association rules. This can be directly used for precise control, efficient retrieval, and cross-domain data linkage verification of technical status. Furthermore, by extracting ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, a ship technical status knowledge graph is constructed, which solves the problem of fragmented data in traditional processes.

[0033] In one embodiment, such as Figure 4 As shown, a ship technical status data management device 10 is provided, including: a data acquisition and classification module 1, a configuration tree structure construction module 2, a configuration tree generation module 3, a node index generation module 4, a knowledge graph construction module 5, a safety and backup management module 6, and a data query and processing module 7.

[0034] The data acquisition and classification module 1 is used to acquire and classify ship technical status data.

[0035] The configuration structure tree construction module 2 is used to construct the ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship.

[0036] The configuration tree generation module 3 is used to associate the basic data of ship type development and equipment development in the ship technical status data with the corresponding level nodes to generate an initial ship configuration tree structure.

[0037] The node index generation module 4 is used to flatten the initial ship configuration structure tree and generate a node index table.

[0038] The knowledge graph construction module 5 is used to traverse each node according to the node index table, obtain the ship technical status data associated with each node, perform data cleaning and standardization, extract the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and construct a ship technical status knowledge graph.

[0039] In this embodiment, the collection and classification of ship technical condition data includes: Collect ship technical status data, which includes ship type development data, equipment development data, ship maintenance data, ship full life cycle technical status data, equipment supplier information, repair regulation information, repair standard information, and quality system information; The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

[0040] In this embodiment, constructing the ship configuration structure tree, which involves setting up nodes at each level of the ship configuration structure tree according to the ownership relationships of equipment within the ship, includes: The data associated with each level is determined according to the type of the ship technical status data classification. The ship as a whole is taken as the root node. The nodes of each level of the ship configuration structure tree are set according to the equipment affiliation relationship of "ship as a whole-system-subsystem-equipment". The attributes of each level node are defined according to the equipment information. The equipment information includes system parameters and equipment models in the ship type development data. The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

[0041] In this embodiment, obtaining the ship technical status data associated with each node includes: Obtain the type of the ship's technical condition data classification; When receiving data classified as unstructured documents, the data is categorized according to "document type - generation time". At the same time, document keywords are extracted to build a retrieval index library. The documents are then encrypted and stored, and the stored documents are associated with the retrieval index library. When receiving data classified as structured relational data, the entities and relationships in the structured relational data are extracted and converted into triple data in the form of "subject-predicate-object". The relational database data containing the generated triple data is virtualized into RDF format. The milliohm names in the ship milliohm table are mapped to RDF predicates and the table values ​​are mapped to RDF objects to form RDF format linked data.

[0042] In this embodiment, the security and backup management module 6 is used for: Query or modify access permissions are assigned to the stored documents and RDF format linked data according to user roles, and user operation logs of the stored documents and RDF format linked data are recorded. Incremental backups and full backups of the stored documents and RDF format linked data are performed regularly.

[0043] In this embodiment, the data query processing module 7 is used for: In response to acquiring the technical status data of a target node, the target node is located through the node index table, and the ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are identified through the ship technical status knowledge graph. The identified ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are then output.

[0044] In this embodiment, the flattening of the initial ship configuration structure tree and the generation of a node index table includes: Obtain the basic data associated with each node in the node index table, integrate the historical maintenance records and technical parameter change data of each node according to the time dimension, generate "time-technical status" associated data, and present the node's technical status evolution information throughout its entire life cycle in list form.

[0045] The aforementioned ship technical status data management device directly binds multi-source ship technical status data to nodes at each level through a refined ship configuration structure tree. It achieves penetrating queries based on a flat index and automatically pushes multi-dimensional data through association rules. This can be directly used for precise control, efficient retrieval, and cross-domain data linkage verification of technical status. Furthermore, by extracting ship technical status data from the ship's core equipment and the corresponding nodes of the core equipment, it constructs a ship technical status knowledge graph, thus solving the problem of fragmented data in traditional processes.

[0046] Specific limitations regarding the ship technical status data management device can be found in the limitations of the ship technical status data management method described above, and will not be repeated here. Each module in the aforementioned ship technical status data management device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the corresponding operations of each module.

[0047] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 5As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores ship technical status data management data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a ship technical status data management method.

[0048] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0049] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps: Collect and classify ship technical condition data; Construct a ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; The basic data on ship type development and equipment development in the ship technical status data are associated with the corresponding hierarchical nodes to generate an initial ship configuration structure tree. The initial ship configuration structure tree is flattened and a node index table is generated; The system iterates through each node according to the node index table, obtains the ship technical status data associated with each node, performs data cleaning and standardization, extracts the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and constructs a ship technical status knowledge graph.

[0050] For specific limitations on the steps implemented by the processor when executing a computer program, please refer to the limitations on the methods for managing ship technical status data mentioned above, which will not be repeated here.

[0051] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor: Collect and classify ship technical condition data; Construct a ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; The basic data on ship type development and equipment development in the ship technical status data are associated with the corresponding hierarchical nodes to generate an initial ship configuration structure tree. The initial ship configuration structure tree is flattened and a node index table is generated; The system iterates through each node according to the node index table, obtains the ship technical status data associated with each node, performs data cleaning and standardization, extracts the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and constructs a ship technical status knowledge graph.

[0052] For specific limitations on the steps implemented when a computer program is executed by a processor, please refer to the limitations on the methods for managing ship technical status data mentioned above, which will not be repeated here.

[0053] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0054] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0055] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for managing ship technical status data, characterized in that, include: Collect and classify ship technical condition data; Construct a ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; The basic data of ship type development and equipment development in the ship technical status data are associated with the corresponding hierarchical nodes to generate an initial ship configuration structure tree. The initial ship configuration structure tree is flattened and a node index table is generated; The system iterates through each node according to the node index table, obtains the ship technical status data associated with each node, performs data cleaning and standardization, extracts the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and constructs a ship technical status knowledge graph.

2. The ship technical status data management method according to claim 1, characterized in that, The collection and classification of ship technical condition data includes: Collect ship technical status data, which includes ship type development data, equipment development data, ship maintenance data, ship full life cycle technical status data, equipment supplier information, repair regulation information, repair standard information, and quality system information; The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

3. The ship technical status data management method according to claim 1, characterized in that, The construction of the ship configuration structure tree involves setting up nodes at each level of the ship configuration structure tree according to the ownership relationships of equipment within the ship, including: The data associated with each level is determined according to the type of the ship technical status data classification. The ship as a whole is taken as the root node. The nodes of each level of the ship configuration structure tree are set according to the equipment affiliation relationship of "ship as a whole-system-subsystem-equipment". The attributes of each level node are defined according to the equipment information, which includes system parameters and equipment models in the ship type development data. The ship technical status data is categorized into hierarchical related data, unstructured document data, and structured relational data.

4. The ship technical status data management method according to claim 2, characterized in that, The acquisition of ship technical status data associated with each node includes: Obtain the type of the ship's technical condition data classification; When receiving data classified as unstructured documents, the system categorizes the documents by "document type - generation time", extracts document keywords to build a retrieval index, encrypts and stores the documents, and associates the stored documents with the retrieval index. When receiving data classified as structured relational data, the entities and relationships in the structured relational data are extracted and converted into triple data in the form of "subject-predicate-object". The relational database data containing the generated triple data is virtualized into RDF format. The milliohm names in the ship milliohm table are mapped to RDF predicates and the table values ​​are mapped to RDF objects to form RDF format linked data.

5. The ship technical status data management method according to claim 4, characterized in that, The method further includes: Query or modify access permissions are assigned to the stored documents and RDF format linked data according to user roles, and user operation logs of the stored documents and RDF format linked data are recorded. Incremental backups and full backups of the stored documents and RDF format linked data are performed regularly.

6. The ship technical status data management method according to claim 1, characterized in that, The method further includes: In response to acquiring the technical status data of a target node, the target node is located through the node index table, and the ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are identified through the ship technical status knowledge graph. The identified ship technical status data corresponding to the target node and the ship technical status data that are linked with the target node are then output.

7. The ship technical status data management method according to claim 1, characterized in that, The process of flattening the initial ship configuration structure tree and generating a node index table includes: Obtain the basic data associated with each node in the node index table, integrate the historical maintenance records and technical parameter change data of each node according to the time dimension, generate "time-technical status" associated data, and present the evolution information of the node's technical status throughout its entire life cycle in list form.

8. A ship technical status data management device, characterized in that, The device includes: The data acquisition and classification module is used to collect and classify ship technical status data; The configuration structure tree construction module is used to construct the ship configuration structure tree and set the nodes of each level of the ship configuration structure tree according to the ownership relationship of the equipment in the ship; The configuration tree generation module is used to associate the basic data of ship type development and equipment development in the ship technical status data with the corresponding hierarchical nodes to generate an initial ship configuration tree structure. The node index generation module is used to flatten the initial ship configuration structure tree and generate a node index table. The knowledge graph construction module is used to traverse each node according to the node index table, obtain the ship technical status data associated with each node, perform data cleaning and standardization processing, extract the ship technical status data of the ship's core equipment and the corresponding nodes of the core equipment, and construct a ship technical status knowledge graph.

9. 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 computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images