Global Manufacturer. Four million dollar Oracle Java audit claim resolved at zero cost.

A global manufacturing group operating in around forty countries with roughly one hundred thousand employees received an Oracle Java claim of approximately four million dollars.

The Java SE Universal Subscription is priced per employee, so a hundred thousand person group is priced on a hundred thousand people regardless of where Java actually runs.

The claim closed at zero. The defence was an inventory that separated Oracle's own Java distributions from everything else.

The customer profile

Around one hundred thousand employees across roughly forty countries, running manufacturing, engineering and corporate systems.

Manufacturing estates are the hardest place to inventory Java, because a large share of the compute sits on the plant floor rather than in a data centre. Machine controllers, quality systems and engineering workstations all commonly carry a runtime supplied by an equipment vendor.

Forty countries also means the estate was never bought or standardised as one thing, so the answer differs by site.

The opening position

Oracle's opening claim was approximately four million dollars, priced across the employee population.

Because the metric keys on headcount, the deployment size barely moves the number. That is exactly why the defence has to address whether a requirement exists at all.

The approach

Not all Java is Oracle Java. OpenJDK builds run the same code and carry no Oracle subscription requirement, and that distinction carried the engagement.

We inventoried by distribution across corporate IT, engineering and the plant estate, separating Oracle binaries from OpenJDK builds and from runtimes embedded in equipment vendor software.

The plant estate was the decisive category. Where a machine or quality system vendor ships and controls its own runtime, the licensing position sits under that vendor's agreement rather than with the manufacturer.

We then documented every Oracle Java removal already performed and reconciled the whole picture against Oracle's download records.

The eleven moves

1. Inventory by distribution. Oracle builds, OpenJDK builds and vendor embedded runtimes are three different licensing positions.
2. Find the bundled runtimes. Third party applications that ship their own Java are the most commonly missed category.
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. Test the employee count definition. Understand precisely who the metric includes.
6. Scope the audit in writing. Entities, systems and periods, agreed before data moves.
7. Answer system by system. A total invites negotiation; a system invites correction.
8. Establish the OpenJDK path. For anything Oracle branded that remained.
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. Java arrives inside other software continuously.

The commercial outcome

The claim closed at zero cost, approximately $4M below Oracle's opening position.

On a manufacturing estate the plant floor is where the answer lives. Inventory that reaches only the corporate desktop will never resolve one of these claims.

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.