Siebel License Position Analysis

A clear view of your
Siebel License Position

Over 8,300 organisations run Oracle Siebel. Most have no independent view of their license position. The skills have thinned out. The SAM tools don't cover it. Oracle's audit teams do.

Lime² Siebel Licensing connects to a Siebel database, reads the responsibility data, and produces an Effective License Position — module by module, user by user. On-premise. No external connections. No agents on Siebel servers.

Get in touch How It Works
Lime² Siebel Licensing — ELP
248
Licensed
217
In Use
31
Variance
87%
Utilisation
CodeProductLicUsedVarRAG
CSSSiebel Call Center 8084-4
Red
SFASiebel Sales Enterprise 6056+4
Amber
FSSiebel Field Service 4031+9
Green
MKTSiebel Campaigns 3022+8
Green
OMSiebel Order Management 3824+14
Green
8,300+
organisations currently running Siebel
2036
Oracle Premier Support extended to
100+
responsibility mappings built in
20+
Siebel license reviews informing this tool
The Problem

Siebel licensing expertise has quietly disappeared

The practitioners who understood Siebel have moved on. SAM tools don't cover it. The consultancies that used to do it have dropped it from their catalogues. What remains is Oracle's own audit team — and the data they collect from LMS scripts.

Most Siebel customers renew without question. Changing it feels too risky, and nobody around them knows enough to push back.

Siebel does not enforce license boundaries technically. Every module is accessible by default. Administrators enable things for testing and they stay enabled. Oracle identifies this during audit by comparing enabled modules against ordering documents. The gap between what's licensed and what's enabled is often significant — and entirely invisible without looking at the data.

The Approach

Built from real Siebel license reviews, not textbook licensing theory

Twenty-plus Siebel license reviews over ten years produce patterns. The responsibility-to-product mapping is where the complexity lives — most estates have responsibilities that don't match standard naming conventions, built up over years of local customisation, industry configuration, and implementation decisions nobody documented.

The tool ships with over 100 built-in mappings covering every standard Siebel CRM responsibility. Unmapped responsibilities are worked through directly — the resulting mappings go into the shared library and improve coverage for every subsequent deployment.

No data leaves the customer environment. The tool installs on any Windows machine with database access. Nothing is written back to Siebel. No agents, no cloud connection, no reporting back.

Lime² Siebel Licensing

Responsibility data mapped to entitlements

Connects to SQL Server or Oracle databases hosting Siebel tables. Reads four tables — S_USER, S_PER_RESP, S_RESP, S_APP_VIEW_RESP. Maps responsibilities to Oracle license products. Produces an ELP with RAG status per module. Exports to CSV for audit response or internal review.

✓
Direct database collection SQL Server and Oracle. Read-only. No changes to the Siebel environment.
✓
CSV import For environments where direct database access isn't available. Run the bundled SQL against Siebel, export the result, import it here.
✓
User drill-down per module Every user mapped to a license product, with last login date and responsibility assignment visible.
✓
On-premise Installs on any Windows machine with network access to the Siebel database. No external connections.
Data Collection — SQL Server
Connection
Server: SQLSRV01
Database: SIEBEL
▶ Collect Now
Collection History
DateSourceRecordsStatus
Today 09:14SQL Server2,847 OK
Mon 08:30CSV Import2,791 OK
See It Working

Three recordings. No narration.

The tool with real Siebel data. Each clip is under 90 seconds.

ELP loading from a live database collection
Dashboard

ELP loading from a live database collection

KPI cards, RAG status, utilisation chart — populated from a real Siebel environment.

Effective License Position — module by module
ELP

Effective License Position — module by module

Select a product row, see every user — login name, last access date, responsibility assignment.

Import from a query export
CSV Import

Import from a query export

For environments where direct database access isn't available. Run the bundled SQL, import the CSV.

Siebel Licensing

Where the compliance risk actually hides

All articles →
Metrics2025

Custom Application Suite bundles — convenient pricing, opaque scope

Oracle's bundled SKUs price several modules under one blended per-user metric. That's simpler to buy, but it obscures exactly which modules are covered and at what quantity — and bundle terms vary enough between contracts that assuming yours matches a colleague's is a common mistake.

Metrics2025

The stack under Siebel has its own licensing, and its own metrics

Siebel's Named User licensing doesn't cover what it runs on. WebLogic, the underlying database, and any Oracle Analytics layered on top are typically licensed by Processor, not by user, with core-factor calculations that have nothing to do with your Siebel head count. A clean Siebel position can still leave an audit finding sitting underneath it.

Licensing2025

Legacy concurrent user contracts — worth reviewing before renewal

Contracts predating Oracle's 2006 acquisition carry ambiguity around Named User Plus conversion that is better resolved before Oracle raises it. These conversations go differently when initiated from a position of knowledge.

GuidanceEvergreen

Inactive accounts — the simplest thing to address

Under Named User licensing, every account authorised to access Siebel counts regardless of last login. Former employees still active in Siebel are a common finding in every review.

Licensing2025

Module drift — the most common finding nobody talks about

Siebel administrators enable modules during testing. Those modules stay enabled. Oracle checks enabled modules against ordering documents during audit. The gap between the two is a finding independent of how many users are assigned to it.

Migration2025

Siebel to Oracle CX Cloud — the licensing conversation nobody is having

Siebel perpetual licences carry no automatic trade-in value against CX Cloud subscriptions. Running both in parallel during migration creates a dual-licensing cost that is consistently underestimated. The negotiation goes better with a documented Siebel position in hand.

Platform2025

Siebel on OCI — containerised deployments now in production

Oracle has demonstrated large-scale Siebel deployments on OCI with Kubernetes. For organisations considering OCI migration, BYOL processor metric calculations under Oracle's cloud policy need careful assessment before any commercial discussion.

GuidanceEvergreen

External users — a separate licensing question most reviews miss

Customers and partners accessing Siebel via portals require external metrics — Registered User, not Application User. The distinction matters and is frequently overlooked in estates that have grown portal usage organically over the years.

Contact

Talk to the team behind the tool

Questions about the tool, your Siebel estate or responsibility mapping? Email us and the response comes directly from the development team, not a sales queue.

Email info@lime-software.com
FAQ

Questions worth answering upfront

Is this tool affiliated with Oracle?
No. SBL-License is built and maintained independently by Lime Software Ltd. It is not affiliated with, endorsed by, or built in partnership with Oracle Corporation. Oracle and Siebel are registered trademarks of Oracle Corporation.
What does SBL-License actually produce?
A full Effective License Position (ELP) — the same output an Oracle audit would produce, but run by you, ahead of time. It covers all modules and all users, with per-module and per-user drill-down, built from direct SQL Server or Oracle collection, or a CSV import if you'd rather not connect directly.
Do I need to install anything in my Siebel environment?
No Oracle client install is required. Data comes in either via direct SQL Server/Oracle collection or a CSV export from your environment, whichever your team is more comfortable with.
What is "responsibility mapping" and why does it matter?
Every Siebel estate accumulates responsibilities that don't match standard naming — custom implementations, industry configurations, years of local convention. Unmapped responsibilities can't be correctly assessed against your entitlements. Mapping them to the correct Oracle license products is what turns raw user data into an accurate compliance position.
Is Lime Software a credible source on Oracle licensing?
Lime Software Ltd is a GLAS Verified Oracle licensing consultancy, independent since 2003, with over 100 client engagements across Siebel, EBS, Database, Java and Middleware. No Oracle reseller relationship and no audit referrals — the assessment is built to work for you, not for Oracle.
How do I get started?
Email info@lime-software.com to get started or ask a question first. Response is direct from the development team, not a sales queue.
About

Lime Software Ltd is an Oracle licensing consultancy based in Norwich, UK. Over 100 client engagements across Siebel, EBS, Database, Java and Middleware over more than 20 years — independent, with no Oracle reseller relationship and no audit referrals.

The Siebel tool was built after working through real customer data and noticing that the skills and tooling to support Siebel license reviews had largely disappeared from the market. Twenty-plus reviews over ten years informed what went into it.

✓ GLAS Verified Oracle Licensing Consultancy
Contact
—info@lime-software.com
—limesquared.com
—Norwich, UK
—UK: +44 161 920 6096
—USA Toll Free: +1 (800) 902-8115
—Independent Oracle licensing consultancy since 2003