Software Asset Management – Why Track Employee Application Use?
Did you know that underutilized software cost businesses a staggering $34 billion per year? With a properly executed Software Asset Management (SAM) strategy you can optimize the capital efficiency of your business and avoid paying for software that your employees aren’t using.
Table of ContentsWhat is Software Asset Management and Why is it Important?
Software Asset Management (SAM) is a subset of IT Asset Management (ITAM) that focuses on the optimization of software usage, procurement, deployment, maintenance, and disposal in an organization. SAM includes the management of software assets, product versions, licenses, and the media used to deliver the software. Aside from license cost optimization SAM also manages the lifecycle of a software product and determines the software’s function in the organization.
A subset of SAM is Software License Management (SLM), which focuses on the optimization of software licenses used within an organization. The goal of SLM is to reduce costs by reducing the amount of unused licenses, optimizing the use of existing licenses, and consolidating redundant licenses. SLM also refers to the optimization of related costs associated with customer support and product maintenance.
SLM can be further refined to Software License Compliance (SLC), which is the practice of maintaining compliance with the terms agreed to in End User License Agreements (EULA). Common terms that organizations need to maintain compliance with include ensuring that only permitted end-users are operating the software, required device configurations are maintained, and that the software is only used in permitted geographic locations.
A successful software asset management (SAM) strategy will help you understand:
- Which applications are we paying for?
- How many employees within my organization actually use a given software?
- Do we have enough (or too many) licenses?
- What will the total costs of this software be throughout its lifecycle?
Throughout this article we will use Software Asset Management (SAM) as an all-encompassing term for both SLM and SLC.
The Goals & Benefits of Software Asset Management
Detect & reduce shadow IT
Shadow IT – also known as Stealth IT, Client IT, or Fake IT – is any system, solution, or software that’s used by the employees of an organization without the knowledge and approval of the corporate IT department.
An effective software asset management program will include a software audit that detects all of the programs that are currently used by the organization, including those that have not been officially adopted for use in the organization.
Reduce software license costs
Underutilized software cost businesses in the US and UK an estimated $34 billion per year. SAM helps organizations manage application sprawl and reduce software costs by tracking the utilization rate of applications.
By monitoring the application use of their employees an organization can make data-informed decisions regarding the need to purchase new licenses and decommission underutilized software.
Reduce corporate risk
SAM is a critical component of corporate risk management. A failed software compliance audit can cost an organization as much as $150,000 in fines per violation. An audit can be failed due to the presence of pirated software, using more licenses than allotted, or other violations of the software’s End-User License Agreement (EULA).
These audits are more frequent than some may realize; a report from Gartner anticipated that 68 percent of enterprises get at least one audit request each year.
The Risks of Poor Software Asset Management
Compliance violations
Each software vendor has their own End-User License Agreement (software license agreement) that the organization must adhere to. Without adequate oversight an organization runs the risk of violating their agreements to the vendors.
Increased costs
- Fines & Penalties: Non-compliance fines from a failed software compliance audit (piracy, exceeding license entitlements, etc)
- Increased SaaS Spend: Software-as-a-Service (SaaS) vendors often license their software by the user. If the organization is being billed for more users than are actively using the service they will have sub-optimal operating expenses. A proper SAM strategy must include SaaS spend management as a component.
- Productivity Loss: If an insufficient amount of licenses are available for the legitimate need of the organization they will experience an increase in downtime. They may also lose billable hours to time spent procuring software for a need that is adequately met by an existing solution.
- Over Licensing: Poor software license management can cause the organization to purchase a greater volume of licenses than they legitimately need.
Lost productivity
Without meaningful insights into the application usage of their employees an organization risks not having enough active software licenses. If all of the available licenses are already used they will experience significant downtime as their other employees cannot make use of the software.
Monitoring the application usage of their employees provides organizations with the historical data they need to decide if a greater amount of licenses need to be procured to meet the demands of peak usage periods.
How To Get Started With Software Asset Management
Audit Your Existing Software
To start, you need to have a thorough understanding of all of the software currently being used by your business. You will need to catalogue the existing licenses your company has, make note of ongoing software expenses, and monitor employee computer activity to determine whether or not the existing solutions are being used.
- Audit your organization’s software procurement history for existing licenses
- Monitor employee application use to determine current utilization and detect the use of undocumented software
- Monitor employee web activity for the use of SaaS platforms
- Categorize the existing software and consolidate any redundant solutions
- Make note of any upcoming renewal dates for monthly/annual subscriptions or maintenance plans
Establish a Software Procurement Process
To reduce unnecessary software expenditure in your business you will need greater control over your software procurement and decommissioning process. This can be accomplished by establishing policies and procedures surrounding the acquisition, documentation, deployment, usage and retirement of software.
Your organization should have official software procurement procedures in place that defines who is permitted to make purchases, when those purchases can be made, and what channels must be consulted for approval before a solution can be purchased and deployed. This will reduce unexpected shadow IT costs and ensure that each software purchase is evaluated against your existing capabilities before approval.
Track & Control Employee Software Use (Software Metering)
The practice of tracking and maintaining software licenses is known as software metering. The goal of software metering is to ensure that license limits are enforced and that licenses are available for each user that needs one. This practice can be further split into two major categories: passive software metering and active software metering.
Passive software metering: Application use is monitored but users are not actively denied access to the software. This provides natural user activity insights that can help determine the amount of licenses needed.
Active software metering: Application use is monitored and access can be denied based on a given set of parameters. For example, an organization with a limited amount of licenses could schedule application permissions to limit the amount of users that can access the software at a given time.
Organizations can further reduce unauthorized software use with an application blocker. Employees that are not authorized to use a given solution can be proactively blocked from launching the program, reducing the opportunity for licenses to be activated without a legitimate need.
Ready to start monitoring and restricting software use in your company? Get started with a FREE trial of CurrentWare.
Frequently Asked Questions
An End User License Agreement (EULA) is a legal agreement between a software vendor and the user of the software. Software companies use EULAs to protect themselves by binding the users of the software with the vendor’s terms, rules or guidelines. The purpose of a EULA is to communicate the acceptable use of the software and establish a legal precedent for enforcement should an end-user misuse the software.
Common stipulations of a EULA include:
1) Limits to how many devices can have the software installed on it
2) Forbidding the reverse-engineering of the software
3) Stipulation that protect the vendor from lawsuits related to the use of their product
4) Geolocation restrictions
5) Who is permitted to use the software (third parties, employee vs non-employee, etc)
Software Asset Management (SAM) is a subset of IT Asset Management (ITAM) that focuses on the optimization of software usage, procurement, deployment, maintenance, and disposal in an organization. SAM includes the management of software assets, product versions, licenses, and the media used to deliver the software. Aside from license cost optimization SAM also manages the lifecycle of a software product and determines the software’s function in the organization.
Common objectives of Software Asset Management include:
• Reducing the complexity of technology in the organization
• Reducing the lifecycle costs of a software product
• Creating a strategic plan for managing new and existing software in the organization
Software License Management (SLM) is a subset of SAM. It focuses on the optimization of software licenses used within an organization. The goal of SLM is to reduce costs by reducing the amount of unused licenses, optimizing the use of existing licenses, and consolidating redundant licenses. SLM also refers to the optimization of related costs associated with customer support and product maintenance.
Common objectives of Software License Management include:
• Reducing costs directly associated with licenses such as over-licensing/under-licensing, maintenance costs, and support costs.
• Ensuring that the correct licenses are available (e.g. product version)
• Reducing software deployment costs by determining the legitimate licensing needs of the organization and consolidating/expanding as needed
Many different types of software licenses exist. The types of licenses available are generally categorized by their intended use and volume.
Examples of software license types
Evaluation license: A limited-time or limited-use license that is intended to be used to provide the user with a demonstration of the product before purchasing.
Concurrent license: A license that can be shared by a designated number of multiple users simultaneously. For example, if you have 6 concurrent licenses you can have up to 6 users operating the software simultaneously; the seventh simultaneous user would not be permitted to use the software. This is also known as a floating license.
Perpetual license: This license type grants access to the current version of the software for a one-time purchase.
Subscription license: This type of license grants access to the software for a monthly or annual fee. This fee is typically based on the amount of users.
Named user license: A license that is intended for use by a specific individual user.
Proprietary: The creator of the software reserves all rights to the product. This type of license often includes stipulations that prohibit its modification or redistribution.
Free and open-source software (FOSS): A software license that gives the user unlimited rights to modify and reuse the software’s code.
Conclusion
Sub-optimal software licensing is a significant source of capital inefficiency for many organizations. By tracking the internet and application usage of your employees you can ensure that the SaaS solutions and software products you invest in are truly necessary and used to their full potential. You can identify which products require a greater volume of licenses and which products can be decommissioned.
Monitor & Control Application Use with CurrentWare
