Oracle Java Audit Defense for Construction and Engineering.

Why construction and engineering draw Oracle's attention

Construction and engineering businesses run Java across design and modeling tools, project controls platforms, document and drawing management systems, and the back office applications that hold them together. They also carry enormous field and site workforces: trades, laborers, site supervisors, and equipment operators whose daily work never involves the Oracle Java runtime. The employee metric charges on counted people, so a contractor whose Java sits on a few engineering and project systems still pays as if every person on every site were running it. That gap is where the defense begins.

The sector also runs on subcontractors and project specific labor. Trades are engaged for a phase, joint ventures spin up for a single scheme, and agency labor scales with the order book. Oracle's opening number treats all of them as permanent counted heads, and that assumption rarely holds once the workforce is mapped.

How the employee metric works, briefly

The mechanics are identical 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, which is why a default renewal at Oracle's opening number is almost never the right answer.

The counted population is the whole game

An engineering and construction group with 25,000 counted staff might run its real Java footprint on design, modeling, and project controls platforms used by a few thousand technical staff. The metric ignores that concentration and bills on the full headcount, including site trades and field labor who never open a Java application. 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 systems 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, so staffing agencies, outsourced functions, and seasonal labor all inflate the number even though those people may never touch a Java application. Establishing clear employment boundaries removes real figures from the claim. Before accepting any headcount, insist on a precise 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.

Subcontractors and joint ventures are a contractual question

Construction lives on subcontracted trades, agency labor, and joint venture structures. Many of these workers are employed by other businesses, and joint ventures often have their own employing entities and their own licensing position. Establishing those boundaries, and documenting which entity actually employs each population, removes real numbers from the claim. Before accepting any headcount, insist on a precise definition of who is being counted, which legal entities are in scope, and on what basis.

A worked exposure illustration

Consider an organization with 25,000 counted staff. 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, 25,000 at $7.50 per employee per month	$2,250,000
Indicative defended outcome after the population is disputed and the estate is migrated	$720,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.

Questions construction buyers ask

Most of our people are on site. Why are they counted?

Because the metric counts heads, not users. That is precisely why the defense is strong: a workforce dominated by field and site labor that has no path to Oracle Java is a large population you can document and remove from the basis of the claim once the estate is mapped and migrated.

How are subcontractors and joint ventures treated?

That is the pivotal question. Workers employed by other businesses, and populations sitting in separate joint venture entities, should be defined precisely before any headcount is accepted. Clarifying who is genuinely your counted employee often removes a meaningful slice of the claim.

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 a Strategy Call covers

A Strategy Call turns the claim into a plan. Bring your renewal date, your headcount, and any audit correspondence. 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. Construction leaders use the call to brief finance, project controls, and IT with figures grounded in a technical user base, not the full site workforce. You leave with a realistic range for your defended number and a clear sense of sequence, grounded in your real estate rather than Oracle's opening position.

What the first 90 days look like

A defense moves faster than most 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 your core systems. Through the following month we rebuild the evidence and model your real number across every band, 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, and open the commercial conversation from a defensible residual rather than the opening claim. Nothing in the defense disrupts a live project, a design environment, or a document management system outside normal change windows.

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. In construction the account also has to show how subcontracted trades, agency labor, and joint venture entities were treated, because those populations dominate the headcount. 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.

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.

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 rhymes with a neighboring sector, see audit defense for manufacturing and the logistics audit playbook. The common thread is the same in all of them: the employee metric overstates what you owe, and a disciplined buyer side defense closes the gap.