Oracle Communications Licensing: BRM and Telco Advisory

Oracle Communications BRM: What It Is and Why Licensing Is Complex

Oracle Communications Billing and Revenue Management (BRM) is an end-to-end revenue management platform used by telecommunications operators, internet service providers, and digital service companies to manage real-time charging, billing, rating, customer care, and revenue assurance. It is the revenue engine for many of the world's largest CSPs (Communications Service Providers), processing hundreds of millions of subscriber billing events daily.

BRM licensing is complex for three reasons. First, Oracle does not publish standard BRM pricing — all costs are negotiated based on your specific deployment size, subscriber base, and the number of service types managed by the platform. Second, BRM interoperates with multiple Oracle database and infrastructure licences, meaning your effective Oracle licence position for BRM encompasses multiple product families. Third, subscriber volumes and service portfolios change over time, creating ongoing true-up risk as your actual deployed metrics drift from the contracted levels.

The global communications software market reached $15.1 billion in 2024 — a 10.4% year-over-year increase — and Oracle BRM remains the market-leading platform in its category. This entrenched position gives Oracle significant pricing leverage at renewal, which is precisely why independent advisory support matters for telcos approaching BRM contract renewals.

Oracle BRM Platform Architecture and Licensing Scope

Oracle Communications BRM is not a single product but a platform comprising several integrated components, each of which may have its own licence obligations depending on your contract structure:

• BRM Core: The foundational billing, rating, and account management engine — the primary licenced component
• Elastic Charging Engine (ECE): Real-time charging and policy management for 5G, IoT, and high-volume digital services
• Pricing Design Center (PDC): Configuration tool for building and managing tariff plans, bundles, and promotional offers
• Billing Care: Customer-facing billing portal and care agent interface
• Business Operations Center (BOC): Operational analytics and reporting layer for BRM deployments

Some of these components are included in the core BRM licence; others are separately licenced modules. The exact scope of what is included in your contract versus what requires additional licence purchase depends on the specific OCS (Oracle Cloud Services) agreement, CSI entitlements, or perpetual licence structure your organisation holds.

Additionally, BRM requires Oracle Database — typically Oracle Database Enterprise Edition with several options — and the licence obligations for those database components must be managed in conjunction with BRM. An incomplete view of the BRM plus database licence position is a common source of compliance shortfalls.

BRM Licensing Metrics: How Oracle Charges

Oracle Communications BRM is typically licenced using one or more of these primary metrics:

Subscriber-Based Licensing

Many BRM contracts are structured around the number of billable subscribers managed by the platform — the total population of customer accounts actively rated and billed through BRM. As subscriber numbers grow, true-up obligations can be triggered if the contracted subscriber ceiling is exceeded.

The subscriber metric is straightforward in concept but complex in execution: what counts as a "subscriber" depends on the contract definition, and organisations with complex multi-service subscriber structures (e.g., a single customer with multiple SIMs, broadband, and IoT devices) may find that Oracle interprets subscriber count differently than expected.

Service-Based or Module-Based Licensing

Some BRM agreements charge based on the number and type of managed services — the distinct service categories being rated and billed through the platform. Adding a new service type (e.g., 5G slice billing or new IoT service tier) without updating the licence can create a compliance exposure.

Processor-Based Licensing

For on-premise BRM deployments, Oracle may apply a processor licence metric to the BRM software stack — subject to the same core factor rules that apply across Oracle's on-premise portfolio (0.5 for Intel/AMD x86). In virtualised environments, Oracle's soft partitioning rules require counting physical cores on the host rather than virtual CPUs allocated to BRM VMs.

Oracle ASAP: Automated Service Activation Platform Licensing

Oracle Communications ASAP (Automated Service Activation Platform) is frequently deployed alongside BRM as the provisioning and service activation layer. ASAP orchestrates the fulfilment of service orders across legacy and cloud-native network elements — from activating a mobile SIM to provisioning 5G network slices.

ASAP is licensed separately from BRM and commonly uses one of three metrics: annual orders processed, number of lines or services activated per year, or subscriber base. The appropriate metric depends on your ASAP usage pattern and your negotiating position at the time of the original contract.

A key compliance risk for ASAP deployments is the addition of new activation workflows — for example, when a telco migrates to 5G or adds a new digital service category — without reviewing whether the new activation volume remains within the contracted metric. Each new network element type, service technology, or geographic market brought under ASAP management may have implications for the licence count.

Oracle Communications Support Costs and Annual Escalation

Oracle charges annual support on BRM and ASAP at rates that form a substantial portion of the total Oracle Communications annual cost. For perpetual licence deployments, Oracle Software Update Licence and Support (ULS) is priced at 22% of net licence cost per year. For cloud-based or subscription deployments, support is embedded in the subscription fee.

Critically, Oracle support fees increase by 8% per year. For a telecommunications operator with a BRM and ASAP support bill of $2 million per year, the 8% compounding escalation means that support costs rise to approximately $2.7 million in year four — without any change in the licence position. Over a five-year contract cycle, this escalation adds more than $2.5 million to the total cost of ownership compared to a flat-rate scenario.

