Features and advantages of examples of the present disclosure will be apparent by reference to the following detailed description and drawings, in which like reference numerals correspond to similar, but in some instances, not identical, components. Reference numerals or features having a previously described function may or may not be described in connection with other drawings in which they appear.
Modern machinery are complex systems with many sensors integrated within the system that provide diagnostics information. The interactions among the various components within a particular system may be unique to that system. Modeling component behavior via sensors integrated in a system allows for detecting abnormalities in the system to prevent a catastrophic failure of a system or determining the source of a malfunctioning system. Generally, component models may describe a hierarchy of functional components in a system, component responsibilities, component static relationships, and the way components collaborate to deliver required functionality within a given system.
Modern systems rely on sensors integrated into the system to provide diagnostics information. Generalized methods are developed to model the states of individual components, such that abnormalities (e.g. faults) can be detected. Current methods are developed with the assumption that components exhibit the same behaviors across all systems, and do not account for the unique interactions among the components within a specific system. Due to this limitation, components are often removed before the end of their useful life based on expensive component failure trials or prior subject matter expert experience. Premature removal of a component or expert experience is not optimal, as faults do not occur on regular predictable timelines across all systems and thus the full value of components are not realized. Similarly, components may be used in a system after a component fault resulting in a failure of the overall system.
Moreover, with expensive components, a very limited sample size may be used to estimate failure rates, with results that are not generalized to a larger population. Not all fault types will be discovered or tested at the time of failure trials. Regular maintenance is often scheduled to inspect components to address issues related to poor estimates of failure rate or limited diagnostic capacities due to current sensor data processing methods. However, regular maintenance reduces the availability and readiness of these systems.
The method herein describes system-specific component behavior models and detects component faults or malfunctions during occurrence, thereby avoiding unnecessary maintenance inspections, premature replacements, inaccurate methods based on expert experience, or overall system failure. Furthermore, the method herein is applicable to any system component in different systems as the method accounts for the system the component is being used in by accounting for unique interactions among the components. The method herein calculates a baseline component state within the system before monitoring the system for faults, malfunctions, or failures. As a result, the method is applicable to any component in a specific system where sensors can be used to monitor the system.
A method for improving a system by detecting faulty components is described herein. The method includes calculating a baseline state of a component, calculating a current state of the component, and detecting a component fault based on the time series of new observed data. Computing the baseline state of a component includes converting a time series of observed data from the component into a sequence of graphs, computing an adjacency matrix and a normalized Laplacian matrix for each graph, computing summary values for each graph, and computing the baseline state of the component. Computing the current state of the component includes converting a time series of new observed data from the component into a sequence of graphs, computing an adjacency matrix and a normalized Laplacian matrix for each graph, and computing summary values for each graph.
Referring now to
Referring back to calculating the baseline state of the component 100, first, a time series of observed data from the component is converted into a sequence of graphs, (Gi), where i is an integer that represents the index for the sequence of graphs 102. For example, Gi represents each graph, G1, G2, G3, etc. in the sequence of all graphs created from the time series of observed data from the component. In an example, (Gi) represents one or more graphs as the sequence of graphs. A graph Gi from the sequence of graphs (Gi) can be represented by Gi=(Vi, Ei) where Vi are vertices for Gi and Et are edges for Gi. In an example, the time series of observed data can be obtained from a sensor. In some examples, the sensor may be any sensor in the aircraft system, the vehicle system, or the ship system. Additionally, in an example, a computer processor and a data storage device may be used to convert and store the sensor data into a sequence of graphs.
Referring back to for each graph Gi in the sequence of graphs, (Gi). The adjacency matrix describes the global structure of each graph when calculated for that graph. The Laplacian matrix describes the local structure of each graph when calculated. Similar to 102, a computer processor and a data storage device may be used to calculate and store the adjacency matrix and the normalized Laplacian matrix for each graph.
Referring back to , for each graph Gi in the sequence of graphs, (Gi), 106. The summary values are calculated using the following equations (I) and (II):
In equations (I) and (II), cA and are user-selected integer values, fA and
are user-defined functions, λAk are the sorted eigenvalues in descending order of the adjacency matrix GiA, and
are the sorted eigenvalues in ascending order of the normalized Laplacian matrix
. In an example, a computer processor and a data storage device may be used to calculate and store the summary values, θG
.
Referring back to from observed values (θG
) from Gi, where i is an integer that represents the index for the sequence of graphs (Gi). For example, Gi represents each graph, G1, G2, G3, etc. in the sequence of all graphs created from the time series of observed data from the component as previously stated herein. The Bayesian parameter estimation is determined using equation (III):
where (θ{tilde over (G)}A, ) represent the baseline parameters estimated from the sequence of graphs (Gi). In an example, a computer processor and a data storage device may be used to calculate and store the baseline state of the component. The baseline state of the component is then used to detect whether the component is faulty in the system.
Referring now to
A component fault is detected based on the time series of new observed data 208. To detect a component fault, a threshold, t, is set to t>0. A component fault is detected when d ((θ{tilde over (G)}A, ), (θG
)≥t, where d is a distance function, for any graph in the sequence of graphs (Gi) from the newly observed time series data. When d((θ{tilde over (G)}A,
), (θG
))≥t, the component is determined to have a fault. In other words, the difference between the baseline state and the newly observed state of the component being monitored is determined. When that difference exceeds the threshold as described above, a component fault is detected. In an example, a computer processor and a data storage device may be used to calculate and store the threshold and distance function of each graph in the sequence of graphs (Gi).
A system for detecting faulty components is also described herein. The system includes a sensor and computer processor with a storage device. The sensor records a time series of observed data and a time series of new observed data. The computer processor with the storage device obtains and stores the time series of observed data and the new time series of observed data from the sensor and calculates and stores a baseline state of a component as previously described herein for
As used herein, the term “about” is used to provide flexibility to a numerical range endpoint by providing that a given value may be “a little above” or “a little below” the endpoint. The degree of flexibility of this term can be dictated by the particular variable and would be within the knowledge of those skilled in the art to determine based on experience and the associated description herein.
As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of a list should be construed as a de facto equivalent of any other member of the same list merely based on their presentation in a common group without indications to the contrary.
Unless otherwise stated, any feature described herein can be combined with any aspect or any other feature described herein.
Reference throughout the specification to “one example”, “another example”, “an example”, means that a particular element (e.g., feature, structure, and/or characteristic) described in connection with the example is included in at least one example described herein, and may or may not be present in other examples. In addition, the described elements for any example may be combined in any suitable manner in the various examples unless the context clearly dictates otherwise.
The ranges provided herein include the stated range and any value or sub-range within the stated range. For example, a range from about 0.1 to about 20 should be interpreted to include not only the explicitly recited limits of from about 0.1 to about 20, but also to include individual values, such as 3, 7, 13.5, etc., and sub-ranges, such as from about 5 to about 15, etc.
In describing and claiming the examples disclosed herein, the singular forms “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
The invention described herein may be manufactured and used by or for the government of the United States of America for governmental purposes without the payment of any royalties thereon or therefor. Licensing and technical inquiries may be directed to the Office of Research and Technical Applications, Naval Information Warfare Center Pacific, Code 72120, San Diego, CA, 92152; (619) 553-5118; NIWC_Pacific_T2@us.navy.mil. Reference Navy Case Number 211152.