Aero-engine design data management method

Abstract

The application belongs to the field of aviation turbine fan engines, and particularly relates to an aviation engine design data management method. The method comprises the following steps: step one, obtaining mission task authorization information requirements, and formulating a task according to an engine research and development process; step two, establishing a process data structure according to the task; step three, performing compliance determination on the process data structure; step four, determining a result data structure; step five, establishing a mapping relationship between the process data structure and the result data structure; step six, performing compliance checking on the mapping relationship, and returning to step two to reestablish the process data structure if the checking fails; step seven, storing engine design data according to a set storage information table; step eight, automatically searching the storage information table, and updating upper associated data in the storage information table according to the engine design data; and step nine, automatically extracting result data from the storage information table according to process data in the engine design data and the mapping relationship.

Description

TECHNICAL FIELD

[0001] The application belongs to the field of aero turbine fan engines, and particularly relates to an aero engine design data management method. BACKGROUND

[0002] An aero engine is a highly complex and precise thermodynamic mechanical structure, and the design process is a repeated iteration process. After overall, compressor, turbine, combustion chamber, control system and other components and systems are designed, design iteration often occurs, and a large amount of design data is formed in the whole design process.

[0003] At present, in the aero engine development process, the management of result data is mainly performed, and the design data in the design process is managed by each professional designer. The design data is dispersed in each professional for management. In the aero engine development process, multiple result schemes are formed after multiple iterations, the process data of scheme iteration is lost, the stored data lacks correlation, the input / output is not obvious, the searching is difficult, the traceability is poor, the non-directly correlated input and output data often cannot find the scheme source, finally, the engine technology state control is poor due to the mismatching of upstream and downstream schemes, which leads to the overturning of the final design scheme. In addition, in the aero engine design review, the aero engine design data management method cannot be traced forward, the design data can only be traced backward from the downstream to the upstream, the traceability is poor, a large amount of human resources needs to be spent to find the design data, human resources are wasted, and the engine development efficiency is affected.

[0004] Therefore, it is desirable to have a technical solution to overcome or at least alleviate at least one of the above-mentioned defects of the prior art. SUMMARY

[0005] The purpose of the present application is to provide an aero engine design data management method to solve at least one problem existing in the prior art.

[0006] The technical solution of the present application is:

[0007] An aero engine design data management method, comprising:

[0008] Step one, obtaining mission task authorization information requirements, formulating a task according to an engine research and development process;

[0009] Step two, establishing a process data structure according to the task;

[0010] Step three, performing compliance determination on the process data structure;

[0011] Step four, determining a result data structure;

[0012] Step five, establishing a mapping relationship between the process data structure and the result data structure;

[0013] Step six, check the mapping relationship for compliance, if the check fails, return to step two to re-establish the process data structure;

[0014] Step seven, store the engine design data according to the set storage information table;

[0015] Step eight, automatically search the storage information table, and update the upper layer associated data in the storage information table according to the engine design data;

[0016] Step nine, automatically extract result data from the storage information table according to the process data in the engine design data and the mapping relationship.

[0017] In at least one embodiment of the present application, in step one, each task according to the engine development process includes input data and output data of the task.

[0018] In at least one embodiment of the present application, in step two, the process data structure is established according to the relationship between the input data and the output data of the task.

[0019] In at least one embodiment of the present application, in step three, the judgment principle for the compliance determination of the process data structure is:

[0020] Uniqueness check: in the process data structure, the name or number of the output data has uniqueness;

[0021] Rationality check: according to the time sequence attribute relationship of the task, check that the completion time of the output data cannot be earlier than the completion time of the input data.

[0022] In at least one embodiment of the present application, in step four, the design data as a technical state control in engine development is taken as result data, and the result data structure is determined hierarchically according to the result data and the internal relationship of the result data.

[0023] In at least one embodiment of the present application, in step six, when the process data in the process data structure contains all the result data in the result data structure, it is considered that the check is passed.

