Best Practice for managing Software Models when Publisher acquired by another Publisher

[Paula Stewart]

What is the best practice of SAM processing for Software Models and Products under the following scenarios:

1. Publisher "B" purchases the complete software portfolio of Publisher "A"

2. Publisher "B" purchases only a portion (several products) of the software portfolio of Publisher "A"

Thanks.

[BradP-InnoSolv]

I am also interested in this topic but seems there is little to no info i can find in documentation or in the community.   

[dreinhardt]

Hi @Paula Stewart, @BradP-InnoSolv,

for all software publishers and products managed by the SAMP content team, the publishers changes are provided and updated during the weekly content update job,

Content updates for Software Asset Management (servicenow.com)

Note: Software models aren’t updated when a publisher's name is updated as part of the content updates. The software model isn't updated because its display name is removed from the core company's reference. 

However, if a product moves to a different publisher, then the software model gets updated during content updates when the product goes from one core company to the other core company. The publisher name is updated for new software models but not for existing software models.

I would also recommend to report any acquisition to the SAMP content team and they'll take care of the update. Manual creation of publisher & products is an option, but I wouldn't recommend it to do not loose the benefits of the content management.

Best, Dennis

[BradP-InnoSolv]

Thank you for responding and helping with this.  Follow up question. 

Since the existing SW models are not updated, then what is the best method to solve this issue of not being able to relate a maintenance entitlement under the new publisher to the perpetual entitlement under the old publisher?   I want to know service now's official recommendation for this for these 2 diff use cases if the answer is different for each.

1. When the publisher has a publisher pack i.e. VMware being purchased by Broadcom. We have hundreds of entitlements and to create an upgrade entitlement for each to convert would be tedious.

2. When the publisher is not under a publisher pack i.e. Hexagon AB ESPRIT which used to be DP Technology ESPRIT? 

[dreinhardt]

@BradP-InnoSolv, I got your point, that the documentation is not clear at this point.

Part 1: However, if a product moves to a different publisher, then the software model gets updated during content updates when the product goes from one core company to the other core company. 

Part2: The publisher name is updated for new software models but not for existing software models.

Part 1 seems to be the match for our use case products moved from VMware to Broadcom. I've seen a few customer instances with a automatic change from VMware to Broadcom for the software model publisher. (DMAP Publisher was updated)

Part 2, not sure about this 😁

 @SrinivasRamanu1 could you please share more details about this process.

2. When the publisher is not under a publisher pack i.e. Hexagon AB ESPRIT which used to be DP Technology ESPRIT?

• check if the new publisher exists in the core_company table
  • if not, create a new one
• navigate to [samp_sw_publisher] table 
• search and open your record Hexagon AB ESPRIT
• change the manufacturer (core company reference) to the new create publisher DP Technology

Recommendation: Report all your custom publishers/products to the SAMP content team and they will take about all the requiered steps (processing time is about 2 weeks).

Best, Dennis