Oracle Siebel licensing – How does it work? – 2022

Oracle Siebel licensing how does it work? In this article we will cover the different Oracle Siebel license models and the top3 Siebel compliance issues we see in our Oracle license reviews. When you search on google there are no official documentation available from Oracle. Lets make an introduction post about how Oracle Siebel works. In a standard installation of Siebel all the modules are unlocked, and you do not need to request additional serial keys from Oracle. This means that an Oracle Siebel end user can use Siebel products that they are missing licenses for.

Three different Oracle Siebel licensing models

 

Application User

Application User – This is a license model where you license every individual who are authorized to use Siebel. The licensing implications are that you need to count multiple users if they are sharing username/login to Siebel. You also need to license users who may not actively be using Siebel anymore, such as users who left your company or users who changed department.

Recommendation: Make sure that you have a process for leavers and are constantly working on user administration for Siebel users. To review Siebel licensing you must map each responsibility / view and then map them to the appropriate Siebel module.

Custom Application Suite (CAS)

With CAS you have created a unique bundle that includes multiple Siebel products. Instead of keeping track of users for each module you have created a package of multiple Siebel products and the users you have are all counted towards that number regardless of if they are using those Siebel products or not.

Recommendation: This license model is easier to manage from a license management perspective, but many Siebel customers are left with a non-optimal licensing model as they have users who are not using some of the Siebel products. To review CAS license model it is very similar as application user, you need to review the responsibilities and connect them with Siebel views to understand licensing position.

 

Enterprise metric

 

With the enterprise metric you are licensing your whole company. A very common license metric is “Enterprise $M in Revenue” where you license Siebel products based on your company revenue. Note that “company” means the companies that are listed on your Siebel licensing agreements.

 

Recommendation: Review customer definition and compare it to your company revenue if that is your licensing metric. Customers should carefully review which legal entities to include in the licensing agreement when entering Siebel enterprise metric agreement.

 

Siebel licensing, which are the main 3 license compliance risks that companies face. Oracle acquired Siebel in 2005 and as many other companies, Oracle slowly changed the licensing models to Oracle standards. We mainly deal with Oracle standard licensing problems in this blog. However, if you have older Siebel licensing metrics, you can have many other types of license challenges.

 

Siebel licensing rules

 

No Oracle technology products are shipped with Siebel, this means if you want to run an Oracle database this must be purchased seperately. 

 

Every Siebel customer must license, at a minimum, one Siebel CRM Base Application. Typically, each employee user of Siebel applications requires a base. Start by selecting the Siebel CRM Base for each Siebel user. All users requiring a base must license the Siebel CRM Base. Then, if the customer requires industry specific functionality, select the industry base option(s) that most appropriately meet customer needs–in addition to the CRM Base. Note that if the customer requires an industry solution, all users must have an industry base option and the Siebel CRM Base

 

 

Siebel CRM – Partner Applications

For each Partner user, Siebel partner options must be licensed at the same level or less then the Siebel Partner Portal. For Example, if the customer licensed 100 Siebel
Partner Portal then Siebel Partner Commerce must have a quantity of 100 or less. This rule applies only to options using the Registered User metric

 

Siebel CRM Web Channel pricing is designed for Siebel customers who desire to extend the usefulness of their Siebel deployment by providing additional users access to Siebel Business
Objects with defined methods, events, and data and reuse Siebel Business Objects and project Siebel Data through an independent User Interface via

 

Built-in scripting of Siebel objects using Siebel VB, Siebel eScript, and Browser Script Component Object Model (COM) using the Siebel Web Client Automation Server, Siebel COM Data Control, Siebel COM Data Server, and Siebel Mobile/Dedicated Web Client Automation Server, Java or J2EE using Siebel Java Data Bean, JMS or JCA

 

