In the last edition of Marwick, we touched on the benefits of software asset management (SAM). Organisations spend a fortune on licenses every year and the failure to manage these licenses can result in heavy fines.
As we already talked about the benefits of SAM, it is now time find out how to get these benefits. Here are some best practices for SAM’s implementation into your organisation.
A starting point for the implementation of SAM is to find out where you currently are in terms of software and what you own. You will need to identify all your organisation’s procured licenses. All licenses do not come in the same shape or colour; hence, deep analysis of your licensing position will be required. Here are some common types of licenses: user license, volume license, agreement types, concurrent licenses, OEM, test evaluation, free licenses.
Once you have established a baseline of the licenses your organisation owns, you will need to identify the deployment of these licenses across your organisation. All license deployments need to be consolidated to identify how many machines have individual licenses.
In most cases you should be able tell whether your organisationis in software license compliance by comparing procured licenses against deployed ones.
After comparing owned vs. used licenses you should be able to tell whether your organisation is exposed to any noncompliance risk. There are two actions to be taken in case of any potential license exposure: either uninstall or procure the products that do not have any licenses assigned.
An organisation’s software environment and software requirements evolve on an ongoing basis and should be reviewed periodically. Software asset management needs to be a continuous process to keep in step with the organisation’s requirements.