[0024] In at least one embodiment of the present application, in step seven, the storage information table includes data number, data name, data version, previous input data, and upper layer associated data.

[0025] The present application has at least the following beneficial technical effects:

[0026] The aero-engine design data management method of the application can comprehensively manage all aero-engine design data in the design process, realize management of aero-engine multi-version and multi-scheme design data, improve engine technical state control quality; can realize two-way tracing of design data, provide a basis for automatic search of informationized design data, reduce the time of manual search, and save human resources. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 is a flow chart of an aero-engine design data management method of an embodiment of the application;

[0028] Figure 2 is a task schematic diagram based on engine research and development process of an embodiment of the application;

[0029] Figure 3 is a process data structure schematic diagram of an embodiment of the application;

[0030] Figure 4 is a result data structure schematic diagram of an embodiment of the application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical scheme and advantages of the application clearer, the technical scheme of the embodiments of the application will be described in more detail below in combination with the drawings of the embodiments of the application. In the drawings, the same or similar notations represent the same or similar elements or elements with the same or similar functions throughout. The described embodiments are part of the embodiments of the application, not all of the embodiments. The embodiments described below by reference to the drawings are exemplary and are intended to explain the application, and cannot be understood as a limitation of the application. Based on the embodiments in the application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the application. The embodiments of the application will be described in detail below in combination with the drawings.

[0032] In the description of the application, it should be understood that the terms "center", "longitudinal", "transverse", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the purpose of facilitating the description of the application and simplifying the description, and do not indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the scope of protection of the application.

[0033] The drawings will be described below in combination with the Figures 1 to 4 The application will be further described in detail.

[0034] The application provides an aero-engine design data management method, comprising the following steps:

[0035] Step one, obtaining mission task authorization information requirements, formulating tasks according to engine research and development processes;

[0036] Step two, establishing a process data structure according to the tasks;

[0037] Step three, performing compliance determination on the process data structure;

[0038] Step four, determining a result data structure;

[0039] Step five, establishing a mapping relationship between the process data structure and the result data structure;

[0040] Step six, performing compliance checking on the mapping relationship, and if the checking fails, returning to step two to reestablish the process data structure;

[0041] Step seven, storing engine design data according to a set storage information table;

[0042] Step eight, automatically searching the storage information table, and updating upper-layer associated data in the storage information table according to the engine design data;

[0043] Step nine, automatically extracting result data from the storage information table according to process data in the engine design data and the mapping relationship.

[0044] The aero-engine design data management method provided by the application, as shown in Figure 1 the input mission task authorization related content, formulates tasks based on processes, establishes a process data structure according to tasks, performs compliance determination on the process data structure, determines a result data structure, establishes a mapping relationship, performs compliance checking on the mapping relationship, stores data according to a storage information table, automatically refreshes storage information table data, and automatically extracts result data, thereby realizing management of engine design data.

[0045] The aero-engine design data management method provided by the application first formulates tasks according to input mission task authorization information requirements based on engine research and development processes. In this embodiment, each task established according to the engine research and development processes contains design input data and output data of the task, and each task can be further decomposed as needed. After the tasks are established, a process data structure is established from design data and relationships thereof according to relationships such as input data and output data in the tasks. The compliance of the process data structure is determined through corresponding determination principles, and a process data structure meeting the compliance requirements is obtained.

[0046] In this embodiment, the determination principles for performing compliance determination on the process data structure are as follows:

[0047] Uniqueness check: in the process data structure, the name or number of output data has uniqueness;

[0048] Rationality check: according to the time sequence attribute relationship of the task, the completion time of the output data cannot be earlier than the completion time of the input data.

[0049] The aero-engine design data management method of the present application, after completing the design of the process data structure, designs the structure data structure. In the preferred embodiment of the present application, the design data required as the technical state control in the engine development is taken as the result data, and the result data structure is determined hierarchically according to the result data and the internal relationship of the result data. Among them, the result data structure can be determined with reference to the engine decomposition structure, or according to the baseline data in the engine type management. The result data structure has no certain input-output relationship.

