Bundled models

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 model composed of multiple individual asset models grouped together—such as a laptop, printer, keyboard, and mouse combined into one bundle. Assigning any asset in the bundle to a user assigns all bundled components collectively. Bundled models serve as templates defining which assets form part of an asset bundle.

    Show full answer Show less

    This functionality is available exclusively with the Hardware Asset Management licensable application from the ServiceNow Store.

    Key Features

    • Bundle assets checkbox: Selecting this in the Product Model form enables bundle functionality, sets the bundled model status to Build, allowing edits. Changing status to In Production locks the model for asset bundle creation. Status can revert to Build only if no bundles exist for the model.
    • Abstract vs. Concrete Bundled Models:
      • Abstract: Acts as a container allowing one model to appear in multiple bundles. One main component is specified for easier tracking. Commonly used for flexible bundle definitions.
      • Concrete: A fixed bundle with a specified main asset component and exact components. Does not support many-to-many relationships between models.
    • Model categories: Control which assets can be included in bundles and which can serve as main components, helping enforce compliance and bundle integrity.
    • Nested bundles: Bundles can include other bundles, supporting complex asset groupings.
    • Assignment and state management: When a parent bundle is assigned or its state changes, child assets automatically reflect those changes, and related fields become read-only to maintain consistency.
    • Transfer and consumption rules: Only entire bundles can be transferred; consumables within bundles are consumed and inherit the main component’s state.
    • Publishing: Bundled models can be published to the product catalog, making them available in the service catalog for ordering.

    Practical Guidance for ServiceNow Customers

    • Use bundled models to simplify asset assignment and lifecycle management by grouping related assets into a single assignable entity.
    • Decide between abstract (flexible, reusable) and concrete (fixed) bundles based on your organizational asset allocation needs.
    • Ensure model categories are configured correctly to control bundle composition and maintain data integrity.
    • Make edits to bundled models only when in Build status and no dependent bundles exist, to avoid data conflicts.
    • Note that software collections require suites rather than bundled models, and software licenses cannot be main components of bundles.
    • Leverage nested bundles for complex asset assemblies, and understand that state and assignment flows from the bundle to its components.
    • Use the Hardware Asset Management application to access and manage bundled model functionality effectively.

    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.