Redundancy Broker

Enhance system reliability with seamless failover capabilities for OPC servers.

OPC Redundancy Broker offers a seamless software solution that implements driver level redundancy supporting both OPC DA, HDA, and A&E

The OPC Redundancy Broker (ORB) enables easy implementation of redundancy in systems that take advantage of OPC technology. ORB is designed for OPC applications that must use redundant hardware and/or software to achieve the highest degree of communication reliability. ORB can even be retrofitted to current systems since ORB functions with any OPC server, regardless of vendor.

ORB constantly monitors the Primary OPC server. When a failure is detected, it automatically redirects communication to the Standby OPC server. No data is lost and there is no system downtime. 

OPC Alarms & Events Functionality

OPC Redundancy Broker now supports the OPC Alarms & Events (OPC A&E) specification. This increased functionality is designed for solutions that require highly available sequence of event (SOE) data. There is no other product on the market today that provides users with industrial strength OPC server level redundancy like MatrikonOPC Redundancy Broker.

Easy Implementation

ORB works with any OPC Client software. It handles all configuration and fail-over issues automatically! ORB enables easy implementation of a transparent, redundant environment with no programming required.

Seamless Integration

ORB can be used to seamlessly upgrade an existing OPC infrastructure. Once a standby OPC Server is added, ORB will automatically enable all the client software to quickly make use of the reinforced system.

Increase the availability of Safety Systems Data

There are countless scenarios where Matrikon OPC Redundancy Broker can be effectively used to enhance the performance of plant safety systems. One such example is to combine the proven reliability of OPC Redundancy technology to create a robust solution for interfacing with Triconex safety systems. This solution provides OPC A&E client applications (i.e. MatrikonOPC A&E Historian) with the ability to increase the availability of Sequence of Event (SOE) data. Users can now easily combine Triconex’s famous triple redundancy with full OPC DA/A&E redundancy right out of the box!

Ensure uninterrupted data delivery with MatrikonOPC Redundancy Broker

Easily set up redundant OPC Server systems to eliminate single points of failure and maintain reliable communications. Protect your critical applications from data loss and downtime—implement OPC Redundancy Broker today for seamless operation and peace of mind!

OPC Redundancy Broker constantly monitors a Primary OPC server that is designated by the user. When a failure is detected, OPC Redundancy Broker automatically redirects communications to a Standby OPC server. By intelligently switching between the primary and standby OPC Servers – OPC Redundancy Broker prevents data loss and downtime in the event one of the OPC Servers fails.

Features

Support for multiple, same server, redundant pairs 
Support redundancy for DA, A&E, and HDA OPC Servers
Full OPC HDA support for selected HDA interfaces
Status tags enable you to track which OPC Servers are down 
Multiple levels of redundancy (Hot, Warm, and Cold)
Automatically switches between from primary to standby or vice versa when the criterion of failover is detected
Allow “Force a Failover” to manually toggle between the primary to standby or vice versa 
Powerful failover detection engine (trigger failover on item deviation, threshold, rate of change, and quality) 
Windows 32-bit and 64-bit are natively supported 

Supported OPC Specs

 OPC DA (OPC Data Access) 1.0a, 2.0, 2.05, 3.0 
 OPC A&E (Alarms and Events) 
 OPC HDA (Historical Data Access)  1.0, 1.1, 1.2 

Types of Redundancy

Hot: in this mode, ORB subscribes to and activates tags on both the primary and the standby servers. This mode minimizes the data gap during failover because both OPC servers in the redundant pair constantly receive the same data updates

Warm: in this mode, ORB subscribes to tags in both the primary and standby servers. Tags are activated only in the primary server. When a failover condition occurs, tags are activated in the standby server. This option is popular in situations where it is not feasible to have the standby OPC server and the primary OPC servers active 

Cold: in this mode, ORB subscribes to and activates tags in the primary server only. When a fail-over occurs, ORB subscribes to and activates tags in the standby server. This is commonly used where only a single connection to the data source is possible (such as a serial connection)