The Unified Namespace has countless advantages over traditional architectural approaches when it comes to IIoT implementation in manufacturing.​Some of these are:👉 More efficient communication and data sharing between different devices and systems.👉 Improved scalability due to a unified interface that is consistent across the entire enterprise network.​But how do you go actually go about building a Unified Namespace Architecture?​To gain an understanding of this, I invited David Schultz for a podcast session.​David is the President of G5 Consulting where he works with manufacturers to help them develop and execute strategies for their digital transformation and asset management initiatives.​Below is the outline of our conversation.​✅ What is The Unified Namespace?✅ MQTT/Sparkplug for Unified Namespace✅ Tools and Strategies for Building the Unified Namespace✅ Data Normalisation and Contextualisation Techniques for UNS✅ Role and Significance of ISA 95 Schema in UNS✅ Using Multiple MQTT Brokers for a Unified namespace✅ Role played by Historian, MES, and ERP in UNS Architecture✅ Use Cases and Technologies for Data lake Integration with UNS✅ Approaches for Extending UNS with transactional Capabilities