Multi-view BOM conversion method and system based on single data source

Abstract

The invention provides a multi-view BOM conversion method and system based on a single data source, and the method comprises the steps: taking EBOM, PBOM and MBOM original data of a ship design and manufacturing system as input, employing a JSON format for storage, and building a full-life-cycle xBOM unified model, and enabling each BOM node to have a static attribute; a mapping rule is dynamically selected through a hybrid mapping rule engine, and EBOM-PBOM-MBOM conversion is completed; data consistency is detected in conversion, various conflicts are resolved by adopting multiple strategies, and the whole process is recorded; according to the method, the efficiency is optimized by combining an incremental updating technology, finally, interactive integration is supported through a Web interface and an API interface, and a manufacturing instruction is generated, multi-view BOM lossless conversion and data communication are achieved, the problems that data are inconsistent and the process and manufacturing resources are disjointed in a traditional method are solved, and the method has the advantages of being accurate in conversion, high in efficiency and easy to maintain.

Description

Technical Field

[0001] This invention belongs to the technical field of data management for complex ship products, specifically relating to a multi-view BOM conversion method and system based on a single data source. Background Technology

[0002] Against the backdrop of the deep advancement of intelligent manufacturing and Industry 4.0, the accuracy and efficiency of bill of materials (BOM) structure calculation for ships, as typical complex products, has become a core bottleneck restricting the progress of intelligent shipbuilding. Ships, as a typical example of highly complex structures, have over 100,000 material items per ship, involving more than 50 different views across design, process, manufacturing, and maintenance, with a lifecycle spanning over 20 years. Their strong component interrelationships are reflected in multi-level nested assembly relationships, where each component from raw materials to the final product forms an organic whole through close hierarchical connections. Simultaneously, ship BOMs exhibit significant dynamic data evolution characteristics, with frequent dynamic events such as design changes, process adjustments, manufacturing anomalies, and operational feedback triggering the need for real-time updates to BOM data. However, traditional BOM management models face multiple challenges in addressing these characteristics: low efficiency in design-manufacturing collaboration, specifically manifested in the lag in the conversion process from the design BOM (EBOM) to the manufacturing BOM (MBOM), leading to a disconnect between the design and manufacturing stages; a broken change propagation chain, making it difficult for engineering changes to be synchronized to the manufacturing view in a timely manner, resulting in repeated adjustments in subsequent production stages; and a prominent problem of multi-source data silos, with inconsistent data standards and semantics among systems such as computer-aided design (CAD), enterprise resource planning (ERP), and maintenance, repair, and operation (MRO), forming information barriers. These problems directly lead to extended shipbuilding cycles and material waste.

[0003] In the current wave of industrial intelligence, the shipbuilding industry is undergoing unprecedented transformation. To adapt to this transformation, shipbuilding BOM management must become more precise and efficient. The complexity of ships lies not only in the sheer number of material items but also in the complexity of their design and manufacturing processes. Ship design and manufacturing involve numerous views, including but not limited to design views, process views, manufacturing views, and operation and maintenance views. The entire lifecycle of a ship can span over 20 years, requiring BOM management to handle long-term data evolution. There are close hierarchical relationships between ship components, starting from raw materials and extending to the final product, forming a multi-layered nested assembly relationship, making each component an integral part of the entire product. The dynamic evolution of shipbuilding BOMs is significant; dynamic events such as design changes, process adjustments, manufacturing anomalies, and operation and maintenance feedback frequently trigger the need for real-time updates to BOM data.

[0004] To effectively address these challenges and meet these demands, BOM management technology must continuously innovate and improve to adapt to ever-growing and changing technological requirements. In the specific field of shipbuilding, the collaborative work of multiple specialized views is becoming increasingly critical. These views include, but are not limited to, core views such as EBOM, PBOM, and MBOM. To ensure a smooth and efficient manufacturing process, seamless and efficient linkage between these different views is required to ensure accurate information transmission and timely updates. These key requirements drive the continuous iteration and upgrading of BOM algorithms in terms of efficiency and accuracy, aiming to achieve a higher level of intelligence. Summary of the Invention

