Module-based aircraft simplified configuration management method

Abstract

The invention belongs to the field of aircraft data management process construction technology management, and relates to a module-based aircraft simplified configuration management method. The method comprises the following steps: creating an engineering change suggestion ECP for a configuration file in an aircraft configuration management platform ACME; calling an LCA interface to carry out number changing or version raising operation on a configuration file in the LCA; generating a change instruction ECO according to the engineering change suggestion ECP; calling an LCA interface to carry out data change on a configuration file in a lifecycle management system LCA; and checking the change execution conditions of the ECP and the configuration file in the LCA, and if the ECP and the configuration file in the LCA are consistent, importing the data in the LCA into an aircraft configuration management platform ACME for checking and signing a change instruction ECO. According to the method, the technical state management and control cost and difficulty are reduced, the engineering change in the trial-manufacturing process is completely controlled, and the engineering change efficiency is improved.

Description

Technical Field

[0001] This application belongs to the field of aircraft data management process construction technology management, specifically involving a module-based simplified aircraft configuration management method. Background Technology

[0002] Currently, aircraft development engineering data management is based on a model of 3D model + 2D drawings + supporting catalog + technical sheet / change order. The main feature is that the data status is expressed by 3D model, 2D drawings and technical sheet / change order, and the supporting catalog is used to express the aircraft status. That is, the 3D model, 2D drawings and supporting catalog express the product baseline of the aircraft, and the technical sheet and change order are supplements to the product baseline.

[0003] The limitations of this management model are mainly manifested in the following aspects: First, the static management of the supporting catalog cannot meet the needs of the process planning in the parallel development stage of models; second, the effective number of engineering changes is expressed through technical sheets / change orders, which are difficult to upload to drawings in a timely manner, affecting the management of product baseline status; third, the management of changes to related data such as borrowed parts, shared parts, and symmetrical parts is difficult, and relying on manual recording and impact analysis is inefficient and costly. Summary of the Invention

[0004] To address the aforementioned issues, this application provides a module-based simplified configuration management method for aircraft, which mainly includes:

[0005] Step S1: Create an Engineering Change Proposal (ECP) for the configuration file in the Aircraft Configuration Management Platform (ACME). The configuration file is a virtual object corresponding to the lowest-level product structure with independent characteristics and interfaces in the aircraft product structure.

[0006] Step S2: Use the WebServices service to call the LCA interface to modify or upgrade the configuration file in the LCA lifecycle management system.

[0007] Step S3: Generate change command (ECO) based on the engineering change suggestion (ECP);

[0008] Step S4: Call the LCA interface to modify the data in the configuration file of the Lifecycle Management System (LCA);

[0009] Step S5: Check the implementation status of the engineering change proposal (ECP) and the configuration file in the lifecycle management system (LCA). If they are consistent, import the data in the lifecycle management system (LCA) into the aircraft configuration management platform (ACME) for ECO approval. During the approval process, freeze the data in the lifecycle management system (LCA) and the aircraft configuration management platform (ACME).

[0010] Preferably, in step S1, the configuration file in the aircraft configuration management platform ACME includes configuration configuration items (CI), configuration specification schemes (CIS), and effectiveness design schemes (VCI). The configuration configuration item (CI) is a node in the product structure that undertakes configuration management and control. There can be multiple configuration configuration schemes (CIS) under one configuration configuration item (CI). The configuration configuration scheme (CIS) is used to reflect the configuration management of multiple specifications under the configuration configuration item (CI) and includes the complete design solution under that specification. The effectiveness design scheme (VCI) is the design solution of the configuration configuration scheme (CIS) under a specific effectiveness, including the complete information of the design solution.

[0011] Preferably, prior to step S1, the procedure further includes:

[0012] Step S01: Determine the change level of the configuration file;

[0013] Step S02: For the highest change level, issue a Change Request (ECR) for the configuration file in the aircraft configuration management platform as input for creating an Engineering Change Proposal (ECP). For other change levels, use the change opinions proposed by the manufacturing end or the design end as input for creating an Engineering Change Proposal (ECP).

[0014] Preferably, prior to step S1, the procedure further includes:

[0015] Step S03: Convert the specification validity on the configuration scheme CIS in the aircraft configuration management platform ACME into flight information, perform intersection calculation with the change flight of the validity design scheme VCI in the life cycle management system LCA, and unidirectionally synchronize the calculation result to all instances of the validity design scheme VCI in the life cycle management system LCA.

