BOM data integrated storage and management method applied to ship overall design software

Abstract

The invention belongs to the technical field of ship engineering and information, and particularly relates to a BOM data integrated storage and management method applied to ship overall design software, which comprises the following steps: defining a metadata model of BOM data in the ship overall design software, including part types, attributes, relationships and constraint information; the management process of the BOM data is simplified through a unified data storage library and standardized processing, and the working efficiency of a design team is improved. And the data error rate is reduced: through data deduplication and redundancy processing, the possibility of data errors is reduced, and the design accuracy is improved. And through data integration and establishment of an association relationship, data exchange and sharing among different majors are promoted, and collaborative design of multiple majors is facilitated. Through data standardization and naming specification, the query and manageability of the BOM data are improved, and a design team can conveniently search and use the data.

Description

Technical Field

[0001] The present invention relates to the field of ship engineering and information technology, and in particular to a BOM data integrated storage and management method applied to ship overall design software. Background Art

[0002] In the field of ship engineering, with the increasing demand for complex ship design and manufacturing, the traditional manual management of BOM and design data can no longer meet the needs of modern production. Integrated PDM systems and CAD systems have emerged to improve design efficiency, ensure data consistency and reduce errors. Typical representatives of these systems include Siemens' TC and NX, Dassault's Enovia and Catia, PTC's Wi ndch ill and Creo, which can not only manage design data, but also provide collaborative tools to support the collaborative work of multidisciplinary teams. However, the above-mentioned similar products are mainly aimed at traditional mechanical products, such as automobiles and aircraft, but for large and complex equipment such as ships, when the amount of data reaches tens of millions, there are still certain limitations in the integrated storage and management of data, especially in the data synchronization and consistency maintenance between different systems, which need further optimization and improvement.

[0003] The overall design of a ship is a complex and comprehensive engineering process, covering multiple professional fields such as hull structure, propulsion system, electrical system, piping system, etc. In order to ensure the integrity and accuracy of the ship design, it is necessary to systematically manage the large number of parts, materials and equipment used in the design process, and BOM is the key link in this process.

[0004] Most traditional design software has independent BOM management modules, but these modules often face the following major problems:

[0005] 1. Data island effect: Different professional fields use their own independent design software and databases, which makes it difficult for BOM data to communicate and share, forming information islands. This situation not only increases the complexity of data management, but also leads to design errors due to inconsistent information.

[0006] 2. Inconsistent formats: There are differences in data formats and storage methods between different software and systems, which makes it difficult to exchange and integrate BOM data between different systems. For example, one system may use XML format to store data, while another system may use JSON or other formats.

[0007] 3. Data redundancy and synchronization issues: Due to the lack of a centralized management mechanism, BOM data often becomes redundant and inconsistent between different systems. After updating the information of a certain component, it needs to be manually synchronized to other systems, which increases the workload and the risk of errors.

[0008] 4. Difficulty in version control: Ship design is an iterative process. With the continuous modification and optimization of the design, BOM data also needs to be updated frequently. However, the traditional method of version control of BOM data is not perfect, which can easily lead to the misuse or loss of old version data.

[0009] 5. Weak authority management: Ship design involves multiple teams and roles, and different personnel should have different access rights to BOM data. However, traditional methods of controlling data authority are relatively rough, which poses the risk of data leakage and misoperation.

[0010] In summary, there are obvious deficiencies in the BOM data management in the current ship overall design software, which not only affects the efficiency and accuracy of the design process, but also increases the workload of the design team. Therefore, a new method is urgently needed to achieve the integrated storage and efficient management of BOM data. Summary of the invention

[0011] (I) Purpose of the invention

[0012] In order to solve the technical problems existing in the background technology, the present invention proposes an integrated storage and management method for BOM data applied to ship overall design software, which realizes the efficient management of BOM data in the process of ship design and manufacturing, solves the problems of data islands, insufficient version control, inconsistent metadata definition and decentralized data storage in the prior art, improves the accuracy, consistency and traceability of data, and provides strong support for efficient collaboration in ship design and manufacturing.

[0013] (II) Technical solution

[0014] In order to solve the above technical problems, the present invention provides a BOM data integrated storage and management method applied to ship overall design software, comprising the following steps:

