A data-driven aero-engine design process management and control method and system

Abstract

The application belongs to the field of aero-engine design and is a data-driven aero-engine design process management and control method and system, which obtains a task item, judges the current task state of the task item, then obtains the number of input data items and the number of output data items of the task item, determines the netted connection relationship, and finally adjusts the task item state according to different change types when the task state is changed; through the input and output transmission process, the design tasks between various professions are established in a netted connection relationship, and the sequence and logical relationship of technical activities can be sorted out. By using the mode of transmitting design output to the downstream in different time periods, different content depth is transmitted in different time periods, the design task promotion mode is adjusted from series to parallel, cross-professional collaborative design is realized, and the design cycle is shortened.

Description

Technical Field

[0001] This application belongs to the field of aero-engine design, and specifically relates to a data-driven aero-engine design process control method and system. Background Technology

[0002] Design process control is a crucial aspect of project management, and how to scientifically and rationally manage the progress of aero-engine design has always been a concern and challenge for research institutes. Currently, the Work Breakdown Structure (WBS) in the aero-engine design field often contains tens of thousands of items, with numerous and complex design tasks that are heavily interconnected. Therefore, timely and accurate identification of design bottlenecks and confirmation of critical tasks affecting key nodes is of paramount importance.

[0003] In the past, through joint analysis by various disciplines, a relatively simple list of design tasks, namely the Work Breakdown Structure (WBS) for aero-engine design, could be formed. The design tasks were presented in a "serial" relationship, using the initial inputs and final outputs of each task as the connection between preceding and subsequent work. Multiple judgment and confirmation steps were set up within each task. Only after each step completed its own iterative confirmation could the work of the next step begin. The overall work steps still followed a "serial" mode of nested judgment loops, proceeding step by step along a linear connection relationship.

[0004] Currently, the following drawbacks exist:

[0005] 1) The design tasks are carried out sequentially at each level. The next task can only be carried out after the previous task has completed all its own iteration confirmation. The design efficiency is too low, which affects the design cycle of aero-engines.

[0006] 2) The multi-version iteration process is uncontrolled. There is a cross-linking relationship between the two task items through the transfer of design data. If the design data is repeatedly iterated and modified and corrected, it is difficult for the downstream task items to track effectively and accurately, resulting in the design process being uncontrolled.

[0007] Therefore, how to adjust the operation mode of design tasks and improve design efficiency is a problem that needs to be solved. Summary of the Invention

[0008] The purpose of this application is to provide a data-driven method and system for controlling the design process of aero-engines, in order to solve the problem of low design efficiency caused by the serial relationship of task items in the prior art.

[0009] The technical solution of this application is: a data-driven method for controlling the design process of aero-engines, comprising:

[0010] Obtain a task item and determine its current task status. The task status includes unpublished, in progress, paused, and completed. Each task item contains at least one input data item and one output data item. Each input data item or output data item represents a design scheme.

[0011] Obtain the number of input data items and the number of output data items for the task item; determine the relationship between each input data item and at least one data item in the previous level task item; and determine the relationship between each output data item and at least one data item in the next level task item.

[0012] Determine if there is a change in task status. If so, determine the type of change. If it is determined that data is being updated, change the status of tasks that are in progress or completed to paused, and keep the status of tasks that are not published or paused unchanged. If it is determined that data is being added, keep the status of tasks that are not published, in progress, or paused unchanged, and change the status of tasks that are completed to in progress.

[0013] Preferably, before the task status changes, a task self-check is performed. If it is determined that each input data item in the task item is in place, the task item start program is executed, and the task status is adjusted to in progress. If it is determined that each output data item is completed, the task status is adjusted to completed.

[0014] Preferably, both the input data item and the output data item include a data item, a data object ID, a data object name, a data item version, an associated task node ID, and a scheme identifier; the data item stores the specific content of the corresponding scheme design, and the associated data item is determined according to the data object ID and the associated task node ID.

[0015] Preferably, when it is determined that a data update is to be performed and the current task status is paused, if the updated data item is related to the task item, the task status is adjusted to in progress; if the updated data item is unrelated to it, the previous task status of the task item is restored.

[0016] Preferably, the method for determining whether the data item is related to the current task item is as follows: retrieve the associated task node ID within the updated data item, match the data object ID of the task item with the associated task node ID, and if a match is found, it means that the updated data item is related to the current task item; otherwise, it is not related.

