Thanks Daniel. A bit more deep-dive and review with some colleagues resulted in the same conclusion. A bit more clarification for others that read this question and answers:
At the moment an Asset/ CI is replaced in an infrastructure the CMDB of that infrastructure should be updated as it should represent the involved infrastructure. With the Asset Swap capability the basic step of updating the CMDB after Asset/ CI replacement is done as within for example the INCident process it's easy to register the Asset action (like swap) and the Swapped CI so there is no need to do this basic CMDB update on CI forms. What happens in this basic CMDB update is that basically Assigned to, State and Substate are updated of both involved Assets/ CI's so of the CI/ Asset involved in the INC and the Swapped CI.
As the CI that is involved in the INC can have a lot of CI relations like relations to installed software or databases on itself or relations to other CI's these relations will NOT be transferred to the Swapped CI.
Relations to installed software or databases on the swapped CI itself do not change due to the swapping action but will have to be removed afterwards depending on the actions that are done with that CI.
Relations to other CI's in the infrastructure have to be rebuild on any way, preferable with a discovery like solution as it is hardly or not possible to automated this in an other way due to the immense number of options/ possibilities here.
Thanks again Daniel. Hopefully the additional info helps others.
Ed
