Why doesn't all the CI classes map to a model category?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-29-2024 09:55 AM
It seems there are many CI classes that do not map to a model category. Should they and if there are marked in the hardware category shouldn't' they definitely have an asset class additionally associated through the model? For example I see Out of Band Device listed under hardware in the CI Class manager but no mapping in the model category table to a CI class or Asset Class. Can anyone explain further how these items should be mapped? Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-29-2024 12:11 PM
There are many infrastructure components which are tracked as both Assets and CIs. These are the model categories which will have both asset class and CI class. But some are only CIs and not assets. These model categories will only have a CI class associated with them. Some are only assets are not CIs. These model categories will only have an asset class associated with them.
If you want to track technical specifications and raise incidents, problems & changes for a component, then it needs to be tracked as a CI. Anything for which you need to track the inventory, contractual, financial or warranty details should be considered as an asset. Based on these considerations, organizations can decide whether something should be treated as an asset or a CI or both.