CMDB Reverse Classification for Cross-Hierarchy Reclassification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional configuration management database (CMDB) techniques struggle to seamlessly retain historical information when a managed item is reclassified to a new class type that is not a descendant of its previous class type, resulting in loss of associated knowledge.
Innovation Solution
Implementing a reverse classification process that identifies a common ancestor of the old and new class types, allowing for seamless transition of attributes and historical data by traversing up and down the class hierarchy to update the configuration item record without administrator intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a managed item is reclassified to a new class type that is not a descendant of its previous class type, then the item can be updated to reflect current configuration, but historical information and associated knowledge are lost
Solution Approach 1:
The patent introduces a common ancestor class as an intermediary between the old and new class types. When reclassifying a configuration item, the system identifies the common ancestor class in the inheritance hierarchy and uses it as a mediator to preserve historical information. The old attributes are retained through the ancestor class while new attributes are added, preventing information loss during cross-hierarchy reclassification.
Solution Approach 2:
The patent adds a temporal dimension to class classification by maintaining multiple class associations for a configuration item over time. Instead of a single linear class path, the system creates a multi-dimensional view where items can have historical class associations and current class associations, allowing traversal through the class hierarchy to preserve and access historical information while accommodating current configuration state.
2Ease of operation
If traditional reclassification methods are used, then the process is simple, but administrator intervention is required and historical data is lost
Solution Approach 1:
The patent implements self-service reclassification by enabling the configuration item to automatically identify its common ancestor class and perform the reclassification process without administrator intervention. The system autonomously traverses the class hierarchy, identifies the appropriate ancestor, and updates the item's class associations while preserving historical data, making the process self-executing and eliminating manual overhead.
Solution Approach 2:
The patent incorporates feedback mechanisms that automatically detect when a configuration item's attributes no longer match its current class type. The system continuously monitors attribute-class compatibility and triggers reclassification when mismatches are detected, providing automatic feedback-driven updates that eliminate the need for manual administrator review while maintaining data integrity.
3Adaptability or versatility
If cross-hierarchy reclassification is allowed, then adaptability increases, but system complexity increases
Solution Approach 1:
The patent segments the reclassification process into distinct manageable steps: identifying the old class type, traversing up the hierarchy to find the common ancestor, and establishing the new class association. This segmentation breaks down the complex cross-hierarchy reclassification into discrete, automated operations that can be executed systematically without overwhelming system complexity.
Data Source
AI summary
Attributes of a configuration item record of a configuration management database (CMDB) are received. Based on the received attributes, a determination is made that the configuration item record belongs to a new child class and no longer belongs to a previously identified child class. While maintaining a same identifier in the configuration item record, a classification of the configuration item record is changed to the new child class including by adding one or more attributes of the new child class to the configuration item record and removing one or more attributes of the previously identified child class from the configuration item record.