By Ann Reist As I reflect back on SoftSummit 2011, the conference dedicated to addressing software licensing and entitlement management topics and trends, one of the highlights of the conference for me was the keynote address from Chris Gahagan, SVP of Products & Solutions for Avid. Chris shared his journey of creating “One Avid.” His story, not unlike most software vendors and intelligent device manufacturers that serve multiple market segments, began with the idea of the value that unified licensing could bring to his organization.
Archive for the ‘Software Piracy’ Category
Software License Management: Process Improvement Using Automatic Renewal
By Flexera Global Consulting Services EMEA I have recently engaged with a software publisher who needed to deliver licenses to customers worldwide. For some countries, customers are allowed to divide payments into multiple chunks over time. The publisher, on the other hand, must ensure the customer performs the payments at the times expected. For this reason, the process of delivering software licenses depends on the ongoing status of their contractual agreement with the publisher: customer receives a new time-limited license with extended validity period every time the publisher receives the payment in advance for that period.
Machine-to-Machine (M2M) Has Evolved
By: Steve Schmidt Everywhere I turn, I seem to run into another interesting opportunity to drive more value out of Machine-to-Machine (M2M) initiatives, so I thought I would share some of my thoughts on M2M. First, a common definition of Machine-to-Machine (M2M)… Machine-to-Machine (M2M) refers to technologies that allow both wireless and wired systems to communicate with other devices of the same ability. [1] [2] M2M uses a device (such as a sensor or meter) to capture an event (such as temperature, inventory level, etc.), which is relayed through a network (wireless, wired or hybrid) to an application ( software program), that translates the captured event into meaningful information. (Source:
We Couldn’t Agree More, Mr. Andreessen!
By Bashyam Anant In a recent Wall Street Journal article, Marc Andreessen pronounced that ” software is eating the world “. He went on to explain ” we are in the middle of a dramatic and broad technological and economic shift in which software
SoftSummit 2011—The Premier Software Licensing, Entitlement Management, and Pricing Conference
By: Flexera Software
Distributed Management Task Force Helps Develop Cloud Licensing Standards
By: John Lipsey Today Flexera Software announced that is has been asked to join the Distributed Management Task Force (DMTF) .
Predictable Pay-For-Use Hardware and Software Licensing
By: Mike Costa Much has been written lately about pay-for-use hardware and software licensing – including the many benefits and drawbacks compared to the traditional, perpetual approach. Pay-for-use licensing comes in many flavors—SaaS, IaaS, PaaS, cloud computing, utility computing, etc. In general, these license models allow customers to rent all or some of the software and/or hardware for which they would otherwise have to purchase perpetual or ownership rights. One of the primary characteristics that differentiate the various types of software/hardware rental is time granularity – the duration of the rental period. Other time granularities include: multi-year, annual, quarterly, monthly, weekly and so on. Subscription and term are two popular rental models. Subscriptions generally provide for ongoing rental until cancelled with pricing based on specific configurations or products rented during one or more time intervals each. Term licensing is similar to Subscription but allows rental over a predefined period of time, not ongoing. I use the term “pay-for-use” to describe ongoing software and hardware rental types, in this case, all but Term. Pay-for-use, in its most valuable form, is fairly dynamic – within reasonable limits, of course. Suppliers can use it to satisfy customer demand whenever and wherever it occurs, gaining market share and increasing revenue. Customers can use it to improve asset flexibility, access and efficiency. So why aren't more suppliers offering pay-for-use and why aren't customers adopting this model when it is offered? The lack of predictability seems to be one of the most often cited reasons. Ironically, pay-for-use is a very important model for suppliers and customers precisely because it addresses unpredictable asset demand. Let's face it, it's a dynamic world. Customers need the ability to quickly increase software and/or hardware resources to meet peak demands – without having to over-purchase for peak needs or risk onerous audit liabilities. Suppliers would much prefer allowing customers to rent assets during these peak periods vs. having to loan them free of charge or strain relationships with audits. The loan approach is much less feasible due to Sarbanes-Oxley financial controls. So how do we crack this predictability “nut”. Actually, with an adequate infrastructure and a supportive pricing model, it can be fairly straightforward. In fact, the common cell phone pricing model provides a useful basis. The cell phone model usually includes a committed “bucket-of-minutes” plan coupled with the customers' ability to exceed his/her committed volume for a peak per-minute fee. Now, there are two major changes needed to make the cell phone model feasible for business customers. First, the peak per-unit fee has to be much less than 5-10x the committed per-unit fee – 1.25x to 2x is probably more reasonable for the same time granularity. The price difference should be high enough that it fairly compensates the supplier while not being so low that it invites peak usage as the norm. Also, as with cell phone plans, peak usage is billed in arrears and customers should be provided the ability to increase their committed volume under suitable conditions. Second, business customers must be able to proactively control their peak use expenses, not experience the surprise of receiving a “budget-busting” bill for usage run amok, after the fact. This can be accomplished by providing customers the ability to control how much, when and to which employees the peak assets are allocated – preferably without having to contact the supplier beforehand. Supplier predictability is optimized because the relative committed vs. peak pricing difference minimizes peak usage. Customer predictability is no longer an issue because they control peak quantities and licensing durations so they can therefore fix maximum incremental cost exposure. Great theory? Not at all. Flexera Software can help suppliers and customers realize these capabilities today. I've personally had the pleasure of working with two innovative software suppliers that have been providing these capabilities to customers using Flexera Software products since 1996. What is your experience with pay-per-use licensing models? Have you cracked the predictability “nut”?
If You Have a License Technology Problem, Start by Understanding Your Business Needs
The “Myth of the Plug-in Solution” By: Victor Hoisington, PMP, ITIL Today, almost every software vendor, and most intelligent device manufacturers (with embedded software) have multiple software license management systems acquired via acquisition, mergers, and divestitures. The problems that result are disconnected systems, manual processes, and the inability to create solutions from products that span the technology of the constituent companies. When this happens, IT is directed to fix these problems of inefficiency in a way to ensure no loss of continuity in the business (we need the revenue), so they try to merge existing systems in a patchwork way, retrofitting, and manually manipulating the systems so that they can deliver to their customers and keep the revenue recognition engine flowing. This works for awhile, but eventually these retrofitted systems simply don't work together and in fact, the situation may become worse. What happens next is that IT starts looking for a “plug-in” technology to fix their problems and make it all better, but – just like the common cold, there is no magic pill to make it better. I call this the “Myth of the Plug-in Solution”. The “myth of the plug-in solution” ignores some pesky systemic problems that probably existed before and that become worse after multiple years of poor definition of the business requirements and business intent behind software licensing and entitlement management . Or, the requirements have changed due to market conditions (e.g. new license models, cloud computing, virtualization, simpler customer experience, etc). As IT focuses on the systems and their connections, they sometimes lose track of the business drivers, and more importantly, the fact that a true solution will require a combination of process, policy, and technology. What's required is an examination of the underlying business requirements and supporting business processes with the involvement of stakeholders from across the entire business. What Flexera Software does when working with customers to solve these problems is to use a defined, top-down framework that starts by examining the business and market requirements then proceeds to understand and share “best practices” on commercial realization models (e.g. product structure and license models), the compliance and enforcement strategy, and finally the “prospect to support” use cases that define the customers' relationship with you. This business first definition of the requirements leads to the systems (of record) and interconnection strategies needed at the IT level and now we can begin to define the technology which most closely meets the needs of the business. Failure to lead with a business first philosophy will lead to propagation of bad solutions. Using a business first based framework to define a business solution and truly understand your business requirements, policies and customer use-cases will drive the correct combination of policies, procedures and finally technology to create the synergy needed to meet your needs and your customers' expectations. Want to know more about our framework and business first process, let us know and we'd be glad to help.



Posted in
Tags: