Without an MQTT Topic Namespace, there is no Unified Namespace (UNS).

But despite being the cornerstone of the UNS, many are unsure how to effectively utilize it for creating a structured data hierarchy. 

Here are five key practices for developing a UNS semantic data hierarchy using the MQTT topic namespace.

Adopt the ISA-95 Common Data Model: Structure your MQTT topic namespace to mirror your organization’s hierarchy (Enterprise > Site > Area > Line > Cell), facilitating efficient data flow in manufacturing environments.

Version Your UNS MQTT Topic Namespace: As your UNS evolves, version your MQTT topic structures (e.g., mySpec/v1/…/$area/$line/$cell/$client-id). This aids in managing updates, maintaining system compatibility, and ensuring service continuity.

Establish an Edge Namespace: Map all data, especially PLC tags, to your UNS, maintaining a specific namespace for raw data (Enterprise/site/area/line/cell/edge/). This step is crucial for initial data collection and aligns with your data governance strategy.

Create a Functional Namespace: Process raw data into a separate, organized namespace for specific applications (Enterprise/site/area/line/cell/functions/…). This structured approach enables the creation of functions and visualizations based on standardized UNS data, supporting various organizational KPIs.

Regularly Remove Inactive Elements from UNS: Audit and cleanse your UNS regularly to eliminate obsolete elements like unused devices and sensors. Use the ‘retain’ flag appropriately to efficiently manage this process.

Additionally, it’s important to document your namespaces clearly and align them with your organizational structure for easy access and consistency. 

Remember, while UNS is a powerful approach, it’s not one-size-fits-all and should be tailored to your organization’s unique needs.

Have a great day, and see you next week.

Kudzai