Versions Compared

Old Version 18

changes.mady.by.user admin

Saved on

compared with

New Version Current

changes.mady.by.user eduardo.bogo@tatsoft.com

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

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:

Table of Contents
maxLevel2
minLevel2
indent10px
excludeSteps
stylenone

   

Overview  →  Architecture | Technology | Differentiators | Solution | Pillars | Editions

through  production using three integrated workspaces:

Key Concepts

  • Three Workspaces: Solution Center, Designer, and Runtime form the complete
development
  • 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)
from same configuration
  • Lifecycle Stages
: Development → Validation → Production deployment pathVersion Management
  • : Controlled progression from development through production


Table of Contents
maxLevel2
minLevel2
indent10px
excludeSteps
stylenone


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

Image ModifiedSolution Center

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



Image Modified Runtime

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

Designer

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

Solution Development Flow

1. Solution Center

  • Create new solutions or open existing
  • Manage licenses and resources
  • Launch Designer for configuration

Project Lifecycle Flow

  • Start Runtime for execution
  • Monitor solution health

2. Designer Environment

PillarPurposeModules
Data FoundationDefine data modelUnified Namespace, Assets, Tags, UDTs
Industrial OperationsConnect to fieldDevices, Alarms, Historian
Business OperationsProcess dataDatasets, Reports, Scripts
User InteractionPresent informationSecurity, Displays, Clients

3. Runtime Environment

  • Load configuration into memory
  • Process real-time data
  • Serve displays to clients
  • Execute scripts and logic
  • Store historian data

Project Development Stages

Panel

Create  →

Panel

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

Development 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

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

——————— ←

Each stage uses a specific execution profile that controls runtime behavior:

StageEnvironmentExecution ProfileKey Events and Characteristics 
CreateSolution Centern/a SolutionDB file created
DevelopDesignerDevelopment Profile• Full editing, simulators
• Full diagnostics and logs
ValidateDesigner / RuntimeValidation Profile• Limited editing, test modules
• Performance metrics logs
DeployRuntime / DeployProduction Profile• Live equipment
• Minimal overhead
MaintainDesigner / RuntimeAccording to task

• Designer DevOps & Track Changes tools
• Runtime Diagnostics and Hot reload tools

Execution Profile Concept

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

Moving Between Stages

Development → Validation

  1. Complete initial configuration in Designer
  2. Test locally with Development profile
  3. Export solution configuration
  4. Import to validation environment
  5. Switch to Validation profile
  6. Begin formal testing

Validation → Production

  1. Complete all testing
  2. Obtain sign-offs
  3. Publish read-only version
  4. Deploy to production servers
  5. Switch to Production profile
  6. Monitor go-live closely

Solution Configuration Workflow

  1. Define Data Model (Pillar 1)

    • Create tags and naming conventions
    • Build asset tree structure
    • Define User-Defined Types
    • Extend with TagProvider services

  2. Connect Field Devices (Pillar 2)

    • Configure communication channels
    • Setup alarm conditions
    • Enable historian collection

  3. Add Business Connections and Logic (Pillar 3)

    • Connect databases
    • Create reports
    • Write scripts

  4. Add Security and Build  Operator UI (Pillar 4)

    • Design displays
    • Configure security
    • Setup client access

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

Version Control Integration

  • Track Changes: Built-in change tracking
  • Build & Backup: Create restore points
  • Publish: Lock versions for production
  • External VCS: Git/SVN integration

Best Practices Checklist

Development Guidelines

  • Follow the Four Pillars sequence
  • Test at each pillar completion
  • Use templates for consistency
  • Document configuration decisions

Progression Rules

  • Never skip validation stage
  • Always test rollback procedures
  • Maintain separate environments
  • Use appropriate execution profiles

Change Management

  • Track all modifications
  • Require approval for production
  • Test changes in development first
  • Document emergency procedures
Excerpt

Explanation - 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...

Page Treeroot@parentspaces93DRAF