Practice iv · BI & Analytics
Oracle BI Licensing
Independent buyer side advisory for Hyperion, OBIEE, Essbase, Oracle Analytics Server, and Oracle Analytics Cloud.
Independent buyer side advisory for Hyperion, OBIEE, Essbase, Oracle Analytics Server, and Oracle Analytics Cloud.
Oracle BI and analytics licensing covers Hyperion, OBIEE, Essbase, and Oracle Analytics, each licensed by Named User Plus or Processor with topology that drives the count. Exposure comes from counting every consumer of a report rather than every authorised user, and from Essbase options. A buyer side review fixes the count and the topology.
Oracle's analytics portfolio is a collection of acquisitions stitched into a stack. Hyperion came from one acquisition, Essbase from another, OBIEE from a third, and Oracle Analytics Server and Oracle Analytics Cloud are the current generation that subsumes them. Each layer kept its own metrics, and a position built across the stack over a decade is rarely coherent.
User counting is where it goes wrong. These products are licensed by Named User Plus or by Processor, and the Named User Plus definition counts everyone authorised to access the application. In analytics, that population is enormous. A financial reporting deployment where every manager can open a dashboard can be read as licensing the entire management layer, even though only a handful of analysts build the models. The distinction between an author, a power user, and a consumer is contractual and frequently ignored in the original purchase.
Essbase adds option exposure. The product carries components that bill separately, and a deployment that grew organically can trigger claims for capabilities that were enabled but never central to the design. Topology matters too, because the number of processors and the way the BI server tier is sized drives the processor count directly.
We rebuild the analytics position by separating authors from consumers, validating the topology that sets the processor count, and mapping the Essbase and Hyperion components actually in use. The reporting population is almost always larger than the licensable population, and closing that gap is the work.
Separation of authors, power users, and consumers, with a defended Named User Plus methodology for read only dashboard access.
Validation of the BI server tier sizing and processor counts that drive the metric on Processor licensed deployments.
A map of which analytics components and options are genuinely in use across the Hyperion and Essbase footprint.
Reconciliation of legacy OBIEE, Essbase, and Hyperion entitlements against the current Oracle Analytics generation.
Assessment of Oracle Analytics Cloud subscriptions and the economics of moving on premises analytics to OAC.
Removal of analytics shelfware and rebalancing of the support stream ahead of renewal.
We open the channel with Oracle on your terms, fix the scope of the conversation, lock the calendar, and ensure no measurement data leaves the perimeter without buyer side review.
An independent measurement against the same ruleset Oracle applies, performed earlier and with cleaner data. Every finding is categorised by exposure tier and tied to the contract clause that governs it.
Findings are documented and argued line by line. Concessions are priced. We have sat on Oracle's side of these tables and know which positions hold and which dissolve.
The settlement is converted into forward commercial value rather than backward payment, with renewal protections, audit cure provisions, and portability written into the result.
Analytics engagements scope to the breadth of the stack and the size of the reporting population. A focused Named User Plus reconciliation fits a fixed fee. A full Hyperion, OBIEE, and Essbase consolidation suits a retainer. Where a claim is live, a gain share arrangement aligns the fee with the reduction secured.
The right structure depends on the engagement. Read our engagement model overview to see when a fixed fee, a retainer, or a gain share arrangement fits, then request a consultation to scope your estate.
Hyperion products are licensed by Named User Plus or by Processor depending on the module. Named User Plus counts everyone authorised to access the application, which in financial reporting can be a large population. The author versus consumer distinction determines whether that population is truly licensable.
Under Oracle's Named User Plus definition, authorised access counts, not active use. A deployment where every manager can open a dashboard can be read as licensing all of them. A defended methodology that separates authors and power users from read only consumers is what controls the count.
Oracle Business Intelligence Enterprise Edition is licensed by Named User Plus or Processor. On Processor deployments the BI server tier topology drives the count, so sizing built for peak load can inflate the licence requirement well beyond production need.
Oracle Analytics Cloud is the subscription generation of the analytics stack. It is priced by user or by capacity rather than by perpetual Named User Plus. Modelling the move from on premises Hyperion or OBIEE to OAC is a common part of a renewal decision.
Essbase carries components and options that bill separately. A deployment that grew organically can enable capabilities that were never central to the design but are billable when measured. Mapping used components against entitlement is the way to control it.
Often yes. OBIEE, Essbase, and Hyperion entitlements acquired over a decade frequently overlap with the current Oracle Analytics generation. Reconciling them surfaces shelfware and can fund the move to a single supported platform.
Before a renewal, before any platform consolidation, and on audit contact. Analytics populations grow quietly as reporting spreads, so a periodic baseline keeps the licensable count aligned with the contract.
The application estate that feeds analytics, sharing user definitions and audit exposure.
View the practice →The database under every BI deployment, with its own metric and option pack rules.
View the practice →End to end response when a Hyperion, OBIEE, or Essbase finding lands.
View the practice →A buyer side review separates authors from consumers and validates the topology, so the licensable population matches the contract rather than the reach of the reports.