Sep 07, 2016 - 02:42 AM
As you say Martin, if you cannot - or have difficulty - measuring it dont allow it in. Deal with complex licensing at either renewal or when there is a decison about extending the product, as publishers are more likely to agree to new terms when they are about to get some extra cash....
Sep 07, 2016 - 04:28 AM
Complexities in licensing are too often unnecessary. They often arise when a vendor changes the licensing terms on a version upgrade or when a vendor acquires a product and then tries to fit the acquired product metrics in to their own licensing models. We often all say that if you cannot - or have difficulty - measuring it don’t allow it in – but we should probably also include if the vendor cannot provide a clear straight-forward way in which their metric can be measured then we should not allow it in.
Licensing models are supposed to be straight-forward ways in which the customer and vendor can measure the use of the software to ensure compliance. Clearly defined metrics with clear definitions around terms such as user/employee, server/CPU/Cores are essential in this process.
As subscription and Cloud licensing increases, the vendors will have to introduce ways in which they can track usage so that they can ensure that they receive what they consider to be appropriate revenues for the use of their products. The metrics should therefore be straight-forward as the vendors will measure the usage to create their invoicing. If the vendor can measure the usage then we should be looking to get regular reports from the vendor showing the usage and allowing us to monitor usage.