[0050] The aero-engine design data management method of the present application, after completing the design of the process data structure and the result data structure, establishes the mapping relationship between the two, which is used to correspond the result data structure and the process data structure. Further, the mapping relationship is checked for compliance. When the process data in the process data structure contains all the result data in the result data structure, it is considered that the check is passed. If the check is not passed, the process data structure needs to be modified in step two.

[0051] The aero-engine design data management method of the present application stores the engine design data according to the set storage information table. The main attributes of the storage information table include the data number, data name, data version, previous input data, and upper associated data of the design data. The design data formed by completing the task is stored according to the process data structure, including the number, name, version, and previous input data of the design data.

[0052] The aero-engine design data management method of the present application, after completing the data storage, automatically finds the storage information table and updates the upper associated data in the storage information table. Finally, the result data is automatically extracted from the process data of the engine design according to the mapping relationship for storage management.

[0053] The aero-engine design data management method of the present application obtains the engine design data information through the above steps, realizes the management of the process data and the result data in the engine design data, and provides support for the engine design data query and the design process traceability.

[0054] In the preferred embodiment of the present application, the project task determined based on the engine development process, such as Figure 2 , contains the input-output data requirements. The established process data structure and result data structure are respectively as shown in Figure 3 , Figure 4The engine design data is generated according to a task flow, and the engine design data is stored from bottom to top. In this embodiment, the storage information table is shown in Table 1. According to the engine design data storage information, bidirectional tracing of the design process and automatic extraction of result data can be realized.

[0055] Table 1 Engine design data storage information table

[0056]

[0057]

[0058] The aero-engine design data management method of the present application can comprehensively manage all data of the design process, avoid loss of the design process data, manage data clues between multiple schemes, realize bidirectional tracing of the engine design data, save a large amount of data searching time, save human resources, effectively improve the technical state control of the engine, improve the research and development quality, and improve the research and development success rate, support engine research and design, quickly improve the research and design complete data, provide a basis for automatic management of the engine design data, and effectively improve the engine research and development efficiency.

[0059] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. An aeroengine design data management method, characterized in that, The method comprises the following steps: Step 1: obtaining mission task authorization information requirements, and formulating tasks according to an engine research and development process; Step 2: establishing a process data structure according to the tasks; Step 3: performing compliance determination on the process data structure; Step 4: determining a result data structure; Step 5: establishing a mapping relationship between the process data structure and the result data structure; Step 6: performing compliance checking on the mapping relationship, and returning to Step 2 to reestablish the process data structure if the checking fails; Step 7: storing engine design data according to a set storage information table; Step 8: automatically searching the storage information table, and updating upper associated data in the storage information table according to the engine design data; Step 9: automatically extracting result data from the storage information table according to process data in the engine design data and the mapping relationship.

2. The aeroengine design data management method of claim 1, wherein, In Step 1, each task formulated according to the engine research and development process comprises input data and output data of the task.

3. The aeroengine design data management method of claim 2, wherein, In Step 2, the process data structure is established according to a relationship between the input data and the output data of the task.

4. The aeroengine design data management method of claim 3, wherein, In Step 3, the determination principle for the compliance determination on the process data structure is as follows: Uniqueness checking: the name or number of the output data has uniqueness in the process data structure; Reasonability checking: according to a time sequence attribute relationship of the task, the completion time of the output data cannot be earlier than the completion time of the input data.

5. The aeroengine design data management method of claim 4, wherein, In Step 4, the design data serving as a technical state control in engine development is taken as the result data, and the result data structure is determined in a hierarchical manner according to the result data and an internal relationship of the result data.

6. The gas turbine engine design data management method of claim 1, wherein, In Step 6, when the process data in the process data structure contains all the result data in the result data structure, it is considered that the checking passes.

7. The aeroengine design data management method of claim 6, wherein, In Step 7, the storage information table comprises data number, data name, data version, previous input data and upper associated data.

Images