Automation Device Edit Sessions for Conflict-Free Multiuser Commissioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing building automation systems lack a managed multiuser support mechanism during engineering or commissioning, leading to redundant data storage and potential conflicts when multiple engineers work on the same device, resulting in invalid configurations due to the 'last wins' principle.
Innovation Solution
A method and tool that allow only one user to lock an automation device for editing, providing real-time lock status visibility and ensuring data accuracy, with automatic unlocking after a timeout or connection loss, enabling parallel work by multiple engineers while maintaining data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple engineers work in parallel on the same automation device without locking mechanism, then productivity is improved through parallel work, but data consistency deteriorates due to the 'last wins' principle causing invalid configurations
Solution Approach 1:
The patent introduces a locking mechanism as an intermediary between multiple engineers and the automation device. When an engineer starts an edit session, they acquire a lock on the device, preventing other engineers from making conflicting changes. This mediator (lock) ensures that only one engineer can modify the device configuration at a time, thereby maintaining data consistency while still allowing parallel work on different devices.
2Reliability
If a locking mechanism is implemented to prevent parallel editing, then data consistency is improved, but productivity deteriorates due to reduced accessibility of the automation device
Solution Approach 1:
The locking mechanism is designed to be dynamic rather than static. The lock is automatically released after a timeout period if the edit session is not properly closed, or when the engineering tool is disconnected. This dynamic behavior ensures that the device becomes accessible again after a reasonable period, preventing permanent blocking while still protecting against concurrent edits during active sessions.
3Manufacturing precision
If the automation device is locked during edit session, then data accuracy is improved by preventing concurrent modifications, but device availability deteriorates as the device cannot be accessed by other users
Solution Approach 1:
The locking mechanism applies the restriction locally to the specific automation device being edited, rather than globally to all devices. Other automation devices remain fully accessible to other engineers, allowing parallel work on different devices. This localized approach minimizes the impact on overall system availability while ensuring configuration accuracy for the specific device under edit.
4Reliability
If manual locking by authorized user is required, then data integrity is improved through controlled access, but ease of operation deteriorates due to additional coordination overhead
Solution Approach 1:
The system provides self-service locking functionality where the lock is automatically acquired when an engineer starts an edit session and automatically released when the session ends or times out. This eliminates the need for manual coordination between engineers, as the system automatically manages the locking and unlocking process based on session state, reducing coordination overhead while maintaining data integrity.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
A method and a tool (e.g. engineering or commissioning tool) for controlling access to an automation device, especially a building automation device, for engineering and/or commissioning the automation device, wherein only one user is allowed to lock the automation device for engineering and/or commissioning by starting an edit session; wherein the automation device stays running and accessible in an online modus during the edit session; wherein other users can see the device lock status of the active edit session and see the last engineering or commissioning action of the automation device in the runtime system; wherein no other users are able to lock the already locked automation device to start a further edit session; and wherein only the user who locked the automation device is able to unlock the automation device to end the started edit session.