This page outlines the various FrameworX deployment scenarios.
Platform → Architecture → Solutions Development | Deployment
Deployment Scenarios: FrameworX provides versatile deployment architectures tailored to your operational requirements, from standalone configurations to sophisticated distributed systems.
Deployment Models
Deployment Options | |
---|---|
Standalone Configuration
| Distributed Architecture
|
Redundant Systems
| Cloud and Hybrid
|
Distributed Architecture
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.
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.
Benefit | Description | Impact |
---|---|---|
Unified Development | Single Designer for all modules | Reduced learning curve |
Modular Design | Independent module operation | Easier troubleshooting |
Open Standards | OPC UA, MQTT, REST APIs | Enterprise integration |
Scalability | From embedded to enterprise | Investment protection |
Platform Agnostic | Windows, Linux, Docker | Deployment flexibility |