Bundled models

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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

    Bundled models in ServiceNow are templates that combine multiple individual asset models—such as a laptop, printer, keyboard, and mouse—into a single, manageable asset bundle. When assigned, any asset in the bundle assigns all components to the user. This functionality requires the Hardware Asset Management application, available in the ServiceNow Store.

    Show full answer Show less

    Bundled models maintain consistency between asset bundles and their templates by enabling the Bundle assets option in the Product Model form. This sets the bundled model status to Build, allowing edits. Changing the status to In Production locks the model, enabling creation of asset bundles. Reverting to Build is only possible if no asset bundles exist.

    Key Features

    • Abstract vs Concrete Bundles: Abstract bundles serve as reusable containers with a main component and multiple additional components, supporting many-to-many relationships. Concrete bundles have fixed components with an asset as the main component and do not support many-to-many relationships.
    • Nested Bundles: Bundles can contain other bundles, allowing complex asset groupings.
    • Assignment and State Management: Child assets inherit assignment and state from the parent bundle, with related fields set to read-only.
    • Model Categories: Control which asset types can be included in bundles and define main component eligibility.
    • Consumables and Transfers: Consumables in bundles are consumed alongside the main asset, and only entire bundles can participate in transfer orders—not individual components.
    • Publishing: Bundled models can be published to the product catalog, making them available in the service catalog for ordering.

    Practical Usage Tips

    • Use abstract bundles to create flexible, reusable asset combinations, such as a computer bundle with peripherals.
    • Use concrete bundles for fixed, exact asset groupings.
    • Model categories ensure compliance with organizational policies on what assets can be bundled.
    • Software collections should be created as suites, not bundled models; software licenses cannot be main components.
    • Modify bundles by adding or removing components as asset requirements evolve.

    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.