Defines how FrameworX solutions progress from initial creation through production.

Platform → Solution Lifecycle | Concept | How-to Guide | Reference

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

Purpose: Solution creation and management

• Create new solutions or open existing
• Manage licenses and resources
• Launch Designer for configuration
• Start Runtime for execution
• Monitor solution health

2. Designer Environment

Purpose: Solution configuration workspace

Configuration follows the Four Pillars Methodology:

→ See Four Pillars Methodology for detailed explanation on Methodology and Modules.

→ See Designer Workspace for explanation of the configuration user interface.

3. Runtime Environment

Purpose: Execute configured solutions

• 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:

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

Execution Profile Concept

Execution profiles allow the same solution configuration to behave differently based on environment:

→ See Runtime Execution Profiles for detailed information

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

When working in Designer, follow this proven sequence:

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

In this section...