Our platform provides versatile deployment choices tailored to your operational requirements. Whether you require a straightforward standalone configuration with both server and client components on a single machine or a sophisticated distributed system optimized for slower networks, our platform seamlessly adjusts.
Our platform is adept at managing client and server systems, whether they are networked computers or accessed remotely via WAN or Cloud. Additionally, it facilitates distributed control systems across various plants for real-time monitoring and management. For mission-critical applications, you have the option to deploy redundant servers with automatic failover and data synchronization, ensuring continuous operation.
On this page:
Typical Deployment Scenarios
Our platform supports projects ranging from Edge applications on embedded devices to large-scale distributed applications.
This section covers some standard deployment architectures.
Stand-Alone System
In a Stand-Alone System, all components run on one machine, like a Windows desktop or industrial PC, serving as both server and client. It can also act as an Edge data collector for remote platforms.
Distributed Data Acquisition System
In a Distributed Data Acquisition System, a server machine hosts device modules communicating with remote PLCs or historians. The SCADA client can be on the same server or a separate computer. This setup is ideal for plants with devices on slow or limited networks, optimized with I/O servers for better performance.
Client and Server System
In a Client and Server System, the platform's server handles server-side modules such as alarms, historians, and data acquisition.
Operator client stations run on other networked or remote computers connected via WAN or Cloud interface.
Distributed Control System
In a Distributed Control System, multiple servers are set up across different plants or projects, enabling access to control rooms for each. Users select the specific plant they wish to monitor since clients for each plant are not integrated into one machine. This setup features discrete locations with local operators and redundant servers for each site, along with a central control room for simultaneous monitoring of all sites. Each site is represented by a separate cluster comprising primary and standby servers.
Redundant Server System
The Redundant Server System comprises two separate computers running the platform's servers, with redundancy managed automatically. Simply specify the IP addresses of the primary and secondary stations. Here are some common deployment scenarios:
- The Alarm and/or Historian database is hosted on a third machine dedicated to historical data.
- Both primary and secondary servers store historical data for the Alarm and/or Historian modules, with automatic data synchronization.
- Redundancy is implemented for the device module (PLC communication).
Devices Redundancy
3rd Machine
Distributed and Redundant Control System
In a Distributed and Redundant Control System, various components such as Alarm modules, Historian, Database, and SCADA Clients are spread across different computers on the network, all connected to a central server machine.
Secure Edge to Cloud Interoperability
In this section...