{"id":760,"date":"2026-03-01T16:39:01","date_gmt":"2026-03-01T06:39:01","guid":{"rendered":"https:\/\/www.nicks-software.com\/wordpress\/?p=760"},"modified":"2026-03-01T16:52:43","modified_gmt":"2026-03-01T06:52:43","slug":"unified-namespace-uns-architecture-topic-structure","status":"publish","type":"post","link":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/","title":{"rendered":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT)"},"content":{"rendered":"<p>If you\u2019re new to the term, here\u2019s the short version: a Unified Namespace (UNS) is a <strong>pub\/sub information architecture<\/strong> for industrial data. It\u2019s not a product. It\u2019s not a dashboard. And it\u2019s definitely not \u201cjust an MQTT broker\u201d.<\/p>\n<p>In this post, I\u2019ll focus on the part most teams get stuck on: <strong>the architecture<\/strong> \u2014 what needs to exist, how to structure your topics, and how to keep your UNS usable (rather than turning into a data swamp).<\/p>\n<hr \/>\n<h2>What \u201carchitecture\u201d means in a Unified Namespace<\/h2>\n<p>When people say \u201cUNS architecture\u201d, they usually mean four things:<\/p>\n<ul>\n<li><strong>Transport\/broker layer<\/strong>: how events move around (MQTT is common).<\/li>\n<li><strong>Namespace structure<\/strong>: how you organise context (enterprise\/site\/line\/station).<\/li>\n<li><strong>Payload contracts<\/strong>: what\u2019s inside messages (schema, units, timestamps, quality).<\/li>\n<li><strong>Governance<\/strong>: who is allowed to publish what, and how you keep it consistent over time.<\/li>\n<\/ul>\n<p>MQTT is popular because it\u2019s lightweight and flexible. But that flexibility is also the trap: <strong>you can publish anything you want on any topic<\/strong>. Without a shared structure and payload contract, you\u2019ll create a system that is technically \u201cconnected\u201d but operationally useless.<\/p>\n<h2>UNS is not a broker (and why that distinction matters)<\/h2>\n<p>A broker is a piece of infrastructure. A UNS is an <strong>information model and distribution pattern<\/strong>. You can implement a UNS on top of multiple broker technologies. MQTT is one of them, and it\u2019s a great fit for many manufacturing environments.<\/p>\n<p>Think of it like this:<\/p>\n<ul>\n<li><strong>MQTT<\/strong> answers: \u201cHow do we move messages?\u201d<\/li>\n<li><strong>UNS<\/strong> answers: \u201cWhat do those messages mean, where do they live, and who can rely on them?\u201d<\/li>\n<\/ul>\n<p>If you treat the broker as \u201cthe UNS\u201d, you\u2019ll usually end up with a flat pile of topics that nobody trusts. If you treat the UNS as an architecture, you can scale to dozens of producers and consumers without reinventing integrations every time.<\/p>\n<hr \/>\n<h2>The core building blocks (practical, not theoretical)<\/h2>\n<h3>1) MQTT brokers (often more than one)<\/h3>\n<p>Most real deployments don\u2019t have a single broker sitting in one place forever. You often end up with brokers at different levels:<\/p>\n<ul>\n<li><strong>Edge\/cell\/machine level<\/strong>: local broker close to equipment for resilience and low latency.<\/li>\n<li><strong>Site level<\/strong>: broker that aggregates multiple lines\/cells.<\/li>\n<li><strong>Enterprise level<\/strong>: broker (or broker cluster) for cross-site visibility and enterprise consumers.<\/li>\n<\/ul>\n<p>This isn\u2019t \u201cover-engineering\u201d \u2014 it\u2019s how you avoid a single point of failure and how you manage bandwidth, latency and intermittent connectivity. Your namespace can be composed and extended as you move up levels.<\/p>\n<h3>2) Producers (publishers)<\/h3>\n<p>Producers create authoritative events\/states. Examples:<\/p>\n<ul>\n<li>Edge applications that read PLC tags and publish normalised values<\/li>\n<li>Connectors that publish MES events (e.g. job start\/stop, routing, quality checks)<\/li>\n<li>Quality systems that publish holds, defects, NCRs\/NCMRs<\/li>\n<li>Maintenance systems that publish downtime reasons, work orders, and completion events<\/li>\n<\/ul>\n<h3>3) Consumers (subscribers)<\/h3>\n<p>Consumers subscribe and act. Examples:<\/p>\n<ul>\n<li>Dashboards \/ BI (Power BI, Grafana, custom)<\/li>\n<li>Historians and time-series storage<\/li>\n<li>Alerting and escalation workflows<\/li>\n<li>AI assistants \/ RAG tools (answer questions from procedures + live context)<\/li>\n<li>Integration services (sync to ERP, planning tools, warehouse systems)<\/li>\n<\/ul>\n<h3>4) A \u201ctranslation\/normalisation\u201d layer<\/h3>\n<p>Raw PLC tags are not a UNS. A UNS typically needs a layer that:<\/p>\n<ul>\n<li>maps tag names into a shared topic hierarchy<\/li>\n<li>normalises units and naming (e.g. \u201cTempC\u201d vs \u201cTemperature\u201d)<\/li>\n<li>adds timestamps and quality<\/li>\n<li>converts legacy formats into consistent payloads<\/li>\n<\/ul>\n<p>This is where most value is created, because this is where \u201cintegration once\u201d becomes possible.<\/p>\n<hr \/>\n<h2>Topic structure: the part that makes or breaks your UNS<\/h2>\n<hr \/>\n<h2>Using ISA-95 as the backbone for the UNS topic structure<\/h2>\n<p>One practical way to keep a Unified Namespace consistent (especially as more producers come online) is to align your topic hierarchy with <strong>ISA-95<\/strong>.<\/p>\n<p>ISA-95 is widely used as a reference model for how manufacturing organisations and systems are structured. You don\u2019t need to \u201cimplement ISA-95 perfectly\u201d to benefit from it \u2014 you just need a stable backbone that matches how factories actually think: enterprise\/site\/area\/line\/cell\/unit.<\/p>\n<h3>ISA-95 levels (quick mapping)<\/h3>\n<ul>\n<li><strong>Level 4<\/strong> \u2014 Enterprise \/ ERP scope<\/li>\n<li><strong>Level 3<\/strong> \u2014 Site\/operations management (MES scope)<\/li>\n<li><strong>Level 2<\/strong> \u2014 Area\/supervisory control (SCADA scope)<\/li>\n<li><strong>Level 1<\/strong> \u2014 Cell\/equipment\/sensors and control (PLC\/edge scope)<\/li>\n<\/ul>\n<p>In an UNS, this helps you create a topic structure where the context is predictable and scalable, and where you can reason about <em>plant-level<\/em> vs <em>enterprise-level<\/em> subscriptions.<\/p>\n<h3>ISA-95-ish topic hierarchy (example)<\/h3>\n<p>Here\u2019s an example that keeps the spirit of ISA-95 and works well in MQTT:<\/p>\n<pre><code>enterprise\/{enterprise}\/site\/{site}\/area\/{area}\/line\/{line}\/cell\/{cell}\/unit\/{unit}\/\n  state\/\n  events\/\n  alarms\/\n  metrics\/\n<\/code><\/pre>\n<p>If your environment uses different terms (e.g. <em>work_center<\/em>, <em>station<\/em>, <em>asset<\/em>), that\u2019s fine \u2014 the key is that the hierarchy remains consistent and that each level has a clear meaning and owner.<\/p>\n<p>The goal of topic structure is simple: <strong>encode context in a predictable way<\/strong>, so any consumer can find what they need without knowing the producer implementation details.<\/p>\n<p>There isn\u2019t one perfect hierarchy, but there are strong patterns. A good hierarchy usually answers these questions:<\/p>\n<ul>\n<li>Which enterprise\/site is this data from?<\/li>\n<li>Which area\/line\/cell\/station produced it?<\/li>\n<li>Is it a state, an event, an alarm, or a KPI?<\/li>\n<li>What is the asset or process being described?<\/li>\n<\/ul>\n<h3>A practical baseline hierarchy<\/h3>\n<p>This is a good starting point for many manufacturers:<\/p>\n<pre><code>enterprise\/{enterprise}\/site\/{site}\/area\/{area}\/line\/{line}\/cell\/{cell}\/station\/{station}\/\n  state\/\n  events\/\n  alarms\/\n  metrics\/\n<\/code><\/pre>\n<p>Notes:<\/p>\n<ul>\n<li><strong>state<\/strong> is the current value (e.g. machine mode, last cycle time, running\/stopped).<\/li>\n<li><strong>events<\/strong> are discrete facts (job started, job completed, defect recorded).<\/li>\n<li><strong>alarms<\/strong> are abnormal conditions and acknowledgements.<\/li>\n<li><strong>metrics<\/strong> are computed for KPIs (OEE components, FPY, throughput).<\/li>\n<\/ul>\n<h3>Alternate hierarchy: asset-centric<\/h3>\n<p>If you\u2019re very asset-focused, an alternative is:<\/p>\n<pre><code>enterprise\/{enterprise}\/site\/{site}\/assets\/{assetId}\/\n  state\/\n  events\/\n  alarms\/\n  metrics\/\n<\/code><\/pre>\n<p>This works well when assets move or when line\/station identity is messy. The tradeoff: you must maintain a reliable asset registry (and mapping to physical context).<\/p>\n<h3>Where \u201cwork orders\u201d and \u201cproducts\u201d fit<\/h3>\n<p>Don\u2019t cram everything into the same branch. A common pattern is to keep operational context separate:<\/p>\n<pre><code>enterprise\/{enterprise}\/site\/{site}\/production\/orders\/{orderId}\/events\nenterprise\/{enterprise}\/site\/{site}\/production\/products\/{productCode}\/spec\n<\/code><\/pre>\n<p>That makes it easier for enterprise consumers to subscribe to \u201call order events\u201d without knowing line topology.<\/p>\n<hr \/>\n<h2>Payloads: don\u2019t let MQTT freedom destroy semantics<\/h2>\n<p>Topics are only half the story. The payload carries the meaning.<\/p>\n<p>A good UNS payload convention makes downstream tools dramatically easier to build. A simple approach is to standardise on JSON with a small set of required fields:<\/p>\n<pre><code>{\n  \"ts\": \"2026-03-01T06:21:00Z\",\n  \"value\": 6.8,\n  \"unit\": \"pH\",\n  \"quality\": \"good\",\n  \"source\": \"PLC-L3-Station2\",\n  \"meta\": {\n    \"tag\": \"PH_Reading\",\n    \"note\": \"optional\"\n  }\n}\n<\/code><\/pre>\n<p>For events, use an event envelope:<\/p>\n<pre><code>{\n  \"ts\": \"2026-03-01T06:21:00Z\",\n  \"eventType\": \"DowntimeStarted\",\n  \"asset\": \"Line3.Station2\",\n  \"payload\": {\n    \"reason\": \"Material shortage\",\n    \"workOrder\": \"MO-18427\"\n  }\n}\n<\/code><\/pre>\n<p>Does it have to be JSON? No. But you need <strong>something<\/strong> consistent. Otherwise, every consumer becomes a bespoke integration again.<\/p>\n<h3>State vs event vs metric payloads<\/h3>\n<ul>\n<li><strong>State<\/strong> should be compact and frequent (changes \/ sampled).<\/li>\n<li><strong>Events<\/strong> should be durable, meaningful, and easy to replay.<\/li>\n<li><strong>Metrics<\/strong> should carry definition metadata (window, aggregation, version).<\/li>\n<\/ul>\n<hr \/>\n<h2>Plant-level visibility vs enterprise-level visibility (how to support both)<\/h2>\n<p>This is a common UNS question: \u201cHow do I implement a hierarchy that supports plant-level and enterprise-level visibility?\u201d<\/p>\n<p>The answer is: <strong>don\u2019t try to cram everything into one subscription pattern<\/strong>. Provide stable subscription points:<\/p>\n<ul>\n<li>Plant-level apps subscribe to: <code>...\/line\/+\/+\/state\/#<\/code> (or similar)<\/li>\n<li>Enterprise apps subscribe to: <code>enterprise\/{enterprise}\/site\/{site}\/+\/+\/metrics\/#<\/code><\/li>\n<li>Cross-site apps subscribe to: <code>enterprise\/{enterprise}\/+\/+\/production\/orders\/+\/events<\/code><\/li>\n<\/ul>\n<p>The trick is to keep the hierarchy predictable. If you need to change it, version it rather than \u201cbreaking\u201d consumers silently.<\/p>\n<hr \/>\n<h2>Governance (the part everyone avoids \u2014 and then pays for)<\/h2>\n<p>UNS governance sounds boring until you\u2019ve got 20 producers publishing 20 different \u201cmachine states\u201d to 20 different places.<\/p>\n<p>Governance is simply answering:<\/p>\n<ul>\n<li><strong>Who can publish?<\/strong> (which systems are authoritative for which topics)<\/li>\n<li><strong>What are the contracts?<\/strong> (schemas, units, naming conventions)<\/li>\n<li><strong>How do we change things?<\/strong> (versioning, deprecation, migration windows)<\/li>\n<li><strong>How do we validate?<\/strong> (linting topics, schema validation, monitoring)<\/li>\n<\/ul>\n<h3>Anti-pattern: \u201canything anywhere\u201d<\/h3>\n<p>MQTT makes it easy to publish anything anywhere. That\u2019s both the superpower and the failure mode. A UNS only works long-term when you restrict publishing paths and enforce a shared model.<\/p>\n<h3>Practical governance you can actually implement<\/h3>\n<ul>\n<li>Create a simple <strong>namespace spec<\/strong> (a 2\u20135 page document) with examples.<\/li>\n<li>Assign <strong>ownership<\/strong> per domain (production, quality, maintenance).<\/li>\n<li>Enforce broker ACLs so only approved producers can publish to critical paths.<\/li>\n<li>Set up monitoring for \u201cunknown topics\u201d and schema violations.<\/li>\n<\/ul>\n<hr \/>\n<h2>Common UNS mistakes (and how to avoid them)<\/h2>\n<ul>\n<li><strong>Flat topics<\/strong> (no context). Fix by encoding site\/line\/station consistently.<\/li>\n<li><strong>No payload standard<\/strong>. Fix by publishing envelopes for state\/events.<\/li>\n<li><strong>Mixing concerns<\/strong> (raw tags + metrics + business events in one branch). Fix by separating namespaces.<\/li>\n<li><strong>Governance after the fact<\/strong>. Fix by starting with a minimal spec and enforcing it.<\/li>\n<li><strong>Assuming the UNS replaces everything<\/strong>. It complements MES\/SCADA\/historians; it doesn\u2019t magically eliminate them.<\/li>\n<\/ul>\n<hr \/>\n<h2>A simple reference implementation roadmap<\/h2>\n<ol>\n<li><strong>Pilot one line<\/strong>: publish a small set of state + events you know you need.<\/li>\n<li><strong>Prove consumers<\/strong>: dashboard + alerting + one integration (e.g. downtime workflow).<\/li>\n<li><strong>Write the spec<\/strong>: freeze naming, payload envelopes, and ACL policy.<\/li>\n<li><strong>Scale producers<\/strong>: replicate the pattern across stations\/lines.<\/li>\n<li><strong>Add enterprise consumers<\/strong>: BI, reporting, analytics, and AI assistants.<\/li>\n<\/ol>\n<h2>Want an UNS functional specification template?<\/h2>\n<p>If you\u2019re implementing a Unified Namespace and want a practical spec template (topic hierarchy, payload contracts, ownership, ACLs), <a href=\"https:\/\/www.nicks-software.com\/wordpress\/contact\/\">contact me<\/a>, and I\u2019ll share a starting point.<\/p>\n<p><strong>Disclaimer:<\/strong> For educational purposes only. Every factory environment is different.<\/p>\n<hr \/>\n<h2>Why a UNS is a strong foundation for AI agents in manufacturing<\/h2>\n<p>Most \u201cAI agent\u201d discussions jump straight to models and prompts. In manufacturing, the bigger issue is usually <strong>context<\/strong>: what\u2019s happening right now, where it\u2019s happening, and what it means.<\/p>\n<p>A Unified Namespace helps because it provides a <strong>standardised, governed event and state layer<\/strong> that agents can subscribe to. Instead of building one-off integrations for each use case, you give agents a consistent way to observe operations.<\/p>\n<h3>UNS + AI agents: the simple mental model<\/h3>\n<ul>\n<li><strong>UNS<\/strong> = what\u2019s happening (events + state in a consistent structure)<\/li>\n<li><strong>RAG \/ knowledge base<\/strong> = what to do about it (SOPs, work instructions, QMS docs)<\/li>\n<li><strong>Agent workflows<\/strong> = who to notify \/ what system to update \/ what action to trigger<\/li>\n<\/ul>\n<p>In other words: RAG can answer questions from documents, but a UNS gives you the live operational signals that tell you <em>when<\/em> to ask the question and <em>which context<\/em> matters (site\/line\/station\/order).<\/p>\n<h3>Concrete examples<\/h3>\n<ul>\n<li><strong>Downtime event<\/strong> (e.g. \u201cLine 3 downtime &gt; 8 minutes\u201d) \u2014 create a maintenance ticket, pull the right troubleshooting steps from SOPs, and notify the right team.<\/li>\n<li><strong>Material shortage event<\/strong> \u2014 alert planning, surface alternates\/notes, and update order status.<\/li>\n<li><strong>Quality hold \/ defect cluster<\/strong> \u2014 trigger containment workflow and attach the correct inspection procedure.<\/li>\n<\/ul>\n<h3>Why this reduces hallucination risk<\/h3>\n<p>Agents fail when they\u2019re fed ambiguous, inconsistent data. A well-governed UNS reduces that risk by enforcing:<\/p>\n<ul>\n<li>consistent topic structure (context is predictable)<\/li>\n<li>payload contracts (schemas\/units\/quality)<\/li>\n<li>ownership of sources (which system is authoritative)<\/li>\n<\/ul>\n<p>If you\u2019re exploring AI agents for manufacturing, you may also like: <a href=\"https:\/\/www.nicks-software.com\/ns-graphrag.html\">Private RAG knowledge assistant<\/a> and <a href=\"https:\/\/www.nicks-software.com\/ai-solutions.html\">AI solutions<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you\u2019re new to the term, here\u2019s the short version: a Unified Namespace (UNS) is a pub\/sub information architecture for industrial data. It\u2019s not a product. It\u2019s not a dashboard&#8230;.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"categories":[48],"tags":[],"class_list":["post-760","post","type-post","status-publish","format-standard","hentry","category-digital-transformation-iiot"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick&#039;s Software<\/title>\n<meta name=\"description\" content=\"Unified Namespace (UNS) architecture for manufacturing: topic structure, naming conventions, examples, governance, and common mistakes. Practical guidance for implementing a UNS over MQTT.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick&#039;s Software\" \/>\n<meta property=\"og:description\" content=\"Unified Namespace (UNS) architecture for manufacturing: topic structure, naming conventions, examples, governance, and common mistakes. Practical guidance for implementing a UNS over MQTT.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/\" \/>\n<meta property=\"og:site_name\" content=\"Nick&#039;s Software Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-01T06:39:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-01T06:52:43+00:00\" \/>\n<meta name=\"author\" content=\"Nick\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick&#039;s Software\" \/>\n<meta name=\"twitter:description\" content=\"Unified Namespace (UNS) architecture for manufacturing: ISA-95-aligned topic structure, MQTT patterns, governance, and examples.\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Nick\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/\"},\"author\":{\"name\":\"Nick\",\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/#\\\/schema\\\/person\\\/08fa5f96dd11f104278373a1f344475a\"},\"headline\":\"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT)\",\"datePublished\":\"2026-03-01T06:39:01+00:00\",\"dateModified\":\"2026-03-01T06:52:43+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/\"},\"wordCount\":1750,\"commentCount\":0,\"articleSection\":[\"Digital Transformation &amp; IIoT\"],\"inLanguage\":\"en-AU\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/\",\"url\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/\",\"name\":\"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick's Software\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/#website\"},\"datePublished\":\"2026-03-01T06:39:01+00:00\",\"dateModified\":\"2026-03-01T06:52:43+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/#\\\/schema\\\/person\\\/08fa5f96dd11f104278373a1f344475a\"},\"description\":\"Unified Namespace (UNS) architecture for manufacturing: topic structure, naming conventions, examples, governance, and common mistakes. Practical guidance for implementing a UNS over MQTT.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/#breadcrumb\"},\"inLanguage\":\"en-AU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/2026\\\/03\\\/unified-namespace-uns-architecture-topic-structure\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Digital Transformation &amp; IIoT\",\"item\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/digital-transformation-iiot\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/#website\",\"url\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/\",\"name\":\"Nick's Software Blog\",\"description\":\"Digital Transformation and IIoT Solutions | Custom Software Development\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-AU\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/#\\\/schema\\\/person\\\/08fa5f96dd11f104278373a1f344475a\",\"name\":\"Nick\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-AU\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/91b5397101137294d66362d624d4300f7535d4d620a6d5f3c4a6617f9da3b211?s=96&d=robohash&r=x\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/91b5397101137294d66362d624d4300f7535d4d620a6d5f3c4a6617f9da3b211?s=96&d=robohash&r=x\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/91b5397101137294d66362d624d4300f7535d4d620a6d5f3c4a6617f9da3b211?s=96&d=robohash&r=x\",\"caption\":\"Nick\"},\"sameAs\":[\"https:\\\/\\\/nicks-software.com\"],\"url\":\"https:\\\/\\\/www.nicks-software.com\\\/wordpress\\\/author\\\/nick\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick's Software","description":"Unified Namespace (UNS) architecture for manufacturing: topic structure, naming conventions, examples, governance, and common mistakes. Practical guidance for implementing a UNS over MQTT.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/","og_locale":"en_US","og_type":"article","og_title":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick's Software","og_description":"Unified Namespace (UNS) architecture for manufacturing: topic structure, naming conventions, examples, governance, and common mistakes. Practical guidance for implementing a UNS over MQTT.","og_url":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/","og_site_name":"Nick&#039;s Software Blog","article_published_time":"2026-03-01T06:39:01+00:00","article_modified_time":"2026-03-01T06:52:43+00:00","author":"Nick","twitter_card":"summary_large_image","twitter_title":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick's Software","twitter_description":"Unified Namespace (UNS) architecture for manufacturing: ISA-95-aligned topic structure, MQTT patterns, governance, and examples.","twitter_misc":{"Written by":"Nick","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/#article","isPartOf":{"@id":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/"},"author":{"name":"Nick","@id":"https:\/\/www.nicks-software.com\/wordpress\/#\/schema\/person\/08fa5f96dd11f104278373a1f344475a"},"headline":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT)","datePublished":"2026-03-01T06:39:01+00:00","dateModified":"2026-03-01T06:52:43+00:00","mainEntityOfPage":{"@id":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/"},"wordCount":1750,"commentCount":0,"articleSection":["Digital Transformation &amp; IIoT"],"inLanguage":"en-AU","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/","url":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/","name":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT) | Nick's Software","isPartOf":{"@id":"https:\/\/www.nicks-software.com\/wordpress\/#website"},"datePublished":"2026-03-01T06:39:01+00:00","dateModified":"2026-03-01T06:52:43+00:00","author":{"@id":"https:\/\/www.nicks-software.com\/wordpress\/#\/schema\/person\/08fa5f96dd11f104278373a1f344475a"},"description":"Unified Namespace (UNS) architecture for manufacturing: topic structure, naming conventions, examples, governance, and common mistakes. Practical guidance for implementing a UNS over MQTT.","breadcrumb":{"@id":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/#breadcrumb"},"inLanguage":"en-AU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.nicks-software.com\/wordpress\/2026\/03\/unified-namespace-uns-architecture-topic-structure\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.nicks-software.com\/wordpress\/"},{"@type":"ListItem","position":2,"name":"Digital Transformation &amp; IIoT","item":"https:\/\/www.nicks-software.com\/wordpress\/digital-transformation-iiot\/"},{"@type":"ListItem","position":3,"name":"Unified Namespace (UNS) Architecture: Topic Structure + Examples (MQTT)"}]},{"@type":"WebSite","@id":"https:\/\/www.nicks-software.com\/wordpress\/#website","url":"https:\/\/www.nicks-software.com\/wordpress\/","name":"Nick's Software Blog","description":"Digital Transformation and IIoT Solutions | Custom Software Development","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.nicks-software.com\/wordpress\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-AU"},{"@type":"Person","@id":"https:\/\/www.nicks-software.com\/wordpress\/#\/schema\/person\/08fa5f96dd11f104278373a1f344475a","name":"Nick","image":{"@type":"ImageObject","inLanguage":"en-AU","@id":"https:\/\/secure.gravatar.com\/avatar\/91b5397101137294d66362d624d4300f7535d4d620a6d5f3c4a6617f9da3b211?s=96&d=robohash&r=x","url":"https:\/\/secure.gravatar.com\/avatar\/91b5397101137294d66362d624d4300f7535d4d620a6d5f3c4a6617f9da3b211?s=96&d=robohash&r=x","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/91b5397101137294d66362d624d4300f7535d4d620a6d5f3c4a6617f9da3b211?s=96&d=robohash&r=x","caption":"Nick"},"sameAs":["https:\/\/nicks-software.com"],"url":"https:\/\/www.nicks-software.com\/wordpress\/author\/nick\/"}]}},"_links":{"self":[{"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/posts\/760","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/comments?post=760"}],"version-history":[{"count":5,"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/posts\/760\/revisions"}],"predecessor-version":[{"id":765,"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/posts\/760\/revisions\/765"}],"wp:attachment":[{"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/media?parent=760"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/categories?post=760"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nicks-software.com\/wordpress\/wp-json\/wp\/v2\/tags?post=760"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}