[0005] The technical problem to be solved by this invention is to provide a multi-view BOM conversion method and system based on a single data source to address the above-mentioned problems. By constructing a dynamic conflict resolution mechanism and a multi-view conversion method, lossless conversion and data integration of EBOM, PBOM and MBOM can be achieved, solving problems such as inconsistent view data and disconnect between process parameters and manufacturing resources in traditional methods.

[0006] The embodiments of this application are implemented as follows: This application provides a method for converting a multi-view BOM based on a single data source, characterized by the following steps: Step a: Input the raw data of EBOM, PBOM and MBOM from the ship design and manufacturing system, store the data in JSON format, and establish a unified xBOM model for the entire life cycle to show the BOM structure. This model encapsulates data and behavior, so that each BOM node has static attributes of the data. Step b: Load the hybrid mapping rule engine and execute the tasks of converting EBOM to PBOM and PBOM to MBOM. The mechanism is based on rules and dynamically selects mapping rules according to the differences in node type and application scenario. Step c: During the data conversion process, data consistency detection is performed. When data conflicts are detected, the conflicts are identified and classified. Based on the specific type of conflict, one or more corresponding resolution strategies are selected to solve the actual conflict problem. In step d, based on the premise of improving efficiency during the data transformation process, incremental updates are implemented in the algorithm. At the same time, the system introduces a caching mechanism to reduce the database load and optimizes memory usage through parallel processing of independent subtrees and lazy loading technology. Step e: Through the web interface and API interface, user interaction and system integration are supported, and the system generates manufacturing instructions after data analysis and processing.

[0007] In some optional implementations, the static attributes of the BOM node described in step a include the following: Node ID: As an identifier, it ensures that each node can be accurately identified and referenced in a complex product structure; Node Name: A descriptive name that reflects the node's function, location, or other key information, providing an intuitive identifier for each node to facilitate understanding and communication among engineers and technicians; Node types include various types such as assemblies, parts, virtual parts, outsourced parts, process parts, and resources, to distinguish nodes of different natures, thereby enabling more refined control and optimization in design, manufacturing, and supply chain management; Attribute dictionary: A collection of attributes in the form of key-value pairs, providing additional information for each node, including size, material, cost, and supplier, providing data support for product lifecycle management; Child node list: Used to reference child nodes, reflecting the hierarchy and recursion of the BOM structure. The child node list shows the assembly relationship and hierarchical structure of the products, providing a basis for production planning and material requirements planning.

[0008] In some alternative implementations, the mapping rules followed by the EBOM to PBOM conversion in step b are as follows: Virtual component deletion rules: When a node type is identified as virtual, it means that the node is a virtual component. Once the triggering condition is met, the system will perform a deletion operation, remove the virtual node, and promote all its child nodes to the parent node level of the original virtual node. Outsourced parts folding rules: When a node type is identified as "outsource", it indicates that the node represents an outsourced component. The system will perform a folding operation to merge the outsourced component nodes into a single node, and add necessary supply chain attributes, such as supplier code, purchase batch and other key information, in the process. Specialized equipment process planning rules When the node type is the equipment, system or component type corresponding to each profession, these nodes usually represent equipment or components of a specific professional field; on these nodes, the system will add specific process parameters required by that professional field, including but not limited to installation methods, accuracy requirements, and fastening standards, to ensure the correct installation and functional realization of the professional equipment; Security specification integration rules: When nodes have electrical characteristics, safety attributes such as explosion-proof requirements and insulation levels are added. The mapping rules followed in the PBOM to MBOM conversion are as follows: Electrical assembly unit division rules: When the node type is process, the process unit is refined into a manufacturing unit; Dedicated equipment resource binding rules: When a node requires dedicated equipment, manufacturing resources are tied to it. Detailed rules for electrical work instructions: When the node involves electrical installation, develop detailed work instructions, including wiring sequence and terminal crimping parameters.

[0009] In some alternative implementations, the resolution of data conflicts in step c includes the following specific details: Step c1 employs an attribute priority strategy, prioritizing manufacturing view parameters, followed by process view parameters, and finally design view parameters when processing data, ensuring that parameters that are closer to actual production needs are processed first. Step c2 uses a timestamp strategy to record the modification time of each parameter. When a data conflict occurs, the latest modified parameter is given higher priority to ensure the real-time performance and accuracy of the data, so that the latest data can be reflected in the conversion results in a timely manner. Step c3 involves using business rule strategies to implement specific industry-specific rules based on industry standards, ensuring that parameters that comply with industry standards and security criteria are given priority during data transformation.

