KR102730085B1 - Aircraft health management method and aircraft health management pparatus - Google Patents

Abstract

An aircraft health management method according to an embodiment of the present invention may include a process for storing operational data collected for each component of an operating aircraft, a process for identifying a data format type of the operational data, a process for determining whether the data format type of the identified operational data is identical to a preset reference data format type, a process for converting the data format type of the operational data into the reference data format type when the data format type of the operational data is different from the reference data format type, and a risk factor determination process for determining whether each component is a risk factor by using at least one of the operational data determined to have the same data format type as the reference data format in the determination process and the operational data converted into the reference data format type by the conversion process.
According to embodiments of the present invention, when the data format type of the operating data is different from the reference data format type, which is a data format type that can be displayed on the display unit, the data format type of the operating data can be converted into the reference data format type. Accordingly, in generating judgment data for determining whether each component is a risk factor, the judgment data can be generated in the reference data format type that can be displayed on the display unit. Accordingly, judgment data that determines whether each component is a risk factor can be displayed on the display unit regardless of the data format of the operating data.

Description

{AIRCRAFT HEALTH MANAGEMENT METHOD AND AIRCRAFT HEALTH MANAGEMENT PPARATUS}

The present invention relates to an aircraft health management method and an aircraft health management device, and more specifically, to an aircraft health management method and an aircraft health management device capable of stably managing the health of an aircraft using operational data acquired during operation of the aircraft.

The main causes of aircraft accidents are aircraft defects, human factors, and natural disasters. In order to prevent aircraft accidents caused by aircraft defects, aircraft must maintain airworthiness.

Traditionally, regular replacement work on aircraft components was performed before and after the aircraft was put into service according to a program approved by the airworthiness authority. This is called preventive health management.

However, even if the components are managed using the preventive health management method, problems may occur in the operation of the aircraft. This is because defects in the components may occur due to other factors such as unexpected situations even before the replacement cycle has been reached. In addition, even if the components have not yet developed defects, abnormal operation may occur temporarily. Therefore, there is a limit to the stable management of the aircraft using the preventive health management method.

To address these issues, methods are being developed to collect operational data during aircraft operation and analyze the operational data to identify risk factors that are likely to cause or have caused defects.

However, the data format type of the operational data is different for each component, and the display unit equipped on the aircraft can only display data having a specific data format type. Therefore, even if risk factors are derived using the operational data, it is difficult to display the derived data on the display unit so that the pilot can confirm it.

Korean Patent Publication No. 10-2020-0008550

The present invention provides an aircraft health management device and an aircraft health management method capable of generating risk factor judgment data that can be displayed on a display unit regardless of the data format of operational data.

An aircraft health management method according to an embodiment of the present invention may include: a process for storing operational data collected for each component of an operating aircraft; a process for identifying a data format type of the operational data; a process for determining whether the data format type of the identified operational data is identical to a preset reference data format type; a process for converting the data format type of the operational data into a reference data format type when the data format type of the operational data is different from the reference data format type; and a risk factor determination process for determining whether a component is a risk factor by using at least one of the operational data determined to have a data format type identical to the reference data format in the determination process and the operational data converted into the reference data format type by the conversion process.

The above-mentioned standard data format type can be set as a data format type that can be displayed on a display section equipped in the cockpit of an aircraft and visually confirmed by a pilot.

The data format type of the judgment data including the judgment result determined in the above risk factor judgment process may be the above reference data format type.

In storing the collected operation data for each component, a plurality of operation data according to the collected time are stored for each component, and the risk factor determination process may include a process of determining whether abnormal operation data is included among the plurality of operation data according to the collected time for each component; and a process of determining the component that generated the abnormal operation data as a risk factor if the plurality of operation data includes abnormal operation data.

In storing the collected operation data for each component, a plurality of operation data according to the collected time are stored for each component, and the risk factor determination process may include a process of determining whether abnormal operation data is included among the plurality of operation data according to the collected time for each component; and a process of determining the component that generated the abnormal operation data as a risk factor if the time at which the abnormal operation data is generated exceeds a preset reference time when the abnormal operation data is included among the plurality of operation data.

The process of determining whether abnormal operation data is included among the above plurality of operation data may include a process of determining operation data that falls outside a preset standard operation data range among the plurality of operation data as abnormal operation data.

A process for determining a risk level for a component determined as a risk factor, which is performed after the above risk factor determination process; and the process for determining the risk level may include a process for determining the risk level of a component determined as a risk factor as a caution level or a warning level with a higher risk level than the caution level, based on a difference between abnormal operation data and reference operation data.

It may include a process of storing judgment data including the judgment result of the above risk factor judgment process in a risk factor storage unit, which is a virtualization platform.

It includes a process of storing judgment data including the judgment result of the above risk factor judgment process in a risk factor storage unit which is a virtualization platform, and the risk factor storage unit can store the judgment data by classifying it according to the risk level included in the judgment data.

The data format type and reference data format type of the above operating data can be any one of the Ethernet type, ARINC 818 type, and ARINC 429 type.

At least one of maintenance and replacement may be performed on components identified as hazardous.

An aircraft health management device according to an embodiment of the present invention may include an operation data unit capable of storing operation data collected for each component of an operating aircraft; an identification unit capable of identifying a data format type of the operation data transmitted from the operation data unit; a conversion necessity determination unit capable of determining whether the data format type of the operation data identified by the identification unit needs to be converted into a reference data format type; a conversion unit capable of converting the data format type of the operation data determined to require conversion by the conversion necessity determination unit into the reference data format type; and a risk factor determination unit capable of determining whether a component is a risk factor by using at least one of the operation data determined to require conversion by the conversion necessity determination unit and the operation data converted by the conversion unit.

The above conversion necessity determination unit may determine that there is no need to change the data format type of the identified operating data if the data format type of the identified operating data in the identification unit is the same as the reference data format type, and may determine that there is a need to change the data format type of the identified operating data to the reference data format if the data format type of the identified operating data in the identification unit is different from the reference data format type.

The above conversion necessity judgment unit sets the above standard data format type, and a data format type that can be displayed on a display unit equipped in the cockpit of an aircraft and visually confirmed by a user can be set as the above standard data format.

