ac:layout <ac:layout-section ac:type="two_equal"> ac:layout-cell
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.
</ac:layout-cell> ac:layout-cell <ac:structured-macro ac:name="panel"> <ac:parameter ac:name="title">On this Page:</ac:parameter> ac:rich-text-body <ac:structured-macro ac:name="toc"> <ac:parameter ac:name="maxLevel">2</ac:parameter> <ac:parameter ac:name="minLevel">2</ac:parameter> </ac:structured-macro> </ac:rich-text-body> </ac:structured-macro> </ac:layout-cell> </ac:layout-section> </ac:layout>
[Insert PlatformFourPillars.png diagram here]
<table> <thead> <tr> <th>Pillar</th> <th>Purpose</th> <th>Key Components</th> <th>Implementation Order</th> </tr> </thead> <tbody> <tr> <td><strong>1. Unified Namespace</strong></td> <td>Data Foundation</td> <td>Tags, Assets, UDTs</td> <td>First - Foundation</td> </tr> <tr> <td><strong>2. Process Modules</strong></td> <td>Field Integration</td> <td>Devices, Alarms, Historian</td> <td>Second - Connect</td> </tr> <tr> <td><strong>3. Application Modules</strong></td> <td>Business Logic</td> <td>Scripts, Datasets, Reports</td> <td>Third - Process</td> </tr> <tr> <td><strong>4. User Interface</strong></td> <td>Visualization</td> <td>Displays, Dashboards, Clients</td> <td>Fourth - Present</td> </tr> </tbody> </table>
The Unified Namespace (UNS) is your solution's data foundation - a single source of truth for all real-time and configuration data.
ac:layout <ac:layout-section ac:type="three_equal"> ac:layout-cell
<h4>Tag Structure</h4> - Define naming conventions - Create tag hierarchy - Set data types and ranges - Configure engineering units </ac:layout-cell> <ac:layout-cell> <h4>Asset Tree</h4> - Mirror physical/logical structure - Organize by area/process/equipment - Create navigable hierarchy - Enable asset-based navigation </ac:layout-cell> <ac:layout-cell> <h4>User Data Types (UDTs)</h4> - Create equipment templates - Define standard objects - Build reusable components - Ensure consistency </ac:layout-cell> </ac:layout-section> </ac:layout>
[Detailed UNS Guide →]
Process modules connect your solution to the physical world, collecting data from field devices and managing industrial operations.
ac:layout <ac:layout-section ac:type="three_equal"> ac:layout-cell
<h4>Device Communications</h4> - Configure channels and protocols - Setup nodes and devices - Map points to tags - Optimize scan rates </ac:layout-cell> <ac:layout-cell> <h4>Alarm Management</h4> - Define alarm areas and groups - Configure conditions and limits - Setup notifications - Implement ISA-18.2 standards </ac:layout-cell> <ac:layout-cell> <h4>Historian</h4> - Configure data storage - Set collection rates - Define retention policies - Plan for growth </ac:layout-cell> </ac:layout-section> </ac:layout>
[Detailed Process Modules Guide →]
Application modules add business logic, data processing, and integration capabilities to transform raw data into actionable information.
ac:layout <ac:layout-section ac:type="three_equal"> ac:layout-cell
<h4>Scripts</h4> - Write calculation logic - Implement workflows - Create data validation - Automate processes </ac:layout-cell> <ac:layout-cell> <h4>Datasets</h4> - Connect to SQL databases - Create queries and views - Setup synchronization - Manage transactions </ac:layout-cell> <ac:layout-cell> <h4>Reports</h4> - Design report templates - Configure schedules - Setup distribution - Export formats (PDF/CSV/XML) </ac:layout-cell> </ac:layout-section> </ac:layout>
[Detailed Application Modules Guide →]
The UI layer presents information to operators, managers, and stakeholders through interactive displays and dashboards.
ac:layout <ac:layout-section ac:type="three_equal"> ac:layout-cell
<h4>Operational Displays</h4> - Process graphics - Control panels - Navigation structure - Alarm summaries </ac:layout-cell> <ac:layout-cell> <h4>Dashboards</h4> - KPI visualization - Analytics views - Mobile layouts - Executive summaries </ac:layout-cell> <ac:layout-cell> <h4>Client Deployment</h4> - Rich clients (.NET) - Web access (WebAssembly) - Mobile UI (Responsive) - Multi-monitor setups </ac:layout-cell> </ac:layout-section> </ac:layout>
[Detailed User Interface Guide →]
<table> <thead> <tr> <th>Benefit</th> <th>Description</th> <th>Impact</th> </tr> </thead> <tbody> <tr> <td><strong>Structured Development</strong></td> <td>Clear sequence of implementation</td> <td>50-70% reduction in rework</td> </tr> <tr> <td><strong>Scalability</strong></td> <td>Foundation supports growth</td> <td>Easy expansion without redesign</td> </tr> <tr> <td><strong>Maintainability</strong></td> <td>Organized architecture</td> <td>Simplified troubleshooting</td> </tr> <tr> <td><strong>Reusability</strong></td> <td>Template-based approach</td> <td>40% faster development</td> </tr> <tr> <td><strong>Best Practices</strong></td> <td>Industry-proven patterns</td> <td>Reliable solutions</td> </tr> </tbody> </table>
? 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
<table> <thead> <tr> <th>Template</th> <th>Description</th> <th>Components</th> <th>Time to Explore</th> </tr> </thead> <tbody> <tr> <td><strong>Basic HMI</strong></td> <td>Simple machine interface</td> <td>Displays, Modbus, TouchPanel UI</td> <td>10 min</td> </tr> <tr> <td><strong>SCADA Starter</strong></td> <td>Small SCADA system</td> <td>Alarms, trends, reports</td> <td>15 min</td> </tr> <tr> <td><strong>MES Interface</strong></td> <td>Production tracking</td> <td>Database, reports, KPIs</td> <td>20 min</td> </tr> <tr> <td><strong>IIoT & MQTT</strong></td> <td>Edge Integration</td> <td>MQTT Broker, Client, SQL</td> <td>15 min</td> </tr> <tr> <td><strong>Enterprise ProveIt!</strong></td> <td>Corporate Level</td> <td>Enterprise Unlimited, Extended UNS</td> <td>20 min</td> </tr> </tbody> </table>
[Insert DevelopmentToProduction_Flow.png here]
ac:layout <ac:layout-section ac:type="five_equal"> ac:layout-cell
<h4>1. Initiate</h4> - Requirements - Scope - Resources </ac:layout-cell> <ac:layout-cell> <h4>2. Design</h4> - Architecture - UNS design - Standards </ac:layout-cell> <ac:layout-cell> <h4>3. Build</h4> - Configuration - Testing - Integration </ac:layout-cell> <ac:layout-cell> <h4>4. Deploy</h4> - Installation - Commissioning - Training </ac:layout-cell> <ac:layout-cell> <h4>5. Support</h4> - Maintenance - Optimization - Updates </ac:layout-cell> </ac:layout-section> </ac:layout>
[Insert PlatformUIToolsInteractions.png here]
<table> <thead> <tr> <th>UI Environment</th> <th>Purpose</th> <th>Key Functions</th> </tr> </thead> <tbody> <tr> <td><strong>Solution Center</strong></td> <td>Solution Management</td> <td>• Create/open solutions<br/>• License management<br/>• Server configuration<br/>• Launch Designer and Runtime</td> </tr> <tr> <td><strong>Designer</strong></td> <td>Solution Configuration</td> <td>• UNS Configuration<br/>• Process Modules Design<br/>• Application Modules Design<br/>• Operator UI Design</td> </tr> <tr> <td><strong>Runtime</strong></td> <td>Execution Environment</td> <td>• Real-time data processing<br/>• Client connections<br/>• Module execution<br/>• Performance monitoring</td> </tr> </tbody> </table>
<table> <thead> <tr> <th>Solution Size</th> <th>Tags</th> <th>Development Time</th> <th>Team Size</th> </tr> </thead> <tbody> <tr> <td>Small</td> <td><1,000</td> <td>1-2 weeks</td> <td>1 person</td> </tr> <tr> <td>Medium</td> <td>1,000-10,000</td> <td>4-8 weeks</td> <td>2-3 people</td> </tr> <tr> <td>Large</td> <td>10,000-50,000</td> <td>3-6 months</td> <td>3-5 people</td> </tr> <tr> <td>Enterprise</td> <td>>50,000</td> <td>6-12 months</td> <td>5+ people</td> </tr> </tbody> </table>
ac:layout <ac:layout-section ac:type="two_equal"> ac:layout-cell
<h4>DO:</h4> ? Start with UNS design ? Use naming conventions ? Create UDTs first ? Test each pillar ? Document decisions ? Use version control </ac:layout-cell> <ac:layout-cell> <h4>DON'T:</h4> ? Start with displays ? Skip testing phases ? Hardcode values ? Ignore standards ? Build without UDTs ? Deploy without backup </ac:layout-cell> </ac:layout-section> </ac:layout>
This structure provides a comprehensive yet navigable guide to The Four Pillars methodology, balancing conceptual understanding with practical implementation guidance.