[0015] Step 1: Data model definition: define the metadata model of BOM data in the ship overall design software, including component types, attributes, relationships and constraint information;

[0016] Step 2: Data integration: Integrate BOM data from different professional fields into a unified data repository, use PDM parts management objects as the carrier, establish a synchronous mapping relationship between data, and remove duplicate and redundant data;

[0017] Step 3: Data standardization: Standardize BOM data in a unified manner, including naming standards, unit standards, and classification standards, to ensure data consistency and queryability;

[0018] Step 4: Data update and synchronization: Establish a data update and synchronization mechanism to ensure timely update and sharing of BOM data, including feedback on design changes and management of data versions;

[0019] Step 5. Data authority management: Set up a data authority management mechanism to protect the security and confidentiality of BOM data.

[0020] Furthermore, in step one, the data model definition includes defining a unified metadata structure in the CAD system and the PDM system, including attributes, relationships, and constraints, to ensure that the BOM data in the CAD and PDM systems follow the same standard to ensure data consistency and integrity.

[0021] Furthermore, in step 2, data integration includes data matching, data checking, and data processing;

[0022] Data matching: Extract BOM data from the CAD system through data type matching and convert it into a format that the PDM system can recognize. Unify standards through metadata models and map data fields in the CAD system to corresponding fields in the PDM system to ensure that all necessary information can be correctly transmitted and stored.

[0023] Data check: During the synchronization process, the CAD data is verified to check whether all required fields have values, whether the numeric fields are within the expected range, etc., to ensure that there is no missing or erroneous information. The synchronized data is verified for consistency in the PDM system to ensure that the data has not been tampered with or lost during the transmission process;

[0024] Data processing: Detect and process duplicate data in the CAD system to avoid storing redundant information in the PDM system; if redundancy exists, merge and clean up the redundant data to ensure that the data in the PDM system is concise and non-duplicate.

[0025] Furthermore, in step 3, data standardization includes unified standardization of BOM data, including naming standards, unit standards, and classification standards;

[0026] Naming standards: formulate unified naming rules, including using short English words or abbreviations and avoiding Chinese or pinyin names to avoid ambiguity;

[0027] Unit standardization: Use a combination of numbers, letters, and symbols to unify the measurement of units to avoid ambiguity.

[0028] Classification specifications include:

[0029] Functional classification: Classification based on function, such as mechanical parts, electronic components, plastic parts, etc.;

[0030] Material classification: Classification according to materials, such as metal materials, plastic materials, electronic materials, etc.

[0031] During the data standardization process, the coding of BOM data is unique. Each BOM data should have a unique coding to ensure that there is no duplication or confusion. For BOM data that changes frequently, the BOM data sub-coding should be updated.

[0032] Furthermore, in step 4, data updating includes the following steps:

[0033] Update of model tree and 3D model in CAD system;

[0034] Extract the BOM data of the updated model tree and 3D model for standardization;

[0035] Confirm the updated content after comparing with the historical BOM data in the data repository;

[0036] Updates include changes to attributes, geometry levels, and assembly relationships.

[0037] Furthermore, in step 4, data synchronization includes the following steps:

[0038] The updated content of the model tree and 3D model in the CAD system is uploaded to the PDM system;

[0039] Detect and confirm updated content and BOM data based on unified standards of metadata structure;

[0040] BOM data needs to be reviewed and approved before it can take effect in the PDM system. For the changed parts, the approval process also needs to be changed to ensure that all BOM data modifications are properly reviewed and approved.

[0041] Furthermore, in step 5, the data rights management mechanism of data rights management is:

[0042] When BOM data in the CAD system changes, the system should automatically notify relevant personnel and manually decide whether to update the corresponding data in the PDM system;

[0043] BOM data needs to be reviewed and approved before it can take effect in the PDM system. For the changed parts, the approval process also needs to be changed to ensure that all BOM data modifications are properly reviewed and approved.

[0044] Furthermore, in step five, version control of the CAD system and the PDM system: no version management is required in the CAD system, and one-way version management is performed after the BOM data is synchronized to the PDM system to ensure that the BOM data in the PDM system can reflect the historical records of each modification and does not affect the design iteration of the BOM data in the CAD system.

