Application detail view

To show detailed information on a specific application, click the item in a list of applications.

The information boxes in the Application detail view show licensing information according to the following table.

Instances

Licenses

License requirement

Coverage

Compliance

Icon depends on type of instance

IconLicenses
IconLicenseReq
IconLicCoverage
IconCompliance

Number of instances.

The type of instance, depends on the metric used to calculate compliance for the application.

Number of available licenses.

Number of licenses required to ensure compliance with the selected metric.

Number of instances covered by available licenses

The calculated difference between Coverage and License requirement.

Compliant: green icon

Non-compliant: red icon

For an application that requires no license (the metric is set to “No license required”), only the information box Installations is used.

informationbox

The bottom section of the detail view contains detailed information on the application presented in tabs according to the following table.

Note

Available tabs in the application detail view depend on the metric and if the application is installed on a computer or on a mobile device.

Tab

Description

Licenses

Purchases

All registered license purchases for the selected application.

Transfers

All received or transferred licenses from/to other application versions via upgrade or downgrade rights.

Tracking

A summary of license requirement and entitlement state for each consumer.

For more information, see Licenses tab.

Allocation

Shows allocation of licenses and installations.

  • The License requirement column shows how many licenses are required for each organization node (i.e. number of licensable installations of the application in question) and includes installed applications without registered usage.

  • The Coverage column shows the number of instances covered by available licenses.

  • The Compliance column shows the calculated difference between Coverage and License requirement.

Compliance

Details

A presentation of how the values displayed in the information boxes of the Application detail view have been calculated.

History

A graph of the highest and lowest compliance values each month over a period of time for the application. The period is selected with the range selector under the graph.

Trend

Graphs of the requirement, coverage, compliance and compliance trend of an application over a period of time. The period is selected with the range selector below the graph. Click the Requirement, Coverage, Compliance and/or Compliance trend labels to hide or show the graphs.

For more information, see Compliance tab.

Computers

Installations

All computers with an installation of the selected application.

History

A graph of the number of installations of the application per month over a period of time. The period is selected with the range selector below the graph.

Mobile device

All mobile devices with an installation of the selected application.

Only available for mobile devices.

Users

Users

All users that have used the application, and the last time they used it.

Concurrent usage

A graph of the maximum number of concurrent users per month over a period of time. The period is selected with the range selector below the graph.

Only displayed for applications with metric Concurrent users.

History

A graph of the number of users of the application per month over a period of time. The period is selected with the range selector below the graph.

Devices

Devices

The devices that have used the application.

Available for applications that can be accessed remotely or via a virtual desktop connection.

Concurrent usage

A graph of the maximum number of concurrent devices per month over a period of time. The period is selected with the range selector below the graph.

Only displayed for applications with metric Concurrent devices and if the application is installed on a device.

History

A graph of the number of devices using the application per month over a period of time. The period is selected with the range selector below the graph.

Bundle content

The names of all applications within the bundle. Also, the number of installations via bundles is compared to the total number of installations, and the difference constitutes the number of stand-alone installations.

Only available for application bundles, such as Adobes Creative Cloud or Microsoft 365.

Information

General information on the application grouped by information type.

Financial info

The financial information that has been entered for the application. All values are shown in the currency set by the user.

For more information, see Financial info tab.

SKU

The Stock-keeping unit (SKU) information for the application.

  • The column Product description shows application details supplied by the manufacturer.

  • The columns UPG and DWN show the product use rights; upgrade and downgrade.

Multiple metrics

If the Multiple metricsSLM_MultipleMetricsIcon.png symbol is displayed next to the application name at the top of the Application detail view, more than one metric can be used in the license assignment, reporting, and compliance calculations for the application. You can add metrics to an application in the Metrics section, see Edit application.

When multiple metrics are included for an application, you can select metric from the pop-up list in the Instance box.

SLM_MultipleMetrics_InstanceBox.png

The information boxes will change to show licensing information for the selected metric.

The selected metric is listed next to the application name together with the Multiple metrics symbol SLM_MultipleMetricsIcon_AlternativeMetric.png.

The Licenses and Allocation tabs display information about the selected metric, and the Compliance tab displays information for all metrics added to the application.

Licenses tab

The Licenses tab contains the views Purchases, Transfers, and Tracking.

Purchases

The Purchases view shows information on all license purchases that have been registered for the application. The Incomplete check box is used for indication of any incomplete licenses.

Click the arrow ArrowRightnext to the purchase date to open a separate window presenting the current license allocation.

Click a purchase in the list to be directed to the details of that license registration.

Transfers

If any licenses have been received or given via upgrade rights or downgrade rights, a list of these transfers can be found in the Transfers view. Information is shown on involved applications, transfer type, metric of the license, and number of transferred licenses.

