Aircraft engineering data model exchange method and device

Abstract

The invention provides an aircraft engineering data model exchange method and device, and belongs to the field of aircraft data management.The method comprises the steps that according to an aircraft engineering data issuing object, a product structure of an aircraft is traversed from top to bottom with a module as a unit, and a complete aircraft product data entity of the latest version in a frozen state is obtained; extracting data module object information in the data entity to construct a module structure import file; constructing a signature information import file according to the signature information of each link in the signature process extracted this time; extracting change information of all the auditing and signing objects at this time to construct a change information import file; extracting exchange object information corresponding to an aircraft top layer product structure from the module to construct a product structure import file; and according to the data entity, the change information import file, the signature information import file, the product structure import file and the module structure import file, generating a data packet for aircraft engineering data model exchange.

Description

Technical Field

[0001] The present application belongs to the field of aircraft data management, and in particular, relates to an aircraft engineering data model exchange method and device. Background Art

[0002] During the aircraft development process, aircraft engineering data transmission generally uses a unified data package to interact with each contracting unit. All externally interacting data must follow a unified format. If there is an update, the updated data can be promptly distributed to the relevant contracting units to ensure the consistency of aircraft engineering data.

[0003] The standard format of aircraft engineering data packets is divided into production drawings and production files according to data objects. When aircraft engineering data in the prior art is exchanged between different systems, it is easy to cause inconsistent data content or format, poor consistency and accuracy. Summary of the invention

[0004] The purpose of the present application is to provide an aircraft engineering data model exchange method and device to solve or alleviate at least one problem in the background technology.

[0005] On the one hand, the technical solution of the present application is: a method for exchanging aircraft engineering data models, comprising: According to the aircraft engineering data release object, traverse the aircraft product structure from top to bottom in modules to obtain the latest version of the complete aircraft product data entity in the frozen state; According to the data entity exchanged this time, the data module object information in the data entity is extracted to construct a module structure import file, which is used by the downstream contracting unit to parse and import the underlying product structure of the data; According to the review information of each link in the review process extracted this time, a review information import file is constructed to restore the review information of structured engineering instructions and module parts list in the data package. One data package corresponds to a complete review information. Extract the change information of all review objects to construct a change information import file, which is used to record the components and document information that have been changed this time; Extract the exchange object information corresponding to the top-level product structure of the aircraft from the module to construct a product structure import file, which is used by the downstream contractor to construct the internal system product structure of the downstream contractor based on the product structure import file; Generate data packages based on data entities, change information import files, review information import files, product structure import files, and module structure import files for aircraft engineering data model exchange.

[0006] Preferably, the data entity includes three-dimensional digital models, two-dimensional drawings, engineering instructions, and module parts lists of all aircraft components.

[0007] Preferably, the data module object information includes component information and assembly hierarchy relationship.

[0008] Preferably, the review information includes the review role, review personnel, review time, and review type.

[0009] Preferably, the change information includes component number, document number, and version information.

[0010] Preferably, the aircraft top-level product structure includes systems, sections, subsystems, subsystems, configuration items CI and configuration schemes CS, and the exchange object information includes component information and / or sub-component information, wherein the component information and / or sub-component information includes the number, version, attribute, name, type, life cycle status, and modification time of the component and / or sub-component.

[0011] On the other hand, the present application provides an aircraft engineering data model exchange device, comprising: The data entity construction module is used to traverse the aircraft product structure from top to bottom in modules according to the aircraft engineering data release object, and obtain the latest version of the complete aircraft product data entity in a frozen state; The module structure import file construction module is used to extract the data module object information in the data entity according to the data entity exchanged this time to construct the module structure import file, which is used by the downstream contracting unit to parse and import the underlying product structure of the data; The review information import file construction module is used to construct the review information import file based on the review information of each link in the review process extracted this time, and is used to restore the review information of the structured engineering instructions and module parts list in the data package. One data package corresponds to a complete review information. The change information import file construction module is used to extract the change information of all review objects to construct a change information import file, which is used to record the components and document information that have been changed this time; The product structure import file construction module is used to extract the top-level product structure information of the aircraft from the module to construct the product structure import file, which is used by the downstream contractor to construct the internal system product structure of the downstream contractor based on the product structure import file; The data package construction module is used to generate data packages based on data entities, change information import files, review information import files, product structure import files and module structure import files for aircraft engineering data model exchange.

