Module usage report

The module usage report provides a summary of usage per month of optional module licenses (for example, change author, requirements access, and so on). Module use reporting may occasionally show that the number of licenses or keys used exceeds the number of licenses purchased. This is typical where the number of purchased licenses is intentionally minimized. Siemens Digital Industries Software allows for a small over-use. Administrators are notified about the over-use so that they can work with their Siemens PLM account representatives to identify the total number of licenses and keys required and take appropriate steps to comply with the licensing agreement. When entering parameter values to generate a module usage report, you can: Enter the month as either a number or text (3-character abbreviations or alphabetic month values). For example, to indicate March, you can enter 3, Mar, or March. Enter the year values. For example, to run the module usage report for all months from January 2017 through December 2018, enter 2017 in From Year and 2018 in End Year. Leave the month fields blank and just enter the year value. For example, to run the module usage report for 2018, enter 2018 in From Year and 2018 in End Year. The Module Usage report saved to a .csv file and viewed in Excel resembles the following: Example module usage report Note The module Usages numbers are accurate for all reported months. However, the Purchased numbers are not stored in the Teamcenter database; all months for Purchased licenses show the numbers pulled from the current license file at the time the report is generated. Therefore in the following situations the purchased numbers in the report are not historically accurate: License modules have been added to or deleted from the server's license file between usage and running of the report. The number of module licenses in the server's license file has increased or decreased. A module has expired in the server's license file between usage and running of the report.