Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Michal Orkisz

dblp:72/3985 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 2020
0000-0001-9534-3900ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 1Applied, interdisciplinary, general and emerging computing · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software architecture › reusable architecture
product line architecture
0.012002
Integrating hundred's of product through one architecture: the industrial IT architecture · ICSE 2002
Requirements engineering and software design
software architecture
0.012002
Integrating hundred's of product through one architecture: the industrial IT architecture · ICSE 2002
Requirements engineering and software design
software product lines
0.012002
Integrating hundred's of product through one architecture: the industrial IT architecture · ICSE 2002

Methods — techniques the papers use, named apart from their topics

case study · 0.0
YearPublicationVenuePosition
2020 Data-Driven Gearbox Failure Detection in Industrial Robots
abstract
Gearbox failures cost thousands of lost production hours in plants that use industrial robots. In this context, an automated monitoring system that can warn the user of an impending failure can save precious resources. This problem has been addressed in many other domains through the use of machine learning approaches. However, standard machine learning algorithms are limited in their ability to detect gearbox failures, mainly due to task variability arises from robot-specific data. To improve detection performance of machine learning approaches, in this paper we propose techniques to curate the data prior to building a classification model. In a systematic hypothesis-driven study exploring the effect of different preprocessing techniques, we evaluate training data augmentation with estimated measurements, data differencing to suppress task dependence, inclusion of local variation, and selection of principal components on data collected from 26 industrial robots from the field. Our results show that preprocessing techniques improve the failure detection performance.
Sathish Vallachira, Michal Orkisz, Mikael Norrlöf, Sachit Butail
IEEE Trans. Ind. Informatics2
2012 Visual modeling of condition monitoring systems
abstract
In this paper a graphical approach for Condition Monitoring Systems (CM) based on Model Driven Architecture is presented; in particular, the software application “Smart Monitoring Agent” or SMA. This graphical approach starts from the idea of modeling, applying and visualizing non-hierarchical relations. The presented method makes use of well-defined data models that take the solution to a superior level of configurability, using only graphical tools. Finally it is explained how this approach enables the flexible knowledge exchange between condition monitoring experts and software engineers.
Maciej Zygmunt, Marek Budyn, Michal Orkisz, James R. Ottewill, Victor H. Jaramillo, Agnieszka Nowak-Brzezinska
ETFA3
2002 Integrating hundred's of product through one architecture: the industrial IT architecture
abstract
During the last few years, software product line engineering has gained significant interest as a way for creating software products faster and cheaper. But what architecture is needed to integrate huge amounts of products, from different product lines? This paper describes such an architecture and its support processes and tools. Through cases, it is illustrated how the architecture is used to integrate new --- and old --- products in such diverse integration projects as vessel motion control, airport baggage handling systems, pulp&paper and oil&gas, in a very large organization. However, in a large organization it is a challenge to make everyone follow an architecture. Steps taken to ensure global architectural consistency are presented. It is concluded that a single architecture can be used to unify development in a huge organization, where the distributed development practices otherwise may prohibit integration of various products.
Lars Bratthall, Robert van der Geest, Holger Hofmann, Edgar Jellum, Zbigniew Korendo, Robert Martinez, Michal Orkisz, Christian Zeidler, Johan S. Andersson
ICSE7