Software License Reconciliation via Subunit Impact Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software license management systems fail to efficiently manage changes to a system, leading to potential licensing compliance issues and inefficiencies in updating reconciliation reports.

Innovation Solution

A computer-implemented method and system that executes an initial reconciliation run, detects changes to subunits, performs an impact analysis, and generates an updated reconciliation report by replacing the initial subunit report with a changed subunit report, using a reconciliation engine to maintain licensing compliance without requiring a full system reconciliation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a full system reconciliation is performed to ensure licensing compliance, then compliance accuracy is improved, but processing time and system resources are significantly increased

Engineering Contradiction:
Improvelicensing compliance accuracyVSAvoidreconciliation processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the reconciliation process by identifying and isolating changed subunits within the system. Instead of reconciling the entire system, the methodology performs targeted reconciliation only on affected subunits, thereby maintaining compliance accuracy while significantly reducing processing time and resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary detection of changes to subunits before executing the reconciliation process. By identifying changed subunits in advance through change detection mechanisms, the system prepares targeted reconciliation reports only for affected areas, avoiding unnecessary full-system processing.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traditional license management systems update reconciliation reports after system changes, then compliance is maintained, but the process is inefficient and resource-intensive

Engineering Contradiction:
Improvecompliance maintenanceVSAvoidupdate efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent divides the reconciliation report into subunit-specific sections, allowing selective updates only for changed subunits. This segmentation enables the system to maintain compliance reliability while improving update efficiency by avoiding redundant processing of unchanged portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs partial reconciliation actions by generating updated reports only for affected subunits rather than performing complete system-wide reconciliation. This partial action approach maintains necessary compliance while significantly improving productivity by reducing unnecessary computational overhead.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the system performs comprehensive reconciliation to identify all licensing issues, then compliance coverage is improved, but processing complexity increases

Engineering Contradiction:
Improvecompliance coverageVSAvoidreconciliation process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the compliance coverage by focusing on changed subunits identified through impact analysis. This segmentation maintains comprehensive coverage of affected areas while reducing overall process complexity by eliminating unnecessary analysis of unchanged system portions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts and isolates changed subunits from the overall system context, performing reconciliation only on these extracted portions. This extraction approach ensures comprehensive compliance coverage for affected areas while significantly simplifying the reconciliation process by removing unrelated system components from the analysis.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10325078B2Software license management impact analysis
Publication Date: 2019.06.18 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10325078B2 patent drawing
  • US10325078B2 patent drawing
  • US10325078B2 patent drawing

AI summary

A computer implemented method, program product, and system for managing software licenses is presented. A licensing management logic executes an initial reconciliation run for an initial system. The licensing management logic detects a change to an initial subunit to create a changed subunit, and executes an impact analysis for the changed subunit. The licensing management logic identifies a subunit reconciliation section from the initial reconciliation run, and executes a subunit reconciliation run for the changed subunit to create a changed subunit reconciliation report. The licensing management logic replaces the initial subunit reconciliation report with the changed subunit reconciliation report to create an updated reconciliation report for a changed system.