Create a Software Asset Management Foundation software model in workspace

task australia Updated Sep 10, 2026 5 min read Create-samf-software-model-workspace.md
Raw file servicenow.com

Create a software model in the Software Asset Workspace to add product details that are used to connect software rights you purchased with software installations discovered on your system.

Before you begin

Role required: sam_user, sam_admin, or model_manager

Procedure

  1. Navigate to All > Software asset > Software Asset Workspace > License operations.

  2. Under Licensing, select software models.

  3. Select New.

  4. On the form, fill in the fields.

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.

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’re using internally are shown.

If the publisher and product don’t exist, you can Add a Basic Software Asset Management custom license metric.

Product

Software product name. The same lookup list provided on the Software Discovery Models form.Note: If the relationship between the software publisher [samp_sw_publisher] and company [core_company] isn’t correct, products for that publisher may not be shown.

Product classification

The official UNSPSC classification of the product.

Product type

  • Child: A subcomponent of main software (not licensable).
  • Driver: A software product that controls a device.
  • Licensable: A software product that is licensable.
  • Not Licensable: A software product that is not licensable.
  • Patch: A software product designed to update, fix, or improve an existing computer program.
  • Unknown: Not discovered.

General

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 that represents the next version of the product.

Owner

The person responsible for the model.

Status

The status of the model. Options are In Production, Retired, and Sold.

Certified

Check box for indicating the software model has been approved for use.

Discovery Mapping

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 configuration.
**Note:** If you have added a discovery map to your product details, predefined suites are used and suite components are created automatically for known suite parent.
  1. To publish the software model to the product catalog, under Related Links, select Publish to Software Catalog and select a category for the software model.

    The values set in the Product Catalog related list are published.

  2. To show the list of discovery models that match the software publisher and product fields of the software model, under Related Links, select Show Matching Discovery Models.

    The Discovery Models list is opened in a new browser tab for your reference.

  3. 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 record (see table for field descriptions).

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.

Risk

  • Very High
  • High
  • Moderate
  • Low
  • None
2. [Create a SAM Foundation entitlement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/software-asset-management-foundation-plugin/t_AddASoftwareEntitlementSAMF.md).
3.  [View Basic Software Asset Management software model results in classic](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/software-asset-management-foundation-plugin/t_ViewSWModelResultsSAMF.md).

    The latest software model results are shown in the Software Model Results related list.

4.  In the Metric Attributes related list, select a metric attribute to set the attribute value field \(see table for field descriptions\).

    The Metric Attributes related list contains metric values set in [Create a SAM Foundation entitlement](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/software-asset-management-foundation-plugin/t_AddASoftwareEntitlementSAMF.md) and is used for reconciliation \(metric group, license metric, and software model combination\).

Field

Description

Software model

Software model associated with the metric attributes.

Metric group

Grouping for the software metric (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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/product-catalog/t_CreateAVendorCatalogItem.md).

Parent Topic:Configuring Basic Software Asset Management workspace

Search documentation
Search document titles and file paths on the australia branch