What is the purpose of this information?
Accounts have the ability to run applications based on their contract type -
Although Open Access can be effectively used to "Pay as you go", not taking the time to properly understand licensing can result in unexpected invoicing.
Background
Accounts are allowed a peak usage (the highest number of unique users in any given usage interval) equal to what is covered under contract. Any usage in excess of what is covered under contract may result in a term license (typically listed as "TL") Invoice. Note that the TL invoice covers the entire period regardless of whether the peak usage (in excess of owned quantity) happed for a single 10 minute interval, or consistently over the entire period.
The period for the TL invoice is based on the contract type. -
Usage interval (the period of time that is looked at in regards to determining peak usage) varies by contract type -
Usage is recorded as follows -
Researching what caused the TL
Users will need at least one of the following roles are able to access the necessary reports:
To determine why you are being billed for you can look at the Product Usage Report. Refer to the following WIKI on how to use this report -
How do I use the Product Usage Report?
You may wish to note whether the term license usage was the result of a checked out license or not.
.If you need further details , after you have determined the date of the term license usage from the product usage report, you can get further details from Subscription Analytics.
Under Subscription Analytics you can research further to see what happened. The general WIKI on Subscription Analytics is here-
Subscription Analytics
If still more detail is needed, the "raw" data can be exported
Analytics Data Export
Some Specifics by Product
Some products are suited products that will install multiple configurations from a single executable. It is up to the user to configure the product correctly so that it draws the correct license when starting the application. Choosing the wrong product / feature level may generate unwanted term license usage.
AutoPipe Applications
gINT Applications
Municipal Applications
The following Municipal applications need a default feature level set before they can successfully draw a license -
Plaxis Applications
Plaxis 2D V20
Plaxis 3D V20
Plaxis 2D V21
Plaxis 3D V21
SACS Applications
Note that these are all in the same download!
Base Products
Add-on Modules (Separate Purchase)
STAAD.Pro
Synchro Pro Applications
Preventing Future TL Invoices
If the term license usage was the result of a checked out license (and the license is still checked out), the license can simply be checked back in This can be done either from the client itself via the License Management Tool or Bentley License Tool [depends on which license model the application uses] or thru an Administrative Interface by an administrator.
If you are using SELECTserver based licensing, there is not much in the way of Bentley provided controls to help you limit usage (this is why SELECTserver based licensing is depreciated, and Bentley Switched to Subscription Entitlement Service licensing).
If you are using Subscription Entitlement Service licensing, you can set up "License Alerting" (this doesn't prevent termed license usage, but a warning message will pop up stating you are about to overuse, and the user would have to acknowledge to proceed). For step-by-step instructions see the following wiki -
How to enable and configure license alerting for Subscription Entitlement Services products
https://communities.bentley.com/products/licensing/w/licensing__wiki/42192/how-to-enable-and-configure-license-alerting-for-products
Setting license alerts does not guarantee protection from a Term License. Refer to the following WIKI -
Limitations of Threshold Alerting
https://communities.bentley.com/communities/other_communities/licensing_cloud_and_web_services/w/wiki/52435/limitations-of-threshold-alerting
Other Language Sources