Page History

The Four Pillars Overview

Image Added

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.

What to Build

[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

[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

[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

[Detailed Operator UI Guide →]

Solution Ready to Run (Secure & Deploy)

Purpose

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

What to Do

[Detailed Solution Runtime Guide →]

Why This Methodology Works

Benefits of the Four-Pillar Approach

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

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

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

Solution Size

Tags

Development Time

Team Size

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

Key Concepts review

Understanding Module Relationships

Tags (UNS)

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

Development Workflow

Image Added

Solution Development Stages

Platform UI Components

Three Essential Workspaces

Image Added

Quick Reference Tables

Development

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

(*) About the Development Time estimates

Best Practices Checklist

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

Next Steps