Design method and device of aero-engine health management ground system

Abstract

The invention provides a design method and device for an aero-engine health management ground system, the design method adopts a multi-view view in a system architecture model tool, and the design method comprises the following steps: identifying a benefit-critical party of an aero-engine, collecting the use requirements of the benefit-critical party for the health management ground system, and calculating the use requirements of the benefit-critical party for the health management ground system; analyzing a top level demand of the health management ground system; based on various scenes of aero-engine delivery, use and maintenance, analyzing and designing various interactive business activities of the benefit-critical party, thereby decomposing the top-level demand of the health management ground system into the various interactive business activities of the benefit-critical party; and analyzing and designing system functions of the health management ground system based on various interactive business activities of the benefit parties, and establishing a system model to realize design work of the health management ground system.

Description

Technical Field

[0001] The present invention relates to the field of aircraft engine products, and in particular to a design method and device for an aircraft engine health management ground system. Background Art

[0002] The Engine Health Management (EHM) ground system is a complex system that ensures the safe and reliable on-wing operation of civil aviation engines. The system obtains the operating status of aircraft engines through satellite telecommunications through onboard sensors, monitors the real-time performance of the engine, and evaluates the health status of engine systems and components. On this basis, it performs fault diagnosis and prediction, and is combined with the operation of other supporting services to share data, information and available resources to achieve condition-based use of engines and predictive maintenance of engines.

[0003] Nowadays, with the development of technologies such as communications, artificial intelligence, and big data, the concept of customized civil aviation engine operation support services with EHM ground systems as the core is constantly updated. The EHM ground system involves many stakeholders, has complex internal logic functions, multiple data interaction interfaces, and high functional scalability requirements, which increases the difficulty of the design of the EHM ground system.

[0004] At the same time, there are many architectural framework design methods in the existing technology, such as the DoDAF architecture framework, the Zachman architecture framework, the ToGAF architecture framework, the NAF architecture framework, etc., which have been actively applied in engineering practice, effectively solving complex practical problems, and can plan, design, manage, implement and apply complex systems. However, there is no development framework for the EHM ground system architecture in the existing technology. The functional design of the EHM ground system is relatively complex, and the system design and development is difficult. For example, the initial demand capture is incomplete, the consistency between demand and design is difficult to ensure, the cross-business communication is inefficient, the design plan is difficult to iterate and update, and the ability to discover problems early is insufficient, resulting in problems such as long system development cycle and low efficiency.

[0005] In order to overcome the above-mentioned defects of the prior art, this field is in urgent need of a design method for an aircraft engine health management ground system, which is demand-driven and guided by the system functional architecture, so as to facilitate designers to quickly carry out EHM ground system architecture design and meet the forward design requirements of civil aviation engine EHM ground systems. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its only purpose is to give some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0007] In order to overcome the above-mentioned defects of the prior art, the present invention provides a design method for an aircraft engine health management ground system. The design method adopts a multi-perspective view in an architecture model tool. The design method includes: identifying the stakeholders of the aircraft engine, collecting the usage requirements of the stakeholders for the health management ground system, and analyzing the top-level requirements of the health management ground system; based on various scenarios of aircraft engine delivery, use and maintenance, analyzing and designing the various interactive business activities of the stakeholders, thereby decomposing the top-level requirements of the health management ground system into the various interactive business activities of the stakeholders; and analyzing and designing the system functions of the health management ground system based on the various interactive business activities of the stakeholders, and establishing a system model to realize the design work of the health management ground system.

[0008] In one embodiment, optionally, the architecture model tool includes a DoDAF structural framework.

[0009] In one embodiment, preferably, the stakeholders include the Civil Aviation Administration, aircraft manufacturers, engine manufacturers, engine purchasers, airlines, crews, airports, maintenance personnel, trainers and subsystem suppliers. The analysis of the top-level requirements of the health management ground system may include: using the global view in the architecture model tool to describe the system's overview information, and using the capability view to describe the system's top-level requirements.

