Service Model Reconciliation via CMDB Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Business Service Management (BSM) faces challenges in modeling and managing complex IT systems due to difficulties in discovering and reconciling resources and relationships within large computing environments, as well as in efficiently updating and distributing service models across distributed Impact Managers.
Innovation Solution
A system with a database and graphical user interface application that facilitates the creation, editing, and publishing of service models, utilizing a Configuration Management Database (CMDB) for resource reconciliation and a Publishing Server for centralized distribution of model updates to Impact Managers, allowing for automated and user-initiated publishing processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Difficulty of detecting and measuring
If multiple discovery applications are used to detect resources in large computing environments, then resource detection capability is improved, but resource reconciliation difficulty increases and duplicate reporting occurs
Solution Approach 1:
The patent introduces a Configuration Management Database (CMDB) as an intermediary component that receives resource information from multiple discovery applications. The CMDB reconciles duplicate resource reports by maintaining a unified configuration management information model, where resources are identified by unique identifiers and cross-referenced across different discovery sources, eliminating redundancy while preserving detection capabilities.
Solution Approach 2:
The CMDB serves as a universal repository that handles resource information from various discovery applications with different detection capabilities. It provides a common data model and reconciliation mechanisms that work across multiple discovery tools, allowing the system to leverage the strengths of each application while maintaining consistency through a single source of truth.
2Speed
If service model portions are stored locally at distributed Impact Managers, then local event processing speed is improved, but model update complexity increases
Solution Approach 1:
The service model is segmented into distributed portions stored at multiple Impact Managers, each responsible for local event processing. This segmentation enables parallel processing and fast local response times while the central CMDB maintains the authoritative master model. Updates are propagated from the central repository to distributed instances, combining the benefits of distribution with centralized control.
Solution Approach 2:
The system implements feedback mechanisms where Impact Managers report local model state and event processing status back to the central CMDB. This feedback loop enables the central repository to track distributed model instances, coordinate updates, and ensure consistency across the distributed system without compromising local processing speed.
3Adaptability or versatility
If service model updates are made at distributed Impact Managers, then local model customization is improved, but update consistency across the network deteriorates
Solution Approach 1:
The patent allows local customization of service model portions at each Impact Manager based on specific local requirements and event types. Each Impact Manager can adapt its local model instance to optimize for local conditions while the central CMDB maintains the master model with global consistency requirements. This enables local quality optimization without sacrificing overall model integrity.
Solution Approach 2:
The system performs preliminary actions by establishing a central CMDB as the authoritative source for service model definitions before distribution to Impact Managers. This preliminary centralization ensures that all local customizations are based on a consistent foundation, and any local modifications can be tracked and reconciled against the master model to maintain network-wide consistency.
4Stability of the object's composition
If a centralized system is used to manage service models, then model consistency is improved, but system complexity increases
Solution Approach 1:
The CMDB acts as an intermediary between the central management function and distributed Impact Managers. It provides a standardized interface for model definition, storage, and distribution, simplifying the central management architecture while maintaining model consistency. The intermediary handles the complexity of coordinating distributed instances through a unified data model and reconciliation processes.
Data Source
AI summary
A modeling system has a database that: stores information of resources of a computer network service. A server f has a graphical user interface application for creating and editing service models. The application receives user-entered search criteria and searches information in the database based on the criteria. The search criteria can include a name, type, attribute, and other information of the resources. In addition, the search criteria can be a user-entered search query entered that has one or more logical or Boolean conditions relating resource attributes to attribute values. Using information obtained through searching, the application is used to create at least a portion of a service model of the computer network service. Once created, the application is used to initiate publishing of at least a portion of the service model to one or more impact managers of the computer network service.