An identification marking and changing method based on a configuration management mode

By adopting a configuration management model in aero-engine design, separating management attributes from drawing and document data, establishing independent identification forms, and automatically generating change notices, the problems of repetitive work and increased costs caused by a large number of change orders are solved, and efficient identification management and technical status control are achieved.

CN122114847APending Publication Date: 2026-05-29AECC SHENYANG ENGINE RES INST

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
AECC SHENYANG ENGINE RES INST
Filing Date
2026-02-10
Publication Date
2026-05-29

AI Technical Summary

Technical Problem

In the current design of aero engines, a large number of change orders are required at key stages such as model transitions, resulting in repetitive mechanical work, increased manpower and management costs, and low visibility of important changes, which is not conducive to technical status control.

Method used

The configuration-based management model separates the management attributes of the engineering dataset, such as type, batch, stage, and maturity status identifiers, from the drawing and document data. An independent identifier form is established for centralized management, and the system automatically generates and issues change notices to achieve automatic synchronization and management of identifiers.

Benefits of technology

It reduced the number of change orders, saved human resources, simplified the processing flow, improved the efficiency of identifying and managing important changes, and supported the effective control of the technical status of aero engines.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122114847A_ABST
    Figure CN122114847A_ABST
Patent Text Reader

Abstract

The application belongs to the technical field of aero-engines, and particularly relates to an identification mark and a changing method based on a configuration management mode. Step S10: management attribute separation and identification establishment. Type, batch, stage, maturity state identification, baseline identification class management attributes of an engineering data set EDS are separated from graphic document data, and an independent identification form is established in a management system to perform centralized management. Step S20: identification change process execution. A DMU administrator receives a change requirement and prepares an identification change application form, associates a change object with the application form to generate a change object list. After the change application form is signed and filed, the management system automatically generates and issues a change notice form for each change object, and automatically modifies related identification to realize system synchronization.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application belongs to the field of aero-engine technology, and specifically relates to a method for identification, marking and modification based on configuration management mode. Background Technology

[0002] Since the 1980s, changes to aero-engine design drawings have primarily been based on HB 5614.4-1987, "Aero-engine Design Drawing Management and Change System." The basic principle is that any change to any drawing document requires a change order, which must be fully signed. However, for changes in management attributes such as stage markings, especially at critical junctures like model transitions, designers must initiate modifications to stage markings on a large number of drawings individually, and the manufacturing unit must implement these changes accordingly. This results in repetitive, mechanical work, increased manpower and management costs, and offers no significant benefit to engine development.

[0003] Furthermore, with the deepening application of information technology in the aero-engine design process, the concept of configuration management has emerged for model development. This involves a gradual shift from batch management to configuration-based unit management. By constructing a full Bill of Materials (BOM) and configuring its effectiveness, the extraction and application of the individual unit's BOM can be achieved, making it more convenient, faster, and more efficient to obtain structural information. It also facilitates the construction, control, querying, and sharing of configurations. Change management is the driving force behind batch and unit effectiveness; therefore, the change management model must also adapt to the new situation.

[0004] The specific disadvantages of the existing technology are as follows:

[0005] 1. At specific stages such as model transition, a large number of change orders need to be issued, including one-to-one changes to some management information in drawings and documents. The manufacturing department needs to issue corresponding process changes, which consumes a lot of manpower and time costs for the design unit and increases the implementation costs for downstream contractors.

[0006] 2. The process of preparing, approving, archiving and issuing change orders with a large number of identical changes is mechanical and repetitive, consuming a lot of manpower and time, and failing to improve the R&D level of designers.

[0007] 3. Modification of management attributes such as stage identifiers and type is unrelated to the model's technical status, but there is no clear distinction between them and changes involving the technical status, resulting in low visibility of important changes and hindering technical status control. Summary of the Invention

[0008] To address the aforementioned problems, this application provides a method for identification, marking, and modification based on configuration management patterns, the method comprising the following steps:

[0009] Step S10: Separate and establish management attributes. Separate the management attributes of the engineering dataset EDS, such as type, batch, stage, maturity status, and baseline, from the drawing and document data. Establish an independent identification form in the management system for centralized management.

