Best practice for creating a dashboard chart for heat distribution in waste incinerators

Hi all,

in short, I am looking for best practices on visualizing (and maybe animating) specific data inside a phoenix app as a 3d chart.

Some background:
I am currently working on a prototype for a status and logbook portal for our waste incineration plant. This will aggregate metrics and logs from our OT systems and store them in Grafana Mimir and Loki via different interfaces (PromEx, AMQP, OpenTelemetry…)

The task I am currently chewing on:
Visualize imbalances in heat distribution inside the incineration boilers. This hints to the perfect time for a maintenance shutdown and scheduling of an explosive pressure wave cleaning (the process creates a really hard crust of salts and other remains) of the boiler internals.

Data structure:
The boiler data is built of positional temperature values in a 6X10x4 matrix and a 6x3x2 matrix for the funnel, that gathers lose salts. These values can be converted to RGB values by thresholds.

I already looked at chart.js and vega-lite, but the nearest thing would be a vega-lite geoshape, which I think is hard to set up for my case, or several heatmaps, that had to be skewed in order to resemble at least a bit of the boiler structure:

heat_distribution

An additional task would be, to be able to switch through the last 90 days or so (which I think could be “easily” done with vega-lite controls.

Has anyone built something similar already and could hint me in the right direction, which approach and tooling would be the most efficient for the visualization? Or has anyone realized this with less effort in Grafana itself, so the charts could be embedded?

Best regards
Marcel

1 Like

I think the important thing is finding the right charting library for the use case. There is certainly no shortage of them. Apache echarts is pretty feature-full and has 3d.

1 Like

I’d question the need to create a pseudo-3D representation of the boiler setups. Is it a definite user requirement, at least for the first iteration?

Perhaps they’d be happy with a vega-lite nested vconcat/hconcat grid without the skewed visual?

For things that look less “graph-ish”, it can be useful to use the full Vega schema versus the simplified version that Vega-lite provides.

For the first iteration, a series of 2d will suffice, I think, and I will go with that.

As the target of the representation will be the senior management, aiming to gain insights for maximizing cycle times, we will have to make this more “digestible” for the MVP.

This is, what my technical contacts told me, they may be biased, though :smiley:

Thank you all for your input :smiley:

After some research, I think, I will go the easy route first for the prototype and just present 4 or 5 side-by-side, animated heatmaps.

For the MVP I will either look deeper into echarts, which I didn´t know yet, because it looks really powerful and ssems to have just what we need (maybe we can map the data onto cylindral surfaces for every boiler) or try to realize something with vega to stay in a bit more known waters. Scanning the full documentation and finding the platformer game, gave me some inspiration for a potential solution.

1 Like

I know how you feel. I work for industrial customers and recently my scope was “I just want I to look cool” :sunglasses:.

I recently built an animation of machine production cycles with liveview and echarts. It is so close to working as I would like it to but will try d3 to get full control, when I have a spare moment.

1 Like