[0010] In one embodiment, preferably, the various scenarios of delivery, use and maintenance of the aircraft engine include pre-service maintenance, route operation, workshop maintenance and decommissioning and scrapping, and the analysis and design of the various interactive business activities of the stakeholders may include: analyzing and designing the relationship between the stakeholders participating in the various interactive business activities in various scenarios, and the activity flow of the various interactive business activities.

[0011] In one embodiment, preferably, the analysis and design of the various interactive business activities of the stakeholders may also include: using the activity view in the architecture model tool to describe the organizational relationship, interactive relationship, interactive data flow and control flow, interactive activity interface and resources between the stakeholders and the activity status of the various interactive business activities, and using the timing diagram in the activity view to describe the events and occurrence order of the various interactive business activities.

[0012] In one embodiment, preferably, the design method may also include: after performing the analysis and designing the various interactive business activities of the stakeholders, using the capability view in the architecture model tool to analyze whether the designed various interactive business activities can meet the top-level requirements of the health management ground system.

[0013] In one embodiment, preferably, the analysis and design of the system functions of the health management ground system based on the various interactive business activities of the stakeholders may include: using the system view in the architecture model tool to describe the external interface of the health management ground system, the internal and external interactive function data flow, the events and sequence of executing functions, the interactive relationship between systems and the interactive resources; and using the system view to analyze whether the designed system functions can meet the execution of the various interactive business activities.

[0014] In one embodiment, preferably, the design method may also include: after the design of each interactive business activity or system function is completed, simulating and verifying the system model, and iteratively optimizing the system model based on feedback of the verification and confirmation results.

[0015] Another aspect of the present invention provides a design device for an aircraft engine health management ground system, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute a design method for an aircraft engine health management ground system as described in any one of the above items.

[0016] The present invention also provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method for designing an aircraft engine health management ground system as described in any one of the above items. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The above features and advantages of the present invention can be better understood after reading the detailed description of the embodiments of the present disclosure in conjunction with the following drawings. In the drawings, the components are not necessarily drawn to scale, and components with similar related properties or features may have the same or similar reference numerals.

[0018] Figure 1 is a schematic diagram of a method flow of a design method of an aircraft engine health management ground system according to an embodiment of the present invention;

[0019] Figure 2 is a schematic diagram of the modeling sequence of the DoDAF-based EHM ground system functional architecture according to an embodiment of the present invention;

[0020] Figure 3 is a schematic diagram of the design process of interactive business activities of the EHM ground system according to an embodiment of the present invention;

[0021] Figure 4 is a schematic diagram of an aircraft engine operation scenario according to an embodiment of the present invention;

[0022] Figure 5 is a schematic diagram of an aircraft engine service scenario according to an embodiment of the present invention;

[0023] Figure 6 is a schematic diagram of the functional design process of the EHM ground system according to an embodiment of the present invention;

[0024] Figure 7 is a schematic diagram of a process flow of system model simulation verification according to an embodiment of the present invention; and

[0025] Figure 8 It is a schematic diagram of the device structure of a design device for an aircraft engine health management ground system according to another aspect of the present invention. DETAILED DESCRIPTION

[0026] The following specific embodiments illustrate the implementation of the present invention, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. Although the description of the present invention will be introduced in conjunction with the preferred embodiment, this does not mean that the features of this invention are limited to this implementation. On the contrary, the purpose of introducing the invention in conjunction with the implementation is to cover other options or modifications that may be extended based on the claims of the present invention. In order to provide a deep understanding of the present invention, the following description will include many specific details. The present invention can also be implemented without using these details. In addition, in order to avoid confusion or blurring the focus of the present invention, some specific details will be omitted in the description.

