Meyer Sound. Five hundred thousand dollar Oracle Java claim resolved at zero cost.

Meyer Sound is a US professional audio equipment manufacturer with roughly five hundred employees. Oracle opened a Java claim of approximately five hundred thousand dollars.

That works out to more than a thousand dollars per employee for a company whose actual Java footprint was a handful of engineering workstations. The arithmetic tells you everything about how the metric behaves at mid market scale.

Large enterprises absorb the Universal Subscription as a line item. For a five hundred person manufacturer it is a material capital decision, which is exactly why the evidence work matters more, not less.

The claim closed at zero.

The customer profile

Around five hundred employees across US operations, designing and manufacturing professional audio systems. Engineering led, with a technology estate shaped by product development rather than by back office scale.

Java appeared where it usually does in an engineering business: inside design and measurement tooling, some of it supplied by third party vendors with their own bundled runtimes, some of it installed years ago by engineers who needed it for a specific task.

Nobody had ever been asked to account for it, because until the metric changed there was no reason to.

The opening position

Oracle's opening claim was approximately five hundred thousand dollars, priced across the whole employee population under the Universal Subscription.

The company had no dedicated software asset management function, which is normal at this size and is also why these claims land hard. There was no existing inventory to answer with and no obvious place to start.

That absence is frequently mistaken for weakness. It is not. It simply means the evidence has to be built rather than retrieved.

The approach

We built the inventory from scratch, across a small enough estate that it could be done thoroughly rather than statistically.

The work separated Oracle's own Java distributions from OpenJDK builds and from runtimes bundled inside third party engineering software. That distinction is the whole case, because OpenJDK builds carry no Oracle subscription requirement.

We then documented every removal that had already taken place and reconciled the position against what Oracle could see in its own download records.

A smaller estate is an advantage here. Where a global enterprise samples and extrapolates, a five hundred person company can produce a complete and defensible picture.

The eleven moves

These are the moves that closed the claim.

1. Inventory by distribution. Oracle builds and OpenJDK builds are different licensing objects.
2. Cover the whole estate, not a sample. At this size completeness is achievable and worth far more than extrapolation.
3. Find the bundled runtimes. Engineering and design tooling frequently ships its own Java.
4. Evidence every removal. Dated records, not recollection.
5. Reconcile against download records. Understand what Oracle can see.
6. Scope the audit in writing. Before producing any data.
7. Answer machine by machine. A complete small estate is a strong position.
8. Establish the OpenJDK path. For anything Oracle branded that remained.
9. Test the employee count definition. Know exactly who is counted.
10. Put download controls in place. One engineer downloading from Oracle rebuilds the exposure.
11. Re inventory annually. Cheap at this scale, and it keeps the position current.

The commercial outcome

Meyer Sound closed the Oracle Java claim at zero cost, approximately five hundred thousand dollars below Oracle's opening position.

The transferable point for any mid sized company is that the absence of a software asset management function is not a losing position. It just means the inventory has to be built, and at this scale it can be built completely.

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.