Editorial photograph of a Mercy Health hospital operations team reviewing the Oracle Java framework
Case Study · Oracle · Mercy Health Java

Mercy Health. Four million dollar Oracle Java claim resolved at zero cost.

Forty thousand employees, and a licence metric that counts every one of them. The claim did not survive an inventory that separated Oracle Java from everything else.

Contact Us Oracle Practice
500+Vendor engagements
$4MJava claim zero cost
Watch the briefingResearch briefing · 4:43

How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal

Priced per employee, every employee, from $15 down to $5.25. At renewal your leverage is thin and OpenJDK threats rarely land. The one-year runway, trading through the wider Oracle relationship, and containing what you sign.

Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Mercy Health is one of the largest Catholic healthcare networks in the United States, operating across multiple states with roughly forty thousand employees. Oracle opened a Java claim of approximately four million dollars.

The size follows directly from the metric. Oracle's Java SE Universal Subscription is priced per employee, so a forty thousand person network is priced on forty thousand people regardless of how many of them ever touch Java.

The claim closed at zero. Not reduced, not settled at a discount. The evidence did not support a requirement, and once that was demonstrated there was nothing left to price.

The customer profile

Around forty thousand employees across a multi state hospital and clinic network, with a technology estate that is unusually varied even by healthcare standards.

Clinical environments are the hardest place to answer a Java question. Medical device software, imaging systems, laboratory equipment and electronic health record modules all commonly ship their own Java runtime, supplied and controlled by the vendor rather than by the hospital.

Add a large clinical workstation estate and a long tail of departmental applications, and the question is genuinely difficult to answer from memory. It is not difficult to answer from evidence.

The opening position

Oracle's opening claim totalled approximately four million dollars, priced across the full employee population under the Universal Subscription metric.

Under that metric the arithmetic is straightforward for Oracle. If any Oracle Java requirement exists anywhere in the organization, the subscription is priced for everybody, so the size of the deployment barely affects the number.

That is exactly why the defence cannot be about volume. It has to be about whether the requirement exists at all, and across which software.

The approach

The whole engagement rested on one distinction: not all Java is Oracle Java. OpenJDK builds run the same code and carry no Oracle subscription requirement.

We inventoried the estate by distribution rather than by presence of Java, separating Oracle's own binaries from OpenJDK builds and from runtimes embedded inside third party clinical applications.

The embedded category mattered more here than on a typical corporate estate. Where a device or clinical system vendor ships and controls its own runtime, the licensing position sits with that vendor's agreement rather than with the hospital.

We then assembled dated evidence for every Oracle Java removal the organization had already performed, which is the step most estates skip and the one that decides the argument.

The eleven moves

These are the moves that closed the claim. The first three carried it.

  1. Inventory by distribution. Oracle builds, OpenJDK builds and vendor embedded runtimes are three different licensing positions.
  2. Identify vendor supplied runtimes. Clinical and device software that ships its own Java sits under the supplier's agreement.
  3. Evidence every removal. Dated and systematic. An undocumented uninstall proves nothing.
  4. Reconcile against download records. Know what Oracle can see before the conversation opens.
  5. Scope the audit in writing. Entities, systems and periods, agreed before data moves.
  6. Answer by system, not by total. A total invites negotiation; a system invites correction.
  7. Establish the OpenJDK position. For anything Oracle branded that remained.
  8. Test the employee count definition. Understand precisely who the metric includes.
  9. Keep the audit separate from any renewal. They are different conversations.
  10. Put controls on Oracle downloads. Otherwise the position rebuilds within a year.
  11. Re inventory annually. Clinical software changes constantly and Java arrives with it.

The commercial outcome

Mercy Health closed the Oracle Java claim at zero cost, approximately four million dollars below Oracle's opening position.

Audit close versus opening claim

PositionClaim value
Oracle opening Java claimApproximately $4M
Final settlement$0
Saving against the opening claimApproximately 100 percent

The durable outcome is the evidence base. The network now holds an inventory that distinguishes distributions, a documented removal trail, and download controls that stop the exposure quietly rebuilding.

How we engage

  • Oracle Java scoping. A six week engagement that inventories Java by distribution, finds the bundled runtimes, and assembles the removal evidence. Oracle services practice.
  • Oracle Java audit defense. We run the response, reconciling download records against evidenced deployment. Oracle Java audit defense playbook.
  • Oracle Java exit. Costed migration to an OpenJDK build, with the controls that stop the position rebuilding. Oracle Java exit.
  • Vendor Shield. Always on cover across Oracle and the wider software estate. Vendor Shield.
  • Run the numbers. The Oracle Java license calculator sizes the employee metric against your actual estate.
Control Oracle Spend: The 5 Year CIO Playbook

Forty pages. The full Oracle position from the practice.

The eleven moves, the employee metric explained, separating Oracle builds from OpenJDK, evidencing removal, and the buyer side position at every step of a Java audit.

Used across more than five hundred enterprise clients. Independent. Buyer side. Built for CIOs running the next Oracle Java audit cycle.

Get the white paper →
Opens the white paper landing page. We only email you about this download.
Run the Oracle Java license calculator against your actual Oracle Java deployment in under five minutes.
Open the Tool →
$4M
Java claim avoided
11 moves
Buyer side moves
3 years
Contracted term
500+
Enterprise clients
100%
Buyer side

Oracle framed the Oracle Java audit as the immediate Oracle Java uplift at the audit cycle. Redress reframed the approach around Mercy Health's actual Oracle Java deployment. Four million dollars resolved at zero cost.

Director Software Asset Management
Mercy Health
Further Reading

From the same practice.

Oracle Practice →
Oracle Services Practice
Oracle · Practice
Oracle Services Practice
The Oracle services practice for the Oracle Java audit cycle.
20 min read
Oracle Java Audit Defense
Oracle · Audit
Oracle Java Audit Defense
The Oracle Java audit defense.
16 min read
Oracle Java Audit Defense Playbook
Oracle · Playbook
Oracle Java Audit Defense Playbook
The Oracle Java audit defense playbook.
18 min read
Oracle Java License Calculator
Oracle · Tool
Oracle Java License Calculator
The Oracle Java license calculator.
8 min read
Oracle Knowledge Hub
Oracle · Hub
Oracle Knowledge Hub
The Oracle knowledge hub.
12 min read
Editorial photograph

When you negotiate, we sit on your side.

Twenty years on the buy side. 500+ enterprises. $2B in client savings.

Oracle Java intelligence, monthly.

Oracle Java audit signals, Oracle Java SE Universal Subscription signals, Oracle Java OpenJDK alternative signals, and the broader Oracle Java licensing leverage signals across the practice.