Skip to main content

Multi-license consumption

This report identifies redundant software usage by flagging instances where a single user is simultaneously holding more than one unique license key for the exact same feature and product combination. The system identifies active sessions with no end time and retains only the most recent unique record per user, feature, product, and license ID to prevent double-counting. It then flags any user simultaneously holding multiple unique license keys for the exact same combination of feature, product, vendor, version, and additional key.

Multi-License Consumption Multi-License Consumption

Detailed dashboard visualizing redundant active sessions where a single user consumes multiple unique license keys for the same feature and product.

KPIs​

The sheet reports 4 counts, in this order:

  • Distinct Users: Total number of unique individuals currently identified as holding multiple concurrent licenses for the same feature.
  • Distinct Features: The number of unique software features or modules currently subject to redundant consumption.
  • Distinct Licenses: The total count of unique license IDs (keys) currently flagged as part of a multi-license consumption event.
  • Distinct Servers: The total number of unique license servers currently involved in redundant license transactions.

Visualizations​

  • Multi-License Consumption Table: A detailed log that captures the full context for flagged redundant sessions.

  • Users by License Count (Bar Chart): Displays users holding the highest number of concurrent licenses for the same feature.

  • License Count by Feature (Bar Chart): Illustrates which specific features are most frequently subject to multi-license consumption.

Values displayed:

  • Username: The user holding the licenses.

  • Feature Name: The specific software feature in use.

  • Product Name: The software product the license belongs to.

  • Server Name: The license server that manages and distributes the licenses.

  • Vendor: The software provider behind the license.

  • License Type: The licensing model, for example floating or node-locked.

  • License ID: The unique identifier of each license key, used to track individual license usage. Two rows that share a user, feature and product but differ here are exactly the redundancy this report exists to surface.

  • Project Name: The project OpenLM attributes the usage to. Records with no project mapping read No Project.

  • Version: The version of the product consuming the license.

  • Active Session Count: The number of currently active sessions for that license record - normally 1 per row.

  • Start Time (UTC): When the license session started.

  • End Time (UTC): When the session ended. An empty value means the session is still open, which is the only state this report reports on.

  • Filters:

  • Date: A relative date filter. It defaults to Last 14 days and prints the resolved range underneath (for example, 2026/07/11 to 2026/07/24). Select another preset, or a custom start and end date, to change the reporting period.

  • Server Name: Users can select any server name from this filter.

  • Vendor: Users can select any vendor from this filter.

  • Feature Name: Users can select any feature name from this filter.

  • Software Name: Select a catalogued product from the SAM Catalog. The catalog normalizes publisher and product names, so filtering here groups license records that carry inconsistent raw license strings.

  • Product Name: Users can select any product name from this filter.

  • License Type: Users can select any license type from this filter.

  • Version: Users can select any version from this filter.

  • User Name: Users can select any username from this filter.

  • Child Username: OpenLM aggregates usage under a parent user account, so User Name shows the combined total for that person. Select a child username here to drill into a single account merged under the parent. See User aliases for how OpenLM builds the mapping.

Interpreting this report​

  • Every row is 1 user holding 2 or more license keys for the same feature, product, vendor, version and key - simultaneously, at this moment. Legitimate causes exist (a workstation switch mid-session, a crashed session not yet reaped), but each occurrence is a seat silently lost to the pool.
  • All KPIs at zero is the healthy state and, because the report only evaluates currently open sessions, also the usual state - findings appear and disappear as duplicates arise and resolve.
  • Recurring names in Users by License Count are the actionable signal: the same user repeatedly double-consuming points at a workstation profile or startup script spawning duplicate checkouts, not user behaviour.
  • Cross-reference a flagged user's rows with Currently consumed licenses to see both sessions side by side, including the workstations they came from.
note

This report describes the current state: it flags sessions that are open at this moment and have no end time. When no user is holding 2 keys for the same feature at this moment, every KPI reads 0 and both charts show No data - and widening the Date filter does not change that, because the date range does not bring closed sessions back into scope.

Last updated on by Maria Gilca