Abstract

Prognostic Health Management (PHM) is a predictive maintenance strategy, which is based on Condition Monitoring (CM) data and aims to predict the future states of machinery. The existing literature reports the PHM at two levels: methodological and applicative. From the methodological point of view, there are many publications and standards of a PHM system design. From the applicative point of view, many papers address the improvement of techniques adopted for realizing PHM tasks without covering the whole process. In these cases, most applications rely on a large amount of historical data to train models for diagnostic and prognostic purposes. Industries, very often, are not able to obtain these data. Thus, the most adopted approaches, based on batch and off-line analysis, cannot be adopted. In this paper, we present a novel framework and architecture that support the initial application of PHM from the machinery producers’ perspective. The proposed framework is based on an edge-cloud infrastructure that allows performing streaming analysis at the edge to reduce the quantity of the data to store in permanent memory, to know the health status of the machinery at any point in time, and to discover novel and anomalous behaviors. The collection of the data from multiple machines into a cloud server allows training more accurate diagnostic and prognostic models using a higher amount of data, whose results will serve to predict the health status in real-time at the edge. The so-built PHM system would allow industries to monitor and supervise a machinery network placed in different locations and can thus bring several benefits to both machinery producers and users. After a brief literature review of signal processing, feature extraction, diagnostics, and prognostics, including incremental and semi-supervised approaches for anomaly and novelty detection applied to data streams, a case study is presented. It was conducted on data collected from a test rig and shows the potential of the proposed framework in terms of the ability to detect changes in the operating conditions and abrupt faults and storage memory saving. The outcomes of our work, as well as its major novel aspect, is the design of a framework for a PHM system based on specific requirements that directly originate from the industrial field, together with indications on which techniques can be adopted to achieve such goals.

Highlights

  • The data are detected under known conditions, the data transmission occurs at fixed moments, such transmitted in these cases are the extracted feature vectors and the associated label as at the endclass of a and shiftRUL)

  • We proposed a case study to validate main parts ofcase the setting, the algorithm corresponds to automatic observation labeling.two

  • A novel framework based on an edge-cloud infrastructure and novel functional and logical architectures for a semi-supervised and partially online Prognostic Health Management (PHM) applications to industrial equipment is introduced

Read more

Summary

Introduction

Data under fault conditions are trickier to obtain than data under healthy conditions, resulting in very unbalanced datasets; the dataset may not include data for different operating conditions, resulting in the impossibility to train accurate diagnostic and prognostic models Given these issues, the main objective for machine producers is to find a PHM architecture that (1) can start from scratch, with very little prior knowledge about machinery behavior;. The definition of an edge-cloud-based PHM framework This allows the real-time health assessment of industrial machines and the simultaneous collection of highfrequency data, low-frequency data, and event-data, from machinery installed in several clients’ plants. The second step is the framework definition, which is a layered structure of the system built according to the requirements It includes the functions, performance, operational conditions, and project constraints that will influence the architecture. The aim is to describe how the PHM system functions can be performed, with a particular focus on the needed input of each technique, their strengths, weaknesses, and use cases

Data Processing Function
Fault Diagnosis Assessment Function
Anomaly Detection
Novelty Detection
Prognostic Assessment Function
Stakeholders’ Expectations and Requirements Definition
The Functional Architecture
The Logical Architecture
Case Study
Features
10. Novelty
12. Novelty
Findings
Conclusions
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.