This is part two of a two-part series on environment recognition. See part one here: ‘Modern SAM requires ‘Environment Recognition’ as much as ‘Software Recognition’.
In my last article I explored the concept of ‘environment recognition’. I suggested that modern Software Asset Management (SAM) is not just about recognizing software in your estate and counting installs, but also understanding the environment in which it is used. In this article I will explore some real life examples of license models that require environment recognition.
There is a convergence in the industry between software, hardware and configuration detail in license models. You could argue that this is mainly due to Moore’s law and the logarithmic growth in processing power and virtualization technologies in datacentres.
Software publishers can maximize license revenue by aligning themselves to this growth in computing power. If software publishers were only charging for their software based on installs they would be missing out on significant leaps forward in innovation and value from the software.
The convergence between SAM and Hardware Asset Management (HAM) has serious impact to how we measure compliance, usage and value and is causing many organizations to revisit their entire SAM strategy.
The following license models are examples of high value software that requires much more than simply counting the number of installs in order to verify compliance:
Around 80% of organisations are making the shift from device to user centric agreements when renewing with Microsoft ~ Paul McAdam #bcscmsg
— Martin Thompson (@itammartin) June 10, 2014
At ITAMS, we recommend to clients that a SKU Catalogue underpin their SAM strategy.
A SKU catalogue allows organizations to build a verified system of record to capture all of the environmental conditions required to measure compliance, usage and maximize value from software investments…. No matter how many inventory and procurement sources the Asset Manager may be juggling with!