<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Asset RMA and CI relationship in CMDB forum</title>
    <link>https://www.servicenow.com/community/cmdb-forum/asset-rma-and-ci-relationship/m-p/3250338#M15470</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;What is the best practice to handle the asset RMA process? Let's say the network device or server gets replaced by a support provider, and it has a new serial number.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Option 1: Can you update the existing asset with a new serial number and document the old serial number on the asset? This way, all the relationships the CI or asset objects have are maintained.&lt;/P&gt;&lt;P&gt;Option 2: Retire existing asset with state Retire and substate RMA. Create a new asset with a new serial number, link the old CI record to the new asset, and make sure all the relationships are established.&lt;/P&gt;</description>
    <pubDate>Tue, 29 Apr 2025 12:44:07 GMT</pubDate>
    <dc:creator>bd547</dc:creator>
    <dc:date>2025-04-29T12:44:07Z</dc:date>
    <item>
      <title>Asset RMA and CI relationship</title>
      <link>https://www.servicenow.com/community/cmdb-forum/asset-rma-and-ci-relationship/m-p/3250338#M15470</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;What is the best practice to handle the asset RMA process? Let's say the network device or server gets replaced by a support provider, and it has a new serial number.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Option 1: Can you update the existing asset with a new serial number and document the old serial number on the asset? This way, all the relationships the CI or asset objects have are maintained.&lt;/P&gt;&lt;P&gt;Option 2: Retire existing asset with state Retire and substate RMA. Create a new asset with a new serial number, link the old CI record to the new asset, and make sure all the relationships are established.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 12:44:07 GMT</pubDate>
      <guid>https://www.servicenow.com/community/cmdb-forum/asset-rma-and-ci-relationship/m-p/3250338#M15470</guid>
      <dc:creator>bd547</dc:creator>
      <dc:date>2025-04-29T12:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: Asset RMA and CI relationship</title>
      <link>https://www.servicenow.com/community/cmdb-forum/asset-rma-and-ci-relationship/m-p/3250492#M15475</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/545858"&gt;@bd547&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would prefer Option 2, the reason being that a new asset and CI (Configuration Item) are installed, and now the attributes of both the asset and CI also get updated. So, using Option 2 makes more sense.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 14:22:38 GMT</pubDate>
      <guid>https://www.servicenow.com/community/cmdb-forum/asset-rma-and-ci-relationship/m-p/3250492#M15475</guid>
      <dc:creator>Dr Atul G- LNG</dc:creator>
      <dc:date>2025-04-29T14:22:38Z</dc:date>
    </item>
  </channel>
</rss>

