DevOps and Version Control

Platform version control integration, built-in features and extensions. 

Platform → Technology → Supporting → DevOps | Concept | Reference

Version Control Architecture

The platform provides two complementary version control approaches:

Track Changes System

Every configuration change is automatically recorded in SQL tables within the solution file:

Configuration Tables Structure

The solution database contains structured tables for each module:

• Tags Tables - Tag definitions, templates, enumerations
• Device Tables - Channels, nodes, points configuration
• Alarm Tables - Items, groups, areas, conditions
• Display Tables - Pages, layouts, symbols
• Script Tables - Tasks, classes, expressions

Each table row includes metadata columns:

Change Tracking Features

• Automatic capture of all modifications
• User attribution for every change
• Timestamp precision to milliseconds
• Before/after value comparison
• Rollback capabilities

Git Integration Workflow

Export solution configuration to JSON for external version control:

Export/Import Process

1. Export to JSON - Human-readable, diff-friendly format
2. Commit to Git - Standard version control workflow
3. Branch Development - Parallel feature development
4. Merge Changes - Combine work from multiple developers
5. Import to Solution - Apply changes back to .dbsln

JSON Structure

{
  "solution": {
    "version": "10.1.0",
    "name": "PlantControl",
    "tags": [
      {
        "name": "Temperature_Tank1",
        "type": "Double",
        "initialValue": 0,
        "description": "Tank 1 temperature"
      }
    ],
    "displays": [...]
  }
}

Collaborative Development

Multi-User Capabilities

The platform supports concurrent development through:

• Server-Based Solutions - Central repository access
• Granular Locking - Module-level conflict prevention
• Real-Time Updates - See changes as they happen
• User Sessions - Track active developers

Conflict Resolution

Development Workflow Patterns

Feature Branch Workflow

main
   feature/new-tank-control
   feature/alarm-updates
   hotfix/communication-fix

1. Create feature branch from main
2. Export solution to JSON
3. Develop and test changes
4. Commit incremental updates
5. Merge back to main
6. Import merged changes

Environment Promotion

Development → Testing → Staging → Production

Each environment maintains:

• Separate solution instances
• Environment-specific execution profiles
• Controlled promotion gates
• Rollback procedures

CI/CD Integration

Automate solution deployment through standard CI/CD tools:

Build Pipeline

1. Trigger - Git commit or schedule
2. Export - Extract configuration from repository
3. Validate - Check syntax and references
4. Test - Run automated test suites
5. Package - Create deployment artifact

Deployment Pipeline

1. Backup - Save current production state
2. Deploy - Apply new configuration
3. Verify - Health checks and smoke tests
4. Monitor - Track performance metrics
5. Rollback - Restore if issues detected

Security and Compliance

Change Authorization

• Role-based access control
• Approval workflows for production
• Digital signatures for releases
• Segregation of duties

Audit Requirements

Track Changes provides compliance with:

• FDA 21 CFR Part 11 - Electronic records
• ISA-95 - Manufacturing operations
• ISO 27001 - Information security

Best Practices

Version Control

• Commit frequently with clear messages
• Use semantic versioning (major.minor.patch)
• Tag releases for production deployments
• Maintain change logs

Branching Strategy

• Protected main branch
• Feature branches for new development
• Hotfix branches for urgent fixes
• Release branches for staging

Testing Approach

• Unit tests for scripts and logic
• Integration tests for communications
• Simulation for process behavior
• User acceptance testing