Page History

FrameworX's flexible architecture empowers a variety of deployment scenarios, making it adaptable to your unique operational needs. From compact stand-alone systems, where Our platform provides versatile deployment choices tailored to your operational requirements. Whether you require a straightforward standalone configuration with both server and client components exist in harmony on a single machine , to intricate distributed data acquisition systems that optimize communication over slower networks, the framework's scalability is truly impressive.or a sophisticated distributed system optimized for slower networks, our platform seamlessly adjusts.

Our platform is adept at managing Furthering its versatility, our platform can accommodate client and server systems, where operator client stations are executed on network computers, or even remotely over whether they are networked computers or accessed remotely via WAN or Cloud. It also enables Additionally, it facilitates distributed control systems , where multiple servers configured across different various plants allow for comprehensive, real-time control monitoring and monitoringmanagement. For mission-critical applications, redundant server systems can be deployed you have the option to deploy redundant servers with automatic failover and data synchronization capabilities, ensuring continuous operation. 

On this page:

Stand-Alone System

In a Stand-alone 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 collectorsall 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 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. As shown in the example image, the . The SCADA client can be installed on the same computer running the server or on a separate oneIt is a functional model in computer. This setup is ideal for plants with devices with serial ports or limited communication capability. In these plants, communication on slow or low bandwidth limited networks is , optimized and with a better global performance by adding I/O servers that interact with the devicesfor better performance.

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.

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.

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

• 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

A In a Distributed and Redundant Control System encompasses a server machine with , various components such as Alarm modules, a Historian, a Database, and SCADA Clients situated on are spread across different computers on the network, all connected to a central server machine.