The above risk factor determination unit generates determination data including the result of determining whether each component is a risk factor, and the data format type of the determination data generated by the risk factor determination unit may be the above reference data format.

In the above operation data section, the operation data for each component is stored, and a plurality of operation data are stored for each component, and a data processing section is included that organizes the plurality of operation data over time; and the data processing section can organize one of the plurality of operation data whose data format type has not been converted and the plurality of operation data whose data format type has been converted by the conversion section over time.

The above risk factor judgment unit judges operation data that falls outside the preset standard operation data range among multiple operation data as abnormal operation data.

The above risk factor determination unit determines a risk level for a component determined to be a risk factor, and the risk factor determination unit can determine the risk level of a component determined to be a risk factor as a caution level or a warning level with a higher risk level than the caution level based on the difference between the abnormal operation data and the standard operation data.

The risk factor storage unit may include a risk factor storage unit capable of storing judgment data on components judged as risk factors in the risk factor judgment unit, and the risk factor storage unit may be a virtualization platform.

The above risk factor storage unit may include a first storage unit capable of storing judgment data for components whose risk level is determined to be a caution level; and a second storage unit capable of storing judgment data for components whose risk level is determined to be a warning level.

According to embodiments of the present invention, when the data format type of the operating data is different from the reference data format type, which is a data format type that can be displayed on the display unit, the data format type of the operating data can be converted into the reference data format type. Accordingly, in generating judgment data for determining whether each component is a risk factor, the judgment data can be generated in the reference data format type that can be displayed on the display unit. Accordingly, judgment data that determines whether each component is a risk factor can be displayed on the display unit regardless of the data format of the operating data.

Due to this, the user can easily check whether there is a risk factor for each component and which components are judged to be risk factors by checking the judgment data displayed on the display unit. Accordingly, maintenance or replacement can be performed on components judged to be risk factors, thereby stably managing the health of the aircraft.

FIG. 1 is a conceptual diagram illustrating an aircraft health management device and a display unit connected to the aircraft health management device according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a process in which operational data is transmitted to each component of an aircraft health management device according to an embodiment of the present invention and a process in which a data format type is converted.
FIG. 3 is a flowchart illustrating an aircraft health management method according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in more detail with reference to the attached drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and these embodiments are provided only to make the disclosure of the present invention complete and to fully inform a person having ordinary skill in the art of the scope of the invention. In order to explain the embodiments of the present invention, the drawings may be exaggerated, and the same reference numerals in the drawings represent the same components.

An aircraft may include a fuselage, wings, engines, landing gear, a pressure regulator for controlling the pressure of the fuselage, a temperature regulator for controlling the temperature of the fuselage, and various sensors installed on the fuselage. In addition, an aircraft may include electronic devices for aircraft operation, such as takeoff and landing, flight, and mission performance.

The sensors may include a speed sensor capable of detecting a speed at which the aircraft is moving, an attitude sensor capable of detecting an attitude of the aircraft, an altitude sensor capable of detecting an altitude of the aircraft, a climb rate detection sensor capable of detecting a speed at which the aircraft ascends and descends (i.e., a climb rate), a turn sensor detecting information including a turn rate of the aircraft, and a heading sensor detecting a current heading of the aircraft. Of course, the aircraft is not limited to the examples described above and may further be equipped with various sensors for takeoff, landing, and flight of the aircraft.

Additionally, the aircraft has a cockpit, which is an area where a pilot can board, and the cockpit can be equipped with a control unit and a display unit.

The control unit may be a device that is connected or linked to each component equipped in the aircraft, so that the pilot can control or manipulate the operation of the components. The display unit may be a device that displays or displays the status of each component, the current location of the aircraft, the flight direction, and the flight path so that the pilot can visually check them.

The electronic device may include an electronic device for operating or working on the aircraft and an electronic device for performing a mission. In addition, a plurality of electronic devices may be provided, and at least some of the plurality of electronic devices may transmit or receive data to at least one of the other electronic devices and the control center. At this time, the electronic devices may transmit and receive data or signals using at least one of a wired network and a wireless network. In addition, the electronic device and the control center may transmit and receive data using a wireless network.

Hereinafter, devices, parts, etc. equipped in or constituting an aircraft are referred to as 'components'. For example, components of an aircraft may include a fuselage, wings, engines, landing gear, pressure regulators, temperature regulators, various sensors, and electronic devices. Of course, components of an aircraft are not limited to the examples described above, and may refer to all elements equipped in or constituting an aircraft.

The display unit may be configured to display or exhibit data having a specific format. The types of data formats of operational data that may be collected from an aircraft may include, for example, an Ethernet type data format, an ARINC 818 (Aeronautical Radio, Incorporated 818) type data format, an ARINC 429 (Aeronautical Radio, Incorporated 429) type data format, etc. The display unit may be configured to process and exhibit data having a data format of any one of a plurality of data formats, and may not be configured to exhibit data having any other type of data format. For example, the display unit may be configured to display data having an ARINC 429 type data format. In addition, the display unit may be configured to not be configured to exhibit data of any other type other than the ARINC 429 type.

'Data format' can mean 'data bus' or 'data format'. In addition, 'data whose data format type is Ethernet' can mean data that can be transmitted and received using Ethernet, 'data whose data format type is ARINC 818' can mean data that can be transmitted and received using ARINC 818, and 'data whose data format type is ARINC 429' can mean data that can be transmitted and received using ARINC 429.

As described above, there may be several types of data formats, and the type may vary depending on at least one of the word length or the word bit length, message structure, communication protocol, and data type. And, the data type may be an unsigned short, an unsigned char, etc.

A message structure includes a plurality of message fields, and the plurality of message fields can be listed in an assigned order. Data can be entered into each of the plurality of message fields, and the data entered into each message field can be different or partially the same. The data entered into the plurality of message fields can be 'contents' that the operation data conveys or means. Data or contents of different fields can be entered into the plurality of message fields. And, different types of data formats can have different data entered into each field. For example, one data format type can include first to fifth message fields, and field A data can be entered into the first message field, field B data can be entered into the second message field, field C data can be entered into the third message field, field D data can be entered into the fourth message field, and field E data can be entered into the fifth message field. And another data format type can include first to fifth message fields, and E field data can be entered in the first message field, D field data can be entered in the second message field, C field data can be entered in the third message field, B field data can be entered in the fourth message field, and A field data can be entered in the fifth message field.