[0016] Preferably, step S2 further includes:

[0017] Based on the input change object validity information, the system automatically identifies whether the change method of the configuration file to which the change object belongs is a version upgrade or a number change. When the validity of the change object changes, the number change method is forced and traced back to the validity design scheme VCI of the configuration file. When the validity of the change object does not change, the version upgrade or number change method is used.

[0018] Preferably, step S5, the approval process for the change order (ECO) further includes:

[0019] The Engineering Change Proposal (ECP) process is used as the main process, and the Change Order (ECO) process is used as a sub-process for nested management. The ECP process is closed only after all change plans in the Engineering Change Proposal (ECP) have been implemented and issued by the Change Order (ECO).

[0020] This application reduces the cost and difficulty of technical status management, achieves complete control over engineering changes during the trial production process, and improves the efficiency of engineering changes. Attached Figure Description

[0021] Figure 1 This is a flowchart of a preferred embodiment of the modular-based aircraft simplified configuration management method of this application. Detailed Implementation

[0022] 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 some, not all, of the embodiments of this application. 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 of 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.

[0023] This application provides a module-based method for simplified aircraft configuration management, such as... Figure 1 As shown, it mainly includes:

[0024] Step S1: Create an Engineering Change Proposal (ECP) for the configuration file in the Aircraft Configuration Management Platform (ACME). The configuration file is a virtual object corresponding to the lowest-level product structure with independent characteristics and interfaces in the aircraft product structure.

[0025] Step S2: Use the WebServices service to call the LCA interface to modify or upgrade the configuration file in the LCA lifecycle management system.

[0026] Step S3: Generate change command (ECO) based on the engineering change suggestion (ECP);

[0027] Step S4: Call the LCA interface to modify the data in the configuration file of the Lifecycle Management System (LCA);

[0028] Step S5: Check the implementation status of the engineering change proposal (ECP) and the configuration file in the lifecycle management system (LCA). If they are consistent, import the data in the lifecycle management system (LCA) into the aircraft configuration management platform (ACME) for ECO approval. During the approval process, freeze the data in the lifecycle management system (LCA) and the aircraft configuration management platform (ACME).

[0029] This application, through research on simplified configuration management based on modules, adopts a modular approach to organize and manage aircraft product structures. It comprehensively considers all elements throughout the entire lifecycle of aircraft product development and, using standardization principles, decomposes aircraft products into abstract product structure objects with independent characteristics and interface structures—the configuration files in step S1—to manage aircraft product effectiveness, significantly simplifying configuration management. Furthermore, the modular product structure organization merges the design and manufacturing separation surfaces, allowing general changes to be resolved within modules, thus reducing the propagation and proliferation of changes. Through a comprehensive study of engineering change identification, control, documentation, and review, and employing an ECR+ECP+ECO change model, it supports the entire process of change initiation, impact analysis and planning, and execution control, thereby achieving modular technical status management.

[0030] Modular product organization transforms aircraft products from a traditional holistic structure to a decentralized modular structure, resulting in a flatter product structure compared to the traditionally deeply hierarchical structure. This simplifies subsequent configuration control and assembly process design, enabling modular design, production, assembly, and service. The modular configuration hierarchical management approach employs a "divide and conquer" method for configuration management. Simplified configuration management for aircraft based on modules relies primarily on the interactive development of the LCA and ACME systems. LCA is a lifecycle management system, advantageous for digital collaborative product design; ACME is an aircraft configuration management platform, a product data management system custom-developed based on PTC's Windchill platform, offering flexible processes suitable for approval, release, and change control. In the integration planning of ACME and LCA systems, LCA is used for design changes, while ACME is used for data approval, status control, and closed-loop management of the change process. Integration interfaces are accessed through Web Services to facilitate the transfer of information (data, status) between systems, thereby enabling control of the engineering change process.

[0031] Firstly, in the aircraft configuration management platform ACME, products are divided into three levels: top level, configuration level, and bottom level. For example, a branch of the top level is a certain aircraft type - fuselage - mid fuselage. The configuration level can be set under the mid fuselage, and the bottom level is under the configuration level. For example, a branch of the bottom level is assembly parts - stringer.

[0032] In some optional implementations, in step S1, the configuration file in the aircraft configuration management platform ACME includes configuration configuration items (CI), configuration specification schemes (CIS), and effectiveness design schemes (VCI). The configuration configuration item (CI) is a node in the product structure that undertakes configuration management and control. There can be multiple configuration configuration schemes (CIS) under one configuration configuration item (CI). The configuration configuration scheme (CIS) is used to reflect the configuration management of multiple specifications under the configuration configuration item (CI) and includes the complete design solution under that specification. The effectiveness design scheme (VCI) is the design solution of the configuration configuration scheme (CIS) under a specific effectiveness, including complete information of the design solution.

[0033] In the product organizational structure, neither the top-level nor the bottom-level product structures participate in configuration control. Effectiveness control is entirely handled by the configuration layer. Effectiveness is directly identified on the Configuration Scheme (CIS) and the Effective Design Scheme (VCI). The effectiveness of lower-level components under the Effective Design Scheme (VCI) is inherited from its respective VCI. This simplified effectiveness management reduces control points from tens of thousands to thousands, significantly reducing the difficulty of configuration control. Virtual Product Management (VPM) is an online collaborative design platform based on CATIA, tightly integrated with the ACME system. VPM obtains aircraft change status and effectiveness information, ensuring the real-time effectiveness of the digital prototype status. It can also obtain the design status of a single aircraft sortie within the VPM system, thus supporting efficient prototype review and other digital prototype-related tasks within the VPM system.

[0034] The creation and adjustment of the product top-level and configuration layer structures are initiated in ACME based on application forms. After process approval, the changes automatically take effect in ACME and VPM by calling the system integration interface. The product structures in the two systems have a close correspondence. In ACME, configuration layer data objects (CI, CIS, VCI) and the relationships between objects are defined to record and manage module status information, thereby supporting modular configuration management, including supporting modular expression of aircraft product structures, validity management, change process control, etc., and realizing real-time acquisition of the BOM for a single aircraft flight.

[0035] In some alternative implementations, prior to step S1, the following is further included:

[0036] Step S01: Determine the change level of the configuration file;

[0037] Step S02: For the highest change level, issue a Change Request (ECR) for the configuration file in the aircraft configuration management platform as input for creating an Engineering Change Proposal (ECP). For other change levels, use the change opinions proposed by the manufacturing end or the design end as input for creating an Engineering Change Proposal (ECP).

[0038] In this embodiment, by developing the ACME platform, the complete change process from ECR to ECP to ECO is supported, realizing closed-loop control of the change process in the system and ensuring that the changed configuration state is controllable and traceable.

[0039] According to the engineering change specifications, the correspondence between change categories and engineering change methods is summarized into five categories:

[0040] The first type of change is to improve the design, such as changing annotations or part errata, which has no impact on work-in-process.

[0041] The second type of change is a general design change, such as a change in the material, size, or shape of a part, but it does not affect the use or interchangeability of the part. This type of change has no impact on existing products and they can continue to be used.

[0042] Category 3 changes are more serious design alterations that affect the shape, size, and quality of already manufactured products. Pre-modification work includes assembled components, parts, and final assemblies, requiring additional processing or replacement.

[0043] Category 4 modifications involve serious design changes, which severely impact aircraft quality. All existing components must be repaired or scrapped and replaced before the modification. Although the aircraft has already left the factory, troubleshooting can be performed at the manufacturing plant's field facilities.

[0044] Category 5 modifications are the most serious design changes, which can severely impact aircraft performance and flight safety. All work-in-process and pre-shipped aircraft components must be repaired or scrapped and replaced.

[0045] In the above embodiments, for the five types of changes, which are considered major engineering changes involving multiple aircraft models and affecting aircraft safety and performance, it is necessary to first analyze and assess the impact of the changes on performance, safety, and cost, and then issue a Change Request (ECR) in the ACME system for decision-making. After the Change Request ECR is approved, an Engineering Change Proposal (ECP) is created using the Change Request ECR as input. For the first four types of changes, change opinions proposed by the manufacturing end or the design end itself can be used as input to create an Engineering Change Proposal (ECP). The ECP is used to describe and plan the proposed engineering changes and should include the following information: ECP type, number of flights to be changed, solution description and justification, list of changes affecting the aircraft, and relevant disciplines. After the ECP is approved, the change execution phase begins. The designer uses the ECP as input to formulate a Change Order (ECO), executes the change in the LCA system through a port, and after the change is completed, switches to the ACME system for review and approval to freeze the ECO and change data, and simultaneously closes the ECP process, completing the engineering change.

[0046] In some alternative implementations, prior to step S1, the following is further included:

[0047] Step S03: Convert the specification validity on the configuration scheme CIS in the aircraft configuration management platform ACME into flight information, perform intersection calculation with the change flight of the validity design scheme VCI in the life cycle management system LCA, and unidirectionally synchronize the calculation result to all instances of the validity design scheme VCI in the life cycle management system LCA.

[0048] In this embodiment, in the Aircraft Configuration Management Platform (ACME), validity is jointly managed by the Configuration Scheme (CIS) and the Validity Design Scheme (VCI). However, in the corresponding LCA system, validity is managed only by the Validity Design Scheme (VCI). Furthermore, in the LCA system, validity resides on instances of the Validity Design Scheme (VCI), while ACME does not have the concept of instances. How to ensure consistency of flight validity between the two systems directly affects the accuracy of single-flight technical status management.

[0049] First, the business logic was reviewed to ensure consistency in validity when multiple instances of the valid design scheme (VCI) exist in the LCA system. Then, through program development, the specification validity of the configuration scheme (CIS) in the ACME was converted into flight information. This information was then dynamically intersected with the flight changes of the valid design scheme (VCI) in the LCA system, and the result was unidirectionally synchronized to all instances of the corresponding valid design scheme (VCI) in the LCA system. Because this program is embedded in the engineering change process and automatically triggered, consistency in flight validity between the Flight Configuration Management Platform (AMCE) and the LCA system is guaranteed.

[0050] In some alternative implementations, step S2 further includes:

[0051] Based on the input change object validity information, the system automatically identifies whether the change method of the configuration file to which the change object belongs is a version upgrade or a number change. When the validity of the change object changes, the number change method is forced and traced back to the validity design scheme VCI of the configuration file. When the validity of the change object does not change, the version upgrade or number change method is used.

[0052] The change management procedures impose strict requirements on the methods of version upgrades and number changes. However, allowing designers to manually determine which change method to use within the system can easily lead to confusion and affect the technical status management of individual flights. Therefore, in this embodiment, change rules are customized into the system. When planning changes in the Aircraft Configuration Management Platform (ACME), the change method is automatically identified based on the input validity information. If the validity of the change object changes, only number changes are permitted, and number changes are forcibly traced back to the validity design scheme VCI level. If the validity remains unchanged, both version upgrades and number changes are allowed. Version upgrades of parts within a package are forcibly traced back to the superior assembly level, ensuring the correct execution of changes.

[0053] Back Figure 1In step S2, after ECP review is completed, automatic numbering and version upgrade operations are performed in the LCA system. Simultaneously, in step S3, a change instruction (ECO) is automatically generated based on the ECP, and the formal data changes are implemented. The change operation is executed in step S4. After the changes are completed, in step S5, ECO approval begins. A consistency check is performed at the start of the approval process, comparing the change plan given by ECP with the actual change execution. If they match, a synchronization operation is performed, exporting data from the LCA system and importing it into the ACME system. After the import is complete, the ECO approval process officially starts. At this time, the ACME system calls the LCA interface through the WebServices service to synchronize the data status in the LCA to "Under Review." Simultaneously, ACME calls its own interface to set the corresponding data in ACME to "Under Review," at which point the data cannot be modified. The ECO approval process involves verification, professional review, and process approval. After approval, the data in the ACME and LCA systems is frozen, and the status is set to "Approved." The ECP process automatically closes after all ECO sub-processes under ECP have completed approval and issuance.

[0054] In some alternative implementations, step S5, the approval process for the ECO (Electronic Change Order), further includes:

[0055] The Engineering Change Proposal (ECP) process is used as the main process, and the Change Order (ECO) process is used as a sub-process for nested management. The ECP process is closed only after all change plans in the Engineering Change Proposal (ECP) have been implemented and issued by the Change Order (ECO).

[0056] In this embodiment, ensuring the execution of changes is crucial for the validity of aircraft data in engineering change management. Within the ACME system, the ECP process serves as the main engineering change process, while the ECO process is a sub-process of the ECP. A program is developed to ensure that the ECP process is only closed after all change plans in the current ECP have been implemented and issued by the ECO. This nested management approach of main and sub-processes achieves closed-loop control of engineering changes. During change implementation, data is transferred between the ACME and LCA systems. The consistency of data between the two systems directly impacts production execution. By establishing mechanisms for pre-approval data verification, data freezing during approval, and data and status synchronization upon approval completion, the system ultimately ensures that the data and status in ACME and LCA are valid and consistent during change implementation.

[0057] This application was achieved through top-level management standards and system development, employing a modular-based simplified configuration management method for military aircraft. It realizes modular product structure planning, process-driven product structure construction, modular engineering change process control, and the queryability, statistical analysis, and traceability of engineering data status information. Updates and improvements were made in usability and approval efficiency, while also establishing a link between manufacturing issues and changes, ensuring the management platform meets project expectations.

[0058] The modular simplified configuration management method adopted in this application realizes multi-specification configuration management under a full three-dimensional design mode. A complete modular simplified configuration management system has been established, realizing digital collaborative development of aircraft across multiple locations, factories, and research institutes. By adopting the modular simplified configuration management method proposed in this project, the cost and difficulty of technical status control have been reduced, complete control of engineering changes during the trial production process has been achieved, and the efficiency of engineering changes has been improved.

[0059] 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 module-based simplified configuration management method for aircraft, characterized in that, Includes the following steps: Step S1: Create an Engineering Change Proposal (ECP) for the configuration file in the Aircraft Configuration Management Platform (ACME). The configuration file is a virtual object corresponding to the lowest-level product structure with independent characteristics and interfaces in the aircraft product structure. Step S2: Use the WebServices service to call the LCA interface to modify or upgrade the configuration file in the LCA lifecycle management system. Step S3: Generate change command (ECO) based on the engineering change suggestion (ECP); Step S4: Call the LCA interface to modify the data in the configuration file of the Lifecycle Management System (LCA); Step S5: Check the implementation status of the engineering change proposal (ECP) and the configuration file in the lifecycle management system (LCA). If they are consistent, import the data in the lifecycle management system (LCA) into the aircraft configuration management platform (ACME) for ECO approval. During the approval process, freeze the data in the lifecycle management system (LCA) and the aircraft configuration management platform (ACME).

2. The modular-based simplified configuration management method for aircraft according to claim 1, characterized in that, In step S1, the configuration files in the aircraft configuration management platform ACME include configuration configuration items (CI), configuration specification schemes (CIS), and effectiveness design schemes (VCI). The configuration configuration item (CI) is a node in the product structure that undertakes configuration management and control. There can be multiple configuration configuration schemes (CIS) under one configuration configuration item (CI). The configuration configuration scheme (CIS) is used to reflect the configuration management of multiple specifications under the configuration configuration item (CI) and includes the complete design solution under that specification. The effectiveness design scheme (VCI) is the design solution of the configuration configuration scheme (CIS) under a specific effectiveness, including complete information of the design solution.

3. The modular-based simplified configuration management method for aircraft according to claim 2, characterized in that, Prior to step S1, the following is further included: Step S01: Determine the change level of the configuration file; Step S02: For the highest change level, issue a Change Request (ECR) for the configuration file in the aircraft configuration management platform as input for creating an Engineering Change Proposal (ECP). For other change levels, use the change opinions proposed by the manufacturing end or the design end as input for creating an Engineering Change Proposal (ECP).

4. The modular-based simplified configuration management method for aircraft according to claim 2, characterized in that, Prior to step S1, the following is further included: Step S03: Convert the specification validity on the configuration scheme CIS in the aircraft configuration management platform ACME into flight information, perform intersection calculation with the change flight of the validity design scheme VCI in the life cycle management system LCA, and unidirectionally synchronize the calculation result to all instances of the validity design scheme VCI in the life cycle management system LCA.

5. The modular-based simplified configuration management method for aircraft according to claim 1, characterized in that, Step S2 further includes: Based on the input change object validity information, the system automatically identifies whether the change method of the configuration file to which the change object belongs is a version upgrade or a number change. When the validity of the change object changes, the number change method is forced and traced back to the validity design scheme VCI of the configuration file. When the validity of the change object does not change, the version upgrade or number change method is used.

6. The modular-based simplified configuration management method for aircraft according to claim 1, characterized in that, Step S5, the approval process for the ECO (Enhanced Change Order) further includes: The Engineering Change Proposal (ECP) process is used as the main process, and the Change Order (ECO) process is used as a sub-process for nested management. The ECP process is closed only after all change plans in the ECP have been implemented and issued by the Change Order (ECO).

Images