Aero-engine product research and development process system architecture model
Through the multi-level process system architecture model, the problem that existing technology cannot support complex business and coordination is solved, and the process construction and coordination of all business, all fields and all levels has been achieved, and the design and development of aircraft engine products have been improved. Management ability, strong versatility.
Patent Information
- Application Number
- CN202411033445.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-11-15
AI Technical Summary
The existing aero engine product R&D process architecture cannot effectively support product planning, technical planning, technical development and production maintenance services, and the level is not clear enough at the business level, the coordination is difficult, and there is a lack of global design and multi-component trade-off design capabilities. , the management perspective is relatively weak.
Aeroengine product R&D process architecture model including R&D business architecture layer, cross-domain collaborative process layer, field process layer, cross-professional collaborative process layer, professional process layer and basic element layer in the field is proposed, and through multi-level process design and collaborative mechanisms support project establishment, product development, design process activities and task allocation, ensuring the integrity and synergy of the process.
It has realized the construction of a process system in all business, all fields and all levels, improved the overall applicability and coordination of the process system, supported the global design of product and multi-component trade-off design capabilities, and has strong versatility to promote to other complex Product research and development.
Smart Images

Figure CN118966921A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of process architecture design, and in particular, relates to an aircraft engine product R&D process system architecture model. Background Art
[0002] The recognition of the important role of the R&D system in the field of aviation engines is gradually deepening. As the core element of the R&D system, the process system plays the role of standardizing product R&D processes and requirements and carrying R&D capabilities. The essence of system construction is the continuous in-depth construction of the R&D process.
[0003] In the early stage, the industry mainly built a process system architecture based on the product decomposition structure for the R&D process of each level of product objects. Specifically, it is manifested as a "double V model", including the architecture V model and the entity V model. The architecture V model reflects the hierarchical structure of the engine product structure, namely the system layer, subsystem layer, and component layer. The entity V model reflects the entire R&D process of "demand, technical indicators, design and development, manufacturing, verification, and confirmation" of R&D objects at each level. The entity V models are linked through the top-down decomposition of requirements and the bottom-up verification and confirmation of requirements to achieve product R&D.
[0004] In the early stage of the industry, the technical processes of R&D objects at all levels were mainly based on the "double V model". Each R&D object included various professional technical processes and capability elements. The R&D objects took over the demands put forward by the upper-level objects and put forward the demands put forward by the lower-level R&D objects. After the development of the R&D objects was completed, they were verified at each level.
[0005] The relevant disadvantages are as follows:
[0006] 1) The existing process system architecture can only support narrow product development, while product development also involves product planning, technical planning, technical development, batch production maintenance and other businesses, which the existing architecture cannot support;
[0007] 2) The existing process architecture is built based on the product decomposition structure, which reflects the physical hierarchy and composition of the product, but cannot effectively reflect the stratification and coordination of the product development process. As a result, the process built under its guidance has unclear business hierarchy and great difficulty in coordination.
[0008] 3) The existing process architecture decouples products into physical R&D objects and considers each R&D object as a whole to build processes. However, engine product development is a process of overall product design and multi-component trade-off design. The process built by this model is not conducive to improving the overall design and multi-component trade-off design capabilities.
[0009] 4) The process itself has the ability to constrain and guide the product development process and has a certain management function. The higher the top-level process, the stronger its management function. However, the existing process system architecture supports the construction of processes from a technical perspective, but the management perspective is relatively weak.
[0010] Therefore, how to establish a more comprehensive and better coordinated process system is a problem that needs to be solved. Summary of the invention
[0011] The purpose of this application is to provide an aircraft engine product R&D process system architecture model to solve the problem of fewer functions and poor coordination of the existing process system.
[0012] The technical solution of the present application is: an aircraft engine product R&D process system architecture model, including an R&D business architecture layer, a cross-domain collaborative process layer, a domain process layer, a cross-professional collaborative process layer within a domain, a professional process layer, and a basic element layer. The R&D business architecture layer is used for project establishment; the cross-domain collaborative process layer is used to determine the product development process activities according to the established project; the domain process layer is used to determine the specific design process activities according to the product development process activities; the cross-professional collaborative process layer within a domain is used to determine the specific design tasks and the required fields according to the specific design process activities, and assign the design tasks in different fields to different professions or departments; the professional process layer corresponds to the profession or department for executing specific process activities according to the received design tasks, and feeding back the design results to the cross-professional collaborative process layer within the domain; the basic element layer is used to provide corresponding capability elements to the professional process layer according to the design activities.
[0013] Preferably, the R&D business architecture layer includes multiple modules, specifically a core business layer and a domain business layer. The core business layer includes a main value business module and a business division and definition module; the domain business layer includes a domain classification and positioning module and a sub-business classification and definition module.
[0014] Preferably, the cross-domain collaborative process layer is designed using a product development swimlane chart, where the horizontal axis is the time dimension of product development, and the vertical axis is the person in charge of each field involved in product development; a number of review points are set according to the specific project establishment, and each review point has a causal relationship with each other. Only after the current review point is passed can the subsequent one or more design activities be carried out. When the design activity is completed, the review of the review point will be carried out.
[0015] Preferably, the review point is reviewed by multiple experts who score the points separately according to the specific design results and take the average value. When the average value reaches the requirement, the review point is judged to be passed.
[0016] Preferably, the domain process layer is designed using a domain process swim lane diagram. The horizontal axis of the domain process swim lane diagram is the time dimension, and is consistent with the time dimension of the corresponding product development swim lane diagram of the cross-domain collaborative process layer; the vertical axis is the main role of the R&D team in the field headed by the domain manager; different domain nodes are designed respectively, and in a certain design process activity, the corresponding domain process swim lane diagram is obtained, and the designed process swim lane diagram is evaluated by experts in the field. After the evaluation is qualified, the corresponding domain node is judged to be completed.
[0017] Preferably, the cross-professional collaborative process layer in the field is designed using a cross-professional collaborative process swim lane diagram, the horizontal axis of the cross-professional collaborative process swim lane diagram is the time dimension, which is consistent with the process corresponding to the field process layer, and the vertical axis is the profession or department of the enterprise.
[0018] Preferably, the professional process layer includes a single professional process module and a complex professional process module. The single professional process module is planned within this level according to specific process activities, and the process activity granularity is planned to the extent that it can be completed by a single person; the complex professional process module is for complex professional process activities, which are completed by multiple professionals of the same profession, and the process activity granularity is also planned to the extent that it can be completed by a single person, and each professional is assigned different tasks.
[0019] Preferably, the basic element layer includes a data module and a constraint module. The data module includes the work instructions, data templates, checklists, software and database required for the execution of each process activity; the constraint module includes the standards, systems, quality requirements and procedure documents for the execution of process activities.
[0020] The aircraft engine product development process architecture model of this application has the following advantages and benefits:
[0021] 1. Support the construction of a "full business, full field, full level" process system to ensure the integrity and coordination of process construction;
[0022] 2. Give equal emphasis to "technology and management", support the construction of different levels of processes from different perspectives, and improve the overall applicability of the process system;
[0023] 3. Emphasize the construction of collaborative processes, support the construction of cross-domain and cross-professional collaborative processes, and drive the improvement of product overall design and multi-component trade-off design capabilities;
[0024] 4. It has strong versatility and can be extended to the construction of process systems for complex product R&D in other industries. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] 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.
[0026] Figure 1 This is a schematic diagram of the overall process of this application;
[0027] Figure 2 This is a schematic diagram of the relationship between the cross-disciplinary collaborative process and the field process for this application;
[0028] Figure 3 This is a schematic diagram of the element categories of the basic element layer of this application;
[0029] Figure 4 It is the calling relationship between the various levels in this application process system. DETAILED DESCRIPTION
[0030] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0031] An aircraft engine product development process architecture model, such as Figure 1 , including R&D business architecture layer, cross-domain collaborative process layer, domain process layer, cross-professional collaborative process layer within the domain, professional process layer and basic element layer. The R&D business architecture layer is used for project establishment; the cross-domain collaborative process layer is used to determine the product development process activities according to the established project; the domain process layer is used to determine the specific design process activities according to the product development process activities; the cross-professional collaborative process layer within the domain is used to determine the specific design tasks and the required fields according to the specific design process activities, and assign the design tasks in different fields to different professions or departments; the professional process layer corresponds to the profession or department to perform specific process activities according to the received design tasks, and feedback the design results to the cross-professional collaborative process layer within the domain; the basic element layer is used to provide corresponding capability elements to the professional process layer according to the design activities, including methods, software tools, databases and standards.
[0032] The R&D business architecture layer classifies different project establishments, and classifies and layers them from a top-level management perspective to clearly define the scope, purpose, input, output and other attributes of business modules at each level, striving to present the product's R&D model in a complete and clear hierarchical manner. This is also the basis for building the following hierarchical processes.
[0033] Preferably, the classification of different projects includes product planning business, technical planning business, product development business, batch production maintenance business, etc.; at the same time, it can also undertake upper-level business, and the business modules involved in various fields include design domain business, manufacturing business, test domain business, financial domain business, etc.
[0034] Preferably, the R&D business architecture layer includes multiple modules, specifically including a core business layer and a domain business layer. The core business layer includes a main value business module and a business division and definition module; the domain business layer includes a domain classification and positioning module and a sub-business classification and definition module.
[0035] Main value business module: The main value business module involved in engine product research and development should achieve 100% coverage of the business directly related to the company's product research and development; in terms of business classification, on the one hand, it should consider and meet the military's product research and development management and control requirements; on the other hand, it should conform to the company's current or pursued business model; for aviation engine research and development, this level involves main value businesses such as product planning, technical planning, product development, technology development, batch production and maintenance.
[0036] Business division and definition module: used for phase division and definition of each main value business of the superior;
[0037] Field classification and positioning module: used to classify and define the business in various fields involved in each stage of the upper level; for aircraft engine research and development, this level involves design, manufacturing, testing, finance, service guarantee, project management and other fields;
[0038] Sub-business classification and definition module: used to further decompose the business in each field into sub-business classification and definition.
[0039] In a specific implementation, the project in the R&D business architecture layer has a "new engine R&D project" to determine the R&D stage, R&D time, R&D funds, R&D goals, etc. After approval, the project will be sent to the cross-domain collaborative process layer.
[0040] The cross-domain collaborative process layer takes over the main value business module and the business division and definition module in the R&D business architecture layer. It is used to define the cross-domain collaborative processes and requirements within the business scope, and is usually carried in the form of a product development swimlane diagram.
[0041] The cross-domain collaborative process layer is used by business leaders to manage business processes. Taking product development as an example, the product development swimlane chart is used to manage the product development process. The horizontal axis of the product development swimlane chart is the time dimension of product development, and the vertical axis is the leaders of each field involved in product development. On the one hand, the development process activities include the key tasks of the product development process, and on the other hand, they are designed based on the collaborative needs of various fields.
[0042] Preferably, the cross-domain collaborative process layer sets several review points according to the specific project establishment, and each review point has a causal relationship. Only after the previous review point is passed can the next one or more design activities be carried out. When the design activity is completed, the review of the review point is carried out. The review of the review point can be specifically that multiple experts score separately according to the specific design results and take the average value. When the average value reaches the requirement, the review point is judged to have passed.
[0043] In a specific implementation, according to the "new engine R&D project", the development process activities corresponding to the design of the cross-domain collaborative process layer include stator case R&D activities, stator blade R&D activities, compressor R&D activities, etc. Each R&D activity can set one or more review points according to the R&D sequence, and each R&D activity is assigned to different departments according to relevant majors.
[0044] The domain process layer takes over the domain classification and positioning module and sub-business classification and definition module in the R&D business architecture layer, defines the R&D process and requirements within the domain, and is usually carried in the form of a domain process swimlane diagram.
[0045] The domain process layer is used to control the use of business processes in its main domain. It is a refinement of the corresponding domain process swimlane diagram in the cross-domain collaborative process layer, and supports the implementation of process activities in the corresponding domain in the cross-domain collaborative process. The horizontal axis of the domain process swimlane diagram is the time dimension, which is consistent with the time dimension of the corresponding product development swimlane diagram in the cross-domain collaborative process layer; the vertical axis is the main role of the R&D team in the domain head. The process activities are mainly determined from the perspective of the output and control of product deliverables, and the review point setting is consistent with the cross-domain collaborative process layer.
[0046] In a specific implementation, according to the stator blade R&D activities, the design domain process, test domain process and manufacturing domain process are determined respectively. For example, in the design domain process of the compressor R&D activities, compressor scheme design activities and fluid mechanics simulation verification activities are carried out. Each process determines the R&D time, R&D goals, R&D personnel and various sub-processes.
[0047] In the domain process layer, different domain nodes are designed according to different design stages. In a certain design process activity, the corresponding domain process swimlane diagram is obtained, and the designed process swimlane diagram is evaluated by experts in the field. After the evaluation is qualified, the corresponding domain node is judged to be completed.
[0048] The cross-professional collaborative process layer within the field is also carried in the form of a cross-professional collaborative process swimlane diagram.
[0049] The cross-professional collaborative process layer in the field is divided into two categories. One category is multi-professional collaborative process activities. For this type of process activities, it is necessary to build a cross-professional collaborative process swimlane diagram in the field and present it at this level. It is a supplement and refinement of the upper-level process activities, presenting the multi-professional collaborative process and the iterative design process between professions, and does not involve specific activity execution methods. The other category is single-professional process activities, which will be further refined and presented in the professional process layer.
[0050] The cross-disciplinary collaborative process layer in the field is subdivided according to the product development object. In a specific implementation, the design domain activities in the cross-disciplinary collaborative process activities in the field are carried out for the new engine method design activities. The swim lane diagram at this level includes:
[0051] Table 1 List of swimlane diagrams for the design domain “cross-disciplinary collaborative process layer” (example)
[0052]
[0053]
[0054] The horizontal axis of the swimlane chart at this level is also the time dimension, which is consistent with the process corresponding to the domain process layer. The vertical axis is the enterprise's profession or department. The design process activities are usually decomposed into tasks that can be undertaken by a single profession / department. This granularity is more conducive to the later application of the process system. When generating project plans based on the process, the process activities at this level can be directly converted into tasks that can be undertaken by the department and directly issued, which is convenient for the deployment and application of the subsequent process system. This level also uses scoring to evaluate each node.
[0055] The cross-disciplinary collaboration process is shown below: Figure 2 shown.
[0056] The professional process layer presents the R&D process within the profession. The process activities at this level are all undertaken by a single profession, so this level is carried in the form of a waterfall chart.
[0057] The professional process layer includes single professional process modules and complex professional process modules. The single professional process module is planned within this level according to specific process activities, and the granularity of process activities is planned to the extent that they can be completed by a single person; the complex professional process module is for complex professional process activities, which are completed by multiple professionals of the same profession. The specific process activities are planned within this level, and the granularity of process activities is also planned to the extent that they can be completed by a single person, and each professional is assigned different tasks.
[0058] The advantage of decomposing process activities to a granularity that can be undertaken by a single person is that in the later application of the process system, when a project plan is generated based on the process, the process activities at that level can be directly converted into tasks that can be undertaken by a single person and issued directly, which facilitates the deployment and application of the subsequent process system.
[0059] As a specific implementation method, in a new engine research and development project, a single person can carry out the compressor overall architecture design, the outer duct structure design or the fan compressor structure design.
[0060] The process is set up with multiple design nodes, each design node has a corresponding design target. The design progress is judged by obtaining the design parameters of the corresponding design nodes. For example, in the design of the outer structure, the current structural design parameters are obtained and compared with the design targets to determine whether the design target requirements are met. If so, the design node is completed and the design of the next design node is carried out; if not, the design is repeated until the design node requirements are met.
[0061] The basic element layer carries the product development process and requirements, which is essentially a sequence of process activities. This layer carries the core R&D capabilities of the underlying product. Through the decomposition of the previous levels of processes, the bottom-level process activities are decomposed to the granularity undertaken by a single professional and a single person. This level only carries the basic elements that support and constrain the execution of each process activity.
[0062] The basic element layer includes data module and constraint module. The data module includes the work instructions, data templates, checklists, software, database and other elements required for the execution of each process activity; the constraint module includes the standards, systems, quality requirements, procedure documents, etc. for the execution of process activities.
[0063] The relationship between basic requirements and various process activities is as follows Figure 3 As shown, the categories of factors can be diversified according to the previous accumulation of the enterprise.
[0064] The calling relationship between each level is as follows Figure 4 As shown, the single professional process module and the complex professional process module call the data in the basic element layer to perform corresponding process activities; the cross-professional collaborative process layer within the domain calls the data in the basic element layer and the professional process layer at the same time to perform corresponding process activities; the domain process layer calls the data in the cross-professional collaborative process layer within the domain to perform corresponding process activities; the cross-domain collaborative process layer calls the data in the domain process layer to perform corresponding process activities; the R&D business architecture layer calls the data in the cross-domain collaborative process layer to perform corresponding process activities.
[0065] Through the above design, the advantages and benefits of this application are as follows:
[0066] 1. Support the construction of a "full business, full field, full level" process system to ensure the integrity and coordination of process construction
[0067] Support the construction of a "full business" process system: covering the entire business scope of product research and development, including product planning, technical planning, product development, technical development, batch production maintenance, etc., to solve the problem of incomplete coverage of existing technical solutions;
[0068] Support the construction of a "full-field" process system: covering all areas of product development, including design, manufacturing, testing, finance, procurement, etc., to ensure the integrity of the process system coverage;
[0069] Support the construction of a "full-level" process system: covering all levels of product development, including "cross-domain collaborative process", "domain R&D process", "cross-professional collaborative process", "intra-professional R&D process", etc., while also taking into account the characteristics of existing technical solutions that "cover R&D objects at all levels of product R&D" to ensure that the stratification and coordination of the process system are clear and reasonable.
[0070] 2. Emphasis on both technology and management, support the construction of different levels of processes from different perspectives, and improve the overall applicability of the process system
[0071] Compared with the existing technical solutions that only consider the technical process of research and development, the present invention attaches equal importance to "technology and management", and constructs "business architecture layer", "cross-domain collaborative process layer" and "domain process layer" from a management perspective in response to the usage needs of users at different levels; and constructs "cross-professional collaborative process layer", "professional process layer" and "basic element layer" from a technical perspective to improve the applicability of the process system to different users.
[0072] 3. Emphasize the construction of collaborative processes, support the construction of cross-domain and cross-professional collaborative processes, and promote the improvement of product overall design and multi-component trade-off design capabilities
[0073] In response to the current problem of insufficient cross-domain and cross-professional collaborative R&D capabilities in the industry, the present invention, from the perspective of the overall product, proposes to set up a cross-domain collaborative process layer and a cross-professional collaborative process layer to carry the product's global design, multi-component trade-off design process and requirements, and drive the improvement of collaborative capabilities.
[0074] 4. It has strong versatility and can be extended to the process system construction of complex product development in other industries
[0075] The process architecture proposed in the present invention has strong versatility, especially for the research and development of complex products such as aerospace, ships, weapons, and automobiles that have the characteristics of "multi-field, multi-professional, and strong coupling", and has great value for replication and promotion.
[0076] Finally, it should be noted that: the drawings of the embodiments disclosed in the present invention only involve structures related to the embodiments disclosed in the present invention, and other structures can refer to the general design. In the absence of conflict, the same embodiment and different embodiments of the present invention can be combined with each other;
[0077] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. An aircraft engine product R&D process system architecture model, characterized by: It includes the R&D business architecture layer, the cross-domain collaborative process layer, the domain process layer, the cross-professional collaborative process layer within the domain, the professional process layer and the basic element layer. The R&D business architecture layer is used for project establishment; The cross-domain collaborative process layer is used to determine the product development process activities based on the project establishment; the domain process layer is used to determine the specific design process activities based on the product development process activities; The cross-disciplinary collaborative process layer within the field is used to determine the specific design tasks and the fields required based on the specific design process activities, and to assign the design tasks in different fields to different professions or departments; the professional process layer corresponds to the profession or department and is used to perform specific process activities based on the received design tasks, and to feed back the design results to the cross-disciplinary collaborative process layer within the field; the basic element layer is used to provide corresponding capability elements to the professional process layer based on the design activities.
2. The aircraft engine product development process architecture model according to claim 1, characterized in that: The R&D business architecture layer includes multiple modules, including a core business layer and a domain business layer. The core business layer includes a main value business module and a business division and definition module; the domain business layer includes a domain classification and positioning module and a sub-business classification and definition module.
3. The aircraft engine product development process architecture model according to claim 1, characterized in that: The cross-domain collaborative process layer is designed using a product development swimlane chart. The horizontal axis of the product development swimlane chart is the time dimension of product development, and the vertical axis is the person in charge of each field involved in product development. Several review points are set according to the specific project establishment items. There is a causal relationship between each review point. Only after the current review point is passed can one or more subsequent design activities be carried out. When the design activity is completed, the review of this review point will be carried out.
4. The aircraft engine product development process architecture model according to claim 3, characterized in that: The review point is reviewed by multiple experts who score the specific design results separately and take the average value. When the average value reaches the requirement, the review point is judged to be passed.
5. The aircraft engine product development process architecture model according to claim 1, characterized in that: The domain process layer is designed using a domain process swim lane diagram, the horizontal axis of which is the time dimension, and is consistent with the time dimension of the product development swim lane diagram corresponding to the cross-domain collaborative process layer; The vertical axis represents the main roles of the R&D team in the field supervised by the field manager; different field nodes are designed respectively, and in a certain design process activity, the corresponding field process swimlane diagram is obtained, and the designed process swimlane diagram is evaluated by experts in the field. After the evaluation is qualified, the corresponding field node is judged to be completed.
6. The aircraft engine product development process architecture model according to claim 1, characterized in that: The cross-professional collaborative process layer in the field is designed using a cross-professional collaborative process swim lane diagram. The horizontal axis of the cross-professional collaborative process swim lane diagram is the time dimension, which is consistent with the process corresponding to the field process layer, and the vertical axis is the profession or department of the enterprise.
7. The aircraft engine product development process architecture model according to claim 1, characterized in that: The professional process layer includes single professional process modules and complex professional process modules. The single professional process module is planned within this layer according to specific process activities, and the granularity of process activities is planned to the extent that they can be completed by a single person; The complex professional process module targets complex professional process activities, which are completed by multiple professionals of the same profession. The granularity of the process activities is also planned to the level that can be completed by a single person, and each professional is assigned different tasks.
8. The aircraft engine product development process architecture model according to claim 1, characterized in that: The basic element layer includes a data module and a constraint module. The data module includes the work instructions, data templates, checklists, software and database required for the execution of each process activity; the constraint module includes the standards, systems, quality requirements and procedure documents for the execution of process activities.