During operation of an aircraft, operational data can be collected for each component of the aircraft. However, the operational data for each component may have different data format types. For example, during operation of an aircraft, operational data for a first component may have an Ethernet data format, operational data for a second component may have an ARINC 818 data format, and operational data for a third component may have an ARINC 429 data format. In addition, the display unit may be configured to display data whose data format type is, for example, ARINC 429.

For convenience of explanation, below, the operational data for the first component is referred to as the first operational data, the operational data for the second component is referred to as the second operational data, and the operational data for the third component is referred to as the third operational data.

By using the component-specific operational data acquired during the operation of the aircraft, it is possible to determine whether each component is a risk factor requiring maintenance or replacement. At this time, the data for the judgment result (hereinafter, judgment data) has a specific type of data format, and the type can be determined according to the data format type of the operational data. That is, if the data format type of the first operational data is Ethernet, the data format of the judgment data that determines whether the first component is a risk factor may be Ethernet type. As another example, if the data format type of the second operational data is ARINC 818, the format of the judgment data that determines whether the second component is a risk factor may be ARINC 818 type. As another example, if the data format type of the third operational data is ARINC 429, the format of the judgment data that determines whether the third component is a risk factor may be ARINC 429 type. However, if the data format of the judgment data is a data format that is not supported or used by the display unit, the judgment data cannot be displayed on the display unit.

The aircraft health management method and the aircraft health management device according to the embodiments can generate risk factor judgment data that can be displayed on the display unit, regardless of the data format of the operating data. That is, the aircraft health management method and the aircraft health management device according to the embodiments can convert the data format of the operating data and display judgment data that determines whether each component is a risk factor on the display unit. More specifically, in the embodiments, when the data format of the operating data and the type of the data format that can be displayed on the display unit are different, the data format of the operating data can be converted to generate judgment data in a data format type that can be displayed on the display unit.

FIG. 1 is a conceptual diagram illustrating an aircraft health management device according to an embodiment of the present invention and a display unit connected to the aircraft health management device. FIG. 2 is a block diagram illustrating a process in which operational data is transmitted to each component of the aircraft health management device according to an embodiment of the present invention and a process in which a data format type is converted.

Referring to FIG. 1, an aircraft health management device (100) may include an operation data unit (110) capable of storing operation data collected from an operating aircraft, a prediction unit (120) capable of converting a data format type of the operation data, and determining whether each component is a risk factor using the operation data.

In addition, the aircraft health management device (100) may include a control unit (130) that controls the operation of at least one of the operation data unit (110) and the prediction unit (120), and an operating unit (140) connected to the control unit (130) so that a user can input a command to the control unit (130).

In addition, the aircraft health management device (100) may include a connection unit (150) connected to the operation data unit (110), the control unit (130), the prediction unit (120), and the display unit (10), and a risk factor storage unit (160) capable of storing components determined as risk factors by the prediction unit (120) by classifying them according to risk level.

The aircraft health management device (100) as described above can be installed in an aircraft.

The connection unit (150) may be connected to an operation data unit (110), a control unit (130), a prediction unit (120), and a display unit (10). Accordingly, the operation data stored in the operation data unit (110) may be transmitted to the prediction unit (120) through the connection unit (150), and the judgment result (judgment data) of the prediction unit (120) may be transmitted to the display unit (10) through the connection unit (150).

The connection part (150) may include a signal line, a network line, and a power supply. In addition, a terminal and a main board connected to the terminal may be connected to an operating data part, a control line, a data transmission line, etc., among the terminals and the main board, and a fishing part, a prediction part, an operation part, and a display part may be connected.

The operating unit (140) can be connected to the control unit (130) and the display unit (10) through the connection unit (150). Accordingly, a command signal input by the user through the operating unit (140) can be transmitted to the control unit (130) through the connection unit (150), and the command signal input to the control unit (130) can be displayed on the display unit (10) so that the user can monitor it. Here, the user can be a pilot boarding the aircraft or a person managing the health of the aircraft.

The control unit (130) can control the operation of the operation data unit (110) so that the operation data for each component stored in the operation data unit (110) can be transmitted to the prediction unit (120). In addition, the control unit (130) can control the operation of the prediction unit (120) so that the data format type of the operation data can be converted, or the result (judgment data) determined by the prediction unit (120) can be transmitted to the display unit (10). In addition, the control unit (130) can control the operation of the risk factor storage unit (160) so that the judgment data stored in the risk factor storage unit (160) can be transmitted to the display unit (10). In addition, the control unit (130) can control the operation of at least one of the operation data unit (110), the prediction unit (120), and the risk factor storage unit (160) according to a command input from the operation unit (140), as described above.

An aircraft is driven to take off. Accordingly, the aircraft may be in a driven state before taking off. That is, some of the plurality of components included in the aircraft are in a driven state for takeoff before takeoff. In addition, the aircraft is driven for a predetermined period of time after landing the aircraft. For example, at least some of the components of the aircraft are in a driven state for a predetermined period of time, such as when the aircraft moves along the runway after landing on the runway. Accordingly, the operational data unit (110) may receive, collect, and store operational data from the aircraft before taking off and after landing the aircraft. In addition, the aircraft is in flight after taking off and before landing.

As described above, the operational data section (110) collects and stores operational data generated from an operating aircraft. When the operational data is stored in the operational data section (110), the operational data may be stored for each component. The operational data for each component may include at least one of the operating status of the component, signal output, received signal, measured value, etc., and the operational data may be different for each component. In addition, the operational data acquired for each component may be in at least one of a numerical form, an image form, and a message form. In addition, at least some of the operational data acquired for each component may have a different type of data format from other operational data. In other words, the type of data format may be different for each operational data.

The component-specific operational data stored in the operational data section (110) may include normal operational data (hereinafter, “normal operational data”) generated when the component operates normally, and abnormal operational data generated when the component operates abnormally.

