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:

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



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


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


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


4. Operator UI - 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

Key Architectural Benefits

BenefitDescriptionImpact
Unified DevelopmentSingle Designer for all modulesReduced learning curve
Modular DesignIndependent module operationEasier troubleshooting
Open StandardsOPC UA, MQTT, REST APIsEnterprise integration
ScalabilityFrom embedded to enterpriseInvestment protection
Platform AgnosticWindows, Linux, DockerDeployment 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: