Gwinnett County Public Schools Oracle Advisory

The Challenge: Oracle Complexity at Scale in a K-12 Environment

Large public school districts face a licensing challenge that commercial enterprises rarely encounter in quite the same form: enormous organisational complexity — tens of thousands of employees, contractors, and part-time staff — combined with constrained budgets, aggressive vendor renewal cycles, and very limited internal Oracle licensing expertise. Gwinnett County Public Schools, serving more than 180,000 students across Georgia and employing over 27,000 staff, found itself in exactly this position.

The district had deployed Oracle ERP and EPM Cloud to modernise its financial planning, budgeting, and HR operations. The technology investment was sound — Oracle's cloud platform delivered genuine operational gains. But the commercial and licensing framework that came with it was a different matter entirely. When Redress Compliance was engaged, the district's Oracle spend had been escalating at 8% per year on the base support fee, compounding annually into a trajectory that its budget office could no longer absorb. Additionally, the district had received its first Oracle audit notification and had no independent expertise to respond.

Critically, the district's internal IT and procurement teams were not Oracle licensing specialists. They had signed a standard Oracle support agreement without a full understanding of which database options and features were implicitly licensed through their ERP deployment, nor how Oracle's audit methodology would scrutinise their environment. This is not an unusual position — it is the default position for most Oracle customers. Redress was brought in to provide what the district needed: independent expertise with no commercial relationship with Oracle, and 20+ years of experience on exactly these engagements. Details of all specific work undertaken are shared with the district's express consent as part of our published case study programme.

Oracle ERP Licensing Risks in a Large K-12 Environment

When Redress conducted its initial Oracle audit risk assessment, the findings were instructive — and they are findings we see repeatedly across large public-sector Oracle customers. First, the district's Oracle Database deployment included several options and packs that had been enabled during routine DBA operations: the Diagnostics Pack (which activates Automatic Workload Repository and Active Session History) had been in use for performance monitoring, and the Tuning Pack had been accessed during a database tuning exercise eighteen months earlier. Neither the DBA team nor the procurement team realised these were separately licensed Oracle options — they assumed they were standard features of Oracle Enterprise Edition.

This is one of the most common and most expensive hidden Oracle audit risks. Oracle Enterprise Edition does not include these packs by default — they require separate licensing at substantial cost. Oracle's LMS (License Management Services, now operating under the GLAS umbrella) is expert at identifying this exposure through its standard Data Collection Script, which logs feature and option usage automatically. When Oracle presented its findings, it initially claimed a shortfall of $2.3 million based on this diagnostic pack usage alone.

The second risk area was Java SE. The district had not tracked which staff were accessing Java-based applications across its estate. Under Oracle's employee-based Java SE Universal Subscription pricing model — introduced from January 2023 — organisations must count all employees regardless of whether they personally use Java. For an organisation of 27,000 staff, that exposure was substantial: at Oracle's standard tier pricing, the district was facing an annual liability of approximately $1.7 million for Java SE alone.

The Redress Engagement: Audit Defence, Cost Recovery, and Ongoing Advisory

Redress deployed a structured response to the Oracle audit notification. The first step was to halt any direct communication between the district's procurement team and Oracle's GLAS team — a critical but often overlooked protective measure. Oracle's audit process is not a neutral compliance review. It is a revenue recovery exercise, and every unguided response from a customer provides Oracle with additional leverage. The district's CIO and procurement director were advised to route all Oracle communications through Redress during the audit period.

Our technical team then conducted a full independent analysis of Oracle's Data Collection Script output. The $2.3 million Diagnostics Pack claim was challenged on two grounds: first, the usage data reflected automatic background collection by Oracle's own tooling rather than deliberate use by the district's staff; and second, the district was able to demonstrate remediation — disabling the relevant features and purging the usage logs — before Oracle's measurement date. Under Oracle's remediation policy, this substantially reduced the chargeable exposure. After twelve weeks of structured negotiation, the Diagnostics Pack claim was settled for zero additional cost. The district's existing licensing position was sufficient to cover the correctly scoped entitlement.

On Java SE, Redress challenged Oracle's employee count methodology and helped the district demonstrate that a significant proportion of its workforce — classroom-facing teaching staff without computer workstations — were definitively outside the scope of the Universal Subscription obligation. By applying the correct employee definition and negotiating a multi-year agreement with volume pricing, Redress reduced the district's Java SE liability from the initial $1.7 million Oracle demand to an agreed $340,000 annual commitment. Over three years, that represents savings of approximately $4.1 million against Oracle's opening position. Further details on this engagement are available on request via our Oracle total cost optimisation programme.

Support Cost Management and Oracle's 8% Annual Escalation

One of the structural challenges facing Oracle customers — and public sector ones particularly — is the compounding nature of Oracle's annual support fee increase. Oracle standard support increases at 8% per year. For a district spending $800,000 per year in Oracle support, the ten-year trajectory without intervention is more than $1.7 million per year by year ten. This is not a theoretical risk; it is what happens when organisations sign Oracle agreements without independent advisory and simply renew year-on-year at Oracle's stated rate.

Redress addressed this through two mechanisms. First, at each annual renewal, Redress prepared detailed benchmarking data showing the district's Oracle support costs relative to peer-group institutions and comparable commercial organisations. This benchmarking is not anecdotal — it draws on Redress's direct experience across 500+ enterprise Oracle engagements and provides a factual negotiating basis. Second, Redress reviewed the district's Oracle footprint for unnecessary support-covered licenses — instances where Oracle products were under support but no longer deployed or actively used — and helped the district terminate support on those products at renewal, reducing the support base before Oracle applied its annual increase.

These two mechanisms, applied consistently over four renewal cycles, held the district's support cost inflation well below Oracle's standard 8% trajectory and generated approximately $100,000 in annual savings against Oracle's standard renewal demand. The Oracle support cost optimisation assessment Redress runs for new clients typically identifies this type of opportunity within the first engagement week.

Key Lessons for Public Sector Oracle Customers

This engagement highlights dynamics that repeat across public sector Oracle customers regardless of institution type or size. The Oracle licensing framework is deliberately complex — Oracle's commercial teams are expert at identifying revenue opportunities within that complexity, while customers are typically under-resourced to counter them. The gap between Oracle's knowledge of your licensing position and your own knowledge of it is where Oracle's audit revenue comes from.

Several specific lessons apply. Oracle ERP and EPM Cloud deployments almost universally carry implicit database option exposure that customers are unaware of. DBAs routinely enable features that trigger separate licensing obligations with no technical barrier to prevent them — Oracle relies on the audit process rather than technical enforcement to collect revenue on these features. Any Oracle customer running Enterprise Edition should conduct an independent options audit before Oracle does. Second, Java SE exposure is not a technology team problem — it is a procurement and HR problem, because Oracle's employee count methodology spans the entire workforce. Organisations that approach Java SE renewal without independent advice consistently overpay. Third, Oracle support costs are manageable with the right negotiating structure — but they require independent benchmarking data and renewal timing discipline. Oracle's natural renewal process is designed to maximise Oracle's revenue; Redress's is designed to minimise yours. To learn how Redress can assess your specific Oracle exposure, book a confidential discovery call with our advisory team.

For a comprehensive review of your Oracle licensing position, our Oracle licensing advisory specialists provide independent assessments for public sector organisations.