Automation Change Coordination for Consistent Multi-Tool Data

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current automation systems face challenges in integrating heterogeneous data from different software tools due to varying protocols, standards, and information models, leading to inconsistencies and inefficiencies, with existing solutions being expensive, time-consuming, and not reproducible, and lacking system-wide consistency checks.

Innovation Solution

A method and device utilizing a common data exchange format and a change transaction manager to ensure consistent data management across multiple software tools by implementing changes locally, checking for compatibility, and synchronizing decentralized modifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a common data exchange format is implemented across multiple software tools, then data consistency and system-wide compatibility are improved, but implementation complexity and coordination overhead increase

Engineering Contradiction:

Improvedata consistencyVSAvoidimplementation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a transaction manager as an intermediary component that coordinates changes across multiple software tools. This mediator receives change requests, manages transactions, and ensures that all tools are updated consistently, thereby reducing the direct complexity of integration while maintaining data consistency through centralized coordination.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the complex integration task into manageable components: a transaction manager layer that handles coordination, individual software tools that maintain their own data models, and a common data exchange format that defines the interface. This segmentation allows each component to be developed and maintained independently while still achieving system-wide consistency.

Inventive Principle:

Principle #1Segmentation

2Reliability

If changes are implemented across multiple software tools simultaneously, then system-wide consistency is improved, but the risk of introducing errors and the cost of rollback increase

Engineering Contradiction:

Improvesystem-wide consistencyVSAvoiderror risk

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The transaction manager performs preliminary actions by validating change requests before implementation, checking compatibility across different software tools' data models. This preliminary validation prevents incompatible changes from being propagated system-wide, thereby reducing error risk while maintaining consistency for valid changes.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements transaction logging and rollback capabilities as a form of beforehand cushioning. If an error occurs during the propagation of changes across multiple tools, the system can automatically rollback to the previous consistent state, preventing permanent corruption and minimizing the impact of errors.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

3Adaptability or versatility

If decentralized data management is maintained in individual software tools, then tool independence and flexibility are improved, but data inconsistencies and integration difficulties worsen

Engineering Contradiction:

Improvetool independenceVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a universal data exchange format that can be used across different software tools with diverse data models. This format acts as a common language that allows each tool to maintain its independence and flexibility while still enabling consistent data exchange and integration, thereby achieving both tool independence and data consistency.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Difficulty of detecting and measuring

If simulation systems are used to check changes before implementation, then consistency checking capability is improved, but maintenance effort and time consumption increase

Engineering Contradiction:

Improveconsistency checking capabilityVSAvoidmaintenance time

Core Design Contradiction:

Difficulty of detecting and measuringVSLoss of time

Solution Approach 1:

The patent replaces complex simulation systems with a lighter-weight transaction manager that performs consistency checking through validation rules and data model compatibility checks. This substitution maintains the essential consistency checking capability while significantly reducing the maintenance burden and time consumption associated with full simulation environments.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentEP4641328A1Method for change management in planning and operating an automation system, computer program product and device

Publication Date: 2025.10.29 SIEMENS AG

Figure 1
Figure 2
Figure 3

AI summary

The invention relates to change management in the planning and operation of an automation system, as well as a computer program product and a device. Previously, no consent-based solutions could be verified. According to the invention, a voting process determines whether the change is consistent with the existing data. Furthermore, the solution is based on two novel approaches combined: - the introduction of an independent metamodel (from the manufacturer or technology) for exchanging models, and - the introduction of a coordination mechanism to ensure consistency for the distributed change.