STOP UNIFYING EVERYTHING
IN A MONOLITHIC UNS WHERE EVERY NODE TRUSTS EVERY OTHER NODE, YOU HAVEN’ T BUILT RESILIENCE, YOU’ VE BUILT A BLAST RADIUS.
The Promise
For the past few years, the industrial automation world has been chasing a single idea: put everything into one monolithic namespace. Connect every PLC, sensor, historian, and ERP system into a single data fabric. One broker to handle protocol conversion, naming conventions, security, and edge-to-cloud bridging. It solves a real problem— decades of incompatible data islands have cost the industry enormously in engineering hours, delayed decisions, and missed optimization.
The Problem
But solving a data accessibility problem by removing all architectural boundaries is like solving traffic congestion by tearing out every curb, sidewalk, and traffic signal.
When every node in your namespace can reach every other node, you have not built a resilient system. A compromised HMI in one building has a direct path to your corporate historian. A misconfigured MQTT client can flood your broker and take down visibility across the entire plant.
In traditional OT architecture, segmentation was a feature— sometimes an accidental one, but a feature nonetheless. Air gaps and protocol barriers meant that a failure or breach stayed local. A monolithic UNS trades that containment for convenience, introducing a single point of failure, increased latency, and difficulty segmenting OT networks.
The architects and engineers who have to live with these systems are asking questions the evangelists skip: What happens when the broker goes down? What is the blast radius of a compromised node? How do you enforce data sovereignty across sites? Who owns the schema?
The Fractal Alternative
There is another way. A fractal UNS replicates the same namespace structure at every level of the operations hierarchy— machine, line, factory, site, enterprise, and cloud. Each cell, line, or site maintains its own local namespace, fully functional and autonomous. Data flows through defined, controlled pathways— not through open mesh connectivity.
34 MACHINERY, AUTOMATION, CONTROL & ENGINEERING