AEC firms bill clients for their professionals’ time. Geotechnical and construction firms bill for the use of physical assets, like bulldozers, ground penetrating radar, and drones. So why not bill for specialty application use?
Topics: Project Management
Every year at renewal time, the question “How many licenses do I need?” drives the beginning of a frustrating data gathering process. For metered applications, the simple answer is to determine how your peak number of users compares to your number of licenses. The reality is that (especially for firms consolidating licenses, using application suites, using several similar versions, or with expensive engineering applications) calculating an optimal answer is much more complicated.
In a previous post we discussed some of the recent trends occurring in the Asset Management space, including applications in the cloud (here). This week, we’ll share our thoughts on the implications of cloud-based license keys on use analysis.
Once a year at renewal time, the question “How many licenses do I need?” drives the beginning of a frustrating data gathering process. For metered applications, the simplistic answer is to determine how my peak use compares to my number of licenses. The reality is that, especially for mid-size companies, firms consolidating licenses, firms with similar applications, or Autodesk application/Suite/Collection users, etc., calculating an optimal answer is more complicated. We’ll try to address those some of those complexities in future posts.
This is the third post in a series of use cases for application use data. In this post, we’ll look at the three ways that associating application use to a project can impact organization revenue and efficiency.
In a previous blog post, we discussed that granular use data supports a number of use cases to justify the cost of implementing and maintaining the data collection process. This post will focus on the value of trending data and how it can apply to short-, medium- and long-term planning. We’ve selected three use cases based on analyses we’ve had from customers and prospective partners. These are:
Application deployment and licensing has evolved from standalone applications to include concurrent/metered licenses, enterprise licenses, cloud-delivered licensing, cloud-server batch, browser-based applications, and APIs. Existing monitoring solutions using license log files can’t monitor and report on applications that receive licenses from outside the enterprise. New approaches to application use monitoring are required to provide the use data enterprises need for license cost reduction and application use optimization.
In our last blog post, we said we were going to look at some of the Use Cases associated with license cost reduction. Reducing license costs assumes there is an overabundance of license availability/capacity relative to the actual need. Different vendors have different licensing approaches, and may have multiple approaches depending on their license or application types. The common elements that enterprises need to understand in order to determine if and how much over-licensing exists are: