Aero-engine health management system

Abstract

The invention particularly relates to an aero-engine health management system. The architecture of the aero-engine health management system comprises a base layer, a platform layer, an application layer and a display layer, the base layer provides computing resources, storage resources and a database required by platform software operation; the platform layer comprises a general basic platform layer and a business platform layer; the general basic platform layer provides basic platform software functions for a user, and is divided into an offline client mode and an online client mode according to the use environment of the user; the business platform layer is used for meeting EHM business requirements of the system, and comprises real-time data state monitoring, physical examination analysis, fault diagnosis, trend analysis, life management, data playback, lubricating oil spectrum analysis, performance screening, brief report customization, third-party algorithm, flight parameter rapid interpretation and performance attenuation analysis; the application layer is used for a user to select an aero-engine model of which data needs to be analyzed in a current use environment through selection configuration; and the display layer provides an operable and result display page for the user.

Description

Technical Field

[0001] The present application belongs to the technical field of aviation engine health management, and specifically relates to an aviation engine health management system. Background Art

[0002] In recent years, with economic development, scientific and technological advancements, and improvements in materials and processes, the research and development of aircraft engines has gradually matured. However, with the maturation and use of aircraft engines, their operational maintenance and condition-based repairs are receiving increasing attention.

[0003] Traditional aircraft engine maintenance relies on manual data playback, spectral analysis, and boresight inspections. Simultaneously, aircraft engine technicians design flight parameter judgment algorithms and analyze engine data using flight parameter interpretation software as a basis for flight launch. Each aircraft engine model has its own software requirements tailored to its specific operational requirements. During field maintenance, all aircraft engines are provided with flight parameter interpretation software. However, software version management is chaotic, making it difficult to meet the efficient maintenance and operation needs of multiple aircraft engine models and batches.

[0004] The main shortcomings of traditional aircraft engine maintenance and support methods are as follows:

[0005] 1) All aircraft engine models are required to provide flight parameter interpretation software, but software version management is chaotic;

[0006] 2) Aircraft engines involve multiple disciplines. During operation, maintenance, and support, each discipline has corresponding monitoring requirements. The proposed algorithm will be adjusted according to usage. Adding algorithm function modules to flight parameter interpretation software is complex, making it difficult to achieve plug-and-play functional algorithms without affecting the flight parameter interpretation program.

[0007] 3) Aircraft engine condition assessment relies on flight parameter interpretation software and manual inspections. As aircraft engine usage demands change, the use scenarios are diverse, including daily inspections, periodic inspections, and long-term trend forecasts. Furthermore, consideration must be given to scenarios such as use in high-altitude environments, training, and drills. Flight parameter interpretation software and manual inspections are no longer sufficient to meet these diverse needs.

[0008] 4) When analyzing multiple aircraft engines, users rely solely on flight parameter interpretation software and auxiliary manual data analysis and inspection, which is time-consuming and labor-intensive, affecting the rapid comprehensive evaluation and deployment of aircraft engines.

[0009] This application is proposed in view of the above-mentioned technical defects. Summary of the Invention

[0010] The purpose of this application is to provide an aircraft engine health management system to overcome or alleviate at least one of the known technical deficiencies.

[0011] The technical solution of this application is:

[0012] An aircraft engine health management system, whose architecture includes a basic layer, a platform layer, an application layer, and a display layer;

[0013] The basic layer provides the computing resources, storage resources, and databases required for the platform software to run;

[0014] The platform layer includes the general basic platform layer and the business platform layer;

[0015] The general basic platform layer provides users with basic platform software functions and is divided into two modes according to the user environment:

[0016] Offline client mode provides basic platform functions, including standard interfaces, user management, user personal center, user-defined pages, local data management, business integration, and local status monitoring functions;

[0017] The online client mode includes the basic functions of the platform, as well as data interface protocols, server-side user management, user personal center, server-side business management, algorithm integration development, user-defined pages, server-side data management, real-time status detection, workflow and real-time alarm functions.

[0018] The business platform layer is used to meet the EHM business needs of the system, including real-time data status monitoring, physical examination analysis, fault diagnosis, trend analysis, life management, data playback, lubricating oil spectrum analysis, performance screening, briefing customization, third-party algorithms, rapid interpretation of flight parameters, and performance degradation analysis;

[0019] The application layer allows users to select the aircraft engine model whose data needs to be analyzed in the current usage environment through configuration selection;

[0020] The presentation layer provides users with actionable and result display pages.

[0021] Optionally, in the above-mentioned aircraft engine health management system, the display layer provides users with operational and result display pages, including aircraft management, aircraft engine management, accessory history management, and custom pages.

[0022] Optionally, the above-mentioned aircraft engine health management system includes data preprocessing, algorithm library, information library, file library, and result display module;

[0023] The data preprocessing module has data preprocessing functions, including data analysis, data extraction, data distribution, and working condition data extraction;

[0024] The algorithm library includes multiple algorithm modules, including flight parameter interpretation module, data playback module, parameter detection and fault diagnosis module, trend analysis module, life management module, performance degradation analysis module, event message analysis module, lubricating oil spectrum analysis module, algorithm scheduling module, and algorithm cascade module, which are used to execute corresponding algorithm functions;

[0025] The information database is used to store pre-processed data, including user information, knowledge information, fault information, engine information, as well as intermediate data, judgment criteria, fault information, and corresponding expert advice;

[0026] The information database provides data support and information assistance for each algorithm module, including aircraft engine history, function usage configuration, data access configuration, model information, and flight information;

[0027] The information database collects and stores the intermediate data, result data, and configurations generated by each algorithm module;

[0028] The file library is used to store flight parameter data, test data, and engine information, providing data support and information assistance for each algorithm module, including flight parameter data, airborne data, test data, event message data, and lubricating oil spectrum data;

[0029] The analysis results of each algorithm module are stored in the information database in the form of information and passed to the result display module to realize trend drawing and report display, and generate aviation engine briefing reports, test reports, and test cards.

[0030] Optionally, in the above-mentioned aviation engine health management system, the data preprocessing module obtains data from the local machine or server, converts the data through data parsing format, and extracts the required parameter data according to the settings of the configuration file. It can meet the different needs of parameter data required by different algorithms, support the extraction of multiple different parameter set data in one operation, match the personalized data needs of different algorithms, and simplify the algorithm's processing of data.

[0031] Optionally, the above-mentioned aircraft engine health management system further includes a network support module;

[0032] The network support module provides network interface and cross-domain data interface, among which,

[0033] The network interface is used to realize communication and data exchange with the server;

[0034] The cross-domain data interface is used to realize the transfer and merging of databases.

[0035] Optionally, in the above-mentioned aircraft engine health management system, the network support module also provides maintenance decision support functions, interface and integration functions.

[0036] This application has at least the following beneficial technical effects:

[0037] Providing an aircraft engine health management system has the following advantages for aircraft engine maintenance:

[0038] 1) The system architecture is designed to meet the needs of aircraft engine operation, maintenance and support. It can integrate the operation, maintenance and support software of multiple models of aircraft engines and submit them to users to solve the problem of software version confusion. The login interface of different engine models can be switched through the system architecture application layer, and the software versions of various models are managed in a unified manner.

[0039] 2) Under a unified architecture, by designing data interface standards, in addition to being compatible with multiple models of flight parameter judgment software, it can provide access to multi-professional aviation engine functional algorithm programs and the integration of third-party algorithms provided by scientific research institutes. Through a common basic platform, a standard data interface or data protocol is provided to facilitate third-party algorithms to directly obtain the required parameters, realizing plug-and-play of functional algorithms.

[0040] 3) In addition to providing flight parameter judgment programs, it also provides functional programs such as status monitoring, fault diagnosis, life management, trend analysis, physical examination analysis, performance screening, and briefing customization, which are convenient for selective use in multiple scenario modes such as daily inspection, regular inspection and long-term trend forecasting. In addition, a variety of functional algorithms can be integrated through the system architecture business platform, and the algorithm can be executed according to the general basic platform data standards and protocols. The algorithm execution results can be displayed in the corresponding display layer of the system architecture. By comprehensively analyzing the algorithm operation results, support can be provided for the rapid deployment of aircraft engines.

[0041] 4) Through rapid batch data processing, while various algorithm engineering programs can be executed in parallel, the general basic platform and business platform in the system architecture business platform can realize rapid batch processing of data in accordance with data standard interfaces and protocols. Through the unified execution and operation result integration of various functional algorithm modules, the health assessment of aircraft engines can be quickly realized, saving the time cost of manual data analysis, and can avoid misjudgment caused by manual analysis through unified program interpretation. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 Schematic diagram of the aircraft engine health management system architecture provided by an embodiment of the present application;

[0043] Figure 2 This is a schematic diagram of the data flow of the aircraft engine health management system provided in an embodiment of the present application.

[0044] In order to better illustrate this embodiment, some contents of the drawings may be omitted, enlarged or reduced, which is only used for illustrative purposes and should not be construed as limiting the present application. DETAILED DESCRIPTION

[0045] To make the technical solution and its advantages of this application more clear, the technical solution of this application will be further described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described here are only some of the embodiments of this application and are only used to explain this application, not to limit this application. It should be noted that for ease of description, only the parts relevant to this application are shown in the accompanying drawings, and other relevant parts can refer to the general design.

[0046] In addition, unless otherwise defined, the technical or scientific terms used in the description of this application shall have the ordinary meanings understood by those skilled in the art to which this application belongs. The term "include" as used in the description of this application means that the concepts preceding the term include the concepts listed after the term and their equivalents, without excluding other related concepts.

[0047] The aircraft engine health management system is used for the maintenance and support of aircraft engines, and its design needs to comprehensively consider various usage scenarios.

[0048] During the aircraft engine development phase, the design unit must conduct bench tests and environmental testing, as well as high-altitude simulation tests on an altitude test platform, to monitor the aircraft engine's status. During the scientific research flight test phase, various scientific research flight test subjects must be verified, while the aircraft engine's health status must be continuously assessed. During the delivery phase, ongoing maintenance and support for the aircraft engine is required. Users will deploy relevant software in the flight control room and maintenance team to analyze data and compile reports, greatly facilitating user operation and maintenance.

[0049] A health monitoring system specifically designed for aircraft engines requires comprehensive consideration. While ensuring the normal operation of the stand-alone aircraft engine ground health management system in the field, the need to deploy the ground health management system software on the user's local area network must also be considered. Aircraft transfers are another routine scenario. Upon return, aircraft or flight parameter data is brought back, which needs to be imported into the user's server for consolidated and cumulative processing. This also requires comprehensive consideration of the health monitoring system software's ability to maintain a separate database. Collaboration among various research institutions requires the use of relevant data resources from the health monitoring system for algorithm research and verification. The health monitoring system needs to consider improving collaboration convenience, mechanism innovation, and technological innovation under controlled conditions through open permissions and data management.

[0050] The following table shows the usage scenarios of the aircraft engine health management system:

[0051] This application provides an aircraft engine health management system that integrates maintenance and support software for multiple aircraft engine models, resolving software version confusion. It also designs a unified standard data interface, compatible with multiple specialized functional algorithms. The system architecture application layer allows for switching between different engine login interfaces, while also managing unified software versions for each model. By rapidly and comprehensively analyzing algorithm execution results, it provides an aircraft engine health assessment report, facilitating system support for rapid aircraft engine deployment.

[0052] The architecture of the aircraft engine health management system is the core of the development of the health monitoring system, such as Figure 2 As shown in the figure, the architecture supports the analysis and processing of data in various storage formats for aircraft engines, providing solutions for parsing multiple types of flight parameter data, accelerating data extraction and alleviating the pressure on algorithms to process data. Flexible configuration interfaces are provided, enabling customized output for multiple algorithms simultaneously, with interfaces reserved for the addition of new algorithms. Compatible with algorithms developed in different languages, this increases the system's openness, flexibility, and scalability. An integrated platform supports effective algorithm scheduling and builds a universal and efficient aircraft engine health management system. Dedicated terminal platform EHM business application software and dedicated business application interfaces are developed for end users in multiple scenarios, enabling flexible version control for multiple aircraft engine models. This platform allows for the development of terminal-specific aircraft engine business content, customized services for corresponding aircraft engine models, and support for the integration of third-party services, resulting in a simple interface. The system architecture's general foundation platform and business platform provide standard data interfaces and protocols to facilitate the processing of aircraft engine data in various storage formats. Processed data is provided to various function algorithm programs according to standard data protocols. Algorithm programs directly call parameters based on standard data interfaces. The software platform architecture supports multi-language programming, allowing for rapid integration and deployment of third-party algorithms at the business platform level.

[0053] The architecture of the aircraft engine health management system includes the basic layer, platform layer, application layer, and display layer.

[0054] The basic layer provides the computing resources, storage resources, and databases required for the operation of the platform software.

[0055] The platform layer includes the general basic platform layer and the business platform layer.

[0056] The general basic platform layer mainly provides users with basic platform software functions and is divided into two modes according to the user's usage environment:

[0057] Offline client mode provides basic platform functions, including standard interfaces, user management, user personal center, user-defined pages, local data management, business integration, local status monitoring, etc.

[0058] The online client mode, in addition to the above functions, also includes data interface protocol, server-side user management, user personal center, server-side business management, algorithm integration development, user-defined pages, server-side data management, real-time status detection, workflow, and real-time alarm functions.

[0059] The business platform layer primarily addresses the system's EHM business requirements, including real-time data status monitoring, health check analysis, fault diagnosis, trend analysis, lifespan management, data playback, oil spectrum analysis, performance screening, customized briefings, third-party algorithms, rapid interpretation of flight parameters, and performance degradation analysis. To subsequently add fault prediction and health management, only service interfaces need to be provided to the service bus, while also opening these services to the system portal for user access.

[0060] The application layer allows users to select the aircraft engine model whose data needs to be analyzed in the current usage environment through configuration selection.

[0061] The display layer mainly provides users with operational and result display pages, including aircraft management, aircraft engine management, accessory history management, custom pages, etc.

[0062] The data flow of the aircraft engine health management system is as follows Figure 2 As shown, the health management system supports multiple formats of aircraft engine input data. Each functional module accesses aircraft engine data from a file library. The algorithm execution module analyzes each functional algorithm. The analysis results are matched with relevant events, fault information, and expert knowledge in the information library to generate a health assessment report, providing support for aircraft engine operation and maintenance. The aircraft engine health management system's interface design and presentation are flexibly configurable. It facilitates management of aircraft engine basic information, reports, algorithm libraries, fault libraries, and knowledge bases. The content and format of the output health management assessment report can be customized.

[0063] The aviation engine health management system includes functional modules such as data preprocessing, algorithm library, information library, file library, result display module, and network support module.

[0064] The aircraft engine health management system relies on two data sources: obtaining flight parameter and controller data from local folders, and downloading these data from a server. The latter approach allows for direct acquisition of test data from the institute's information system, as well as for the Flight Parameter Room to obtain flight parameter data directly from the station's local area network, rather than downloading and transferring data from a third-party digital platform.

[0065] The data preprocessing module has data preprocessing functions such as data analysis, data extraction, data distribution, and working condition data extraction.

[0066] The data preprocessing module retrieves data from the local machine or server, converts the data through data parsing formats, and extracts the required parameter data according to the configuration file settings. This not only accelerates data processing but also reduces the output processing pressure of subsequent algorithm modules. To meet the different parameter data requirements of different algorithms, the module supports extracting multiple different parameter sets in a single operation, matching the personalized data needs of different algorithms, simplifying the algorithm's data processing, and helping algorithm developers focus on their expertise.

[0067] The algorithm library includes flight parameter interpretation module, data playback module, parameter detection and fault diagnosis module, trend analysis module, life management module, performance degradation analysis module, event message analysis module, lubricating oil spectrum analysis module, algorithm scheduling module, algorithm cascade module and other algorithm modules to execute corresponding algorithm functions.

[0068] The information database is used to store data that has undergone data preprocessing, including user information, knowledge information, fault information, engine information, as well as intermediate data, judgment criteria, fault information, corresponding expert advice, etc.

[0069] The information database provides data support and information assistance for each algorithm module, including aircraft engine history, function usage configuration, data access configuration, model information, flight information, etc.

[0070] The information database collects the intermediate data, result data, configuration, etc. generated by each algorithm module and stores them to provide data management support for subsequent use.

[0071] The file library is used to store flight parameter data, test data, and engine information, providing data support and information assistance for each algorithm module, including flight parameter data, airborne data, test data, event message data, lubricating oil spectrum data, etc.

[0072] The analysis results of each algorithm module are stored in the information database in the form of information and passed to the result display module to realize trend drawing and report display, generate aircraft engine briefing reports, test reports, test cards, etc., and provide digital support for aircraft engine status assessment.

[0073] The network support module provides a network interface and a cross-domain data interface. The network interface is used to realize communication and data exchange with the server, and the cross-domain data interface is used to realize the transfer and merging of databases.

[0074] The network support module can also provide maintenance decision support functions, interface and integration functions, etc.

[0075] In order to realize the functions of communication, scheduling, data transmission and management, an aviation engine health management system can also be designed, including an engine information management module, a report management module, an algorithm execution module, a fault library management module, a knowledge base management module, a user management module, a log management module, a communication service module (can you further explain the functions of each module and its cross-linking relationship with other functional modules), etc. The management modules provided are used for aircraft and engine information and fault management. The relevant information is associated with the results of the functional algorithms of the business platform layer to jointly realize the customized generation of engine health assessment reports. To realize the corresponding functions, please refer to Figure 2 For example, the communication service module is used to realize communication with the engine test bench and aircraft system, and is used to transmit ground test bench data, high-altitude test bench data, event insulation data, lubricating oil spectrum data, airborne data, flight parameter data, event message data, etc.

[0076] The aircraft engine health management system disclosed in the above-mentioned embodiments utilizes a unified architecture to integrate the operational and maintenance requirements of multiple aircraft engines into the health monitoring system software for development and user delivery. The system can be designed to consist of both a web-based and stand-alone version, offering onboard real-time monitoring and offline analysis capabilities. It can directly analyze and interpret raw data from single or multiple aircraft flights, enabling rapid interpretation of aircraft engine data, condition monitoring, fault diagnosis, lifespan management, trend analysis, and health status assessment. It also meets users' needs for understanding aircraft engine operational status, intuitively providing comprehensive recommendations on aircraft engine health and operation, and supporting aircraft engine test runs and field flights. The system can be used for both field user aircraft engine parameter interpretation and real-time test data monitoring and algorithm verification. Through rapid data processing and analysis, it integrates multiple analysis results to perform aircraft engine health assessments, saving labor costs while improving the accuracy of aircraft engine health assessments and enhancing aircraft engine operational and maintenance support capabilities. The system architecture supports web and stand-alone deployment, and can provide standard data interfaces and protocols through the same basic platform, support online and offline software operation, deploy functional algorithm programs at the business platform layer, support third-party algorithm integration based on the provided standard data, and has the ability to continuously expand functional algorithms. Based on different functional algorithms, it can meet the needs of different scenarios and different personnel.

