Swedish Manufacturing Group. Oracle Java quote cut 70 percent.

A Swedish manufacturing group found Oracle JDK embedded across plant systems, build servers, and engineering tools. An estate split between IT and OT, a disciplined migration, and a short bridge closed the matter 70 percent below the opening quote.

Why did Oracle approach the Swedish manufacturing group?

Oracle approached the group with download records spanning several years and multiple sites, then quoted the Java SE Universal Subscription across the entire workforce. For a group with thousands of employees across plants, the opening number was a board level figure.

Manufacturing estates attract this motion because Java hides well there. Build servers, engineering tools, and plant adjacent systems accumulate JDK installs that nobody centrally tracks.

• The outreach: a licensing review referencing JDK downloads across European sites.
• The metric: every employee in the group, office and plant floor alike.
• The blind spot: OT systems running Java outside the IT asset register.

What did splitting the estate between IT and OT reveal?

The split revealed two different problems. The IT estate was large but fast to migrate, while the OT estate was smaller but slow, gated by maintenance windows and equipment vendor support positions documented against the Oracle JDK licensing FAQ.

Why does OT Java need its own track?

Because plant systems change on the plant's calendar, not the negotiation's. Forcing OT swaps to meet a licensing deadline risks production, and that risk is exactly what the vendor's timeline pressure monetizes.

How did the group run the migration and the negotiation in parallel?

The group migrated loudly on the IT side while negotiating quietly on the OT side, so every monthly status update showed Oracle a shrinking footprint and a hardening alternative.

1. Build the first complete Java inventory across IT and OT, plant by plant.
2. Migrate build servers and internal tooling to OpenJDK immediately.
3. Document equipment vendor support positions and exclude vendor covered stacks.
4. Schedule OT runtime swaps into the next two maintenance window cycles.
5. Negotiate a bridge over the OT remainder only, with list pricing as the ceiling.

What evidence carried the most weight with Oracle?

Completed migrations. Plans are debatable; decommissioned installs are not. Each phase report moved the retained core downward and with it the only number the subscription could honestly price.

What was the outcome for the manufacturing group?

The matter closed 70 percent below the opening quote, with a fixed term bridge covering the OT remainder while maintenance windows completed the swaps. No retroactive fees were paid.

• Quote reduction: 70 percent below the opening employee metric number.
• Scoped bridge: OT systems only, term matched to the maintenance window calendar.
• Forward posture: Java tracked in the asset register across IT and OT, downloads policed at the edge.

What changed permanently in how the group manages Java?

Java became an inventoried asset class. New plant systems now declare their runtime and license source at procurement, which keeps the next outreach letter answerable in a week.

Where the common advice on manufacturing Java estates is wrong

The standard advice is that manufacturers should settle Java claims quickly because plant complexity makes a clean defense impossible. We disagree. In roughly 40 to 60 Java engagements Fredrik Filipsson advised in 2024 to 2025, the plant complexity argument favored the buyer once the estate was split: the complex OT remainder was small enough to bridge cheaply, and the large IT estate migrated in a quarter or two. The buyer side move is to refuse the single blended number, split IT from OT, and let each segment price on its own facts and its own calendar.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Run a Java inventory that explicitly includes OT and plant adjacent systems.
2. Split the estate into IT and OT tracks with separate owners and calendars.
3. Migrate build servers and internal tooling to OpenJDK this quarter.
4. Document equipment vendor support positions on bundled runtimes in writing.
5. Schedule OT runtime swaps into existing maintenance windows, not new ones.
6. Respond to any Oracle outreach with conclusions from your inventory, never raw logs.

White Paper · Oracle

Oracle Java Audit Defense 2026

Oracle now audits Java SE on employee count, not installs, which can multiply the bill several times over. Read it free.

Read the white paper

Frequently asked questions

What triggered Oracle's Java outreach to the Swedish manufacturer?

Years of Oracle JDK downloads from the group's sites triggered it. Oracle's Java team opened with a licensing review and quoted the employee metric across the entire workforce within weeks.

How much did the manufacturing group save against the Java quote?

The matter closed 70 percent below the opening number. Coverage shrank from the full workforce to a fixed term bridge over OT systems awaiting maintenance window swaps.

Why is Java licensing harder in manufacturing than in office estates?

Visibility. OT and plant adjacent systems held 20 to 40 percent of Java installs in our manufacturing engagements but were missing from IT inventories, so the buyer often discovers their real footprint during the dispute.

Can plant systems running Java move to OpenJDK?

Usually yes, within maintenance windows. The constraint is scheduling and equipment vendor support positions rather than technical compatibility, which is why OT swaps ride the maintenance calendar instead of the negotiation deadline.

Do equipment vendor systems with embedded Java need our own Oracle license?

Generally no. Systems whose vendor ships and licenses their own runtime are covered under the vendor's terms. Documenting those positions in writing removed a material slice of the quoted need in this case.