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 Methodology
Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application:
Panel | ||||
---|---|---|---|---|
| ||||
Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application: |
Expand | ||
---|---|---|
| ||
1. Unified Namespace (UNS) - Foundation LayerThe UNS serves as the central data model for your entire solution:
|
Expand | ||
---|---|---|
| ||
2. Process Modules - Industrial Integration LayerConnect and collect data from field devices and industrial systems:
|
Expand | ||
---|---|---|
| ||
3. Application Modules - Business Logic LayerProcess and transform data for business needs:
|
Expand | ||
---|---|---|
| ||
4. Operator UI - Visualization LayerPresent information to operators and managers:
|
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
Panel | ||||
---|---|---|---|---|
| ||||
Three-Tier Architecture
|
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:
Children Display | ||
---|---|---|
|