Oracle Analytics Cloud Licensing:
Professional vs Enterprise Tiers, What Fusion Already Includes, and How OCPU Pricing Works

Oracle Analytics Cloud: The Analytics Layer With a Hidden Cost Architecture

Oracle Analytics Cloud (OAC) is Oracle's cloud-native analytics and business intelligence platform, built to replace Oracle Business Intelligence Enterprise Edition (OBIEE) on-premises. OAC runs on Oracle Cloud Infrastructure and is licensed in OCPUs — the same consumption unit as Autonomous Database and other OCI services. This creates a pricing model that is fundamentally different from Oracle's on-premises BI licensing (which used processor or named user metrics like other Oracle software) and interacts with OCI Universal Credits in ways that IT finance teams frequently miss until the first renewal. The hidden complexity that catches most organisations is the relationship between OAC's OCPU pricing, the analytics capability embedded within Oracle Fusion Cloud (which is included in the Fusion subscription), and the additional OAC instances required for custom analytics workloads that exceed what Fusion's embedded reporting provides. For Oracle Fusion ERP pricing context, see our Oracle Fusion Cloud ERP Pricing Guide. For OCI pricing in which OAC consumption sits, see our OCI Pricing and Universal Credits Guide. For OAC licensing review, our Oracle advisory team assesses analytics licensing positions and OCI cost management.

OAC Professional vs Enterprise: The Tier Difference

Oracle Analytics Cloud is offered in two tiers with distinct OCPU pricing and capability sets:

The OCPU price difference between Professional ($0.625/hr) and Enterprise ($2.1026/hr) is 3.4×. For a 4-OCPU OAC instance running 720 hours/month: Professional costs $1,800/month ($21,600/year); Enterprise costs $6,055/month ($72,660/year). The Essbase inclusion in Enterprise is the primary technical differentiator for organisations with existing Oracle Essbase (Hyperion) workloads. For organisations without Essbase requirements, Professional typically provides equivalent analytics capabilities at 30% of Enterprise's OCPU cost.

What Fusion Cloud's Embedded Analytics Includes — and Where OAC Is Needed

Oracle Fusion Cloud (ERP, HCM, SCM) includes embedded analytics capabilities as part of the subscription. Understanding what is included vs what requires a separate OAC instance is the most important OAC cost control question for Fusion customers:

Included in Fusion subscription: Pre-built subject areas for Fusion modules (Financials, Procurement, HR, Supply Chain), standard reports and dashboards using Oracle Analytics Publisher, KPI and metric tiles on Fusion home pages, standard Oracle Transactional Business Intelligence (OTBI) reports, and Oracle Digital Assistant analytics interactions.

Requires separate OAC instance: Custom analytics dashboards beyond OTBI's subject area scope, data blending that combines Fusion data with external data sources (Salesforce, SAP, flat files, data warehouse), Essbase financial planning models, custom ML models applied to Fusion data, high-volume analytics workloads that exceed Fusion's embedded reporting performance limits, and any analytics requirement that needs a dedicated semantic model (RPD) built outside Fusion's pre-built subject areas.

OBIEE to OAC Migration: What Changes and What the Transition Costs

Organisations running Oracle Business Intelligence Enterprise Edition (OBIEE) on-premises face the same migration decision as EBS customers: Oracle is pushing cloud migration, and OBIEE's long-term on-premises roadmap is limited. The OAC migration from OBIEE involves:

RPD (semantic model) migration. OBIEE's Repository (.rpd) semantic model can be imported into OAC Enterprise with Oracle's migration tool. The tool handles most metadata migration but requires manual remediation for OBIEE features that OAC implements differently — typically 20–40% of the semantic model requires manual rework for complex OBIEE implementations.

Dashboard and report migration. OBIEE Classic dashboards and Answers reports migrate to OAC. The fidelity of the migration depends on the complexity of the original content — simple reports migrate cleanly; complex conditional formatting, drill paths, and custom visualisations often require redesign.

Infrastructure transition. OBIEE runs on customer-managed servers; OAC runs on OCI with Oracle managing the infrastructure. The OCPU sizing for OAC should reflect actual OBIEE usage patterns — many OBIEE implementations were significantly over-provisioned on hardware, and right-sizing for OAC OCPU consumption can produce cost savings vs the OBIEE infrastructure cost.

OAC Pricing Within OCI Universal Credits

OAC OCPU consumption counts against OCI Universal Credits. For organisations with an existing OCI Universal Credits commitment, OAC Professional and Enterprise OCPU charges are discounted at the same rate as the overall UC discount — a 40% UC discount applies to OAC consumption as it does to compute and ADB. This makes OAC pricing bundled into a UC deal significantly more attractive than OAC at PAYG rates. The negotiation implication: if OAC adoption is planned alongside Fusion ERP and OCI infrastructure, including OAC consumption in the Universal Credits sizing (larger UC commit = deeper discount rate on all OCI including OAC) produces better OAC pricing than a standalone OAC purchase. For OAC licensing strategy within an OCI deal, our Oracle advisory team models the UC sizing that optimises OAC cost alongside Fusion subscription and OCI infrastructure. Contact us for an Oracle analytics licensing review.