TP3.3: Visual Service-Management Control Panel

The subproject TP3.3 is the continuation of subproject TP3.2. Whereas TP3.2 deals with the challenges how to monitor the multi-level architecture of the open mobility platform, TP3.3 focuses more on the visualization of the distributed architecture and of the extracted monitoring data. The goal of the subproject TP3.3 is to design and to develop a visual control panel for the integrated monitoring. The visual control panel will provide variety of information about the static architecture of the mobility platform, the service dependencies, the transaction flow and the business processes that are running on top of the services. Furthermore, the visualization tool provide metrics about the hardware, application performance, business activities and user related KPIs.

“Business Continuity” is one of the critical success factors for the service operator. In order to be able to ensure this, it is required to monitor the availability of the provided services continuously. Because of the diversity of the provided services and the variety of potential control panel user groups, the subproject requires flexible, expendable, target group-specific and configurable data views. Furthermore, the data on technical availability has to be integrated with the transactional business data in order to be able to draw conclusions of the users’ behavior in terms of business performance. Currently, no consistent modelling approaches exists for the presentation and integration of such monitoring data.

Figure 1: Realtime Platform Architecture Visualization

Figure 2: Log data Visualization

Monitoring data is described in several formats that represents the instrumented architecture in different ways. Hardware metrics are described in key – value pairs whereas the timestamp will be mostly used as the key and the sensor data like CPU utilization, memory bandwith, idle time etc. are the values of these keys. Log data is stored in a semistructured format, like json or xml. These kind of representation describes the behavior of the architecture and is suitable for analyse errors that occure. The communication behavior between services and their dependencies depicts the architecture in a graph-based way with nodes as the services and edges as the dependencies between the services. The execution sequence of business activities that covers a business process describes the data flow also in a graph-based way. A lot of these mentioned monitoring data require a particular visual representation. Depending on the type of data, some visualizations might be more suitable to support human understanding of the results and, ultimately, decision making as a response to the observed system behavior.

The difficulty here is how to combine the several visualization types in an understandable and meaningful way, covering the static architecture of the platform and the dynamic behavior. Especially in the investigation of the root cause of failures or the impact of failures, there exists no suitable visual representation that supports the analysis process in this context. This leads to the implementation of plenty of different dashboards, view switches and time-consuming searches. Within the research of TP3.3 we want to solve this problem.


Kleehaus, M.; Uludağ, Ö.; Matthes, F.: Towards a Multi-Layer IT Infrastructure Monitoring Approach based on Enterprise Architecture Information, 2nd Workshop on Continuous Software Engineering: SE, Hannover, 2017
Landthaler, J.; Kleehaus, M.; Matthes, F.: Multi-level Event And Anomaly Correlation Based on Enterprise Architecture Information, 12th International Workshop on Enterprise & Organizational Modeling and Simulation: EOMAS, Ljubljana, Slovenia, 2016


Daniel Hoyos: Interactive Visualizations for supporting the Analysis of Distributed Services utilization in the context of Business Processes