[0012] Preferably, the data entity includes three-dimensional digital models, two-dimensional drawings, engineering instructions, and module parts lists of all aircraft components.

[0013] Preferably, the data module object information includes component information and assembly hierarchy relationship.

[0014] Preferably, the review information includes the review role, review personnel, review time, and review type.

[0015] Preferably, the change information includes component number, document number, and version information.

[0016] Preferably, the aircraft top-level product structure includes systems, sections, subsystems, subsystems, configuration items CI and configuration schemes CS, and the exchange object information includes component information and / or sub-component information, wherein the component information and / or sub-component information includes the number, version, attribute, name, type, life cycle status, and modification time of the component and / or sub-component.

[0017] In a third aspect, the present application provides an electronic device, including: one or more processors; Memory; One or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more application programs are configured to implement the aircraft engineering data model exchange method as described in any one of the above items.

[0018] In the final aspect, the present application provides a computer-readable storage medium, which stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the aircraft engineering data model exchange method as described in any one of the above items.

[0019] The aircraft engineering data model exchange method provided by this application follows the idea of ​​a unique data source, and follows a certain standard format when exchanging data across systems, which can ensure the accuracy and uniqueness of data in different systems. This application solves the problem of inconsistent formats when engineering data is exchanged between different systems, and ensures the consistency and accuracy of engineering data flowing across systems throughout the life cycle of aircraft development. This application improves the efficiency and quality of model development and reduces development costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solution provided by the present application, the following is a brief introduction to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present application.

[0021] Figure 1 This is a schematic diagram of the composition of data packets in the aircraft engineering data model exchange method of the present application.

[0022] Figure 2 Schematic diagram of the aircraft engineering data model exchange device of the present application.

[0023] Figure 3 Schematic diagram of an electronic device according to an embodiment of the present application. Detailed implementation manners

[0024] To make the purpose, technical solutions, and advantages of the implementation of the present application clearer, the technical solutions in the embodiments of the present application will be described in more detail below with reference to the accompanying drawings in the embodiments of the present application.

[0025] As Figure 1 shown, the present application provides an aircraft engineering data model exchange method, including the following steps: S100: According to the aircraft engineering data distribution object, traverse the product structure of the aircraft from top to bottom in units of modules, and obtain the complete aircraft product data entity in the latest version in the frozen state.

[0026] In the present application, the data entities used for this distribution include the 3D digital models, 2D drawings, EO (Engineering Order), and MPL (Modules Parts List) of all the components of the aircraft.

[0027] S200: According to the data entities to be exchanged this time, extract the data module object information in the data entities to construct a module structure import file for the downstream manufacturing unit to parse and import the underlying product structure of the data.

[0028] The following code is the data module object information recorded in the module structure import file in the embodiment of the present application, which includes component information and assembly hierarchy relationships, etc.