[0045] The above technical solution of the present invention has the following beneficial technical effects:

[0046] 1. Improve data management efficiency: Through a unified data repository and standardized processing, the management process of BOM data is simplified and the work efficiency of the design team is improved.

[0047] 2. Reduce data error rate: Through data deduplication and redundancy processing, the possibility of data errors is reduced and the accuracy of the design is improved.

[0048] 3. Promote multi-disciplinary collaboration: Through data integration and the establishment of association relationships, data exchange and sharing between different disciplines are promoted, which is conducive to multi-disciplinary collaborative design.

[0049] 4. Improve data queryability: Through data standardization and naming specifications, the queryability and manageability of BOM data are improved, making it easier for the design team to find and use data. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 It is a schematic diagram of the integrated storage and management method of BOM data applied to ship overall design software of the present invention;

[0051] Figure 2 It is a schematic diagram of the BOM data integrated storage workflow of the present invention;

[0052] Figure 3 A system architecture diagram of the BOM data integrated storage method of the present invention;

[0053] Figure 4 It is a schematic diagram of the BOM data integration conversion method of the present invention. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. In addition, in the following description, the description of well-known structures and technologies is omitted to avoid unnecessary confusion of the concept of the present invention.

[0055] like Figure 1-4 As shown, the present invention proposes a BOM data integrated storage and management method applied to ship overall design software, comprising the following steps:

[0056] Step 1: Data model definition: define the metadata model of BOM data in the ship overall design software, including component types, attributes, relationships and constraint information;

[0057] Data model definition includes defining a unified metadata structure in the CAD system and PDM system, defining the CAD metamodel and PDM metamodel in terms of attributes, relationships and constraint information, unifying information in multiple aspects, and ensuring that the BOM data in the CAD and PDM systems follows the same standard to ensure data consistency and integrity.

[0058] Step 2: Data integration: Integrate BOM data from different professional fields into a unified data repository, use PDM parts management objects as the carrier, establish a synchronous mapping relationship between data, and remove duplicate and redundant data;

[0059] Due to the differences in data formats and storage methods between different software and systems, it is difficult to exchange and integrate BOM data between different systems. For example, one system may use XML format to store data, while another system may use JSON or other formats. Unified BOM data is defined through metadata structure and can be identified in CAD system and PDM system. Unified data repository and standardized processing assist different design teams to interact between the two systems through BOM data. Through data integration and the establishment of association relationships, data exchange and sharing between different disciplines are promoted, which is conducive to multi-disciplinary collaborative design.

[0060] Data integration includes data matching, data checking and data processing;

[0061] Data matching: Extract BOM data from the CAD system through data type matching and convert it into a format that the PDM system can recognize. Unify standards through metadata models and map data fields in the CAD system to corresponding fields in the PDM system to ensure that all necessary information can be correctly transmitted and stored.

[0062] Data check: During the synchronization process, the CAD data is verified to check whether all required fields have values, whether the numeric fields are within the expected range, etc., to ensure that there is no missing or erroneous information. The synchronized data is verified for consistency in the PDM system to ensure that the data has not been tampered with or lost during the transmission process;

[0063] Data processing: Detect and process duplicate data in the CAD system to avoid storing redundant information in the PDM system; if redundancy exists, merge and clean up the redundant data to ensure that the data in the PDM system is concise and non-duplicate.

[0064] Step 3: Data standardization: Standardize BOM data in a unified manner, including naming standards, unit standards, and classification standards, to ensure data consistency and queryability;

[0065] Data standardization includes unified standardization of BOM data, including naming standards, unit standards, and classification standards;

[0066] Naming standards: formulate unified naming rules, including using short English words or abbreviations and avoiding Chinese or pinyin names to avoid ambiguity;

[0067] Unit standardization: Use a combination of numbers, letters, and symbols to unify the measurement of units to avoid ambiguity.

[0068] Classification specifications include functional classification and material classification:

[0069] Functional classification: Classification based on function, such as mechanical parts, electronic components, plastic parts, etc.;

[0070] Material classification: Classification according to materials, such as metal materials, plastic materials, electronic materials, etc.

