A method for exporting an EBOM report

Abstract

This application belongs to the field of aircraft data management, and particularly relates to a method for exporting EBOM reports. The method includes: Step S1, receiving an EBOM export task sent by a client through a master node; Step S2, distributing computing tasks; Step S3, connecting to an LCA database through a slave node and extracting the underlying data of the LCA database according to the object identifier OID; Step S4, performing a hierarchical depth-first traversal on the extracted underlying data, mapping structured data objects to an EBOM linked list temporary storage area according to attributes, and completing structured conversion of unstructured data through an object parsing engine; Step S5, temporarily storing the EBOM data that has completed structured conversion and recombination in the form of a linked list, and synchronizing it to the local file system at a set time interval; Step S6, the master node merges the outputs of the slave nodes that have completed the tasks. This application improves the efficiency of EBOM report export by the master node performing load balancing and task distribution, and the slave node performing asynchronous computing.

Description

Technical Field

[0001] This application belongs to the field of aircraft data management, and particularly relates to a method for exporting EBOM reports. Background Art

[0002] EBOM (Engineering Bill of Materials) is the source data for product development, running through various stages such as conceptual design, computational analysis, detailed design, and manufacturing. It is the carrier for the transfer and sharing of product data throughout its entire life cycle, and also the bridge and data medium for information connection among various units involved in product R & D.

[0003] EBOM usually appears as a tree - like data structure, reflecting the parent - child relationship of components. It is a technical document describing the product structure, defining the structural relationship between product components, sub - components, parts, and even raw materials. It is the source of the Process BOM (PBOM) and Manufacturing BOM (MBOM) required for engineering development.

[0004] The general steps for generating EBOM are as follows:

[0005] Step 1. The system receives an EBOM calculation instruction.

[0006] Step 2. The system connects to the corresponding database according to the product identifier and establishes a long - term connection.

[0007] Step 3. The system traverses the PBS according to the depth - first rule and extracts the underlying data according to the data identifier (oid).

[0008] Step 4. If a structured data object is traversed, perform an associated query on the data object to obtain associated information such as materials, standard parts, and usage locations; if an unstructured data object is traversed, record its metadata.

[0009] Step 5. Calculate, integrate the query results and record them in the EBOM file in sequence. If the PBM traversal is not completed, jump back to Step 3 to continue the calculation.

[0010] Existing EBOM generation solutions rely on relational database queries and structured data object aggregation at the hardware level. For structures such as aircraft design that cover a large number of materials, there are the following problems in exporting EBOM reports:

[0011] a) The number of single - aircraft materials can reach hundreds of thousands, and the overall time consumption for EBOM calculation and generation is relatively long. During the execution process, it is easy for calculation tasks to fail due to factors such as database connection timeouts, network fluctuations, and disk failures.

[0012] b) The aircraft EBOM is mainly constructed based on the CATIA model. In addition to structured information in the model, there is a large amount of unstructured data in the assembly model and pipeline model. The traditional EBOM generation method based on database query can only extract structured data, resulting in low data integrity and quality. Summary of the Invention

[0013] To solve the above problems, the present application provides an EBOM report export method, which mainly includes:

[0014] Step S1: Receive the EBOM export task sent by the client through the master node and add it to the calculation task queue;

[0015] Step S2: Calculate the task queue load of each slave node through the master node and distribute the calculation tasks;

[0016] Step S3: Connect to the LCA database through the slave node, and extract the underlying data of the LCA database according to the product decomposition structure interval and data dictionary assigned by the master node by object identifier OID;

[0017] Step S4: Each slave node performs a depth-first traversal of the extracted underlying data, maps the structured data objects to the EBOM linked list temporary storage area according to attributes, and completes the structured conversion of the unstructured data through the object parsing engine;

[0018] Step S5: Each slave node temporarily stores the EBOM data that has completed structured conversion and recombination in the form of a linked list and synchronizes it to the local file system at a set time interval;

[0019] Step S6: The master node merges the outputs of the slave nodes that have completed the tasks.

[0020] Preferably, step S2 includes: reading the working status logs of each slave node from the cluster operation logs, and sorting them in descending order according to the task queue load of each node. The cluster includes one master node and multiple slave nodes.

[0021] Preferably, step S2 further includes that the master node distributes the calculation tasks according to the product decomposition structure and the working status of each slave node, and records the task assignment node, start time, and running status in the task monitoring queue for monitoring the task execution status.

[0022] Preferably, in step S3, the slave node connects to the LCA database through the persistent layer connection pool.

[0023] Preferably, in step S4, the structured conversion of the unstructured data through the object parsing engine includes:

