Topic hub
OPC UA, MQTT, Sparkplug, SQL and REST: protocol, topic, schema and data contract decisions when connecting systems.
Protocols solve the connection; what makes data meaningful is naming, unit, time and quality rules. OPC UA and MQTT solve different problems and are often used together.
This hub brings together the articles on OPC UA architecture, MQTT in production, how the two compare and the Unified Namespace, plus the tools that generate topics and SQL schemas.
Implementation guides
Go beyond connecting to a broker. Make message meaning, duplication and freshness explicit and manageable.
Read the guideDecide on time, quality, uniqueness and retention before turning a tag list into database tables.
Read the guideArticles
OPC UA’s node-based address space, subscription model and security layers from an integration point of view: NodeId, sampling and certificate decisions.
Read the articlePractical design principles for industrial MQTT projects: topic hierarchy, QoS choice, use of retain and Last Will, session handling and the payload contract.
Read the articleOPC UA is an information model and a set of services; MQTT is a messaging transport. Where each is strong and how an integration layer joins them.
Read the articleThe Unified Namespace idea explained step by step for a plant: topic hierarchy, state versus event, payload contract and governance decisions.
Read the articleRelated solutions
Make shop-floor data ready to share.
IT/OT architects and system integratorsFlow & project scope Sensor / OPC UA → Model / MQTT / RESTFeed your model with actual shop-floor data.
Digital transformation and engineering teamsFlow & project scopeYour next step
Share your source, destination and intended outcome. We’ll help define the project scope.