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.
- Standalone Configuration
- Distributed Architecture
- Redundant Systems
- Cloud and Hybrid
FrameworX embodies the principle of Unified by Design: the single platform architecture approach that natively includes all required modules for real-time applications.
- Designer: solution configuration using the Four Pillars concept.
- Runtime: multi-platform runtime server for Desktop, Web, and Mobile clients
On this page:
Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps style none
FrameworX → Overview | Architecture | Technology | Operations | Editions | Differentiators
Real-Time In-Memory Database
FrameworX kernel is designed upon the concepts of Real-Time In-Memory Database and Unified Namespace.
→ Learn more about Real-Time Tag Database (Concept)
→ Learn more about Unified Namespace Architecture (Concept)
All-inclusive Philosophy
Built-in Features
All components required to deliver complete real-time applications are included on day-one.
Unified Designer: one tool, configure all modules. UI Displays, track changes.
Build once, run everywhere: .NET desktop & WebAssembly (web+mobile)
Multiplatform runtime: Windows, macOS, Linux, containers
Industrial core: Scripting (.NET C#/VB & Python 3) · Historian · Alarms · Reports · SQL
UNS-native: built-in MQTT broker & client (flat & Sparkplug B) — Local, Linked & Dynamic Tags
Open by design: OPC UA (server & client); 100+ connectors, extensibility libraries.
Secure by design: RBAC, Secrets management, Audit logging, GIT Json files, managed code
Edge-ready: store-and-forward; Edge SQL; connectors & DevOps API
AI-ready: ML Integration, MCP tools & AI documentation assistant
Hot-standby failover capable across all editions
The Four-Pillars Methodology
Born from decades of Industrial DNA experience, the Four Pillars methodology guides the reliable and efficient development of industrial grade applications.
→ Learn more about the Four Pillars (Concept)
→ Learn more about the 100+ Connectors Library
Deployment Models
FrameworX provides versatile deployment architectures tailored to your operational requirements, from standalone configurations to sophisticated distributed systems.
| Deployment Options | |
|---|---|
Standalone Configuration
| Distributed Architecture
|
Redundant Systems
| Cloud and Hybrid
|
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
| 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 |
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|