Software assets in AC

tis_itsm · Active Member Joined: 07 Jan 2009 Posts: 10 Location: UK

Hello experts,

Would like to know your opinion on the way Software assets are treated in AC.

Currently, we create an asset record for every software asset and add them as child element to the corresponding CPU asset.

Now, we are in the process of evaluating the options for maintaining softwares as a link to CPU assets rather than parent/child relationship. In other words, if more than one CPU has same kind of Software, then, only one software asset will be created and linked to each CPU through N-N link.

What are the pros/cons of this proposed approach?

Thanks..

chuck_darst · Active Member Joined: 26 Jan 2009 Posts: 10

This is only a partial answer.

First, do you have access to the "HP Asset Manager 5.10 - Software Assets" reference guide?

An important point of clarification is the distinction of software “installations” or “utilizations” versus software “assets”, which are represented in Asset Manager as a “license” or more detailed “contract” of terms and conditions. The reference guide (from the Asset Manager documentation library) covers these concepts and how they are implemented as best practices within the HP Software product.
_________________
Chuck Darst
ITSM Product Marketing
HP Software & Solutions
chuck.darst@hp.com
Tel: +1 970 898 2064