How to map predecessor / successor relationships in ServiceNow?

[Manu15]

Hi all,

from the enterprise architecture view we want to map predecessor / successor relationships on two different levels:

1. Version level: e.g. Windows Server R2012 is predecessor of Windows Server R2016

2. Content level: e.g. Red Hat is successor of SUSE Linux

Is there a way to map 1 or 2 OOTB in ServiceNow or do we have to add a m2m table for mapping?

I couldn't find anything about this topic in the sn documentation. Do you have any idea?

Thanks for help!

[Doron Orbach]

I will check with the SAM PMs as this is more relevant for mapping of software and dependency between software versions. As for the 2nd example we also build a new model ('Technology Reference Model') that will enable to map standards of technology within the organization (like emerging or sunset etc).

Thanks,

Doron

[Manu15]

Hi Doron,

sounds very interesting. From my perspective it is interesting at the software product level and at the business application level. Do you already have a plan in which of the coming releases the Technology Reference Model will be usable?

Thanks

Manu

[Doron Orbach]

The TRM module is planned for the release after San Diego, so in several months.

If you are interested in more details, send me an email and we can discuss more details.

As for software, I discussed it with the SAM team and this is what can be done with software today:

We have downgrade rights that provides a list of versions that the customer is entitled to use based on the license they have purchased for their current version.  We also provide a Next Version upgrade if their license type allows for automatic upgrade.

Customers could add these manually too in the downgrade table or in the next version field on the software model.

[Manu15]

Thanks, Doron. The hint concerning "Next Version" helps already. For more TRM details I gonna write you an email 🙂