Aircraft engineering data modular exchange method and system

Abstract

The invention belongs to the field of aircraft data management, and particularly relates to an aircraft engineering data modular exchange method and system.The aircraft engineering data is decomposed into a plurality of standardized function modules according to an aircraft design tree, and each function module represents a minimum unit capable of being independently designed by an aircraft; taking the data in each functional module as initial data, establishing a first batch of data, and storing the data in an engineering database; and when any modification is carried out on each functional module, adding registration of one modification batch, and uploading modification information to the functional module. Through the technical means of modular decomposition, standard labels, batch management, decoupling storage and the like, the problems of version chaos, semantic ambiguity, cross-domain delay, collaborative out-of-control and the like in aircraft engineering data interaction are systematically solved, full-link accurate circulation of data from design to manufacturing is achieved, the development efficiency and quality controllability are remarkably improved, and the development cost is reduced. And a replicable technical scheme is provided for digital collaboration of complex equipment.

Description

Technical Field

[0001] This application belongs to the field of aircraft data management, and specifically relates to a modular exchange method and system for aircraft engineering data. Background Technology

[0002] Aircraft development is a complex systems engineering project involving multiple disciplines, specialties, and units, and its core relies on the accurate flow and sharing of engineering data throughout the entire lifecycle. From conceptual design to detailed design, from parts manufacturing to complete aircraft assembly, from ground testing to airworthiness verification, engineering data such as structural design parameters, material performance indicators, process specifications, and test data generated at each stage need to be efficiently exchanged among different specialties (such as overall design, strength, avionics, and manufacturing), different systems (such as CAD / CAE tools, PLM platforms, and MES systems), and different stakeholders (OEMs, suppliers, and airworthiness authorities). However, due to limitations in technical architecture, standards systems, and collaborative models, the accuracy of current engineering data exchange generally suffers from significant deficiencies, which has become a key bottleneck restricting the improvement of development efficiency and quality control.

[0003] When design changes occur, if the latest model is only synchronized via email or shared folder without updating the associated EBOM (Bill of Materials) and process documents, the manufacturing end may produce based on the old drawings, resulting in rework (for example, more than 100 parts of a certain aircraft model were scrapped because the dimensions of the door seals were not updated in time).

[0004] When collaborating across regions (such as between the main manufacturer and overseas suppliers), due to time zone differences and communication delays, the data recipient may carry out subsequent work based on outdated versions, resulting in "data silos" and "version conflicts," ultimately requiring a significant investment of manpower for manual verification and correction.

[0005] Therefore, improving the accuracy of aircraft engineering data exchange is a problem that needs to be solved. Summary of the Invention

[0006] To address the aforementioned issues, this application provides a modular exchange method and system for aircraft engineering data, thereby resolving the problem of low accuracy in existing aircraft engineering data exchange technologies.

[0007] The technical solution of this application is: a modular exchange method for aircraft engineering data, comprising:

[0008] The aircraft engineering data is decomposed into several standardized functional modules according to the aircraft design tree. Each functional module represents the minimum unit that the aircraft can be designed independently. Each functional module is then associated with the corresponding upstream and downstream systems.

[0009] Each functional module is assigned a unique label, and all functional modules are associated according to the aircraft design tree based on these unique labels. The hierarchy and structural category of each functional module are also registered to establish an engineering database.

[0010] The data within each functional module is used as initial data to create the first batch of data, which is then stored in the project database. Whenever any modification is made to a functional module, a modification batch is added to the record, and the modification information is uploaded to the functional module. The functional module adjusts the stored content based on the modification information.

[0011] Whenever batch data changes, the function module saves the latest modified function module information and deletes the corresponding data before the modification; the modified function module is sent to the upstream and downstream systems on a regular basis.

[0012] Preferably, each of the functional modules includes one or more of the following: material data, avionics data, structural data, process data, test data, and modified batch data; the functional modules of the same component may have one or more of these.