[0027] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0028] In addition, the terms "upper", "lower", "left", "right", "top", "bottom", "horizontal" and "vertical" used in the following description should be understood as the directions shown in the paragraph and the related drawings. Such relative terms are only used for the convenience of description and do not mean that the device described therein must be manufactured or operated in a specific direction, and therefore should not be understood as limiting the present invention.

[0029] It is understood that although the terms "first", "second", "third", etc. may be used herein to describe various components, regions, layers and / or parts, these components, regions, layers and / or parts should not be limited by these terms, and these terms are only used to distinguish different components, regions, layers and / or parts. Therefore, the first component, region, layer and / or part discussed below may be referred to as a second component, region, layer and / or part without departing from some embodiments of the present invention.

[0030] In order to overcome the above-mentioned defects of the prior art, the present invention provides a design method for an aircraft engine health management ground system (EHM), which is demand-driven and guided by the system functional architecture, so as to facilitate designers to quickly carry out the architecture design of the aircraft engine health management ground system and meet the forward design requirements of the civil aviation engine health management ground system.

[0031] The Engine Health Management Off-board System (EHM) uses onboard sensors to obtain the engine's operating status, monitor the engine's real-time performance, evaluate the health status of engine systems and components, and provide airlines with engine health status information and operating recommendations.

[0032] Figure 1 The present invention is a flowchart of a method for designing an aircraft engine health management ground system according to an embodiment of the present invention.

[0033] The design method of the aircraft engine health management ground system provided by the present invention adopts the multi-view view in the system architecture model tool, please refer to Figure 1 , the design method 100 may include:

[0034] Step 101: Identify the stakeholders of the aircraft engine, collect the requirements of the stakeholders for the use of the health management ground system, and analyze the top-level requirements of the health management ground system;

[0035] Step 102: Analyze and design various interactive business activities of the stakeholders based on various scenarios of aircraft engine delivery, use, and maintenance, thereby decomposing the top-level requirements of the health management ground system into various interactive business activities of the stakeholders; and

[0036] Step 103: Analyze and design the system functions of the health management ground system based on the various interactive business activities of the stakeholders, and establish a system model to implement the design work of the health management ground system.

[0037] There are many architectural frameworks in the prior art that can be used for planning, designing, managing and implementing complex practical problems such as aircraft engine health management ground systems. Optionally, in the embodiments of this article, the DoDAF architectural framework is used as an example to explain the forward design process of the EHM system.

[0038] DoDAF is a universal architecture, a guide for architecture design, and a top-level conceptual model for architecture development. After more than a decade of research and development, the DoDAF architecture has become a de facto standard for countries to learn and draw lessons from. The DoDAF architecture framework includes eight types of views: global view, capability view, operation view, service view, system view, data and information view, standard view, and project view. However, the DoDAF architecture framework theory only provides the basic concept of the standard view, and does not provide a specific methodology and detailed process for the construction of the standard view during the equipment development process.

[0039] Figure 2 1 is a schematic diagram of a DoDAF-based EHM ground system functional architecture modeling sequence according to an embodiment of the present invention.

[0040] Step 101 corresponds Figure 2 Model building process of top-level analysis. In a preferred embodiment, the identified stakeholders may include the Civil Aviation Administration, aircraft manufacturers, engine manufacturers, engine purchasers, airlines, crews, airports, maintenance personnel, trainers, and subsystem suppliers. Among them, the needs of the Civil Aviation Administration and airlines can be summarized as follows: During the engine operation and use phase, the EHM ground system analyzes the engine trend status through the engine operation and use data, assists airlines in meeting civil aviation regulations and safety during engine operation, optimizes engine operation status, and reduces engine maintenance costs; telecommunications operators and big data operators participate in the air-to-ground link data transmission between the EHM airborne system and the ground system, and their needs can be summarized as follows: the data transmission protocol should comply with existing standards; and the main engine manufacturer, as the provider of engines and service products, needs to establish an engine operation and use data feedback mechanism to feed back engine manufacturing and design and improve engine quality.

