Asset and CI mapping

Synchronize asset records and CI records by mapping their fields, states, and statuses to each other. Changes made to one record trigger the same updates on the corresponding record, ensuring consistent reporting. You can synchronize out-of-the-box and custom mappings.

Note: If you have upgraded from the Geneva or a prior release and had customized the AssetAndCISynchronizer script include before the upgrade, you must overwrite the customization, and then recreate the custom mappings.
For fields one-to-mapping is done. However, for states, the asset-CI synchronization can be driven in the following ways:
  • Asset to CI: Changes to the asset are updated to the logically mapped CI.
  • CI to asset: Changes to the CI are updated to the logically mapped asset.
  • Both: Changes to either the asset or the CI are updated to the logically mapped record.
Figure 1. Asset-CI mapping and synchronization
Asset-CI mapping and synchronization is based on the following factors:
  • To synchronize asset and CI records, you can create the following mappings:
    • Asset fields with CI fields.
    • Asset State and Substate fields with CI Install Status fields.
    • Asset State field and Substate fields with CI Hardware Status and Substatus fields.
  • Assets and CIs are not mapped on a one-to-one basis. The fields are mapped to the most logical counterpart. For example, for a hardware asset set to the In Stock state and Pending disposal substate, the corresponding CI is set to the In Disposition state with no substate.
  • For a hardware CI, if both the Hardware Status and Install Status fields are mapped and updated, the Hardware Status field change is considered for mapping the corresponding state of the asset.
  • The Install Status and Hardware Status fields of a CI are independent of each other. There is no correlation between them. A change to the Hardware Status field does not change the CI Install Status field and vice versa.