Oracle Java Audit Defense for Energy and Utilities.

Why energy and utilities draw Oracle's attention

Energy and utility companies run dispersed workforces across generation sites, field crews, control rooms, and corporate offices, while their Java estate concentrates in control, metering, trading, and asset management systems. The employee metric charges for every field technician and every meter reader, regardless of whether they ever open a Java application. With large field and operational populations, the counted headcount becomes the central commercial question.

Utilities also operate a strict divide between operational technology and corporate IT, and that divide is often where the audit conversation goes wrong. Oracle counts people, not systems, so a workforce concentrated in operations can be charged as if every worker were running enterprise Java. Getting the boundary right is the first move in any serious defense.

How the employee metric works, briefly

The mechanics are the same in every sector. In January 2023 Oracle moved Java SE to the Universal Subscription, priced on a per employee metric rather than on what you actually deploy. List pricing runs from 5.25 to 15.00 dollars per employee per month, stepping down through volume bands, so smaller estates sit near the 15.00 ceiling and the largest sit near the 5.25 floor. The metric counts every full time and part time employee, every contractor, and every temporary worker, regardless of who ever opens a Java application. LMS audits intensified in 2026 with a three year lookback, and the opening claim is simply the counted population multiplied by the list rate, before any discount Oracle chooses to offer.

This is a sharp break from the past. Before April 2019, Java SE updates were effectively free for most commercial use, and even after that the older per processor and Named User Plus models charged for where Java actually ran. The employee metric severs cost from deployment entirely. For most large energy and utility companies it can cost several times the old approach for the very same systems, which is why a default renewal at Oracle's opening number is almost never the right answer.

The counted population is the whole game

A utility with 35,000 staff might run its real Java footprint on the control, metering, and trading platforms maintained by a few hundred specialists. The metric ignores that concentration and charges on the full headcount, including every field crew member and every site worker. When the basis of the charge bears no relationship to actual Java use, there is a large and legitimate gap to close. The buyer side task is to rebuild the picture from your own records, isolate the workloads that genuinely require Oracle Java, and show that the rest either already runs on a free OpenJDK distribution or can move there.

Contractors and temporary workers, the hidden multiplier

The single most overlooked driver of the claim is the inclusion of non employees. The metric counts every contractor and every temporary worker, which means staffing agencies, outsourced functions, and seasonal labor all inflate the number even though those people may never touch a Java application. Energy and utility operators run large contractor populations for construction, maintenance, metering, and field services, often through engineering partners and labor agencies. Many of these workers are employed by other businesses, yet Oracle may try to count them. Establishing those employment boundaries removes real numbers from the claim. Before accepting any headcount, insist on a clear definition of who is being counted and on what basis. In many estates, challenging the contractor and temporary worker assumptions alone removes a substantial share of the opening claim.

Operational technology systems are the real estate

The Java that matters in this sector sits in grid and plant control systems, metering and data collection platforms, energy trading and risk systems, and the asset management tools that schedule maintenance. Many of these are safety relevant or revenue critical and run continuously, which is why utilities assume they are locked into Oracle Java across the estate. In practice a large share of these workloads run on a free OpenJDK distribution with no functional change. Isolating the components that genuinely need Oracle support, and moving the rest under controlled change, is what shrinks the residual to a defensible size.

Field and site workforces are not a Java footprint

The largest part of a utility's workforce is in the field, on tools and handheld devices that have nothing to do with the Oracle Java runtime. Pulling those populations out of the counted base, and documenting that they have no path to Oracle Java, deflates the opening claim quickly. Oracle's opening number treats a line worker the same as a trading platform engineer, and that assumption does not survive scrutiny once the estate is mapped properly.

Change control is a feature of the defense, not a blocker

Utilities live under regulatory oversight and rigorous change control, and teams are rightly cautious about altering systems that keep the lights on. A buyer side migration is built around that reality. Workloads move in governed stages with testing and rollback, so a runtime change never becomes an operational or compliance event. The aim is a documented, credible path off Oracle Java that protects safety and reliability while removing the assumption that you must renew the whole estate.

A worked exposure illustration

Consider an energy or utility company with 35,000 counted staff across generation, networks, field, and corporate functions. At an indicative rate it produces the opening claim below, alongside the kind of defended outcome we target across the estates we work on.

Indicative figures for illustration only

Line	Amount per year
Oracle opening claim at list, 35,000 at $7.50 per employee per month	$3,150,000
Indicative defended outcome after the population is disputed and the estate is migrated	$1,008,000
Indicative reduction versus the opening number	about 68 percent

Indicative only. The 68 percent reflects our average reduction versus Oracle's opening number across the audits we defend. Your outcome depends on your deployment, your contract, and how the population is counted. We confirm your real number before you commit.

The defense, step by step

