IT/OT, production data and industrial digitalisation. No buzzword battle.
This is about what actually works in real production environments, where architecture becomes unnecessarily complex, and what really matters when scaling.
Practical guidance on IT/OT integration, Unified Namespace, production data architectures and scaling digital solutions in industry.
Understand the problem first. Then talk about MQTT.
What a UNS really is, which problem it solves and, above all, why an MQTT broker alone does not make a data architecture.
Read article →
Three things that are constantly mixed up.
They solve different tasks. OPC UA helps with structured access to industrial data. MQTT distributes information. The UNS defines how that information is organised and used consistently across systems.
Read article →
What actually replaces what?
A UNS does not suddenly replace MES, historians or ERP.
The more interesting question is which task should sit in which system in future – and how production information should be made available cleanly between them.
Read article →
Production Data in Brownfield Environments: Why Machine Connectivity Is Rarely the Real Problem.
Getting data out of a machine is usually the easy part. The real challenge is turning it into reliable, reusable information that still works across 50, 200 or 500 machines.
Read article →
Not every architecture needs more technology
Sometimes a new data layer is the right answer.
Sometimes a clean interface is enough.
And sometimes the real problem is neither MQTT nor OPC UA, but that nobody has clarified which information is actually needed and who is responsible for it.
These differences are exactly what this knowledge section is about.