[0013] Preferably, when each functional module needs to be modified, a functional modification request is initiated in the engineering database; after the request is approved, the functional module is copied to the corresponding applicant's location; after the applicant redesigns and modifies the module, the data in the functional module is directly modified, and the functional modules from the previous batch are replaced.

[0014] Preferably, during the modification process of a certain functional module, all modification applications for that functional module except for the applicant making the modification are frozen until the current applicant completes the replacement of the current functional module.

[0015] Preferably, the upstream system includes a data management module, a modification management module, and a data interaction module; the data management module includes an engineering database and a decoupling database; the functional modules are stored in the decoupling database, and each functional module is decoupled from the others within the decoupling database.

[0016] The modification management module can register each R&D personnel, and each R&D personnel can apply for R&D projects, call and modify functional modules; the data interaction module can call communication protocols; there are multiple downstream systems, and when any downstream system transmits data with the upstream system, the data interaction module calls the corresponding communication protocol to receive the data.

[0017] Preferably, after the functional modules are stored in the decoupled database, the corresponding address information is output, all the address information is organized to obtain an address information table, and the address information table is associated with each individual tag; when extracting functional modules, the individual tags of the extracted functional modules are converted into address information through the address information table for individual extraction.

[0018] Preferably, the modification management module marks the functional modules associated with each R&D personnel. When the downstream system transmits modification suggestions, the data interaction module receives the corresponding modification suggestions and sends them to the modification management module. The modification management module sends the corresponding modification suggestions and functional modules to the corresponding R&D personnel according to the relationship between the R&D personnel and the functional modules. The R&D personnel then conduct further R&D and modification of the corresponding functional modules according to the modification suggestions.

[0019] Preferably, when a new design goal is received from the upper level of any design tree, the functional modules associated with the design goal are retrieved through the engineering database, and the design goal is assigned to each functional module. Then, it is sent to each R&D personnel, who redesign the structure within the functional modules according to the new design goal.

[0020] Preferably, when a downstream system performs system-level verification on a certain upper-level system, it obtains the system-level verification requirements from the upstream system, and then combines multiple functional modules of the same component under the system according to the output parameters to obtain one or more systems that meet the requirements. The combined one or more system solutions are then sent to the downstream system. After the downstream system selects a solution, all relevant functional modules are sent to the corresponding downstream system.

[0021] Another technical solution of this application is: a modular exchange system for aircraft engineering data, comprising:

[0022] The functional decomposition module is used to decompose aircraft engineering data into several standardized functional modules according to the aircraft design tree. Each functional module represents the minimum unit that the aircraft can be designed independently. Each functional module is associated with the corresponding upstream and downstream systems.

[0023] The engineering database creation module is used to set a unique label for each functional module, associate all functional modules according to the aircraft design tree based on the unique labels, and register the level and structure category corresponding to each functional module to create an engineering database.

[0024] The function call module is used to use the data within each function module as initial data to create the first batch of data and store it in the project database; when any modification is made to each function module, a modification batch is added to the registration and the modification information is uploaded to the function module; the function module adjusts the stored content according to the modification information.

[0025] The function sending module is used to save the latest modified function module information and delete the corresponding data before the modification whenever batch data changes; and to send the modified function module to the upstream and downstream systems on a regular basis.

[0026] The modular exchange method and system for aircraft engineering data in this application have the following advantages:

[0027] By decomposing aircraft engineering data into "standardized functional modules" according to the design tree and establishing a unified labeling system to associate the design tree hierarchy with structural categories, atomic data splitting and semantic alignment are achieved. This avoids interaction errors caused by mixed data formats or semantic ambiguity in traditional models.

