Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Add a software model

Log in to subscribe to topics and get notified when content changes.

Add a software model

Software models are used to connect purchased software rights with discovered software installations. Additionally, software models can be used to manage suites of software as well as to publish requestable software to the Service Catalog.

Before you begin

Role required: sam_user or model_manager

About this task

Manage software available and tie software installations (software being used) with entitlements (software owned) using software models. Create software models for all software to be monitored.
Note: Users with the model_manager role can navigate to Product Catalog > Product Model > Software Models, but cannot administer all aspects of software models.

Predefined suites are used so suite components are automatically created for known suite parent software models. Discovery maps indicate whether a suite is defined for the product.

You can also track a software model lifecycle phase for use with the Technology Portfolio Management.

Note: Any install condition added to a software model will be used on the software model level. Unlicensed installs are aggregated to the product results level, which ignores the install condition of the software model.


  1. Navigate to Software Asset > Licensing > Software Models and create a new record (see table for field descriptions).
    Table 1. Software Model form
    Field Description
    Display name [Read-only] Name of the model. The system property glide.cmdb_model.display_name.shorten controls how software model display names are generated. System administrators can configure this property.

    Default format is publisher + product + version + edition + platform + language.

    Platform and language values are appended if they are not set to --Anything--.

    Publisher Publisher of the software. You can use the lookup list provided.
    Note: Publisher is a reference to the company [core_company]. Only companies you are using internally are shown.
    Product Software product name. The same lookup list provided on the Software Discovery Models form. You can create a custom product from the lookup list, if desired.
    Note: If the relationship between the software publisher [samp_sw_publisher] and company [core_company] is not correct, products for that publisher may not be shown.

    If the publisher and product do not exist, you can Add a custom software product.

    Product classification [Read-only] The official UNSPSC classification.
    Product type [Read-only] Product type values include: Child, Driver, Licensable, Not Licensable, Patch, and Unknown.
    Note: The reconciliation process only considers software discovery models that are licensable.
    Short description A brief description of the model.
    Cost The cost of a single unit of the software.
    Next version Reference to another software model of the same manufacturer which represents the next version of the product.
    Owner The person responsible for the model.
    Status The current status of the model. Options are In Production, Retired, and Sold.
    Certified Check box for indicating the software model has been approved for use.
    Blacklisted Check box for blacklisting the software model.

    Blacklisting identifies software that should not be installed in your environment (inappropriate software, or software with vulnerabilities, for example).

    A scheduled job runs nightly that creates removal candidates for blacklisted software if they do not already exist.

    Discovery Mapping
    Discovery map A predefined set of conditions that determine which software discovery models get mapped to which software models. Purchased rights are only applied to software discovery models that meet the condition. This matching is important for reconciliation.

    Discovery models with predefined suites are indicated in the Suite defined field. A value of Yes indicates that the discovery model is a suite parent.

    You can use the discovery maps provided, or you can choose to specify the condition information directly instead.
    Note: A user with the sam_admin role can choose to create a custom discovery map.

    If the discovery map has a lifecycle definition defined, those settings are automatically populated in the Software Model Lifecycles related list.

    You can verify which discovery models get mapped to the software model by clicking the Show Matching Discovery Models related link.

    If the Publisher and Product fields are empty, the values are automatically populated according to the discovery map.

    Version condition Condition qualifier for the Version field.
    • starts with
    • is
    • is anything

    Default is is anything.

    Version Version of the software product.

    Required if version condition value is starts with or is.

    Edition condition Condition qualifier for the Edition field.
    • starts with
    • is
    • is anything

    Default is is anything.

    Edition Edition of the software product to use when searching for the normalized discovery model.

    Required if edition condition value is starts with or is.

    Platform Platform of the software product to use when searching for the normalized discovery model.

    Default is --Anything-- for Windows, Mac, Unix.

    Language Language of the software product to use when searching for the normalized discovery model, which is populated once it has been normalized or added manually.

    Default is --Anything--.

    Software installation condition Only software installations that meet this software discovery map condition are counted during reconciliation.

    If needed, specify a subset of software installations that should be counted during reconciliation.

    Product Catalog
    Catalog Item The information about the model as it appears in the product catalog and service catalog.

    Information only appears if the model has been published to the product catalog.

    Description Description of the software model as it appears in the product catalog.
    Picture An image of the software logo can be added. This logo appears in the Service Catalog if the software model is published.

    The Suite Components and Suite Parents related lists consist of parent and child software suite configuration.

  2. To publish the software model to the product catalog, under Related Links, click Publish to Software Catalog and select a category for the software model.
    The values set in the Product Catalog related list are published.
  3. To show the list of discovery models that match the software publisher and product fields of the software model, under Related Links, click Show Matching Discovery Models.
    The Discovery Models list is opened in a new browser tab for your reference.
  4. To perform additional configuration, select the new software model record in the Software Models list.
    1. In the Software Model Lifecycles related list, create a new record (see table for field descriptions).
      Table 2. Software Model Lifecycle form
      Field Description
      Software model [Read-only] Name of software model.
      Lifecycle type
      • Internal
      • Publisher
      Lifecycle phase
      • Pre Release
      • General Availability

        Date the software became generally available to the market.

      • Upgrade

        Only shown when the Lifecycle type field is Internal.

      • End of Life

        Date the software was no longer supported by the publisher.

      • End of Support
      • End of Extended Support
      Source [Read-only] Internal (for new records created manually), or ServiceNow (when created automatically).
      Description Description of the software model lifecycle.
      Phase start date Date the lifecycle phase starts.
      Phase end date Date the lifecycle phase ends.
      • Very High
      • High
      • Moderate
      • Low
      • None
    2. Add a software entitlement.
    3. View software model results. The latest software model results are shown in the Software Model Results related list.
    4. In the Metric Attributes related list, click a metric attribute to set the attribute value field (see table for field descriptions).
      The Metric Attributes related list contains metric values set in software entitlements and is used for reconciliation (metric group, license metric, and software model combination).

      For more information, see Software license metrics.

      Table 3. Metric Attributes form
      Field Description
      Software model Software model associated with the metric attributes.
      Metric group Grouping for the software metric.

      If you have optional publisher packs installed that the software applies to, those options are shown. Otherwise, the metric group value is Common.

      License metric The license metric that the software license is counted against when reconciliation is run (per user, per device, for example).
      Description Attribute type description that is based on license metric value.
      Attribute Attribute type for reconciling entitlements license metric.
      • Maximum active OSEs per server
      • Maximum installs per OSE
      • Maximum installs per right: For Per User, Per Device, Per Named User, and Per Named Device.
      • Maximum processors per right
      • Minimum users per processor
      • Minimum cores per processor
      • Minimum cores per server
      Attribute value Value of the attribute (integer).
      Attribute value is unlimited Check box for setting the attribute as unlimited.
    5. Create a vendor catalog item.
    6. Add a software client access record.