The prediction unit (120) can convert the data format type of the operation data transmitted from the operation data unit (110) into a data format type that can be displayed on the display unit (10). In addition, the prediction unit (120) can use the operation data for each component to determine whether the corresponding component is a risk factor. In other words, the prediction unit (120) can predict a risk factor among the components of the aircraft.

Hereinafter, the type of data format that can be displayed on the display unit (10) or the type of data format that can be processed on the display unit is defined as a ‘reference type’ or a ‘data format of the reference type.’

Referring to FIG. 1, the prediction unit (120) may include an interface unit (121) capable of receiving operation data stored in the operation data unit (110), an identification unit (122) capable of identifying a data format type of the operation data transmitted from the interface unit (121), a conversion necessity determination unit (123) capable of determining whether the data format type of the operation data needs to be changed by comparing the data format type of the operation data with a reference data format type, and a conversion unit (124) capable of converting the data format type of the operation data to a reference data format type.

In addition, the prediction unit (120) may include a data processing unit (125) that can organize or display operational data as operational data over time for each component, and a risk factor determination unit (126) that determines whether a component that generated the operational data is a risk factor using the operational data over time.

The interface unit (121) is a means for transmitting and receiving data. The interface unit (121) may include a plurality of protocol modules so as to be able to transmit and receive different types of data formats. That is, the interface unit (121) includes a plurality of protocol modules so as to be able to receive all of the operating data stored in the operating data unit (110), and the plurality of protocol modules may be of different types. For example, the interface unit (121) may include an Ethernet protocol module capable of transmitting and receiving an Ethernet type data format (hereinafter, a first type data format), an ARINC 818 protocol module capable of transmitting and receiving an ARINC 818 type data format (hereinafter, a second type data format), and an ARINC 429 protocol module capable of transmitting and receiving an ARINC 429 type data format (hereinafter, a third type data format). Of course, the protocol module equipped in the interface section (121) is not limited to the above-described example, and may be replaced or added with a suitable protocol module depending on the data format type of the operating data for each component.

Hereinafter, for convenience of explanation, an example will be given of a case where the data format of the component-specific operation data stored in the operation data section (110) is one of the first type data format (Ethernet type data format), the second type data format (ARINC 818 type data format), and the third type data format (ARINC 429 type data format). In addition, for convenience of explanation, the first type data format, the second type data format, and the third type data format are abbreviated as the first type, the second type, and the third type, respectively.

The interface unit (121) can connect the connection unit (150) and the identification unit (122). Accordingly, the operation data received by the interface unit (121) through the connection unit (150) can be transmitted to the identification unit (122). At this time, the interface unit (121) includes a plurality of protocol modules so that operation data having different data format types can be received as described above. Accordingly, the operation data stored in the operation data unit (110) can be transmitted to the identification unit (122) through the interface unit (121) regardless of the data format type.

The identification unit (122) receives the operation data from the interface unit (121) and can identify, distinguish, or classify the data format type of the operation data received. In other words, it can identify or determine which of the first to third types of data format type of the operation data transmitted from the interface unit (121) to the identification unit (122) is used. At this time, the identification unit (122) can identify the type of the data format of the operation data by using at least one of the word format, the number of bits, and the data type by word area of the operation data, for example. In addition, the identification unit (122) can identify the data format type of the operation data by using artificial intelligence (AI).

The conversion necessity determination unit (123) determines whether the data format type of the operating data identified by the identification unit (122) is the same as the reference data format type. That is, the conversion necessity determination unit (123) compares the data format type of the operating data with the reference data format type to determine whether the data format type of the operating data is the same as the reference data format type. If the data format type of the operating data is different from the reference data format type, the conversion necessity determination unit (123) determines that the data format type of the operating data needs to be changed to the reference data format type. Conversely, if the data format type of the operating data is the same as the reference data format type, the conversion necessity determination unit (123) determines that there is no need to change the data format type of the operating data to the reference data format type. At this time, the conversion necessity determination unit (123) can determine whether the data format type of the operating data is the same as the reference data format type by using artificial intelligence (AI) and determine whether conversion is necessary.

The conversion unit (124) converts the data format type of the operating data to be the same as the reference data format type according to the judgment result of the conversion necessity judgment unit (123). That is, if the conversion necessity judgment unit (123) determines that the data format type of the operating data is different from the reference data format type, the conversion unit (124) converts the data format type of the operating data to the reference data format type. At this time, the conversion unit (124) converts the data format type of the operating data using a generally well-known conversion method.

An Interface Control Document (ICD) specifies the structure or specifications of various or different data format types. In the conversion unit (124) according to the embodiment, when converting the data format type, a general conversion method of converting based on the Interface Control Document (ICD) is used. That is, the conversion unit (124) can convert the data format type of the operation data into the reference data format type based on the regulations for each data format type included in the Interface Control Document (ICD). To this end, the conversion unit (124) can include an interface control document section in which the Interface Control Document (ICD) is stored. That is, the interface control document section can be a configuration of the conversion unit (124).

And the interface control document (ICD) stored in the interface control document section may include a structure or specification for multiple data format types that may occur in the aircraft. In addition, the interface control document (ICD) stored in the interface control document section may include a structure or specification for a reference data format type.

The conversion unit (124) converts the data format type of the operating data into the reference data format type. For example, if the data format type of the operating data is the second type (ARINC 818) and the reference data format type is the third type (ARINC 429), the operating data whose data format type is the second type (ARINC 818) is converted into the reference data format type (the third type (ARINC 429)). At this time, the interface control document (ICD) stores the reference data format type, for example, the third type (ARINC 429), and stores the data format type of the operating data, for example, the second type (ARINC 818). Accordingly, the conversion algorithm of the conversion unit (124) can convert the data format type of the operating data into the reference data format type by using the structure (or standard) of the third type (ARINC 429) and the structure (or standard) of the second type (ARINC 818) included in the interface control document (ICD). At this time, the conversion unit (124) can convert the data format type using a general method or a well-known method using an interface control document (ICD).

