The case for deployment maximization is easiest to see line by line. This worked example walks a certified processor count from a first production estimate to a defensible final number, and shows why support does not move while the count nearly doubles. All figures are indicative.
Certified counts often land 1.5 to 2.5 times higher than a first estimate once cloud, disaster recovery, and non production deployments are handled properly, and support stays flat at the ULA level throughout. The example below shows a count that starts at a production figure of 200 processors and finishes at 430, captured once and held forever. The multiple is indicative and depends entirely on the estate and the specific contract language.
Maximization is not a trick. It is the patient work of counting every defensible deployment you already paid for, evidencing each one, and refusing to leave the unlimited part of the agreement uncounted.
A mid sized insurer approached its ULA exit expecting to certify around its production database footprint, roughly 200 processors. That figure was the obvious count, the one Oracle's first pass tends to produce, and the one that leaves the most value behind. Working through the estate against the contract added four more categories, each legitimate, each evidenced, each deployed inside the term.
Each line below is a real category of deployment that a first estimate missed. The core factor is applied where relevant, and every line carries an evidence trail of host, date, and workload.
The final defensible count was 430 processors against a first estimate of 200, an uplift of roughly 2.15 times. Every added line was a genuine deployment the insurer was entitled to count, and every one was supported by evidence that would hold under review.
This is the part that surprises people, so it is worth stating plainly. There is no fee for certification itself. Support fees continue at the ULA level regardless of the certified count, so certifying 430 processors rather than 200 did not raise the insurer's annual support bill by a cent. The fear that a larger certified number increases support is a myth. The extra 230 processors are free value, captured once and held as perpetual entitlement forever. The only thing that closes the opportunity is the end of the term.
The number is only as durable as the evidence behind it. Each line was supported by a server or instance list, a deployment date inside the term, and a record of the workload. The cloud lines carried the additional proof their clauses required, including the continuous run record for the AWS deployment. Audit risk rises in the first two years after certification, and the evidence file is what defends every line if a review comes. A high count with no trail is not value, it is exposure.
Whether cloud counts, how virtualization is read, which products allow an alternative metric, and what scope applies all come from the specific agreement. The insurer's 2.15 multiple is its own, not a benchmark. Your estate and your contract will produce a different line by line build. In ULA work the answer almost always depends on the specific wording, so the math is run against your own contract, never a template.
If your ULA is approaching its end, the fastest way to see your own number is to build it line by line against your contract. Start with the deployment maximization pillar guide, then read the deployment maximization guide and moving workloads on premises to count them.
Certified counts often land 1.5 to 2.5 times higher than a first estimate once cloud, disaster recovery, and non production deployments are handled properly. The exact multiple is indicative and depends entirely on the estate and the specific contract language. The worked example here shows the count roughly doubling.
No. There is no fee for certification, and support fees continue at the ULA level regardless of the certified count. A higher defensible number is captured once and held forever without raising the annual support cost, which is why maximization is so one sided in the customer's favor.
Every deployment in the count needs an evidence trail, a host or instance, a deployment date inside the term, and a record of the workload. The evidence file matters as much as the number, because audit risk rises in the first two years after certification and an unsupported line is what a review removes.
Book a confidential assessment and we will build your certified count against your own contract, with the evidence trail behind every line.