Oracle ULA Asian Telecom. The ULA certification case study.

A leading Asian telecommunications group engaged Redress Compliance for its Oracle ULA certification at the end of a three year term. The customer operates across multiple Asian markets at the upper end of the telecommunications customer scale. Its Oracle estate ran substantial deployments of Oracle Database, Oracle WebLogic Server, Oracle SOA Suite, and a wider Oracle middleware footprint across the customer's data centers.

The customer had entered the ULA on the back of a sharply rising Oracle deployment trajectory, anchored to the principal Database and middleware products across the three year term. Read the related Oracle advisory practice, the Oracle ULA pillar, the Oracle ULA landing, the Oracle ULA certification service, and the Oracle CIO playbook.

Engagement snapshot

The ULA

An Oracle Unlimited License Agreement is the headline commercial vehicle Oracle uses with its largest customers. The publisher writes the contract against the customer's expanding Oracle footprint over a three year term and prices it against an aggressive deployment trajectory. The agreement runs alongside the rest of the Oracle estate, including standalone Database licenses, middleware entitlements, and any prior contractual positions.

The customer's ULA bundled the principal Database and middleware products into a single unlimited deployment right. The contract covered:

• Oracle Database Enterprise Edition
• Oracle Real Application Clusters (RAC)
• Oracle Partitioning
• Oracle Advanced Compression
• Oracle Diagnostics Pack
• Oracle Tuning Pack
• Oracle WebLogic Server Enterprise Edition
• Oracle SOA Suite
• Wider Oracle middleware components

The objective at certification was straightforward. Convert the unlimited rights into a perpetual license count that reflects the customer's actual deployment, not the publisher's opening position. Read the broader CIO playbook for Oracle Database licensing and options for the deeper Oracle Database licensing context.

ULA certification

ULA certification is the commercial event at the end of the three year term. Oracle approaches certification with a clear preference. Push the customer's declared deployment as high as possible so the perpetual count fixed at certification carries forward as a large, recurring support base.

The certification cycle breaks into three phases:

1. Pre certification. The twelve month window before the ULA end date. This is where deployment data is gathered, license positions are reconciled, and the buyer side prepares for declaration.
2. Certification. The window in which the customer issues the formal certification declaration, negotiates the deployment count, and closes out the unlimited term.
3. Post certification. The period after the ULA closes, covering ongoing support, future Oracle licensing requirements, and any renewal cycle considerations.

Deployment data

Deployment data is the second pillar of certification. It anchors the declared count against what the customer actually runs, not against Oracle's preferred broad estimate. The customer's deployment data covered Oracle Database installations across the data centers, WebLogic Server installations across the middleware tier, and the wider Oracle middleware footprint.

The data was segmented by product:

• Oracle Database deployments
• Oracle WebLogic Server deployments
• Oracle SOA Suite deployments
• Wider Oracle middleware deployments

The buyer side discipline was to base the deployment data on what was actually installed and running, rather than on the publisher's opening position. Read the related Oracle license management services for the broader deployment data practice.

License position

The license position is the third pillar of certification. It captures what the customer is entitled to before, during, and after the ULA. The customer's position covered Oracle Database licenses, WebLogic Server licenses, SOA Suite licenses, and the wider Oracle entitlement set across the estate.

The license position itself segments into three layers:

• Pre ULA licenses. The entitlements held before the ULA was signed.
• ULA term entitlements. The unlimited deployment rights during the three year term.
• Post ULA licenses. The perpetual count fixed at certification.

The buyer side discipline was to anchor the license position against the customer's actual entitlement and the actual deployment. The position then feeds directly into the certification declaration. Read the broader Oracle license management services for the license position work.

The negotiation moves

The buyer side negotiation followed eleven moves that compounded across the certification cycle.

1. Anchor the certification. Anchor the certification declaration against the customer's actual deployment, actual license position, and actual integration, not against the publisher's opening position.
2. Build the deployment data. Run a full deployment inventory across the Oracle estate so the declared count matches what is installed.
3. Reconcile the license position. Reconcile entitlements across the pre ULA, term, and post ULA layers so the position is defensible.
4. Phase the certification. Run pre certification, certification, and post certification as separate phases with clear deliverables.
5. Negotiate the declaration. Counter the publisher's opening position with a declaration grounded in the actual deployment data.
6. Negotiate the post ULA position. Settle the perpetual count and the post ULA licensing terms in line with the actual Oracle estate.
7. Negotiate post ULA support. Push back on the publisher's opening support base and anchor support against the agreed perpetual count.
8. Negotiate the renewal cycle. Hold post ULA renewal terms against the customer's actual renewal needs rather than the publisher's opening position.
9. Sequence with the wider Oracle renewal cycle. Run the certification alongside the wider Oracle renewal cycle so commercial leverage compounds.
10. Bring in Vendor Shield. Engage Vendor Shield advisory across the wider Oracle estate so the certification does not stand alone.
11. Track audit exposure. Monitor Oracle audit exposure across the estate so the certification does not trigger a follow on audit.

The outcome

The engagement delivered a material commercial outcome at certification. The deployment data anchored the certified count against the customer's actual deployment, not against the publisher's opening position. The license position anchored the entitlement reconciliation against the customer's actual Oracle estate.

The certification declaration matched the customer's actual deployment. The post ULA position, including the perpetual count, the ongoing support base, and the renewal cycle terms, was settled against the actual Oracle estate. The cumulative effect was a material commercial outcome at certification that reflected what the customer actually ran, not what the publisher preferred to fix at certification.

Lessons learned

The principal lesson is that Oracle ULA certification is a commercial event, not an operational one. The buyer side anchors the certification against the customer's actual deployment, integration, and license position, not against the publisher's opening position. The full approach is set out in our Oracle ULA pillar, the Oracle ULA landing, the Oracle ULA certification service, and the Oracle CIO playbook.

For related reading see the Oracle license management services, the Oracle cost optimization playbook, the Oracle audit defense service, the Oracle audit response playbook, the CIO playbook for Oracle Database licensing and options, and the CIO playbook for Oracle Exadata and engineered systems licensing. The Oracle third party support landing page and the Oracle advisory practice cover the wider Oracle renewal cycle.

• Anchor certification against the actual deployment. ULA certification is a commercial event. The buyer side anchors the declaration against the customer's actual deployment rather than the publisher's opening position.
• Run deployment data continuously. Deployment data should run continuously across the ULA term, not only at the certification window. The buyer side keeps the inventory current so the declaration is defensible.
• Negotiate the post ULA position commercially. The post ULA position, including the perpetual count, support base, and renewal cycle terms, is a commercial negotiation grounded in the actual Oracle estate.
• Bring in Vendor Shield. Vendor Shield advisory runs across the wider Oracle estate and anchors the position against what the customer actually runs. Vendor Shield.
• Run the calculator. The Oracle Java license calculator sizes the Oracle exposure against the customer's actual deployment.