[0010] In some alternative implementations, the types of data conflicts include attribute conflicts, structural conflicts, and semantic conflicts; the resolution strategies include manual intervention, automatic merging, and rule-based solutions.

[0011] In some optional implementations, the incremental update described in step d includes the following: Step d1 involves using trigger mechanisms to monitor data changes in real time, accurately capturing add, delete, and modify operations, and providing accurate change inputs for subsequent processing. Step d2 involves conducting an in-depth impact analysis on the captured changes, identifying the range of nodes affected by the changes and constructing an impact subtree to clarify the propagation path and scope of the changes. Step d3: Implement a local update strategy based on the affected subtree, only adjust the data in the affected part, avoid the performance overhead of full update, and improve data processing efficiency. Step d4 involves maintaining the data version history through the version management module, fully recording detailed information of each change, supporting data rollback to address accidental operations, and providing a reliable basis for audit trails.

[0012] In some optional implementations, the depth impact analysis described in step d2 specifically includes the following: A depth-first search is used to traverse the affected subtrees, with a time complexity of O(n), where n is the number of affected nodes. Change handling is achieved through a closed-loop design of capture-analysis-update-trace.

[0013] In some alternative implementations, the generation of manufacturing instructions in step e involves automatically extracting design information, separating processes, decomposing the structure into manufacturable units, planning assembly sequences, and dynamically adjusting the allocation of manufacturing resources.

[0014] In some alternative implementations, the entire process of resolving data conflicts is recorded, including the strategies adopted, the steps taken, and the final result.

[0015] A multi-view BOM conversion system based on a single data source is characterized by comprising a data layer, a rule layer, an engine layer, and an execution layer, with the specific functions of each layer as follows: Data Layer: A master dataset is built based on a single data source to store the EBOM, PBOM, and MBOM data of the ship design and manufacturing system; the data layer adopts a distributed database to establish a unified xBOM model for the entire lifecycle, supporting concurrent access by multiple users and data version control; Rule layer: Includes a hybrid mapping rule base, a conflict resolution rule base, and a ship design-specific rule base. The rule layer stores rules in XML format and supports dynamic loading and updating.

[0016] Engine layer: Includes mapping engine, conflict resolution engine and incremental update engine. The engine layer adopts a microservice architecture and supports high concurrency processing.

[0017] Execution Layer: The transformation execution layer provides a web interface and API interface to support user interaction and system integration. It includes three core modules: EBOM parsing module, PBOM generation module, and MBOM optimization module, which realize automatic extraction of design information, process separation, structural decomposition into manufacturable units, assembly sequence planning, and dynamic adjustment of manufacturing resource allocation.

[0018] The beneficial effects of this application are: 1. This application provides a multi-view BOM conversion method and system based on a single data source, which ensures high accuracy in the conversion process according to professional electrical-specific rules and an efficient conflict resolution mechanism. Figure 1 1. Excellent consistency performance with error rate kept to an extremely low level; 2. By introducing advanced incremental update and parallel processing technologies, the time required for large-scale data transformation can be significantly shortened, resulting in high processing efficiency; 3. Modular design facilitates system upgrades and maintenance. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart of the multi-view BOM conversion method in the embodiments of this application; Figure 2 This is a schematic diagram of the Web interface in an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0022] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0023] It should be understood that the sequence number of each step in the embodiment does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0024] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0025] The features and performance of this application will be further described in detail below with reference to the embodiments.

[0026] like Figure 1 , Figure 2 As shown, the multi-view BOM conversion method based on a single data source provided in this application adopts an object-oriented data model to represent the BOM structure. This model encapsulates data and behavior, enabling each BOM node to not only possess static data attributes but also exhibit dynamic relationships with other nodes. Each BOM node possesses the following attributes: (1) Node ID: As a globally unique identifier, it ensures that each node can be accurately identified and referenced in a complex product structure.

