Getting Started with Asset Management

Asset Management brings your CMDB, asset lifecycle, financial attributes, and discovery integrations into one workspace. This page orients you and points you to the right starting task.

The workspace

Asset Management combines a CMDB, the configuration items and the relationships between them, with lifecycle management from procurement through retirement, technical and financial attributes, and integration with your discovery tools. Everything lives in a single workspace, organized into tabs:

• Reports: the CMDB Health dashboard, covering duplicate candidates, check-in freshness, field population, and relationship coverage.
• Configuration Items: the inventory of every tracked instance, filterable by view and by Active or Inactive.
• CI Rules: automation rules that keep configuration item data consistent.
• Products: the catalog of models and types that configuration items are instances of.
• Product Categories: the classification layer; each category's rule set decides which fields and relationships are available.
• Lifecycle Reviews: date-driven reviews for warranty, end-of-support, and refresh.

A mental model

One way to hold it together: Product categories and products describe what things are. Configuration Items describe what you have. Rules and lifecycle reviews keep the data moving. CMDB Health tells you whether to trust it.

Start here

Pick the task that matches what you are trying to do:

• Stand up the CMDB. Design your classification first: Product Category and Rule Sets, then build the Product catalog.
• Get configuration items in. See Registering Configuration Items for manual, bulk, and integration routes.
• Stop duplicates as data arrives. Turn on reconciliation: Getting Started with Reconciliation.
• Check whether your data is trustworthy. Read CMDB Health and work the measures that need attention.
• Track warranties and renewals. Configure Lifecycle Reviews.

Order matters

When you are setting the module up from scratch, work outside in: categories before products, products before configuration items, and automation and reviews only once real data exists. Turning on reconciliation early is worth it, because it keeps the CMDB clean from the first integration onward rather than leaving you a duplicate queue to work later.