[0017] Preferably, the status of an unpublished task is set to the status after the task item is created and its attributes are configured, and the responsible person does not currently have the task item under their name if it is not published; the status of an ongoing task is set to the status after the task item is published, and the task item has reached the responsible person's name; the status of a paused task is set to the status of one of the multiple design inputs issuing a version change; and the status of a completed task is set to the status of all multiple design outputs being completed and archived.

[0018] Preferably, the task item includes a task ID, task name, task description, task status, planned completion time, reminder time, scheme identifier, and assigned input and output data; the assigned input item contains at least one data packet, and each data packet stores one input data item; the output data contains at least one data packet, and each data packet stores one output data item.

[0019] As one specific implementation method, a data-driven aero-engine design process control system includes:

[0020] The task status judgment module is used to determine the current task status of the task item. The task status includes unpublished, in progress, paused and completed. Each task item contains at least one input data item and one output data item. Each input data item or output data item represents a design scheme.

[0021] The task item association module is used to obtain the number of input data items and the number of output data items of the task item, determine the relationship between each input data item and at least one data item in the upper-level task item, and determine the relationship between each output data item and at least one data item in the lower-level task item.

[0022] The task status change module is used to determine whether there is a task status change. If so, it determines the type of task change. When it is determined that data is being updated, the status of tasks that are in progress or completed is changed to paused, while the status of tasks that are not published or paused remains unchanged. When it is determined that data is being added, the status of tasks that are not published, in progress, or paused remains unchanged, while the status of tasks that are completed is changed to in progress.

[0023] During the task status change process, when an input data item from the upper level is entered into a data item from the lower level, it is determined whether the input data item is the top-level file. If it is, no input is performed.

[0024] This application discloses a data-driven method and system for controlling the design process of aero-engines. It acquires a task item, determines its current task status, then obtains the number of input and output data items for that task item, establishes a network of connections, and finally adjusts the task item status according to different change types when a task status change is detected. Through the input and output transmission process, a network of connections is established between design tasks across different disciplines, enabling the identification of the sequence and logical relationships of technical activities. By utilizing a time-sharing approach to transmit design outputs downstream, different levels of content are delivered at different times, shifting the design task progression from sequential to parallel, enabling cross-disciplinary collaborative design and shortening the design cycle. Attached Figure Description

[0025] To more clearly illustrate the technical solutions provided in this application, the accompanying drawings will be briefly described below. Obviously, the drawings described below are merely some embodiments of this application.

[0026] Figure 1 This is a schematic diagram of the overall process of this application;

[0027] Figure 2 This is a schematic diagram illustrating the status definition of the task items in this application;

[0028] Figure 3 This is a schematic diagram illustrating the relationship between various tasks based on data-driven principles in this application;

[0029] Figure 4 This is a schematic diagram of the data-driven model of this application;

[0030] Figure 5 This is a schematic diagram illustrating the adjustment measures in this application;

[0031] Figure 6 Input a limiting diagram for this application. Detailed Implementation

[0032] 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.

[0033] A data-driven method for controlling the design process of aero-engines, such as Figure 1 As shown, it includes the following steps:

[0034] Step S100, as follows Figure 2 As shown, define the task state.

[0035] Obtain a task item and determine its current task status. The task status includes unpublished, in progress, paused, and completed. Each task item contains at least one input data item and one output data item. Each input data item or output data item represents a design scheme.

[0036] The status of an unpublished task is set to the status after the task item is created and its attributes are configured. If the task is not published, the responsible person does not currently have the task item. The status of an ongoing task is set to the status after the task item is published. The task item has been assigned to the responsible person. The status of a paused task is set to the status when one of the multiple design inputs has been issued a version change. The status of a completed task is set to the status when all multiple design outputs have been completed and archived.

[0037] Preferably, both input and output data items include a data item, a data object ID, a data object name, a data item version, an associated task node ID, and a scheme identifier. Each data item stores the specific content of the corresponding scheme design, and its associated data item is determined based on the data object ID and the associated task node ID. When a party reviews an input data item, they can obtain all relevant information such as the current data item's data, data description, and data version through its internal information, facilitating subsequent work.

[0038] Preferably, each task item includes a task ID, task name, task description, task status, planned completion time, reminder time, scheme identifier, assigned input items, and output data. The assigned input items contain at least one data packet, each storing one input data item. The output data contains at least one data packet, each storing one output data item. When a party reviews a corresponding task item, they can obtain all relevant and related information through the information within the task item, facilitating subsequent work.

