• "OPC Gateway" between any Data Access resp. XML-DA implementations
• bridges the differences of Data Access version 1,2 or 3 implementations
• turns a non-compliant OPC server into a compliant OPC server
• connects DCOM with Web Services platforms
• enables OPC communication via Internet
• "OPC bridge" between Windows and Linux or any other operating system with web services support
• no programming required
• supports OPC DA 1.0a, 2.0, 3.0, XML-DA 1.0
• can be used as application (executable), InProc DLL or as service
• with own Web Server diagnostic interface

From the point of view of an OPC client application, access to the configured OPC server through the OPC Bridge is fully transparent, which means that the OPC Bridge provides the namespace of the configured OPC server to a client without any changes.

Bridge Between Data Access Implementations
There are only minor differences between the DA 1.0, DA 2.05 and DA 3 versions. Nevertheless, the more recent versions contain extensions that are not supported by previous implementations. As no compliance test tool exists for the DA 1.0 Specification, no compliance verification can be provided for DA 1.0 servers. The OPC Bridge turns a non-compliant OPC server into a compliant OPC server!

Bridge between DA and XML-DA Implementations
Substantial differences exist between the DCOM based Data Access Specifications and the web services and XML based XML-DA Specification. XML-DA servers can run on all operating systems that support web services. The XML-DA client and server can communicate over the Internet across firewall boundaries. The OPC Bridge connects the DCOM world with the web services world. The OPC Bridge always needs to be installed in a PC supporting DCOM.