Bundled models

  • Release version: Xanadu
  • Updated August 1, 2024
  • 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 multiple individual models, such as combining a laptop, printer, keyboard, and mouse into one asset bundle. Assigning any asset from the bundle to a user assigns all components collectively. Bundled models act as templates defining which assets belong in a bundle and require selecting theBundle assetscheckbox in the Product Model form to enable bundle functionality.

    Show full answer Show less

    The status of a bundled model controls editing: when set to Build, changes are allowed; switching to In Production makes the model read-only and enables creating asset bundles from it. The status can revert to Build only if no asset bundles are linked.

    This feature is accessible exclusively with the Hardware Asset Management application, available through the ServiceNow Store.

    Key Features

    • Abstract vs. Concrete Bundled Models:
      • Abstract: Acts as a container allowing one model to be used in multiple bundles. It designates a main component to simplify tracking. Model categories control allowable components and main assets. Abstract bundles are more common.
      • Concrete: Fixed bundle with a specified main component asset and exact components, without supporting many-to-many relationships.
    • Nested Bundles: Bundles can include other bundles as components, supporting complex configurations.
    • Assignment and State Inheritance: Child asset assignment and state fields become read-only when linked via a parent bundle, reflecting the parent’s status and assignee.
    • Consumables and Transfers: Consumables in bundles are consumed, and all assets adopt the main component’s state. Only entire bundles can be part of transfer orders, not individual components.
    • Model Categories: Control what asset types are allowed in bundles, preventing incompatible assets, such as disallowing servers in bundles.
    • Software Licensing: Software licenses cannot be main components of bundles; software collections require suites instead.
    • Component Management: Components can be added or removed from bundled models to reflect changes like upgrades or replacements.
    • Publishing: Bundled models can be published to the product catalog, making them available in the service catalog for users to request.

    Practical Guidance for ServiceNow Customers

    • Use bundled models to efficiently manage and assign groups of related hardware assets as a single unit.
    • Leverage abstract bundles for reusable configurations with flexible component use, and concrete bundles for fixed, defined asset sets.
    • Ensure your model categories are properly configured to enforce what assets can be bundled.
    • Remember that once bundles are in production and associated with asset bundles, you cannot modify them, so plan carefully before publishing.
    • Use the Hardware Asset Management application to enable and manage bundled models, as it is required for this functionality.

    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.