Use > Data Flow Management > Universal Discovery > Inventory Discovery > Mapping Hardware or Asset Fields to UCMDB - Use-Case Scenario

Mapping Hardware or Asset Fields to UCMDB - Use-Case Scenarios

This document describes common scenarios for customized mappings of data from scan files to UCMDB.

For a task related to this scenario, see How to Map Scan File Attributes to UCMDB.

For concept details, see Custom Hardware or Asset Mapping.

These use cases assume that the scanner has captured the data that you want from the target machine, and that the scanner has written the data to the scan file. Configuring the scanner to collect data and store it in an empty field in the scan file is beyond the scope of this document. For more information, see Asset Data Page.


  • The field names and attribute names described in this document are merely examples. The attribute names were selected because they should not impact out-of-the-box reconciliation rules in UCMDB. Before mapping, always perform an analysis to ensure that storing data in scan file fields and in CIs will not impact other data, or impact reconciliation. For information about reconciliation, see Reconciliation Overview.
  • Generally, most hardware and asset-related information is stored in an attribute under Node CI. If you create your own CI to store your data, it is recommended to create a relationship between your new CI and Node CI.

Tip you can map several strings of data from scan file fields to several CI attributes as long as the CI attributes belong to the same CI in a single pass through the wizard. For example, to map String1 to NodeCI and to map String 2 to Node2CI. you must make two passes through the wizard.