[0027] (2) Node Name: A descriptive name that provides an intuitive identifier for each node, facilitating understanding and communication among engineers and technicians. The name typically reflects the node's function, location, or other key information.

[0028] (3) Node types: These include various types such as assemblies, parts, virtual parts, outsourced parts, process parts, and resources. This classification method helps to distinguish nodes of different natures, thereby enabling more refined control and optimization in design, manufacturing, and supply chain management.

[0029] (4) Attribute dictionary: A collection of attributes in key-value pairs, providing rich additional information for each node. These attributes may include size, material, cost, supplier, etc., providing necessary data support for product lifecycle management.

[0030] (5) Child Node List: Used to reference child nodes, it reflects the hierarchy and recursion of the BOM structure. The child node list clearly shows the assembly relationship and hierarchical structure of the products, providing a basis for production planning and material requirements planning.

[0031] The data storage strategy uses JSON format to support hierarchical storage and fast querying. JSON format is widely used for data exchange and storage due to its lightweight and easy-to-parse characteristics. In this system, JSON format not only ensures data readability and usability but also supports efficient processing of complex BOM structures through its structured nature.

[0032] Taking the EBOM structure of a ship's electrical system as an example: { "id": "ES001", "name": "Marine Electrical Systems", "type": "assembly", "attributes": { "systemType": "Main Power System", voltage: 440V frequency: 60Hz }, "children": [ { "id": "PS001", "name": "Power Generation System", "type": "assembly", "attributes": {...}, "children": [...] } ] The hybrid mapping rule engine forms the core component of the system, undertaking the critical tasks of converting EBOM to PBOM and PBOM to MBOM. This engine employs a rule-driven mechanism, dynamically selecting mapping rules based on differences in node type and application scenario.

[0033] The conversion from EBOM to PBOM follows these rules: 1. Virtual component deletion rules: a) Triggering condition: When the node type is identified as "virtual", it means that the node is a virtual component.

[0034] b) Operation: Once the triggering condition is met, the system will perform a deletion operation, remove the virtual node, and promote all its child nodes to the parent node level of the original virtual node.

[0035] c) Example: During the product design verification phase, the virtual nodes used for the "short-circuit analysis model" are removed when converted to PBOM, and their child nodes are directly assigned to the parent node to ensure the accuracy of PBOM.

[0036] 2. Folding rules for outsourced parts: a) Triggering condition: When the node type is identified as "outsource", it indicates that the node represents an external component.

[0037] b) Operation: The system will perform a folding operation, merging the outsourced component nodes into a single node, and adding necessary supply chain attributes such as supplier code, purchase batch and other key information during the process.

[0038] c) Example: In the PBOM, the "mainframe base" is treated as an outsourced component and is collapsed into a single node, with relevant supplier information injected to facilitate subsequent procurement and supply chain management.

[0039] 3. Electrical equipment process planning rules: a) Triggering conditions: When the node type is "electrical", "panel" or "cable", these nodes typically represent electrical equipment or its components.

[0040] b) Operation: At these nodes, the system will add specific process parameters, including but not limited to installation methods, alignment requirements, torque values, etc., to ensure the correct installation and functional realization of electrical equipment.

[0041] a) Example: For the main generator, a critical electrical device, process parameters such as "flexible base mounting" and "laser alignment" will be added to the PBOM to guide the subsequent production and installation process and ensure the accurate installation and efficient operation of the equipment.

[0042] 4. Security Specification Integration Rules: a) Triggering condition: The node has electrical characteristics b) Operation: Add safety attributes such as explosion-proof requirements and insulation class. c) Example: Add the "Fire Resistance Rating A-60" attribute to the cable system. The conversion from PBOM to MBOM follows these rules: 1. Rules for dividing electrical assembly units: a) Triggering condition: Node type is "process" b) Operation: The process unit is further subdivided into manufacturing units, such as power generation equipment installation unit, switchboard manufacturing unit, etc. c) Example: The power generation equipment installation unit is subdivided into "main generator installation" and "standby generator installation" workstations. 2. Dedicated equipment resource binding rules: a) Triggering condition: The node requires dedicated equipment. b) Operation: Bind manufacturing resources (equipment, tools, fixtures, etc.) c) Example: The main distribution board is installed and bound to both a "CNC punching machine" and a "busbar processing machine". 3. Detailed Rules for Electrical Work Instructions: a) Triggering condition: The node involves electrical installation. b) Operation: Develop detailed work instructions, including wiring sequence, terminal crimping parameters, etc. c) Example: Terminal crimping operations specify "hydraulic crimping pliers" and "IEC 60352 standard".