To explain more specifically, an example is given below. The data format type of the operational data may include the first to fifth message fields, and may be a state in which E field data is entered in the first message field, D field data is entered in the second message field, C field data is entered in the third message field, B field data is entered in the fourth message field, and A field data is entered in the fifth message field. In addition, the reference data format type may include the first to fifth message fields, and may be a structure in which A field data is entered in the first message field, B field data is entered in the second message field, C field data is entered in the third message field, D field data is entered in the fourth message field, and E field data is entered in the fifth message field. In converting the data format type of the operating data into the reference data format type in the conversion unit (124), the data format type can be converted by inputting the data in the A field of the operating data into the first message field, the data in the B field into the second message field, the data in the C field into the third message field, the data in the D field into the fourth message field, and the data in the E field into the fifth message field. Of course, in addition to changing the message field by field as described above, the data format type of the operating data is converted to conform to the reference data format type. The conversion unit (124) can convert the data format type of the operating data into the reference data format type by using the structure (or standard) for each data format type included in the Interface Control Document (ICD).

This will be described more specifically with reference to FIG. 2. For example, the first operation data may have a data format type of type 1 (type 1 data format), the second operation data may have a data format type of type 2 (type 2 data format), and the third operation data may have a data format type of type 3 (type 3 data format). In addition, the reference data format type may be type 3 (type 3 data format).

When the first to third operating data are transmitted to the conversion necessity determination unit (123), the conversion necessity determination unit (123) compares the data format types of the first to third operating data with the reference data format type. Then, the conversion necessity determination unit (123) determines whether the data format types of the first to third operating data and the reference data format type are the same. At this time, the conversion necessity determination unit (123) can determine that the data format types of the first and second operating data and the reference data format type are different, and that the data format of the third operating data and the reference data format type are the same. Therefore, the conversion necessity determination unit (123) can determine that the data format type of the first and second operating data needs to be changed, and that the data format type of the third operating data does not need to be changed.

Accordingly, the first and second operation data are transmitted to the conversion unit (124), and the third operation data is not transmitted to the conversion unit (124). Then, the conversion unit (124) converts the data format type of the input first and second operation data into the reference data format. At this time, the data format type of the third operation data is not converted because it is the same as the reference data format.

The data processing unit (125) organizes or displays the operational data as data over time. More specifically, the operational data is acquired in real time during the operation of the aircraft, and the acquired operational data is transmitted to and stored in the operational data unit (110). That is, multiple operational data are collected and stored for each component, and the multiple operational data may have different collection or storage times. For example, multiple first operational data are acquired by driving or operating the first component, and the multiple first operational data may have different collection or storage times. In addition, multiple second operational data are acquired by driving or operating the second component, and the multiple second operational data may have different collection or storage times. The data processing unit (125) can classify the operational data according to the time at which it was acquired. In addition, the data processing unit (125) can display the change trend of the operational data over time in a table or graph. For example, the data processing unit (125) can organize multiple first operational data for the first component over time and display them in a table or graph. In addition, the data processing unit (125) can organize multiple third operation data for the second component over time and display them in a table or graph.

The operational data transmitted to the data processing unit (125) may be operational data whose data format type has not been converted, or operational data whose data format type has been converted by the conversion unit (124). For example, if the conversion necessity determination unit (123) determines that the data format type of the operational data and the reference data format type are the same, the format type of the operational data is not changed as described above. In other words, the operational data is not transmitted to the conversion unit (124). Accordingly, the operational data is transmitted to the data processing unit (125) without going through the conversion unit (124). In other words, the operational data received by any one of the interface unit (121), the identification unit (122), and the conversion necessity determination unit (123) is transmitted as is to the data processing unit (125). In other words, the data format type of the operational data received by any one of the interface unit (121), the identification unit (122), and the conversion necessity determination unit (123) is not converted, and the operational data is transmitted to the data processing unit (125). As another example, if the conversion necessity judgment unit (123) determines that the data format type of the operating data is different from the standard data format type, the operating data is transmitted to the conversion unit (124) to convert the data format type of the operating data. Accordingly, the operating data whose data format type has been converted through the conversion unit (124) is transmitted to the data processing unit (125). Accordingly, the data format type of the operating data input to the data processing unit (125) may be the same as the standard data format type.

To explain more specifically with an example of Fig. 2, the first and second operation data are transmitted to the conversion unit (124), and the conversion unit (124) converts the data format type of the first and second operation data into a reference data format type. That is, the conversion unit (124) converts the data format type of the first and second operation data into the same as the reference data format type. Then, the first and second operation data whose data format type has been converted by the conversion unit (124) are transmitted to the data processing unit (125). On the other hand, the data format type of the third operation data is not transmitted to the conversion unit (124) because it is the same as the reference data format type. Accordingly, the third operation data received by any one of the interface unit (121), the identification unit (122), and the conversion necessity determination unit (123) is transmitted as is to the data processing unit (125).

In the above, an example is described of comparing the data format type of the operating data with the standard data format type to determine whether conversion is necessary, and then transmitting the converted or unconverted operating data to the data processing unit (125).

However, it is not limited to this, and after the data format type of the operating data is identified in the identification unit (122), it can be transmitted to the data processing unit (125) to organize the operating data in chronological order, and then the operating data according to time can be transmitted to the conversion necessity determination unit (123). As another example, the operating data can be transmitted to the data processing unit (125) to organize the operating data in chronological order, and then transmitted to the identification unit (122) and the conversion necessity determination unit (123).

The operational data is acquired in real time for each component. Accordingly, there may be multiple sets of operational data for each component, and the multiple sets of operational data may be divided according to the time at which they were collected or stored. The multiple sets of operational data acquired for each component may include at least one of normal operational data and abnormal operational data. For example, the multiple sets of first operational data acquired by the operation or operation of the first component may include at least one of normal operational data and abnormal operational data. In addition, the multiple sets of second operational data acquired by the operation or operation of the second component may include at least one of normal operational data and abnormal operational data.

The risk factor determination unit (126) analyzes a plurality of operation data to determine whether the plurality of operation data includes abnormal operation data. In other words, the risk factor determination unit (126) searches for abnormal operation data included in the plurality of operation data. For example, the risk factor determination unit (126) determines whether the plurality of first operation data includes abnormal operation data and determines whether the plurality of second operation data includes abnormal operation data.

