MatrikonOPC Data Manager

MatrikonOPC's Data Manager acts as a data bridge between OPC Servers and links them together

Acts as a data bridge between OPC Servers and links them together

Matrikon OPC Data Manager (ODM) is a software application that transfers data from one OPC server to another. Use ODM when you need to share data between two or more control systems (e.g. PLC and a DCS). With ODM this connectivity can be accomplished with standard, off-the-shelf software

Traditionally hard wires connected both inputs and outputs of control systems to transfer such data. This made data sharing complex to setup properly and expensive to maintain. OPC is well suited to sharing data between different vendors’ systems because it eliminates connectivity problems caused by proprietary communications. The easiest way to connect two OPC Servers (one for each device) is to use OPC Data Manager. OPC Data Manager is specifically designed to share real-time, historical, and Alarm & Events data between two or more control systems in a secure and reliable manner. The interface is intuitive making the mapping process quick and easy.

 

OLE for Process Control (OPC) servers are available for every major system on the market today. OPC-enabled systems share data by implementing one application as an OPC client and another as an OPC server. Sometimes, however, neither application is an OPC client; instead, both are servers. Two OPC servers can't exchange data, as they are designed to respond to a client's requests and are unable to generate requests. OPC Data Manager solves this problem by acting as a 'double-headed' or 'thin' OPC client to both OPC Servers. It requests data from one server and immediately sends it to the other OPC server.

 

Seamlessly link your OPC servers with Matrikon OPC Data Manager (ODM)!

Easily transfer real-time, historical, and Alarm & Events data between different control systems—no complex wiring needed. Simplify your data sharing and ensure secure, reliable connectivity with our intuitive software. Ready to streamline your data integration? Get started with ODM today!

Although OPC is a standard, it only supports communications between OPC servers and OPC clients. If data needs to be transferred from one OPC server to another or from one OPC client to another, standard OPC is insufficient. Matrikon OPC™ Data Manager is an OPC client designed to provide a solution for these OPC connectivity problems. MatrikonOPC Data Manager allows you to link OPC-compliant servers so that data changes on one server can be transmitted (i.e., mirrored) to another server

Features

OPC 1.0a, and OPC 2.0
Supports both COM and DCOM.
Can run as a Windows server, or as a normal application.
Enables easy and efficient re-transmission of data among OPC servers.
Allows this data to be viewed as it is updated.
Provides DDE and OPC server functionality.
Performs extensive error tracking and management.
Supports redundancy operation (version 4.0 and onward).

Software Requirements

The server requires the following software:
Microsoft Windows 7 (32-bit and 64-bit) or 10 or 11 or
Microsoft Windows Server 2008 R2, or 2012 R2 or 2016 or 2019 or 2022.

Note: It is recommended that the most current service packs are
installed.

Microsoft .NET Framework
o On Microsoft Windows 7 and 2008, the Matrikon OPC installation package will automatically install the required Dot Net framework.
o On Microsoft Windows 10, Windows 2012, and higher, Microsoft Dot Net 3.5 will need to be installed manually by the user before the OPC server can be installed.

Hardware Requirements

The server requires the following hardware:
Intel® Pentium® 4 Processor
512 MB RAM
40 GB 7200 RPM hard drive

Bridging OPC Servers

 OPC servers are available for every major system on the market today. Traditional OPC enabled systems share data by implementing one application as an OPC client and another as an OPC server. Sometimes, however, neither application is an OPC client; instead, both are servers. Two OPC servers can‘t exchange data, as they are designed to respond to a client‘s requests and are unable to generate requests. ODM solves this problem by acting as a “double-headed” or “thin” OPC client to both servers. It requests data from one server and immediately sends it to the other OPC server