[0039] Because the task has multiple levels with hierarchical relationships, and the design of tasks at the same level involves multiple disciplines, it is currently being carried out sequentially along a linear relationship. This application requires cross-scheme collaborative design. Step S100 is a preparatory step for task design. How to conduct data interaction across disciplines and fields is the key to this scheme design, specifically including:

[0040] Step S200: Clarify the relationship between tasks and data.

[0041] Obtain the number of input data items and the number of output data items for the task item; determine the relationship between each input data item and at least one data item in the previous level task item; and determine the relationship between each output data item and at least one data item in the next level task item.

[0042] There is at least one hierarchical relationship between each data item and the output data item. There can be 2 / 3 / 4 relationships or more. In this way, through the input and output transmission process, a network relationship is established between the tasks of various disciplines, so as to sort out the sequence and logical relationship of the tasks.

[0043] Typical network connectivity is as follows Figure 3 As shown, the input data for Task C are output data item 002 from Task A and output data item 003 from Task B. These three are linked through data. The data in Task A, Task B, and Task C can belong to the same domain or not to different domains. The relationship between them is not sequential but rather an overlapping structure. When a new task is added, Task D can be introduced. For example, data item 004 in Task D also becomes an input item for Task C. At this point, Task C can have three or more input items, supporting continuous expansion. The data flow forms the relationships between various tasks in the product design.

[0044] Data-driven model, such as Figure 4 As shown. The design inputs for Task E are output data item 1 from Task A and output data item 5 from Task C. Tasks are advanced through the transfer of input and output data items. Before a task status change, a self-check is performed. If it is determined that every input data item for a task is in place, the task start program is executed, and the task status is adjusted to "in progress." If it is determined that every output data item is completed, the task status is adjusted to "completed" to ensure the accuracy of the current task status.

[0045] By using a time-sharing approach to deliver design outputs downstream, different levels of content can be delivered at different times, shifting the design task progression from sequential to parallel, enabling cross-disciplinary collaborative design and shortening the design cycle.

[0046] Step S300: Adjust the task status according to the input.

[0047] Determine if there is a task status change. If so, determine the task item change type. If data updates are detected, change the status of tasks in progress and completed to paused, while leaving the status of unpublished and paused unchanged. If a data item is added, leave the status of tasks unpublished, in progress, and paused unchanged, while changing the status of completed tasks to in progress. For completed tasks, if any output data item is uploaded to a temporary file again, the task status will not be adjusted.

[0048] Preferably, such as Figure 5As shown, when it is determined that data updates are to be performed and the current task status is paused, if the updated data item is related to the task item, the task status is adjusted to in progress; if the updated data item is unrelated to it, the task status of the task item is restored to its previous state.

[0049] Preferably, the method for determining whether a data item is related to the current task item is as follows: retrieve the associated task node ID within the updated data item, match the data object ID of the task item with the associated task node ID, and if a match is found, it means that the updated data item is related to the current task item; otherwise, it is not related.

[0050] When updating specific data, based on the relationship between data items and task items, data from at least one set of data items is transferred to the corresponding task item to complete the update. Therefore, the update requires providing change descriptions, version information, and other details to clearly define the differences between the two versions of data and the relevant professional impact, facilitating downstream professional assessment. The parties involved can directly obtain cross-domain data update content based on the specific content of the task item.

[0051] Furthermore, to avoid widespread issues related to related updates, lower-level tasks should avoid using top-level files as design input, thus facilitating the updating and transformation of requirements. For example... Figure 6 As shown, Task E, as a subordinate task of Task A, should not use the top-level file as its design input; the top-level input can only be used as the design input for Task A.

[0052] This application obtains a task item, determines its current task status, then acquires the number of input and output data items for that task item, establishes a network of connections, and finally adjusts the task item status according to different change types when a task status change is detected. Through the input and output transmission process, a network of connections is established between design tasks of various disciplines, enabling the identification of the sequence and logical relationships of technical activities. By utilizing a time-sharing approach to transmit design outputs downstream, different levels of content are delivered at different times, shifting the design task progression from sequential to parallel, enabling cross-disciplinary collaborative design and shortening the design cycle. A task status adjustment mechanism is established: if the design input of a task is updated, the task status can be adjusted and confirmed through information technology by determining whether the specific adjustments to the design input are relevant to the task, thereby completing the corresponding improvement design activities. This ensures a one-to-one correspondence between the design input and output versions of the task, and the process is controlled.

[0053] As one specific implementation, a data-driven aero-engine design process control system employs the above-described method, including:

