Software Entitlement vs Enforcement
We had another discussion today on the differences between entitlement and enforcement in software licensing schemes.
Here is an image we have used to draw the distinction from our perspective.
We’ve developed our systems to enable publishers a high degree of control over the entitlement of software and technology. Preserving flexible entitlement choices for publishers eases some of the burden on downstream enforcement tools in a number of business scenarios.
Jay – nice article. We view the entitlement as the “rights”, and “enforcement” as the method to ensure usage “compliance” with those rights.
The method of enforcement (technology) and user experience when a user is out-of-bounds with those rights is dictated by the balance of revenue recovery and the customer experience for the software publisher.
We view the market, product lifecycle, geography and other factors when helping software companies develop one or more “enforcement profiles” to govern out-of-compliance experience for the end-user.
This enforcement profile, along with the license models, can then be used to tune the license technology implementation and back-office processes.
Cris Wendt
March 14, 2010 at 14:51 pm
Thanks Chris,
Understood. I think OMS SafeHarbor and your company, Flexera, are largely consistent with these definitions. We are seeing more requests for information from publishers of all types of digital assets looking to make the distinction between “who gets our stuff under what conditions” and, “how do we help them stay in compliance with those terms after delivery”. Hopefully this thread helps.
Thanks for the comments.
Cheers,
Jay Nash
Jay Nash
March 16, 2010 at 14:36 pm