[0028] By employing modular decomposition, standardized labeling, batch management, and decoupled storage technologies, the system systematically addresses issues such as "version confusion, semantic ambiguity, cross-domain delays, and loss of collaborative control" in aircraft engineering data interaction. This enables precise data flow across the entire chain from design to manufacturing, significantly improving development efficiency and quality controllability, and providing a replicable technical solution for digital collaboration in complex equipment. Attached Figure Description

[0029] Figure 1 This is a schematic diagram of the overall process of this application. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages 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 drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are only some, not all, of the embodiments of this application. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this 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. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0031] The first aspect of this application provides a modular exchange method for aircraft engineering data, capable of stable data exchange between upstream and downstream systems, such as... Figure 1As shown, the specific steps include the following:

[0032] Step S100: Decompose the aircraft engineering data into several standardized functional modules according to the aircraft design tree. Each functional module represents the minimum unit that the aircraft can be designed independently. Then associate each functional module with the corresponding upstream and downstream systems.

[0033] Each functional module includes one or more of the following: material data, avionics data, structural data, process data, test data, and modification batch data; the same component may have one or more functional modules. Structural data includes structural data, drawings, EBOM, etc.

[0034] The upstream system comprises systems related to aircraft research and development, while the downstream system comprises systems used for manufacturing, testing, etc., and involves different stakeholders.

[0035] Functional modules are those that can be independently developed or manufactured.

[0036] Step S200: Set a separate label for each functional module, associate all functional modules according to the aircraft design tree based on the separate labels, and register the level and structural category corresponding to each functional module to establish an engineering database.

[0037] By setting individual tags, the design content of each functional module can be sent to the downstream system for manufacturing or verification. When the downstream system provides feedback, it can identify the corresponding functional module by marking the corresponding tag, which is quite convenient. The engineering database can allocate and retrieve functional modules so that the corresponding functional modules can be retrieved when verifying or developing the system or the whole machine.

[0038] The upstream system includes a data management module, a modification management module, and a data interaction module; the data management module includes an engineering database and a decoupling database; the functional modules are stored in the decoupling database, and each functional module is decoupled from the others within the decoupling database.

[0039] The modification management module can register each R&D personnel, and each R&D personnel can apply for R&D projects, call and modify functional modules; the data interaction module can call communication protocols; there are multiple downstream systems, and when any downstream system transmits data with the upstream system, the data interaction module calls the corresponding communication protocol to receive the data in order to adapt to different systems.

[0040] By managing functional modules, we can prevent confusion in the calls.

[0041] Preferably, after the functional modules are stored in the decoupled database, the corresponding address information is output, all the address information is organized to obtain an address information table, and the address information table is associated with each individual tag; when extracting functional modules, the individual tags of the extracted functional modules are converted into address information through the address information table for individual extraction.

[0042] Step S300: Use the data in each functional module as initial data to create the first batch of data and store it in the project database; when any modification is made to each functional module, add a modification batch registration and upload the modification information to the functional module; the functional module adjusts the stored content according to the modification information.

[0043] A single modification to a functional module does not represent an official release. Rather, it is a modification made to that functional module when any issues are discovered upstream or downstream, and this modification batch is recorded separately. This modification batch runs concurrently with the official release, and a functional module within each official release may have one or more modification batches.

[0044] When modifications are needed for each functional module, a functional modification request is initiated in the project database. After the request is approved, the functional module is copied to the corresponding applicant's location. After the applicant redesigns and modifies the module, the data in the functional module is directly modified, and the functional modules from the previous batch are replaced to prevent errors or omissions.

[0045] During the modification process of a certain functional module, all modification requests for that module, except for the original applicant, are frozen until the current applicant completes the replacement of the current functional module. This is to prevent simultaneous modifications to the same functional module, which could lead to modification confusion and the inability to find the correct functional module.

[0046] Step S400: Whenever batch data changes, the function module saves the latest modified function module information and deletes the corresponding data before the modification; the modified function module is sent to the upstream and downstream systems periodically.