[0054] The task status judgment module is used to determine the current task status of the task item. The task status includes unpublished, in progress, paused and completed. Each task item contains at least one input data item and one output data item. Each input data item or output data item represents a design scheme.

[0055] The task item association module is used to obtain the number of input data items and the number of output data items of the task item, determine the relationship between each input data item and at least one data item in the upper-level task item, and determine the relationship between each output data item and at least one data item in the lower-level task item.

[0056] The task status change module is used to determine whether there is a task status change. If so, it determines the type of task change. When it is determined that data is being updated, the status of tasks that are in progress or completed is changed to paused, while the status of tasks that are not published or paused remains unchanged. When it is determined that data is being added, the status of tasks that are not published, in progress, or paused remains unchanged, while the status of tasks that are completed is changed to in progress.

[0057] During the task status change process, when an input data item from the upper level is entered into a data item from the lower level, it is determined whether the input data item is the top-level file. If it is, no input is performed.

[0058] 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 data-driven based aero-engine design process management method, characterized in that, The method comprises the following steps: acquiring a task item, judging the current task state of the task item, the task state comprising unissued, in progress, suspended and completed, each task item comprising at least one input data item and one output data item, each input data item or output data item representing a design scheme; acquiring the number of input data items and the number of output data items of the task item, determining the relationship between each input data item and at least one data item in a previous level task item, and determining the relationship between each output data item and at least one data item in a next level task item; judging whether there is a task state change, if yes, judging the task item change type, when judging that data is updated, adjusting the task state from in progress and completed to suspended, and keeping the task state from unissued and suspended unchanged; when judging that data is added, keeping the task state from unissued, in progress and suspended unchanged, and adjusting the task state from completed to in progress; the input data item and the output data item each comprise a data item, a data object ID, a data object name, a data item version, an associated task node ID and a scheme identifier; the data item stores specific contents corresponding to a scheme design, and the associated data item is determined according to the data object ID and the associated task node ID; when judging that data is updated and the current task state is suspended, if the updated data item is related to the task item, the task state is adjusted to in progress; if the updated data item is not related to the task item, the previous task state of the task item is restored; the method for judging whether the data item is related to the current task item comprises the following steps: calling the associated task node ID in the updated data item, matching the data object ID of the task item with the associated task node ID, if a matching item is found, it is indicated that the updated data item is related to the current task item; otherwise, it is indicated that the updated data item is not related to the current task item.

2. The data-driven based aero-engine design process management method of claim 1, wherein: before the task state is changed, self-checking of the task item is performed, when judging that each input data item in the task item is in place, a task item starting program is executed, and the task state is adjusted to in progress; when judging that each output data item is completed, the task state is adjusted to completed.

3. The data-driven based aero-engine design process management method of claim 1, wherein: the unissued task state is set as the state after a completed task item is created and attribute configuration, and the task item does not exist under the name of a responsible person in the unissued state; the in progress task state is set as the state after the task item is issued, and the task item has reached the name of a responsible person; the suspended task state is set as a version change of one of multiple design inputs; and the completed task state is set as that multiple design outputs are all completed and archived.

4. The data-driven based aero-engine design process management method of claim 1, wherein: the task item comprises a task ID, a task name, a task description, a task state, a planned completion time, a reminding time, a scheme identifier, acquired and allocated input items and output data; at least one data packet is arranged in the acquired and allocated input items, and one input data item is stored in each data packet; at least one data packet is arranged in the output data, and one output data item is stored in each data packet.

5. A data-driven aero-engine design process management system, adopting the method of any one of claims 1-4, characterized in that, The method comprises the following steps: A task state determining module is configured to determine the current task state of the task item, and the task state includes unissued, in progress, paused and completed. Each task item includes at least one input data item and one output data item, and each input data item or output data item represents a design scheme. A task item association module is configured to obtain the number of input data items and the number of output data items of the task item, determine the relationship between each input data item and at least one data item in the task item of the previous level, and determine the relationship between each output data item and at least one data item in the task item of the next level. A task state changing module is configured to determine whether there is a task state change. If yes, determine the task item change type. When data updating is determined, adjust the task state from in progress and completed to paused, and keep the task state from unissued and paused unchanged. When it is determined that data items are added, keep the task state from unissued, in progress and paused unchanged, and adjust the task state from completed to in progress. During the task state changing process, when the input data item of the previous level is input into the data item of the next level, determine whether the input data item is a top file. If yes, do not input.

Images