Page History
Defines how FrameworX solutions progress from initial creation through production.
Modules → Solution Lifecycle | Tutorial | How-to Guide | Reference
Overview
The 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.
...
...
Key Concepts
- Three Workspaces: Solution Center, Designer, and Runtime form the complete environment
- Four Pillars Methodology: Structured approach for organizing Designer configuration
- Solution File (.dbsln): Single encrypted database containing all configuration
- Execution Profiles: Different runtime behaviors (Development, Validation, Production)
- Lifecycle Stages: Controlled progression from development through production
...
Workspaces
The Solution Lifecycle deployment. It encompasses three essential workspaces that work together to create, configure, and execute industrial automation solutions.
|
|
|
...
Solution Development Flow
1. Solution Center
...
- Create new solutions or open existing
- Manage licenses and resources
- Launch Designer for configuration
- Start Runtime for execution
- Monitor solution health
2. Designer Environment
...
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.
3. Runtime Environment
...
- Load configuration into memory
- Process real-time data
- Serve displays to clients
- Execute scripts and logic
- Store historian data
→ See Runtime for execution details
...
Project Development Stages
The typical automation project follows those stages:
| Panel |
|---|
Create → Develop → Validate → Deploy → Operate → Maintain |
...
| 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 |
...
Moving Between Stages
Development → Validation
...
Solution Configuration Workflow
When working in Designer, follow this proven sequence:
Define Data Model (Pillar 1)
- Create tags and naming conventions
- Build asset tree structure
- Define User-Defined Types
- Extend with TagProvider services
Connect Field Devices (Pillar 2)
- Configure communication channels
- Setup alarm conditions
- Enable historian collection
Add Business Connections and Logic (Pillar 3)
- Connect databases
- Create reports
- Write scripts
Add Security and Build Operator UI (Pillar 4)
- Design displays
- Configure security
- Setup client access
...
| Excerpt |
|---|
Solution Lifecycle LinksExplanation - to understand concepts→ Modules / Solution Lifecycle Tutorials - to learn by doing→ Tutorials / Solution Lifecycle Tutorials How-to Guides - to accomplish specific tasks→ How-to Guides / Solution Lifecycle How-to Guide Reference - technical details→ Technical Reference / Solution Lifecycle / Reference |
...
In this section...
...
...