1

Business Unit

Select the business unit to which the software license belongs

2

Product Type

Select the appropriate product type:

Bundle - refers to software that is sold with a hardware component. For example, Microsoft Windows comes with many bundled software tools

Suite - software suite is a collection of programs usually application software or programming software of related functionality often sharing a common user interface with some ability to smoothly exchange data with each other. Example - Microsoft Office Suite

3

Manufacturer

This field refers to the manufacturer of the software. This field is not supported for bundle and OS product types.

4

Product

Select the product for which the license is added

Note: Click '' to add a new product. Product type suite software can be added from Settings > Asset and Inventory Management > Software Normalization

5

Edition

Version

Select the edition and version of the software product. Edition and version is listed only if it is collected during inventory collection as the edition and version is present with the product name. But for software such as MSSQL and Oracle, these fields are captured separately.

6

Product Key

Enter the unique product key received on purchase of the software to certify that the software product copy is original

7

Product SKU

Product Stock keeping unit which is the number of the specific product available for sale. If a hardware device or software package comes in different versions, there is an SKU for each one

8

License Metric

This field is provided to define how a particular product is licensed. When adding a license metric, the following information has to be provided:

Metric Name - unique name for the license metric

Metric Behavior - parameter on which the license metric is based (core count, device, device CAL, processor core count, processor count, user, user CAL)

• Device - License is machine based - one device can have only one license

• Device CAL - With a device CAL, you purchase a CAL for every device that accesses your server regardless of the number of users who use that device to access the server

• User - License is assigned to a named user who must be identified to ensure the license agreement is validated and the license terms are adhered to

• User CAL - With a user CAL, you purchase a CAL for every user who accesses the server to use services such as file storage or printing, regardless of the number of devices they use for that access.

• Core Count - Here, the number of licenses required equals the number of physical cores on the server multiplied by the applicable core factor.

• Processor Count - A license based on the number of CPU/Processor sockets on which the software will run, and not the logical processors aka cores

• Physical Core Count/Physical Processor Count - is the same as core count/processor count but it is applicable for virtual machines where software on the guest machine needs to be licensed for the number of processors/cores in the VM host where the guest is running

Consider Threads - Check this box if the license has to be considered for individual threads in case of core/processor count

Minimum Quantity - of the above selected behavior to be used

Maximum Quantity - of the above selected behavior to be used

Minimum License Quantity - minimum number of licenses that can be applied on a single machine

Factor Type - Multiplying factor or core factor for the processor or core count. Multiplying factor specifies the number of licenses to be provided per processor/core/thread. For example, if each processor has to be licensed with count two for a product, then multiplying factor is two . If you are running the product in four processor machines, then the total number of licenses to be applied = Number of processors * multiplying factor = 4*2=8

If core factor is selected, you need to enter the core factor for each processor name

Important: Software license reconciliation is supported for Device, Core, Processor, Physical Core and Physical Processor metric only. This may be user defined metric or pre-shipped license metric.

9

License Model

Specify whether the license is base or upgrade license. The following license models are pre-shipped:

Base License - License to use a particular product. Later if newer version of the product is released, it can be upgraded by purchasing an upgrade license to it

License Only - License to use a particular product

License With Maintenance -  License to use a particular product with additional benefit of maintenance

Maintenance Only - For one product, if maintenance alone is purchased separately, this model can be used. It should be linked to the corresponding base license, for which it will act as a maintenance license

Step Up License - Step Up License is a type of upgrade license where the user migrates from a lower edition of a particular product to its higher edition without incurring full cost of licensing two separate editions of software.

Step Up License With Maintenance - similar to Step Up License with additional benefit of maintenance

Subscription License - is generally an annual or multi-year software license that combines the right to use the software with the rights to obtain software updates and service

Upgrade License - License to upgrade from an existing version of a product. In order to purchase upgrade license, there should be a base license for the earlier version of the same product.

Upgrade License With Maintenance - similar to Upgrade License with additional benefit of maintenance.
Upgrade Plan - Upgrade Plan is similar to upgrade license. This term is generally used in Adobe Volume Licensing

10

License Source

This field indicates how the license was issued to the customer by the vendor. The following license sources are pre-shipped:

1. Enterprise Agreement (EA)

2. Full Packaged Product (FPP)

3. Original Equipment Manufacturer (OEM)

11

Country of usage

Select the country where the license will be used

12

Environment

Organizations can internally have various environments and can define a license record which can be used under a specific environment such as testing or development environment. Some of the important environments are pre-shipped

13

Agreement Name

Select the agreement from the drop down list if any

14

License Start

Select the license start date

15

License End

Select the license end date or check the box if the license is a perpetual license

16

License Quantity

Enter the license quantity  or check the box if the license is unlimited

17

Maintenance Start

Maintenance End

Select the maintenance start and end dates

18

Maintenance Quantity

Enter the maintenance quantity or check the box if the maintenance quantity is unlimited

19

Purchased Cost

Enter the purchase cost of the license in the respective currency

20

Purchase Order(s)

Select the corresponding purchase orders for the license