Defines how FrameworX solutions progress from initial creation through production.

Platform → Architecture | Technology  | Solution | Pillars | FrameworX |  Editions 

Solution Lifecycle → Concept | How-to Guide | Reference



Overview

   The Solution Lifecycle describes how solutions move from development through production. Three workspaces work together:

→ Solution Center creates and manages solutions.
→ Designer configures the solution.
→ Runtime executes the solution.

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

Workspaces

The Solution Lifecycle  deployment. It encompasses three essential workspaces that work together to create, configure, and execute industrial automation solutions.

Solution Center

  • Entry point for all operations
  • Solution management hub
  • License control center
  • Launch point for Designer ↓ and Runtime →



Runtime

  • Execution environment
  • Real-time operations
  • Client services
  • Performance monitoring

Designer

  • Configuration workspace
  • Module development
  • Build and validation
  • Launch point for Runtime →


Development Stages

Define → Develop → Validate → Deploy → Operate → Maintain
                     ↑                                                                         ↓
                     ↑——————  Update/Enhance ——————— ←

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

Progression

  1. Development → Validation
    • Build and test locally
    • Export configuration
    • Import to test environment
    • Switch execution profile
  2. 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:

AspectDevelopmentValidationProduction
DatabasesLocal SQLiteTest SQL ServerEnterprise SQL
SecurityMinimalTest credentialsFull authentication
DiagnosticsFull loggingPerformance metricsMinimal overhead
Data SourcesSimulatorsTest devicesLive equipment
ChangesOnline editsRestrictedProtected

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

In this section...