[0043] During data conversion, this system employs multiple strategies to address potential data conflicts and ensure data consistency and accuracy: First, it uses an attribute priority strategy, prioritizing manufacturing view parameters, followed by process view parameters, and finally design view parameters, ensuring that parameters closer to actual production needs are processed first. Simultaneously, a timestamp strategy is used to record the modification time of each parameter. When data conflicts occur, the most recently modified parameter is given higher priority, guaranteeing data real-time performance and accuracy, ensuring the latest data is reflected in the conversion results promptly. Furthermore, a business rule strategy is implemented, incorporating industry-specific rules based on industry standards for industries such as electrical engineering. For example, when processing safety-related parameters, explosion-proof requirements are prioritized, ensuring that parameters conforming to industry standards and safety specifications are given priority during data conversion.

[0044] This invention requires conflict detection, a step that involves carefully comparing the same node attributes in different views to identify potential inconsistencies.

[0045] Once a conflict is detected, it needs to be categorized. This step involves identifying three main conflict types: attribute conflicts, structural conflicts, and semantic conflicts, in order to take targeted measures to address them.

[0046] After classification, the next stage is to select a strategy. In this stage, one or more appropriate resolution strategies will be selected based on the specific type of conflict. These strategies may include manual intervention, automatic merging, or rule-based solutions.

[0047] After selecting a strategy, the next step is to resolve the conflict. In this stage, the previously chosen strategy is applied to address the actual conflict, ensuring that the node attributes across all views are consistent.

[0048] To ensure transparency and traceability throughout the process, the system will record detailed logs. These logs will document the entire conflict resolution process, including the strategies adopted, the steps taken, and the final results, providing necessary information for subsequent audit trails.

[0049] As the core component of BOM data change management, the incremental update engine ensures the consistency of multi-view data through four key steps: First, it monitors data changes in real time using trigger mechanisms to accurately capture add, delete, and modify operations, providing accurate change input for subsequent processing; second, it performs in-depth impact analysis on captured changes, identifies the scope of nodes affected by the changes, constructs an impact subtree, and clarifies the propagation path and scope of the changes; third, it implements a partial update strategy based on the impact subtree, adjusting only the affected parts of the data to avoid the performance overhead of full updates and improve data processing efficiency; finally, it maintains the data version history through the version management module, fully recording detailed information for each change, supporting data rollback to deal with accidental operations, and providing a reliable basis for audit trails.

[0050] In terms of algorithm implementation, incremental updates employ a depth-first search to traverse the affected subtrees. This traversal method efficiently covers all affected nodes with a time complexity of O(n) (where n is the number of affected nodes), ensuring the efficiency and accuracy of change propagation. The entire process, through a closed-loop design of "capture-analysis-update-trace," achieves both efficient change processing and ensures the consistency of multi-view data, providing strong support for the stable management of BOM data.

[0051] Example 1 In response to the complexity of ship electrical systems, a specialized BOM conversion process was designed to comprehensively cover the entire lifecycle management of the three major subsystems: power generation, power distribution, and cables.

[0052] In the power generation system processing, the EBOM stage defines key components such as generators and circuit breakers and their basic attributes (e.g., voltage parameters of a 750kW diesel generator) from a design perspective. The PBOM stage plans the installation process according to process rules (e.g., installation of the flexible base for laser alignment instrument calibration) and adds time estimation. The MBOM stage further links manufacturing resources (e.g., 50-ton overhead crane and laser alignment instrument-AL101) and refines them to process parameters (480-minute cycle and operator association).

[0053] The power distribution system follows the same logic, but in terms of safety regulations, the explosion-proof requirements and protection levels are strengthened. In the MBOM stage, the busbar processing and terminal crimping are precisely controlled through the association of CNC equipment.

