This page outlines the various FrameworX deployment scenarios.

PlatformArchitecture Solutions Development | Deployment


Deployment Scenarios: FrameworX provides versatile deployment architectures tailored to your operational requirements, from standalone configurations to sophisticated distributed systems.

  • Standalone Configuration
  • Distributed Architecture 
  • Redundant Systems
  • Cloud and Hybrid


Deployment Models

Deployment Options

Standalone Configuration

  • All components on a single machine
  • Ideal for small to medium applications
  • Can serve as Edge data collector
  • Simplified maintenance

Distributed Architecture

  • Multiple servers with specialized roles:

  • DataHub Station - Field-level I/O acquisition, alarm processing, historian

  • Displays Portal - User interface serving for distributed operator groups

  • Enterprise-wide solutions with optimized network usage

Redundant Systems

  • Hot-standby failover with automatic switchover
  • No data loss during transitions
  • Synchronized historian and alarm databases
  • Mission-critical application support

Cloud and Hybrid

  • On-premise edge runtime for local control
  • Cloud services for analytics and storage
  • MQTT/HTTPS protocols for secure communication
  • Flexible scaling based on demand



Typical Deployment Scenarios

Single Server

  • Server handles all runtime functions


Stand-Alone System

  • Local client via Rich Client or remote SmartClient or Web
  • Suitable for machine operation and Edge systems.

Server and Clients System

  • Local or remote clients via Rich Client, Web Browser, or Mobile
  • Suitable for single-site or line operations

Distributed Architecture

  • Multiple servers across locations
  • DataHub Station - Field-level I/O acquisition, alarm processing, historian
  • Displays Portal - User interface serving for distributed operator groups
  • Enterprise-wide solutions with optimized network usage


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.

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. This setup features discrete locations with local operators and redundant servers for each site.


Redundant Server Configuration

  • Primary and backup servers with heartbeat monitoring
  • Automatic client reconnection on failover


Local Database with Alarm/Historian Synchronization

Remote Database Cluster



Key Architectural Benefits

BenefitDescriptionImpact
Unified DevelopmentSingle Designer for all modulesReduced learning curve
Modular DesignIndependent module operationEasier troubleshooting
Open StandardsOPC UA, MQTT, REST APIsEnterprise integration
ScalabilityFrom embedded to enterpriseInvestment protection
Platform AgnosticWindows, Linux, DockerDeployment flexibility



In this section...