Connecting machine data: a measurement needs units and a time reference.
Read selected machine data into a dashboard or business system. Preserve its meaning, timestamps and quality.
Read the German originalUnderstand transport and meaning separately
OPC UA describes information models and the exchange of industrial data, among other things. MQTT can provide transport in suitable architectures. The OPC Foundation explains why these approaches can be used together. Your specific installation determines the available path.
Start with a few signals and a clear question, such as how a machine state changes over time. Check whether documented read access is available and who can confirm the meaning of each signal.
Old values must not look current
A temperature without a unit or a state without a timestamp can mislead an analysis. A value therefore needs information about its origin and quality. When a connection fails, the time of the last valid observation must remain visible.
Agree on buffering and recovery. Measurements delivered later belong to their original time. Mark a gap visibly instead of silently covering it with the last known value.
Begin with reading and expand deliberately
A pilot reads one data source and presents the agreed signals in one target system. It does not change machine parameters. Check the analysis with the people who understand the equipment and its states.
Only then add more signals or sources. Control functions need their own design and the relevant operational approvals. A useful long-term data path needs monitoring and maintenance of its signal model as well as the initial connection.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
OPC UA & MQTT: make machine data usable · Packages