Versions Compared

Old Version 1

changes.mady.by.user admin

Saved on

compared with

New Version Current

changes.mady.by.user admin

Saved on

Key

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

The Four-Pillar Methodology

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

Building successful FrameworX solutions follows a proven four-pillar methodology that ensures scalability, maintainability, and performance. This structured approach guides you from initial data modeling through to final deployment, with each pillar building upon the previous to create a complete industrial application.

The Four-Pillar Methodology:

Foundation → Industrial Operations → Business Logic → Visualization

Each pillar represents a critical layer of your solution, implemented in sequence for optimal results. This field-proven approach has been refined across hundreds of deployments to minimize rework and maximize reliability.

On this page:

Table of Contents
maxLevel2
minLevel2
indent10px
excludeSteps
stylenone


The Four Pillars Overview

Image Added

Panel
borderStylesolid
titleSolution Development Workflow

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

What to Build

Tag Structure Image Added

Asset TreeImage Added

User Data TypesImage Added

  • Define naming conventions
  • Create tag hierarchy
  • Set data types and ranges
  • Configure engineering units
  • Mirror physical/logical structure -
  • Organize by area/process/equipment -
  • Create navigable hierarchy -
  • Enable asset-based navigation
  • Create equipment templates
  • Define standard objects
  • Build reusable components
  • Ensure consistency

[Detailed UNS Guide →]

  • 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

    Industrial Operations)

    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

  • Configure communication channels
    • Define device nodes

    What to Build

    Device CommunicationsImage Added

    Alarm ManagementImage Added

    HistorianImage Added

    • Configure channels and protocols 
    • Setup nodes and devices
    • Map points to
    UNS
    • tags
  • Set up alarm conditions
  • Configure historian collection
    • Optimize scan rates
    • - Define alarm areas and groups
    • - Configure conditions and limits
    • - Setup notifications -
    • Implement ISA-18.2 standards
    • Configure data storage
    • Set collection rates
    • Define retention policies 
    • Plan for growth

    [Detailed Process Modules Guide →]

    Pillar 3: Application Modules (

    Store & Process

    Business Logic)

    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

    What to Build

    ScriptsImage Added

    DatasetsImage Added

    ReportsImage Added

    • Write calculation logic
    • Implement workflows
    • Create data validation
    • Automate processes
    • Connect to SQL databases 
    • Create queries and views
    • Setup synchronization
    • Manage transactions
    • Design report templates
    • Configure schedules
    • Setup distribution
    • Export formats (PDF//XML/JSON)

    [Detailed Application Modules Guide →]

    Pillar 4: User Interface (

    Analyze & Visualize

    Visualization)

    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

    Panel
    borderStylesolid

    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

    What to Build

    Operational DisplaysImage Added

    DashboardsImage Added

    Operator UI ClientsImage Added

    • Process graphics
    • Control panels
    • Navigation structure
    • Alarm summaries
    • KPI visualization
    • Analytics views
    • Mobile layouts
    • Executive summaries
    • Rich & Smart clients (.NET)
    • Web access (WebAssembly)
    • Mobile UI (Responsive)
    • Multi-monitor setup


    [Detailed Operator UI Guide →]

    Solution Ready to Run (Secure & Deploy)

    Purpose

    Solution ready to Run, validate, apply security, and deploy.

    What to Do

    RuntimeImage Added

    SecurityImage Added

    DeploymentImage Added

    • Test with Execution Profiles
    • Development Environment (Lab)
    • Validation Environment (FAT)
    • Production Environment (SAT)
    • Protect Configuration
    • Secure Scripts and IP
    • Defile Users & Roles
    • Apply on Operator UI
    • Single file deployment
    • Publish to FDA & regulated area
    • Container for Edge & Cisco Routers
    • Setup Version Control & Maintenance 

    [Detailed Solution Runtime Guide →]

    Why This Methodology Works

    Benefits of the Four-Pillar Approach

    BenefitDescriptionImpact
    Structured DevelopmentClear sequence of implementation50-70% reduction in rework
    ScalabilityFoundation supports growthEasy expansion without redesign
    MaintainabilityOrganized architectureSimplified troubleshooting
    ReusabilityTemplate-based approach40% faster development
    Best PracticesIndustry-proven patternsReliable solutions

    Common Mistakes to Avoid

    (error) Starting with displays - Without proper data structure

    (error) Skipping UDTs - Leading to tag sprawl

    (error) Direct device-to-display binding - Creating maintenance nightmares

    (error) Ignoring naming conventions - Causing confusion later

    (error) Building monolithic solutions - Instead of modular architecture


    Solution Templates

    Quick Start Templates

    TemplateDescriptionComponentsTime to Explore
    Basic HMISimple machine interfaceDisplays, Modbus, TouchPanel UI10 min
    SCADA StarterSmall SCADA systemAlarms, trends, reports15 min
    MES InterfaceProduction trackingDatabase, reports, KPIs20 min
    IIoT & MQTTEdge IntegrationMQTT Broker, Client, SQL15 min
    Enterprise ProveIt!Corporate LevelEnterprise Unlimited, Extended UNS20 min


    Development Workflow

    Image Added

    Solution Development Stages

    InitiateDesignBuildDeploySupport
    • Requirements
    • Scope
    • Resources
    • Architecture
    • UNS design
    • Standards
    • Configuration
    • Testing
    • Integration
    • Installation
    • Commissioning
    • Training
    • Maintenance
    • Optimization
    • Updates

    Platform UI Components

    Three Essential Workspaces


    Image Added


    UI EnvironmentPurposeKey Functions
    Solution CenterSolution Management
    • Create/open solutions
    • License management
    • Server configuration
    • Launch Designer and Runtime
    DesignerSolution Configuration
    • UNS Configuration
    • Process Modules Design
    • Application Modules Design
    • Operator UI Design
    Runtime

    Solution Execution

    • Real-time data processing
    • Client connections
    • Module execution
    • Performance monitoring


    Quick Reference Tables

    Development Time Estimates

    Solution SizeTagsDevelopment Time (*)Team Size
    Small<1,0001-2 weeks1 person
    Medium1,000-10,0004-8 weeks2-3 people
    Large10,000-50,0003-6 months3-5 people
    Enterprise>50,0006-12 months5+ people

    (*) About the Development Time estimates

    Best Practices Checklist

    DO:DON'T:

    ?(tick) Start with UNS design

    ?(tick) Use naming conventions

    ?(tick) Create UDTs first

    ?(tick) Test each pillar

    ?(tick) Document decisions

    ?(tick) Use version control

    ?(error) Start with displays

    ?(error) Skip testing phases

    ?(error) Hardcode values

    ?(error) Ignore standards

    ?(error) Build without UDTs

    ?(error) Deploy without backup


    Next Steps

    • Get Started: Download [Solution Templates]
    • Deep Dive: Explore each pillar's detailed guide
    • Learn More: Review [Best Practices] documentation
    • Get Help: Access [Training Resources]


    In this section...

    Page Tree
    root@parent
    spaces93DRAF

    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

  • Unified Namespace - Start with data modeling
  • Process Modules - Connect to field devices
  • Application Modules - Add business logic
    • User Interface - Create visualizations