Oracle licensing assessment. Six million dollars saved at the ULA certification framework.

A national oil and gas operator in the United Arab Emirates engaged the Oracle practice in the middle of an Oracle Unlimited License Agreement certification cycle. The publisher's opening position anchored certification against an aggressive view of the customer's Oracle deployment trajectory across the upstream, midstream, and downstream operations.

The buyer side response anchored certification against the customer's actual Oracle deployment, the actual database estate, the actual technology footprint, and the live support contracts. The net effect was that the ULA certification matched what the customer was really running, not the publisher's opening position.

Total saving was six million dollars across a fourteen week engagement. Read the related Oracle services practice, the Oracle knowledge hub, and the Oracle ULA certification service.

The engagement covered five commercial dimensions across the customer's Oracle estate.

1. ULA certification. Anchored the certification number against actual ULA deployment counts.
2. Database estate. Tied the database scope to actual installs across upstream, midstream, and downstream operations.
3. Technology stack. Tied WebLogic, Identity Management, and Forms and Reports counts to actual corporate use.
4. Support contracts. Anchored Premier Support against the actual supported population across the support cycle.
5. Commercial position. Held the commercial discussion to the customer's real estate rather than the publisher's opening position.

The five dimensions compounded. ULA certification became the load bearing Oracle licensing conversation across the certification cycle.

Customer profile

The customer is a national oil and gas operator in the United Arab Emirates running a substantial Oracle estate across upstream, midstream, and downstream operations.

• Database tier. Oracle Database Enterprise Edition with Real Application Clusters, Partitioning, Advanced Compression, Active Data Guard, Diagnostics Pack, Tuning Pack, and Database In Memory across the upstream production estate.
• Technology tier. Oracle WebLogic Server, Oracle Identity Management, Oracle Forms and Reports, and Oracle E Business Suite across the corporate estate.
• Support tier. Oracle Premier Support across the broader Oracle estate.

The customer entered the engagement fourteen months into an Oracle Unlimited License Agreement covering the principal database tier, the technology tier, and a subset of Oracle E Business Suite. The ULA contractual end date was eighteen months away at engagement scoping, with the publisher's certification process already in flight against the broader Oracle estate.

Procurement, finance, IT operations, and legal were already engaged. The publisher's preferred certification approach anchored the conversation to a broad reading of the customer's Oracle deployment. Read the broader Oracle ULA framework, the Oracle ULA case study, and the Oracle database licensing optimization framework.

The exposure

The exposure sat on the certification dimension of the customer's ULA. The publisher's preferred certification anchored against an aggressive reading of the customer's deployment across upstream, midstream, and downstream operations, rather than against the actual estate.

That preferred reading covered four principal exposure populations.

1. Oracle Database Enterprise Edition. A broad reading of the customer's database installs.
2. Database options. A broad reading of the Real Application Clusters, Partitioning, Advanced Compression, Active Data Guard, Diagnostics Pack, Tuning Pack, and Database In Memory populations.
3. Technology stack. A broad reading of the WebLogic, Identity Management, and Forms and Reports populations.
4. Premier Support. A broad reading of the supported population across the support cycle.

Read the broader Oracle license management services and the Oracle audit services.

The actual deployment

Actual deployment was anchored against installed and used Oracle, not the publisher's opening position. The work segmented the estate across four populations.

1. Upstream production. Actual database installs across the upstream production estate.
2. Midstream. Actual database installs across the midstream estate.
3. Downstream. Actual database installs across the downstream estate.
4. Corporate. Actual technology stack installs across the corporate estate.

The cumulative effect of the four populations was a deployment view rooted in what the customer actually ran.

That view reframed the ULA conversation. It anchored the actual Database Enterprise Edition footprint, the actual option footprint across Real Application Clusters, Partitioning, Advanced Compression, Active Data Guard, Diagnostics Pack, Tuning Pack, and Database In Memory, the actual technology stack footprint, and the actual support footprint. Read the broader Oracle cost optimization playbook and the Oracle CIO playbook.

The certification

The certification work anchored the customer's ULA against actual deployment. It segmented across four certification populations.

1. Scope. What products and options the certification number covered.
2. Quantity. The certified counts mapped to actual deployment.
3. Environment. The covered environments across upstream, midstream, downstream, and corporate operations.
4. Timing. The certified counts as of the contractual certification date.

The cumulative effect was a certification number that matched the customer's actual ULA deployment rather than the publisher's broader opening position.

The certification work reframed scope, quantity, environment, and timing across the certification cycle. The certified number matched what the customer was actually running. Read the broader Oracle ULA certification service and the Oracle license audit defense playbook.

The support position

Support was anchored against the actual supported estate. The work segmented across four populations.

1. Oracle Premier Support. The actual Premier Support footprint.
2. Support renewal. The renewal sequence across the renewal cycle.
3. Support reduction. Shelfware and unused options removed from the support base.
4. Third party support. Selective third party support across the broader Oracle estate.

The cumulative effect was a support position grounded in the customer's actual estate rather than the publisher's broader opening position. Read the broader Oracle third party support landing and the Oracle third party support transition service.

The buyer side moves

The buyer side response was eleven moves that compounded across the engagement.

1. Anchor ULA certification against actual deployment rather than the publisher's opening position.
2. Anchor the database estate against actual installs across upstream, midstream, and downstream operations.
3. Anchor the technology stack against actual corporate use.
4. Anchor support against the actual supported population across the support cycle.
5. Run the certification across the four certification populations so the certified number matched actual ULA deployment.
6. Run the deployment view across the four deployment populations so the view matched the actual estate.
7. Run the support position across the four support populations so it matched the actual supported estate.
8. Negotiate the certification against the publisher's broader opening position.
9. Negotiate the database scope against the publisher's broader opening position.
10. Negotiate support against the publisher's broader opening position.
11. Run the broader commercial discussion alongside ULA certification across the certification cycle.

The full sequence is set out in the Oracle ULA framework, the Oracle CIO playbook guide, and the broader Oracle managed service.

The outcome

The engagement delivered $6M in savings across certification, the database estate, the technology stack, and support.

The ULA was certified at the customer's actual deployment rather than the publisher's opening position. The certified number reflected the actual Database Enterprise Edition footprint, the actual option footprint, and the actual technology stack.

Support was renegotiated against the actual supported estate, with shelfware removed from the support base. The broader commercial discussion was held to the customer's real estate rather than the publisher's opening position across the commercial cycle. Read the related Broadcom Oracle UK media case study, the Oracle ULA Asian telecom case study, and the Aegean Airlines Java advisory case study.

How we engage

• Oracle ULA certification scoping. Six week engagement that scopes the ULA certification, anchors actual deployment, and identifies the immediate commercial moves at the next certification cycle. Oracle ULA certification service.
• Oracle ULA certification negotiation. Certification negotiation engagement covering certification, the database estate, the technology stack, and the broader support conversation across the certification cycle. Oracle contract negotiation service.
• Oracle audit defense. Audit defense engagement covering audit response, compliance posture, and the broader audit cycle. Oracle audit services.
• Vendor Shield. Always on multi vendor management posture covering Oracle alongside the broader enterprise software estate. Vendor Shield.
• Run the calculator. The Oracle Java license calculator sizes Java against actual deployment, alongside the broader software spend assessment.