[0010] Step S20: The identification change process is executed. The DMU administrator receives the change request and prepares the identification change application form. The change object is associated with the application form to generate a list of change objects. After the change application form is signed and archived, the management system automatically generates and issues change notification forms for each change object and automatically modifies the relevant identifications to achieve system synchronization.

[0011] Preferably, in step S10, the display interface of the identification form includes management attribute information such as type, batch, stage, maturity status identification, and baseline identification, and centrally displays the current status of each management attribute in the form of a form.

[0012] Preferably, in step S20, the basic process of the identifier change includes:

[0013] The DMU administrator receives the identifier change request information and determines the change content based on the collected change requests;

[0014] Prepare a signage change application form, clarify the reasons for the change, identify the objects involved in the change, and generate a list of change objects;

[0015] After initiating the change request process and completing the signing and archiving, the system will automatically generate a change notification form and send it to the relevant units.

[0016] The system modifies the identifiers according to the change objects and content specified in the change request, and achieves synchronization across multiple unit systems.

[0017] Preferably, it also includes a specific method for changing the model batch identifier:

[0018] Step S31: The system records the reference relationships of components in the EBOM and displays the application model and batch list in the identification form;

[0019] Step S32: When the EBOM reference relationship changes, the system automatically refreshes the model batch list in the identification form and generates a change notification form based on the published "Add Component" or "Remove Component" information.

[0020] Preferably, the process for changing the model batch identifier specifically includes:

[0021] Changes in EBOM reference relationships, EBOM archive release, system lookup of reference relationship changes, system generation of change notifications, distribution of change notifications, system modification of model batch tags, and system synchronization of model batch tags.

[0022] Preferably, it also includes a specific method for changing the maturity status indicator, the principles of which include:

[0023] Modifications to maturity status indicators should be made progressively higher, and changes from higher to lower levels are not permitted.

[0024] The changes apply to EDS and its subordinate components.

[0025] When referenced by multiple models, the identifier inherits the highest level.

[0026] The change process includes: receiving requirements, determining the content of the change, sorting out information, preparing a change application, executing the approval process, automatically generating and issuing a change notification form, and modifying and synchronizing the identifier.

[0027] Preferably, the maturity status indicator change process specifically includes:

[0028] The DMU administrator receives change request information based on EDS status, determines the content of the change, sorts out the objects involved in the change, prepares a change application form, initiates the approval process, the system generates a change notification form, the change notification is issued, the system modifies the maturity status identifier, and the system synchronizes the maturity status identifier.

[0029] Preferably, the management attributes include at least one of type, batch, stage, maturity status identifier, and baseline identifier.

[0030] Preferably, the change notification is automatically generated by the system based on a preset template, and includes information about the object of the change, the content of the change, the reason for the change, and the effective time.

[0031] The advantages and beneficial effects of this invention are as follows:

[0032] 1. The identification and modification method based on configuration management provided by this invention manages stage markers and other identifiers separately by decoupling them from the dataset, reducing the number of change orders, increasing the automatic transmission process of the system, reducing human intervention, and saving human resources;

[0033] 2. The identification and modification method based on configuration management provided by this invention can distinguish the type of modification from the design source. After receiving the identification change notification, the manufacturing unit can clearly identify the content of the modification, simplify the processing flow of such modifications, and save management costs.

[0034] 3. The identification and modification method based on configuration management provided by this invention can distinguish identification changes, enabling designers to focus on important technical status changes, which is more conducive to the technical status management of aero-engines. Attached Figure Description

[0035] Figure 1 This is a flowchart of the model batch change process;

[0036] Figure 2 This is a flowchart of the process for changing the maturity status indicator. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below with reference to the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The described embodiments are only a part of the embodiments of this application, not all of them. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without creative effort are within the scope of protection of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings. The purpose of this invention is to provide a method for identification marking and modification based on configuration management, as follows.

[0038] For the management attributes of type, batch, stage, maturity status identifier, and baseline identifier, the document is separated from the diagram. The EDS is used as the management unit to simplify the control process of identifier changes. The DMU administrator manages them uniformly. These identifiers can be displayed in the system in the form of an identifier form.

[0039] Basic process of logo change

[0040] The basic process includes applying for a change of identification and notifying the applicant of the change. The general process is as follows:

[0041] a) The DMU administrator receives the identifier change request information and determines the change content based on the collected change request information;

