ClearSCADA

  DNP3 EcoStruxture Web Services OPC-DA OPC-XML-DA
Environment Description DNP3 Slave running at one end, standard DNP3 driver at the other EWS server enabled at one end, EWS client at the other OPC-DA client at one end, DBServer is inherently an OPC-DA server OPC-XML-DA client at one end, DBServer is inherently an OPC-XML-DA server
Addressing Method DNP3 point address as configured in the valuemap Database fullname and property Database fullname and property Database fullname and property
Data Read Current value, historical data and trends Current value, historical data and forecasts Current value Current value
Data Read Efficiency Good: Class 0, 1, 2, 3 polls and unsolicited Poor: Synchronous supported Excellent: Asynchronous supported Poor: Synchronous supported
Data Read Bandwidth Dependency Low, able to handle low bandwidth links when configured suitably Medium, http based High, affected by limited bandwidth Medium, http based
Data Read Latency Dependency Low, able to handle high latency when configured suitably Medium, http based Medium Medium, http based
Controls Supported Yes Yes Yes Yes
ClearSCADA Licence Requirements Included by default in licence WebX licence required OPC licence required OPC licence required
Database Authentication None, DNP3Secure v2 supported by DNP3 slave Defined by the server for all connecting clients Defined by the client, using private security only None (not supported by standard)
Ease of Configuration and Maintenance Poor, lots of options to tweak, valuemaps to maintain Great, simple configuration options Great, simple configuration options Great, simple configuration options
Inbuilt Encryption None, could use IPSec tunnels Use of https Not enabled by default Use of https
Basic Network Security Statically configured TCP/UDP connection Statically configured TCP connection Uses DCOM for dynamic port assignments Statically configured TCP connection
Network Analysis (i.e. Deep Packet Inspection/NIDS/NIPS) Limited protocol support on specialist devices XML based protocol, able to be processed by most IT appliances Microsoft DCOM so very limited processing possible by specialist devices XML based protocol, able to be processed by most IT appliances
The information provided above is for connecting two ClearSCADA 2017 R2 versions together. For earlier versions of ClearSCADA the information above should still be accurate. For connecting to non-ClearSCADA systems the information will depend on what is supported by the remote device and as such this table should not be used for that decision making