In the ever-evolving landscape of industrial control systems (ICS), the Purdue Model has long been a standard for architecting these systems. However, as technology advances and the Industrial Internet of Things (IIoT) rises in significance, the Unified Namespace (UNS) architecture has become increasingly prominent. Read More
The Unified Namespace (UNS) has proven to be a popular architecture for folks undergoing a digital transformation initiative. At the core of the unified namespace architecture is a centralized repository of structured data which any application or device can subscribe or publish data to. Utilizing a hub and spoke architecture provides the benefit of decoupling your data from the application layer – each node only needs to subscribe and publish to data within the UNS rather than create discrete connections to each device/application in your ecosystem. Read More
We are currently working with a greenfield food and beverage startup and are implementing a unified namespace. To put it simply, a unified namespace is a centralized repository of structured data in which any application or device can subscribe and/or publish data to. In our case this centralized repository is an MQTT broker.
For plant floor device integration, we are using HighByte Intelligence Hub to model information from plant floor devices and ‘flow’ that data to the broker.