Overview
FrameworX 10.1 follows a modular architecture designed for industrial applications, providing a complete solution from field connectivity to enterprise integration.
Three-Tier Architecture
- Presentation Tier
- Rich Client (.NET)
- Web Client (WebAssembly)
- Mobile Client (WebAssembly)
- Application Tier
- FrameworX Runtime (TServer)
- UNS (Tag & UDT) | Field Devices | Alarms
- Historian | Reports | Dataset SQL | Scrips
- Data Tier
- Solution DB (configuration), Historian DB (Time-Series) and Alarms DB
- External SQL, Objects DB, or Cloud Storage, or custom connectors.
- Drivers (70+ field protocols), UPC-UA, MQTT + third-party extensions.
The Four Pillars Architecture
Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application:
Deployment Architectures
Standalone Configuration
- Single server with local clients
- Ideal for small to medium applications
- Simplified maintenance
Distributed Architecture
- Multiple servers across locations
- Distributed Remote I/O and UI Portal (DataHubNode & ApplicationNode)
- Enterprise-wide solutions
Redundant Systems
- Hot-standby failover
- No data loss during switchover
- Mission-critical applications
Cloud and Hybrid
- Cloud-hosted servers
- Edge devices for local processing
- Flexible scaling
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 |
Platform UI environment
UI Environment | Purpose | Key Features |
---|---|---|
SolutionCenter | Solution management and launch point |
|
Designer | Solution Configuration |
|
Runtime | Execution environment |
|