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 one asset from the bundle to a user means the entire set is assigned. Bundled models act as templates defining which assets form asset bundles, helping streamline asset management and assignment.

    Show full answer Show less

    This functionality requires the Hardware Asset Management (HAM) licensable application. Selecting the "Bundle assets" checkbox in the Product Model form enables this feature, setting the bundled model status to Build. While in Build status, you can modify the bundle; switching to In Production locks the model for edits and allows creation of asset bundles from it. The status can revert to Build only if no asset bundles exist for that model.

    Types of Bundled Models

    • Abstract Bundles: Serve as containers allowing reuse of one model in multiple bundles. They have a designated main component and additional components. Abstract bundles support many-to-many relationships and are more commonly used. For example, a computer as the main component with mouse and keyboard as additional parts.
    • Concrete Bundles: Fixed bundles with a specified main asset component and exact additional components. They do not support many-to-many model relationships and represent a precise asset grouping.

    Key Features and Usage Tips

    • Bundles can be nested within other bundles, using any asset model type.
    • Assignment and state fields for child assets in a bundle are read-only when a parent link exists; they inherit values from the parent bundle.
    • Assigning a bundle to a user automatically assigns all child assets to the same user.
    • Bundles cannot be pre-allocated.
    • Consumable assets in a bundle are consumed upon assignment, and asset states align with the main component.
    • Only the whole bundle can be included in transfer orders, not individual components.
    • Model categories control what assets can be included in bundles and define which asset can serve as the main component. For example, some categories might exclude servers from bundles.
    • Software collections require creating suites instead of bundled models, and software licenses cannot serve as main components.

    Managing Bundled Models

    • Creating an Abstract Model: Set the model category to "Bundle" and add components accordingly.
    • Creating a Concrete Model: Use Product Catalog > Product Model > Bundled Models to create and add components.
    • Adding Components: Modify bundles as needed to upgrade or expand asset sets.
    • Removing Components: Replace or remove components from bundles to maintain accuracy.
    • Publishing Bundled Models: Bundled models can be published to the product catalog to make them available in the service catalog for easy ordering.

    Practical Benefits for ServiceNow Customers

    This bundled model capability enables customers to efficiently manage and assign groups of related assets as single units, reducing administrative overhead and improving asset tracking accuracy. It ensures consistency by controlling bundle composition through model categories and provides flexibility with abstract and concrete bundle options. The integration with asset assignment and transfer processes supports streamlined lifecycle management of complex asset sets.

    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.