Defines how FrameworX solutions progress from initial creation through production.
Platform → Architecture → Solution Lifecycle | Concept | How-to Guide | ReferenceSolutions Development | Deployment
The FrameworX manages the complete Solution Lifecycle describes how solutions move , from development through production using three integrated workspaces:
→ Solution Center - Creates and manages solutions configuration files.
→ Designer - Configures solutions using the Four Pillars Methodology.
→ Runtime - Executes the solution configuration in real-time.
Overview Table of Contents maxLevel 2 minLevel 2 indent 10px exclude Steps style none
The Solution Lifecycle deployment. It encompasses three essential workspaces that work together to create, configure, and execute industrial automation solutions.
Solution Center
|
|
Runtime
| |
Designer
|
Purpose: Solution creation and management
Purpose: Solution configuration workspace
Configuration follows the Four Pillars Methodology:
Pillar | Purpose | Modules |
---|---|---|
Data Foundation | Define data model | Unified Namespace, Assets, Tags, UDTs |
Industrial Operations | Connect to field | Devices, Alarms, Historian |
Business Operations | Process data | Datasets, Reports, Scripts |
User Interaction | Present information | Security, Displays, Clients |
→ See Four Pillars Methodology for detailed explanation on Methodology and Modules.
→ See Designer Workspace for explanation of the configuration user interface.
Purpose: Execute configured solutions
→ See Runtime for execution details
The typical automation project follows those stages:
Panel |
---|
Create → Develop → Validate → Deploy → Operate → Maintain |
• Designer DevOps & Track Changes tools
• Runtime Diagnostics and Hot reload tools
Execution profiles allow the same solution configuration to behave differently based on environment:
Aspect | Development | Validation | Production |
---|---|---|---|
Databases | Local SQLite | Test SQL Server | Enterprise SQL |
Security | Minimal | Test credentials | Full authentication |
Diagnostics | Full logging | Performance metrics | Minimal overhead |
Data Sources | Simulators | Test devices | Live equipment |
Changes | Online edits | Restricted | Protected |
→ See Runtime Execution Profiles for detailed information
When working in Designer, follow this proven sequence:
Define Data Model (Pillar 1)
Connect Field Devices (Pillar 2)
Add Business Connections and Logic (Pillar 3)
Add Security and Build Operator UI (Pillar 4)
All configuration stored in one .dbsln file:
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page Tree | ||||
---|---|---|---|---|
|