By definition, Software Asset Management (SAM) is a business practice that involves managing and optimizing the purchase, deployment, maintenance, utilization, and disposal of software applications within an organization.
To many of our customers, SAM is associated with software compliance, software audits, risk mitigation, risk analysis, and cost savings. All of these ring true.
My experience with SAM as a discipline spans all types of businesses, whether SMB, Corporate, Enterprise, all the way up to Government and Education. SAM, whether we realize it or not, truly is a subject that affects nearly all organizations at some point in time.
If you’ve ever been faced with a Software audit, or have been tapped on the shoulder for a “voluntary” compliance check by a Software Manufacturer, SAM is typically the discipline utilized to come the rescue.
Over the course of my 18 years in IT, SAM has been one of the top growth areas across the software segment.
Whether a small-mid sized or large enterprise, the risks and impact to the organization remain the same. Organizations who are found out of compliance can expect to be dealt heavy fines, whether from the BSA (Business Software Alliance) or the software manufacturer; negative internal & external exposure (especially for state/local government and publicly traded organizations); and in many cases I’ve seen, a loss in employment to those directly in charge of managing the software assets in question.
So, yes, SAM is a critical discipline. When we talk about SAM, as a starting point, we consider the following:
- Title
- Version number
- What licensing considerations apply (by user/device/processor/core/etc.)
- Whether or not the license is covered via maintenance
What we understand about SAM goes far beyond being under-licensed. I’ve seen many cases where legacy buying behaviors often reveal over-licensing. By understanding what you’ve purchased, whether or not it’s used, and how often it’s used, we create a business case for future purchases – Or sometimes the opposite: the case to support a NON purchase event.
The Evolution of Software Asset Management
Years ago, Software Asset Management (SAM) was a novelty, as there was very limited visibility around the benefits SAM brought to clients. Probably the easiest way to capture this scenario was almost like selling a bike without a helmet. The client would begin their journey via the licensing vehicle. However, when they ran into a bump in the road, severe trauma was likely. SAM was the helmet – the way to protect clients from said trauma.
Before too long, Microsoft, in addition to many Tier 1 Software Vendors, announced mandatory audits for ALL customers. What this meant was if you invested in licensing, you were subject to an audit at any given time by a vendor. I recall these early years as there was a significant spike in partners who obtained proficiency in the SAM discipline.
Today, Software Asset Management is as relevant as it ever has been. Many clients have either gone down the path of an audit; know someone who has; or are uncertain, when the audit does come, whether they will be in compliance.
Non-compliance comes at a high cost:
- Hefty legal fines via the BSA/Vendor,
- Negative internal exposure at an organization,
- Negative public exposure (diminished shareholder value),
- These are just a few. Trust me, there are more.
Thoroughly understanding what’s at stake is why Zunesis incorporates SAM Disciplines during each licensing engagement. Quite simply, it’s ensuring that our clients’ investments in licensing are fully optimized. Whether it means we identify scenarios in which a client is over licensed and can eliminate the need to invest further, under licensed and needs help producing a strategy to address the gap, or ensuring that every license corresponds with the right amount of usage (specific to an end user role or department), are some of the ways we optimize IT investments and shield customers from the effects of non-compliance.
