15. Connectivity (process connectivity)

The SCADA system supports connectivity to common types of automation equipment. In addition to the cyclical queries from controls (PLC) the system is also capable of event-oriented communication both on this level and with remote terminal units (RTU).

Depending on the communication protocol it is possible to use the periphery timestamp (real-time) from external sources or automatically assign such upon arrival in the system. Quality information (invalid, from general inquiry, etc.) can also be transferred and integrated in the status word of the SCADA related value.

15.1. Drivers

Linkup over various Ethernet variants or general driver interfaces is supported. Amongst other drivers for the following interfaces are included:

• Siemens Industrial Ethernet for S7
• Logo 8
• Ethernet / IP
• Rockwell Ethernet
• S-Bus (SAIA)
• SINAUT
• IEC 60870-5-104
• IEC 60870-5-101
• IEC 61850 Client
• IE 61840 (MMS)
• IEC 61400 (MMS)
• DNP3
• BACnet
• Modbus TCP native
• Modbus Server
• Modbus Client
• Serial: Simatic MPI, 3964R, RK512, ...
• Omron-Fins
• OPC Data Access Client & Server
• OPC Alarms&Events Client & Server
• OPC UA Data Access Client & Server
• OPC UA Alarms&Conditions Client & Server
• OPC UA Historical Access Client & Server
• ProfiNET
• ProfiSAFE
• Simulator
• Sinumerik powerline
• SSI
• TLS (Technical Terms of Delivery for Remote Monitoring Stations) Client & Server
• NTCIP

Additional drivers can be included and/or independently developed over an API upon request.

15.2. Interfaces

Openness and provision of international standardized interfaces represent a major factor regarding security of investment. The system has all major communication and database interfaces (depending on the OS) in addition to those stated under Process Connectivity:

Parameterization interfaces

ASCII import / export

XML-import / export

Database interfaces

OLE-DB

ADO / ODBC / Unix ODBC

SOAP

Programming interfaces

DLL API (extension of the CONTROL language scope)

API (C++ library for creating proprietary manager modules)

COM

ActiveX

XML

JSON

Communication

TCP/IP, SSL/TLS

OPC UA server/client

HTTP / HTTPS

SMTP / POP3

RS232 / V24

SMS / GSM / UCP / TAP

DDE

XML-RPC

JSON REST

Web Sockets

Network monitoring

SNMP Manager

SNMP Agent

Customer specific interfaces can be both integrated and/or developed addressing customer request.

15.3. Native support of redundant PLC and networks

The S7 driver is a native driver for peripheral connections to the Siemens S7 PLC. The driver can communicate with S7-300, S7-400, S7-1200, and S7-1500 series. The native S7 driver can be used under Windows and Linux for:

• Sending of data to the PLC
• Querying of data from the PLC
• Receipt of spontaneous data from the PLC. To receive spontaneous data from the PLC, TSPP (Time Stamped Push Protocol) extension can be used for cyclical services on S7-300 and S7-400.
• Enhanced Support of TSPP for S7 1200 and S7 1500
• Cyclic services (Poll rates and polling groups) are directly set by system via configuration
• Receiving and acknowledging of S7 alarms

Connection of peripherals (the device and the connections can be configured redundantly) using the specific S7 data transfer protocol (S7-300 and S7-400 series) for communication can be established using the native S7 driver. The use of the S7 driver is the simplest way to connect to a Siemens peripheral without long engineering times. Addressing follows protocol specific notation and use of symbolic addresses during parameterization of peripheral equipment addresses is supported.

An optimized driver for the new generation of Siemens PLC (S7-1200 / S7-1500) is available for optimized communication with Siemens peripherical devices and supports the new PLC notation. Beside that the new driver also supports the new symbols used in recent devices and PLCs. More efficient engineering and optimized communication are ensured through optimization for Siemens equipment. Complete end-to-end encryption of data between the PLC and the SCADA system is ensured. The driver supports not only querying of the notation but also of the PLC based alarms and online browsing including the search for data points on the PLC.

This driver should also be capable to run redundant S7-1500 H PLC, as the redundancy is not handled by SCADA system, but via a SIEMENS component before transmission of information. SCADA system still handles the redundant pair of PLCs as one device in the field.

15.4. TIA Importer

A tool for integrating existing TIA project data into the SCADA system is available. Additionally, it is possible to integrate exports from the TIA portal and hence to work in both systems using the same notation. Using the provided tool data points and their notation can be accessed and correspondingly imported and administered. These options are available for TIA V14, V15 and V16 projects. This enables particularly efficient integration of S7-1200 and S7-1500 as well as existing and new TIA based projects.

In Addition, exports from TIA Portal must be available and the integration shall allow to use the same symbols in both systems.

15.5. BACnet support and certificate

The system supports BACnet (EN ISO 16484-5) and directs connectivity to libraries and objects. Additionally, BACnet data such as BIBBS or PICS are provided, and an EDE based data interface supported. The BACnet interface has a standard-compliant certification. The solution should provide a certificate regarding BACnet compliance. At least this should be guaranteed for level B-OWS.

The chosen BACnet solution provides an integrated BACnet-compliant online/offline engineering solution for building automation technology, including object library. Adding this technology allows the use of BACnet driver, diagnostics and an included BACnet engineering environment. The engineering environment consists of BACnet object library (including face plates), BACnet browser, EDE tool and EDE file interface.

BACNet objects are dedicated to be used with BACNet Driver. They can be added and enlarged by activating BACNet packs or add them on individual base.

The BACnet driver must feature the Advanced Workstation (AWS) level.

15.6. MQTT driver

MQTT (Message Queuing Telemetry Transport) is a message protocol based on TCP/IP and intended for communication in networks with limited bandwidth. The system must represent an MQTT client, which can be either publisher or subscriber, and enable the connection to MQTT brokers. The MQTT driver must support redundant connections and be able to connect to any number of brokers.

15.7. Support of other servers and terminals

The following servers and terminals are supported by the solution and can be correspondingly integrated:

• SIMATIC Information Server
• TeleControl Server Basic
• SIMATIC Industrial Thin Client (ITC) in latest version ITCv3

15.8. Support of Rockwell PLCs

Due to an integrated driver to run Rockwell PLCs, the following equipment should be supported by the solution:

• ControlLogix
• CompactLogix
• FlexLogix
• MicroLogix
• SLC5
• PLC5

15.9. Cloud connectivity

The software can establish a native connection to an industrial cloud. Transfer speeds to the cloud of up to 20,000 values per 10 seconds must be ensured.

Connections should be possible to SIEMENS MindSphere© including services and apps available there.

Furthermore it shall be possible to connect to other cloud providers and to integrate them to the solution (e.g. Microsoft Azure or AWS)

There shall be an integrated driver for MQTT. This allows to connect to cloud services and enables possibilities to create M2M solutions. More than that this builds a basement for connections with small bandwidths.