The risk factor determination unit (126) can search for or distinguish abnormal operation data using preset reference data. To this end, the risk factor determination unit (126) can store 'reference data' for each component. The 'reference data' for each component can be the same or different. And the reference data can be data having a predetermined range. And, the risk factor determination unit (126) determines operation data included in the preset reference operation data range among the data included in the plurality of operation data as normal operation data. Conversely, the risk factor determination unit (126) determines operation data included in the plurality of operation data that falls outside the reference operation data range as abnormal operation data.

If abnormal operation data is included in multiple operation data, the risk factor determination unit (126) determines the component that generated the operation data as a risk factor. That is, the risk factor determination unit (126) determines the component that generated the abnormal operation data as a risk factor (first risk factor).

In the above, when multiple operation data include abnormal operation data, it has been described that the component that generated the abnormal operation data is judged as a risk factor. However, the present invention is not limited thereto, and depending on the time at which the abnormal operation data was generated, the component that generated the abnormal operation data may or may not be judged as a risk factor. That is, when multiple operation data include abnormal operation data and the time at which the abnormal operation data was generated is within a preset reference time range, the component that generated the abnormal operation data may or may not be judged as a risk factor. As another example, when multiple operation data include abnormal operation data and the time at which the abnormal operation data was generated is outside a preset reference time range, the component that generated the abnormal operation data may be judged as a risk factor. That is, the risk factor judgment unit (126) may determine a risk factor using the abnormal operation data or may determine a risk factor using the time at which the abnormal operation data was generated.

The risk factor determination unit (126) can determine the risk level for a component determined as a risk factor. The risk level can include a caution level and a warning level with a higher risk level than the caution level, and the risk factor determination unit (126) can determine the risk level of a component determined as a risk factor as either a caution level or a warning level. At this time, if the operating data exceeds the standard operating data range and the difference is below the preset standard difference, it can be determined as a caution level, and if it exceeds the standard difference, it can be determined as a warning level.

Meanwhile, the reason why abnormal operation data is generated from a component may be due to a problem with the component itself or another component that operates in conjunction with the component. In addition, the reason why abnormal operation data is generated from a component may be due to the component itself and another component that operates in conjunction with the component.

For example, the first component can operate in conjunction with the second component in all of the pre-takeoff state, the in-flight state, and the post-landing state. As another example, the third component can operate in conjunction with the fourth component in the pre-takeoff state and the post-landing state, and in conjunction with the fifth component in the in-flight state. As another example, the sixth component can operate in conjunction with the seventh component in the pre-takeoff state, in conjunction with the eighth component in the in-flight state, and in conjunction with the ninth component in the post-landing state. As another example, the tenth component can operate independently without being associated with any component in all of the pre-takeoff state, the in-flight state, and the post-landing state.

Therefore, the risk factor determination unit (126) additionally derives a risk factor (second risk factor) depending on whether there is a component that operates in conjunction with the first risk factor. That is, if the one component is determined to be the first risk factor using the operation data for the one component, the risk factor determination unit (126) determines whether there is a component that operates in conjunction with the one component. At this time, if there is another component that operates in conjunction with the one component, the risk factor determination unit (126) additionally determines the other component as a risk factor (second risk factor).

And, the risk level of the second risk factor may vary depending on the risk level of the first risk factor. If the risk level of the first risk factor is a caution level, the risk factor determination unit (126) may determine the risk level of the second risk factor as a caution level. As another example, if the risk level of the first risk factor is a warning level, the risk factor determination unit (126) may determine the risk level of the second risk factor as a warning level.

Data (judgment data) for the judgment result judged by the risk factor judgment unit (126) may be a standard data format type. That is, since the data format type of the operational data transmitted to the risk factor judgment unit (126) is a standard data format type, the judgment data judged by the risk factor judgment unit (126) may be generated in a standard data format type.

The judgment data, which is the output of the risk factor judgment unit (126), can be transmitted to the display unit (10). At this time, the display unit (10) can display the judgment data or cannot display it, depending on the data format type of the judgment data unit. That is, if the data format type of the judgment data is the same as the standard data format type, the judgment data can be displayed. However, if the data format type of the judgment data is different from the standard data format type, the judgment data cannot be displayed.

The data format type of the judgment data output from the risk factor judgment unit (126) according to the embodiment may be the same as the reference data format. Accordingly, when the judgment data output from the risk factor judgment unit (126) is transmitted to the display unit (10), the display unit (10) can display the judgment data. For example, the display unit (10) can display the judgment data including data that can identify a component determined to be a risk factor.

The risk factor storage unit (160) can store judgment data for components judged as risk factors by the risk factor judgment unit (126). At this time, the risk factor storage unit (160) can separately store judgment data according to the risk level. For example, the risk factor storage unit (160) can include a first storage unit that stores judgment data for risk factors judged as a caution level and a second storage unit that stores judgment data for risk factors judged as a warning level. Then, when judgment data is transmitted from the risk factor judgment unit (126), the risk factor storage unit (160) can classify and store the judgment data in the first storage unit or the second storage unit according to the risk level included in the judgment data. That is, judgment data for risk factors judged as a caution level can be automatically stored in the first storage unit, and judgment data for risk factors judged as a warning level can be automatically stored in the second storage unit. This risk factor storage unit (160) can be a virtualization platform, and a more specific example can be Docker.

When displaying judgment data on the display unit (10), judgment data stored in the risk factor storage unit (160) can be loaded and displayed. For example, when a user inputs a command to transmit judgment data stored in the first storage unit of the risk factor storage unit (160) to the control unit (130) using the operation unit (140) to the display unit (10), the control unit (130) can control the operation of the risk factor storage unit (160) so that the judgment data stored in the first storage unit is transmitted to the display unit (10). Accordingly, components can be identified according to risk levels.

FIG. 3 is a flowchart illustrating an aircraft health management method according to an embodiment of the present invention.

Hereinafter, an aircraft health management method according to an embodiment of the present invention will be described with reference to FIGS. 1 to 3. At this time, any content that overlaps with the previously described content will be omitted or briefly described.

At this time, an example is given where the type of the standard data format is the third type, i.e., the ARINC 429 type. In addition, an example is given where the data format type of the operational data for the first component is the first type, the data format type of the operational data for the second component is the second type, and the data format type of the operational data for the third component is the third type.

When the operation of taking off and flying the aircraft begins, the operational data is collected for each component. Then, the operational data collected for each component can be transmitted to the operational data unit (110) and stored (S10). The operational data can be stored in the operational data unit (110) by dividing it by component. In addition, the operational data can be collected according to the operating time of the component, and the operational data can be stored by time. The collection and storage of the operational data as described above can be performed while the aircraft is in operation.

During operation of the aircraft or after the end of aircraft operation, it is determined whether there is a risk factor among the components. To this end, the operation data stored in the operation data unit (110) is transmitted to the interface unit (121) of the prediction unit (120). More specifically, the user can input an 'operation data transmission command' to the operation data unit (110) using the operating unit (140). Accordingly, the control unit (130) controls the operation of the operation data unit (110) according to the input command, and transmits the operation data stored in the operation data unit (110) to the interface unit (121).

The interface unit (121) can receive the operating data transmitted from the operating data unit (110). At this time, the interface unit (121) includes a plurality of protocol modules, and the plurality of protocol modules can be of different types. Accordingly, even if the data format type of the operating data for each component included in the operating data unit (110) is different, each operating data can be received.

The operational data transmitted to the interface unit (121) is transmitted to the identification unit (122). The identification unit (122) identifies the data format type of the received operational data (S20). For example, it identifies or distinguishes whether the data format type of the received operational data is one of the first to third types.

Next, the conversion necessity judgment unit (123) determines whether the data format type of the operating data and the standard data format type are the same (S30). Then, the conversion necessity judgment unit (123) determines whether the data format type of the operating data needs to be converted based on the result of the determination of whether they are the same.

For example, if the data format type of the operating data and the standard data format type are the same (S30 --> Yes), the conversion necessity determination unit (123) determines that conversion is not necessary for the data format type of the operating data. Accordingly, the operating data is transmitted to the data processing unit (125). That is, the operating data is transmitted directly to the data processing unit (125) without going through the conversion unit (124). At this time, the data format type of the operating data transmitted to the data processing unit (125) is the same as the standard data type.

As another example, if the data format type of the operating data is different from the standard data format type (S30 --> No), the conversion necessity determination unit (123) determines that the data format type of the operating data requires conversion. Accordingly, the operating data is transmitted to the conversion unit (124). Then, the conversion unit (124) converts the data format type of the operating data to the standard data format type (S31). For example, if the data format type of the operating data is the first type and the standard data format type is the third type, the conversion unit (124) converts the data format type of the operating data to the third type. Then, the operating data whose data format type has been converted by the conversion unit (124) is transmitted to the data processing unit (125).

The data processing unit (125) organizes or displays the operational data as data over time (S41). For example, the data processing unit (125) can classify the operational data according to the time it was acquired, and display it as a table or graph so that the change trend of the operational data over time is shown.

The risk factor determination unit (126) determines whether the component that generated the operation data is a risk factor using the operation data over time. To this end, the risk factor determination unit (126) first determines whether the plurality of operation data includes abnormal operation data (S50). At this time, the risk factor determination unit (126) determines whether the plurality of operation data includes abnormal operation data for each component. For example, it determines whether the plurality of first operation data acquired by the operation or operation of the first component includes abnormal operation data, and determines whether the plurality of first operation data acquired by the operation or operation of the second component includes abnormal operation data. At this time, if the plurality of operation data does not include abnormal operation data (S50--> No), the risk factor determination unit (126) determines that the component that generated the operation data is not a risk factor (S62). Conversely, if the plurality of operation data includes abnormal operation data (S50--> Yes), the risk factor determination unit (126) determines that the component that generated the operation data including the abnormal operation data is a risk factor (S61). Additionally, the risk factor judgment unit (126) can determine the risk level for the risk factor.

The judgment data in the risk factor judgment unit (126) can be generated in a standard data format type. Then, the risk factor judgment unit (126) can transmit the judgment result to the display unit (10). Accordingly, the display unit (10) can display the judgment data.

The judgment data may include at least one of the results of judging whether each component is a risk factor and data that can identify the component judged as a risk factor. In addition, the judgment data may include a risk level. Accordingly, the user or pilot can use the judgment data displayed on the display unit (10) to judge or recognize which component is judged as a risk factor. In addition, the risk level of the component judged as a risk factor can be judged or recognized. Then, maintenance or replacement can be performed on the component judged as a risk factor (S70). At this time, maintenance or replacement can be performed depending on the risk level of the risk factor. For example, if the risk level of the component judged as a risk factor is a caution level, maintenance can be performed on the component. As another example, if the risk level of the component judged as a risk factor is a warning level, replacement can be performed on the component.

In the above, it has been described that the judgment data from the risk factor judgment unit (126) is directly transmitted to the display unit (10). However, this is not limited to this, and the judgment data from the risk factor judgment unit (126) may be transmitted to and stored in the risk factor storage unit (160). In addition, the judgment data stored in the risk factor storage unit (160) may be transmitted to the display unit (10).

According to embodiments of the present invention, when the data format type of the operating data is different from the reference data format type, which is a data format type that can be displayed on the display unit (10), the data format type of the operating data can be converted to the reference data format type. Accordingly, in generating judgment data for determining whether or not each component is a risk factor, the judgment data can be generated in the reference data format type that can be displayed on the display unit (10). In other words, risk factor judgment data that can be displayed on the display unit (10) can be generated regardless of the data format of the operating data.

Accordingly, the judgment data that determines whether each component is a risk factor can be displayed on the display unit (20). Accordingly, the user can easily check whether each component is a risk factor and the components determined to be risk factors by checking the judgment data displayed on the display unit (10). Accordingly, maintenance or replacement can be performed on components determined to be risk factors, thereby stably managing the health of the aircraft.

122: Identification section 123: Conversion requirement judgment section
124: Conversion section

Claims (19)