[0041] Furthermore, the analysis of the top-level requirements of the health management ground system may include: using the global view (AV) in the architecture model tool to describe the system's overview information, and using the capability view (CV) to describe the system's top-level requirements.

[0042] In this step, typical operating scenarios of civil aviation engines are defined, and the top-level capability requirements of the EHM ground system are summarized according to airworthiness regulations, industry benchmarks, and user expectations. This will enable the system to monitor engine conditions, performance deterioration, and safety operations in operating scenarios, and corrective measures can be taken in advance.

[0043] More specifically, reference Figure 2 and Figure 1 First, we focus on the needs of stakeholders, business opportunities, deficiencies in existing systems, policies and regulations, PESTEL (political, economic, social, technological, environmental and legal) and other factors, analyze the system from both internal and external perspectives, and extract business background information and business missions. At the same time, we use the AV-1 view in the DoDAF architecture to express the system's summary information, such as the use environment, the use object, etc. The global view file can actually be a document file, a picture file or a table.

[0044] Next, the top-level requirements and capabilities that the system should have are summarized based on the business mission analysis, and the concept is expressed using the CV-1 capability view, which is a structure diagram. The engine life cycle can be divided into different stages in the CV-1 view according to the aircraft engine operation scenario monitoring requirements, and the capabilities of the EHM ground system when the engine is running on wing can be determined.

[0045] Then, based on the top-level requirements, the overall target capability of the system is decomposed, and the decomposition is expressed using the CV-2 capability view, which is a structure diagram. For example, monitoring the engine status can be decomposed into monitoring the engine through QAR / CEOD, monitoring through ACARS messages, and monitoring algorithm development capabilities.

[0046] Figure 3 It is a schematic diagram of the design process of interactive business activities of the EHM ground system according to an embodiment of the present invention.

[0047] Figure 3 The specific content of step 102 is shown as follows: analyzing interactive business activities based on scenarios, and also Figure 2 The specific content of the activity planning column in the figure is displayed, that is, the modeling process based on the scenario activity design model. The modeling process based on the scenario activity design model is implemented on the basis of the top-level requirements analyzed in step 101. In this step, the top-level scenario used in the system operation is firstly described, and the system and external system activity models are established.

[0048] Next, refine the top-level scenario and describe the top-level graph of the activity concept under the formulated operation scenario. Use the OV-1 top-level scenario concept view to express it, and the type is graph.

[0049] Figure 4It is a schematic diagram of an aircraft engine operation scenario drawn according to an embodiment of the present invention. Figure 5 It is a schematic diagram of an aircraft engine service scenario according to an embodiment of the present invention.

[0050] exist Figure 4 , Figure 5 In the illustrated embodiment, the various scenarios of the delivery, use and maintenance of the aircraft engine may include pre-service maintenance, route operation, workshop maintenance and decommissioning, i.e., the top-level scenario here. For example, under the top-level scenario of route operation, many specific scenarios may also be included, such as engine operation, various inspections and maintenance.

[0051] In these scenarios, the EHM ground system mainly participates in the engine operation scenarios through four service scenarios under route operation: engine operation, pre-flight, short stop, and post-flight inspection. When the engine is running, the onboard system obtains snapshot data of the engine status, which is transmitted to the ground system via the air-to-ground data transmission link for remote monitoring of the engine status; during pre-flight, short stop, and post-flight inspections, the engine status continuous data and maintenance data are obtained through manual download or wireless Wi-Fi transmission by the maintenance staff for engine fault analysis and diagnosis; the EHM ground system formulates operation and predictive maintenance suggestions for airlines to refer to, and assists airlines in operating engines safely and economically.

[0052] It can be understood that the usage scenario can better describe the interaction between the system product and its operating environment, and systematically identify and analyze various scenarios of engine use and maintenance. For example, the environmental elements of the EHM system can mainly include the health management airborne system, crew, air-to-ground data transmission link, ground monitoring personnel, operation support personnel, etc. Based on the scenario, the interaction process or interaction relationship between these elements can be better described, and then the functional requirements of the system can be obtained.

