Oracle ULA product scope negotiation.

The product scope clause of an Oracle Unlimited License Agreement is the single most leveraged clause in the contract. It defines what the unlimited right actually covers. A deployment of a product inside the scope is fully licensed throughout the term and converts to perpetual licences at certification. A deployment of a product outside the scope is a compliance exposure waiting for an LMS audit.

Oracle's preferred opening position on scope is a narrow list of three to five core products. The customer's preferred position is the broadest list defensible against the projected deployment roadmap. The negotiation between those two positions is detailed, technical, and worth millions of dollars of contract value. This article walks through the buyer side mark up we use on every ULA scope clause.

The structure of an Oracle scope list

An Oracle ULA scope list typically reads as a bulleted enumeration of Oracle program names with edition qualifiers and option qualifiers. A representative line might read: Oracle Database Enterprise Edition, including Partitioning, Advanced Security, and Real Application Clusters. The customer's unlimited right covers Database Enterprise Edition deployments that include those specific options. Deployments that include other options, such as Active Data Guard or the In Memory Database option, are outside the scope unless those options are explicitly listed.

The scope list also includes program version qualifiers. The unlimited right covers the version current at the start of the ULA term and all versions released by Oracle during the term. The unlimited right does not always extend to versions released after the term, which is one reason the certification clause matters so much.

Database edition and option scope

Database is the centre of most ULA scope negotiations. Oracle's preferred opening position is Database Enterprise Edition without options. The customer's preferred position is Enterprise Edition with the full set of options the customer expects to deploy.

The options that most customers should fight to include are Partitioning, Real Application Clusters, Real Application Clusters One Node, the Multitenant Option, Active Data Guard, Advanced Security, Advanced Compression, Database Vault, the Diagnostics Pack, the Tuning Pack, the Database Lifecycle Management Pack, and the Real Application Testing pack. Each of these options carries a separate list price ranging from 11,500 dollars per processor to 23,000 dollars per processor. Adding an option to the ULA scope is much cheaper than buying the option separately later. Tuning Pack pricing negotiation covers the standalone Tuning Pack dynamic for customers who are not on a ULA.

The In Memory Database option is a particular flashpoint. Oracle commonly excludes it from default scope on the grounds that it is a newer option with rapidly evolving deployment patterns. Customers who expect to deploy In Memory should specifically request its inclusion. The list price is 23,000 dollars per processor. Excluding it from scope creates the largest single line exposure in most ULA certifications.

Middleware scope

For customers with significant WebLogic, Coherence, or Internet Application Server footprints, the middleware scope is the second most consequential scope decision. Oracle's preferred opening is WebLogic Server Standard Edition. The customer's preferred is WebLogic Server Enterprise Edition or WebLogic Suite, with Coherence and the SOA Suite components specifically included.

The Java SE rights in a ULA are a related question. Modern Oracle Java is a separate subscription product priced per employee. Some legacy ULAs included Java SE Advanced as part of the middleware bundle. We push for Java SE Universal Subscription rights to be included in any new ULA where the customer has a meaningful Java footprint. Oracle resists this on the basis that Java is now sold separately, but on large enough ULAs Oracle has signed Java inclusion at no incremental price. Oracle Java covers the broader Java dynamic.

Applications scope

For customers running EBS, PeopleSoft, JD Edwards, or Siebel, the applications scope is its own conversation. Oracle's preferred position is to exclude applications from the ULA scope entirely and require separate Applications Unlimited or per user licensing. The customer's preferred position depends on the planned application deployment.

If the customer is deploying or expanding an Oracle application footprint during the ULA term, application scope inclusion is high value. If the customer is migrating off Oracle applications, application scope is irrelevant. The decision is driven by the customer's deployment roadmap, not by Oracle's pricing structure. Oracle E-Business Suite covers the EBS specifics. Oracle JD Edwards covers JDE.

Cloud scope and the data centre clause

Modern ULAs include rights to deploy the scoped products in cloud environments, but the cloud language varies. The customer should push for cloud deployment rights that match the customer's projected cloud architecture, including OCI, AWS, Azure, Google Cloud, and where relevant, Equinix Metal or other co location providers.

The data centre clause specifies the geographic locations where ULA deployments are permitted. Oracle's standard language permits deployment in the customer's principal place of business and a defined set of approved regions. For customers with global operations, we push for global deployment rights with no per region cap.

The non scoped products list

Every ULA scope clause carries an implicit corollary, the list of products not in scope. Customers should explicitly identify the non scoped products and either accept that they will be separately licensed during the term or push to add them to scope. The implicit list is more dangerous than the explicit list because it can be invoked by Oracle in certification to argue that a particular deployment falls outside the agreed coverage.

We require the contract to list non scoped products by name on every ULA we negotiate. The list functions as a positive declaration of what is excluded, which prevents Oracle from arguing post hoc that an unspecified product was always outside scope. Licensing Compliance covers the broader compliance dynamic of in scope versus out of scope deployments.

The version uplift clause

The standard ULA scope covers the program version current at the start of the term and all versions released by Oracle during the term. It does not cover Oracle program renames or major architectural changes that Oracle markets as a new product rather than a new version. The Oracle Autonomous Database is the canonical example. Customers with a ULA covering Database Enterprise Edition may find that Autonomous Database is treated as a new product, outside the scope.

The buyer side mark up is a version uplift clause that explicitly extends the scope to any product Oracle markets as a successor or as a functionally equivalent offering during the term. Oracle resists this on the basis that successor products are commercially separate, but on large enough ULAs Oracle has signed limited successor language. The clause is most valuable for customers whose Oracle estate is likely to shift to newer Oracle products during the ULA term.

The engagement model

We mark up the scope clause on every ULA engagement. The mark up is part of the broader ULA negotiation service and is priced on a blend of fixed fee for the scope analysis and success fee for the savings against Oracle's first written offer. The scope alone commonly accounts for 30 to 50 percent of the total ULA value, and a well negotiated scope clause adds materially to the customer's bargaining position at certification. For the broader ULA framework see ULA Negotiation. For the underlying ULA deal structure see ULA. For Oracle Database licensing context see Oracle Database. For the full ULA framework download The ULA Exit Framework.