Versions Compared

Old Version 5

changes.mady.by.user Support

Saved on

compared with

New Version Current

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

Easy Heading MacroheadingIndent40navigationTitle

On this page:

selector

Table of Contents

h2,h3

maxLevel

wrapNavigationText

3

true

stylenone



navigationExpandOptiondisable-expand-collapse

This page presents typical deployment scenario for your applications.

Typical Deployment Scenarios

Projects powered by this framework can range Our platform supports projects ranging from Edge applications running on embedded devices to large-scale distributed applications. 

This section illustrates covers some typical standard deployment architectures. 

<<<<. Review Add EdgeHMI Edge, EdgeGateway, SecureGateway, and IIoT scenarios, broker. HMI Panels Routers >>>>




Stand-Alone System

In a Stand-

alone

Alone System,

the server-side components (Data acquisition, Alarms, and data logging) and the client-side components (displays and client-side scripts) run on the same computer.The computer can be a Windows desktop, Panel PC, industrial PC, Linux device, or embedded system. The stand-alone system can act as a data publisher for remote platform's servers that act as Edge data collectors

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.


Image Modified



Distributed Data Acquisition System

In a Distributed Data Acquisition System

has

, a server machine

and

hosts device modules

that run on computers dedicated to communication with

communicating with remote PLCs or historians

on remote networks that a server computer cannot reach. In the example image, the

. The SCADA client can be

placed

on the same

computer that is running the

server

computer

or

in

a

remote 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

separate computer. This setup is ideal for plants with devices on slow or limited networks, optimized with I/O servers for better performance.


 

Image Modified



Client and Server System

In a Client and Server System,

a

the platform's server

runs the

handles server-side modules

(alarm, historian,

such as alarms, historians, and data acquisition

)

.

Other network computers

Operator client stations run on other networked or remote computers connected

by a

via WAN or Cloud interface

execute the operator client stations

.



Image Modified



Distributed Control System

A

In a Distributed Control System

can have

, multiple servers

configured in a distributed architecture in

are set up across 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

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.

Image Modified




Redundant Server System

The Redundant Server System

presents

comprises two

different

separate computers running the platform's servers,

and the

with redundancy

is done automatically by the supervisory system itself. Thus, it is only necessary to

managed automatically. Simply specify the IP addresses of the primary and secondary stations.

There are a few typical

Here are some common deployment scenarios

for redundant servers

:

  • The Alarm and/or Historian database
runs
  • is hosted on a third machine dedicated to historical data.
The databases in the
  • Both primary and secondary servers
are used to
  • store
the
  • historical data
of
  • for the Alarm and/or Historian modules, with automatic data synchronization
between them
  • .
The
  • Redundancy is implemented for the device module (PLC communication)
is also made redundant
  • .

Devices Redundancy

Image Modified

3rd Machine

Image Modified



Distributed and Redundant Control System

A

In a Distributed and Redundant Control System

includes a server machine with

, various components such as Alarm modules,

a

Historian,

a

Database, and SCADA Clients

located on

are spread across different computers on the network, all connected to a central server machine.

Image Modified



Secure Edge to Cloud Interoperability

Image Added



In this section...

Page Tree
root@parent
spacesV10