Versions Compared

Old Version 16

changes.mady.by.user admin

Saved on

compared with

New Version 17

changes.mady.by.user admin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

FrameworX 10.1 follows a modular architecture designed for industrial applications, providing a complete solution from field connectivity to enterprise integration.


Panel
borderStylesolid
titleSystem 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.


The Four Pillars Architecture

Panel
borderStylesolid
titleSolution Building Blocks

Every FrameworX solution is built on four foundational pillars that work together to create a complete industrial application:



Expand
title1. Unified Namespace (UNS) - Foundation Layer

1. Unified Namespace (UNS) - Foundation Layer

The UNS serves as the central data model for your entire solution:

  • Tags - Real-time data points with types, scaling, and properties
  • Asset Tree - Hierarchical organization of your plant/process
  • User Data Types (UDTs) - Reusable templates for complex objects
  • TagProviders - External data source connections


Expand
title2. Process Modules - Industrial Integration Layer

2. Process Modules - Industrial Integration Layer

Connect and collect data from field devices and industrial systems:

  • Devices - 70+ native drivers for PLCs, RTUs, and field devices
  • Alarms - Event detection, notification, and audit trail
  • Historians - Time-series data storage and retrieval


Expand
title3. Application Modules - Business Logic Layer

3. Application Modules - Business Logic Layer

Process and transform data for business needs:

  • Scripts - Custom logic in C#, VB.NET, Python, JavaScript
  • Datasets - SQL database connections and queries
  • Reports - Document generation and data export


Expand
title4. User Interface - Visualization Layer

4. User Interface - Visualization Layer

Present information to operators and managers:

  • Displays - HMI/SCADA screens with rich graphics
  • Dashboards - KPI monitoring and analytics
  • Clients - Rich (.NET), Web (HTML5), and Mobile applications


Deployment Architectures

Unified Designer

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