Aircraft effectiveness management method
By effectively managing the configuration and specification layers and using sequential digital codes to label flight sorties, the risk of data management in aircraft engineering development has been resolved, enabling precise control and efficiency improvement in the aircraft development process.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHENYANG AIRCRAFT DESIGN INST AVIATION IND CORP OF CHINA
- Filing Date
- 2025-12-03
- Publication Date
- 2026-04-21
AI Technical Summary
In current aircraft engineering development, the adoption of a static management model leads to significant risks in technical status and data management under development models characterized by incremental capability enhancement, phased evaluation, multiple configurations, and complex supervision, making it impossible to meet development requirements.
By adopting an aircraft validity management approach, and through validity management at the configuration and specification levels, using sequential digital codes to mark flight sorties, the system enables automatic truncation and upgrade of design and specification validity, forming new configurations and specifications, and ensuring accurate data control.
It enables precise control of product data during aircraft development, improves the efficiency and quality of development work, reduces deviations, and adapts to the diverse needs and complex regulatory environment of aircraft development.
Smart Images

Figure CN121902291A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of aircraft R&D process construction technology management, and specifically involves an aircraft effectiveness management method. Background Technology
[0002] Currently, domestic aircraft engineering development typically adopts a static management model. The issuance, modification, and control of engineering data only meet the needs of iterative development processes. The validity control of engineering data is based on blueprints and only satisfies data control at the current iteration stage. When facing a development model that involves incremental capability enhancement, phased evaluation, multiple configurations, and complex supervision, factors such as the complexity and high integration of the project itself, the multiple states of research prototypes, and tight development cycles can create significant risks to technical status and data management, making it impossible to meet development requirements. Summary of the Invention
[0003] To address the aforementioned problems, this application provides an aircraft availability management method, which mainly includes:
[0004] Step S1: Obtain the aircraft product structure containing the configuration layer. The configuration layer is located between the top and bottom layers of the aircraft product structure. Multiple aircraft parts at the bottom layer are combined to form a module, which serves as the bottom layer configuration VCI of the configuration layer. The configuration VCI has a configuration type and is marked with design validity. The layer above the configuration VCI is the specification layer CIS, which is marked with specification validity.
[0005] Step S2: When a new design scheme exists, the new configuration is added by automatically truncating the design validity of the previous configuration.
[0006] Step S3: When modifying the existing design scheme, upgrade or split the existing configuration into a new configuration based on the design effectiveness parameters involved in the modified scheme.
[0007] Step S4: When new specifications need to be added, generate a new configuration;
[0008] Step S5: Determine the specification validity parameters of the specification layer CIS based on the validity before and after the configuration VCI changes.
[0009] Preferably, in step S1, both the design validity and specification validity are sequential digital codes that represent the adapted flight sorties.
[0010] Preferably, in step S1, each module has a designated, unique module manager.
[0011] Preferably, step S2 further includes:
[0012] Step S21: Obtain the flight number corresponding to the new design scheme;
[0013] Step S22: Determine the configuration in which the flight sortie number is located;
[0014] Step S23: Cut off the flight sorties within the configuration according to the flight sortie number to generate a new configuration with new design effectiveness parameters.
[0015] Preferably, step S3 further includes:
[0016] When the design validity parameters of the existing configuration are completely within the range of the design validity parameters involved in the change scheme, the configuration is upgraded.
[0017] When the design validity parameters of the existing configuration are partially within the range of design validity parameters involved in the change scheme, a new configuration is generated from those partial design validity parameters.
[0018] Preferably, in step S5, the minimum set of all affected configuration VCIs is used as the final specification validity parameter for specification adjustment.
[0019] This application enables precise control over the validity of product data during the aircraft development process, effectively improving the efficiency and quality of aircraft development work. Attached Figure Description
[0020] Figure 1 This is a schematic diagram illustrating the specification validity and design validity of a preferred embodiment of the aircraft validity management method of this application. Detailed Implementation
[0021] 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.
[0022] This application provides an aircraft availability management method that enables availability management of aircraft status data that meets multiple requirements, configurations, and complex regulations while maintaining controllable status for each flight. The method mainly includes:
[0023] Step S1: Obtain the aircraft product structure containing the configuration layer. The configuration layer is located between the top and bottom layers of the aircraft product structure. Multiple aircraft parts at the bottom layer are combined to form a module, which serves as the bottom layer configuration VCI of the configuration layer. The configuration VCI has a configuration type and is marked with design validity. The layer above the configuration VCI is the specification layer CIS, which is marked with specification validity.
[0024] Step S2: When a new design scheme exists, the new configuration is added by automatically truncating the design validity of the previous configuration.
[0025] Step S3: When modifying the existing design scheme, upgrade or split the existing configuration into a new configuration based on the design effectiveness parameters involved in the modified scheme.
[0026] Step S4: When new specifications need to be added, generate a new configuration;
[0027] Step S5: Determine the specification validity parameters of the specification layer CIS based on the validity before and after the configuration VCI changes.
[0028] This application first constructs an aircraft product structure including a configuration layer in step S1, such as... Figure 1 As shown, Figure 1 In this context, products are those that can be managed individually based on their functional and physical characteristics and contribute to achieving the overall end-use requirements. In principle, based on the Product-Side Structure (PBS), the technical status items are progressively developed from project level, aircraft level, system level, subsystem level, and sub-system level, reflecting serialization and generalization design requirements. This forms the top layer of the aircraft product structure. Based on the selection of higher-level technical status items, the top-level technical status items are further divided for trial production, flight testing, and subsequent development stages. This division creates smaller-granular modules, namely the configuration layer and the bottom layer. The configuration layer is a virtual layer, and below it is the bottom layer composed of components.
[0029] The components at the bottom layer of the aircraft product structure are aggregated into modules. The validity of a module ensures the validity of all components within it. All components within a module are packaged together to form the bottom layer of the configuration layer, namely the configuration VCI. The configuration VCI has a configuration type and is marked with design validity. The module categories are defined from the perspective of design data type, such as airframe structure, supporting products, piping, wiring harness, support equipment / tools, technical documents, etc.
[0030] Validity is a marker that defines the scope of effectiveness of a component, indicating when a change to a specific product or the handling of a difference takes effect or has already taken effect. Aircraft development data validity is expressed using a 4-digit sequential code, such as 0003-0015, representing the applicable flight sorties from flight sortie 3 to flight sortie 15. The placement of validity markers at different levels or nodes in the product structure tree significantly impacts configuration management methods. The simplified configuration management approach in this application places validity at the module level, specifically at the link between the configuration layer and modules. This validity management method is advanced and reasonable, particularly effective for managing the configurations of complex products.
[0031] In some alternative implementations, in step S1, each module has a designated, unique module manager.
[0032] In this embodiment, by dividing the system into modules, each module is managed by a single responsible person, and the validity of the module is marked on the module. Components inherit the validity of the module. Components have unique identifiers, and changes to components can be made through version updates, but the new version replaces the old version. Component changes involving functional, shape, or other status changes follow the principle of changing the model number. Technical status management is responsible for creating and modifying the top-level product configuration layer, and the technical status management team is responsible for adjusting specification validity according to the production plan. The design team is responsible for creating and modifying the underlying product structure below the VCI (Visual Identity Center).
[0033] Steps S2-S5 provide a specific validity control scheme. Validity control is divided into specification validity and design validity. Specification validity is ultimately converted into flight log information, and changes are controlled through the specification validity maintenance process. Design validity is controlled through engineering change planning. When the validity of a module changes, it is changed in the form of changing the number. The validity of flights before and after the module change is automatically truncated and calculated, thereby realizing the control of flight validity.
[0034] In some alternative implementations, step S2 further includes:
[0035] Step S21: Obtain the flight number corresponding to the new design scheme;
[0036] Step S22: Determine the configuration in which the flight sortie number is located;
[0037] Step S23: Cut off the flight sorties within the configuration according to the flight sortie number to generate a new configuration with new design effectiveness parameters.
[0038] This embodiment illustrates the steps for creating design validity. For example, module A has only a single specification (0001-0007), and the initial design scheme 1 has a design validity of (0001-9999), with configuration type 0001. Later, due to iterative improvements to the design scheme, a new scheme with configuration type 0002 was created when there were 2 flights. The validity of the original scheme was automatically truncated, valid only for flights 0001, while the new scheme was valid for flights 0002-9999. Subsequently, during the design of the 5th aircraft, a second new scheme with configuration type 0003 was created. The validity of the scheme with configuration type 0002 was automatically truncated, valid only for flights 0002-0005, while the new scheme with configuration type 0003 was valid for flights 0006-9999. Subsequently, during the design of the 8th aircraft, a new scheme with a third configuration designation of 0004 was developed. The validity of the scheme with configuration designation 0003 was automatically truncated, and it was only valid for sorties 0006-0007. The new scheme with configuration designation 0003 was valid for sorties 0008-9999. The final results are shown in Table 1 below.
[0039] Table 1. Example of New Validity Specification Comparison
[0040]
[0041] In some alternative implementations, step S3 further includes:
[0042] When the design validity parameters of the existing configuration are completely within the range of the design validity parameters involved in the change scheme, the configuration is upgraded.
[0043] When the design validity parameters of the existing configuration are partially within the range of design validity parameters involved in the change scheme, a new configuration is generated from those partial design validity parameters.
[0044] This embodiment illustrates a specific method for changing configurations and design validity, where a single change covers multiple configurations and should be issued as multiple separate changes, as shown in the following example:
[0045] Assuming VCI specification validity (0001-9999), three configuration states arise during the design refinement process:
[0046] The design validity (0001-0006) of configuration 0001 of VCI A;
[0047] The design validity of VCI configuration 0002 (0007-0009).
[0048] The 0003 configuration of VCI A, design validity (0010-9999).
[0049] At this point, the design issue a design validity (0004-9999) change. At this time, the design validity parameters given for the existing configurations 0002 and 0003 are completely within the range of design validity parameters involved in the change plan. Therefore, for configuration 0002 of VCI A, the design validity (0007-0009) remains unchanged, and only an upgrade change is made, that is, the configuration number is changed from the original 0002(A) to 0002(B); for configuration 0003 of VCI A, the design validity (0010-9999) remains unchanged, and only an upgrade change is made, that is, the configuration number is changed from the original 0003(A) to 0003(B).
[0050] For configuration 0001, since the given design validity parameters (0004-0006) fall within the range of design validity parameters involved in the modified scheme, a new configuration 0004 is generated from these design validity parameters, with a design validity of 0004-0006. The design validity of the original configuration 0001 is truncated to 0001-0003. The entire design process is shown in Table 2 below.
[0051] Table 2 Example of Change Validity Specification Comparison Table
[0052]
[0053] If a change covers multiple specifications, the design change procedure is the same as above, and the actual number of flights is calculated based on the above and the specified number of flights.
[0054] In step S4, when adding a new specification, if the design status adjustment requires the addition of a new specification, the technical status management personnel adjust the specification validity of the original CIS, issue a specification validity adjustment order to the manufacturing end, and at the same time release the new CIS (new specification) and the new VCI. See Table 3 below for an example.
[0055] Table 3. Example of comparison of the effectiveness of newly added specifications
[0056]
[0057] In some alternative implementations, in step S5, the minimum set of design validity of all affected configuration VCIs is used as the final specification validity parameter for specification adjustment.
[0058] In this embodiment, the validity of specification data is calculated through a separate module, ensuring the completeness and accuracy of the data change scope. For example, if an adjustment is made to a CIS under a certain CI, assuming it affects n VCIs: A, B, C, D..., and the validity of the Ath VCI before the change is defined as A-, and the validity after the change is defined as A+, and the same logic applies to changes to other VCIs, then the system calculates the specification validity as follows:
[0059] Validity (Change) = [( A- ∪A+)-( A- ∩A+)] ∪ [( B- ∪B+)-( B- ∩B+)] ∪[( C- ∪C+)-( C- ∩C+)] ∪ [( D- ∪D+)-( D- ∩D+)]∪...
[0060] This application aims to achieve single-flight management of aircraft products facing multiple demands, configurations, and complex regulations. Through methods such as managing data validity benchmark modules, managing product module validity expression, and controlling product module validity, it achieves precise control over product data validity during the military aircraft development process. This forms a system platform and framework for current military aircraft development configuration management, fundamentally simplifying all processes related to aircraft configuration management and production, and providing strong support for current military aircraft research and production. In actual research and production activities, it effectively improves the efficiency and quality of aircraft development work, reduces deviations, and has significant economic benefits for the technical management of aircraft development work.
[0061] 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 managing aircraft availability, characterized in that, Includes the following steps: Step S1: Obtain the aircraft product structure containing the configuration layer. The configuration layer is located between the top and bottom layers of the aircraft product structure. Multiple aircraft parts at the bottom layer are combined to form a module, which serves as the bottom layer configuration VCI of the configuration layer. The configuration VCI has a configuration type and is marked with design validity. The layer above the configuration VCI is the specification layer CIS, which is marked with specification validity. Step S2: When a new design scheme exists, the new configuration is added by automatically truncating the design validity of the previous configuration. Step S3: When modifying the existing design scheme, upgrade or split the existing configuration into a new configuration based on the design effectiveness parameters involved in the modified scheme. Step S4: When new specifications need to be added, generate a new configuration; Step S5: Determine the specification validity parameters of the specification layer CIS based on the validity before and after the configuration VCI changes.
2. The aircraft availability management method according to claim 1, characterized in that, In step S1, both the design validity and specification validity are sequential digital codes that represent the compatible flight sorties.
3. The aircraft availability management method according to claim 1, characterized in that, In step S1, each module has a designated, unique module manager.
4. The aircraft availability management method according to claim 1, characterized in that, Step S2 further includes: Step S21: Obtain the flight number corresponding to the new design scheme; Step S22: Determine the configuration in which the flight sortie number is located; Step S23: Cut off the flight sorties within the configuration according to the flight sortie number to generate a new configuration with new design effectiveness parameters.
5. The aircraft availability management method according to claim 1, characterized in that, Step S3 further includes: When the design validity parameters of the existing configuration are completely within the range of the design validity parameters involved in the change scheme, the configuration is upgraded. When the design validity parameters of the existing configuration are partially within the range of design validity parameters involved in the change scheme, a new configuration is generated from those partial design validity parameters.
6. The aircraft availability management method according to claim 1, characterized in that, In step S5, the minimum set of all affected configuration VCIs is used as the final specification validity parameter for specification adjustment.