The process of storing operational data collected for each component of an aircraft in operation;
The process of identifying the data format type of operational data;
A process for determining whether the data format type of the identified operating data is the same as a preset reference data format type;
When the data format type of the above operating data is different from the above reference data format type, a process of converting the data format type of the above operating data to the reference data format type; and
Including a risk factor determination process for determining whether each component is a risk factor by using at least one of the operating data determined to have the same data format type as the reference data format in the above determination process and the operating data converted to the reference data format type by the above conversion process;
In storing the operational data collected for each component above, multiple operational data are stored for each component according to the collected time.
The above risk factor assessment process is:
A process of determining whether abnormal operating data is included among multiple operating data over time, by component;
If abnormal operation data is included among the above multiple operation data, a process of determining the first risk factor using the abnormal operation data; and
An aircraft health management method, comprising: a process of determining another component that operates in conjunction with the first risk factor as a second risk factor. In claim 1,
The above-mentioned standard data format type is a method for managing aircraft health, wherein the data format type is set to a data format type that can be displayed on a display section equipped in the cockpit of an aircraft and visually confirmed by a pilot. In claim 1,
The data format type of the judgment data including the judgment result determined in the above risk factor judgment process is the aircraft health management method which is the above standard data format type. In claim 1,
The process of determining the first risk factor using the above abnormal operation data is as follows:
An aircraft health management method, comprising: a process for determining a component that has generated the abnormal operating data as a first risk factor when the above-mentioned plurality of operating data includes abnormal operating data; In claim 1,
The process of determining the first risk factor using the above abnormal operation data is as follows:
An aircraft health management method, comprising: a process for determining a component that has generated the abnormal operation data as a first risk factor if the time at which the abnormal operation data is generated exceeds a preset reference time when the above-described plurality of operation data includes abnormal operation data; In claim 4 or claim 5,
The process of determining whether abnormal operation data is included among the above multiple operation data is as follows:
An aircraft health management method including a process of determining operational data that falls outside a preset standard operational data range among multiple operational data as abnormal operational data. In claim 6,
It is carried out after the above risk factor assessment process, and includes a process of assessing the risk level for components assessed as risk factors;
The process of determining the above risk level is:
The process of determining the risk level of a component determined as a first risk factor based on the difference between the abnormal operation data and the reference operation data as a caution level or a warning level with a higher risk level than the above caution level; and
An aircraft health management method, comprising: a process for determining a grade for another component determined as the second risk factor as the same as the grade for the component determined as the first risk factor; In claim 1,
An aircraft health management method comprising a process of storing judgment data including the judgment result of the above risk factor judgment process in a risk factor storage unit, which is a virtualization platform. In claim 7,
It includes a process of storing judgment data including the judgment result of the above risk factor judgment process in a risk factor storage unit, which is a virtualization platform.
The above risk factor storage unit is an aircraft health management method that stores judgment data by classifying it according to the risk level included in the judgment data. In claim 1,
An aircraft health management method wherein the data format type and reference data format type of the above operating data are any one of the Ethernet type, ARINC 818 type, and ARINC 429 type. In claim 1,
An aircraft health management method that performs at least one of maintenance and replacement for components determined to be at risk. An operational data section capable of storing operational data collected for each component of an aircraft in operation;
An identification unit capable of identifying the data format type of the operating data transmitted from the above operating data unit;
A conversion necessity judgment unit capable of determining whether the data format type of the operational data identified in the above identification unit needs to be converted to a standard data format type;
A conversion unit capable of converting the data format type of the operational data determined to require conversion in the conversion necessity judgment unit to a standard data format type; and
A risk factor determination unit capable of determining whether each component is a risk factor by using at least one of the operational data determined as unnecessary for conversion in the conversion necessity determination unit and the operational data converted in the conversion unit;
In the above operation data section, operation data for each component is stored, and multiple operation data are stored for each component.
The above risk factor assessment department is,
For each component, determine whether abnormal operation data is included among multiple operation data over time,
If abnormal operation data is included among the above multiple operation data, the first risk factor is determined using the abnormal operation data.
An aircraft health management device that determines another component that operates in conjunction with the first risk factor as a second risk factor. In claim 12,
The above conversion necessity judgment unit is,
If the data format type of the operation data identified in the above identification section is the same as the above reference data format type, it is determined that there is no need to change the data format type of the identified operation data.
An aircraft health management device that determines that the data format type of the identified operational data needs to be changed to the reference data format when the data format type of the identified operational data in the above identification section is different from the reference data format type. In claim 12,
The above conversion necessity judgment unit sets the above standard data format type,
An aircraft health management device that sets the data format type that can be displayed on a display section that is installed in the cockpit of an aircraft and can be visually confirmed by a user to the above-mentioned reference data format. In claim 12,
The above risk factor judgment unit generates judgment data including the results of judging whether each component is a risk factor,
The data format type of the judgment data generated by the above risk factor judgment unit is the aircraft health management device, which is the above standard data format. In claim 12,
A data processing unit that organizes the above plurality of operating data over time;
The above data processing unit is an aircraft health management device that organizes one of a plurality of operating data whose data format type has not been converted and a plurality of operating data whose data format type has been converted by the conversion unit over time. In claim 12,
In determining whether abnormal operation data is included among multiple operation data over time for each component, the above risk factor judgment unit:
The above risk factor judgment unit judges operation data that falls outside the preset standard operation data range among multiple operation data as abnormal operation data.
The above risk factor assessment unit assesses the risk level for the component assessed as the first risk factor, and assesses the level for another component assessed as the second risk factor to be the same as the level for the component assessed as the first risk factor.
The above risk factor judgment unit is an aircraft health management device that judges the risk level of a component judged as the first risk factor based on the difference between the abnormal operation data and the reference operation data as a caution level or a warning level with a higher risk level than the caution level. In claim 17,
Includes a risk factor storage unit capable of storing judgment data on components judged as risk factors in the above risk factor judgment unit,
The above risk factor storage unit is an aircraft health management device that is a virtualized platform. In claim 18,
The above risk factor storage unit is,
A first storage unit capable of storing judgment data for components whose risk level is judged to be a caution level; and
An aircraft health management device including a second storage unit capable of storing judgment data on components whose risk rating is determined to be a warning rating.

Images