[0042] b) Prepare a signage change application form, clearly stating the reasons for the change, identifying the objects to be changed, and associating the objects to be changed with the change application to generate a list of objects to be changed;

[0043] c) Initiate a change request process. After the change request is completed, signed, and archived, the system will generate a change notification form for each change object. After the change notification form is generated, the system will issue it to the relevant units.

[0044] d) After the change application is completed, signed and archived, the system modifies the identifier according to the change object and content determined in the change application, and synchronizes it with other unit systems.

[0045] e) Method for changing model and batch identification

[0046] The system records the EBOM reference relationships of components and displays a list of all archived application models and batches in the component item identification form on the collaboration platform. When the EBOM reference relationship changes, the system refreshes the application model and batch list in the component identification form based on the published "Add Component" and "Remove Component" folder associations. See Table 1 for process description.

[0047] Table 1. Model Batch Change Process Description

[0048] step Implementing department or personnel Job duties 1. Changes in EBOM reference relationships Designer Changes in the design structure may result in the addition or removal of components, causing changes in EBOM reference relationships. 2 EBOM Archive Release Designer The designer completes the initial drafting or revision of the EBOM structure and completes the review and approval process for release. 3. Search for changes in reference relationships system The system locates the component models and batches that need to be added or removed based on the published component change information. 4. Generate change notification system The system generates a change notification form for each object. See Appendix D for change notification form templates and description examples. 5. Issuance of Change Notice system Once the change notification is generated, it is frozen by the system and distributed to the relevant units. 6. Modification of Model Batch Marking system System modification of model batch marking 7. Model batch marking synchronization system The system synchronously updates the model and batch marking information of the issuing units.

[0049] Other methods of changing logos

[0050] The methods for changing stage markers, maturity status markers, and baseline markers are similar. The following explanation uses the change of maturity status markers as an example to illustrate the change method.

[0051] Maturity status indicators are indicators determined based on the maturity level of the design scheme. They are used for change control of EDS at different maturity levels, and are hereinafter referred to as maturity status indicators. Maturity status indicators are divided into four states based on the maturity level of the design scheme: Release Completed, First Article Qualification, Performance Testing Begins, and Performance Testing Completed. The change principles are as follows:

[0052] a) The order of maturity status indicators is "Completed issuance", "Passed first article inspection", "Started performance testing", and "Passed performance testing". Modifications to the indicators should be made at each level, and it is not allowed to change from a higher level to a lower level.

[0053] b) The change of maturity status identifier applies to EDS and its subordinate components;

[0054] c) When referenced by multiple models, changes to the maturity status indicators of EDS, components, and technical documents are uniformly inherited from the highest level;

[0055] d) After the contractor completes the first piece inspection, it should promptly report the relevant status information through the collaborative platform.

[0056] See the process for changing the maturity status indicator. Figure 2 The process description is shown in Table 2.

[0057] Table 2. Description of the Maturity Status Identifier Change Process

[0058] step Implementing department or personnel Job duties 1. Receive change requests DMU Administrator The DMU administrator receives change request information based on the EDS status. 2. Determine the content of the changes DMU Administrator The DMU administrator determines the content of the changes based on the project's development progress and technical status control requirements. 3. Organize the relevant materials DMU administrator-related professional departments The DMU administrator identified the affected entities and confirmed the changes with relevant professionals. 4. Prepare a change application DMU Administrator The DMU administrator prepares an identifier change request form, clearly stating the reasons for the change, and associates the changed objects with the change request to generate a list of changed objects. 5. Approval of Change Request DMU administrator, relevant professional department head, chief (deputy chief) engineer, user representative The DMU administrator initiates a change request process, and according to the model approval requirements, selects relevant professional departments for countersigning and the chief (deputy chief) engineer for approval as needed. 6. Generate change notification system After the change request is completed, signed, and archived, the system will generate a change notification form for each changed object. See Appendix D for change notification form templates and description examples. 7. Issuance of Change Notice system Once the change notification is generated, it is frozen by the system and distributed to the relevant units. 8. Modification of maturity status indicator system After the change request is completed, signed, and archived, the system will modify the maturity status indicator according to the change objects and contents specified in the change request. 9. Synchronization of maturity status indicators system Maturity status identifiers issued by the system to the unit

