Model-based airplane maintainability design demand analysis method and system

Through the model-based aircraft maintenance design requirements analysis method, Harmony SE and SysML are used to build a maintenance scenario model, which solves the problem of lack of maintenance design analysis in the aircraft development stage, and realizes accurate capture and design verification of aircraft maintenance requirements, which improves the Product maintenance design quality.

CN118965562AActive Publication Date: 2024-11-15CHINA AERO POLYTECH ESTAB

Patent Information

Application Number
CN202410952971.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-16
Publication Date
2024-11-15
Estimated Expiration
2044-07-16

AI Technical Summary

Technical Problem

The existing technology lacks a perfect aircraft maintenance design requirement analysis method that can combine user needs, which leads to the inability to comprehensively and accurately capture maintenance user needs and reasonably convert them into corresponding design requirements in the aircraft development stage, resulting in a lack of maintenance design in the design stage. Analysis and verification.

Method used

Using a model-based aircraft maintenance design requirement analysis method, a maintenance scenario model is constructed through Harmony SE methodology, and combined with SysML language to perform failure mode and impact analysis, repair level analysis, preventive maintenance analysis and emergency repair task analysis, which is transformed into maintenance quantitative and Qualitative design requirements and validate them in product design.

Benefits of technology

It has achieved comprehensive and accurate capture of maintenance user needs in the aircraft development stage, and timely discovered design-related problems, reducing the time and cost of design changes, and improving the quality of product maintenance design.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118965562A_ABST
    Figure CN118965562A_ABST
Patent Text Reader

Abstract

The invention provides a model-based airplane maintainability design demand analysis method and system, and relates to the technical field of airplane maintainability design, and the method comprises the following steps: S1, obtaining a model-based airplane maintainability user demand, and achieving the comprehensive and correct understanding of the airplane maintainability user demand; s2, analyzing a model-based airplane maintainability design demand, and realizing mapping from an airplane maintainability user demand to a design demand; and S3, converting and verifying the airplane maintainability design demand based on the model to realize implementation of the airplane maintainability demand towards the design. According to the technical method of the system, the maintainability demand management process and the design process of the aircraft are combined, and the technical method that the maintainability user demand is comprehensively and accurately captured in the development stage of the aircraft, the maintainability user demand is converted into the maintainability design demand, and the maintainability design demand is implemented in product design and verified is formed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of aircraft maintainability design, and in particular to a model-based aircraft maintainability design requirement analysis method and system. Background Art

[0002] Maintainability refers to the ability of a product to maintain or return to a specified state when maintained under specified conditions and within a specified time according to specified procedures and methods. Maintainability design and analysis is the fundamental way to give products good maintainability. Maintainability design is supported by a series of maintainability design and analysis work projects. The purpose of maintainability design and analysis is to apply mature maintainability design and analysis technology to the product development process, select a group of maintainability work projects that are effective for product design, meet the maintainability requirements of the ordering party for the product through design, and discover the weak links or design defects of the product as early as possible through analysis, and take effective design measures to improve them, so as to improve the maintainability of the product.

[0003] Model-Based Systems Engineering (MBSE) shifts its emphasis from control system documentation to control system models. MBSE integrates system requirements, design, analysis, and verification models to address multiple aspects of a system in a coherent manner, rather than through separate, individual models. Compared to traditional systems engineering, MBSE leverages a large software platform to model various levels of requirements, designs, and corresponding system solution elements, previously conveyed through documentation. This centralized, unified modeling approach transforms the systems engineering methodology and process, ensuring consistent system development.

[0004] Harmony SE, a MBSE methodology, is a proven approach for systems engineering, implemented using the IBM Rational Rhapsody tool. Harmony reflects the classic V-model of system design, with models and requirements stored in a central model / requirements repository. It follows a top-down design process, encompassing steps such as requirements analysis, functional analysis, and design synthesis. It primarily utilizes the SysML language to construct models such as use case diagrams, activity diagrams, and sequence diagrams to identify and communicate requirements. A comprehensive aircraft maintainability design requirements analysis method does not exist in the prior art, necessitating the urgent need for a maintainability design requirements analysis method that incorporates user needs. Summary of the Invention

[0005] In order to address the above-mentioned deficiencies in the existing technologies, and given that the MBSE-based development model has been widely adopted in the current development of new equipment models, the present invention proposes a model-based aircraft maintainability design requirements analysis method. Through the technical methods of this system, it is possible to comprehensively and accurately capture maintainability user requirements during the aircraft development stage, and rationally convert them into corresponding maintainability design requirements, which are reflected in product design and verified.

[0006] Specifically, on one hand, the present invention provides a model-based aircraft maintainability design requirements analysis method, which includes the following steps:

[0007] S1. Obtain aircraft maintainability user requirements based on the model and explain the aircraft maintainability user requirements;

[0008] S2. Analyze the aircraft maintainability design requirements based on the model. Conduct maintainability design requirements analysis in conjunction with aircraft design. Use the Harmony SE methodology to construct a maintenance scenario model. Analyze maintainability design requirements based on the maintenance scenario model. This includes the following sub-steps:

[0009] S21. Determine the analysis object;

[0010] S22: Construct a maintenance use case diagram model. For the analysis object determined in step S21, construct a maintenance use case model, specifically including the following steps:

[0011] S221. Conduct failure mode and effect analysis and repair level analysis respectively, and determine the corrective maintenance tasks for the analyzed objects;

[0012] S222. Conduct failure mode and effect analysis and reliability-centered maintenance analysis respectively, and determine the preventive maintenance tasks for the analysis objects;

[0013] S223. Conduct damage mode and impact analysis and determine emergency repair tasks for the analyzed objects;

[0014] S224. Construct a maintenance use case diagram model to describe each maintenance task and task concept. Each maintenance use case includes the name of the maintenance use case, a brief description, and related participants.

[0015] S23. Construct a maintenance scenario model. For each maintenance use case, construct one or more corresponding maintenance scenarios. Specifically, the following steps are included:

[0016] S231. Conduct maintenance task analysis and determine the maintenance process in each maintenance scenario;

[0017] S232. Draw an activity diagram using the Sysml modeling language, perform activity modeling on the maintenance use case from a functional logic perspective, and establish a maintenance process for the maintenance object in the maintenance scenario.

[0018] S233. Use Sysml modeling language to draw sequence diagrams. Draw sequence diagrams based on activity diagrams to describe the interactions between maintenance activities and maintenance personnel.

[0019] S24. Analyze model-based quantitative maintainability design requirements, including:

[0020] S241. For each parameter definition, based on the maintenance scenario model of the corresponding maintenance task, the maintenance time of each maintenance activity is obtained by analyzing the time sequence and logical relationship of the maintenance activities therein;

[0021] S242. Conduct quantitative maintainability analysis based on virtual maintenance in the digital prototype. Calculate the maintenance time and maintenance space requirements by executing maintenance activities in the maintenance scenario model.

[0022] S25. Analyze model-based qualitative design requirements for maintainability, including:

[0023] S251. Based on the constructed maintenance scenario model, refer to relevant standards and combine engineering practice experience and product characteristics to propose qualitative design requirements for maintainability;

[0024] S252. Conduct qualitative maintainability analysis based on virtual maintenance using a digital aircraft prototype. By executing maintenance activities in a maintenance scenario model, propose qualitative maintainability design requirements.

[0025] S3. Transform and verify the aircraft maintainability design requirements based on the model. Transform the maintainability qualitative design requirements into product design features directly related to product design and verify them. The specific steps are as follows:

[0026] S31. Transform model-based maintainability design requirements: Based on the constructed maintenance scenario model, combined with the technical solution, digital prototype, and physical prototype of the maintenance object, propose product design features and establish a one-to-one correspondence between maintainability design requirements and product design features;

[0027] S32. Verify model-based maintainability design requirements: Based on the maintenance scenario model, digital prototype, physical prototype and technical solution of the corresponding maintenance object at the current development stage, conduct requirement verification and evaluate the degree to which the design requirements are met.

[0028] Preferably, step S1 specifically includes the following sub-steps:

[0029] S11. Identify aircraft stakeholder needs;

[0030] S12. Determine the quantitative needs of maintainability users;

[0031] S13. Determine other requirements.

[0032] Preferably, the maintenance use case in step S22 is used to describe maintenance tasks, which include corrective maintenance tasks, preventive maintenance tasks, and emergency repair tasks.

[0033] Preferably, the quantitative maintainability design parameters in step S24 mainly include maintenance time parameters, maintenance man-hour parameters and task maintainability parameters.

[0034] Preferably, in step S21 , during the preliminary design stage or the detailed design stage, the maintenance object is determined according to the configuration of the aircraft, and functional analysis and architecture design are carried out layer by layer according to aircraft-system-subsystem-equipment / LRU.

[0035] Preferably, the timing in step S241 refers to whether the execution time of a single activity overlaps, and the timing relationship between activities includes a parallel relationship or a serial relationship;

[0036] Logic refers to the impact of the success or failure of a single activity on the success of the combined activity. The logical relationship between activities includes serial or parallel relationships.

[0037] Preferably, the product design features in step S31 include but are not limited to external dimensions, equipment layout, modular standardization, fastening method, cable laying and fault detection.

[0038] Preferably, in step S242, the digital prototype is generated by a computer, the digital prototype includes a design model, a virtual human model, a support resource model and an environment model, and the physical prototype is a product based on the digital prototype.

[0039] Preferably, step S11 specifically includes the following steps:

