Licensing (Depracated)
What is the current licensing model?
Outline
Generally the process to license a Recorder is:
- Use a generation tool to create a licence key (this will include assigning the "Recorder ID")
- Apply the licence key in the Recorder web UI
- Generate further licence keys, one per integration required (bound to the Recorder ID)
- Apply the licence keys in the Recorder as before
Yusuf Limalia (Unlicensed) , Simon Jolly (Unlicensed) - what is the commercial licensing model? Per recorder then what? How do agents figure? What other SKUs/features are licensed separately?
There are different types of licence (e.g. dongle-based, software-based, timed). I usually use software-based. When you do this there is a further step (using quotes below where where I'm not totally sure of the terminology)
- For software licences the licences need to be "signed" in some way, otherwise they expire after a time period (a month or so I think)
- The Recorder web UI has a page that will generate you a "signing request" file to email to RBR support desk
- They do some magic to produce a "signed" file which can then be uploaded to the Recorder web UI (Phil also knows how to do this part, but I don't)
- The license is then permanent
New Platform Licensing Model
Candidates for technical licensing
http://www.licensespot.com/features/licensing
https://lab.junian.net/Standard.Licensing/
Merge Below
=======================================================================================================
Pages have been merged to avoid duplication. Below the line Includes the first draft of analysis.
Business Requirements: Pete Ellis (Unlicensed), Josh Hepworth (Unlicensed) and Yusuf Limalia (Unlicensed)
Technical Discussions: Simon Jolly (Unlicensed) and Kirill Zotkin (Unlicensed)
=======================================================================================================
Licencing is one of the largest features the project needs to cater for. It is arguably the most important from the businesses perspective as well as it has a monetary value attached to it. It as also the value that sales people as well as customers will have at the forefront of their minds. We must ensure we get this correct from the outset.
Licencing Models
The business requires a few licensing models to be designed and developed. This document will outline both the business requirement and technical architecture required to achieve said models. Each licencing model needs to cover both on premise and cloud deployments of the application.
Per Channel
A customer will want to licence the system on a per channel basis. This is the licencing model model that most customers use and needs to be catered for in the new system.
Eg: A customer has a licence for 100 channels, but they have 200 users (Day staff and Night staff) each with a single device that requires a single channel. The system will only allow 100 of those users to be recording simultaneously at any point in time.
Per Device
A customer will want to licence the system on a per device bases. This builds on the per Channel licence model. The consideration here is that a device can have multiple channels.
Per User - Recording and Search & Replay (Perpetual / Subscription)
A customer will want to licence the system on a per user basis. A user is defined as a single person who has record-able items or devices. A user may have multiple devices such as a desk phone and a mobile phone.
Eg: 10 Users can use the system concurrently and the customer will either be billed once (perpetual) or on a monthly basis (subscription).
Per Device - Recording and Search & Replay (Perpetual / Subscription)
A customer will want to licence the system on a per device basis. A device is defined as a single record-able item such as a desk phone or a mobile phone.
Eg: 10 Devices can record concurrently and the customer will either be billed once (perpetual) or on a monthly basis (subscription).
Per User Time Limited - Recording Search & Replay (Perpetual / Subscription)
A customer will want to licence the system for a specific amount of users and have it active for a limited amount of time. This can be used for demo systems
Eg: 10 Users can record concurrently for up to 1 Week
Eg: 10 Users can record concurrently for up to 1 Month.
Eg: 10 Users can record concurrently for up to 1 Year.
What Happens When Recording Licences Expire?
The system will continue to record until the storage limit is reached but the search and replay will be disabled until payment is made. The amount of "Grace Period" needs to be configurable.
Eg: Customer A is allowed to record on the system for 6 months, and the search and replay UI will be disabled. Recording will not happen after the grace period has ended.
Metered Licencing
Customers will be charged depending on how much of the system they use. This is going to be tricky on on premise deployments as the deployment will require a constant internet connection. For on Prem deployments customers will need an offline method of installing a new licence. This licence could be generated via a licencing portal where a customer could upload their usage reports. This portal is being discussed versus sending the customer an email.
Licenced per API Requests
While we will not charge for x number of API request, we require control for who is using our APIs. The idea is that a customer / vendor would like to access our API suite, we would then give them a licence to use the APIs after gathering information about their company etc.
Mixed Licencing
A customer will want to have a mixed set of licences.
Eg: A customer is paying for 100 perpetual channel licences. Occasionally the customer has contractors come in and want to record their calls. The customer will want 10 metered channel licences over and above the perpetual licences.
Feature Licencing
Per Feature (Perpetual / Subscription)
There are features over and above call recording that customers can purchase. Some features will be licensed on per enterprise basis, and some features will be licensed on a per user per feature basis. Features can also have mixed mode licensing.
Eg: All the users on the system can view the live calls ongoing in the system
Eg: 10 Users can have all their calls transcribed
What Happens When Feature Licences Expire?
There will be three categories of what will happen to a feature when its licence expires.
- Feature functionality is paused, functionality resumes when licence is renewed. Any functionality that needs to be applied retrospectively (such as transcriptions) will be applied once the licence is renewed. (Category A)
- Feature functionality is stopped, functionality is restored once licence is renewed. This will cover features like Record on Demand that won't require retrospective application to their functionality. (Category B)
- Feature has limited functionality. This will cover UI elements that may be licensed. Restrictions such as disabling of pages etc. may be applied on expired feature licences. (Category C)