Explanation of concepts and architecture, understanding the platform.
Start | Platform | Modules | Tutorials | How-to | Reference | Connectors | Cases | Resources
Find Topics of Interest
| Livesearch | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
→ What's FrameworX
Create, Design and Run real-time applications (SCADA, HMI, MES, IIoT). A Unified engineering environment and a consistent runtime dleliver all core modules under one project model.
→ Architecture
System architecture, deployment patterns, and performance design. Learn how FrameworX achieves millisecond response times with enterprise-grade security through its distributed runtime architecture.
→ Technology Foundation
Core technologies powering FrameworX - .NET 8, real-time databases, unified namespace, and modern UI frameworks. Understand why each technology choice matters for industrial automation
→ Security and Performance
Built on 100% managed .NET code, the platform delivers millisecond response times while maintaining defense-in-depth protection and full compliance capabilities
→ Why FrameworX
How FrameworX's unique combination of native drivers, unified architecture, and modern technology creates competitive advantages. See how these elements work synergistically to eliminate traditional SCADA limitations..
→ Product Editions
From Edge to Enterprise - understand the scalability editions that allow FrameworX to deploy from small edge devices to mission-critical distributed systems. Choose the right edition for your requirements.
Aim high, start simple, scale without limits.
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|
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
Management
- Create/open solutions
- License management
- Server configuration
- Launch Designer and Runtime
Designer
Solution
Configuration
- UNS Configuration
- Process Modules Design
- Application Modules Design
- Operator UI Design
Runtime
Execution
environment
- Real-time data processing
- Client connections
- Module execution
- Performance monitoring
The Four Pillars Methodology
Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application:
| 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. 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 | ||
|---|---|---|
|