CMDB Software License Compliance Evaluation Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Configuration Management Databases (CMDBs) lack the capability to ensure enterprise compliance with software license contracts, leading to potential legal and financial risks due to unmanaged software asset usage.

Innovation Solution

A method and system that store deployment models of software products in a CMDB and corresponding software license contracts in a license database, allowing for compliance evaluation by connecting and comparing these models to generate exception indications for non-compliance, enabling appropriate action to bring software assets into compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional CMDBs are used to manage software assets, then basic configuration management is achieved, but software license compliance capability is lacking

Engineering Contradiction:
Improvesoftware license compliance capabilityVSAvoidCMDB system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines the CMDB with license compliance management functionality by integrating a license model store, deployment model store, and compliance evaluation module into the existing CMDB infrastructure. This merging approach enables the CMDB to simultaneously manage configuration items and evaluate software license compliance without requiring entirely separate systems.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent extends the CMDB's functionality to perform multiple roles: traditional configuration management, software asset tracking, license contract storage, deployment modeling, and compliance evaluation. By making the CMDB universal, it can handle diverse software asset management tasks including generating exception indications for license violations.

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

2Reliability

If software asset usage is not monitored, then operational simplicity is maintained, but legal and financial risks increase

Engineering Contradiction:
Improvelicense compliance assuranceVSAvoidcompliance verification efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary actions by storing both deployment models and license contract models in advance within the CMDB. The system pre-establishes the framework for compliance evaluation by maintaining ready-to-compare models, so that when compliance checking is needed, the evaluation can proceed immediately without delayed data collection or manual contract retrieval.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the compliance evaluation module continuously compares deployment models against license contract models and generates exception indications when violations are detected. This feedback loop enables the organization to take corrective actions promptly, improving reliability by ensuring ongoing compliance while maintaining efficiency through automated monitoring.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8646093B2Method and system for configuration management database software license compliance
Publication Date: 2014.02.04 BMC HELIX INC
  • US8646093B2 patent drawing
  • US8646093B2 patent drawing
  • US8646093B2 patent drawing

AI summary

A software license engine allows an enterprise to model software license contracts and evaluate deployment of software for compliance with the software license contracts. Deployment of software products in the enterprise is modeled in a configuration management database. The software license engine maintains a license database for connecting software license contracts with software deployment modeled by the configuration management database. Users of the software license engine may use license types that are predefined in the software license engine or may define custom license types. The software license engine may indicate compliance or non-compliance with the software license contracts.