Overview
FrameworX 10.1 follows a modular architecture designed for industrial applications, providing a complete solution from field connectivity to enterprise integration.
Platform UI environment
UI Environment | Purpose | Key RolesFeatures | |
---|---|---|---|
Solution Center | Solution |
|
|
Designer | Solution |
|
|
Runtime | Execution |
|
|
The Four Pillars
Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application:
Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application:
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 |
System Network Architecture
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.
Platform Components
The platform operates through three essential workspaces:
- [Platform Architecture (Concept)] - Technical foundation and component integration
- [Solution Center (Concept)] - Solution management and launch point
- [Designer Workspace (Concept)] - Configuration environment for all modules
- [Runtime Environment (Concept)] - Execution environment for deployed solutions
- [Network Topologies (Concept)] - Deployment architectures from standalone to distributed
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 |
CHILDREN PAGES: