The Four-Pillar Methodology

Building a FrameworX solution follows a logical progression through four integrated pillars. Each pillar builds upon the previous, creating a complete industrial application.

Foundation → Integration → Logic → Visualization

Start with data modeling, connect to field devices, add business logic, then create user interfaces.


Pillar 1: Unified Namespace (Foundation)

Purpose

The Unified Namespace (UNS) is your solution's data foundation - a single source of truth for all real-time and configuration data.

Key Components

Component

Description

Common Uses

Tags

Real-time data variables

Process values, setpoints, calculations

Asset Tree

Hierarchical data organization

Plant structure, equipment groups

User Data Types

Reusable data templates

Motor, valve, PID loop templates

TagProviders

External data connections

OPC servers, databases, cloud services

Best Practices

  • Design your tag structure before connecting devices
  • Use consistent naming conventions
  • Create UDTs for repeated equipment types
  • Organize assets to match your process

Pillar 2: Process Modules (Connect & Collect)

Purpose

Process modules connect your solution to the physical world, collecting data from field devices and managing industrial operations.

Core Modules

Module

Function

Typical Configuration

Devices

Field communication

Channels → Nodes → Points mapping

Alarms

Event management

Areas → Groups → Items → Notifications

Historian

Time-series storage

Storage locations → Tables → Tag mapping

Integration Flow

  1. Configure communication channels
  2. Define device nodes
  3. Map points to UNS tags
  4. Set up alarm conditions
  5. Configure historian collection

Pillar 3: Application Modules (Store & Process)

Purpose

Application modules add business logic, data processing, and integration capabilities to transform raw data into actionable information.

Module Capabilities

Module

Primary Use

Key Features

Scripts

Custom logic and automation

Tasks, classes, expressions, multi-language

Datasets

Database integration

SQL queries, stored procedures, real-time sync

Reports

Data exchange and documentation

PDF generation, Excel export, scheduled delivery

Common Implementations

  • Production calculations and KPIs
  • Database logging and retrieval
  • Shift reports and batch records
  • Integration with ERP/MES systems

Pillar 4: User Interface (Analyze & Visualize)

Purpose

The UI layer presents information to operators, managers, and other stakeholders through interactive displays and dashboards.

Visualization Options

Type

Target Users

Deployment

Displays

Operators, Engineers

Control rooms, plant floor

Dashboards

Managers, Analysts

Offices, meeting rooms

Mobile Apps

Field technicians, Supervisors

Tablets, smartphones

Client Technologies

  • Rich Clients - Full-featured .NET applications
  • Web Clients - HTML5 browser-based access
  • Mobile Clients - iOS and Android apps

Module Dependencies and Interactions

Understanding module relationships helps build robust solutions:

  • Tags are used by all other modules
  • Devices populate tag values
  • Alarms monitor tag conditions
  • Historians record tag changes
  • Scripts manipulate tag values
  • Displays visualize tag data


Solution Building Checklist

Foundation Phase

% Define tag naming standards
% Create Asset Tree structure
% Build User Data Types
% Configure TagProviders

Integration Phase

% Set up device communications
% Map device points to tags
% Configure alarm areas and groups
% Set up historian storage

Logic Phase

% Create calculation scripts
% Configure database connections
% Build report templates
% Test data flows

Visualization Phase

% Design operator displays
% Create management dashboards
% Configure navigation
% Deploy clients

Quick Start Templates

Template

Includes

Best For

Basic HMI

Tags, Displays, Navigation

Simple machine control

SCADA System

Devices, Alarms, Historian, Displays

Process monitoring

MES Integration

Datasets, Scripts, Reports, Dashboards

Production tracking

IIoT Gateway

MQTT, TagProviders, Cloud connectivity

Edge computing



Next Steps