Typical Deployment Scenarios
Projects powered by this framework can range from Edge applications running on embedded devices to large-scale distributed applications.
This section details some standard deployment architectures.
Stand-Alone System
In a Stand-alone System, both the server-side components (Data acquisition, Alarms, and data logging) and the client-side components (displays and client-side scripts) run on a single machine run on the same computer.
This machine could be a Windows desktop, Panel PC, industrial PC, Linux device, or an embedded system. The stand-alone system can act as a data publisher for remote platform's servers that act as Edge data collectors.
Distributed Data Acquisition System
Distributed Data Acquisition System has a server machine and device modules that run on computers dedicated to communication with PLCs or historians on remote networks that a server computer cannot reach. As shown in the example image, the SCADA client can be installed on the same computer running the server or on a separate one
It is a functional model in plants with devices with serial ports or limited communication capability. In these plants, communication on slow or low bandwidth networks is optimized and with a better global performance by adding I/O servers that interact with the devices.
Client and Server System
In a Client and Server System, a platform's server runs the server-side modules (alarm, historian, data acquisition).
Other network computers or remote computers connected by a WAN or Cloud interface execute the operator client stations.
Distributed Control System
A Distributed Control System can have multiple servers configured in a distributed architecture in different plants and for different projects. This configuration allows specific clients to access a control room for these plants or projects. Since the plant's clients will not be integrated with a single machine, it is necessary to specify which plant the users want to watch.
In this scenario, the system organization is in discrete locations controlled by local operators supported by local redundant servers. At the same time, it is possible to set a management level in a central control room to monitor all sites simultaneously. A separate cluster represents each site in the project, grouping their primary and standby servers.
Redundant Server System
The Redundant Server System presents two different computers running the platform's servers, and the redundancy is done automatically by the supervisory system itself. Thus, it is only necessary to specify the IP addresses of the primary and secondary stations.
There are a few typical deployment scenarios for redundant servers:
The Alarm and/or Historian database runs on a third machine dedicated to historical data.
The databases in the primary and secondary servers are used to store the historical data of the Alarm and/or Historian modules, with automatic data synchronization between them.
The device module (PLC communication) is also made redundant.
Devices Redundancy
3rd Machine
Distributed and Redundant Control System
A Distributed and Redundant Control System encompasses a server machine with Alarm modules, a Historian, a Database, and SCADA Clients situated on different computers on the network
Secure Edge to Cloud Interoperability
In this section...