Skip to main content

Customers

  • Updated

The Customers section presents all the information collected about licensable users, your end customers, and customer groups.

Users

The USERS tab contains details of all licensable users of the service. Typically, users are the employees of your customers, service accounts, and administrators. Some important fields to mention:

  • Licensing start date: When you define a licensing start date, the SPLA usage report will take that into the account and only count that user if the licensing start date is in the date range of the report observation period.
  • Licensing end date: When you define a licensing end date, the SPLA usage report will take that into the account and only count that user if the licensing end date is in the date range of the report observation period.
  • Account expires on: This field is collected by OC Scanner from the Active Directory. That field is taken into consideration when the SPLA usage report is calculated.
  • Other attributes: If you wish to scan additional attributes of users, you can configure that in OC Configurator. These other attributes and their values will be listed as comma-separated in this field.
  • Exclude from SPLA usage report: By default, all users with SPLA relevant licenses are included in the SPLA usage report calculation. You can exclude users manually over this field. But the better and more secure approach is to do that over scripts.
  • In the field Map same users over, you can map different user accounts which belong to the same user over user attributes. If the user accounts have the same attribute values, they will be mapped to one user for the licensing calculation.
  • Status: The status of a user is collected by OC Scanner.

Multiplexing (Pooling)

For the user licenses, it is sometimes difficult to collect the real number of users accessing specific software, which is very important for an accurate SPLA usage report. For instance, it is possible that users have indirect access to a SQL server over a third-party application. In such cases, OC Scanner will not be able to know, how many users are actually accessing the SQL server. There are different approaches you can cover such scenarios. The first one is to define the relevant AD groups or OUs which can access that software, the other approach is to enter the real number in the SOFTWARE tab in the detailed user view in the field Effective number of SAL (multiplexing / pooling).

Customers

The CUSTOMERS tab contains details of all your customers. They are either created by the imported data scanned by OC Scanners or they can be created manually in this section. If they are automatically created by the data import, then the customers were already configured on the scan file level in OC Configurator.

If you create the customers manually in OC Reporter, then you need to map the infrastructure machines such as the virtual machines or the licensable users over scripts to the customers. Click here for more information about scripting.

Some important fields to mention:

  • Customer group: Customers can be grouped into customer groups. That allows setting values on the customer group level, which are inherited by the customers in that group.
  • Internal ID: This field can be used by you to set the ID of the customer, which you are using in your internal systems.
  • Extra field 1: As the name already says, this is an extra field to be used by you to store some extra data of the customer.
  • Extra field 2: As the name already says, this is an extra field to be used by you to store some extra data of the customer.
  • Own use: If this checkbox is set, that means this customer is your own company. That field is used to calculate if your own usage of the entire SPLA usage is not higher than 50%. Please keep in mind, own usage of SPLA needs also to be licensed and reported.
  • SPLA end customer enrollment no.: If your end customer reports more than USD 1000.- in SPLA usage, you are required to apply for an end customer enrollment number and report that customer separately to your reseller. Enter in this field that enrollment number, so OC Reporter will calculate the SPLA usage separately for that customer and licensing data gets deducted from the main SPLA report, and shown in a separate tab.
  • CSP tenant ID: Enter in this field the CSP tenant ID of the customer. That is important for the QMTH report.
  • Price category: In this field, you can set up the price category of the customers. If the field is empty, by default the price category will be Corporate.
  • Currency: You set up in which currency you are billing your end customer.
  • Start date of end-customer testing phase: You can set up the start date of the testing phase. That field has no effect on the SPLA usage calculation, it is more informal data.
  • Licensing start date: When you define a licensing start date, the SPLA usage report will take that into the account and only count the users and servers assigned to the customer if the licensing start date is in the date range of the report observation period.
  • Licensing end date: When you define a licensing end date, the SPLA usage report will take that into the account and only count the users and servers assigned to the customer if the licensing end date is in the date range of the report observation period.
  • Customer VM billing calculation: By default, OC Reporter calculates the VM licenses of the customers in the same approach as it counts it for the reseller. It takes the host into account and calculates then the OS licenses. That is not always the ideal approach for customer billing. In this field, you can configure the approach you would like to use for the VM billing calculation. The configuration is defined in four parts, each part is separated by a semicolon ":".
    • The first part defines on which level the calculation should be done. We can define if we want to take the virtual machines or the host into consideration. In the first part, two options are available: vm or host.
    • The second part defines which attribute of the server should be taken for the calculation. We can calculate based on the number of cores (number_core), number of CPU (number_cpu), the hard drive space (hard_drive_space), the used hard drive space (used_hard_drive_space), or the number of RAM (number_ram). There is a special parameter count that can also be used to simply count the number of virtual machines for the calculation.
    • The third part defines if there is a minimum amount is required of the calculated attribute in the calculation. For instance, you could set the number 1 ins this part, which would mean the minimum required amount is one for the billing calculation.
    • The fourth part defines the sales price.
    • Example:
    • vm:number_core:1:4.35
    • In this example, **vm **is the first part, number_core is the second part, 1 is the third part and 4.35 is the fourth part.
    •  
    • Note: If you want to disable the OS licenses entirely from customer billing, simply assign the relevant underlying hosts to the customer named as your company. In that case, the OS licenses will not anymore be licensed for the end customers.
  • Scripts to be executed after data import is completed: In this field, you can execute scripts related to the customer. You can assign users or servers to the customer, or exclude specific users or servers from SPLA, etc. Click here for more information about scripting.
  • In the field Map same users over, you can map different user accounts which belong to the same user over user attributes. If the user accounts have the same attribute values, they will be mapped to one user for the licensing calculation.
  • Status: The status of the customer can be set by you. If it is set to Archived, the users and servers of that customer are not counted for the SPLA usage report.

Customer Groups

The CUSTOMER GROUPS tab allows you to manage your customers by grouping them and applying common settings to all customers within a group. The settings in the customer group are inherited by the customers unless they are overwritten on the customer level.

Salesprices Licensecatalog

In the detailed customer or customer group view, there is a tab SALESPRICES LICENSECATALOG. In this tab, you can set a sales price for each license. You are also able to set the number of sold licenses and if available license mobility numbers.

Related articles