[0040] S111. Determine the stakeholders and their types at each stage of the aircraft's life cycle. Stakeholders related to each stage of the aircraft's life cycle are sorted to form a stakeholder set. The importance of each stakeholder is determined and ranked, with the needs of stakeholders with high importance being prioritized.

[0041] S112. Collect requirements from stakeholders;

[0042] S113. Based on the collected stakeholder requirements, a scenario construction method is used. Based on the DoDAF framework, the aircraft operation and maintenance process is expressed in multiple views through modeling. The specific sub-steps include:

[0043] S1131. Operational Mission Analysis: Based on the mission positioning of a particular aircraft, analyze and decompose the specific flight missions that the aircraft will undertake to determine the aircraft's flight mission set. Decompose the flight missions according to mission objectives, mission phases, and mission types to form a tree-like decomposition of the missions. Construct a high-level concept diagram (OV-1), describe the flight missions through graphics and text, and ultimately determine the flight mission set.

[0044] S1132, Maintenance Task Analysis: Based on the determined flight mission set, analyze the maintenance tasks that will be generated and determine the maintenance task set. Decompose the tasks by maintenance site and maintenance type to form a tree-like decomposition, construct a high-level concept diagram OV-1, describe the maintenance tasks through graphics and text, and ultimately determine the maintenance task set.

[0045] S1133, Maintenance Activity Analysis: Based on each aircraft maintenance task, combined with the existing maintenance system and maintenance objects, further analyze the maintenance activities and related conditions included in the maintenance task from a business perspective. For each maintenance task scenario in the maintenance task set, decompose its maintenance activities, simultaneously construct maintenance nodes and information, and build the organizational relationship diagram (OV-4) for executing maintenance tasks, the maintenance activity model (OV-5b), and the maintenance event tracking model (OV-6c).

[0046] S1134, Maintainability Capability Requirements Analysis: By mapping maintenance activities to maintainability capabilities, a final list of maintainability capability requirements is obtained. Based on the information in the maintenance task organization chart OV-4, the maintenance activity model OV-5b, and the maintenance event tracking model OV-6c, maintainability capability requirements are extracted and summarized to construct the maintenance capability classification model CV-2.

[0047] Among them, the high-level concept diagram OV-1 describes the high-level operational concept through graphics or text;

[0048] The organizational relationship diagram OV-4 for maintenance tasks can represent the relationship between organizational structures. The relationships between organizational structures include affiliation, command, coordination, or task relationships.

[0049] The maintenance activity model OV-5b is able to represent capabilities and behaviors and their relationships in actions, inputs, and outputs;

[0050] The maintenance event tracking model OV-6c can represent the sequence of executing combat activities during the time development process;

[0051] The maintenance capability classification model CV-2 can characterize the capability levels of all capabilities.

[0052] Preferably, in step S21, the Harmony SE methodology is used to carry out functional analysis and architectural design layer by layer according to aircraft-system-subsystem-equipment / LRU. Functional analysis refers to analyzing maintainability design requirements by constructing black box activity diagrams and black box sequence diagrams; architectural design refers to allocating maintainability design requirements to each component unit by constructing white box activity diagrams and white box sequence diagrams.

[0053] On the other hand, the present invention provides an analysis system for the above-mentioned model-based aircraft maintainability design requirement analysis method, which includes an aircraft maintainability user requirement acquisition module, an aircraft maintainability design requirement analysis module, and an aircraft maintainability design requirement conversion and verification module;

[0054] The aircraft maintainability user demand acquisition module is used to acquire aircraft maintainability user demand based on the model and interpret the aircraft maintainability user demand;

[0055] The aircraft maintainability design requirements analysis module is used to conduct maintainability design requirements analysis in conjunction with aircraft design, using the Harmony SE methodology to construct a maintenance scenario model, and analyze maintainability design requirements based on the maintenance scenario model;

[0056] The aircraft maintainability design requirement conversion and verification module is used to convert maintainability qualitative design requirements into product design features that are directly related to product design and perform verification.

[0057] Compared with the prior art, the present invention has the following beneficial effects:

[0058] (1) The present invention proposes a model-based aircraft maintainability design requirements analysis method that can solve the problem of disconnection between aircraft maintainability design and functional performance design. In the traditional maintainability design work process, a serial working method is often adopted. That is, in the aircraft development stage, the main focus is on the realization of functions and performance, and maintainability is considered based on the experience of designers. In the later stage of the development stage, the maintainability level of the aircraft is evaluated and verified based on the physical prototype. At this time, although problems related to maintainability design can be found, the design of the product has been solidified and cannot be changed, or design changes will bring about a large time and cost cost. The method of the present invention can perform maintainability requirements analysis in the design stage, timely discover problems related to maintainability design, and timely change the product design.