Securing a support price cap — limiting annual escalation to a defined percentage below Oracle's standard 8% — is one of the most impactful negotiation objectives for any BRM or ASAP renewal. This concession is achievable in competitive renewal situations and when Oracle has an interest in securing a multi-year commitment.

Compliance Risks in Oracle BRM Deployments

Oracle BRM compliance risk is driven by three primary factors: metric drift, platform expansion, and database licence misalignment.

Metric Drift

Subscriber numbers, service counts, and order volumes all change over time in a live telco environment. Customer acquisitions, mergers, product launches, and network migrations can push actual usage metrics above the contracted levels without any deliberate decision to under-licence. When Oracle reviews the deployment at renewal or audit, metric drift is the most common source of true-up demands — which Oracle will seek to collect at full list price plus back-support.

Platform Expansion Without Licence Review

Adding BRM modules (e.g., bringing ECE online for a 5G network launch, or deploying PDC for a new product tier) without reviewing whether those modules are included in the existing licence creates new compliance exposure. Similarly, deploying BRM in additional data centres or migrating to a new infrastructure platform can expand the licenceable footprint beyond what was originally contracted.

Oracle Database Licence Misalignment

BRM's reliance on Oracle Database Enterprise Edition means that the database licence position must be maintained in parallel with the BRM licence. If Oracle Database options such as Advanced Compression, Diagnostics Pack, or Real Application Clusters are used in the BRM infrastructure without being licenced, the compliance shortfall affects both product families simultaneously.

Negotiation Strategies for Oracle BRM Renewals

Oracle BRM renewals offer genuine opportunities to optimise cost — but only if telcos approach them with independent benchmarking data, clear metrics documentation, and a prepared alternative position. Key strategies include:

• Audit your own metrics before Oracle does: Commission an independent licence review to establish your actual deployed subscriber count, service types, and order volumes before entering negotiations. Knowing where you stand — and where gaps exist — allows you to decide whether to remediate before or during the renewal conversation.
• Benchmark against comparable deals: Oracle's initial BRM renewal proposals routinely exceed market-rate terms by 20% to 40%. Independent benchmarking against comparable telco BRM contracts is the most effective tool for challenging Oracle's commercial position.
• Negotiate support price caps: Request a cap on annual support fee escalation as part of the renewal terms. Over a five-year period, a 2–3% support cap versus Oracle's standard 8% saves millions on large BRM and ASAP contracts.
• Explore OCS consolidation: If your Oracle Communications estate includes BRM, ASAP, Order Management (OSM), and Unified Inventory Management (UIM), consolidating these into a single Oracle Cloud Services agreement can provide pricing efficiencies and simplify the compliance management burden.
• Leverage Oracle's Q4 window: Oracle's fiscal year ends May 31. BRM renewals that close during Oracle's Q4 (March to May) tend to attract the most favourable commercial terms as account teams chase year-end targets.
• Evaluate third-party support: For organisations with stable, mature BRM deployments not requiring Oracle-delivered updates, third-party support providers (such as Rimini Street) offer an alternative to Oracle ULS at substantially lower cost. Raising this option — even without immediate intent to switch — creates commercial pressure that Oracle's renewal team will respond to.

ULA and PULA for Oracle Communications

For large telecommunications operators with broad Oracle Communications footprints spanning BRM, ASAP, OSM, UIM, and associated infrastructure, Oracle's Unlimited Licence Agreement (ULA) or Perpetual Unlimited Licence Agreement (PULA) may provide a cost-effective structure for managing licence growth over a defined term.

Under a ULA covering Oracle Communications products, the organisation pays a fixed fee for unlimited deployment of the covered products during the agreement term (typically three to five years). Support fees are fixed regardless of how many additional BRM instances, ASAP nodes, or database servers are deployed — meaning every additional deployment during the term costs nothing in licence terms. This makes it strategically critical to maximise your Oracle Communications deployment before the ULA certification date, as the certified licence count becomes your perpetual entitlement at the end of the term.

Oracle has no Enterprise Agreement construct. The ULA and PULA are the primary vehicles for broad, multi-product Oracle deployment flexibility. Any organisation considering a ULA for Oracle Communications should obtain independent advisory support to structure the agreement terms and ensure the post-certification perpetual position adequately covers anticipated future deployment growth.

How Redress Compliance Supports Telco Oracle Engagements

Redress Compliance has delivered Oracle Communications licence advisory, BRM renewal negotiation support, and audit defence engagements for telecommunications operators across EMEA, North America, and APAC. Our team includes former Oracle LMS auditors with direct experience of Oracle Communications compliance reviews from both sides of the table.

Our Oracle Communications services for telcos include independent BRM licence position reviews, ASAP and OSM metric analysis, renewal strategy development and active negotiation support, ULA structuring, and audit response advisory if Oracle LMS has already engaged. Contact our Oracle advisory team to discuss your situation.