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

    A bundled model in ServiceNow is a single composite model made up of individual asset models, such as combining a laptop, printer, keyboard, and mouse into one bundle. Assigning any asset from this bundle to a user assigns all components together. Bundled models serve as templates that define which assets form an asset bundle.

    Show full answer Show less

    The "Bundle assets" checkbox on the Product Model form activates bundled model functionality and locks the model in a "Build" status for editing. Once set to "In Production," the model becomes read-only, allowing creation of asset bundles from it. The status can revert to "Build" only if no asset bundles are linked.

    This feature requires the Hardware Asset Management application available from the ServiceNow Store.

    Key Features

    • Abstract vs. Concrete Bundled Models:
      • Abstract: Acts as a container allowing one model to be used in multiple bundles with a designated main component (e.g., computer as main with mouse and keyboard). The main component simplifies tracking and assignment.
      • Concrete: A fixed bundle with a specific main asset component and other exact assets. Does not allow many-to-many model relationships.
    • Nested Bundles: Bundles can contain other bundles.
    • Assignment and State Propagation: When a parent bundle is assigned or its state changes, all child assets inherit those attributes and related fields become read-only on child records.
    • Model Categories: Control which assets can be included in bundles and what can be main components. For example, some categories like Servers can be excluded from bundles.
    • Consumables Handling: Consumable assets in bundles are consumed together, and asset states align with the main component.
    • Transfer and Pre-allocation: Only the entire bundle can be transferred, not individual components. Bundles cannot be pre-allocated.
    • Software Bundles: Software collections require creating suites, not bundled models; software licenses cannot be main components.

    Practical Guidance for ServiceNow Customers

    • To create an abstract bundled model, assign the model category "Bundle" and add components with a main component specified.
    • To create a concrete bundled model, use the Product Catalog > Product Model > Bundled Models module to define main and additional components.
    • You can add or remove model components from an existing bundled model to reflect upgrades or replacements.
    • Publish bundled models to your product catalog to make them accessible in your service catalog for end users.

    Benefits

    Bundled models simplify asset management by grouping related hardware into a single assignable unit, ensuring consistent tracking, assignment, and lifecycle management. This improves inventory accuracy, streamlines asset assignment processes, and enforces bundle integrity through controlled model categories and states.

    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.