[0077] In addition, technical personnel in the field should also be able to realize that the various modules of the aircraft engine health management system disclosed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, this application generally describes them according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Technical personnel in the field can choose to use different methods to implement the described functions for each specific application and its actual constraints, but such implementation should not be considered to be beyond the scope of this application.

[0078] So far, the technical solution of the present application has been described in conjunction with the preferred embodiments shown in the accompanying drawings. Those skilled in the art should understand that the scope of protection of the present application is obviously not limited to these specific embodiments. Without departing from the principles of the present application, those skilled in the art can make equivalent changes or replacements to the relevant technical features, and the technical solutions after these changes or replacements will fall within the scope of protection of the present application.

Claims

1. An aircraft engine health management system, characterized in that: Its architecture includes the basic layer, platform layer, application layer, and presentation layer; The basic layer provides the computing resources, storage resources, and databases required for the platform software to run; The platform layer includes the general basic platform layer and the business platform layer; The general basic platform layer provides users with basic platform software functions and is divided into two modes according to the user environment: Offline client mode provides basic platform functions, including standard interfaces, user management, user personal center, user-defined pages, local data management, business integration, and local status monitoring functions; The online client mode includes the basic functions of the platform, as well as data interface protocols, server-side user management, user personal center, server-side business management, algorithm integration development, user-defined pages, server-side data management, real-time status detection, workflow and real-time alarm functions. The business platform layer is used to meet the EHM business needs of the system, including real-time data status monitoring, physical examination analysis, fault diagnosis, trend analysis, life management, data playback, lubricating oil spectrum analysis, performance screening, briefing customization, third-party algorithms, rapid interpretation of flight parameters, and performance degradation analysis; The application layer allows users to select the aircraft engine model whose data needs to be analyzed in the current usage environment through configuration selection; The presentation layer provides users with actionable and result display pages.

2. The aircraft engine health management system according to claim 1, characterized in that: The display layer provides users with operational and result display pages, including aircraft management, aircraft engine management, accessory history management, and custom pages.

3. The aircraft engine health management system according to claim 2, characterized in that: Including data preprocessing, algorithm library, information library, file library, and result display modules; The data preprocessing module has data preprocessing functions, including data analysis, data extraction, data distribution, and working condition data extraction; The algorithm library includes multiple algorithm modules, including flight parameter interpretation module, data playback module, parameter detection and fault diagnosis module, trend analysis module, life management module, performance degradation analysis module, event message analysis module, lubricating oil spectrum analysis module, algorithm scheduling module, and algorithm cascade module, which are used to execute corresponding algorithm functions; The information database is used to store pre-processed data, including user information, knowledge information, fault information, engine information, as well as intermediate data, judgment criteria, fault information, and corresponding expert advice; The information database provides data support and information assistance for each algorithm module, including aircraft engine history, function usage configuration, data access configuration, model information, and flight information; The information database collects and stores the intermediate data, result data, and configurations generated by each algorithm module; The file library is used to store flight parameter data, test data, and engine information, providing data support and information assistance for each algorithm module, including flight parameter data, airborne data, test data, event message data, and lubricating oil spectrum data; The analysis results of each algorithm module are stored in the information database in the form of information and passed to the result display module to realize trend drawing and report display, and generate aviation engine briefing reports, test reports, and test cards.

4. The aircraft engine health management system according to claim 3, characterized in that: The data preprocessing module obtains data from the local machine or server, converts the data through data parsing format, and extracts the required parameter data according to the settings of the configuration file. It can meet the different needs of parameter data required by different algorithms and support the extraction of multiple different parameter set data in one operation to match the personalized data needs of different algorithms and simplify the algorithm's processing of data.

5. The aircraft engine health management system according to claim 4, characterized in that: It also includes a network support module; The network support module provides network interface and cross-domain data interface, among which, The network interface is used to realize communication and data exchange with the server; The cross-domain data interface is used to realize the transfer and merging of databases.

6. The aircraft engine health management system according to claim 5, characterized in that: The network support module also provides maintenance decision support, interface and integration functions.

Images