---
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 individual asset models, such as a laptop, printer, keyboard, and mouse combined into one bundle.
When any asset from a bundled model is assigned to a user, all components within that bundle are assigned together.
Bundled models serve as templates defining the asset components in a bundle and require enabling theBundle assetsoption in the Product Model form, which is part of the Hardware Asset Management application available in the ServiceNow Store.
Show full answer Show less  

## Key Features

* **Status Management:** Bundled models have statuses---*Build* for editing and *In Production* for read-only. Changes can only be made when in Build status and if no asset bundles exist when switching back from In Production.
* **Abstract vs. Concrete Bundles:**
  * **Abstract bundles** act as containers allowing one model to be reused in multiple bundles. They specify a main component (e.g., a computer) and additional components (e.g., mouse, keyboard), facilitating assignment tracking.
  * **Concrete bundles** are fixed bundles with a specified main asset and components; they do not support many-to-many relationships.
* **Model Category Control:** The model category governs which assets can be included in bundles and which can serve as main components (e.g., servers might be excluded).
* **Bundle Behavior:** Bundles can be nested, and changes to a parent bundle affect all child assets. Assignment and state fields of child assets are read-only and mirror the parent bundle's details. Consumables within bundles are consumed, and assets take on the main component's state. Only the entire bundle can be transferred, not individual components.
* **Software and Licensing:** Software collections require suites instead of bundled models, and software licenses cannot be main components of bundles.
* **Management Functions:** You can add or remove components from bundled models to update or replace assets as needed. Bundled models can be published to the product catalog for availability in the service catalog.

## Practical Implications for ServiceNow Customers

Using bundled models allows efficient asset assignment by grouping related hardware into a single bundle, simplifying asset lifecycle management and tracking. The distinction between abstract and concrete bundles provides flexibility in how assets are grouped and reused. Control over model categories ensures compliance with organizational policies on asset bundling. Status controls ensure that bundles are stable when in production, preventing unintended changes. Publishing bundled models to the product catalog streamlines service catalog management and asset provisioning.  
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