- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 10:01 AM
Let's assume I'm creating an power adapter consumable record, for 10 proprietary power adapters. I want to track these for inventory purposes to enable a user to scan out a quantity, and have the system notify me, and update qty in the system/record. I have a few questions:
- When creating the consumable, what is the significance of a model category?
- What is the significance of the consumable model?
- How does selecting multiple model categories (when creating a new consumable model) help/hinder?
- After creating both of these items, and attempting to create a consumable, I have to select "model" first in order to see selectable options. Otherwise, if I select a "model category" first, "model" will return no results. Is this correct behaviour?
Thanks
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 11:40 PM
Hi 6-string,
Some direct answers to your questions in your use case:
For each item you have to track on qty (consumable) or on individual item (asset) a Product Model should be created: In this case for each connector and adapter a Product Model with Product Model category = Consumable should be created.
Why: To distinguish the involved item (connector / adaptor) and to track these items as consumables: Track based on item quantities.
The consumables tab in this form will give you a list of users or assets where the involved item was assigned to: Monitoring on consumables users / assets is possible in this way.
By defining stock rules (one rule for every involved Product Model in every involved Stockroom) you can automate the reordering proposal of an item in case minimum stock levels are reached. With this proposal you can decide to re-order items by using the procurement process.
Hope this helps.
Ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 11:43 AM
Hi
1)Model categories associate CI classes with asset classes. Model categories are part of the Product Catalog application.
Model definitions can be based on vendor-provided criteria, for example, the manufacturer name Apple MacBook Pro, or on a custom abstraction, for example, Graphic Designer Workstation. All model information is located in the Product Catalog application.
A model can be in one or more model categories. For example, a laptop can be a computer and a server. Model definitions specify whether the model creates an asset, a configuration item, or both. On a hardware model record, compatible hardware models can be added.
Unless otherwise noted, working with product models requires the model_manager role. This role is contained by other roles, such as sam, category_manager, and asset.
4)The base system provides a model category for each CI class in the CMDB. As you create cmdb_ci classes, create a corresponding row in the model category table for the model table to be used.