[0047] Both upstream and downstream systems may modify functional modules. When a downstream system finds that the design goals cannot be achieved or the upstream system proposes new design goals, it can assign the specific design goals to the corresponding functional modules.

[0048] Preferably, the modification management module marks the functional modules associated with each developer. When a downstream system transmits modification suggestions, the data interaction module receives the corresponding suggestions and sends them to the modification management module. The modification management module then sends the corresponding modification suggestions and functional modules to the relevant developers based on the relationship between the developers and the functional modules. The developers then re-develop and modify the corresponding functional modules according to the modification suggestions. This ensures orderly invocation and prevents simultaneous invocation of the same functional module.

[0049] Upon receiving a new design goal from the upper level of any design tree, the functional modules associated with that design goal are retrieved from the engineering database, and the design goal is assigned to each functional module. Then, it is sent to each R&D personnel, who redesign the structure within the functional modules according to the new design goal.

[0050] The above design ensures that no confusion will occur when design changes take place.

[0051] Preferably, when a downstream system performs system-level verification on a certain upper-level system, it obtains the system-level verification requirements through the upstream system, and then combines multiple functional modules of the same component under the system according to the output parameters to obtain one or more systems that meet the requirements. The combined one or more system solutions are then sent to the downstream system. After the downstream system selects a solution, all relevant functional modules are sent to the corresponding downstream system, thereby enabling the overall invocation of the system or the whole machine.

[0052] As one specific implementation, an aircraft engineering data modular exchange system includes:

[0053] The functional decomposition module is used to decompose aircraft engineering data into several standardized functional modules according to the aircraft design tree. Each functional module represents the minimum unit that the aircraft can be designed independently. Each functional module is associated with the corresponding upstream and downstream systems.

[0054] The engineering database creation module is used to set a unique label for each functional module, associate all functional modules according to the aircraft design tree based on the unique labels, and register the level and structure category corresponding to each functional module to create an engineering database.

[0055] The function call module is used to use the data within each function module as initial data to create the first batch of data and store it in the project database; when any modification is made to each function module, a modification batch is added to the registration and the modification information is uploaded to the function module; the function module adjusts the stored content according to the modification information.

[0056] The function sending module is used to save the latest modified function module information and delete the corresponding data before the modification whenever batch data changes; and to send the modified function module to the upstream and downstream systems on a regular basis.

[0057] In summary, this application has the following advantages:

[0058] By decomposing aircraft engineering data into "standardized functional modules" according to the design tree and establishing a unified labeling system to associate the design tree hierarchy with structural categories, atomic data splitting and semantic alignment are achieved. This avoids interaction errors caused by mixed data formats or semantic ambiguity in traditional models.

[0059] By employing modular decomposition, standardized labeling, batch management, and decoupled storage technologies, the system systematically addresses issues such as "version confusion, semantic ambiguity, cross-domain delays, and loss of collaborative control" in aircraft engineering data interaction. This enables precise data flow across the entire chain from design to manufacturing, significantly improving development efficiency and quality controllability, and providing a replicable technical solution for digital collaboration in complex equipment.

[0060] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A modular exchange method for aircraft engineering data, characterized in that, include: The aircraft engineering data is decomposed into several standardized functional modules according to the aircraft design tree. Each functional module represents the smallest unit that the aircraft can be designed independently. And associate each functional module with its corresponding upstream and downstream systems; Each functional module is assigned a unique label, and all functional modules are associated according to the aircraft design tree based on these unique labels. The hierarchy and structural category of each functional module are also registered to establish an engineering database. The data within each functional module is used as initial data to create the first batch of data, which is then stored in the project database. Whenever any modification is made to a functional module, a modification batch is added to the record, and the modification information is uploaded to the functional module. The functional module adjusts the stored content based on the modification information. Whenever batch data changes, the function module saves the latest modified function module information and deletes the corresponding data before the modification; the modified function module is sent to the upstream and downstream systems on a regular basis.

