You can use software bundle management to optimize the processor value unit (PVU) calculation and generate accurate audit reports by correctly confirming or assigning component instances to products.
The agents during software scans discover components. Each component may be a part of one or more software products and the same component may also be a part of different products. Moreover, every product can be made up by one or more components, as you may see from the examples below:
The pricing of a given component depends on the product with which it is associated. For example, you may be entitled to use Database component for free if it is bundled with Product 1. However, if it is bundled with Product 3, you may have to pay for it. Because of this fact, you should bundle the discovered components with the chosen products in such a way that the associations between them reflect the actual software inventory.
The default bundling rule
After the discovery of new components, by default, the server automatically associates component instances with products, following this rule:
The component is associated with the simplest product that contains it, that is the product consisting of the lowest number of components. Instances associated in this way are referenced to as unconfirmed instances. This is to differentiate between the instances automatically assigned to a product by the Tivoli® Asset Discovery for Distributed server, and the ones that have been explicitly created by you through the Manage Software Bundles wizard. You may see an example of how the default bundling rule works below:
- Confirming instances in default products.
- Assigning instances from a default product to a different product.
- Reassigning instances from one product to another.
- Adding instances to a product.
- Removing instances from a product.
Concept topic
)