[0024] Loading the parsing program of the unstructured data object from the preset parsing rule pool;

[0025] Invoke the developer tool for the unstructured data object to instantiate the sub-assembly and fastener information included in the unstructured data object into sub-objects.

[0026] Preferably, the parsing rule pool stores unstructured data object meta-information, and the meta-information includes category names, file formats, and parsing program configuration items.

[0027] Preferably, in step S5, the set time interval is 30 seconds.

[0028] Preferably, in step S6, the master node polls the execution status of each slave node task in the task monitoring queue to determine whether each slave node task is completed.

[0029] In this application, the master node performs load balancing and task distribution, and the slave nodes perform asynchronous calculations, converting the synchronous sequential report generation process into a distributed asynchronous extraction-transformation-loading process, endowing the system with the ability of horizontal expansion and improving the EBOM report export efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 is a flowchart of the EBOM report export method of this application.

[0031] Figure 2 is this application Figure 1 system architecture diagram of the illustrated embodiment. DETAILED DESCRIPTION

[0032] To make the purpose, technical solutions, and advantages of the implementation of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below with reference to the accompanying drawings in the embodiments of this application. In the drawings, the same or similar reference numerals denote the same or similar elements or elements with the same or similar functions from beginning to end. The described embodiments are some but not all of the embodiments of this application. The embodiments described below by referring to the drawings are exemplary and are intended to explain this application and should not be construed as limiting this application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of this application without creative efforts shall fall within the scope of protection of this application. The embodiments of this application will be described in detail below with reference to the drawings.

[0033] The present invention proposes an EBOM report export method, as Figure 1 shown, mainly including:

[0034] Step S1: Receive the EBOM export task sent by the client through the master node and add it to the calculation task queue;

[0035] Step S2: The master node calculates the task queue loads of each slave node and distributes computing tasks.

[0036] Step S3: The slave nodes connect to the LCA database, and according to the product breakdown structure interval and data dictionary assigned by the master node, extract the underlying data of the LCA database by object identifier OID.

[0037] Step S4: Each slave node performs a hierarchical depth-first traversal on the extracted underlying data, maps the structured data objects to the EBOM linked list temporary storage area according to attributes, and completes the structured conversion of the unstructured data through the object parsing engine.

[0038] Step S5: Each slave node temporarily stores the EBOM data that has completed structured conversion and recombination in the form of a linked list and synchronizes it to the local file system at a set time interval.

[0039] Step S6: The master node merges the outputs of the slave nodes that have completed the tasks.

[0040] This application adopts a master-slave cluster architecture solution. The master node is identified as Master, and the slave nodes are identified as Follwer. The cluster receives the computing tasks initiated by the user through the master node, establishes a connection with the underlying database of the LCA system through the persistent layer connection pool, and the overall architecture is as Figure 2 shown. The main responsibilities of the master node in the system are: receiving the EBOM report export request sent by the client; querying the cluster running status; load balancing and task distribution; distributing the unstructured object parsing program. The main responsibilities of the slave nodes are: obtaining the required data objects through the persistent layer in the data object cache pool indexed by OID; the object parsing engine contains the object parsing program synchronized from the master node and is responsible for parsing the unstructured data according to the data type; the linked list temporary storage area is responsible for storing the parsed structured tree data.

[0041] In this embodiment, the EBOM report export is divided into a synchronous stage and an asynchronous stage (synchronous means that when an interface call occurs, the calling party needs to wait for the return result to continue executing the subsequent program; asynchronous means that the calling party can execute the subsequent program without waiting for the return result). The master node is responsible for the task distribution and data aggregation work in the synchronous stage, and the slave nodes are responsible for performing data extraction, conversion, and loading work. Steps S1 - S2 are the synchronous stage, steps S3 - S5 are the asynchronous stage, and step S6 is the synchronous stage.

[0042] In some alternative embodiments, step S2 includes: reading the working status logs of each slave node from the cluster running logs, sorting them in descending order according to the task queue loads of each node, and using them as alternative computing resources. The cluster includes one master node and multiple slave nodes.

[0043] In some alternative embodiments, step S2 further includes that the master node distributes computing tasks according to the product breakdown structure and the working status of each slave node, and records the task assignment node, start time, and running status in the task monitoring queue for monitoring the task execution status.

[0044] In some alternative embodiments, in step S4, the structured conversion of unstructured data by the object parsing engine includes:

[0045] Loading the parsing program for the unstructured data object from the preset parsing rule pool;

[0046] Invoking the developer tool of the unstructured data object to instantiate the sub-assembly and fastener information included in the unstructured data object into sub-level objects.

