Bundled models

Release version: Zurich

Updated July 31, 2025

2 minutes to read

Summarize

Summarized using AI

Summary of Bundled models

Bundled models in ServiceNow are single models composed of multiple individual models, such as a laptop, printer, keyboard, and mouse combined into one asset bundle. Assigning any asset from the bundled model assigns the entire bundle to the individual. Bundled models act as templates defining which assets form asset bundles, ensuring streamlined management and assignment of grouped assets.

Show full answer Show less

The Bundle assets check box in the Product Model form enables bundled model functionality and is available only with the Hardware Asset Management application from the ServiceNow Store. When this box is selected, the bundled model’s status defaults to Build, allowing modifications. Changing the status to In Production makes the model read-only, enabling creation of asset bundles from it. The status can revert to Build only if no asset bundles are linked.

Key Features

Abstract Bundled Models: Serve as containers allowing reuse of one model in multiple bundles. They designate a main component to facilitate tracking. For example, a computer as the main component with mouse and keyboard as additional components. Abstract bundles are common and support many-to-many relationships.
Concrete Bundled Models: Represent fixed bundles with a specified main component and exact components. They do not support many-to-many relationships.
Nested Bundles: Bundles can contain other bundles, allowing complex asset groupings.
Assignment and State Inheritance: When a parent bundle is assigned or its state changed, child assets inherit these attributes and related fields become read-only.
Model Categories: Control which assets can be included in bundles and define allowable main components. For instance, servers can be restricted from inclusion in bundles.
Consumables and Transfers: Consumables in a bundle are consumed on assignment, and asset states mirror the main component. Only entire bundles can be transferred—not individual components.
Software Restrictions: To group software, create suites instead of bundled models. Software licenses cannot be main components in bundles.

Managing Bundled Models

Creating Abstract Bundles: Set the model category to Bundle and add components accordingly.
Creating Concrete Bundles: Use the Product Catalog > Product Model > Bundled Models module to define components and the main asset.
Adding or Removing Components: Modify bundled models during the Build status by adding or removing components to reflect changes such as upgrades or replacements.
Publishing to Product Catalog: Bundled models can be published to the product catalog to be available in the service catalog for user requests.

Practical Considerations for ServiceNow Customers

Bundled models simplify asset management by grouping related hardware into a single assignable entity.
Maintaining bundle integrity is critical; changes to parent bundles cascade to child assets.
Use model categories to enforce governance on which assets can be bundled, ensuring compliance with organizational policies.
Hardware Asset Management licensing is required to enable bundled model features.
Understanding the difference between abstract and concrete bundles helps optimize asset lifecycle and assignment strategies.

A bundled model is a single model comprised of individual models. For example, a laptop, printer, keyboard, and mouse can be combined into a single bundled model. If you assign any one asset from the bundled model to an individual, that person receives all the components in the bundle.

Bundled model is a template to define the kind of assets that would be a part of asset bundles. To maintain the integrity between asset bundles and bundled models, select the Bundle assets check box in the Product Model form layout. Once you select the check box, the status of the bundled model defaults to Build. While the status is in build, you can add make changes to the bundled model. Once you change the status to In Production, no changes can be made to the bundled model. Now that the bundled model is read-only, you can create asset bundles out of this bundled model. You can change the status of the bundled model back to Build only if there are no asset bundles associated with the bundled model.

Note:

The Bundle assets check box functionality is available only with the Hardware Asset Management licensable application. Hardware Asset Management is available in the ServiceNow Store. To view more information on the asset bundle functionality, see asset bundles.

Bundled models can be abstract or concrete.

Abstract: Permits use of one model in multiple bundles. The abstract bundle is created as a container. One asset in the bundle is specified as the main component. Model categories define which assets can be included in a bundle. Model categories also define what can be the main component of a bundle.
Add a main component to make it easier to track the bundle components. For example, create an abstract bundle adding a computer as the main component and a mouse and keyboard as additional components. When the bundle is assigned to a user, the asset record for the computer shows the computer, mouse, and keyboard all assigned to the user. Abstract bundles are used more often than concrete bundles.
Concrete: Is a fixed bundle where the main component is an asset. Specify the main component and the other components to create an exact bundle. Concrete bundles do not allow for a many-to-many relationship with models.

Keep the following tips in mind when creating and using bundled models.

Bundles can be nested inside bundles.
Any type of model can be used in a bundle.
When a parent link is defined, the fields related to assignment and state of the child assets are read-only. They are populated based on the parent's assignment and state fields.
If you make a change to the parent bundle, the children in the bundle are affected. For example, if you assign a bundle to an individual, all child asset records show that same individual as the person assigned.
You cannot pre-allocate bundles.
In a bundle, consumables are consumed and assets are set to the same state as the main component.
Only the bundle, not individual components, can be part of a transfer order.
You control what can go into a bundle through the model category. For example, the model category Servers could be set to never allow servers in bundles.
To create a collection of software, you must create a suite instead of a bundled model.
A software license cannot be the main component of a bundle.

To create an abstract model, set the model category to Bundle and add the components. To create a concrete model, create a model in the Product Catalog > Product Model > Bundled Models module and add components.