[0053] More specifically, for example, the working process of the EHM system in expected environments such as engine operation and maintenance can be envisioned, the usage scenarios of interaction with the EHM system during engine operation and maintenance can be identified and established, and the stakeholders and various environmental elements of the scenarios can be identified, so that the functions required by the system can be sorted out based on the needs of the stakeholders.

[0054] The following further describes how the design method provided by the present invention specifically executes the content of this step.

[0055] Please refer to Figure 2 and Figure 3 After determining the top-level scenario, extract the activity participants in the top-level scenario, or the stakeholders involved in the activities of these scenarios, such as airlines, telecom operators, big data operators, main engine manufacturers, etc., and express them using the OV-4 organizational relationship view, the type of which is a structure diagram.

[0056] In a preferred embodiment, the analysis and design of the various interactive business activities of the stakeholders in the EHM system design method provided by the present invention may include: analyzing and designing the association relationships between the stakeholders participating in the various interactive business activities in various scenarios, and the activity processes of the various interactive business activities.

[0057] Further preferably, the activity view in the architecture model tool can be used to describe the organizational relationship, interaction relationship, interaction data flow and control flow, interaction activity interface and resources, and activity status of each interactive business activity among the stakeholders, and the timing diagram in the activity view can be used to describe the events and occurrence order of each interactive business activity.

[0058] Specifically, we can continue to combine Figure 2 The modeling order shown is as follows. The activity behavior of each activity participant, as well as the data flow and control flow between the activity participants are defined below, and these activities are assigned to different lanes. Each lane is associated with a specific activity participant and expressed using the OV-5b activity view, which is a structure diagram.

[0059] Then, define the synchronous or asynchronous information transmitted between the activity participants in the top-level scenario, that is, the timing migration of the activity, and use the OV-6c activity timing description diagram to express it, the type is a timing diagram. Following the flowchart downward, the state migration logic of each activity participant in the top-level scenario is defined, and the OV-6b activity state transition view is used to express it, the type is a state machine. For example, analyze the activity status of airlines, telecom operators, big data operators, and engine manufacturers, respectively establish the state machine and state transfer conditions of each activity participant, and assign them to the relevant interactive business activities.

[0060] Based on the previous steps, develop the simulation components of the activity model, write test cases, and use the human-in-the-loop simulation method to verify the logic and rationality of the model. On this basis, establish the activity participant interaction matrix, use OV-3 to describe the interaction relationship between different activity participants, and the type is table. Establish activity resource interaction, use OV-2 to describe the interaction resources of different activity participants, and the type is structure diagram.

[0061] In a preferred embodiment, the design method provided by the present invention may also include: after performing the analysis and designing the various interactive business activities of the stakeholders, using the capability view in the architecture model tool to analyze whether the designed various interactive business activities can meet the top-level requirements of the health management ground system.

[0062] For example, Figure 2As shown, a capability-activity mapping matrix can be established, and the CV-6 view can be used to analyze whether the designed activities can meet the system capability requirements. The type is table.

[0063] The scenario-based interactive business activity design considers how different activity participants cooperate to complete corresponding tasks during the operation and use of aircraft engines from the operational level. At this stage, the relationship between stakeholders participating in the activities and the entire activity process should be analyzed. Through mission task decomposition, the corresponding activity participants are determined, such as the Civil Aviation Administration, airlines, telecom operators, big data operators, engine manufacturers, etc. The tasks of the activity participants are determined and the activity analysis is carried out. In this process, various uncertainties in the operation process are considered as detailed as possible, the operation rules are analyzed one by one, and the real-time status of the stakeholders participating in the activities and the activities performed are confirmed.

[0064] Figure 6 FIG. 4 is a schematic diagram of a functional design flow of an EHM ground system according to an embodiment of the present invention.

[0065] Figure 6 The content shown corresponds to step 103: analyzing and designing the system functions of the health management ground system based on the various interactive business activities of the stakeholders, and at the same time Figure 2 The specific content of the system function planning column is shown in the figure. The functional boundaries of the EHM ground system are specified through the scenario-based interactive business activity design, providing a basis for the design of the EHM ground system functional architecture model.

[0066] The system functional architecture analysis targets the EHM ground system requirements and determines the functional boundaries and functions of the EHM ground system according to typical scenarios and activity processes of aircraft engine operation monitoring, such as algorithm updates, message and data processing, abnormal classification alarms, establishment of fault cases, and issuance of maintenance recommendations.

[0067] In a preferred embodiment, in the design method of the aircraft engine health management ground system provided by the present invention, the system functions of the health management ground system are analyzed and designed based on the various interactive business activities of the stakeholders, which may include: using the system view in the architecture model tool to describe the external interface of the health management ground system, internal and external interactive function data flows, events and sequence of execution functions, interactive relationships between systems, and interactive resources; and using the system view to analyze whether the designed system functions can meet the execution of the various interactive business activities.

[0068] For example, we can combine the engine operation scenario and service scenario, and the EHM ground system requirements, and further determine other systems that can participate according to the typical scenarios and activity processes of aircraft engine operation monitoring, and determine the top-level functions of the EHM ground system. For example, the airborne EHM is responsible for collecting continuous data after the engine is started and generating supplementary messages, manual messages, and post-flight messages. The avionics system is responsible for collecting and storing the data of the airborne EHM and the aircraft after power-on, generating corresponding messages in each flight phase and making abnormal judgments and processing, storing the messages generated in the aircraft phase and the messages generated by the airborne EHM, etc. The operation and use data management system is responsible for continuous data reception, receiving messages on the server, decoding and storing them in the database, and importing the solutions of the engine main manufacturer's quick response system into the case database. Among them, the EHM ground system requirements can include: the engine status data processing and analysis should be realized, the engine abnormality classification alarm should be issued and the traceability process should be established, the maintenance proposal should be issued, and the monitoring plan update requirements should be fed back to the design and development.

[0069] Combine the following Figure 2 The modeling sequence shown specifically expands the EHM ground system functional design modeling process.

[0070] First, from the perspective of system design and development, according to the scenario-based interactive business activity design, the requirements of the activity participants are converted into functional requirements of the system, and the activity participants are assigned to the system. For example, the EHM ground system belongs to the activity participant, the main engine manufacturer. Then, the interface between EHM and the external system is established. The SV-1 view can be used to express the interface relationship between the EHM system and the external system, and the type is a structure diagram.

[0071] Then, based on the business activities assigned to the EHM ground system, the knowledge and technology field is used to carry out system function decomposition and analysis, and the functions are assigned to different lanes. The internal components of each lane are defined, and the SV-4 view is used to describe and express the system function flow, including the functions of the EHM ground system and the data flow between the functions and the interaction with the external system function flow. The type is a structure diagram.

[0072] Next, analyze the synchronous or asynchronous information transmitted between systems, that is, the timing migration of business activities, and use the SV-10c view to describe and express the system timing. The type is a timing diagram, so as to establish the events and sequence of the functions executed by each system during the entire operation process.

[0073] Then, analyze the status of the EHM ground system and other external systems, analyze the system's state transition logic, establish the state machine and state transfer conditions of each activity participant, integrate the various functions assigned in the previous steps, and use the SV-10b view to express the system state transition, which is a state machine type.

[0074] On this basis, develop simulation components of the system function model, write test cases, and use human-in-the-loop simulation methods to verify the logic and rationality of the model. You can also establish a system interaction matrix to describe the system interface, and use the SV-3 view to describe the interaction relationship between systems. The type is table. Establish system resource interaction, use the SV-2 view to describe the interface and interaction content between systems, and the type is a structure diagram. Finally, establish a system function-activity mapping matrix, and use the SV-5b view to analyze whether the system function design can meet the execution of activities. The type is table.

[0075] The design method of the aviation engine health management ground system provided by the present invention is based on the standard modeling language SysML (Systems Modeling Language) of system engineering, and adopts the Unified Profile for DoDAF and MoDAF (UPDM) defined by the Object Management Group (OMG), and combines the design characteristics of the engine customer service product to form a system architecture model design tool that meets the DoDAF2.0 standard. The characteristics of the system architecture expressed by the model include clear system functions, clear underlying logic of system data, clear data flow content, and obvious interface relationships between different systems. This system architecture modeling expression effectively eliminates the ambiguity problems easily caused by natural language, avoids the understanding deviation caused by the unclear meaning of pure document materials, and helps different professional and technical personnel to quickly align their understanding, achieve efficient communication, and improve cross-business communication efficiency.

[0076] In a preferred embodiment, the design method provided by the present invention may also include: after the design of each interactive business activity or system function is completed, simulation verification and confirmation of the system model are performed, and the system model is iteratively optimized based on the feedback of the verification and confirmation results.

[0077] Figure 7 FIG. 4 is a flow chart of a system model simulation verification process according to an embodiment of the present invention.

[0078] In order to verify the logical correctness, functional accessibility and integrity, and requirement coverage of the EHM ground system architecture in different application scenarios, it is necessary to perform logical self-consistent simulation and verification on the architecture model. Figure 7, design test case documents based on typical operation monitoring scenarios. Test cases should be constructed separately from each perspective and be able to fully cover the normal and abnormal conditions of the entire operation process. In the EHM system product architecture model design tool, complete the code framework generation and run the simulation model to complete the logical self-consistency verification and test case verification respectively, and complete the model iterative optimization based on the verification and business feedback results. Using test cases to simulate and verify the EHM ground system architecture can intuitively find out whether the architecture model can correctly and completely reflect its functions, logical interactions, interface relationships, etc. in the EHM process. According to the simulation test results, iterative optimization of the architecture model can be achieved, which provides guarantee for the quality of the EHM ground system architecture model and provides a test basis for the subsequent optimization and reuse of the EHM ground system architecture.

[0079] Understandably, the use of simulation to verify the functional logic of the EHM system architecture design can also eliminate unreasonable designs in the design phase, thereby accelerating the optimization and iteration of complex system product architectures. Human-in-the-loop simulation and superposition of different test cases can incorporate random factors in the system usage environment, that is, the architecture of complex EHM systems is simulated and verified using test cases with uncertainty. This type of architecture model simulation verification not only provides a visual means to deduce the self-consistency of the architecture model logic, but also makes the activities and resource exchanges of various stakeholders explicit, facilitating the accelerated iteration of the architecture model.

[0080] It should be noted that the simulation verification of the EHM ground system architecture model belongs to the executable logic model simulation. Different from common simulation work such as algorithm simulation and three-dimensional model simulation, the simulation process is also a visual display of the simulation results. When executing the system architecture model simulation, the state nodes, state transitions, and state response actions of each view model are observed to see whether they meet the business requirements to determine whether the model behavior logic and functions are complete and correct.

[0081] Although the above methods are illustrated and described as a series of actions for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but understandable to those skilled in the art.

[0082] Figure 8 It is a schematic diagram of the device structure of a design device for an aircraft engine health management ground system according to another aspect of the present invention.

[0083] According to another aspect of the present invention, this document also provides an embodiment of a design device 800 for an aircraft engine health management ground system.

[0084] like Figure 8 As shown, the design device 800 of the aircraft engine health management ground system provided in this embodiment may include a memory 801 and a processor 802 coupled to the memory 801. The processor 802 may be configured to implement any of the above-mentioned design methods of the aircraft engine health management ground system.

