Contents IT Service Management Previous Topic Next Topic Asset and CI mapping Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share 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. Map asset and CI fieldsWhen you map the asset and CI fields, synchronization happens both ways. Changes to either the asset or CI record are updated to the logically mapped record. You can synchronize custom mappings and mappings provided with the base instance.Map asset state and CI install statusMap the asset State and Substate fields to the CI Install Status field. The CI Install Status field does not have a Substatus field and must be used for CIs other than hardware. When you create the mapping, you can set the synchronization direction from the asset, CI, or both. Map asset state and CI hardware statusMap the asset State and Substate fields to the CI Hardware Status and Substatus fields. The Hardware Status field is visible only for hardware CIs. When you create the mapping, you can set the synchronization direction from the asset, CI, or both. For hardware, you can synchronize custom mappings.List of synchronized asset and CI fieldsSome asset and CI fields are mapped by default. If you update a mapped field on the asset or CI record, the same field on the corresponding record is automatically updated. Related tasksCreate assetsAdd depreciation to an assetCreate pre-allocated assetsCreate license assetsSet asset states and substatesRetire assetsDelete assetsRelated conceptsCreate fixed assetsConsumables life cycle On this page Send Feedback Previous Topic Next Topic
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. Map asset and CI fieldsWhen you map the asset and CI fields, synchronization happens both ways. Changes to either the asset or CI record are updated to the logically mapped record. You can synchronize custom mappings and mappings provided with the base instance.Map asset state and CI install statusMap the asset State and Substate fields to the CI Install Status field. The CI Install Status field does not have a Substatus field and must be used for CIs other than hardware. When you create the mapping, you can set the synchronization direction from the asset, CI, or both. Map asset state and CI hardware statusMap the asset State and Substate fields to the CI Hardware Status and Substatus fields. The Hardware Status field is visible only for hardware CIs. When you create the mapping, you can set the synchronization direction from the asset, CI, or both. For hardware, you can synchronize custom mappings.List of synchronized asset and CI fieldsSome asset and CI fields are mapped by default. If you update a mapped field on the asset or CI record, the same field on the corresponding record is automatically updated. Related tasksCreate assetsAdd depreciation to an assetCreate pre-allocated assetsCreate license assetsSet asset states and substatesRetire assetsDelete assetsRelated conceptsCreate fixed assetsConsumables life cycle
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. Map asset and CI fieldsWhen you map the asset and CI fields, synchronization happens both ways. Changes to either the asset or CI record are updated to the logically mapped record. You can synchronize custom mappings and mappings provided with the base instance.Map asset state and CI install statusMap the asset State and Substate fields to the CI Install Status field. The CI Install Status field does not have a Substatus field and must be used for CIs other than hardware. When you create the mapping, you can set the synchronization direction from the asset, CI, or both. Map asset state and CI hardware statusMap the asset State and Substate fields to the CI Hardware Status and Substatus fields. The Hardware Status field is visible only for hardware CIs. When you create the mapping, you can set the synchronization direction from the asset, CI, or both. For hardware, you can synchronize custom mappings.List of synchronized asset and CI fieldsSome asset and CI fields are mapped by default. If you update a mapped field on the asset or CI record, the same field on the corresponding record is automatically updated. Related tasksCreate assetsAdd depreciation to an assetCreate pre-allocated assetsCreate license assetsSet asset states and substatesRetire assetsDelete assetsRelated conceptsCreate fixed assetsConsumables life cycle