1. Bound the request. Fix the population, the period, and the data format before anything leaves your building, so the audit runs on your scope rather than Oracle's.
2. Rebuild the evidence. Use your own asset and configuration records to show what Java is actually deployed and who genuinely uses it.
3. Dispute the population. Remove workers who have no path to Oracle Java and challenge contractor and temporary worker assumptions that inflate the count.
4. Shrink the residual. Migrate everything that can move to a free OpenJDK distribution, leaving a small Oracle envelope that you can defend.
5. Negotiate and clean the contract. Settle against the smaller envelope and strip the minimum annual floor, the annual true up, and the renewal escalator from the renewal.

What a Strategy Call covers

A Strategy Call is the fastest way to turn an abstract claim into a plan. Bring your renewal date, your rough headcount, and any audit correspondence you have received. In under an hour we map your likely band, identify the populations that should never have been counted, and sketch which workloads can move to a free OpenJDK distribution. You leave with a realistic range for your defended number and a sense of the sequence, before you commit to anything. Energy and utility leaders use the call to brief finance and operations with figures grounded in your real estate rather than Oracle's opening position.

What the first 90 days look like

A defense moves faster than most operational teams expect once the scope is bounded. In the first two weeks we contain the data request and stand up an internal view of what Java is really deployed across control, metering, and trading systems. Through the following month we rebuild the evidence and model your real number across every band and legal entity, so you know your floor and ceiling before Oracle does. In the final stretch we dispute the population, sequence a migration of everything that can leave Oracle Java under your change control, and open the commercial conversation from a defensible residual rather than the opening claim. Nothing in the defense requires you to alter a safety relevant system on Oracle's timetable.

Questions buyers ask

Does it matter that few of our people actually use Java?

For the claim, no, and that is the problem. The metric counts the whole population regardless of use. For the defense, it matters a great deal, because the wider the gap between counted heads and real users, the more of the opening number is open to challenge once you migrate the estate to a free distribution.

Can Oracle reach back into prior years?

The 2026 audits apply a three year lookback, so deployment history matters. Rebuilding a clear record of what was installed and when, from your own asset data, is part of bounding what Oracle can reasonably claim for past periods.

What if we want to leave Oracle Java entirely?

For many workloads that is realistic. Most Java can run on a free OpenJDK distribution with no functional change, leaving only the systems that genuinely need Oracle support. A credible plan to move is also your strongest position at the table, because it removes the assumption that you have no choice but to renew.

Our control systems cannot just be changed. Does that lock us in?

No. A handful of components may genuinely need to stay on Oracle Java, and those define your residual. The rest of the estate almost always has a migration path on a governed timeline. A small, well documented Oracle envelope is exactly what a strong settlement is built on.

How we are paid

We work two ways, both built so the risk sits with us. A Fixed Fee starts from $18,000, agreed up front and backed by our guarantee. Or you can choose Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to you. If we do not reduce your Oracle Java cost, you do not pay for an outcome we did not deliver. Across the work we do, we have defended more than $120M in Java exposure and over 300 Java audits, with more than 20 years of combined experience on the buyer side of the table.

Building the internal business case

The hardest part of a defense is often internal, not external. Finance wants a number it can plan against, IT wants assurance that nothing breaks, and legal wants to know the position is defensible. A buyer side defense produces the evidence each of them needs: a modeled exposure range across every band, a migration plan that names what moves and when, and a clear account of which populations were removed from the count and why. That shared picture lets the organization decide with confidence rather than reacting to Oracle's deadline.

It also reframes the conversation from cost to choice. Once leadership can see that most of the estate can run on a free OpenJDK distribution, and that the genuine Oracle Java need is small, the renewal stops being an inevitability and becomes one option among several. That shift, more than any single negotiating tactic, is what produces a durable reduction rather than a one time discount that erodes at the next anniversary.

Five mistakes that cost energy and utilities teams money

The same avoidable errors appear again and again. First, treating Oracle's opening number as a starting point that is roughly right rather than an unbounded claim that has to be earned line by line. Second, sending the LMS team raw data before the population and the period are bounded. Third, accepting a headcount that includes contractors, temporary workers, and entities that should never have been in scope. Fourth, agreeing a subscription on the whole workforce when only a fraction of systems need Oracle Java and the rest can move to a free OpenJDK distribution. Fifth, signing a renewal that still carries a minimum annual floor, an annual true up, and an escalator, so the cost climbs again the moment the ink dries.

Each of these is reversible if it is caught early, which is the strongest argument for bringing in a buyer side defense the moment an audit letter arrives rather than after data has already changed hands.

Where to go next

The fastest way to ground your team is our Oracle Java licensing guide for 2026, which lays out the metric, the bands, and the defense in full. If your situation looks like a neighboring sector, see the manufacturing audit playbook and audit defense for telecom. The common thread across all of them is the same: the employee metric overstates what you owe, and a disciplined buyer side defense closes the gap.