Posts Tagged ‘entitlement management’

How Device Manufacturers Can Thrive in a Software-Centric World

By John Lipsey Jim Ryan, Flexera Software's chief operating officer, spends significant time talking with Intelligent Device Manufacturers to understand the challenges they're facing as their margins increasingly are being squeezed by competition and commoditization. In this video, Jim discusses the changes occurring in the intelligent device space, where manufacturers increasingly are having to think like software vendors, where embedded software on devices is the norm and where key technology to help manufacturers reduce supply chain costs, differentiate and develop products in a more agile environment are key to maintaining profitability.

Can you quickly and accurately determine your installed base?

By Michael Costa That seems like a fairly easy and obvious question. Do you know who has which of your licensed software and/or hardware products, where they are located and to what each of your customers is entitled? With many companies responding to market demands for greater license flexibility and customer self-service, maintaining accurate installed base data is becoming a huge problem that must be addressed. Accurate installed base data allows you to maintain and grow your software and/or intelligent hardware business. Revenue from compliance true-ups, maintenance, support, upgrades, up-selling and cross-selling all depend on accurate installed base data. Attempting to audit license compliance based on erroneous installed base data can severely damage your relationships and reputation. Maintenance and support renewal quoting always starts with an accurate installed base view and asking customers to tell you their installed base undermines customer confidence. An otherwise focused up-selling or cross-selling campaign is considered “spam” to targeted customers that do not meet the applicable installed base profile. And, requiring your channel partners to report installed base lifecycle data in an accurate and timely manner is often more than they can achieve. Maintaining accurate installed base data is usually difficult because licenses tend to change during their lifecycle – sometimes frequently. Some of the common lifecycle stages include: initial sale, maintenance renewal, move, rehost, update, upgrade, downgrade, subscription extension, end-of-life and return. In addition, if you have an indirect sales channel, the initial sale can include two or more additional sub-stages. Inadequately integrating these transactions renders the installed base data for applicable licenses obsolete and useless. Workarounds require expensive, custom or manual integration with other transaction systems – and these workarounds are seldom scalable. One of the most common misconceptions I've heard is that the “installed base” module in an ERP system is a viable system-of-record for storing all license lifecycle transactions. The problem is, as Mathieu Baissac pointed out , ERP systems were never architected to support the dynamic nature of today's flexible, self-served license transactions. ERP systems were designed to manage relatively static, physical assets – largely from an accounting perspective. They worked OK for software when license rights (i.e., entitlements) were relatively static – involving only initial sale, fixed period maintenance and end-of-life. But, as entitlements became more dynamic and hardware became field-expandable and networked, ERP systems became less and less viable. Many companies invested heavily to augment their EPR installed base modules to fill the functionality and performance gaps, but that has proven prohibitively expensive, slow and risky. At this point, ERP systems are only the system-of-record for the initial sale stage of the license lifecycle – primarily because they are often used to process orders. SalesForce.com is increasingly the primary or secondary order entry system for many companies because it is a natural, lower-cost environment for that purpose. An Entitlement Management System is increasingly recognized as the “always-accurate” installed base data solution. An entitlement management system converts orders into entitlements consisting of license rights that customers can then consume, transform and manipulate – within the terms of the purchased license rights. Those rights can include all of the license lifecycle stages mentioned above and many others – overdraft, peak usage, draw-downs and term licenses. License rights are not only applicable to software. Many intelligent hardware products are also being developed with flexible use rights metrics like storage capacity, router channels, networking bandwidth, medical diagnostic tests and even surgical procedures. Flexera Software's FlexNet Operations solution is an example of a mainstream entitlement management system that is specifically designed to manage the dynamic nature of current and future software and intelligent hardware lifecycles. It integrates with other on-premises, on-demand and mixed-environments like Oracle, SAP, Saleforce.com and many others using standard, configurable interfaces. Also, its tight integration with electronic software download, in-product license management and in-product messaging functionality to provide commercial, out-of-the-box best practices.

Webinar: 2011 Key Trends in Software Licensing and Pricing & 2012 Predictions

By Ann Reist The 2011 Key Trends in Software Licensing and Pricing Survey, prepared jointly by Flexera Software and

Maintenance Deserves the Same Respect as Your Software License

By Cris Wendt and Anna Connell IDC conducted a survey a few years ago that illustrated the importance of software maintenance to the overall revenue stream of an enterprise software company (generally offering a perpetual software license model). The result of the analysis was a simple, compelling graph. One line was the license revenue growing at an annual compounded rate of 7% (healthy, but not spectacular), and the other line showed the growth of maintenance revenue, priced at 20% (annually) of the associated perpetual license with an 85% renewal rate. It showed that within 10 years, the maintenance revenue was a greater portion of overall revenue than license revenue (and continues to grow). This illustrates the power of maintenance revenue over an ever-increasing software installed base. However, in the spirit of a marketing perception audit, if maintenance were a person, it would be Rodney Dangerfield, and would be quipping, “Hey, I get no respect”. While software companies generate substantial amounts of money from maintenance, maintenance is often treated as an appendage to the primary software products, with a surprising inattention to optimization of the offering. Here are signs that you may be neglecting your maintenance business and leaving millions of dollars of (mostly bottom line) revenue off of the table: Lack of a maintenance offering. Sometimes software companies seem overwhelmed or new to software and declare that they “provide updates and bug fixes for free for as long as the customer owns the product. Maybe someday, we'll have an offering”. Maintenance is not treated like a product, where it is assigned a product manager, whose responsibility is define the product, price it, and communicate its salient features to customers and channel partners. Maintenance renewals are not handled by a separate and dedicated team whose role is to generate high renewals rates and protect/grow the existing maintenance revenue stream. Without this level of focus, maintenance revenue is frequently cannibalized in preference of new license revenue. The maintenance offering is often ill-defined other than “phone support and updates”. Little consideration is given to what is included in an “update” and what might the value be to the customer. Are there boundaries to what functionality defines an “update” you receive on maintenance as opposed to an option that is paid as an “upgrade”? Software companies often have poor discipline accurately keeping accurate records of their customers – either by company name or by key contacts at their customers. This means that the maintenance renewal process cannot be effectively performed, if it can be performed at all. The problem becomes worse if sales are made through an indirect sales channel. Keeping accurate customer and sales records allows companies to track maintenance revenue and renewal rates which can gauge the health of their business long term. Pricing for maintenance is very ad-hoc, over-simplified, and pays little attention to the product lifecycle. Maintenance may have 1 or 2 price points that reflect an annual price that is a simple percentage of the purchase price of the original software license. Little value is given to the fact some products may provide tremendous value with their updates and may reflect a different price than maintenance on another product. Also, phone support is rarely separated from software updates (although often for good reason). Maintenance and renewal are typically overlooked when an event occurs on the product associated with the maintenance. A price change to the list license price of the product has the same result to maintenance and must be explained at renewal. When products are re-packaged and re-bundled, entire customer configurations often have to be adjusted to reflect the new packaging and pricing, leading to many manual steps to align current product offerings with what the customer originally purchased. While many of the problems above are related to ” entitlement management ” business processes and systems where Flexera Software can help you, a good first step is to honestly evaluate your maintenance business and to make it a priority with good leadership.

Reflections on SoftSummit 2011 Software Licensing Conference

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.

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.

SoftSummit 2011 Software Licensing Conference News and Twitter Chatter

By John Lipsey SoftSummit is the industry's leading event for application producers, who come together once a year to discuss and share knowledge about software licensing, entitlement management, software delivery and enforcement.

Embedded Systems Best Practice: Standardizing on a Common Software Licensing Platform

By: Tu Le We are living in the “Age of Mobility” as seen by exponential growth in smart Internet devices such as the iPhone/iPad/Android/Tablets. These devices are powered by high-end electronic circuitry equivalent to desktop or laptop systems from just a few years ago; however, these devices are driven by multiple layers of software applications more complex in nature than just a normal operating system interface. To reduce manufacturing costs, manufacturers are looking at various ways to reduce complexity and leverage existing hardware. One trend is System on Chip (SoC) where major semiconductor companies are looking to integrate and package all of the electronic components into one single component and allowing software to control various aspects of the functionality on the chip. As demand increases for more features and functionality, manufacturers are filling the need by developing complex software applications to manage and scale as new capabilities are introduced into the system. As with all software development, new capabilities mean an increase in complexity. Hence, many manufacturers differentiate from their products through innovation of their software instead of the hardware. One process for managing software complexity is through the usage of a standardized software package, such as Android, the popular embedded mobile framework. As the industry trends to more prepackaged, standardized applications, software licensing is one critical area that should also be addressed in the ongoing evolution of mobility based applications and the device's respective capabilities. By standardizing on a common licensing platform, manufacturers are able to: Monitor software usage and determine market demands Monetize software features without having to create additional device model/family Manage field, upgrade, and license activation that is consistent across all devices Adapt and respond to customer demographic profile without burden of additional hardware Standardization in software licensing helps to establish customer expectations both present and future. Software licensing enables manufacturers to integrate and scale new capabilities so that they are able to meet market demand on time. As more capabilities are introduced, software licensing can assist manufacturers to reduce via a Java cliché – “build once, monetize many” –without requiring smart device manufacturers to build derivative device types to support different features and/or capabilities.

SoftSummit 2011—The Premier Software Licensing, Entitlement Management, and Pricing Conference

By: Flexera Software

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.

Don’t Put Your Software License Business in Jeopardy – Entitlement Management BI has the Answers

By: Chris Wendt I found a way to beat Jeopardy, especially when my software license business is at stake. When I need answers, I found that I only need to ask the right question, “What can a COTS software licensing and entitlement management system do (provide) for me that an ERP or a homegrown system can't provide?” Software entitlement management systems are an integral part of protecting your organization's valuable IP, generating licenses, and providing the customers with a nice self-serve portal to manage licensing and compliance. But, such a system can also provide you with valuable information from which you may be able to tune your business. An entitlement management system is often integrated with other systems such as CRM, ERP, and LDAP to perform the operations backbone for all business processes. An entitlement management system is also the system of record for software downloads, and license key generators and can provide valuable information for improving processes and increasing revenue. Consider the following, “What can a COTS software licensing and entitlement management system do (provide) for me that an ERP or a homegrown system can't provide?” Determine channel velocity, or, sales effectiveness through a channel –determine the elapsed time from when an order is shipped to a channel partner, to when it is eventually activated by the customer to find interesting patterns in different partners and partner processes, helping you to improve the time to revenue, and perhaps increase revenue. Measure the effectiveness of new upgrade campaigns by measuring the time it takes for customers to activate new versions of products from the time the release is made available. Establish support business readiness parameters for support by knowing, based upon the historical time from shipment to activation, when you may receive the bulk of support calls regarding features/functions in the new release. Find where piracy may be occurring, or, where there are up-sell opportunities, via standard reports to determine which licenses are activated multiple times, or attempted to be activated multiple times and establish patterns. Find sales opportunities by looking how many demo license activations actually convert to revenue licenses, and, if in the process there are patterns around channel partner, geography or type of user that allow the tuning of such programs. When selling through a channel, get more real time-data on which products are selling best by looking at product activation reports. By viewing activation reports in an indirect sales model, tune up-sell programs by knowing which combinations of products are actually used in combination, and correlating that to geography, channel partner, or type of customer. By viewing patterns in activations for new product releases, determine how many products are still active for obsolete or end-of-life products, so that you can determine the need to create a campaign to migrate these customers to new releases?” So, are you ready for some Jeopardy? If you need answers, just ask the right question, “What kind of business intelligence can I get from a COTS entitlement management system ?”

Want a Better Customer Experience, Think Software Licensing: Try the “Out-of-Box” Experience

By: Cris Wendt Want to make it easier for customers to adopt your software products, license models and technology? If so, try