Page History

Overview

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

Operation

Operations → Business Logic

& Data

→ 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.

The Four Pillars Overview

Image Added

Image Removed

Pillar 1

- Foundation - Unified Namespace: Tag, AssetTree, User Data Types
Pillar 2 - Industrial Operations - Process Modules: Devices, Alarms, Historian
Pillar 3 - Logic & Data Enrichment - Application Modules: Scripts, Datasets (SQL), Reports (PDF/JSON/XML(
Pillar 4 - User Interface Modules: Displays, Dashboards, Layouts. Desktop, Web and Mobile clients.

: 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.

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 →]

Pillar 2: Process Modules (Industrial Operations)

Purpose

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

What to Build

Device CommunicationsImage Added	Alarm ManagementImage Added	HistorianImage Added
Configure channels and protocols Setup nodes and devices Map points to tags 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 (Business Logic)

Purpose

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

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 (Visualization)

Purpose

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

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

Why Follow This Methodology?

Field Proven

→ Catalog

Benefits of the Four-Pillar Approach

Reduced errors and Faster solution

Benefit	Description	Impact
Structured Development	Clear sequence of implementation
50-70% reduction in rework
Scalability	Foundation supports growth	Easy expansion without redesign
Maintainability	Organized architecture	Simplified troubleshooting
Reusability	Template-based approach
40% faster development
Best Practices	Industry-proven patterns	Reliable
solutions

Common Mistakes to Avoid

Starting with displays - Without proper data structure

Skipping UDTs - Leading to tag sprawl

Direct device-to-display binding - Creating maintenance nightmares

Ignoring naming conventions - Causing confusion later

Building monolithic solutions - Instead of modular architecture

Solution Templates

Quick Start

Templates, with guided explorer

Templates

. MQTT & Publisher & Central Server
Situational Awareness,
Corporation Local & , Direct Binding to MQTT

Template	Description	Components	Time to Explore
Basic HMI	Simple machine interface	Displays
, Modbus, TouchPanel UI	10 min
SCADA Starter	Small SCADA system	Alarms, trends, reports	15 min
MES Interface	Production tracking	Database, reports, KPIs	20 min
IIoT & MQTT
Edge Integration	MQTT Broker, Client
, SQL	15 min
Enterprise ProveIt!
Corporate Level	Enterprise Unlimited,
Extended UNS
	20 min
Industry Templates
Discreet manufacturing OEE calculations Andon Dashboards	Utilities GEO Asset Monitor Distributed Systems
Continuous Process Brewery Plant High Performance HMI	Edge & IIoT Edge PLC to SQL Protocol Converter & OPC UA server

Next Steps

After Understanding the Methodology

Deep Dive Into Each Pillar

Get Hands-ON

Get Aware of the Quick Links Tables
Follow a Tutorial
Build a sample solution
Follow a tutorial
Modify a template

Quick Reference Tables

→ Four Pillars At a Glance
→ Modules Key Concepts Review
→ Development Time Estimates
→ Shorten Dev time & Increase Reliability Checklist
→ Best Practices Checklist
→ Common Pitfalls and Solutions

Development Workflow

Image Added

Solution Development Stages

Initiate	Design	Build	Deploy	Support
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 Environment	Purpose	Key Functions
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	Solution Execution	Real-time data processing Client connections	Module execution Performance monitoring

Quick Reference Tables

Four Pillars at a Glance

Four Pillars at a Glance
Pillar	Purpose	Key Components	Order
UNS	Data foundation	Tags, Assets, UDTs	First
Process	Field integration	Devices, Alarms, Historian	Second
Application	Business logic	Scripts, Datasets, Reports	Third
Interface	Visualization	Displays, Dashboards, Clients	Fourth

Modules Key Concepts Review

One Line Descriptions

Data Flow Examples

Tags (UNS)

→ Devices (Read/write values)
→ Alarms (Monitor conditions, notify and request ack, as needed)
→ Historian (store and recover time-series data)
→ Scripts (process data, implement workflows)
→ Dataset (sync with SQL databases, or recipe files)
→ Reports (pub PDF or CSV data, exchange JSON/XML data
→ Displays (Visualize)
Security Module
→ Restrict access to configuration modules and artifacts.
→ Provides Identification & Authorization for Displays client users.

Example 1: PLC to Display

PLC → Driver (Device Point) → Tag → Display

Example 2: PLC to Display, using Direct Binding.

PLC address → Dynamic TagProvider → Display

Example 3: Calculation to Database

Tags → Script (Calculation) → Result Tag → Dataset (SQL)

Example 4: User Command

Display → Button Click → Tag Write (UNS) → Device → PLC

Development Time Estimates

Solution Size	Tags	Development Time (*)	Team Size
Small	<1,000	1-2 weeks	1 person
Medium	1,000-10,000	4-8 weeks	2-3 people
Large	10,000-50,000	3-6 months	3-5 people
Enterprise	>50,000	6-12 months	5+ people

Note: Those are order of magnitude references. Specific requirements & workflow & user review process need to be accounted for.

Shorten Dev time & Increase Reliability Checklist

What to doReasonStart with UNS, not DisplaysDisplays seems easier, but without proper data structure, the total development time increases, and reliability decreases.Leverage UNS featuresLocal UNS Tags x Linked-Tags x Direct Mapping establishes the foundation for the entire solution Life-cycle Maintain Library of Classes, Symbols & Templates.Create a solution-specific reusable artifacts. Keeps consistency.Building Modular
Scalable solutionsModular architecture & solid design, prevent errors to happen, and provide core to future requirements not yet identified or raised by the end-users, avoid monolithic solution design.

Best Practices Checklist

Design Phase

Define clear naming conventions
Create reusable UDTs
Plan for 20-30% growth
Document all decisions
Review with stakeholders

Development Phase

Follow the four-pillar sequence
Test each component thoroughly
Use version control
Regular backups
Code reviews for scripts

Deployment Phase

Complete testing before production
Train all users
Document operational procedures
Establish support processes
Monitor performance

Maintenance Phase

Regular backups
Performance monitoring
Security updates
User feedback
Continuous improvement

Common Pitfalls and How to Resolve

Pitfall

Impact

How to Resolve

No naming standardConfusion, errorsDefine and enforce standards earlySkipping UDTsMaintenance nightmareCreate templates for all equipmentOver-polling devicesPerformance issuesOptimize scan rates based on needsComplex displaysOperator confusionFollow ISA-101, simplify graphicsNo documentationSupport difficultiesDocument as you buildIgnoring securityVulnerabilitiesImplement security from start

(*) About the Development Time estimates

Best Practices Checklist

DO:

DON'T:

? Start with UNS design

? Use naming conventions

? Create UDTs first

? Test each pillar

? Document decisions

? Use version control

? Start with displays

? Skip testing phases

? Hardcode values

? Ignore standards

? Build without UDTs

? 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
spaces	93DRAF

AI Assistant Data

<details> <summary>Structured Information for AI Tools</summary>

json

{
  "page": "Building Solutions",
  "type": "Methodology Guide",
  "purpose": "Explain the four-pillar solution building approach",
  "pillars": [
    {
      "name": "Unified Namespace",
      "order": 1,
      "purpose": "Data foundation",
      "components": ["Tags", "Assets", "UDTs"]
    },
    {
      "name": "Process Modules",
      "order": 2,
      "purpose": "Field integration",
      "components": ["Devices", "Alarms", "Historian"]
    },
    {
      "name": "Application Modules",
      "order": 3,
      "purpose": "Business logic",
      "components": ["Scripts", "Datasets", "Reports"]
    },
    {
      "name": "User Interface",
      "order": 4,
      "purpose": "Visualization",
      "components": ["Displays", "Dashboards", "Clients"]
    }
  ],
  "workflow": {
    "phases": ["Planning", "Development", "Deployment"],
    "duration": "1-12 months depending on size",
    "approach": "Sequential pillar implementation"
  },
  "bestPractices": [
    "Follow pillar sequence",
    "Create reusable components",
    "Document everything",
    "Test thoroughly",
    "Plan for growth"
  ]
}

</details>

Page tree

Page History

Versions Compared

Old Version 20

New Version Current

Key

On this page:

The Four Pillars Overview

Pillar 1

: Unified Namespace (Foundation)

Purpose

What to Build

Pillar 2: Process Modules (Industrial Operations)

Purpose

What to Build

Pillar 3: Application Modules (Business Logic)

Purpose

What to Build

Pillar 4: User Interface (Visualization)

Purpose

What to Build

Solution Ready to Run (Secure & Deploy)

Purpose

Why This Methodology Works

Why Follow This Methodology?

Field Proven

Benefits of the Four-Pillar Approach

Common Mistakes to Avoid

Solution Templates

Quick Start

Templates

Industry Templates

Next Steps

After Understanding the Methodology

Deep Dive Into Each Pillar

Get Hands-ON

Quick Reference Tables

Development Workflow

Image Added

Solution Development Stages

Platform UI Components

Three Essential Workspaces

Quick Reference Tables

Four Pillars at a Glance

Four Pillars at a Glance

Modules Key Concepts Review

One Line Descriptions

Data Flow Examples

Example 1: PLC to Display

Development Time Estimates

Shorten Dev time & Increase Reliability Checklist

Best Practices Checklist

Design Phase

Development Phase

Deployment Phase

Maintenance Phase

Common Pitfalls and How to Resolve

Best Practices Checklist

Next Steps

In this section...

AI Assistant Data