Abstract:
A method for creating predictive damage models includes receiving a first predictive damage model, identifying latent space between a first and a second domain asset, building a regression model from first domain asset projected source data, create target dependent variables of a second model, applying classification or regression techniques to determine a function expressing the dependent variables, determining data points from the function to develop a second regression model, applying the second regression model to data points to predict target dependent variables, evaluating the second predictive damage model using the predicted target dependent variables, performing a sensitivity study to determine a directionality parameter of the second predictive damage model, and if the results are within an acceptable predetermined range, providing maintenance or servicing recommendations generated by the second predictive model to a user platform display, else repeating the process by rebuilding the regression model to further refine the regression model.

Description:
BACKGROUND 
       [0001]    Predictive analytic models can be based on data extracted from a product&#39;s historical performance. A predictive model can predict trends and behavior patterns to create maintenance schedules that both improve the product&#39;s field reliability and minimize its downtime. To predict a future event, a predictive model can be based on past occurrences, component reliability, and/or engineering predictions. 
         [0002]    It can be desirable to make assessment and/or predictions regarding the operation of a real world physical system, such as an electro-mechanical system—e.g., an aircraft turbine engine. The predictive model can be used to predict a condition of the system, or a portion of the system, to help make maintenance decisions, budget predictions, etc. Even with improvements in sensor and computer technologies, however, accurately making such assessments and/or predictions can be a difficult task. 
         [0003]    A predictive model can include parameters and dimensions of the real-world physical system, which can be updated by historical maintenance records and/or data from sensors embedded in the system itself. A robust predictive model can consider multiple components of a system, each having its own micro-characteristics and not just average measures of a plurality of components associated with a production run or lot. Moreover, it may be possible to very accurately monitor and continually assess the health of individual components, predict their remaining lives, and consequently estimate the health and remaining useful lives of systems that employ them. 
         [0004]    Mechanical systems wear or change over time, which affects the performance of these mechanical systems. Conventional predictive models can estimate the wear of a mechanical system. These models can be updated with information regarding the longevity of various components of the mechanical system using data collected over a system&#39;s life as input to statistical models. Theoretical models of the mechanical system which use physics or engineering information to build a model using test data. Such modeling is based on understanding how a system operates and progresses to a failure via knowledge, for example, of material properties and response to loading. However, conventional predictive models are confined to known systems and their component longevity. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0005]      FIG. 1  depicts a process for creating predictive damage models in accordance with embodiments; 
           [0006]      FIGS. 2A-2B  depict predictive model performances in accordance with embodiments; and 
           [0007]      FIG. 3  depicts a high-level architecture of an exemplary system in accordance with embodiments. 
       
    
    
     DETAILED DESCRIPTION 
       [0008]    Embodying systems and methods provide for creating predictive damage models by transductive transfer learning across domains (i.e., new asset types (e.g., engines, vehicles, etc.), on new aviation carriers, on expanded asset sets within the same type, on alternate flight condition expectations, etc.). Predictive models of distress or damage for aviation assets (or their components or subcomponents) are applied across domains by statistical learning of a functional difference(s) between the model&#39;s current domain and the new domain(s). The knowledge of these functional differences can be used to transform data from the new domain to equivalent points in the original (model construction) domain, thereby allowing for direct application of the model as if all data originated together. Conventional aviation damage models cannot be directly applied to data from other domains without a significant loss in accuracy and/or prediction effectiveness. 
         [0009]    In accordance with embodiments, multiple methods can perform the statistical learning of functional differences between the data domains—including, but not limited to, dimensionality reduction (where a common lower-dimensional manifold can be estimated along with domain-to-manifold lossy transfer functions), and transfer adaptive boosting (where aggregate boosting of transfer function hypotheses can produce an ensemble estimate of a domain-to-domain function that aligns data distributions and minimizes error for known point correspondences). These methods allow for the direct application of existing models on transformed data without a significant loss of performance. 
         [0010]    Embodying systems and methods can be used to develop predictive models for new products prior to the availability of a sufficient dataset for “from scratch” model development. Accordingly, the new products can benefit from effective service/maintenance schedules from their launch into the marketplace. Thus achieving better servicing, reliability, and also revenue for the entire asset performance period starting at its entry-into-service point. Additionally, predictive model development costs can be reduced by relying on existing predictive models to be updated to be applied to the new domain. Customized, per-carrier predictive models can be deployed rapidly, allowing for customized service to improve services, experience, and value. 
         [0011]      FIG. 1  depicts process  100  for creating predictive damage models in accordance with embodiments. Process  100  begins with a first predictive damage model which is operative to predict behavior(s) of a first, real-world physical asset (i.e., a first domain) being provided, step  105 . Typically, the first predictive damage model is for an already existing domain. However, the invention is not so limited. Process  100  can be implemented from a first predictive damage model for a yet-to-be realized second domain asset so long as the predictive capabilities of the first predictive damage model are within acceptable limits. Process  100  creates a second predictive damage model operative to predict behavior(s) of a second, real-world physical asset (i.e., a second domain) through transductive transfer learning using knowledge of the first domain and of the second domain. 
         [0012]    At step  110 , latent space between the first domain asset and the second domain asset is identified. In accordance with some implementations, the latent space can be identified by solving a semidefinite programming (SDP) problem to optimize a user-specified function. The solution to the SDP problem can provide a latent universal kernel between the two domains. This latent space highlights the similarities between the two domains and is used as a bridge from the first predictive model to the second predictive model using knowledge transfer. 
         [0013]    A regression model is built, step  115 , with projected source data of the first domain. In accordance with some implementations, the regression model can apply a principal component analysis (PCA) to the latent space kernel. The PCA analysis results in vectors of an uncorrelated orthogonal basis set. The principal components are orthogonal because they are the eigenvectors of the symmetric covariance matrix. 
         [0014]    Using the top k eigenvectors of the PCA analysis as a basis, x′ tar  and x′ src  are created, step  120 . Standard classification or regression techniques can be used to learn, step  125 , the function ƒ:x′ src -&gt;y src . Knowing the function, ƒ(x′ tar ) can be used to determine, step  130 , y tar . The resulting regression model is applied, step  135 , directly to projected target data of the second domain. Applying the regression model to projected target data can predict target dependent variable(s). 
         [0015]    The predicted target dependent variables are used to evaluate, step  140 , the performance of the second predictive damage model. Because the dependent variables in the final regression model are not intuitive, a sensitivity study is performed, step  145 . The sensitivity study is performed to determine whether the model directionality is correct, and that it does not diverge. Results of studies have demonstrated that population shift post-transformation is minimal regardless of perturbation, which suggests a high tool robustness to input noise for the second predictive damage model created by transductive transfer learning in accordance with embodiments. 
         [0016]      FIG. 2A  graphically depicts the performance of a first predictive damage model for a first domain when it is applied directly as a predictive model for a second domain.  FIG. 2A  illustrates that the first predictive damage model results in predictions well distant from a perfect performance line  210  of an ideal predictive model.  FIG. 2B  graphically depicts the performance of a second predictive damage model created for a second domain from the first predictive model by transductive transfer learning in accordance with embodiments. As illustrated in  FIG. 2B , the performance of the second predictive damage model straddles the perfect performance ideal  210  with acceptable residual errors (e.g., root mean square error (RMSE) of about 2.1). 
         [0017]    With continued reference to  FIGS. 1A-1B , the results of the sensitivity study are evaluated, step  150 , to determine if the performance of the second predictive damage model (created by transductive transfer learning) are within a predetermined acceptable limit. If the sensitivity study results are outside the acceptable limit, process  100  returns to step  115  to build a further-refined regression model. The further-refined regression model can be progressively retuned by comparing residual root mean square errors against a few know labels in the new domain. If the sensitivity study results are within the acceptable limit, maintenance and/or servicing schedules for the new second domain asset are generated, step  155 . These maintenance and/or servicing schedules are delivered to a user platform for access by users. 
         [0018]      FIG. 3  is a high-level architecture of system  300  in accordance with some embodiments. System  300  includes a computer data store  310  that includes parameter information  312 , and performance information  314  related to first domain asset  350  (e.g., a turbine engine). The data store can also include parameter information  316 , and performance information  318  related to second domain asset  354 . Usage information  320 ,  322  in the data store can include, for example, engine sensor information, exhaust gas temperatures, fuel combustion rates, component reliability predictions, etc. The usage information related to the first domain asset can be both calculated, and real-world observances obtained from manual examination of first domain asset(s). 
         [0019]    First predictive model  326  can be resident in the data store, and include instructions that can cause control processor  330  to create a prediction and/or result that may be transmitted to various user platforms  360  as appropriate (e.g., for display to a user). Second predictive damage model  328  can be located in the data store after it is generated in accordance with process  100 . The components of system  300  can be located locally to each other, or remotely, or a combination thereof. Communication between the system components can be over electronic communication network  340 . 
         [0020]    The electronic communication network can be an internal bus, or one or more of a Local Area Network (“LAN”), a Metropolitan Area Network (“MAN”), a Wide Area Network (“WAN”), a proprietary network, a Public Switched Telephone Network (“PSTN”), a Wireless Application Protocol (“WAP”) network, a Bluetooth network, a wireless LAN network, and/or an Internet Protocol (“IP”) network such as the Internet, an intranet, or an extranet. Note that any devices described herein may communicate via one or more such communication networks. 
         [0021]    The prediction model(s), and system  300  itself, can store information into and/or retrieve information from various data sources, such as the computer data store  310  and/or user platforms  360 . The various data sources may be locally stored or reside remote from system  300 . A user may access system  300  via one of the user platforms  360  (e.g., a personal computer, tablet, smartphone, etc.). 
         [0022]    In accordance with some embodiments, a computer program application stored in non-volatile memory or computer-readable medium (e.g., register memory, processor cache, RAM, ROM, hard drive, flash memory, CD ROM, magnetic media, etc.) may include code or executable instructions that when executed may instruct and/or cause a controller or processor to perform methods discussed herein such as creating predictive damage models by transductive transfer learning across domains, as described above. 
         [0023]    The computer-readable medium may be a non-transitory computer-readable media including all forms and types of memory and all computer-readable media except for a transitory, propagating signal. In one implementation, the non-volatile memory or computer-readable medium may be external memory. 
         [0024]    Although specific hardware and methods have been described herein, note that any number of other configurations may be provided in accordance with embodiments of the invention. Thus, while there have been shown, described, and pointed out fundamental novel features of the invention, it will be understood that various omissions, substitutions, and changes in the form and details of the illustrated embodiments, and in their operation, may be made by those skilled in the art without departing from the spirit and scope of the invention. Substitutions of elements from one embodiment to another are also fully intended and contemplated. The invention is defined solely with regard to the claims appended hereto, and equivalents of the recitations therein.