How to represent Platforms vs. the Application and/or Module/Components

[klpawlenty]

Hello,

Just looking for ideas...  We have not implemented SW or HW Asset Management in the ServiceNow tool yet, but we have a built out the CMDB (mostly automated, some manual).  There are some scenarios in our Application CI manual population where we have a "Platform" Application CI with additional "Application" CIs or maybe even an "Application" CI with additional "Module" or "Component" CIs.  How does Software Asset Management in ServiceNow represent this?  I have been reading on the product model or model categories, but unsure if I am down the right path OR how ServiceNow would intend to have these represented.

Anyone also experience this question on how to represent Platforms, Applications, Modules/Components clearly?

Thank you,
Kari

[Daniel Slocum]

Hi Kari,

I've seen several customers represent this relationship as a Business Service CI with various Servers and other Infrastructure CI's related under it in the CMDB Dependancy Map.  How Software is identified within SAM is installation records on the supporting hardware.  When ServiceNow Discovery scans the network, software installed on the servers supporting the business service is read.  Each software title found on the server is added to the Software Installations related list on the CI record.  Reconciliation within SAM allows for license management of installed software across the enterprise, while License Change Projection integrates SAM into the Change Control process in support of the Servers hosting the business service.

I hope this answers your question.  if not, please do reply with additional clarifying questions and I'll do my best to respond appropriately.

Daniel

[cody_wolf]

Do you have APM by chance?

SAM + APM "Better Together" use case.

Here is a snip of the SAM data model