[0059] (2) The present invention proposes a model-based aircraft maintainability design requirement analysis method. In the current development of new equipment models, the MBSE-based development model has been widely adopted. Through the technical methods of this system, it is possible to comprehensively and accurately capture the maintainability user requirements of the aircraft during the development stage, and reasonably convert them into corresponding maintainability design requirements, which are applied in product design and verified. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 Schematic diagram of the flow of the model-based aircraft maintainability design requirements analysis method of the present invention;

[0061] Figure 2 A schematic diagram of a process for capturing aircraft maintainability user requirements based on a model in the present invention;

[0062] Figure 3 A schematic diagram of the process for capturing aircraft stakeholder requirements in the present invention;

[0063] Figure 4 A schematic diagram of the process for developing the operational concept of the present invention;

[0064] Figure 5 A schematic diagram of the flow chart of the model-based aircraft maintainability design requirements analysis in the present invention;

[0065] Figure 6 A schematic diagram of the process of constructing a maintenance use case model in the present invention;

[0066] Figure 7 A schematic diagram of the process of constructing a maintenance scenario model in the present invention;

[0067] Figure 8 Schematic diagram of the process of model-based quantitative maintainability design requirements analysis in the present invention;

[0068] Figure 9 Schematic diagram of the process of model-based maintainability qualitative design requirements analysis in the present invention;

[0069] Figure 10 A schematic diagram of the process of converting and verifying aircraft maintainability design requirements based on the model in the present invention;

[0070] Figure 11 Schematic diagram of the system framework of the present invention;

[0071] Figure 12 is a schematic diagram of an activity diagram in an embodiment of the present invention;

[0072] Figure 13 Schematic diagram of a sequence diagram in an embodiment of the present invention. DETAILED DESCRIPTION

[0073] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0074] Specifically, on the one hand, the present invention provides a model-based aircraft maintainability design requirements analysis method, such as Figures 1 to 10 As shown, it includes the following steps:

[0075] S1. Obtain aircraft maintainability user requirements based on the model and interpret the aircraft maintainability user requirements. This step specifically includes the following sub-steps:

[0076] S11. Determine aircraft stakeholder needs, including the following steps:

[0077] S111. Determine the stakeholders and their types at each stage of the aircraft's life cycle. By sorting out the stakeholders related to each stage of the aircraft's life cycle, form a stakeholder set, determine the importance of each stakeholder and rank them, and prioritize the needs of stakeholders with high importance.

[0078] S112. Collect the requirements raised by stakeholders. In specific applications, face-to-face meetings, questionnaires, and receipt of demand documents can be used to collect the requirements raised by stakeholders and construct a data set.

[0079] S113. Based on the collected stakeholder requirements, a scenario construction method is used. Based on the DoDAF framework, the aircraft operation and maintenance process is expressed in multiple views through modeling. The specific sub-steps include:

[0080] S1131. Use mission analysis: Based on the mission positioning of a certain aircraft, analyze and decompose the specific flight missions that the aircraft must undertake to determine the aircraft's flight mission set; decompose the flight mission according to mission objectives, mission phases, and mission styles to form a tree-like decomposition of the mission, construct a high-level concept diagram OV-1, describe the flight mission through graphics and text, and ultimately determine the flight mission set.

[0081] S1132, Maintenance Task Analysis: Based on the determined flight mission set, analyze the maintenance tasks that will be generated and determine the maintenance task set; decompose according to maintenance site and maintenance type to form a tree-like decomposition of tasks, construct a high-level concept diagram OV-1, describe the maintenance tasks through graphics and text, and finally determine the maintenance task set.

[0082] S1133, Maintenance Activity Analysis: Based on the various maintenance tasks of the aircraft, combined with the existing maintenance system and maintenance objects, further analyze the maintenance activities and related conditions included in the maintenance tasks from a business perspective; for each maintenance task scenario in the maintenance task set, decompose its maintenance activities, and simultaneously construct maintenance nodes and information, and build the organizational relationship diagram OV-4 for executing maintenance tasks, the maintenance activity model OV-5b, and the maintenance event tracking model OV-6c.

[0083] S1134. Maintainability Capability Requirements Analysis: By mapping maintenance activities to maintainability capabilities, the final maintainability capability requirement list is obtained. Based on the information in the organizational relationship chart for performing maintenance tasks OV-4, the maintenance activity model OV-5b, and the maintenance event tracking model OV-6c, the maintainability capability requirements are extracted and summarized to construct the maintenance capability classification model CV-2.

[0084] Among them, the High-Level Concept Diagram (OV-1) describes high-level operational concepts through graphics or text. The Organizational Relationship Diagram (OV-4) for Maintenance Tasks represents organizational relationships, including those related by affiliation, command, coordination, or task. The Maintenance Activity Model (OV-5b) represents capabilities and behaviors and their relationships across actions, inputs, and outputs. The Maintenance Event Tracking Model (OV-6c) represents the sequence of operational activities over time. The Maintenance Capability Classification Model (CV-2) represents the capability levels of all capabilities.

