Open Platform Communications (OPC) Protocol Driver for OASyS

To retrieve data from a third-party Open Platform Communications (OPC) server, you must implement and configure communication between AVEVA Enterprise SCADA and the third-party OPC server.

The incoming OPC interface uses the standard Omnicomm protocol infrastructure to leverage the existing baseline functionality for krunching data, alarming, etc. Since a typical Omnicomm protocol is a one-thread process and uses native protocol rather than COM or DCOM, a front-end processor (OPC client process) is required to facilitate communication between the AVEVA Enterprise SCADA host and the OPC server. A visual representation of this is shown in the model below.

The OPC Client process communicates with the OPC server via COM or DCOM.

Omnicomm communicates with the OPC Client process using OPC Client process protocol via TCP/IP.