Drive Configuration History and Rules for Lifecycle Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The life cycle of drive devices involves overlapping and repetitive phases such as maintenance, configuration changes, and commissioning, which require tracking of previous configurations and parameters, but existing methods lack efficient data management and synchronization, leading to potential misconfigurations and increased downtimes.
Innovation Solution
A central database is implemented to store and manage data for planning, configuring, and maintaining drive devices, allowing for temporal data storage, configuration rule enforcement, and simulation capabilities, ensuring centralized data access and reducing misconfigurations through defined configuration rules and warnings for atypical changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is stored at multiple storage locations for design, configuration, and maintenance tasks, then data accessibility is improved, but data synchronization complexity and error-proneness increase
Solution Approach 1:
The patent merges multiple distributed data storage locations into a single centralized database that serves all application programs (design, configuration, maintenance). This consolidation eliminates the need for complex synchronization mechanisms between multiple storage locations while maintaining universal data accessibility through the centralized system.
Solution Approach 2:
The centralized database is designed to serve multiple functions and multiple application programs simultaneously. It provides a universal data storage and retrieval mechanism that replaces multiple specialized storage locations, simplifying the system architecture while improving ease of operation through a single point of access.
2Reliability
If data is manually managed and synchronized across different storage locations, then data availability is maintained, but time consumption and error-proneness increase
Solution Approach 1:
The centralized database automatically manages data storage, retrieval, and synchronization for all application programs. The system serves itself by providing built-in mechanisms for data consistency and availability without requiring manual intervention for synchronization tasks, thereby eliminating time consumption and reducing errors associated with manual data management.
3Adaptability or versatility
If configuration changes are made without centralized tracking, then configuration flexibility is improved, but misconfiguration risk and commissioning time increase
Solution Approach 1:
The centralized database provides automatic feedback mechanisms that track all configuration changes made by different application programs. When a configuration change occurs, the system records it centrally and notifies relevant programs, ensuring that flexibility is maintained while misconfiguration risk is reduced through centralized monitoring and version control.
4Quantity of substance
If historical configuration data is not preserved, then storage space is optimized, but the ability to track changes and revert to previous configurations is lost
Solution Approach 1:
The centralized database is designed to automatically preserve historical configuration data as part of its core functionality. Before any configuration change is made, the system preliminarily stores the previous state, enabling automatic tracking and reversal capabilities. This preliminary action ensures that configuration history is maintained without requiring additional manual archiving steps.
Data Source
AI summary
The invention relates to a method for designing, configuring and maintaining a drive device (2), with a central database (3) being provided for application programs (4 to 7) used for designing, configuring and maintaining the drive device (2), in which database data are stored as temporal data and can be read and supplemented by the application programs (4 to 7), wherein configuration rules, dependent on the life cycle phase of the drive device (2), for an execution and/or an extent of a configuration change to the configuration of the drive device (2) are defined.