ClearSCADA

compared with
Current by Adam Woodland
on Mar 19, 2019 18:19.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (6)

View Page History

|| || DNP3 || EcoStruxture Web Services (EWS) || OPC-DA || OPC-XML-DA ||
|| Environment Description | DNP3 slave running at one end, DNP3 master at the other; both components of the DNP3 driver | EWS server enabled at one end, Advanced EWS client driver at the other | OPC-DA client driver at one end, DBServer is inherently an OPC-DA server. Recommended to use the Advanced OPC driver in ClearSCADA if possible | OPC-XML-DA client driver at one end, DBServer is inherently an OPC-XML-DA server ||
|| Available Target for Data | Main server only | Any Main or Standby server | Any Main or Standby server | Any Main or Standby server ||
|| Data Addressing Method | DNP3 point address as defined in the valuemap at the slave | Database object's fullname and property | Database object's fullname and property | Database object's fullname and property ||
|| Method Calls | Yes | No | No | No ||
|| File Transfer | Yes | No | No | No ||
|| ClearSCADA Licence Requirements | Included by default in the core licence | WebX client licence currently required | OPC licence required | OPC licence required ||
|| ClearSCADA Licence Requirements | DNP3 driver included by default in the core licence | No additional licence required. See footnote ^1^ | OPC licence required | OPC licence required ||
|| Protocol Encryption | None, could use external IPSec tunnels | Use of https if configured | AES tunnel when using DBClient to tunnel, when using DCOM dependent on DCOM configuration | Use of https if configured ||
|| Database Authentication | Device based, DNP3Secure v2 supported | Connection based, defined at the server for all connecting clients | Defined at the client, using private security only | None (not supported by OPC standard) ||
|| Network Analysis Support (e.g. DPI/NIDS/NIPS) | Limited protocol support on specialist devices | XML based protocol, able to be processed by most IT appliances | Limited processing possible by specialist devices | XML based protocol, able to be processed by most IT appliances ||

{note}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 protocols and functions are supported by the remote device and as such this table should not be used for that decision making{note}
Footnote ^1^ - In ClearSCADA 2017 R3, ClearSCADA 2017 R2 and ClearSCADA 2017 from build version 7013 (~15th March 2019) onwards ensures no WebX licence is consumed. Previous versions of ClearSCADA may consume a WebX licence under certain circumstances which may stop users successfully connecting.

{note}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 should the required drivers be available. For connecting to non-ClearSCADA systems the information will depend on what protocols and functions are supported by the remote device and as such this table should not be used for that decision making{note}

{warning}The use of terms such as 'Low', 'Medium', 'High', 'Poor', 'Good' and 'Great' are subjective and should act as a guide only. Additional research, such as review of the protocol and specific system testing should occur to identify and quantify any metrics for your system design{warning}