Model-based aircraft maintainability design requirements analysis method and system

Abstract

The present invention provides a model-based aircraft maintainability design requirement analysis method and system, which relates to the field of aircraft maintainability design technology. The method includes the following steps: S1, obtaining model-based aircraft maintainability user requirements to achieve a comprehensive and correct understanding of aircraft maintainability user requirements; S2, analyzing model-based aircraft maintainability design requirements to achieve the mapping of aircraft maintainability user requirements to design requirements; S3, transforming and verifying model-based aircraft maintainability design requirements to achieve the implementation of aircraft maintainability requirements to design. The present invention combines the aircraft maintainability requirement management process with the design process through a systematic technical method, forming a technical method for comprehensively and accurately capturing maintainability user requirements during the development stage of an aircraft, and transforming them into maintainability design requirements, which are implemented in product design and verified.

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 it is 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 items. 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 items 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 from emphasizing control system-related documents to control system models. MBSE integrates system requirements, design, analysis, and verification models to address multiple aspects of the system in a coherent manner, rather than a separate individual model. Compared with traditional systems engineering, MBSE relies on a large software platform to model the various levels of requirements, designs, and corresponding system solution elements that were previously delivered through documents, changing the system engineering method flow in a centralized and unified modeling manner to implement system development.

[0004] Harmony SE is an MBSE methodology and a mature method for systems engineering. It is implemented using the IBM Rational Rhapsody tool. Harmony reflects the classic V model of system design, and models and requirements are stored in a central model / requirements library. It is a top-down design flow, including steps such as requirements analysis, functional analysis, and design synthesis. It mainly uses the SysML language to build models such as use case diagrams, activity diagrams, and sequence diagrams to identify and transfer requirements. There is no complete aircraft maintainability design requirements analysis method in the prior art, so there is an urgent need to study a maintainability design requirements analysis method that can combine user needs. Summary of the invention

[0005] In order to address the deficiencies of the above-mentioned prior art, under the current MBSE-based development model that has been widely adopted in the 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 the maintainability user requirements of the aircraft during the development stage, and reasonably transform 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 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:

[0009] S21, determining the analysis object;

[0010] 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:

[0011] S221. Carry out 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 the emergency repair tasks for the analyzed objects;

[0014] 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;

[0015] S23, construct a maintenance scenario model, and for each maintenance use case, construct one or more corresponding maintenance scenarios, specifically including the following steps:

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

[0017] 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;

[0018] 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;

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

[0020] 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;

[0021] S242. In the digital prototype, quantitative maintenance analysis based on virtual maintenance is carried out to calculate the maintenance time and maintenance space requirements by executing the maintenance activities in the maintenance scenario model;

[0022] S25. Analyze the 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. Use the digital prototype of the aircraft to carry out qualitative maintainability analysis based on virtual maintenance, and propose qualitative maintainability design requirements by executing maintenance activities in the maintenance scenario model;

