Siebel CRM legacy metrics versus Oracle metrics
The licensing metrics that Oracle today applies for the Siebel products are not totally different from the legacy metrics used by Siebel Systems before the acquisition of the company in 2006. Siebel products were generally sold per user. One of the most common user-based metrics was Named User, which migrated to the Application User metric in use today.
We broadly discuss the most common license management issues in our white paper where you can find how to avoid the most common pitfalls.
Why all this is so important
Due to the large amount of different license metrics on which Siebel software programs can be licensed, it is at all times crucial to check the original contractual Ordering Documents and corresponding License Agreements. Only this way you will be able to understand what specific (legacy) license metric definition is applicable to the Siebel software licenses purchased. Below we provide some illuminating examples of intricacies and complexities you may face.
Both Named User and Application User licenses focus on the number of individuals authorized to use the software, regardless of whether the user is actively using it or not. Here are both the Named User and Application User metric definitions, as listed in Oracle’s current pricelist for Siebel products.
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. Customer may copy, install and use these Siebel Programs for additional Named Users only upon payment of additional Siebel Program license fees.
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.
Another type of user-based license is Registered User. The current Registered User licenses are equivalent to the legacy Registered User licenses: both focus on the number of business partner individuals authorized to use the software. Partner Applications are typically licensed under this metric.
The so called 2-SHIFT or 3-SHIFT User licenses sold by Siebel in the past, were a powerful license metric for organizations working in different shifts. For example, a company with 300 call center employees working in 3 shifts of 100 distinct individuals would require 100 3-SHIFT user licenses; under the current terms and conditions of Oracle this would require 300 Application User licenses.
For other, non user based licenses such as Processor, Physical Server, Computer etc., usage counts are based upon the (physical) hardware on which the Siebel software programs are deployed.
Computer licenses are very similar to the legacy Physical Server licenses; both focus on the number of servers where the software is installed. Licenses on the Physical Server metric often come with limitations such as number of CPUs on the machine or number of records stored in the database installed. End users need to make sure that these extra limitations in the terms of their agreement are being respected, since any breach of these restrictions would require purchasing additional licenses.
Some metrics only became available for Siebel Products after Oracle’s acquisition, such as Custom Suite User, Enterprise, and metrics that are not available anymore like Concurrent Users.
The ways in which original Siebel metrics differ from Oracle metrics may rule your licensing agreement if you are a long-standing customer of the CRM software. Many organizations were using Siebel before Oracle’s acquisition of the company. Therefore you must be aware of how the licensing metrics changed since then. Only this way you will be able to determine what exactly you are entitled to and how this affects your financial relationship with Oracle in the context of using Siebel CRM software.
Ana is one of our project managers who helps customers to overcome their SAM challenges. Ana joined the SAM world in 2011 when she started working as a Technical Analyst within Oracle’s License Management Services (LMS) team and currently uses her diverse SAM experience to support customers during the implementation of our SAM Managed Service solution. Ana holds a master’s degree in Accounting, Audit and Information Systems Management from the Academy of Economic Studies of Bucharest.