[0029] <!--PDMDataFile: Product data | DataPackageNumber: Data packet number; containerName: Product container; forceSend: Whether to force retransmission --> <PDMDataFile DataPackageNumber ="" containerName="" forceSend="N"> <!--Part: Component | PartID: Component number; Revision: Edition; Version: Version --> <part partid=" " revision="" version=" "> <!-- Attributes:Component attributes --> <attributes> <!--PartName: Component Name--> <partname>< / partname> <!--PartType: Component Type (DesignPart is in-house manufactured part, StandardParts indicates standard part, EquipmentPart indicates airborne equipment)--> <parttype>< / parttype> <!--PartDesc: Component Description--> <partdesc>< / partdesc> <!--TeamID: Team ID--> <teamid>< / teamid> <!--lifecycleTemplate: Lifecycle Template--> <lifecycletemplate> MAWTPartLC< / lifecycletemplate> <!--lifecycleState: Lifecycle State--> <lifecyclestate> APPROVED< / lifecyclestate> <!--endItem: Whether it is a finished product (Y: Yes; N: No)--> <enditem>< / enditem> <!--view: View--> <view>< / view> <!--CreatedBy: Creator--> <createdby>< / createdby> <!--UpdatedBy: Modifier--> <updatedby>< / updatedby> <!--CreatedTime: Creation Time--> <createdtime>< / createdtime> <!--LastUpdated: Last Update Time--> <lastupdated>< / lastupdated> <!--Maturity: Maturity Level--> <maturity>< / maturity> <!--EffValue: Effectiveness--> <effvalue / > <!-- ibaAttr: Extended attribute | Name: Attribute name; Type: Data type --> <ibaattr Name=" " Type="String" / > Attribute value …… <ibaattr Name=" " Type="String" / > Attribute value <!-- Attributes: Component attributes --> < / attributes> <!--RelatedDocuments:Related documents --> <relateddocuments> <!--CADDocument: Model Information | DocID: Model Number; Revision: Edition; Version: Version--> <CADDocument DocID="" Revision="" Version="A"> <!—Attributes: Model Attributes--> <attributes> <!--DocName:Model Name--> <docname>< / docname> <!--CADDocType:Model Type (CADASSEMBLY for assembly / CADCOMPONENT for component / CATDrawing for 2D drawing)--> <caddoctype> CADASSEMBLY< / caddoctype> <!--CADAppType:Design Software--> <cadapptype> CATIAV5< / cadapptype> <!--TeamID:Team ID--> <teamid>< / teamid> <!--lifecycleTemplate:Lifecycle Template--> <lifecycletemplate>< / lifecycletemplate> <!--lifecycleState:Lifecycle State--> <lifecyclestate>< / lifecyclestate> <!--CreatedBy:Creator--> <createdby>< / createdby> <!--UpdatedBy:Modifier--> <updatedby>< / updatedby> <!--CreatedTime:Creation Time--> <createdtime>< / createdtime> <!--LastUpdated:Last Update Time--> <lastupdated>< / lastupdated> <!--ibaAttr:Extended Attribute|Name:Attribute Name;Type:Data Type --> <ibaattr Name=" " Type="String" / > Attribute Value …… <ibaattr Name=" " Type="String" / > Attribute Value <!-- Attributes:Model Attributes--> < / attributes> <!--DocContent: Model Content Information--> <doccontent> <!--ContentPath: Model content storage path--> <contentpath> ContentPath< / contentpath> <!--ContentFileName: Model content name--> <contentfilename>< / contentfilename> <!--ContentType: Model type--> <contenttype> Application< / contenttype> <!--ContentRole: Content role (PRIMARY indicates main content / SECONDARY indicates attachment)--> <contentrole> PRIMARY< / contentrole> < / doccontent> <!-- / DocContent: End of Model Information--> <!--WTDocument: Document Information | DocID: Document Number; Revision: Edition; Version: Version--> <WTDocument DocID="" Revision="1" Version="A"> <!-- Attributes: Document Attributes--> <attributes> <!--DocName:Document Name--> <docname>< / docname> <!--DocType:Document Type--> <doctype>< / doctype> <!--lifecycleTemplate:Lifecycle Template--> <lifecycletemplate> MAWTDocLC< / lifecycletemplate> <!--lifecycleState:Lifecycle State--> <lifecyclestate> APPROVED< / lifecyclestate> <!--CreatedBy:Creator--> <createdby>< / createdby> <!--UpdatedBy:Modifier--> <updatedby>< / updatedby> <!--CreatedTime:Creation Time--> <createdtime>< / createdtime> <!--LastUpdated:Last Update Time--> <lastupdated>< / lastupdated> <!--ibaAttr:Extended Attribute|Name:Attribute Name;Type:Data Type --> <ibaattr Name=" " Type="String" / > Attribute Value …… <ibaattr Name=" " Type="String" / > Attribute Value <!-- Attributes:Document Attributes--> < / attributes> <!—DocContent: Document Content Information--> <doccontent> <!--ContentPath: Content storage path--> <contentpath> ContentPath< / contentpath> <!--ContentFileName: File name--> <contentfilename>< / contentfilename> <!--ContentType: Type--> <contenttype> Application< / contenttype> <!--ContentRole: Content role (PRIMARY indicates main content / SECONDARY indicates attachment)--> <contentrole> PRIMARY< / contentrole> < / doccontent> <!-- / DocContent: End of Document Information--> <!-- / RelatedDocuments: End of Related Documents--> < / relateddocuments> <!--PartUses:Installation locations of each component under assembly --> <partuses> <!--Part: Components | Amount: The installation quantity of the PartID part under the current assembly; PartID: Component number--> <part amount="1" partid=""> <!--Transform: Installation position of the current part--> <transform> <m0>< / m0> <m1>< / m1> <m2>< / m2> <m3>< / m3> < / transform> < / part> < / partuses> <!--BomUses:Process route --> <bomuses> <!--Bom: Process Route | Amount: Installation Quantity; PartID: Component Number; XacRoute: Process Route--> <bom Amount="1" PartID="" XacRoute="" / > < / bomuses> < / part> ; S300. Construct a signature and review information import file based on the signature and review information of each link in the signature and review process extracted this time, which is used to restore the signature and review information of structured EO and MPL in the data packet. One data packet corresponds to a complete signature and review information.