Click an application in the list to be directed to the details of that application.

Tracking

The Tracking view shows a list of all consumers that require a license for the application.

If multiple metrics are available for the application, the type of consumer and related information depends on the selected metric.

  • The Used column indicates if the installation is used or not.

  • The Required column shows the number of licenses that is required for coverage. Click the arrow next to the quantity to see information on any license adjustments that have been made to the initial license requirement.

  • The Entitlement state column shows to what extent the consumer is covered. Click the arrow next to the state to see more information, and to be directed via a link to any license purchase that is used for coverage.

Click a consumer in the list to be directed to the details of that consumer.

Compliance tab

The Details view on the Compliance tab shows in-depth information on how licenses, requirement, and coverage on the Application detail view have been calculated.

The top section shows calculations based on the metric of the application. If any licenses have been registered with other metrics than the application’s metric, additional sections with calculations will follow.

If multiple metrics are available for the application, select Show additional metrics to see the calculations for all available metrics.

Tab

Description

Initial requirement

The initial license requirement before any adjustments have been made. The number is expressed in the metric of the application or, for licenses with another metric, translated into the corresponding quantity of that metric.

Example 9.

The metric is set to Number of processors. There are 10 servers with in total 14 processors where this application is detected. The initial requirement will in this case be 14 processors. If a license purchase is registered with the metric Installations the initial requirement will correspond to 10 installations.

For more information, refer to the Compliance examples in the Appendix.



Licenses

Information on available licenses that can be used to cover this application.

Number of registered purchased licenses are shown as well as any license adjustments that have been made, for example:

  • transfers of licenses via upgrade or downgrade rights (+/-)

  • incomplete or unassigned licenses (-)

  • subscription licenses for which the subscriptions have expired (-).

Required licenses

Information on number of licenses that are required.

Number of initially required licenses are shown as well as any license adjustments that have been made, for example:

  • extended coverage or secondary use rights (-)

  • application bundling (-)

  • usage outside the metering period (-)

  • VDI (-)

  • manual compliance exclusions (-)

  • Core factors (+/-).

These details are only shown in the section for the metric of the application.

Coverage

Information on to what extent the application is covered.

Number of available licenses are shown as well as any license adjustments that have been made, for example:

  • covered by other metrics (+)

    Select the figure to see a pop-up window with additional information.

  • licensing other metrics (-)

  • site licenses (+)

  • VM use rights (+)

  • Covered by subscription plan (+)

    Note

    To automatically detect license coverage of applications included in Microsoft 365, users in SAM on Atlas must be linked with Microsoft 365 users. Also, the Snow Integration Connector for Microsoft 365 must be setup.

  • Double licensed (-)

    Note

    A double licensed application is an application that is both covered by a license and a subscription plan.

    The normal license auto allocation does not take into account which users have a subscription plan that is covering the application. This will result in both the normal license, and the subscription plan covering the same user.

    We recommend that you use the Snow Integration Connector for Microsoft 365 and user linking to provide coverage for applications included in your Microsoft 365 subscription plans. If you need to add coverage for an application using a normal license, make sure to assign it to the specific user or device you want covered, rather than using auto allocate.

Compliance

A summary that shows whether the application is compliant or not:

Compliance = Coverage – Required licenses

Financial info tab

The Financial info tab shows costs and financial risks related to the application.

Type

Description

Total application cost

This cost is calculated as:

Application cost per metric × License requirement

Application cost per <metric>

This cost is set manually in the Edit application view.

Total license cost

This cost is calculated as:

Total license purchase + Total maintenance cost + Total support cost

  • Total license purchase = sum of Purchase price for all licenses registered for the application

  • Total maintenance cost and total support cost are based on all periods and for all licenses registered for the application.

Average cost per license (metric)

This cost is based on the metric of the application:

Total license cost / Total number of licenses

Note

This cost is only calculated for license purchases with the same metric as the application.

Risk

Shows the compliance discrepancy in cost for the application. Risk can be negative or positive depending on if the compliance is negative or positive. The risk is calculated as:

Average cost per license (metric) × Compliance

If no licenses are purchased for the application or if the registered licenses have different metrics than the metric of the application, then the risk is calculated as:

Application cost per metric × Compliance

Risk (unused software)

Shows the cost for unused software.

If licenses are purchased for the application AND the licenses have the same metric as the application:

Average cost per license (metric) × Number of unused installations

If no licenses are purchased for the application OR the licenses have different metrics than the application:

Application cost per metric × Number of unused installations

The risk also shows to what extent the application is used, displayed in percentage:

(Number of unused installations / Total number of installations) × 100