DCS Version Management With Conflict Detection and Merge Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current version management systems for Distributed Control Systems (DCSs) lack integrated version management, conflict detection, and merging capabilities, leading to complexity, errors, and increased costs, which can result in system downtime and reduced user adoption.

Innovation Solution

A method and system for version management in DCSs that retrieves source files and their versions from a data repository and model services, allowing for execution of operations based on user inputs, and manages versions by tracking changes, merging changes, and resolving conflicts, thereby providing a centralized repository for efficient collaboration and data management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual version management is used in DCS, then system complexity is reduced, but version tracking accuracy and conflict detection capability deteriorate

Engineering Contradiction:
Improvesystem complexityVSAvoidversion tracking accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent introduces an intermediary version management system that acts as a mediator between multiple engineering teams and the DCS configuration data. This intermediary automatically tracks versions, detects conflicts, and manages merges, providing accurate version control without requiring complex manual processes from the engineering teams.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The version management system performs self-service by automatically detecting conflicts, tracking version changes, and managing configuration data without requiring manual intervention from engineers. The system autonomously maintains version accuracy while keeping the overall process simple for users.

Inventive Principle:
Principle #25Self-service

2Measurement precision

If integrated version management with conflict detection is implemented, then version tracking accuracy improves, but device complexity increases

Engineering Contradiction:
Improveversion tracking accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system creates and manages copies of configuration data packages for different versions and engineering teams. By working with copies rather than the master configuration, the system achieves accurate version tracking while keeping the core DCS system simple and unchanged.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The version management system segments configuration data into separate manageable packages that can be independently versioned, tracked, and merged. This segmentation allows accurate version control of individual components without increasing the complexity of the entire DCS system.

Inventive Principle:
Principle #1Segmentation

3Productivity

If multiple engineering teams work simultaneously on DCS configuration, then productivity increases, but conflict frequency and error rate increase

Engineering Contradiction:
Improveengineering productivityVSAvoidconfiguration error rate
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The version management system provides continuous feedback to engineering teams about configuration conflicts, version status, and merge states. This feedback mechanism allows multiple teams to work simultaneously while automatically detecting and managing conflicts, maintaining both high productivity and configuration reliability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system acts as an intermediary that coordinates between multiple engineering teams, automatically detecting conflicts before they become errors and managing the integration of changes from different teams. This mediation enables simultaneous work while preventing configuration errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of information

If add-on version management systems are used, then version tracking capability is provided, but ease of operation deteriorates due to setup and configuration complexity

Engineering Contradiction:
Improveversion information trackingVSAvoidsystem setup ease
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The version management functionality is merged directly into the DCS configuration environment, eliminating the need for separate add-on systems. This integration provides comprehensive version tracking while simplifying operation by unifying the interface and reducing setup complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The version management system is designed to be universal and multi-functional, handling version tracking, conflict detection, merge management, and auditing within a single integrated platform. This universality eliminates the need for multiple separate tools and simplifies the overall system operation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS20240403039A1Method and System for Version Management in Distributed Control Systems (DCS)
Publication Date: 2024.12.05 ABB (SCHWEIZ) AG
  • US20240403039A1 patent drawing
  • US20240403039A1 patent drawing
  • US20240403039A1 patent drawing

AI summary

A method of version management for Distributed Control Systems (DCSs) includes retrieving source files related to objects corresponding to a function of a device of a DCS from a data repository associated with the DCS, based on receiving a request from users associated with the DCS; retrieving versions of the source files, from model services corresponding to the source files; and executing operations for the device of the DCS based on user inputs. The operations are executed based on the source files from the data repository and the versions from the one or more model services, and managing the versions of the source files based on execution of the operations.