Best Practices for UEM License Management and Consumption?

Hi Chris,

I am not sure such a document exists.  Maybe one of our enablement services folks or engineers may have some ideas around your request.

Have you considered limiting the percentage of visits collected at the application definition level in the UEM settings?  I know it contradicts the idea around capturing all visits and user actions, but it could extend the life of the licensed visit count.

Hi Chris,

Remember that UEM is licensed by visits not transactions so it might last a bit longer than you're thinking.  Also, you can restrict UEM by IP range or browser type.  You could also try and adjust the "visit coverage" found on the user experience management settings.  I personally haven't messed with that setting since typically you want every visit to be recorded.

Hope that helps.

Mike

Hi Chris,

I'm looking for the same advise.  From the looks of it there does not seem to be a rule of thumb or best practise.  Since asking this question in early December have you come up with any of your own practises to help put some constraints on the license consumption?

Thanks,

David

Hi,

To get the best answer to your questions, please contact your sales contact. He should know how your contract looks like and depending on your version and contract he can discuss the best scenario for you.

But I try to summarize the key items:
The UEM license is based on an annual visit volume. This volume will be automatically renewed every year. Annual visits are sold in blocks and you can start with a small block and add additional blocks if needed.
This helps if you don't have an estimation of your visits per year. After 100% of purchased annual visits are consumed, a buffer of additional visits will be provided.
The buffer is calculated as the number of annual visits purchased divided by 12.
The annual consumption start date for all the blocks would be the same as the first block purchased and would automatically reset to the full available amount of visits at the beginning of each year.
Informational email notifications will be sent to registered administrator when 75%, 90%, 95% and 100% of annual visits are consumed during the maintenance (consumption) year.

Which visits are considered for reducing the license volume?

• Only visits with more than one user action are reducing the volume - So bounces will not reduce the volume.
• There is no difference between native mobile and browser (web/mobile) visits for licensing
• A visit ends when the browser is either closed or inactive for 30 minutes. If then the same user accesses the application again it will create a new visit, which will also consume a visit from the volume.
• Long running visits will reduce every sixty minutes the license volume. Example: if a visit has a duration of 140 minutes, it will show up in the visit dashlet as one visit, but the license volume will be reduced by three visits.
• A visit can't cross applications. Applications and visits are a one to one mapping. So if you have defined two applications by url pattern and your customer is accessing both apps, it will result in two visits, even if it was without a timeout.
• There exists Self-Monitoring measures for controlling the visit licensing volume:
  1. UEM - Used License Volume (Visits)
  2. UEM - Visits not considered for License (Bounce)
  3. UEM - Visits split for License (Visits > 1h)
     
     

Thanks Alexander!  I appreciate your great input on this!  I will also be following up with our sales contact.