[0030] The following code shows the signature and review information recorded in the signature and review information import file in the embodiment of the present application, including signature and review roles, signature and review personnel, signature and review time, signature and review types, etc.

[0031] <!--SignInfo: Signature and review information--> <signinfo> <!--Document: Document|SignType: Signing type--> <document signtype="审签"> <!-- Attributes: Sign-off attributes --> <attributes> <!--signinfo: Signing and review information | role: Signing and review role; user: Signing and review personnel; time: Signing and review time--> <signinfo role="编制" user=" " time="2020 / 06 / 19" / > <signinfo role="校对" user=" " time="2020 / 06 / 19" / > <signinfo role="审核" user=" " time="2020 / 06 / 19" / > <signinfo role="标审" user=" " time="2020 / 06 / 19" / > <signinfo role="工艺分发" user=" " time="2020 / 06 / 19" / > <signinfo role="批准" user=" " time="2020 / 06 / 19" / > <signinfo role="顾客代表" user=" " time="2020 / 06 / 19" / > < / attributes> <!--Document: Document--> < / document> <!--Document: Document|SignType: Signing type--> <document signtype="会签"> <!-- Attributes: Sign-off attributes --> <attributes> <!--signinfo: Signing and review information|role: Signing and review role; user: Signing and review personnel; time: Signing and review time--> <signinfo role="材料会签" user=" " time="2020 / 06 / 19" / > <signinfo role="重量会签" user=" " time="2020 / 06 / 19" / > <signinfo role="设计会签" user=" " time="2020 / 06 / 19" / > <signinfo role="强度会签" user=" " time="2020 / 06 / 19" / > < / attributes> <!--Document: Document--> < / document> <!--SignInfo: Signing information--> < / signinfo> ; S400. Extract the change information of all review objects this time to construct a change information import file, which is used to record the component and document information that has changed this time.

[0032] The following code shows the change information recorded in the change information import file in the embodiment of the present application, including component number, document number, version information, etc.

[0033] <!--ChangeInfos: Change information|DataPackageNumber: Data packet number--> <ChangeInfos DataPackageNumber=" "> <!--ChangeInfo: Change information| Module: Module number; ChangeType: Change type (New means newly issued / ChangeVersion means version change / ChangeNum means number change / RepairDM means repair / SpecialParts means special parts change / QuickChange means quick change)--> <changeinfo module=" " changetype=" "> <!--Part: Components|srcNumber: Previous number; srcVersion: Previous version; number: Revised number; version: Revised version--> <part srcNumber="" srcVersion=" " number="" version=" " / > …… <!--WTDocument: Technical document|srcNumber: Previous number; srcVersion: Previous version; number: Revised number; version: Revised version--> <WTDocumentsrcNumber=""srcVersion=" "number="" version=" " / > …… <!--EPMDocument: Model document|srcNumber: Previous number; srcVersion: Previous version; number: Revised number; version: Revised version--> <EPMDocumentsrcNumber=""srcVersion=" "number="" version=" " / > …… <!--ChangeInfos: Change information--> ; S500, Extract the exchange object information corresponding to the top - level product structure of the aircraft from the module to construct a product structure import file, which is used by downstream contractors when constructing the product structure of the downstream contractor's internal system based on this product structure import file.