[0085] According to another aspect of the present invention, an embodiment of a computer storage medium is also provided herein.

[0086] The computer storage medium stores a computer program, which, when executed by a processor, can implement any of the steps of the above-mentioned design method for an aircraft engine health management ground system.

[0087] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the present invention.

[0088] The processor described in this case can be implemented using electronic hardware, computer software or any combination thereof. Whether such processors are implemented as hardware or software will depend on the specific application and the overall design constraints imposed on the system. As an example, the processors presented in this disclosure, any part of the processors, or any combination of processors can be implemented with microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable processing components configured to perform various functions described throughout this disclosure. The functionality of the processors presented in this disclosure, any part of the processors, or any combination of processors can be implemented with software executed by a microprocessor, microcontroller, DSP or other suitable platform. 。

[0089] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0090] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A design method for an aircraft engine health management ground system, the design method using a multi-view view in an architecture model tool, the design method comprising: Identify stakeholders of aircraft engines, collect the stakeholders' requirements for the use of the health management ground system, and analyze the top-level requirements of the health management ground system; Based on the various scenarios of aircraft engine delivery, use and maintenance, analyze and design the interactive business activities of the stakeholders, so as to decompose the top-level requirements of the health management ground system into the interactive business activities of the stakeholders; as well as Based on the interactive business activities of the stakeholders, the system functions of the health management ground system are analyzed and designed, and a system model is established to implement the design work of the health management ground system.

2. The design method according to claim 1, characterized in that: The architecture model tool includes a DoDAF structural framework.

3. The design method according to claim 2, characterized in that: The stakeholders include the Civil Aviation Administration, aircraft manufacturers, engine manufacturers, engine purchasers, airlines, crews, airports, maintenance personnel, trainers and subsystem suppliers. The top-level requirements of the health management ground system are analyzed, including: The global view in the architecture model tool is used to describe the summary information of the system, and the capability view is used to describe the top-level requirements of the system.

4. The design method according to claim 2, characterized in that: The various scenarios of aircraft engine delivery, use and maintenance include pre-service maintenance, route operation, workshop maintenance and decommissioning. The analysis and design of various interactive business activities of the stakeholders include: Analyze and design the relationships between stakeholders involved in each interactive business activity in each scenario, as well as the activity flow of each interactive business activity.

5. The design method according to claim 4, characterized in that: The analysis and design of various interactive business activities of the stakeholders also includes: The activity view in the architecture model tool is used to describe the organizational relationship, interaction relationship, interaction data flow and control flow, interaction activity interface and resources between the stakeholders, and the activity status of each interactive business activity. The timing diagram in the activity view is used to describe the events and occurrence order of each interactive business activity.

6. The design method according to claim 5, characterized in that: The design method further comprises: After performing the analysis and designing the interactive business activities of the stakeholders, the capability view in the architecture model tool is used to analyze whether the designed interactive business activities can meet the top-level requirements of the health management ground system.

7. The design method according to claim 2, characterized in that: The system functions of the health management ground system are analyzed and designed based on the interactive business activities of the stakeholders, including: Using the system view in the system architecture model tool to describe the external interface of the health management ground system, the internal and external interactive function data flow, the events and sequence of executing functions, the interactive relationship between systems and the interactive resources; and Use the system view to analyze whether the designed system functions can meet the execution of the various interactive business activities.

8. The design method according to claim 1, characterized in that: The design method further comprises: After the interactive business activities or system functions are designed, the system model is simulated, verified and confirmed, and the system model is iteratively optimized based on the feedback of the verification and confirmation results.

9. A design device for an aircraft engine health management ground system, comprising: Memory; as well as A processor coupled to the memory, wherein the processor is configured to execute the design method for an aircraft engine health management ground system according to any one of claims 1 to 8.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for designing an aircraft engine health management ground system according to any one of claims 1 to 8 is implemented.

Images