[0047] In this embodiment, referring to Figure 2 , the parsing rule pool is stored in the master node and contains parsing rules for various models such as self-made parts, pipeline black boxes, A models, and wiring harness models. For example, if the current unstructured data object is an assembly model, the assembly model parsing program is loaded, the CAA developer tool is invoked, and the sub-assembly and fastener information included in the assembly model are instantiated into sub-level objects. The parsing of other types of unstructured objects is the same.

[0048] In some alternative embodiments, the parsing rule pool stores meta-information of unstructured data objects, and the meta-information includes category names, file formats, and parsing program configuration items. In alternative embodiments, the parsing rule pool further includes several custom parsing rules. Developers write parsing programs according to the parsing interface definition rules, and after packing the compiled program files, upload them to the cluster master node.

[0049] In some alternative embodiments, in step S5, the set time interval is 30 seconds. In this embodiment, each slave node temporarily stores the EBOM data that has completed structured conversion and recombination in the form of a linked list and synchronizes it to the local file system once every 30 seconds to prevent the loss of work completed due to node failures. It can be understood that through the above method, in case of node failures, after restarting, the tasks will continue to be executed according to the local temporary files.

[0050] In some alternative embodiments, in step S6, the master node polls the task execution status of each slave node in the task monitoring queue to determine whether the tasks of each slave node are completed. In this embodiment, the outputs of the nodes that have completed the tasks are merged, and at the same time, the working status of this node in the monitoring queue is updated. After all tasks are completed, a complete EBOM report is generated.

[0051] This application converts the synchronous sequential report generation process into a distributed asynchronous extraction - transformation - loading process by having the master node perform load balancing and task distribution and the slave node perform asynchronous computing, endowing the system with the ability of horizontal expansion and improving the EBOM report export efficiency.

[0052] This application solves the problem of the overall system crash caused by the failure of a single node through a distributed EBOM report export architecture; through timed log synchronization, it ensures the immediate storage of task progress, reduces the cost of fault recovery, and improves the overall reliability of the system.

[0053] A method for processing unstructured data in aircraft design digital models using pluggable application programming interfaces is proposed. It can cover various unstructured data such as pipeline black boxes and assembly models to implement a general - purpose and extensible unstructured data parsing engine, solve the problem that various unstructured data in the design model cannot be presented in the EBOM form, and provide the system with flexible, configurable, and extensible unstructured data parsing and reconstruction capabilities.

[0054] The above are only the specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by this application should be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. An EBOM report export method, characterized in that, it includes: Step S1: Receive the EBOM export task sent by the client through the master node and add it to the calculation task queue; Step S2: Calculate the task queue load of each slave node through the master node and distribute the calculation tasks; Step S3: Connect to the LCA database through the slave node, and extract the underlying data of the LCA database according to the product decomposition structure interval and data dictionary assigned by the master node by object identifier OID; Step S4: Each slave node performs a hierarchical depth-first traversal on the extracted underlying data, maps the structured data objects to the EBOM linked list temporary storage area according to attributes, and completes the structured conversion of the unstructured data through the object parsing engine; Step S5: Each slave node temporarily stores the EBOM data that has completed structured conversion and reorganization in the form of a linked list and synchronizes it to the local file system at a set time interval; Step S6: The master node merges the outputs of the slave nodes that have completed the tasks; Among them, Step S2 includes: reading the working status logs of each slave node from the cluster operation logs, sorting them in descending order according to the task queue load of each node, and the cluster includes one master node and multiple slave nodes; the master node distributes the calculation tasks according to the product decomposition structure and the working status of each slave node, and records the task assignment node, start time, and running status in the task monitoring queue for monitoring the task execution status; In Step S4, the structured conversion of the unstructured data through the object parsing engine includes: Loading the parsing program of the unstructured data object from the preset parsing rule pool; Invoking the developer tool of the unstructured data object to instantiate the sub-assembly and fastener information included in the unstructured data object into sub-level objects.

2. The EBOM report export method according to claim 1, characterized in that, in Step S3, the slave node connects to the LCA database through the persistent layer connection pool.

3. The EBOM report export method according to claim 1, characterized in that, the parsing rule pool stores the meta-information of the unstructured data object, and the meta-information includes the category name, file format, and parsing program configuration items.

4. The EBOM report export method according to claim 1, characterized in that, in Step S5, the set time interval is 30 seconds.

5. The EBOM report export method according to claim 1, characterized in that, in Step S6, the master node polls the task execution status of each slave node in the task monitoring queue to determine whether the tasks of each slave node are completed.

Images