[0034] In this application, the top - level product structure of the aircraft can usually be stratified according to levels such as system, section, subsystem, sub - subsystem, configuration item CI (Configuration Item, used to represent a certain design unit of the aircraft), configuration solution CS (Configuration Solution, used to represent a certain design state of the aircraft design unit), etc.

[0035] The following code is the exchange object information recorded in the product structure import file in the embodiment of this application, which includes component information and / or sub - component information. Among them, the component information and / or sub - component information includes the number, version, attributes, name, type, life - cycle status, modification time, etc. of the component and / or sub - component.

[0036] <!--PDMDataFile: Product Data | DataPackageNumber: Data Package Number; containerName: Product Container; forceSend: Whether to Force Resend--> <PDMDataFile DataPackageNumber=" " containerName="Three - level Prototype Management Library" forceSend="N"> <!--Part: Component (Model Information) | PartID: Component Number; Revision: Edition; Version: Version--> <part partid="XX" revision="1" version="A"> <!-- Attributes:Part attributes --> <attributes> <!--PartName:Part Name--> <partname> XX< / partname> <!--PartType:Part Type--> <parttype> ......< / parttype> <!--PartDesc:Part Description--> <partdesc> XX< / partdesc> <!--TeamID:Team ID--> <teamid> teamid< / teamid> <!--lifecycleTemplate:Lifecycle Template--> <lifecycletemplate> MAWTPartLC< / lifecycletemplate> <!--lifecycleState:Lifecycle State--> <lifecyclestate> RELEASED< / lifecyclestate> <!--endItem:Is it a finished product (Y: Yes; N: No)--> <enditem> N< / enditem> <!--view:View--> <view> Design< / view> <!--CreatedBy:Creator--> <createdby>< / createdby> <!--UpdatedBy:Modifier--> <updatedby>< / updatedby> <!--CreatedTime:Creation Time--> <createdtime>< / createdtime> <!--LastUpdated:Last Update Time--> <lastupdated>< / lastupdated> <!--Maturity:Maturity--> <maturity>< / maturity> <!--EffValue:Effectiveness--> <effvalue / > < / attributes> <!--PartUses:Sub-component information--> <partuses> <!--Part: Sub-component information; Amount: Installation quantity; PartID: Component number; XacRoute: Process route--> <part Amount="1" PartID="S5" XacRoute="" / > < / partuses> < / part> <!--Part: Component (Section / System Information) | PartID: Component Number; Revision: Edition; Version: Version--> <part partid="XX" revision="1" version="A"> <!-- Attributes:Part attributes --> <attributes> <!--PartName:Component Name--> <partname> Body structure< / partname> <!--PartType:Component Type--> <parttype>< / parttype> <!--PartDesc:Component Description--> <partdesc> Body structure< / partdesc> <!--TeamID:Team ID--> <teamid> teamid< / teamid> <!--lifecycleTemplate:Lifecycle Template--> <lifecycletemplate> MAWTPartLC< / lifecycletemplate> <!--lifecycleState:Lifecycle State--> <lifecyclestate> RELEASED< / lifecyclestate> <!--endItem:Is it a finished product (Y: Yes; N: No)--> <enditem> N< / enditem> <!--view:View--> <view> Design< / view> <!--CreatedBy:Creator--> <createdby>< / createdby> <!--UpdatedBy:Modifier--> <updatedby>< / updatedby> <!--CreatedTime:Creation Time--> <createdtime>< / createdtime> <!--LastUpdated:Last Update Time--> <lastupdated>< / lastupdated> <!--Maturity:Maturity Level--> <maturity>< / maturity> <!--EffValue:Effectiveness--> <effvalue / > < / attributes> <!-- PartUses:Sub-component information --> <partuses> <!--Part: Sub-component information | Amount: Installation quantity; PartID: Component number; XacRoute: Process route--> <part Amount="1" PartID="" XacRoute="" / > < / partuses> < / part> <!--Part: Component (Sub - system / Sub - subsystem Information) | PartID: Component Number; Revision: Edition; Version: Version--> <part partid="XX" revision="1" version="A"> <!-- Attributes:Part attributes--> <attributes> <!--PartName:Part Name--> <partname> Rear< / partname> <!--PartType:Part Type--> <parttype>< / parttype> <!--PartDesc:Part Description--> <partdesc> Rear< / partdesc> <!--TeamID:Team ID--> <teamid> teamid< / teamid> <!--lifecycleTemplate:Lifecycle Template--> <lifecycletemplate> MAWTPartLC< / lifecycletemplate> <!--lifecycleState:Lifecycle State--> <lifecyclestate> RELEASED< / lifecyclestate> <!--endItem:Whether it is a finished product (Y: Yes; N: No)--> <enditem> N< / enditem> <!--view:View--> <view> Design< / view> <!--CreatedBy:Creator--> <createdby>< / createdby> <!--UpdatedBy:Modifier--> <updatedby>< / updatedby> <!--CreatedTime:Creation Time--> <createdtime>< / createdtime> <!--LastUpdated:Last Update Time--> <lastupdated>< / lastupdated> <!--Maturity:Maturity--> <maturity>< / maturity> <!--EffValue:Effectiveness--> <effvalue / > < / attributes> <!--PartUses:Sub-component information--> <partuses> <!--Part: Sub-component information; Amount: Installation quantity; PartID: Component number; XacRoute: Process route--> <part Amount="1" PartID="" XacRoute="" / > < / partuses> < / part> <!--Part: Component (Configuration Item CI Information) | PartID: Component Number; Revision: Edition; Version: Version--> <part partid="" revision="1" version="A"> <!-- Attributes:Component attributes --> <attributes> <!--PartName:Part Name--> <partname> Rear< / partname> <!--PartType:Part Type--> <parttype> ......< / parttype> <!--PartDesc:Part Description--> <partdesc>< / partdesc> <!--TeamID:Team ID--> <teamid> teamid< / teamid> <!--lifecycleTemplate:Lifecycle Template--> <lifecycletemplate> MAWTPartLC< / lifecycletemplate> <!--lifecycleState:Lifecycle State--> <lifecyclestate> RELEASED< / lifecyclestate> <!--endItem:Is it a finished product (Y: Yes; N: No)--> <enditem> N< / enditem> <!--view:View--> <view> Design< / view> <!--CreatedBy:Creator--> <createdby>< / createdby> <!--UpdatedBy:Modifier--> <updatedby>< / updatedby> <!--CreatedTime:Creation Time--> <createdtime>< / createdtime> <!--LastUpdated:Last Update Time--> <lastupdated>< / lastupdated> <!--Maturity:Maturity--> <maturity>< / maturity> <!--EffValue:Effectiveness--> <effvalue / > < / attributes> <!--PartUses:Sub-component information--> <partuses> <!--Part: Sub-component information | Amount: Installation quantity; PartID: Component number; XacRoute: Process route--> <part Amount="1" PartID=" " XacRoute="" / > < / partuses> < / part> <!--Part: Component (Configuration Solution CS Information) | PartID: Component Number; Revision: Edition; Version: Version--> <part partid=" " revision="1" version="A"> <!-- Attributes:Part attributes --> <attributes> <!--PartName: Part Name--> <partname>< / partname> <!--PartType: Part Type--> <parttype> ......< / parttype> <!--PartDesc: Part Description--> <partdesc>< / partdesc> <!--TeamID: Team ID--> <teamid> teamid< / teamid> <!--lifecycleTemplate: Lifecycle Template--> <lifecycletemplate> MAWTPartLC< / lifecycletemplate> <!--lifecycleState: Lifecycle State--> <lifecyclestate> RELEASED< / lifecyclestate> <!--endItem: Whether it is a finished product (Y: Yes; N: No)--> <enditem> N< / enditem> <!--view: View--> <view> Design< / view> <!--CreatedBy: Creator--> <createdby>< / createdby> <!--UpdatedBy: Modifier--> <updatedby>< / updatedby> <!--CreatedTime: Creation Time--> <createdtime>< / createdtime> <!--LastUpdated: Last Update Time--> <lastupdated>< / lastupdated> <!--Maturity: Maturity--> <maturity>< / maturity> <!--EffValue: Effectiveness--> <effvalue / > < / attributes> <!--PartUses:Sub-component information--> <partuses> <!--Part: Sub-component information | Amount: Installation quantity; PartID: Component number; XacRoute: Process route--> <part Amount="1" PartID=" " XacRoute="" / > < / partuses> < / part> ; Step S600, generate a data package according to the data entity, change information import file, review information import file, product structure import file, and module structure import file for aircraft engineering data model exchange.