[0071] During the data standardization process, the coding of BOM data is unique. Each BOM data should have a unique coding to ensure that there is no duplication or confusion. For BOM data that changes frequently, the BOM data sub-coding should be updated.

[0072] Step 4: Data update and synchronization: Establish a data update and synchronization mechanism to ensure timely update and sharing of BOM data, including feedback on design changes and management of data versions;

[0073] The data update includes the following steps:

[0074] Update of model tree and 3D model in CAD system;

[0075] Extract the BOM data of the updated model tree and 3D model for standardization;

[0076] Confirm the updated content after comparing with the historical BOM data in the data repository;

[0077] Updates include changes to attributes, geometry levels, and assembly relationships.

[0078] Data synchronization includes the following steps:

[0079] The updated content of the model tree and 3D model in the CAD system is uploaded to the PDM system;

[0080] Detect and confirm updated content and BOM data based on unified standards of metadata structure;

[0081] BOM data needs to be reviewed and approved before it can take effect in the PDM system. For the changed parts, the approval process also needs to be changed to ensure that all BOM data modifications are properly reviewed and approved.

[0082] Step 5. Data authority management: Set up a data authority management mechanism to protect the security and confidentiality of BOM data.

[0083] The data rights management mechanism of data rights management is: when the BOM data in the CAD system changes, the system should automatically notify the relevant personnel and manually decide whether to update the corresponding data in the PDM system;

[0084] BOM data needs to be reviewed and approved before it can take effect in the PDM system. For the changed parts, the approval process also needs to be changed to ensure that all BOM data modifications are properly reviewed and approved.

[0085] In step five, version control of CAD system and PDM system: no version management is required in the CAD system, and one-way version management is performed after the BOM data is synchronized to the PDM system to ensure that the BOM data in the PDM system can reflect the historical records of each modification and does not affect the design iteration of the BOM data in the CAD system.

[0086] In this embodiment, the method achieves the goal of improving data management efficiency, reducing data error rate, promoting multi-professional collaboration and improving data queryability;

[0087] Through a unified data repository and standardized processing, the BOM data management process is simplified and the work efficiency of the design team is improved;

[0088] Through data deduplication and redundancy processing, the possibility of data errors is reduced and the accuracy of design is improved;

[0089] Through data integration and the establishment of association relationships, data exchange and sharing between different disciplines are promoted, which is conducive to multi-disciplinary collaborative design;

[0090] Through data standardization and naming conventions, the queryability and manageability of BOM data are improved, making it easier for design teams to find and use data.

[0091] like Figure 3 As shown in the figure, the overall ship design software consists of two systems and one integration module: the CAD system is mainly used for the construction of BOM data of various disciplines, the BOM data integration module is mainly used for data standardization processing and update synchronization, and the PDM system is mainly used for the integrated management of BOM data versions;

[0092] The overall ship design software uses a relational database, and the data is integrated and converted within the same database to ensure data consistency and integrity, and improve the timeliness of data update and synchronization;

[0093] The data permission management of the ship overall design software adopts the same permission mechanism to ensure that the data has a high degree of security in both design and management activities.

[0094] like Figure 4 As shown in the figure, the BOM data integration conversion method is described as follows: the model tree and 3D model are constructed in the CAD system according to the design requirements. The 3D model includes attributes, geometry level and assembly relationship;

[0095] Through the BOM data integration module, the CAD model is standardized, updated and synchronized. The preset data type matching rules are defined through metadata. The CAD model is automatically converted into the component type defined in PDM and a data integrity check is performed. Attribute field mapping and geometric set lightweight processing are then performed. After the processing is completed, the components are mounted to their respective intermediate products according to the assembly relationship.

[0096] It should be understood that the above specific embodiments of the present invention are only used to illustrate or explain the principles of the present invention, and do not constitute a limitation of the present invention. Therefore, any modifications, equivalent substitutions, improvements, etc. made without departing from the spirit and scope of the present invention should be included in the protection scope of the present invention. In addition, the appended claims of the present invention are intended to cover all changes and modifications that fall within the scope and boundaries of the appended claims, or the equivalent forms of such scope and boundaries.

