Siebel CRM – Employee, customer and partner products

oracle warehouse

Organizations can make use of the internal Siebel products by obtaining licenses for the Employee Products, and can make use of the external Siebel products by obtaining licenses for Customer Products and/or Partner Products.  Understanding which licenses are required in specific situations is necessary to make sure that you are correctly licensed.

External and internal

When using external facing applications you should purchase licenses on a metric for external (non-employee) users. External licensing (e.g. on the legacy Concurrent User metric or Processor) is more expensive than internal licensing (e.g. on the legacy Named User metric or Application User).

Many organizations provide external users access to internal applications without owning external-type licenses. In these situations, the license compliance position will be determined on the available (internal) license metrics – typically Named User, Application User or Concurrent User – resulting in large non‐compliance situations and associated costs.

Concurrency will migrate to processor if licenses are exceeded

There are legacy licensing metrics (e.g. Concurrent User) that Oracle nowadays does not sell anymore. In case a customer on old license metrics exceeds their current license grant – even by just one concurrent user – they are required to migrate the old license metrics to the current license metrics and purchase additional licenses on the new license metrics, which are typically more expensive.

Properly keeping track of the changing population will allow organizations to make sure that legacy license metrics do not exceed the entitled quantity, and gives time to assess the new metrics on which Oracle sells its products today. Keeping track of the changes in Oracle’s licensing practices and migrations will keep you up to date of possible implications that may occur when extending the use for certain old metrics.

Custom views determine usage

Many organizations have implemented customized views in their Siebel installation to accommodate their specific needs based on the standard Siebel functionality. The bulk of Siebel usage in organizations comes from custom views. You should pay close attention to what Siebel modules and functionalities the custom views are build upon. Only one single custom view mapped to an unlicensed application may result into large compliance risks and associated financial risks.

Most Siebel CRM customers don’t realize that users with access to custom views are required to be licensed as well for the Siebel modules on which the customizations have been applied.

Make sure you have the right expertise

You can of course invest in staff and building knowledge completely on your own to address software compliance issues. But you might also want to consider enrolling in a fully operational license management program. This can be done in less than three months and will be tailored to the specific demands of your company.

This article was published on 08-03-2016