[0054] The cable system is centered on path planning, extending from the cable type definition in the EBOM stage to the cable tray installation process in the PBOM stage, and finally completing the allocation of manufacturing resources for cutting, stripping, and crimping in the MBOM stage.

[0055] The system's underlying layer achieves O(n) time complexity for BOM tree traversal using a tree-based traversal algorithm, combined with the KMP pattern matching algorithm to accelerate rule application. A hash table is used to achieve O(1) time complexity for conflict detection. The core data structure employs a three-level design: BOMNode, Mapping Rule, and Conflict Resolution Rule, which respectively handle node attributes, mapping logic, and conflict resolution strategies. To improve efficiency, the system introduces a caching mechanism to reduce database load and optimizes memory usage through parallel processing of independent subtrees and lazy loading techniques.

[0056] In practical applications, taking the main generator DG001 as an example, its EBOM attributes are expanded by process rules in the PBOM stage, and finally form a complete manufacturing instruction including train scheduling and time recording in the MBOM stage; while the main switchboard MSB001 is integrated with CNC equipment through safety specifications, realizing closed-loop control from explosion-proof design to punching operation, verifying the scalability and practical application value of the system in complex scenarios.

Claims

1. A multi-view BOM conversion method based on a single data source, characterized in that, Includes the following steps: Step a: Input the raw data of EBOM, PBOM and MBOM from the ship design and manufacturing system, store the data in JSON format, and establish a unified xBOM model for the entire life cycle to show the BOM structure. This model encapsulates data and behavior, so that each BOM node has static attributes of the data. Step b: Load the hybrid mapping rule engine and execute the tasks of converting EBOM to PBOM and PBOM to MBOM. The mechanism is based on rules and dynamically selects mapping rules according to the differences in node type and application scenario. Step c: During the data conversion process, data consistency detection is performed. When data conflicts are detected, the conflicts are identified and classified. Based on the specific type of conflict, one or more corresponding resolution strategies are selected to solve the actual conflict problem. In step d, based on the premise of improving efficiency during the data transformation process, incremental updates are implemented in the algorithm. At the same time, the system introduces a caching mechanism to reduce the database load and optimizes memory usage through parallel processing of independent subtrees and lazy loading technology. Step e: Through the web interface and API interface, user interaction and system integration are supported, and the system generates manufacturing instructions after data analysis and processing.

2. The multi-view BOM conversion method based on a single data source according to claim 1, characterized in that, The static attributes of the BOM node mentioned in step a include the following: Node ID: As an identifier, it ensures that each node can be accurately identified and referenced in a complex product structure; Node Name: A descriptive name that reflects the node's function, location, or other key information, providing an intuitive identifier for each node to facilitate understanding and communication among engineers and technicians; Node types include various types such as assemblies, parts, virtual parts, outsourced parts, process parts, and resources, to distinguish nodes of different natures, thereby enabling more refined control and optimization in design, manufacturing, and supply chain management; Attribute dictionary: A collection of attributes in the form of key-value pairs, providing additional information for each node, including size, material, cost, and supplier, providing data support for product lifecycle management; Child node list: Used to reference child nodes, reflecting the hierarchy and recursion of the BOM structure. The child node list shows the assembly relationship and hierarchical structure of the products, providing a basis for production planning and material requirements planning.

3. The multi-view BOM conversion method based on a single data source according to claim 2, characterized in that, The mapping rules followed in step b for the EBOM to PBOM conversion are as follows: Virtual component deletion rules: When a node type is identified as virtual, it means that the node is a virtual component. Once the triggering condition is met, the system will perform a deletion operation, remove the virtual node, and promote all its child nodes to the parent node level of the original virtual node. Outsourced parts folding rules: When a node type is identified as "outsource", it indicates that the node represents an external component. The system will perform a folding operation, merging the outsourced parts nodes into a single node, and adding necessary supply chain attributes, such as supplier codes, purchase batches and other key information, in the process. Specialized equipment process planning rules When the node type is the equipment, system or component type corresponding to each profession, these nodes usually represent equipment or components of a specific professional field; on these nodes, the system will add specific process parameters required by that professional field, including but not limited to installation methods, accuracy requirements, and fastening standards, to ensure the correct installation and functional realization of the professional equipment; Security specification integration rules: When nodes have electrical characteristics, safety attributes such as explosion-proof requirements and insulation levels are added. The mapping rules followed in the PBOM to MBOM conversion are as follows: Electrical assembly unit division rules: When the node type is process, the process unit is refined into a manufacturing unit; Dedicated equipment resource binding rules: When a node requires dedicated equipment, manufacturing resources are tied to it. Detailed rules for electrical work instructions: When the node involves electrical installation, develop detailed work instructions, including wiring sequence and terminal crimping parameters.

