---
sourceDocument: Yokohama IT Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-asset-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Bundled models

# Bundled models {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Bundled models

A bundled model in ServiceNow is a single composite model made up of multiple individual asset models, such as combining a laptop, printer, keyboard, and mouse into one bundle.
Assigning any asset from the bundle to a user results in all components being assigned to that user.
Bundled models act as templates to define the assets included in asset bundles, helping streamline asset assignment and management.
Show full answer Show less  

## Key Features

* **Bundle assets checkbox:** Available with the Hardware Asset Management application, this checkbox on the Product Model form marks a model as a bundled model, changing its status to *Build* for editing, and then to *In Production* to make it read-only and ready for asset bundle creation.
* **Abstract vs. Concrete Bundled Models:**
  * **Abstract:** Acts as a container allowing one model to be part of multiple bundles, with a designated main component for tracking (e.g., computer as main, mouse and keyboard as components).
  * **Concrete:** A fixed bundle with a specific main asset and defined components, without many-to-many relationships.
* **Nested bundles:** Bundles can contain other bundles, enabling complex asset groupings.
* **Assignment and state inheritance:** Child assets inherit assignment and state fields from the parent bundle, ensuring consistency.
* **Bundle restrictions and controls:** Model categories control which assets can be bundled; consumable assets follow the main component's state; only bundles (not individual components) can be part of transfer orders.

## Practical Guidance for ServiceNow Customers

* Use bundled models to simplify asset management by grouping related assets for assignment and tracking.
* Ensure the "Bundle assets" checkbox is selected to activate bundled model functionality and manage lifecycle status properly.
* Create abstract bundles to reuse common asset groups across multiple bundles or concrete bundles for fixed asset combinations.
* Update bundled models by adding or removing components as business needs evolve, but only when the status is in *Build* and no asset bundles exist for that model.
* Publish bundled models to the product catalog to enable end users to request bundled assets through the service catalog.
* Note that software collections require suites, not bundles, and software licenses cannot be main components in bundles.

## Expected Outcomes

By leveraging bundled models, you can efficiently manage complex asset combinations, ensure consistent assignment and lifecycle status across related assets, and streamline asset provisioning processes. This reduces administrative overhead and improves asset tracking accuracy within your organization.  
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](https://www.servicenow.com/docs/_mj2pxsqCHxaihQiVBJyyw "Asset bundles help you bundle a group of assets, already in your inventory, as a single entity.").  
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.
{#c_CreatingBundledModels__ul_bly_zvj_54}

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 CatalogProduct ModelBundled Models module and add components.
* **[Add model components to a bundle](https://www.servicenow.com/docs/NPuSSyC2uLuSX1TEd8NGRQ)**   
  Add model components to a model as needed, for example, when you upgrade a bundle to include additional assets.
* **[Remove model components from a bundle](https://www.servicenow.com/docs/UvpaYMYJw5NMeWrOUBE9~A)**   
  Remove a component from a bundled model, for example, when you want to replace it with a different component.
* **[Publish bundled models to product catalog](https://www.servicenow.com/docs/zk4gJFK41PesDgMoNVxecw)**   
  You can publish bundled models to the product catalog to make the bundled models available in the service catalog.

**Related concepts**   

* [Model categories](https://www.servicenow.com/docs/CpIGVZh9x0gJ670omM_SfQ "Model categories associate CI classes with asset classes. Model categories are part of the Product Catalog application.")  
**Related tasks**   

* [Create pre-allocated assets](https://www.servicenow.com/docs/K62ipORpdwCb_yp0cFc7rw#t_CreatingPreAllocatedAssets "Create a pre-allocated asset that physically exists, but isn’t yet a financial liability.")
* [Consume consumable assets](https://www.servicenow.com/docs/lZfox8BIkaP5UTeUZI9Nbg "To consume consumable assets, they must have a state of In Stock and a substate of Available.")

*[\>]: and then