License Update Engine for Dynamic Configuration Drift
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software rights management systems, such as FlexNet Manager Suite, fail to automatically update licenses as their underlying definitions evolve, leading to reduced accuracy and optimization value for customers, as licenses become static and do not reflect changes in licensing terms and conditions over time.
Innovation Solution
A license update engine is implemented within a license entitlement automation system that regularly analyzes licenses for drift from their original definitions, generating proposals for operators to update license configurations, including changes to license types, applications, and usage rights, which are stored in a database for acceptance or ignoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If licenses are created based on static definitions, then license configuration is simple and stable, but licenses do not reflect updates to licensing terms and conditions over time
Solution Approach 1:
The license management system transitions from static definitions to dynamic definitions that automatically update when licensing terms change. The definition store maintains versioned definitions and automatically applies updates to affected licenses, ensuring license configurations remain current without manual intervention.
Solution Approach 2:
The system implements a feedback mechanism where the license management system monitors for definition updates, compares them against existing licenses, and generates notifications or automatic updates. This closed-loop feedback ensures licenses remain synchronized with current licensing terms.
2Ease of operation
If licenses automatically inherit settings from definitions, then license configuration is simplified, but customer-negotiated terms may be inadvertently changed
Solution Approach 1:
The system performs preliminary analysis before applying definition updates by identifying which licenses would be affected and what changes would occur. Operators review these predicted changes and approve or reject them before actual updates are applied, preventing inadvertent changes to negotiated terms.
Solution Approach 2:
The system introduces an intermediary review layer between definition updates and license applications. The update engine generates proposed changes that are presented to operators for approval, acting as a mediator that balances automatic updates with manual oversight to protect customer-negotiated terms.
3Adaptability or versatility
If manual updates to license definitions are allowed, then flexibility to adapt to changing terms is improved, but accuracy and optimization value are reduced
Solution Approach 1:
The license management system performs self-service by automatically detecting definition updates, analyzing their impact on existing licenses, and applying updates without requiring manual operator intervention. This automated self-updating process maintains both adaptability to changes and accuracy through systematic processing.
Solution Approach 2:
The system replaces manual mechanical processes of tracking and applying license definition updates with an automated computational system. The update engine systematically monitors definitions, compares versions, and applies updates algorithmically, eliminating human error and improving accuracy while maintaining adaptability.
4Device complexity
If licenses remain static after creation, then system simplicity is maintained, but licenses drift from their original definition reducing optimization value
Solution Approach 1:
The license management system implements periodic automated updates by monitoring for definition changes at scheduled intervals or triggered by events. This periodic action ensures licenses are updated regularly to maintain optimization value while keeping the overall system architecture simple and manageable.
Data Source
AI summary
A license update engine is run as part of a license entitlement automation system. The license update engine is minimally executed daily and identifies, for example, content updates to be applied and licenses that have drifted from their definition. The license update engine then generates proposals for operators to consider. Accepted proposals update the license configuration. Thus, the license update engine identifies licenses and the definitions that are connected to them, including definitions that the licenses from which the were created and definitions that are linked to SKUs of entitlement purchases. Analyses relates three categories of proposal, including license types, applications linked to licenses, and usage rights on licenses. Proposals are stored in a database and operators can accept or ignore them. The database maintains a history of license changes.