4. The multi-view BOM conversion method based on a single data source according to claim 3, characterized in that, Step c describes resolving data conflicts, which includes the following specific details: Step c1 employs an attribute priority strategy, prioritizing manufacturing view parameters, followed by process view parameters, and finally design view parameters when processing data, ensuring that parameters that are closer to actual production needs are processed first. Step c2 uses a timestamp strategy to record the modification time of each parameter. When a data conflict occurs, the latest modified parameter is given higher priority to ensure the real-time performance and accuracy of the data, so that the latest data can be reflected in the conversion results in a timely manner. Step c3 involves using business rule strategies to implement specific industry-specific rules based on industry standards, ensuring that parameters that comply with industry standards and security criteria are given priority during data transformation.

5. The multi-view BOM conversion method based on a single data source according to claim 4, characterized in that, The types of data conflicts include attribute conflicts, structural conflicts, and semantic conflicts; the resolution strategies include manual intervention, automatic merging, and rule-based solutions.

6. The multi-view BOM conversion method based on a single data source according to claim 4 or 5, characterized in that, The incremental update mentioned in step d includes the following: Step d1 involves using trigger mechanisms to monitor data changes in real time, accurately capturing add, delete, and modify operations, and providing accurate change inputs for subsequent processing. Step d2 involves conducting an in-depth impact analysis on the captured changes, identifying the range of nodes affected by the changes and constructing an impact subtree to clarify the propagation path and scope of the changes. Step d3: Implement a local update strategy based on the affected subtree, only adjust the data in the affected part, avoid the performance overhead of full update, and improve data processing efficiency. Step d4 involves maintaining the data version history through the version management module, fully recording detailed information of each change, supporting data rollback to address accidental operations, and providing a reliable basis for audit trails.

7. The multi-view BOM conversion method based on a single data source according to claim 6, characterized in that, The in-depth impact analysis described in step d2 specifically includes the following: A depth-first search is used to traverse the affected subtrees, with a time complexity of O(n), where n is the number of affected nodes. Change handling is achieved through a closed-loop design of capture-analysis-update-trace.

8. The multi-view BOM conversion method based on a single data source according to claim 1 or 7, characterized in that, The generation of manufacturing instructions in step e involves automatically extracting design information, separating processes, decomposing the structure into manufacturable units, planning assembly sequences, and dynamically adjusting the allocation of manufacturing resources.

9. The multi-view BOM conversion method based on a single data source according to claim 5 or 7, characterized in that, The process of resolving data conflicts is recorded, including the strategies adopted, the steps taken, and the final result.

10. A system employing the multi-view BOM conversion method based on a single data source as described in claim 7, characterized in that, It includes a data layer, a rules layer, an engine layer, and an execution layer. The specific functions of each layer are as follows: Data Layer: A master dataset is built based on a single data source to store the EBOM, PBOM, and MBOM data of the ship design and manufacturing system; the data layer adopts a distributed database to establish a unified xBOM model for the entire lifecycle, supporting concurrent access by multiple users and data version control; Rule layer: Includes a hybrid mapping rule base, a conflict resolution rule base, and a ship design-specific rule base. The rule layer stores rules in XML format and supports dynamic loading and updating.

11. Engine Layer: Includes mapping engine, conflict resolution engine and incremental update engine. The engine layer adopts a microservice architecture and supports high concurrency processing.

12. Execution Layer: The transformation execution layer provides a web interface and API interface to support user interaction and system integration. It includes three core modules: EBOM parsing module, PBOM generation module, and MBOM optimization module, which realize automatic extraction of design information, process separation, structural decomposition into manufacturable units, assembly sequence planning, and dynamic adjustment of manufacturing resource allocation.

Images