[0085] S12. Determine quantitative user requirements for maintainability. Using support effectiveness modeling and simulation, construct models for the aircraft's flight mission, equipment, support organization, support resource, and support process. By simulating and analyzing the entire aircraft operation and maintenance process, calculate support effectiveness indicators and decompose them into quantitative maintainability indicators.

[0086] S13. Determine other requirements. In specific applications, brainstorming, questionnaires, and analysis of regulatory and standard data are used to determine requirements related to the experience of existing similar products and the application of new technologies, ultimately forming a dataset of other requirements.

[0087] S2. Analyze the aircraft maintainability design requirements based on the model. Conduct maintainability design requirements analysis in conjunction with aircraft design. Use the Harmony SE methodology to construct a maintenance scenario model. Analyze maintainability design requirements based on the maintenance scenario model. This includes the following sub-steps:

[0088] S21. Determine the analysis object. Determine the analysis object based on the aircraft's development progress. During the demonstration or scheme design phase, when conducting aircraft-level functional analysis and architectural design, the maintenance object is the aircraft as a whole. During the preliminary design or detailed design phase, the maintenance object is determined based on the aircraft's configuration. Functional analysis and architectural design should be conducted layer by layer according to the "aircraft-system-subsystem-equipment / LRU" hierarchy. In specific applications, the Harmony SE methodology is adopted. "Functional analysis" is to analyze the maintainability design requirements by constructing black box activity diagrams and black box sequence diagrams, that is, treating the maintenance object as a black box as a whole; "Architecture design" is to clarify the next level of the maintenance object by constructing white box activity diagrams and white box sequence diagrams, that is, allocating maintainability design requirements to each component unit.

[0089] For example, aircraft-level maintainability design requirements are derived through aircraft-level "functional analysis," and then allocated to each system through aircraft-level "architecture design." At the system level, "functional analysis" and "architecture design" continue, using the aircraft-level allocated requirements as input.

[0090] S22: Construct a maintenance use case diagram model. For the analysis object determined in step S21, construct a maintenance use case model, specifically including the following steps:

[0091] S221. Conduct failure mode and effect analysis and repair level analysis respectively, and determine the corrective maintenance tasks for the analyzed objects;

[0092] S222. Conduct failure mode and effect analysis and reliability-centered maintenance analysis respectively, and determine the preventive maintenance tasks for the analysis objects;

[0093] S223. Conduct damage mode and impact analysis and determine emergency repair tasks for the analyzed objects;

[0094] S224. Construct a maintenance use case diagram model to describe each maintenance task and task concept. Each maintenance use case includes the name of the maintenance use case, a brief description, and related participants.

[0095] Among them, maintenance use cases are used to describe maintenance tasks, which include corrective maintenance, preventive maintenance, and emergency repair.

[0096] S23. Construct a maintenance scenario model. For each maintenance use case, construct one or more corresponding maintenance scenarios. Specifically, the following steps are included:

[0097] S231. Conduct maintenance task analysis and determine the maintenance process in each maintenance scenario;

[0098] S232. Draw an activity diagram using the Sysml modeling language, perform activity modeling on the maintenance use case from a functional logic perspective, and establish a maintenance process for the maintenance object in the maintenance scenario.

[0099] S233. Use Sysml modeling language to draw sequence diagrams. Draw sequence diagrams based on activity diagrams to describe the interactions between maintenance activities and maintenance personnel.

[0100] S24. Analyze model-based quantitative maintainability design requirements, including:

[0101] S241. Based on the maintenance scenario model for each parameter definition, analyze the timing and logical relationships of maintenance activities. Specifically, reference relevant standards and incorporate practical engineering experience to determine the maintenance time for each maintenance activity. Use quantitative maintainability indicators to estimate the maintainability of the product and determine the quantitative maintainability requirements that the proposed design solution should meet under specified maintenance conditions.

[0102] S242. Build a digital prototype and conduct a quantitative maintainability analysis based on virtual maintenance within it. By executing maintenance activities in the maintenance scenario model, calculate the maintenance time and space requirements. Quantitative maintainability design parameters primarily include maintenance time parameters, maintenance man-hour parameters, and task maintainability parameters. The digital prototype is computer-generated and includes a design model, a virtual human model, a support resource model, and an environmental model. A physical prototype is a product produced based on the digital prototype.

[0103] S25. Analyze model-based qualitative design requirements for maintainability, including:

[0104] S251. Based on the constructed maintenance scenario model, refer to relevant standards and combine engineering practice experience and product characteristics to propose qualitative design requirements for maintainability.

[0105] S252. Conduct qualitative maintainability analysis based on virtual maintenance using a digital prototype of the aircraft. By executing maintenance activities in the maintenance scenario model, propose qualitative maintainability design requirements.

[0106] S3. Transform and verify the aircraft maintainability design requirements based on the model. Transform the maintainability qualitative design requirements into product design features directly related to product design and verify them. The specific steps are as follows:

