Dynamic CMDB Identification via Universal N-Tuple Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Configuration Management Database (CMDB) systems face challenges in creating a single integrated view of IT information from multiple disparate systems and tools, as they lack normalized and dynamic representation, leading to duplicative data and increased complexity in maintaining custom maps, which hinders activities like change planning and service optimization.
Innovation Solution
A dynamic identification system using universal identifying n-tuples generates a unique identifying signature for records across originating systems and the CMDB, allowing for normalized and consistent referencing without static mappings, adapting over time and accommodating variance in data structures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom maps are used to integrate multiple disparate systems with CMDB, then system integration is achieved, but device complexity and maintenance effort increase
Solution Approach 1:
The patent implements a universal identification mechanism using standardized n-tuples that can be applied across multiple disparate systems and tools. This universal approach eliminates the need for system-specific custom maps, as the same identification rules and signature generation process work across all originating systems, thereby reducing maintenance complexity while preserving integration capability
Solution Approach 2:
The patent changes the approach from static custom mappings to dynamic parameter-based identification. By using configurable n-tuples with variable parameters (such as different data elements for different CI types) and configurable matching rules, the system adapts to different originating systems through parameter configuration rather than through complex custom maps, reducing structural complexity
2Adaptability or versatility
If static mappings are used for record association, then integration is achieved, but adaptability to data structure variance is reduced
Solution Approach 1:
The patent replaces static mappings with dynamic identification processes. The system generates identifying signatures dynamically based on the actual data present in records and applies configurable matching rules that can adapt to different data structures. This dynamic approach allows the system to handle variance in data structures across different originating systems without requiring pre-defined static mappings for each scenario
Solution Approach 2:
The patent introduces an intermediary identification layer using standardized n-tuples and signature generation processes. This intermediary mechanism sits between the diverse originating systems and the CMDB, translating various data structures into a common identification format. The intermediary handles the adaptability burden, allowing originating systems to maintain their own data structures while achieving consistent integration with the CMDB
3Loss of information
If multiple disparate systems are integrated without normalization, then system independence is maintained, but information accuracy and duplication increase
Solution Approach 1:
The patent segments the integration process into distinct layers: originating systems maintain their independence and data structures, while a separate identification layer applies standardized n-tuple extraction and signature generation. This segmentation allows each originating system to remain independent and unchanged, while the intermediate identification layer ensures normalized processing for accurate CMDB integration, eliminating duplication through consistent identification
Data Source
AI summary
Disclosed herein are various systems, methods, and apparatuses for providing a system independent Configuration Management Database identification system. In an implementation, a dynamic identification system correlates records of an originating system with records of an Authoritative Configuration Management Database (CMDB) including a set of one or more identifying rules that define a minimum amount of information in order to generate an identifying signature that serves as a common reference between a record of the originating system with a matching Configuration Item (CI) record of the ACMDB, receiving, from the originating system, information to generate an identifying signature, determining that the generated first identifying signature matches a stored identifying signature, and correlating the first record of the originating system corresponding with the generated first identifying signature with the one of the CI records of the ACMDB corresponding with the matching one of the identifying signatures.