[0059] The system automatically changes the maturity status identifiers of EDS-affiliated components.

[0060] The advantages and beneficial effects of this invention are as follows:

[0061] 1. The identification and modification method based on configuration management provided by this invention manages stage markers and other identifiers separately by decoupling them from the dataset, reducing the number of change orders, increasing the automatic transmission process of the system, reducing human intervention, and saving human resources;

[0062] 2. The identification and modification method based on configuration management provided by this invention can distinguish the type of modification from the design source. After receiving the identification change notification, the manufacturing unit can clearly identify the content of the modification, simplify the processing flow of such modifications, and save management costs.

[0063] 3. The identification and modification method based on configuration management provided by this invention can distinguish identification changes, enabling designers to focus on important technical status changes, which is more conducive to the technical status management of aero-engines.

[0064] 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 method for identification, marking, and modification based on configuration management patterns, characterized in that, The method includes the following steps: Step S10: Separate and establish management attributes. Separate the management attributes of the engineering dataset EDS, such as type, batch, stage, maturity status, and baseline, from the drawing and document data. Establish an independent identification form in the management system for centralized management. Step S20: The identification change process is executed. The DMU administrator receives the change request and prepares the identification change application form. The change object is associated with the application form to generate a list of change objects. After the change application form is signed and archived, the management system automatically generates and issues change notification forms for each change object and automatically modifies the relevant identifications to achieve system synchronization.

2. The identification, marking, and modification method based on configuration management pattern according to claim 1, characterized in that, In step S10, the display interface of the identification form includes management attribute information such as type, batch, stage, maturity status identification, and baseline identification, and displays the current status of each management attribute in a centralized form.

3. The identification, marking, and modification method based on configuration management pattern according to claim 1, characterized in that, In step S20, the basic process of the identifier change includes: The DMU administrator receives the identifier change request information and determines the change content based on the collected change requests; Prepare a signage change application form, clarify the reasons for the change, identify the objects involved in the change, and generate a list of change objects; After initiating the change request process and completing the signing and archiving, the system will automatically generate a change notification form and send it to the relevant units. The system modifies the identifiers according to the change objects and content specified in the change request, and achieves synchronization across multiple unit systems.

4. The identification, marking, and modification method based on configuration management pattern according to claim 1, characterized in that, It also includes a specific method for changing model batch identifiers: Step S31: The system records the reference relationships of components in the EBOM and displays the application model and batch list in the identification form; Step S32: When the EBOM reference relationship changes, the system automatically refreshes the model batch list in the identification form and generates a change notification form based on the published "Add Component" or "Remove Component" information.

5. The identification, marking, and modification method based on configuration management pattern according to claim 4, characterized in that, The process for changing the model batch identifier specifically includes: Changes in EBOM reference relationships, EBOM archive release, system lookup of reference relationship changes, system generation of change notifications, distribution of change notifications, system modification of model batch tags, and system synchronization of model batch tags.

6. The identification, marking, and modification method based on configuration management pattern according to claim 1, characterized in that, It also includes a specific method for changing the maturity status indicator, and the principles for such changes include: Modifications to maturity status indicators should be made progressively higher, and changes from higher to lower levels are not permitted. The changes apply to EDS and its subordinate components. When referenced by multiple models, the identifier inherits the highest level. The change process includes: receiving requirements, determining the content of the change, sorting out information, preparing a change application, executing the approval process, automatically generating and issuing a change notification form, and modifying and synchronizing the identifier.

7. The identification, marking, and modification method based on configuration management pattern according to claim 6, characterized in that, The process for changing the maturity status identifier specifically includes: The DMU administrator receives change request information based on EDS status, determines the content of the change, sorts out the objects involved in the change, prepares a change application form, initiates the approval process, the system generates a change notification form, the change notification is issued, the system modifies the maturity status identifier, and the system synchronizes the maturity status identifier.

8. The identification, marking, and modification method based on configuration management pattern according to claim 1, characterized in that, The management attributes include at least one of type, batch, stage, maturity status identifier, and baseline identifier.

9. The identification, marking, and modification method based on configuration management pattern according to claim 1, characterized in that, The change notification is automatically generated by the system based on a preset template and includes information about the object of the change, the content of the change, the reason for the change, and the effective time.