[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 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;

[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, carry out requirement verification work 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, and the maintenance tasks 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 a 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 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;

[0041] S112. Collect requirements from stakeholders;

[0042] 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:

[0043] 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;

[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 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;

[0045] 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 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;

[0046] 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 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 organizational relationship. The relationship between each organizational structure includes affiliation, command relationship, coordination relationship or task relationship.

[0049] The maintenance activity model OV-5b is able to characterize capabilities and behaviors and their relationships among 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 architecture 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; architecture 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 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;

[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 to verify them.

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

[0058] (1) The model-based aircraft maintainability design requirements analysis method proposed in the present invention can solve the problem of the 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 requirements analysis method. Under the current MBSE-based development model that is widely used in the development of new equipment models, the technical methods of this system can be used to comprehensively and accurately capture the maintainability user requirements of the aircraft during the development stage, and reasonably transform them into corresponding maintainability design requirements, which are applied in product design and verified. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 It is a flow chart of the model-based aircraft maintainability design requirement 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 stakeholders' requirements in the present invention;

[0063] Figure 4 A schematic diagram of the process flow for developing the operating concept in 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 A schematic diagram of the flow of the model-based quantitative design requirements analysis for maintainability in the present invention;

[0068] Fig. 9 It is a flow chart of the model-based maintainability qualitative design requirement analysis in the present invention;

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

[0070] Fig.11 It is a schematic diagram of the system framework of the present invention;

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

[0072] Fig.13 It is a 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 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 explain 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 types at each stage of the aircraft's life cycle, form a stakeholder set by sorting out the stakeholders related to each stage of the aircraft's life cycle, determine the importance of each stakeholder and rank them, and preferentially determine the needs of stakeholders with high importance.

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

[0079] 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:

[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, 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.

[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 the maintenance site and maintenance type to form a tree decomposition of the task, 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 construct maintenance nodes and information at the same time, 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.

[0083] 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 summarized and constructed.

[0084] 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 performing maintenance tasks can represent the organizational relationship, and the relationship between each organization includes affiliation, command relationship, coordination relationship or task relationship. The maintenance activity model OV-5b can represent capabilities and behaviors and their relationship in actions, inputs and outputs. The maintenance event tracking model OV-6c can represent the sequence of performing combat activities during the course of time. The maintenance capability classification model CV-2 can represent the capability levels of all capabilities.

[0085] S12. Determine the quantitative needs of maintainability users; use the support effectiveness modeling and simulation method to build the aircraft's flight mission model, equipment model, support organization model, support resource model, and support process model. Calculate the aircraft's support effectiveness index through simulation and data statistics of the entire process of aircraft use and maintenance, and decompose it to obtain the quantitative maintainability index.

[0086] S13. Determine other requirements. In specific applications, brainstorming, questionnaire surveys, and analysis of laws, regulations, and standards data are used to determine the experience of existing similar products, the application of new technologies, and other requirements data sets, and finally form other requirements data sets.

[0087] 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:

[0088] S21. Determine the object of analysis. Determine the object of analysis based on the development progress of the aircraft. In the demonstration stage or the scheme design stage, when conducting functional analysis and architectural design at the aircraft level, the maintenance object is the entire aircraft. In the preliminary design stage or the detailed design stage, the maintenance object is determined based on the configuration of the aircraft, and functional analysis and architectural design should be carried out layer by layer according to "aircraft-system-subsystem-equipment / LRU". 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, the maintenance object is regarded as a black box as a whole; "Architecture design" is to construct white box activity diagrams and white box sequence diagrams, that is, to clarify the next level of the maintenance object and allocate the maintainability design requirements to each component unit.

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

[0090] 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:

[0091] S221. Carry out 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 the 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, the maintenance use case is used to describe the maintenance tasks, which include corrective maintenance, preventive maintenance and emergency repair.

[0096] S23, construct a maintenance scenario model, and for each maintenance use case, construct one or more corresponding maintenance scenarios, specifically including the following steps:

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

[0098] 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;

[0099] 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;

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

[0101] S241. For each parameter definition, based on the maintenance scenario model of the corresponding maintenance task, the time sequence and logical relationship of the maintenance activities are analyzed. In the specific process, the maintenance time of each maintenance activity is given by referring to relevant standards and combining engineering practice experience. The maintainability of the product is estimated through the quantitative indicators of maintainability, and the quantitative maintainability requirements that the proposed design scheme should meet under the specified guarantee conditions are obtained.

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

[0103] S25. Analyze the 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. Use the digital prototype of the aircraft to carry out qualitative maintainability analysis based on virtual maintenance, and propose qualitative maintainability design requirements by executing maintenance activities in the maintenance scenario model.

[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, product design features are proposed to establish a one-to-one correspondence between maintainability design requirements and product design features. Among them, product design features include but are not limited to external dimensions, equipment layout, modular standardization, fastening methods, cable laying and fault detection.

[0108] S32. Verify the 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 the requirements verification work and evaluate the degree of satisfaction of the design requirements. Afterwards, based on the degree of satisfaction of the design requirements, timely discover the maintainability design defects and weak links, and put forward improvement suggestions.

[0109] In specific applications, modeling software such as Rhapsody and MagicDraw are used to draw activity diagrams and sequence diagrams. The basic elements in the activity diagram include solid dots, circled dots, small boxes, and lines with arrows. Solid dots are used as the starting point of the maintenance task, circled dots are used as the end point of the maintenance task, small boxes represent maintenance operations, and lines with arrows are used to connect various operations to indicate the relationship between the front and back. The basic elements in the sequence diagram include vertical lines, horizontal lines with arrows, and reflexive full arrows on related lifelines. Vertical lines are 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, etc.

[0110] On the other hand, the present invention provides an analysis system for the above-mentioned model-based aircraft maintainability design requirements analysis method, such as Fig.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 demand acquisition module 1 is used to acquire the aircraft maintainability user demand based on the model and interpret the aircraft maintainability user demand.

[0112] Aircraft maintainability design requirement analysis module 2 is used to conduct maintainability design requirement 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 the aircraft maintainability user requirements based on the model, analyzing the aircraft maintainability design requirements based on the model, and transforming and verifying the aircraft maintainability design requirements based on the model, and finally realizing the aircraft maintainability design requirements analysis based on the model. The specific implementation steps are as follows:

[0116] Taking the development of a certain type of rescue aircraft as an example, its typical use 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 realization of the "earthquake relief" mission, the mission execution process of this type of aircraft includes take-off, cruising, entry, mission execution, exit, return, landing, etc. It is inevitable that the aircraft will fail during the mission, or preventive measures need to be taken for failures that affect safety and missions, so maintenance tasks need to be carried out, thus proposing 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] Activity diagrams and sequence diagrams are defined for "corrective maintenance". In this use case, maintenance activities such as preparation, fault isolation, access, disassembly and replacement, reinstallation, adjustment, and inspection are performed on the aircraft. The activity diagram in this embodiment is as follows Fig.12 As shown, the sequence diagram is as Fig.13 shown.

[0120] The quantitative design requirements for maintainability, such as maintenance time and maintenance space requirements, can be calculated based on the maintenance scenario model (including activity diagrams and sequence diagrams) of the corresponding maintenance tasks, and the virtual scene generated by the computer, which includes the design model, virtual human model, support resource model and environmental model, etc. The qualitative design requirements for maintainability include, but are not limited to: layout design, accessibility design, operability design, visibility design, interchangeability design, maintenance channel design, maintenance hatch / cover design, maintenance identification design, error-proofing design, human factor engineering design, maintenance safety design, and emergency repair 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 in the product design plan, the requirements verification work is carried out to evaluate the degree of satisfaction with the design requirements. The verification methods for quantitative maintainability requirements include maintainability prediction, maintainability quantitative analysis methods based on virtual maintenance, etc.; the verification methods for qualitative maintainability requirements include preliminary maintainability qualitative analysis methods based on tables, maintainability qualitative analysis methods based on virtual maintenance, etc.

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

[0124] The embodiments described above are only descriptions of the preferred implementation modes of the present invention, and are not intended to limit the scope of the present invention. Without departing from the design 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 all fall within the protection scope determined by the claims of the present invention.

Claims

1. A model-based aircraft maintainability design requirements analysis method, characterized by: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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, characterized in that: 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 performing maintenance tasks can represent the relationship between organizational structures. The relationship between organizational structures includes affiliation, command, coordination 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, characterized in that: 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.

Images