The Solution Lifecycle describes how solutions move from development through production. Three workspaces work together: Solution Center creates and manages solutions, Designer configures them, and Runtime executes them. Each stage has specific purposes - Development for building, Validation for testing, and Production for live operations.
→ Concept | How-to Guide | Reference
On this page:
Key Concepts
- Three Workspaces: Solution Center, Designer, and Runtime form the complete development environment
- Solution File (.dbsln): Single encrypted database containing all configuration
- Execution Profiles: Different runtime behaviors (Development, Validation, Production) from same configuration
- Lifecycle Stages: Development → Validation → Production deployment path
- Version Management: Controlled progression through solution versions
Understanding the Solution Lifecycle
The Solution Lifecycle defines how FrameworX solutions progress from initial creation through production deployment. It encompasses three essential workspaces that work together to create, configure, and execute industrial automation solutions.
The Three Workspaces
|
|
|
Project Lifecycle Flow
Define → Develop → Validate → Deploy → Operate → Maintain
↑ ↓
↑—————— Update/Enhance ——————— ←
evelopment Stages
Development Stage
Purpose: Create and configure the solution
- Full editing capabilities
- Local databases (SQLite)
- Simulation and test data
- Comprehensive diagnostics
- Unrestricted changes
Validation Stage
Purpose: Test and verify solution behavior
- Limited editing
- Test databases
- Real device connections
- Performance testing
- Change control begins
Production Stage
Purpose: Live operations
- Read-only configuration
- Enterprise databases
- Live equipment
- Minimal diagnostics
- Strict change control
Version Progression
Version Numbering
Solutions follow semantic versioning: Major.Minor.Build
Development Versions
- Auto-increment build numbers
- Developer annotations
- Frequent saves
- Full rollback capability
Production Versions
- Published as .dbrun files
- Release notes required
- Change documentation
- Deployment packages
Migration Path
- Development → Validation
- Build and test locally
- Export configuration
- Import to test environment
- Switch execution profile
- Validation → Production
- Complete testing sign-off
- Publish read-only version
- Deploy to production servers
- Monitor closely after go-live
Execution Profiles
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 |
Solution Management
Single File Architecture
All configuration stored in one .dbsln file:
- Tags and templates
- Device configurations
- Displays and scripts
- Security settings
- All module configurations
Benefits
- Simple deployment (one file)
- Easy backup and restore
- Version control friendly
- Consistent configuration
- No missing dependencies
Multi-User Collaboration
- Concurrent engineering on same solution
- Server-based central repository
- Granular access control
- Change tracking
- Conflict resolution
What's Next
- [Solution Center (Concept)] - Understand the management hub
- [The Four Pillars (Concept)] - Learn the development methodology
- [Solution Lifecycle (How-to Guide)] - Step-by-step lifecycle management
Complete solution management from creation through production deployment and ongoing maintenance.
In this section...