Dashboards

Question and objective

What information does a team need to share on a regular basis? A dashboard consolidates verified individual analyses for monitoring, shift briefings, or in-depth analysis.

Implementation in Bytefabrik

Dashboards are based on the StreamPipes dashboard feature and are composed of existing charts. This allows the chart query to be reused. The dashboard is used to configure the layout and joint display; depending on the settings, a common time range and automatic refresh may also be included.

Best Practices for Setting Up

1. Define the target audience and the decision: Equipment monitoring requires different details than a quality analysis.
2. First, create and review the required charts one by one.
3. Put the most important information at the top and include only the necessary details.
4. Coordinate the time range and refresh rate of the charts.
5. Check readability and permissions using an account from the designated user group.

Example: A line dashboard displays output and relevant process values. An unusual trend triggers a detailed analysis; the dashboard itself does not need to display every single measurement at the same time.

What You Should Keep in Mind

Different time frames can create an apparent contradiction between key metrics. Check to see if all charts use the same time frame or if they intentionally use their own time logic.

A dashboard is not a static record of findings. To ensure that the situation can be understood later, document the time period, context, and supporting evidence in a data story.

Additional User Instructions: Apache StreamPipes Dashboards.