Context-Aware Performance Benchmarking of a Fleet of Industrial Assets

Industrial assets are instrumented with sensors, connected and continuously monitored. The collected data, generally in form of time-series, is used for corrective and preventive maintenance. More advanced exploitation of this data for very diverse purposes, e.g. identifying underperformance, operational optimization or predictive maintenance, is currently an active area of research. The general methods used to analyze the time-series lead to models that are either too simple to be used in complex operational contexts or too difficult to be generalized to the whole fleet due to their asset-specific nature. Therefore, we have conceived an alternative methodology allowing to better characterize the operational context of an asset and quantify the impact on its performance. The proposed methodology allows to benchmark and profile fleet assets in a context-aware fashion, is applicable in multiple domains (even without ground truth). The methodology is evaluated on real-world data coming from a fleet of wind turbines and compared to the standard approach used in the domain. We also illustrate how the asset performance (in terms of energy production) is influenced by the operational context (in terms of environmental conditions). Moreover, we investigate how the same operational context impacts the performance of the different assets in the fleet and how groups of similarly behaving assets can be determined

Improving Prolog Programs: Refactoring for Prolog

Refactoring is an established technique from the OO-community to restructure code: it aims at improving software readability, maintainability and extensibility. Although refactoring is not tied to the OO-paradigm in particular, its ideas have not been applied to Logic Programming until now. This paper applies the ideas of refactoring to Prolog programs. A catalogue is presented listing refactorings classified according to scope. Some of the refactorings have been adapted from the OO-paradigm, while others have been specifically designed for Prolog. Also the discrepancy between intended and operational semantics in Prolog is addressed by some of the refactorings. In addition, ViPReSS, a semi-automatic refactoring browser, is discussed and the experience with applying \vipress to a large Prolog legacy system is reported. Our main conclusion is that refactoring is not only a viable technique in Prolog but also a rather desirable one.Comment: To appear in ICLP 200

Isolating crosscutting concerns in system software

This paper reports upon our experience in automatically migrating the crosscutting concerns of a large-scale software system, written in C, to an aspect-oriented implementation. We zoom in on one particular crosscutting concern, and show how detailed information about it is extracted from the source code, and how this information enables us to characterise this code and define an appropriate aspect automatically. Additionally, we compare the already existing solution to the aspect-oriented solution, and discuss advantages as well as disadvantages of both in terms of selected quality attributes. Our results show that automated migration is feasible, and can lead to significant improvements in source code qualit