All modules, except those in the “Applications Not Requiring CRM Base” section, require a Siebel CRM Base–see the price list supplement for detailed
requirements on each module. All Oracle customers can add CRM modules to their solution–including Industry users. There are some modules that have an industry
specific version. When licenses an industry base option check that industry module section for a replacement. n. (e.g. if the customer licenses the Communications, Media & Energy base option and they want contracts functionality, they should license Siebel CME Contracts not Siebel Contracts

 

 

Common Siebel licensing definitions

 

Application User: is defined as an individual authorized by you to use the applicable licensed application programs which are installed on a single server or on multiple servers regardless of
whether the individual is actively using the programs at any given time. If you license the Oracle Self Service Work Request option in conjunction with Oracle Enterprise Asset Management, you
are required to maintain licenses for the equivalent number of Application users licensed and you are granted unlimited access to initiate work requests, view work request status and view
scheduled completion date for your entire employee population. For Order Management, application users are allowed to manually enter orders directly into the programs but any orders entered
electronically from other sources must be licensed separately by Electronic Order Line.

 

$M in Application Annual Revenue: is defined as one million U.S. dollars excluding taxes processed through the licensed program. For Oracle Self-Service E-Billing products, the Annual
Revenue is equivalent to the total invoiced amount for all company accounts that have at least one enrolled user per billing period.

 

1,000 Claims: is defined as one thousand unique claims processed through the program during a 12 month period. A unique claim is defined as one of the following: OEM Claims entry, supplier
claims entry, adjudication. Claims flow through to OPA for automated processing. You may not exceed the licensed number of transactions during a 12 month period unless you acquire
additional transaction licenses from Oracle

 

Customer Record: is defined as each unique Customer Record (including contact records, prospect records and records in external data sources) that you may access using the program

 

Electronic Order Line: is defined as the total number of distinct electronic order lines entered electronically into the Oracle Order Management application from any source (not manually entered
by licensed Order Management Users, Professional Users 2003, or Professional Users 2003 External) during a 12 month period. This includes order lines originating as external EDI/XML
transactions and/or sourced from other Oracle and non-Oracle applications. You may not exceed the licensed number of order lines during any 12 month period

 

Employee: Enterprise Employee: is defined as (i) all of your full-time, part-time, temporary employees, and (ii) all of your agents, contractors and consultants who have access to, use, or are
tracked by the Oracle Programs. The quantity of the licenses required is determined by the number of Enterprise Employees and not the actual number of users. In addition, if you elect to
outsource any business function(s) to another company, all of the company’s full-time, part-time, temporary employees and agents, contractors and consultants that are providing the outsourcing
services for you who have access to, use, or are tracked by the Oracle Programs must be counted for the purposes of determining the number of Enterprise Employees.

 

Named User Plus / Named User is defined as an individual authorized by you to use the programs which are installed on a single server or multiple servers, regardless of whether the individual is
actively using the programs at any given time. All of the remaining provisions of this definition apply only with respect to Named User Plus licenses, and not to Named User licenses. A non human
operated device will be counted as a named user plus in addition to all individuals authorized to use the programs, if such devices can access the programs. If multiplexing hardware or software
(e.g., a TP monitor or a web server product) is used, this number must be measured at the multiplexing front end. Automated batching of data from computer to computer is permitted. You are
responsible for ensuring that the named user plus per processor minimums are maintained for the programs contained in the user minimum table in the licensing rules section; the minimums table
provides for the minimum number of named users plus required and all actual users must be licensed.

 

Partner Organization: is defined as an external third party business entity that provides value-added services in marketing and selling your products. Depending upon the type of industry, partner
organizations play different roles and are recognized by different names such as reseller, distributor, agent, dealer or broker.

 

Registered User: is defined as an individual authorized by you to use the programs which are installed on a single server or multiple servers, regardless of whether the individual is actively using
the programs at any given time. Registered Users shall be only your business partners and/or customers and shall not be your employees

 

 

 

Siebel licensing – Most common Oracle compliance challenges

 

 

Not end-dating users

 

Application User – This is a license model where you license every individual who are authorized to use Siebel. When we review Siebel using the same methodology and toolset as Oracle LMS. We identify that the client has more users accessing Siebel Modules, than they have licenses for. In most cases this is due to not end dating users who no longer require access to Siebel.

 

Mistakenly assigning responsibilities

 

As Siebel standard installation provides Oracle customers with all Siebel modules unlocked, no serial keys or pre-purchase is required. It is very easy for a Siebel administrator to assign responsibilities that will provide the end user with views – Siebel modules that they are not using or require. However, if Oracle would conduct an Oracle License audit they would require the user to be licensed.

 

Custom views

 

If your company develops and use custom views in Siebel. You may unwittingly be using Siebel products and modules that you do not have a license for. You need to map each view to each specific Siebel product.

 

Read more on our blog

 

Oracle license compliance scripts
Oracle License Audit & Ultimate Guide

 

If you would like to be updated on Oracle licensing and recieve more tips follow us on
social media:

✔️ Follow us on LinkedIn
✔️ Subscribe to our channel on YouTube

 

Are you an Oracle Siebel customer and want help to do an Oracle license review?  We are able to use Oracle license compliance / Oracle LMS scripts to audit your environment. We have over 10+ years of Oracle Siebel licensing expertise and we did audit customers on behalf of Oracle for Siebel.  Contact us today to find out how we can help your company with Siebel license models and compliance.