IT asset management for physical hardware is a comparatively simple task: Optimally, an asset number is assigned to the object (server, printer, network components, ...) after purchase. On the one hand, this is attached to the device as a label, and on the other hand, it is recorded in a database (CMDB). There, the data is enriched with as much relevant lifecycle data as possible:

• date of purchase

• purchase price

• maintenance period

• depreciation period

• current book value

• Location

• resposnible user

• “End Of Life” date

• … etc.

The challenge is to live the processes in handling the devices in such a way that changes in status (e.g. change of location or user, repair, maintenance extension, etc.) are immediately updated in the database.

The next challenge and increased complexity came with the virtualization of the hardware.

Obviously, these processes can only be taken over by Software Asset Management to a very limited extent. This is why this discipline has mostly been managed and implemented independently as a special feature of ITAM.

But ultimately, "classic" SAM is also "just" about "weighing, measuring, counting ..."

And the purpose of implementing SAM was primarily to comply with licensing guidelines and to avoid so-called license audits by software manufacturers, or to survive without legal and financial consequences.

Here, too, the ongoing virtualization of hardware brought new challenges, as almost all software vendors have special licensing terms for software running on virtualized hardware.

But then there came the CLOUD ...and everything changed!

With the advent of software that can be used and licensed as a cloud application (e.g. Microsoft 365 ...), the rumor arose that software asset management was no longer necessary, since the manufacturer "sees anyway to what extent the corresponding software is used".

But it turned out quite differently, because there is indeed a lower risk to use software beyond its licensing, BUT:

If cloud licenses are not managed correctly and actively, there is always the risk of paying for unused or only partially used licenses!

However, the cloud now offers not only software solutions (Software-as-a-Service ("SaaS")) but also, for example, Infrastructure-as-a-Service ("IaaS"). Here, entire server and network landscapes can be mapped and used. This is particularly practical if, for example, a test environment is required for a limited period of time. In addition to a number of advantages over an in-house solution, there are also a number of risks, both financial and in terms of security.

This is how ITAM and SAM grow together!

And suddenly (almost) everything is licenses.

As it is one of the main responsibilities of the management of companies of any size to identify and minimize risks and avoid unnecessary costs, the topic #ITAM/#SAM MUST be on the agenda of EVERY management!

Contact us today for a no obligation initial consultation. Let us find out if there is still potential for optimization. Maybe we will find "still sleeping" potential together.