Claims

1. A method for integrated storage and management of BOM data applied to ship overall design software, characterized in that: The following steps are involved: Step 1: Data model definition: define the metadata model of BOM data in the ship overall design software, including component types, attributes, relationships and constraint information; Step 2: Data integration: Integrate BOM data from different professional fields into a unified data repository, use PDM parts management objects as the carrier, establish a synchronous mapping relationship between data, and remove duplicate and redundant data; Step 3: Data standardization: Standardize BOM data in a unified manner, including naming standards, unit standards, and classification standards, to ensure data consistency and queryability; Step 4: Data update and synchronization: Establish a data update and synchronization mechanism to ensure timely update and sharing of BOM data, including feedback on design changes and management of data versions; Step 5. Data authority management: Set up a data authority management mechanism to protect the security and confidentiality of BOM data.

2. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 1, characterized in that: In step one, the data model definition includes defining a unified metadata structure in the CAD system and the PDM system, including attributes, relationships, and constraints, to ensure that the BOM data in the CAD and PDM systems follow the same standard to ensure data consistency and integrity.

3. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 1, characterized in that: In step 2, data integration includes data matching, data checking, and data processing; Data matching: Extract BOM data from the CAD system through data type matching and convert it into a format that the PDM system can recognize. Unify standards through metadata models and map data fields in the CAD system to corresponding fields in the PDM system to ensure that all necessary information can be correctly transmitted and stored. Data check: During the synchronization process, the CAD data is verified to check whether all required fields have values, whether the numeric fields are within the expected range, etc., to ensure that there is no missing or erroneous information. The synchronized data is verified for consistency in the PDM system to ensure that the data has not been tampered with or lost during the transmission process; Data processing: Detect and process duplicate data in the CAD system to avoid storing redundant information in the PDM system; If there is redundancy, the redundant data will be merged and cleaned up to ensure that the data in the PDM system is concise and non-repetitive.

4. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 1, characterized in that: In step 3, data standardization includes unified standardization of BOM data, including naming standards, unit standards, and classification standards; Naming standards: formulate unified naming rules, including using short English words or abbreviations and avoiding Chinese or pinyin names to avoid ambiguity; Unit standardization: Use a combination of numbers, letters, and symbols to unify the measurement of units to avoid ambiguity. Classification specifications include: Functional classification: Classification based on function, such as mechanical parts, electronic components, plastic parts, etc.; Material classification: Classification according to materials, such as metal materials, plastic materials, electronic materials, etc.

5. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 4, characterized in that: During the data standardization process, the coding of BOM data is unique. Each BOM data should have a unique coding to ensure that there is no duplication or confusion. For BOM data that changes frequently, the BOM data sub-coding should be updated.

6. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 1, characterized in that: In step 4, data updating includes the following steps: Update of model tree and 3D model in CAD system; Extract the BOM data of the updated model tree and 3D model for standardization; Confirm the updated content after comparing with the historical BOM data in the data repository; Updates include changes to attributes, geometry levels, and assembly relationships.

7. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 6, characterized in that: In step 4, data synchronization includes the following steps: The updated content of the model tree and 3D model in the CAD system is uploaded to the PDM system; Detect and confirm updated content and BOM data based on unified standards of metadata structure; BOM data needs to be reviewed and approved before it can take effect in the PDM system. For the changed parts, the approval process also needs to be changed to ensure that all BOM data modifications are properly reviewed and approved.

8. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 1, characterized in that: In step 5, the data rights management mechanism of data rights management is: When BOM data in the CAD system changes, the system should automatically notify relevant personnel and manually decide whether to update the corresponding data in the PDM system; BOM data needs to be reviewed and approved before it can take effect in the PDM system. For the changed parts, the approval process also needs to be changed to ensure that all BOM data modifications are properly reviewed and approved.

9. The method for integrated storage and management of BOM data applied to ship overall design software according to claim 1, characterized in that: In step five, version control of CAD system and PDM system: no version management is required in the CAD system, and one-way version management is performed after the BOM data is synchronized to the PDM system to ensure that the BOM data in the PDM system can reflect the historical records of each modification and does not affect the design iteration of the BOM data in the CAD system.

Images