Disadvantages of a Single-Piece Namespace Architecture and Alternative Approaches

[Süeda Asil]

In the industrial automation sector, while the idea of collecting all data within a single namespace and managing all systems through the same protocol and broker is gaining traction, this approach brings with it many significant risks and limitations.

Connecting PLCs, sensors, historians, and ERP systems via a single central broker simplifies access to operational data but also increases potential error and security problems within the system. Such a monolithic structure, while providing system integration, can lead to the entire system going offline in case of failures.

### Disadvantages of a Monolithic Namespace

• A central broker failure can cause the entire production facility to lose visibility.
• A single faulty or misconfigured component can affect the entire network, stopping data flow.
• Lack of segmentation from a security perspective increases the risk of attacks and errors spreading.
• Data sovereignty is difficult to implement across different geographies and regulations.
• Performance issues can occur in large systems containing over 150,000 tags.
• Managing the namespace schema and controlling changes becomes difficult.

### Fractal Namespace Alternative
The fractal namespace architecture provides fault isolation and segmentation by replicating a similar namespace structure at each level of the hierarchical structure. Each layer, such as factory, line, machine, and cloud, has its own autonomous and local namespace.

This structure;

• Provides fault isolation, preventing a failure in one layer from spreading to the entire plant level.
• Limits the spread of attacks through architectural segmentation.
• Ensures data sovereignty suitable for different regulations and field needs.
• Namespace management is shared among relevant teams, and changes can be made locally.
• Traffic is only sent to higher levels when necessary, preserving performance.

### Main Reasons for Adopting a Fractal Approach

• Monolithic UNS systems carry risks such as complexity and the entire plant losing visibility due to faulty configurations.
• Fractal design distributes complexity among teams familiar with the process, enabling on-site management.
• Specialized software is used to ensure data quality and consistency.
• Security is provided through architectural segments; it is more flexible than policy-based solutions.

### Conclusion
While a single, flat namespace may seem to solve the integration problem, it is a weak architecture in terms of resilience, security, and sustainability. Industry should move towards structural segmentation and fractal namespace models, considering failure and security modes as much as integration. "Stop trying to unify everything; start with purpose-built segmentation.