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
Benefit | Description | Impact |
---|---|---|
Structured Development | Clear sequence of implementation | Reduced errors and rework |
Scalability | Foundation supports growth | Easy expansion without redesign |
Maintainability | Organized architecture | Simplified troubleshooting |
Reusability | Template-based approach | Faster development |
Best Practices | Industry-proven patterns | Reliable solution |
Solution Templates
Quick Start Templates, with guided explorer
Template | Description | Components | Time to Explore |
---|---|---|---|
Basic HMI | Simple machine interface | Displays. Modbus , TouchPanel UI | 10 min |
SCADA Starter | Small SCADA system | Alarms, trends | 15 min |
MES Interface | Production tracking | Database, reports, KPIs | 20 min |
IIoT & MQTT | MQTT Edge Integration | MQTT Broker, Client & Publisher & SQL | 15 min |
Central Server ProveIt! | Situational Awareness, Corporation Level | Enterprise Unlimited, Local & Extended UNS, Direct Binding to MQTT | 20 min |
Industry Templates | |
---|---|
Discreet manufacturing
| Utilities
|
Continuous Process
| Edge & IIoT
|
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 |
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) | Example 1: PLC to DisplayPLC → 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 do | Reason |
Start with UNS, not Displays | Displays seems easier, but without proper data structure, the total development time increases, and reliability decreases. |
Leverage UNS features | Local 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
| Development Phase
|
Deployment Phase
| Maintenance Phase
|
Common Pitfalls and How to Resolve | ||
---|---|---|
Pitfall | Impact | How to Resolve |
No naming standard | Confusion, errors | Define and enforce standards early |
Skipping UDTs | Maintenance nightmare | Create templates for all equipment |
Over-polling devices | Performance issues | Optimize scan rates based on needs |
Complex displays | Operator confusion | Follow ISA-101, simplify graphics |
No documentation | Support difficulties | Document as you build |
Ignoring security | Vulnerabilities | Implement 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>