[0107] S31. Transform model-based maintainability design requirements: Based on the constructed maintenance scenario model, combined with the technical solution, digital prototype, and physical prototype of the maintenance object, propose product design features and establish a one-to-one correspondence between maintainability design requirements and product design features. Product design features include, but are not limited to, dimensions, equipment layout, modular standardization, fastening methods, cable routing, and fault detection.

[0108] S32. Verify model-based maintainability design requirements: Conduct requirements verification based on the maintenance scenario model, digital prototype, physical prototype, and technical solution for the corresponding maintenance object at the current development stage to evaluate the degree to which design requirements are met. Based on the degree to which design requirements are met, promptly identify maintainability design flaws and weaknesses, and propose improvement suggestions.

[0109] In specific applications, modeling software such as Rhapsody and MagicDraw is used to draw activity diagrams and sequence diagrams. The basic elements in activity diagrams include solid dots, circled dots, small boxes, and lines with arrows. Solid dots represent the starting point of a maintenance task, circled dots represent the end point of a maintenance task, small boxes represent maintenance operations, and lines with arrows connect various operations to indicate the preceding and following relationships. The basic elements in sequence diagrams include vertical lines, horizontal lines with arrows, and reflexive full arrows on related lifelines. Vertical lines represent the lifelines of maintenance tasks and participants, horizontal lines with arrows represent the transmission of messages or forces, and reflexive full arrows on related lifelines represent maintenance operations.

[0110] On the other hand, the present invention provides an analysis system for the above-mentioned model-based aircraft maintainability design requirement analysis method, such as Figure 11 As shown, it includes an aircraft maintainability user demand acquisition module 1, an aircraft maintainability design demand analysis module 2, and an aircraft maintainability design demand conversion and verification module 3.

[0111] The aircraft maintainability user requirement acquisition module 1 is used to acquire aircraft maintainability user requirements based on the model and interpret the aircraft maintainability user requirements.

[0112] Aircraft Maintainability Design Requirements Analysis Module 2 is used to conduct maintainability design requirements analysis in combination with aircraft design. It adopts the Harmony SE methodology, builds a maintenance scenario model, and analyzes maintainability design requirements based on the maintenance scenario model.

[0113] The aircraft maintainability design requirement conversion and verification module 3 is used to convert the maintainability qualitative design requirements into product design features that are directly related to product design and verify them. Specific embodiments

[0115] This embodiment proposes a model-based aircraft maintainability design requirements analysis method, such as Figure 1 As shown, the method of the present invention includes three steps: determining model-based aircraft maintainability user requirements, analyzing model-based aircraft maintainability design requirements, and transforming and verifying model-based aircraft maintainability design requirements, ultimately achieving model-based aircraft maintainability design requirements analysis. The specific implementation steps are as follows:

[0116] Taking the development of a certain type of rescue aircraft as an example, its typical usage activities include: after an earthquake, carrying emergency rescue engineers, medical personnel, loading machinery and equipment, rescue tents, food, medical supplies and other materials to the disaster area, and carrying the wounded back to the base for treatment.

[0117] To support the "earthquake relief" mission, this type of aircraft's mission execution process includes takeoff, cruising, entry, mission execution, exit, return, and landing. During the mission, aircraft failures are inevitable, and preventive measures must be taken for failures that affect safety and mission. Therefore, maintenance tasks are necessary, which puts forward the demand for maintenance capabilities such as "aircraft should be easy to maintain."

[0118] Aircraft maintenance use cases are divided into corrective maintenance, preventive maintenance, and emergency repair.

[0119] Define activity diagrams and sequence diagrams for "corrective maintenance". In this use case, the aircraft is prepared, fault isolated, approached, disassembled and replaced, reassembled, adjusted, inspected, and other maintenance activities. The activity diagram in this embodiment is as follows: Figure 12 As shown, the sequence diagram is as Figure 13 shown.

[0120] Based on the maintenance scenario model (including activity diagrams and sequence diagrams) corresponding to the maintenance task and a computer-generated virtual scenario that includes a design model, a virtual human model, a support resource model, and an environmental model, quantitative maintainability design requirements such as maintenance time and maintenance space requirements can be calculated. Qualitative maintainability design requirements also include, but are not limited to, layout design, accessibility design, operability design, visibility design, interchangeability design, maintenance access design, maintenance hatch / cover design, maintenance signage design, error-proofing design, human factors engineering design, maintenance safety design, and repairability requirements.

[0121] Based on the constructed maintenance scenario model, combined with the technical solution, digital prototype model, and physical prototype model of the maintenance object, specific product design features are proposed. Product design features include but are not limited to external dimensions, equipment layout, modular standardization, fastening methods, cable laying, fault detection, etc.