2. The modular exchange method for aircraft engineering data as described in claim 1, characterized in that, Each of the aforementioned functional modules includes one or more of the following: material data, avionics data, structural data, process data, test data, and modified batch data; the same component may have one or more of the aforementioned functional modules.

3. The modular exchange method for aircraft engineering data as described in claim 2, characterized in that, When modifications are needed for each functional module, a functional modification request is initiated in the project database. After the request is approved, the functional module is copied to the corresponding applicant's location. After the applicant redesigns and modifies the module, the data in the functional module is directly modified, and the previous batch of functional modules is replaced.

4. The modular exchange method for aircraft engineering data as described in claim 3, characterized in that, During the modification process of a certain functional module, all modification requests for that functional module, except for the applicant making the modification, are frozen until the current applicant completes the replacement of the current functional module.

5. The modular exchange method for aircraft engineering data as described in claim 4, characterized in that, The upstream system includes a data management module, a modification management module, and a data interaction module; the data management module includes an engineering database and a decoupling database; the functional modules are stored in the decoupling database, and each functional module is decoupled from the others within the decoupling database. The modification management module can register each R&D personnel, and each R&D personnel can apply for R&D projects, call and modify functional modules; the data interaction module can call communication protocols; there are multiple downstream systems, and when any downstream system transmits data with the upstream system, the data interaction module calls the corresponding communication protocol to receive the data.

6. The modular exchange method for aircraft engineering data as described in claim 5, characterized in that, After the functional modules are stored in the decoupled database, the corresponding address information is output. All the address information is organized to obtain an address information table, and the address information table is associated with each individual tag. When extracting a functional module, the individual tags of the extracted functional module are converted into address information through the address information table for individual extraction.

7. The modular exchange method for aircraft engineering data as described in claim 5, characterized in that, The modification management module marks the functional modules associated with each R&D personnel. When the downstream system transmits modification suggestions, the data interaction module receives the corresponding modification suggestions and sends them to the modification management module. The modification management module sends the corresponding modification suggestions and functional modules to the corresponding R&D personnel according to the relationship between the R&D personnel and the functional modules. The R&D personnel then conduct further R&D and modification of the corresponding functional modules according to the modification suggestions.

8. The modular exchange method for aircraft engineering data as described in claim 7, characterized in that, Upon receiving a new design goal from the upper level of any design tree, the functional modules associated with that design goal are retrieved from the engineering database, and the design goal is assigned to each functional module. Then, it is sent to each R&D personnel, who redesign the structure within the functional modules according to the new design goal.

9. The modular exchange method for aircraft engineering data as described in claim 2, characterized in that, When a downstream system performs system-level verification on a certain upper-level system, it obtains the system-level verification requirements from the upstream system, and then combines multiple functional modules of the same component under the system according to the output parameters to obtain one or more systems that meet the requirements. The combined one or more system solutions are sent to the downstream system. After the downstream system selects a solution, all relevant functional modules are sent to the corresponding downstream system.

10. A modular exchange system for aircraft engineering data, employing the method described in any one of claims 1-9, characterized in that, include: The functional decomposition module is used to decompose aircraft engineering data into several standardized functional modules according to the aircraft design tree. Each functional module represents the minimum unit that the aircraft can be designed independently. And associate each functional module with its corresponding upstream and downstream systems; The engineering database creation module is used to set a unique label for each functional module, associate all functional modules according to the aircraft design tree based on the unique labels, and register the level and structure category corresponding to each functional module to create an engineering database. The function call module is used to use the data within each function module as initial data to create the first batch of data and store it in the project database; when any modification is made to each function module, a modification batch is added to the registration and the modification information is uploaded to the function module; the function module adjusts the stored content according to the modification information. The function sending module is used to save the latest modified function module information and delete the corresponding data before the modification whenever batch data changes; and to send the modified function module to the upstream and downstream systems on a regular basis.

Images