Need help working from home with your Bentley software? We're here to help - click here
How did I incur overcharges for 3 license of AutoPIPE when I only have 2 license?
AutoPIPE V8i 09.05.xx.xx and lower does not support trust licensing, and since these version of the program require an available license, how can I possible be over using my licenses?
AutoPIPE V8i 09.06.xx.xx and higher does support trust licensing, how would I incur overusage with this version of the application.
Regardless which version of the program currently being used, suggest to ask your Bentley On-Site Administrator to log into the SELECTServer and pull a usage report for the time period in question. If you have access to the SELECTServer but do not know how to create such a report, contact the Bentley Licensing department for assistance.
Company has received information that there has been overusage for AutoPIPE or other applications for the past billing cycle, How to view the details of when overusage had occurred?
Detailed information would only be available to those people who have been appointed as Bentley On-site Administrators at your company and Bentley employees. These people have access to log into the Bentley SELECTServer and runs a "Daily Peak Application Usage" report (example shown below):
Shown in the image above, this account, only has 2 licenses on their contract. This is indicated by 2 methods:
1. Numerically, in the column indicating "License" = 2.
2. Graphically, the bold horizontal line is placed at a height of 2 per the left axis of the chart. Any indications above this line is an overusage occurrence.
For a given period, Bentley allows 3 overusage, However as seen above, there was 7 occurrences during this period. As a result, a invoice for the overusage is sent out to the respective company.
How can I see what occurred on these days to indicate overcharges?
To clearly understand why the overusage occurred, create an "Application Usage By Hour Report", shown below
Here one can clearly see when particular applications are checked out and checked back in.
User #1, checked out the license from 10:05 PM to 10:11 PM
User #2, had 1 license checked out the entire day.
User #3, checked out a license from 1:27 PM to 10:01 PM
Since SELECTServer XM release (over 8 years ago), license usage has been counted by the number of machines that used a product at any time in a given hour. The number of machines using the product simultaneously at a given moment has no bearing on the usage calculation. For example, the company in the screenshot above has two licenses of a product, yet usage numbers greater than two licenses are still possible since a User may check the license back in earlier in the hour to be checkout by another User by the product later in the same measured hour.
Company has only two licenses, where the application needs a license in order to function. However, an overusage was logged, How could that of happened?
SELECT Open Access Usage Calculation
The application was used by 3 different computers during the 10 'o clock hour (i.e. 10:00 PM-10:59 PM).
User #1 - from 10:05 pm to 10:11 pm - logged as 1 usage
User #2 - from 10:00 pm to 10:59 pm - logged as 1 usage
User #3 - from 10:00 pm to 10:01 pm - logged as 1 usage
Total usage = 3
Again, this Bentley policy of accounting for application usage is nothing new. In the past, overusages were dealt with by the Account Managers making personal phone calls, which took a considerable amount of time. However, today the process has since been automated, allowing for notifications to be transmitted in a more timely manner for all users.
Please note that Quarterly Term License (QTL) invoices for overusage may in some cases be cheaper than purchasing a new license. So overusage should not necessarily be viewed as a penalty. It is essentially a quarterly lease that is provided only as needed. Your account manager can help you determine the most cost-effective mix of product licenses to own and overusage charges to be expected for a given time-period. For complete details on Select Open Access, see also the following: Application Usage TechNotes and FAQs
Managing License issue