You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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?

Field Proven

→ Catalog

Benefits of the Four-Pillar Approach

BenefitDescriptionImpact
Structured DevelopmentClear sequence of implementationReduced errors and rework
ScalabilityFoundation supports growthEasy expansion without redesign
MaintainabilityOrganized architectureSimplified troubleshooting
ReusabilityTemplate-based approachFaster development
Best PracticesIndustry-proven patternsReliable solution

Solution Templates

Quick Start  Templates, with guided explorer

Template

Description

Components

Time to Explore

Basic HMISimple machine interfaceDisplays. Modbus , TouchPanel UI10 min
SCADA StarterSmall SCADA systemAlarms, trends15 min
MES InterfaceProduction trackingDatabase, reports, KPIs20 min
IIoT & MQTTMQTT Edge IntegrationMQTT Broker, Client & Publisher & SQL15 min
Central Server
ProveIt!
Situational Awareness,
Corporation Level
Enterprise Unlimited, Local & Extended UNS, Direct Binding to MQTT20 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

Four Pillars at a Glance

Four Pillars at a Glance

Pillar

Purpose

Key Components

Order

UNSData foundationTags, Assets, UDTsFirst
ProcessField integrationDevices, Alarms, HistorianSecond
ApplicationBusiness logicScripts, Datasets, ReportsThird
InterfaceVisualizationDisplays, Dashboards, ClientsFourth

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,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

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 doReason
Start 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  solutions
Modular 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 early
Skipping UDTsMaintenance nightmareCreate templates for all equipment
Over-polling devicesPerformance issuesOptimize scan rates based on needs
Complex displaysOperator confusionFollow ISA-101, simplify graphics
No documentationSupport difficultiesDocument as you build
Ignoring securityVulnerabilitiesImplement security from start

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>


  • No labels