The 'License Model' field is an optional field. The text below is a citation from the online help page that you can open by clicking on the '?' help icon from the page where you took the screenshot: Tip:  A license model defines the product use rights that are added to the license (for example, the second-use, downgrade or upgrade rights). License models and their links to applications are a part of the product use templates from the Product Use Rights Library. Therefore, there are no recommended license models when: You have not purchased the appropriate option for  FlexNet Manager Suite  that covers the  Product Use Rights Library  for the publisher of your application (as above, clear the  Show only recommended license models  check box to see other models from this publisher) The particular application is not listed in any  Product Use Rights Library  (clearing the same check box now shows general models for the selected license type). If you choose not to select any license model, or the selected model does not meet all of your requirements, you can later edit these details in license properties.     ... View more

Hi Regan, I'd probably say YES to your first question, and NO to the second one: The purchase order (PO) for the perpetual license entitlements SHOULD BE be linked to a contract in case the license is affected by the contract. For the maintenance purchase order, it probably does not matter as long as the license that the maintenance PO will be applied to is linked to the contract correctly. You should set maintenance = TRUE for the perpetual entitlements ONLY IF maintenance has been included in the initial purchase of the perpetual license. This may have been the case even though you obviously did buy extra maintenance in the second PO. For the second purchase order, you should not set Maintenance = TRUE as this second PO IS for maintenance, resulting in maintenance being applied to the perpetual license, typically for a fixed amount of time. ... View more

Hi, The IBM PVU license consumption calculation relies on peak usage data by definition. PVU consumption related raw data can be collected either by ILMT or by using the Flexera agent. In any case, you must historical consumption data available for your servers to allow for  calculation of peak usage data. If you manually assign a license with PVU metric to additional computers, you have to: Make sure that conditions for PVU usage calculation are met. The agents running on these computers have to learn (via download of the policy) that these computers are linked to a license with PVU metric now. Make sure that FNMS is configured correctly for PVU licensing. This will allow Flexera agents and VMware scanning to run every 30 minutes as required by IBM Only after agents running on all servers linked to a license with PVU metric have downloaded the PVU settings, they will start collecting IBM PVU related consumption data and will be doing the frequent hardware scanning required by IBM. You have to be patient and wait for the agents running on the two computers that have been linked to the PVU license recently to pick up the new information. Give them some time to collect and upload PVU related consumption data. Once these agents have collected PVU data for a reasonable amount of time you will see peak consumption data. Once peak consumption data are available for your servers, PVU consumption will be calculated for servers that have been manually allocated to a PVU metric license, too. ... View more

Hi Gopal, In this scenario, instead of exempting certain servers from consuming a license, a recommended best practice is to: Use license scoping (tab "restrictions") for restricting where a license can be used (like by Organizational Unit) Manually allocate your computers (servers) to the license As you noticed, if you exempt a device from consuming on a software license in FNMS, that device will not consume any other software license that has been configured to use the same application. This means that the device will not show any usage data for the application, too. ... View more