Developing an estimated license position

License Optimizer enables you to develop an estimated license position by comparing usage with entitlement: taking software inventory and comparing it against your license entitlements. When you have developed an estimated license position, your licensing expert can use it to identify where your organization is under-licensed (at risk of a compliance audit) or over-licensed (wasting money on unnecessary software purchases). Note that owing to the complexity of many licensing rules, your true license position can be determined only by an experienced licensing expert. License Optimizer helps your licensing expert to gather the data they require and then identify areas for them to focus their efforts on. This enables them to produce a document known as an Effective License Position (ELP).

A video that gives an overview of License Optimizer is available: Conceptual Overview (4:39)

The approach below provides a guide for developing estimated license positions within License Optimizer. For more information, click the highlighted sections in the diagram below:

Add Install-based Inventory

Import, or manually create install-based inventory

Check Software Teaching for new or unrecognized products

Run recognition

 

 

 

 

 

 

Is install-based inventory complete?

 

 

 

 

 

 

 

 

 

 

 

 

Add usage-based inventory

Import, or manually create, usage-based inventory

 

 

 

 

 

 

 

 

 

 

Is usage-based inventory complete?

 

 

 

 

 

 

 

 

 

 

 

 

Add License data

Import, or manually create, entitlement

Match entitlement to DSL

Check metrics and paths
(Downgrades, maintenance, etc)

 

 

 

 

 

 

Is entitlement complete?

 

 

 

 

 

 

 

 

 

 

 

 

Run reconciliation

 

 

 

 

 

 

 

 

 

 

 

 

Data Summary

 

 

 

 

 

 

For more information on Reconciliation, see Reconciling liabilities with entitlements.

When you have completed the reconciliation, you can review the reconciliation data from the Data Summary page. If the results are not as expected, look back through the workflow above to determine any possible gaps or issues.