Nov 01, 2019 - 02:13 AM
It depends what they are designing, what it does, how it is measured, monitored, controlled! Is there a route for restriction (so enforced compliancy like O365) or relaxed approach based on annual monitoring (Windows Server on an Annual TrueUp), or consumption of resource like Azure.
Once you have worked out your license metric, it will then be identifying the value of the license (monetise) to ensure a profit is made or R&D investment is returned.
Essentially you want a strategy and approach that can be managed via an automated process if practical so both the designer and consumer can easily identify a clear position.
Or you could go the Oracle/IBM route where you have 16 different models for the same product and each price is based on CPU's blood type on the 3rd day of each other calendar month aside from the 1st Tuesday before the weekend where its the 23rd and then its the other rules...
Nov 01, 2019 - 02:38 AM
I doubt you'll find any resources available online as these things are usually kept confidential or not explained to the public. I would approach this as follows:
1. Think of the intended use cases and added value your product adds to the end user. Also think of what deployment scenarios would make the software product perform better, i.e. would an increase in CPU capacity make your product perform better (perhaps prodcess tasks faster)? If so it might be good to design a CPU related metric (you also need to think which CPU metric drives the performance, is it actual number CPUs? or CPU cores? do you want to measure actual capapcity or potential capacity i.e. nuber of actual CPUs /CPU cores or number of sockets?).
Perhaps it's a client product, intended for individual use, in which case you should define user based metrics. Or perhaps it's a server product where you want to measure the number of devices connected, or users (named users/devices or concurrent).
2. Identify simillar products and research their related license models. Think of what the similarities are and see if you can apply the same principles to your product. Also as important is to identify the differences, and any license rules which might be redundant for your use case. That is the part where you customise the license model to fit exactly your product.
I suggest you make a list of the most common license metrics and their related definitions. You can start with the top vendors (Oracle, Microsoft, IBM etc.) there are plenty of resources online. See which ones apply to, or are relevant for your product and think of how you can tailor it for your use case.
To conclude, a software license desing (terms and conditions) should be a derivate of the intended product use cases and the license measurement (metrics) should be based on technical deployment scenarios where the product performance is enhanced as a result of hardware configuration (e.g. increase in capacity) or as a result of software configuration (e.g. increase in usage capacity, for example more users or devices).
Hope this helps! Let me know if you require further clarification.