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 Operations → Business Logic → 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
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
Tag Structure | Asset Tree | User Data Types |
|---|---|---|
|
|
|
[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 Communications | Alarm Management | Historian |
|---|---|---|
|
|
|
[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
Scripts | Datasets | Reports |
|---|---|---|
|
|
|
[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 Displays | Dashboards | Operator UI Clients |
|---|---|---|
|
|
|
[Detailed Operator UI Guide →]
Solution Ready to Run (Secure & Deploy)
Purpose
Solution ready to Run, validate, apply security, and deploy.
What to Do
Runtime | Security | Deployment |
|---|---|---|
|
|
|
[Detailed Solution Runtime Guide →]
Why This Methodology Works
Benefits of the Four-Pillar Approach
| 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
| 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 |
Development Workflow
Solution Development Stages
| Initiate | Design | Build | Deploy | Support |
|---|---|---|---|---|
|
|
|
|
|
Platform UI Components
Three Essential Workspaces
| UI Environment | Purpose | Key Functions | |
|---|---|---|---|
| Solution Center | Solution Management |
|
|
| Designer | Solution Configuration |
|
|
| Runtime | Solution Execution |
|
|
Quick Reference Tables
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 |
(*) About the Development Time estimates
Best Practices Checklist
| DO: | DON'T: |
|---|---|
? ? ? ? ? ? | ? ? ? ? ? ? |
Start with UNS designNext 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...