Case Study – Oracle ULA Optimization Service – Oracle ULA Certification Empowers UK Insurance Group to Reduce Risk and Spend
Background
In this case, a UK-based insurance group engaged Redress Compliance to assist in exiting an Oracle ULA and optimizing their license position.
The client is a prominent insurance provider headquartered in London, with operations across the UK and Europe. They have about 6,000 employees and an annual premium revenue of £3 billion.
The company’s IT systems include several Oracle technologies: Oracle Database serves as the core of their policy administration and claims management systems, Oracle PeopleSoft is utilized for HR and financial management, and Oracle WebLogic servers host various custom insurance applications.
These were encompassed in a 4-year Oracle Unlimited License Agreement, which was nearing its end.
The Oracle ULA was signed following a merger that the insurance group underwent, which temporarily required a spike in Oracle usage as systems were consolidated.
With the merger integration complete and IT systems stabilized, the company’s focus shifted to cost optimization and ensuring it only pays for what it needs going forward. Thus, they were inclined to certify out of the ULA rather than renew, if it could be done safely.
Challenges
The insurance firm faced several notable challenges on the path to ULA exit:
- Post-Merger Bloat: During the merger, the ULA had served as a convenient umbrella, and many Oracle instances were spun up liberally to facilitate data migration and integration. Afterward, some of these systems became redundant or were slated for decommission. However, if not carefully handled, they would still be counted in the ULA certification, potentially locking the company into licenses for software it no longer needed. The challenge was to identify and shed this “Oracle bloat” before certification.
- License Type Mix (Database and PeopleSoft): The ULA covered Oracle Database and PeopleSoft applications (which are licensed by the number of employees/users). Exiting meant counting both processors for databases and module licenses for PeopleSoft. This mixed counting is complex, and the company worried about miscounting PeopleSoft HR licenses (especially since not all employees use the system fully, but Oracle might consider all employees as named users by default).
- Oracle Audit Anxiety: The client was nervous about Oracle’s audit posture. The insurance industry is heavily regulated, and an Oracle audit discovering compliance issues could lead to not just financial penalties but also regulatory headaches (if critical systems are deemed improperly licensed). Oracle’s UK auditors had a reputation for being thorough. The company’s management wanted absolute assurance that exiting the ULA would not invite an audit they couldn’t pass.
- Timeline Pressure: The ULA was set to expire in six months, and the decision to exit was made somewhat late. This compressed timeline meant the work of cleanup, counting, and negotiating with Oracle (if needed) had to be done quickly. If they failed to certify properly in time, they’d either lapse into non-compliance or be forced to hastily renew under Oracle’s terms.
- Future Growth Uncertainty: While current usage had stabilized, the insurance group did plan on digital expansion (new online services, possibly an acquisition of a smaller regional insurer). Some in leadership worried that exiting the ULA might be short-sighted if growth resumed, possibly necessitating new Oracle licenses within a year or two. There was an internal debate: save costs now or keep unlimited cushion “just in case”?
How Redress Compliance Helped
Redress Compliance provided a structured approach to help the UK insurer tackle these challenges pragmatically and efficiently:
- Oracle Environment Audit: Redress initiated a rapid yet comprehensive audit of the Oracle environment. They used discovery scripts and interviews with IT teams to map all Oracle Database instances and PeopleSoft usage. Crucially, they identified systems earmarked for decommission. Redress recommended accelerating the retirement of certain duplicate databases that were remnants of the merger, ensuring they could be shut down before the final ULA count.
- Optimization and Rightsizing: For active systems, Redress found opportunities to optimize. For example, some database servers were running at low utilization on 16-core machines. Redress suggested partitioning or moving some databases to smaller servers, effectively reducing the required license counts for certification. They also guided the company in archiving some historical data to allow for shutting down a large reporting database that was barely used. In PeopleSoft, Redress collaborated with HR to clarify the actual active user counts versus dormant accounts, providing a more accurate picture of licensing needs.
- Proof of Compliance Preparation: Anticipating Oracle’s scrutiny, Redress prepared a detailed compliance package. This included evidence of each and every Oracle deployment with timestamps, proving what was active at the ULA end. For PeopleSoft, they prepared user lists and documentation showing how the count was derived (excluding, for instance, contractors or former employees who were still in directories but not actual users of the system). This proactive stance meant that if Oracle audited right after ULA, the company would hand over a neatly packaged report, likely deterring a prolonged investigation.
- Executive Stakeholder Alignment: Redress helped mediate the internal debate about exiting vs. renewing. They provided a scenario analysis: if growth occurs and more Oracle licenses are needed in two years, what would that cost compared to paying for a renewal now? The analysis showed that even with growth, it was cheaper to exit and later buy additional licenses if required than to renew preemptively. This data convinced the cautious executives, uniting everyone behind the exit plan.
- Oracle Engagement and Certification Filing: When it came time to certify, Redress carefully guided the creation of the certification letter to Oracle. They ensured it included all necessary details and nothing superfluous. Redress also pre-briefed Oracle’s UK LMS (License Management Services) team with a high-level summary of what the client would certify, framing it positively (e.g., highlighting that the company had streamlined its usage and was a satisfied Oracle customer continuing with substantial perpetual licenses). This amicable engagement helped set the tone that the client was professional and prepared, not a target for a fight.
- Post-Certification Support Plan: Redress didn’t stop at just the certification. They helped the client outline a post-certification license management plan: how to monitor Oracle usage going forward, how to handle any new projects needing Oracle (with a process to evaluate if existing licenses suffice or if purchases are needed). This plan was part of ensuring the client wouldn’t slip into any compliance issues after the ULA.
Outcome and Impact
The UK insurance group successfully navigated the ULA exit with impressive results:
- Certified Out Cleanly: The client completed the ULA certification on time, listing all Oracle Database processor licenses and PeopleSoft user licenses they would keep. Oracle accepted the certification without dispute. The preparation paid off – there were no follow-up questions from Oracle, and no audit was initiated in the aftermath. The company effectively “graduated” from the ULA with a clean bill of health.
- Cost Savings Achieved: By not renewing the ULA, the company avoided an immediate £10 million renewal fee that Oracle had informally proposed for a three-year extension. Instead, they paid £0 in new licenses at exit, as their optimized usage fit within their existing rights. They anticipated approximately £2 million/year in Oracle support fees for the now-perpetual licenses, but this was still a significant reduction from the £4 million/year they would have paid under a renewal. Over three years, they are projected to save roughly £6 million in net costs.
- Lean License Footprint: Through the optimization efforts, the final license count was notably leaner. They ended up certifying around 20% fewer Oracle processors than they had running six months prior, thanks to cleanup and downsizing. For PeopleSoft, they certified licenses only for active named users, which was thousands less than the total employee count – avoiding over-licensing. This lean footprint means lower support costs and less shelfware.
- No Interruption to Business: The entire transition was invisible to business operations. Policy management systems, claims processing, and HR functions all continued smoothly with no downtime. Users and customers were unaware of any change – exactly the outcome desired for a risk-averse insurance business. The IT team was able to tighten the environment without affecting service levels.
- Future-Ready Posture: Now operating with owned licenses, the insurance group has the flexibility it needs. Should they acquire another company or launch a new product line, they can evaluate if Oracle is the right choice or if other solutions make sense, without the all-or-nothing pressure of an expiring ULA. If Oracle usage needs to grow, they can consider another ULA or one-off purchases, but on a timeline that suits them. They regained control over their IT strategy rather than being bound by Oracle’s renewal cycle.
- Risk Mitigation: From a governance perspective, the company’s risk profile improved. There is no looming compliance threat or vendor-driven deadline. They have documented compliance, which can be shown to regulators or auditors if needed. The CIO reported to the board that the Oracle licensing risk was “mitigated and under control,” a significant relief for a heavily regulated entity.
Client Quote
“Exiting an Oracle ULA felt like walking a tightrope – one misstep could have cost us millions or landed us in hot water with an audit. Redress Compliance was the safety net that ensured we got to the other side without a scratch. Their team helped us find and eliminate inefficiencies, count exactly what we needed, and confidently stand up to Oracle with facts and figures. The result is real savings and, frankly, a huge weight off our shoulders. We’re now in control of our Oracle licenses, instead of the other way around. I’d recommend Redress to any company that wants to make their Oracle situation work for them rather than against them.” – IT Operations Director, UK Insurance Group (anonymous)
Call-to-Action (CTA)
Thinking about exiting your Oracle ULA but worried about the risks? Redress Compliance is here to help. Schedule a free Oracle ULA exit consultation with our experts.
We’ll assess your situation, help you clean up unused licenses, and craft a bulletproof certification strategy. Don’t let fear of audits or vendor pressure keep you from saving money – contact Redress Compliance today and take the first step toward licensing freedom.
Read about our Oracle ULA License Optimization Service.
Read about our other Oracle Case Studies.
