Bundled models

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 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 and which 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 other 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.
Hardware and consumable models can be used in a bundle. Software and contract models cannot 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.
Taking action on the parent bundle affects the children in the bundle. 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 master 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 master component of a bundle.

To create an abstract model, set the model category to Bundle and add components. To create a concrete model, create a model in the Product Catalog > Product Model > Bundled Models module and add components.

Bundled models

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 and which 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 other 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.
Hardware and consumable models can be used in a bundle. Software and contract models cannot 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.
Taking action on the parent bundle affects the children in the bundle. 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 master 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 master component of a bundle.

How search works:

Topics are ranked in search results by how closely they match your search terms

Bundled models

Bundled models

On this page

Bundled models

Bundled models

Log in to personalize your search results and subscribe to topics