Safety I/O Mesh Architecture for Flexible Controller Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Safety Instrumented Systems (SIS) in industrial automation have a fixed relationship between safety I/O modules and controllers, requiring dedicated communication structures and manual configurations, which limits flexibility and increases upfront architecture and design work, and reduces availability due to dependency on other controllers' operation.
Innovation Solution
Implementing an I/O mesh network that allows any safety controller to utilize I/O points from a pool of safety I/O modules, enabling flexible configuration and shared resource usage between safety and process control systems, thereby enhancing modular construction and capital efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a fixed relationship between safety I/O modules and controllers is used, then system reliability is improved through dedicated communication structures, but device complexity and upfront design work increase
Solution Approach 1:
The patent implements a universal I/O pooling mechanism where safety I/O modules can be dynamically allocated to multiple controllers through a mesh network. Instead of dedicating specific I/O modules to specific controllers, the system creates a shared pool that any controller can access, reducing communication structure complexity while maintaining reliability through redundant pathways.
Solution Approach 2:
The system transitions from static I/O-controller assignments to dynamic allocation through the mesh network architecture. Controllers can dynamically request and access I/O points from any module in the pool based on real-time needs, allowing the system to adapt to changing requirements without reconfiguring physical connections.
2Stability of the object's composition
If dedicated communication structures are used for each controller-I/O pair, then system stability is improved, but ease of operation and flexibility decrease
Solution Approach 1:
The patent segments the communication architecture into two independent layers: a stable mesh network infrastructure that provides redundant communication pathways, and a flexible logical allocation layer that manages I/O point assignments. This segmentation allows the physical communication structure to remain stable while the logical configuration can be easily reconfigured.
Solution Approach 2:
The mesh network acts as an intermediary layer between controllers and I/O modules, decoupling their direct relationships. Controllers communicate through the mesh network infrastructure to access I/O points, allowing stable communication pathways to remain unchanged while flexibility is achieved through logical routing and allocation decisions made by the mesh network.
3Manufacturing precision
If manual configuration is required for I/O point allocation, then measurement precision of control assignments is improved, but loss of time in setup and configuration increases
Solution Approach 1:
The system implements self-service through automated I/O point allocation mechanisms within the mesh network. Controllers can automatically discover available I/O points in the pool and establish connections without manual configuration, while the system maintains precise tracking of assignments through automated registration and status monitoring.
Solution Approach 2:
The mesh network incorporates feedback mechanisms where controllers report their I/O requirements and the system automatically allocates appropriate points from the pool. The system continuously monitors assignment status and can dynamically reconfigure allocations based on changing conditions, maintaining precision while eliminating manual configuration time.
4Reliability
If I/O points are dedicated to specific controllers, then reliability is improved through reduced dependency, but productivity and capital efficiency decrease
Solution Approach 1:
The patent merges multiple controllers' I/O requirements into a single shared pool of I/O modules through the mesh network architecture. Instead of each controller having dedicated I/O modules, the system combines resources so that any controller can access any I/O point in the pool, improving capital efficiency and productivity while maintaining reliability through the redundant mesh communication pathways.
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
A safety instrumented system (SIS) includes safety controllers, and safety input/output (I/O) modules coupled to safety field devices that are coupled in parallel with a process control system's field devices to processing equipment which is configured and controlled to run a process. An I/O mesh network between the safety controllers and the safety I/O modules is configured for selecting any safety controller to become coupled to any safety I/O module to function as a pool of safety I/O modules so that any safety controller is configurable to receive sensor signals from and transmit control signals to any safety field device. The safety field devices are for monitoring process variable(s) for the process so that when one of the safety controllers recognizes a hazardous condition regarding the processing equipment, the SIS independently takes action to keep the processing equipment under control or bring it to a safe state.