Goodmorning, can someone explain to me what the added value is of UMH in comparison to using MQTT directly?

you have for example ah istorian in there, you have all the management features in there, you have the protocol converters, etc. Check out htis pages: https://www.umh.app/product/unified-namespace https://www.umh.app/product/protocol-converter https://www.umh.app/product/data-flow-component https://www.umh.app/product/historian

from a OT guys perspective; No doubt it's an advantage, you get the full package (for free) without the hassle of managing everything

Alright thanks for the links, most of it is in jargon, probably perfect for your target audience but still unclear for a noob like me. I have to convince some people to implement this system because I see the added benefits for the long term, and the complexity of managing all the data that we can pull out of our production line. Best is to show them I think, would it be possible to split the data that now runs into InfluxDB, and send it to an UMH instance on my laptop on the network aswell?

sure that's possible! Do you have data going to an MQTT broker before it gets to influx?

@theunr To show the value you have to compare how you currently would connect, store and visualize data and how quickly you can do it with UMH. Most people are familiar with the duration and price ranges of classic integration projects. Give people some examples on the typical workflow with UMH and they will quickly see the benefits. Typical pitch looks like this: - describe the current situation and workflow for integrations and its challenges - show how to connect a tag to the UNS and visualize it (can be from the included simulators) - show the north star/vision of what is possible (e.g., webinar templates in action) - your idea on how to integrate UMH with the current enterprise architecture Doing this hands-on will allow people without technical background to make an informed decision. Reactions might differ based on the past experiences with integration projects.

My turn! MQTT by itself is barely enough. It gets you just current state and messages. That’s great if that’s all you need, but if you want to historize that data, build an API, build analytical visuals, have the tools needed to enable everyone in the business to contribute, UMH gives you ALL of the infrastructure as a FOSS solution. If you want to scale this and derive actual value in a short time (we need a new KPI for our machines, we need to link our orders with the quality system, we need to link inventory to have the machines request more materials), the management UI is how you will achieve these integrations at speed. You don’t have to be a terminal wizard to understand how to solve these problems. You just have to be an engineer who understands the problem.