Unified Service and CI Database for Hybrid IT Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Configuration Management Databases (CMDBs) struggle to provide a comprehensive, integrated view of services and micro-services in hybrid IT landscapes, especially in dynamic 'As-a-Service' models, where relationships between Configuration Items (CIs), micro-services, and parent services are complex and require a unified management system.

Innovation Solution

A system comprising a database that stores details of services, micro-services, and CIs, mapping micro-services with CIs to facilitate operation and providing an integrated view, enabling root cause analysis and integration with discovery tools for efficient management and maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If a conventional CMDB is used to track CIs and relationships, then IT infrastructure tracking is maintained, but it cannot provide integrated visibility of services, micro-services, and CIs in hybrid cloud environments

Engineering Contradiction:
Improvevisibility of services and infrastructureVSAvoidsystem architecture
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent merges the service catalog layer with the CMDB layer into a unified system. The service catalog table and CMDB table are integrated such that services, micro-services, and CIs are all tracked in a single database structure, eliminating the need for separate tracking systems and providing holistic visibility across hybrid IT landscapes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The unified database structure serves multiple functions simultaneously: it acts as both a service catalog (tracking services and micro-services) and a CMDB (tracking CIs and relationships). This multi-functional approach allows the system to handle both service-level and infrastructure-level data without requiring separate specialized systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of manufacture

If multiple databases are used to store service details and CI details separately, then data organization is maintained, but data duplication and management overhead increase

Engineering Contradiction:
Improvedata managementVSAvoiddata storage
Core Design Contradiction:
Ease of manufactureVSQuantity of substance

Solution Approach 1:

The patent combines service catalog data and CMDB data into a single unified database structure. Instead of maintaining separate databases for service details and CI details, the system uses one database with integrated tables that store both types of information, eliminating data duplication and reducing management overhead while maintaining proper data organization through structured relationships.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If CMDB focuses on IT infrastructure level, then CI tracking is effective, but service level visibility is lost in modern XaaS models

Engineering Contradiction:
Improveservice managementVSAvoiddata model
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data model into hierarchical levels within a unified structure: services at the top level, micro-services as intermediate components, and CIs at the infrastructure level. This segmentation allows the system to maintain service-level visibility while preserving detailed CI tracking, with each level properly represented and related in the unified database schema.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11824734B2System providing management of services and a method thereof
Publication Date: 2023.11.21 HCL AMERICA INC
  • US11824734B2 patent drawing
  • US11824734B2 patent drawing
  • US11824734B2 patent drawing

AI summary

Disclosed is a system providing management of services. The system comprises a database configured to store details of one or more services and one or more micro-services associated with each service of the one or more services. The database is also configured to store one or more Configuration Items (CIs) facilitating operation of the one or more services in an application. The one or more micro-services are mapped with one or more CIs for facilitating the operation of the one or more services in the application.