Overview
FrameworX 10.1 follows a modular architecture designed for industrial applications, providing a complete solution from field connectivity to enterprise integration.
The Four Pillars ArchitecturePlatform 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:
|
System Architecture
Three-Tier Architecture
- Rich Client (.NET)
- Web Client (WebAssembly)
- Mobile Client (WebAssembly)
- Solution DB (configuration), Historian DB (Time-Series) and Alarms DB
- External SQL, Objects DB, or Cloud Storage, or custom connectors
- Drivers (70+ field protocols), OPC-UA, MQTT + third-party extensions
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 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
Overview
FrameworX 10.1 follows a modular architecture designed for industrial applications, providing a complete solution from field connectivity to enterprise integration.'
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
The Four Pillars Architecture
| borderStyle | solid |
|---|---|
| title | Solution Building Blocks |
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. User Interface - Visualization LayerPresent information to operators and managers:
|
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
- Create/open solutions
- License management
- Server configuration
- Launch Designer and Runtime
Designer
Solution Configuration
- Unified development interface
- Module configuration
- Display creation
- Multi-user support
Runtime
Execution environment
- Real-time data processing
- Client connections
- Module execution
- Performance monitoring
CHILDREN PAGES:
| Children Display | ||
|---|---|---|
|