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 → Logic & Data → Visualization

Each pillar represents a critical layer of your solution, implemented in sequence for optimal results:

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.

Why Follow This Methodology?

Benefits of the Four-Pillar Approach

Common Mistakes to Avoid

• Starting with displays - Without proper data structure

• Skipping UDTs - Leading to tag sprawl

• Not leveraging UNS features - Local UNS Tags x Linked-Tags x Direct Mapping  

• Ignoring naming conventions - Causing confusion later

• Building monolithic solutions - Instead of modular architecture

Solution Templates

Quick Start Templates

Industry Templates

To Do: Priorize and Implement 

Manufacturing Template

• Production tracking
• OEE calculations
• Downtime analysis
• Quality management
• Inventory tracking

Utilities Template

• SCADA infrastructure
• Telemetry systems
• Regulatory reporting
• Load management
• Outage management

Building Automation

• HVAC control
• Lighting management
• Energy monitoring
• Access control
• Tenant billing

Explore All Templates →

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

Next Steps

After Understanding the Methodology

1. Deep Dive into Each Pillar
   • Unified Namespace Details
   • Process Modules Guide
   • Application Modules Guide
   • User Interface Guide
2. Explore Examples
   • Solution Examples
   • Industry Templates
   • Architecture Patterns
3. Get Hands-On
   • Build a sample solution
   • Follow a tutorial
   • Modify a template

Quick Reference

Four Pillars at a Glance

Time Estimates

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

Common Pitfalls and Solutions

Key Concepts review

Understanding Module Relationships

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.

Data Flow Examples

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

Solution Templates

Quick Start Templates

Industry Templates

Manufacturing Template

• Production tracking
• OEE calculations
• Downtime analysis
• Quality management
• Inventory tracking

Utilities Template

• SCADA infrastructure
• Telemetry systems
• Regulatory reporting
• Load management
• Outage management

Building Automation

• HVAC control
• Lighting management
• Energy monitoring
• Access control
• Tenant billing

Explore All Templates →

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 Solutions

Next Steps

After Understanding the Methodology

1. Deep Dive into Each Pillar
   • Unified Namespace Details
   • Process Modules Guide
   • Application Modules Guide
   • User Interface Guide
2. Explore Examples
   • Solution Examples
   • Industry Templates
   • Architecture Patterns
3. Get Hands-On
   • Build a sample solution
   • Follow a tutorial
   • Modify a template

Quick Reference

Four Pillars at a Glance

Time Estimates

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

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>

Claude can make mistakes.
Please double-check responses.

Quick Start Templates

Next Steps

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