[0037] The aircraft engineering data model exchange method provided by this application follows the idea of a single data source. When data is exchanged across systems, it complies with a certain standard format, which can ensure the accuracy and uniqueness of data in different systems. This application solves the problem of inconsistent formats when engineering data is exchanged between different systems, ensuring the consistency and accuracy of engineering data flowing across systems throughout the entire life cycle of aircraft development. This application improves the efficiency and quality of model development and reduces the development cost.

[0038] On this basis, such as Figure 2 As shown, the present application provides an aircraft engineering data model exchange device 100, the device 100 comprising: The data entity construction module 101 is used to traverse the aircraft product structure from top to bottom in modules according to the aircraft engineering data distribution object, and obtain the latest version of the complete aircraft product data entity in a frozen state; The module structure import file construction module 102 is used to extract the data module object information in the data entity according to the data entity exchanged this time to construct the module structure import file, which is used by the downstream contracting unit to parse and import the underlying product structure of the data; The review information import file construction module 103 is used to construct the review information import file according to the review information of each link in the review process extracted this time. One data package corresponds to a complete review file, which is used to restore the review information of the structured engineering instructions and the module parts list in the data package; The change information import file construction module 104 is used to extract the change information of all the review objects to construct a change information import file, which is used to record the components and document information that have been changed this time; The product structure import file construction module 105 is used to extract the exchange object information corresponding to the aircraft top-level product structure from the module to construct a product structure import file, which is used by the downstream contractor to construct the product structure of the downstream contractor's internal system based on the product structure import file; The data package construction module 106 is used to generate data packages for aircraft engineering data model exchange according to data entities, change information import files, review information import files, product structure import files and module structure import files.

[0039] For the processing process or content of each module of the aircraft engineering data model exchange device of the present application, reference may be made to the aircraft engineering data model exchange method of the present application, and will not be repeated here.

[0040] like Figure 3 As shown, an embodiment of the present application further provides an electronic device 200, which includes a processing device 201, which can perform various appropriate actions and processes according to a program stored in a ROM 202 or a program loaded from a storage device 208 to a RAM 203. The processing device 201 may, for example, include a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processing device 201 may also include an onboard memory for caching purposes. The processing device 201 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present application.

[0041] In RAM 203, various programs and data required for the operation of electronic device 200 are stored. Processing device 201, ROM 202 and RAM 203 are connected to each other via bus 204. Processing device 201 performs various operations of the method flow according to the embodiment of the present application by executing the program in ROM 202 and / or RAM 203. It should be noted that the program can also be stored in one or more memories other than ROM 202 and RAM 203. Processing device 201 can also perform various operations of the method or flow according to the embodiment of the application by executing the program stored in the one or more memories.

[0042] According to an embodiment of the present application, the electronic device 200 may further include an I / O interface 205, which is also connected to the bus 204. The electronic device 200 may further include one or more of the following components connected to the I / O interface 205: an input device 206 including a keyboard, a mouse, etc.; an output device 207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage device 208 including a hard disk, etc.; and a communication device 209 including a network interface card such as a LAN card, a modem, etc. The communication device 209 performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface 205 as needed. A removable storage medium, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive as needed so that a computer program read therefrom is installed into the storage device 208 as needed.

[0043] The present application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, various operations of the above methods or processes according to the embodiments of the present application are implemented.

[0044] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.< / changeinfo>

Claims

1. A method for exchanging aircraft engineering data models, characterized in that: include: According to the aircraft engineering data release object, traverse the aircraft product structure from top to bottom in modules to obtain the latest version of the complete aircraft product data entity in the frozen state; According to the data entity exchanged this time, the data module object information in the data entity is extracted to construct a module structure import file, which is used by the downstream contracting unit to parse and import the underlying product structure of the data; According to the review information of each link in the review process extracted this time, a review information import file is constructed to restore the review information of structured engineering instructions and module parts list in the data package. One data package corresponds to a complete review information. Extract the change information of all review objects to construct a change information import file, which is used to record the components and document information that have been changed this time; Extract the exchange object information corresponding to the top-level product structure of the aircraft from the module to construct a product structure import file, which is used by the downstream contractor to construct the internal system product structure of the downstream contractor based on the product structure import file; Generate data packages based on data entities, change information import files, review information import files, product structure import files, and module structure import files for aircraft engineering data model exchange.

2. The aircraft engineering data model exchange method according to claim 1, characterized in that: The data entities include three-dimensional digital models, two-dimensional drawings, engineering instructions, and module parts lists of all aircraft components.

3. The aircraft engineering data model exchange method according to claim 1, characterized in that: The data module object information includes component information and assembly hierarchy relationship.

4. The aircraft engineering data model exchange method according to claim 1, characterized in that: The review information includes the review role, review personnel, review time, and review type.

5. The aircraft engineering data model exchange method according to claim 1, characterized in that: The change information includes component number, document number, and version information.

6. The aircraft engineering data model exchange method according to claim 1, characterized in that: The aircraft top-level product structure includes systems, sections, subsystems, subsystems, configuration items CI and configuration schemes CS, and the exchange object information includes component information and / or sub-component information, wherein the component information and / or sub-component information includes the number, version, attribute, name, type, life cycle status, and modification time of the component and / or sub-component.

7. An aircraft engineering data model exchange device, characterized in that: include: The data entity construction module is used to traverse the aircraft product structure from top to bottom in modules according to the aircraft engineering data release object, and obtain the latest version of the complete aircraft product data entity in a frozen state; The module structure import file construction module is used to extract the data module object information in the data entity according to the data entity exchanged this time to construct the module structure import file, which is used by the downstream contracting unit to parse and import the underlying product structure of the data; The review information import file construction module is used to construct the review information import file based on the review information of each link in the review process extracted this time, and is used to restore the review information of the structured engineering instructions and module parts list in the data package. One data package corresponds to a complete review information. The change information import file construction module is used to extract the change information of all review objects to construct a change information import file, which is used to record the components and document information that have been changed this time; The product structure import file construction module is used to extract the exchange object information corresponding to the top-level product structure of the aircraft from the module to construct the product structure import file, which is used by the downstream contractor to construct the internal system product structure of the downstream contractor based on the product structure import file; The data package construction module is used to generate data packages based on data entities, change information import files, review information import files, product structure import files and module structure import files for aircraft engineering data model exchange.

8. The aircraft engineering data model exchange device according to claim 7, characterized in that: The data entities include three-dimensional digital models, two-dimensional drawings, engineering instructions, and module parts lists of all aircraft components.

9. The aircraft engineering data model exchange device according to claim 7, characterized in that: The data module object information includes component information and assembly hierarchy relationship.

10. The aircraft engineering data model exchange device according to claim 7, characterized in that: The review information includes the review role, review personnel, review time, and review type.

11. The aircraft engineering data model exchange device according to claim 7, characterized in that: The change information includes component number, document number, and version information.

12. The aircraft engineering data model exchange device according to claim 7, characterized in that: The aircraft top-level product structure includes systems, sections, subsystems, subsystems, configuration items CI and configuration schemes CS, and the exchange object information includes component information and / or sub-component information, wherein the component information and / or sub-component information includes the number, version, attribute, name, type, life cycle status, and modification time of the component and / or sub-component.

13. An electronic device, characterized in that: include: one or more processors; Memory; One or more application programs are stored in the memory and configured to be executed by the one or more processors, wherein the one or more application programs are configured to implement the aircraft engineering data model exchange method according to any one of claims 1 to 6.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores: At least one instruction, at least one program, code set or instruction set, wherein the at least one instruction, the at least one program, the code set or instruction set is loaded and executed by a processor to implement the aircraft engineering data model exchange method according to any one of claims 1 to 6.

Images