Licensing inactive units
In an HRIS (human resources) application there are active and inactive employees - the inactive need to be kept for legal reasons but also for application effectiveness as employee id is used as a lookup in many modules.
From a licensing standpoint, the industry practice is to only charge for active employees - if a client has 100 active employees and 500 inactive they only pay for 100.
The problem is that at any time an employee could be moved between the two states which opens the system up to manipulation - for example, client above archives 100 employees and moves 100 of their currently archived employees to active hence never passing 100 active employees but, in effect, they are managing 600 employees but paying for 100.
This use case is specific to an HRIS but how do others approach licensing for inactive or archived components when that component is their main pricing meter? The only way I can think of is to either restrict the movement from inactive of active to x% of their total active per month or limit the number of inactive to x% of total active - any other thoughts how to do this without impacting the genuine customers?
-
shouldn't the question read "they only pay for 100" ? – Jim Galley 10 years ago
-
I can't believe you took the time to type all that out. Who cares? Really, if they want to, someone will always game any system. Make it so that they pay for any active employee in a month, then if they mess around as you describe, they'll still get billed. – Steve Jones 10 years ago
-
Yes it should Jim, changed – Bhttoan 10 years ago
-
@SteveJones Just because someone will always try to get around any system is not a reason to not try and stop them and as we are building the integration to our billing system right now we are working through every possible scenario and this is one which came up. – Bhttoan 10 years ago
-
@bhttoan what I mean is the answer is obvious and trivial, as I said in my previous comment. No need to have long explanations. – Steve Jones 10 years ago
1 Answer
Consider letting them game the system, but make it very inconvenient. For instance, consider things like only allowing for active employees to be viewed in Reports. Or, only allow 1 employee to be moved at a time from Active to Inactive. Or something similar...
I don't like trying to eliminate the possibility of them gaming the system. And I don't like the idea of charging for every employee who was Active even briefly. These approaches are often anti-productive because they tend to inconvenience the normal users who are NOT trying to rip you off.