[0122] After converting maintainability design requirements into product features and implementing them into the product design plan, requirements verification is conducted to evaluate the degree to which the design requirements are met. Methods for verifying quantitative maintainability requirements include maintainability prediction and quantitative maintainability analysis based on virtual maintenance. Methods for verifying qualitative maintainability requirements include preliminary qualitative maintainability analysis based on tables and qualitative maintainability analysis based on virtual maintenance.

[0123] Through the above analysis, we can capture, analyze, transform and verify the top-level demand such as "earthquake relief" layer by layer, and implement the maintainability design requirements in terms of aircraft dimensions, equipment layout, modular standardization, fastening methods, cable laying, fault detection, etc.

[0124] The embodiments described above are merely descriptions of preferred implementations of the present invention and are not intended to limit the scope of the present invention. Without departing from the spirit of the present invention, various modifications and improvements made to the technical solutions of the present invention by ordinary technicians in this field should fall within the scope of protection determined by the claims of the present invention.

Claims

1. A model-based aircraft maintainability design requirements analysis method, Features: It includes the following steps: S1. Obtain aircraft maintainability user requirements based on the model and explain the aircraft maintainability user requirements; S2. Analyze the aircraft maintainability design requirements based on the model, conduct maintainability design requirements analysis in combination with aircraft design, use the Harmony SE methodology, build a maintenance scenario model, and analyze the maintainability design requirements based on the maintenance scenario model. The specific steps include the following: S21, determining the analysis object; S22, constructing a maintenance use case diagram model. For the analysis object determined in step S21, constructing a maintenance use case model specifically includes the following steps: S221. Carry out failure mode and effect analysis and repair level analysis respectively, and determine the corrective maintenance tasks for the analyzed objects; S222. Conduct failure mode and effect analysis and reliability-centered maintenance analysis respectively, and determine the preventive maintenance tasks for the analysis objects; S223. Conduct damage mode and impact analysis and determine the emergency repair tasks for the analyzed objects; S224, construct a maintenance use case diagram model, describe each maintenance task and task concept, and each maintenance use case includes the name of the maintenance use case, a brief description and related participants; S23, construct a maintenance scenario model, and for each maintenance use case, construct one or more corresponding maintenance scenarios, specifically including the following steps: S231. Conduct maintenance task analysis and determine the maintenance process in each maintenance scenario; S232, using Sysml modeling language to draw an activity diagram, perform activity modeling on the maintenance use case from the perspective of functional logic, and establish a maintenance process for the maintenance object in the maintenance scenario; S233. Draw sequence diagrams using Sysml modeling language, and draw sequence diagrams based on activity diagrams to describe the interactions between maintenance activities and maintenance personnel; S24. Analyze the model-based quantitative design requirements for maintainability, including: S241, for each parameter definition, based on the maintenance scenario model of the corresponding maintenance task, obtain the maintenance time of each maintenance activity by analyzing the time sequence and logical relationship of the maintenance activities therein; S242. Build a digital prototype and conduct quantitative maintenance analysis based on virtual maintenance in the digital prototype. By executing maintenance activities in the maintenance scenario model, calculate the maintenance time and maintenance space requirements; S25. Analyze the model-based qualitative design requirements for maintainability, including: S251. Based on the constructed maintenance scenario model, refer to relevant standards and combine engineering practice experience and product characteristics to propose qualitative design requirements for maintainability; S252. Use digital prototypes to conduct qualitative maintainability analysis based on virtual maintenance, and propose qualitative maintainability design requirements by executing maintenance activities in the maintenance scenario model; S3. Transform and verify the aircraft maintainability design requirements based on the model. Transform the maintainability qualitative design requirements into product design features directly related to product design and verify them. The specific steps are as follows: S31. Transform the model-based maintainability design requirements: Based on the constructed maintenance scenario model, combined with the technical solution, digital prototype and physical prototype of the maintenance object, propose product design features and establish a one-to-one correspondence between maintainability design requirements and product design features; S32. Verify model-based maintainability design requirements: Based on the maintenance scenario model, digital prototype, physical prototype and technical solution of the corresponding maintenance object at the current development stage, carry out requirement verification work and evaluate the degree to which the maintainability design requirements are met.

2. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: Step S1 specifically includes the following sub-steps: S11. Identify aircraft stakeholder needs; S12. Determine the quantitative needs of maintainability users; S13. Determine other requirements.

3. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: The maintenance use case in step S22 is used to describe the maintenance tasks, which include corrective maintenance tasks, preventive maintenance tasks and emergency repair tasks.

4. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: The quantitative design parameters of maintainability in step S24 include maintenance time parameters, maintenance man-hour parameters and task maintainability parameters.

5. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: In step S21, in the preliminary design stage or the detailed design stage, the maintenance object is determined according to the configuration of the aircraft, and the functional analysis and architecture design are carried out layer by layer in the order of aircraft, system, subsystem and equipment / LRU; In this step, the Harmony SE methodology is used to carry out functional analysis and architecture design layer by layer in the order of aircraft, system, subsystem and equipment / LRU. Functional analysis refers to analyzing maintainability design requirements by constructing black box activity diagrams and black box sequence diagrams. Architectural design refers to allocating maintainability design requirements to each component unit by constructing white box activity diagrams and white box sequence diagrams.

6. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: In step S241, the timing refers to whether the execution time of a single activity overlaps, and the timing relationship between activities includes a parallel relationship or a serial relationship; Logic refers to the impact of the success or failure of a single activity on the success of a combined activity. The logical relationship between activities includes serial or parallel relationships.

7. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: The product design features in step S31 include, but are not limited to, external dimensions, equipment layout, modular standardization, fastening methods, cable laying, and fault detection.

8. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: In step S242, the digital prototype is generated by a computer, the digital prototype includes a design model, a virtual human model, a support resource model and an environment model, and the physical prototype is a product based on the digital prototype.

9. The model-based aircraft maintainability design requirements analysis method according to claim 1, Features: Step S11 specifically includes the following steps: S111. Determine the stakeholders and types at each stage of the aircraft's life cycle, sort out the stakeholders related to each stage of the aircraft's life cycle, form a stakeholder set, determine the importance of each stakeholder and rank them, and preferentially determine the needs of stakeholders with high importance; S112. Collect requirements from stakeholders; S113. Based on the collected stakeholder requirements, the scenario construction method is used. Based on the DoDAF framework, the aircraft operation and maintenance operation process is expressed in multiple views through modeling. The specific sub-steps include: S1131. Use mission analysis: Analyze and decompose the specific flight missions to be undertaken by a certain aircraft according to its mission positioning, and determine the flight mission set of the aircraft; decompose the flight mission according to the mission objectives, mission phases and mission styles to form a tree-like decomposition of the mission, construct a high-level concept diagram OV-1, describe the flight mission through graphics and text, and finally determine the flight mission set; S1132, Maintenance task analysis: Based on the determined flight mission set, analyze the maintenance tasks that will be generated and determine the maintenance task set; decompose according to the maintenance site and maintenance type to form a tree decomposition of the task, build a high-level concept diagram OV-1, describe the maintenance tasks through graphics and text, and finally determine the maintenance task set; S1133, Maintenance activity analysis: Based on the various maintenance tasks of the aircraft, combined with the maintenance system and maintenance objects, further analyze the maintenance activities and related conditions included in the maintenance tasks from a business perspective; for each maintenance task scenario in the maintenance task set, decompose its maintenance activities, and construct maintenance nodes and information, and construct the organizational relationship diagram OV-4 for executing maintenance tasks, the maintenance activity model OV-5b, and the maintenance event tracking model OV-6c; S1134, Maintainability capability requirement analysis: By mapping maintenance activities to maintainability capabilities, the final maintainability capability requirement list is obtained. Based on the information in the organizational relationship chart for performing maintenance tasks OV-4, the maintenance activity model OV-5b, and the maintenance event tracking model OV-6c, the maintainability capability requirements are extracted and the maintenance capability classification model CV-2 is constructed; Among them, the high-level concept diagram OV-1 describes the high-level operational concept through graphics or text; The organizational relationship diagram OV-4 for maintenance tasks can represent the organizational relationship. The relationship between each organizational structure includes affiliation, command relationship, coordination relationship or task relationship. The maintenance activity model OV-5b is able to characterize capabilities and behaviors and their relationships among actions, inputs, and outputs; The maintenance event tracking model OV-6c can represent the sequence of executing combat activities during the time development process; The maintenance capability classification model CV-2 can characterize the capability levels of all capabilities.

10. An analysis system for the model-based aircraft maintainability design requirements analysis method according to claim 1, Features: It includes an aircraft maintainability user demand acquisition module, an aircraft maintainability design demand analysis module, and an aircraft maintainability design demand conversion and verification module; The aircraft maintainability user demand acquisition module is used to acquire aircraft maintainability user demand based on the model and interpret the aircraft maintainability user demand; The aircraft maintainability design requirement analysis module is used to carry out maintainability design requirement analysis in combination with aircraft design, adopt Harmony SE methodology, build a maintenance scenario model, and analyze maintainability design requirements based on the maintenance scenario model; The aircraft maintainability design requirement conversion and verification module is used to convert maintainability qualitative design requirements into product design features that are directly related to product design and to verify them.

Citation Information

Patent Citations

  • Wapon six-property collaborative optimization method and system taking supportability as center

    CN114118757A

  • Model-driven aero-engine multi-reliability database system design method

    CN115630043A

  • Image processing method and image processing apparatus

    US20060256036A1

Cited By

  • Metrological demand analysis method based on MBSE and computer equipment

    CN119940739A

  • Manufacturing equipment design demand intelligent auxiliary acquisition method and system

    CN120196617A