Software License Edition Tracking and Redistribution via Universal Query
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Organizations face challenges in managing software licenses due to difficulties in identifying software package editions and monitoring usage, leading to under-licensing or over-licensing, especially during audits, as edition information is often inaccessible and traditional software metering generates excessive data.
Innovation Solution
An edition-managing software application, such as a PowerShell script, is installed on client devices to collect edition information and store it in a universal storage location, while a usage-tracking program retrieves the last used date of software packages, reducing data demands and identifying underutilized packages for license redistribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional software metering is used to monitor usage, then usage data can be collected, but excessive data is generated leading to high storage and processing demands
Solution Approach 1:
The patent extracts only the essential usage information (last used date) from the full usage data, storing only this critical element while discarding redundant detailed usage records. This extraction approach maintains the ability to determine software usage status without retaining excessive data volume.
Solution Approach 2:
The patent employs temporary or session-based tracking mechanisms that do not require persistent storage of detailed usage logs. Instead of maintaining long-term detailed records, the system uses short-lived data structures that are discarded after extracting the necessary last used date information.
2Measurement precision
If edition information is retrieved from publisher-specific locations, then accurate edition data can be obtained, but the system complexity increases due to multiple query locations
Solution Approach 1:
The patent creates a universal query mechanism that can access multiple publisher-specific registry locations through a single standardized interface. The software package edition information is retrieved from various publisher-specific locations (Microsoft, Adobe, Oracle, etc.) using one unified PowerShell script approach, making the system adaptable to different publishers without increasing apparent complexity.
Solution Approach 2:
The patent introduces a standardized intermediary layer (the universal query function in PowerShell) that mediates between the system management software and various publisher-specific registry locations. This intermediary handles the complexity of multiple query locations internally while presenting a simple interface to the system management software.
3Productivity
If detailed usage monitoring is implemented, then software utilization can be tracked, but significant resources are consumed for data analysis and storage
Solution Approach 1:
The patent extracts only the essential usage information (last used date) from the full usage data, storing only this critical element while discarding redundant detailed usage records. This extraction approach maintains the ability to determine software usage status without retaining excessive data volume.
Solution Approach 2:
The patent applies partial monitoring by tracking only the last used date rather than complete usage history. This partial action approach provides sufficient information for license management decisions (whether software is currently in use) while consuming minimal processing and storage resources.
Data Source
AI summary
In accordance with the present approach, an edition-managing software application may be provided to query registries of client devices for edition information associated with a target software package. When retrieved, the edition information may then be stored in a universal storage location from which the edition-managing software application may generate an edition report that provides an accurate representation of actual installations of each edition of the target software package on the client devices. Further, in accordance with the present approach, a usage-tracking software program may be provided to retrieve a last used date of a target software package on client devices. If the last used date is beyond a threshold time period for the client devices, the enterprise may determine that the target software package is underutilized compared to a desired usage. Then, the target software package may be uninstalled from the client devices and installed on other client devices.