Create and manage a software suite

Create a suite and add the corresponding components to the suite so the rights that your organization owns are counted accurately during reconciliation.

Before you begin

Role required: sam_user or model_manager

About this task

A software suite is a group of related software offered as one unit. An example is the Microsoft Office Professional suite of office productivity software tools that includes PowerPoint, Word, Excel, Outlook, and Access.

For any software model, you have the option to specify whether the model is a suite (parent) or a component (child). A software model can be a component in multiple suites. For example, Microsoft Word is a component in Microsoft Office Standard and Microsoft Office Professional. Although you can set a single software model as both a suite and a component, software is not typically sold as nested suites.

Use the Inference percent and Mandatory fields for even greater control of suites.
  • Inference percent: specifies what percentage of the components in the suite must be installed for the software to be identified as a suite.
  • Mandatory: enforces whether a specific component in a suite must be installed to infer that the suite is installed. Choices are: Optional, Always Mandatory, Mandatory Group.

For example, say you specify the Inference percent as 80% and set the Mandatory field to Always Mandatory on Microsoft Access. These settings specify that Microsoft Access must be installed, along with three out of four other products (Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Outlook) to infer that Microsoft Office Professional is installed on a device.

When a suite parent is detected during reconciliation, the suite components do not count for the individual license.
Note: Users with the model_manager role can navigate to Product Catalog > Product Model > Software Models, but cannot administer all aspects of software models.

Procedure

  1. Navigate to Software Asset > Licensing > Software Models and open the software model record to add suite configuration to.
  2. Configure the software model as a suite parent or child.
    • To make the software model a suite parent, in the Suite Components related list, create a record to specify the child software model to include in the suite (see table for field descriptions).
      Table 1. Suite Components fields
      Field Description
      Inference percent The percentage of suite components that need to be present on a system to count as a suite. Used for suite management.

      Software installations on the same device and assigned to same user that meet the inference percent could be considered a suite.

      For example, if the inference percent for a suite of five products is set to 60% and three software installs on the same device, or assigned to the same user, are discovered, all three installations are considered a suite.

      Suite child The child product or products of the suite. For example, Microsoft Word and Microsoft Excel are child products of Microsoft Office.
      Mandatory Determines whether a suite component is optional, mandatory, or part of a mandatory group.

      Set to Always Mandatory if the software must be installed to count the model as a suite.

    • To make the software model a suite child item, in the Suite Parents related list, create a record to add the parent software model to which this software must belong (see table for field descriptions).
      Table 2. Suite Parents fields
      Field Description
      Suite parent The parent suites to which the software is assigned. For example, the parent suite for several common Microsoft products is a version of Microsoft Office.
      Mandatory Determines whether a suite component is optional, mandatory, or part of a mandatory group.

      Set to Always Mandatory if the software must be installed to count the model as a suite.