Kuwait National Petroleum Company Saves $1.3M Through Internal Assessment

Executive Summary: $1.3M Annualised Savings Through Proactive IBM Licence Optimisation

Kuwait National Petroleum Company (KNPC) — a subsidiary of the Kuwait Petroleum Corporation and one of the largest oil refining and downstream companies in the Middle East — operates multiple refineries, distribution hubs, and engineering centres with over 6,000 employees. KNPC's complex IT infrastructure supports mission-critical refinery operations, production management, logistics, finance, and environmental compliance systems.

KNPC had used IBM software for over 15 years, with products including IBM Maximo (enterprise asset management for refinery equipment), WebSphere (application middleware), Tivoli (monitoring and workload automation), and DB2 (database platform). These systems were deeply embedded in plant management workflows, safety-critical processes, and regulatory reporting.

When KNPC's internal audit team raised concerns over IBM licence visibility and cost optimisation, Redress Compliance was engaged to conduct an independent IBM licensing assessment. The four-phase programme — entitlement reconstruction, deployment analysis, optimisation execution, and governance implementation — delivered $1.3 million in annualised cost savings while achieving full compliance and audit readiness.

The Challenge: 15 Years of IBM Licensing in a Refinery Environment

KNPC's IBM licensing challenges were shaped by the intersection of two forces: the complexity of IBM's licensing model and the unique demands of oil and gas operations where IBM software — particularly Maximo — is embedded in safety-critical processes.

IBM Maximo — The Refinery Backbone

IBM Maximo was the single most important IBM product in KNPC's estate. As an enterprise asset management (EAM) platform, Maximo tracked every piece of refinery equipment — pumps, compressors, heat exchangers, pipelines, instrumentation, safety systems — through their entire lifecycle: installation, maintenance scheduling, work order management, spare parts inventory, safety inspections, and regulatory compliance documentation.

Maximo's licensing was complex because it used multiple metrics simultaneously: Authorised Users (named users accessing the system), Concurrent Users (simultaneous active sessions), and in some configurations, PVU-based licensing for the underlying application server. Over 15 years, KNPC had accumulated Maximo entitlements through multiple purchases — some for specific refinery expansions, others for enterprise-wide rollouts — without consolidating the licence position or reconciling against actual usage patterns.

Middleware and Database Overgrowth

Oil and Gas Operational Constraints

IBM licence optimisation in a refinery environment carries risks that do not exist in financial services or technology companies. Maximo is connected to process safety management (PSM) systems — if a Maximo licence change disrupts access to equipment maintenance records or safety inspection schedules, the consequences are not just financial. KNPC required an optimisation approach that would deliver cost savings without any risk to plant safety, regulatory compliance, or operational continuity.

This constraint shaped the entire engagement: every optimisation recommendation had to be validated against operational requirements before execution, with plant operations teams involved in sign-off for any change affecting refinery-connected systems.

Phase 1: Entitlement Reconstruction and Contract Consolidation

The first phase built a complete, accurate entitlement register from KNPC's 15-year history of IBM contracts — replacing the fragmented, incomplete records that had accumulated through successive purchases, amendments, and renewal cycles.

Contract Archaeology — 15 Years of IBM Agreements

KNPC's IBM contract history included: original Passport Advantage agreements from the early 2010s; product-specific purchases for refinery expansion projects (Mina Abdullah, Mina Al-Ahmadi); enterprise-wide Maximo deployment contracts; middleware and database licence additions for ERP integration; Tivoli monitoring and scheduling purchases for operational technology environments; and annual support renewal documents that had evolved independently of the underlying licence grants.

The independent IBM advisory team reconciled every contract, ordering document, and amendment into a single register — mapping each entitlement to its product name and version, licence metric and quantity, source contract and date, current support status, and mapping to KNPC's current Passport Advantage site structure.

The Discovery — Fragmentation and Overlap

The reconstruction revealed a pattern typical of long-tenured IBM customers in the oil and gas sector: licence purchases were tied to capital projects (refinery expansions, new plant builds) rather than centralised IT procurement. Each project procured the IBM licences it needed independently — without checking whether existing enterprise entitlements already covered the requirement. The result was overlapping entitlements, duplicative purchases, and a total licence position significantly larger than operational requirements.

Phase 2: Deployment and Usage Analysis

With the entitlement position established, the second phase mapped actual IBM software deployment and usage across KNPC's refinery IT environment — identifying the gap between what was licensed and what was needed.

Maximo Usage Analysis

Maximo was KNPC's largest IBM product by licence cost — and the area with the greatest optimisation potential. The analysis examined total Authorised Users licensed versus active users in the Maximo application, Concurrent User peak measurements over a 90-day period, user role distribution (maintenance planners, technicians, inspectors, supervisors, finance, read-only), and access patterns by site (Mina Abdullah, Mina Al-Ahmadi, head office, engineering centres).

Middleware and Database Analysis

WebSphere and DB2 deployments were mapped across KNPC's server estate using ILMT scan data and CMDB records. The analysis identified: WebSphere PVU allocations based on legacy Power Systems hardware that had since been migrated to x86 — reducing the PVU-per-core requirement significantly; DB2 instances still under licence for applications that had been decommissioned or migrated to alternative databases; and Tivoli ITM agents licensed and under support on servers that had been decommissioned or moved to a replacement monitoring platform.

The Waste Map

Phase 3: Optimisation Execution — Safety-First Approach

The third phase executed the optimisation recommendations — with a methodology specifically designed for refinery environments where IBM software is embedded in safety-critical operations.

Three-Tier Execution Model

Every optimisation action was classified into one of three tiers based on operational risk.

Tier 1 — Zero operational impact: Actions that reduce licensing costs without touching any deployed software. This included support termination for products confirmed as not installed, PVU recalculations based on current hardware (entitlement adjustment, not software changes), and consolidation of overlapping contract entitlements into a single, clean licence position.

Tier 2 — Administrative changes with operations sign-off: Actions that modify user access or licence assignments but do not change system functionality. This included Maximo user deactivation for confirmed inactive users (with operations team validation that each user was genuinely no longer needed), Maximo user tier reclassification from full Authorised User to limited-access, and Tivoli agent removal from decommissioned servers.

Tier 3 — System changes requiring plant coordination: Actions that involve modifying, migrating, or decommissioning IBM software in the production environment. This included DB2 instance decommissioning for retired applications (requiring database migration confirmation and data archival sign-off) and Tivoli Workload Scheduler migration to alternative scheduler (requiring job schedule validation and parallel running period).

Maximo Optimisation — The Largest Savings Component

The Maximo user cleanup was executed in close coordination with KNPC's plant operations management. Each inactive user was verified through a three-step process: HR records confirming the employee had left, retired, or transferred; plant operations confirming no operational dependency; and IT security confirming the account could be deactivated. For tier reclassification, the operations team reviewed each candidate to confirm that read-only access was sufficient for their role — ensuring that maintenance planners, supervisors, and inspectors retained the access levels their safety responsibilities required.

Phase 4: Governance and Renewal Strategy

The final phase established governance controls tailored to KNPC's operational environment — ensuring savings were sustained and that IBM licensing remained aligned with refinery operations as the business evolved.

Capital Project Licence Integration

The primary root cause of KNPC's over-licensing was capital project-driven procurement — each refinery expansion or upgrade procured IBM licences independently without checking existing entitlements. The governance framework introduced a mandatory licence check for every capital project involving IBM software: before any new IBM purchase is authorised, the project team must confirm with the central IT asset management function that existing entitlements do not already cover the requirement. This single control eliminates the duplicative purchasing pattern that had accumulated over 15 years.

Maximo User Lifecycle Management

Maximo user licences are now integrated with HR and identity management systems: when an employee leaves, retires, or transfers to a non-Maximo role, their Maximo Authorised User licence is automatically flagged for deactivation at the next quarterly review. New Maximo users are classified into the correct licence tier at provisioning — preventing the default of assigning everyone a full Authorised User licence.

Renewal Negotiation Leverage

The optimised, documented licence position gave KNPC significantly improved negotiating leverage for IBM renewals. With a verified entitlement register and documented usage data, KNPC's procurement team could approach renewals with clear data on what was needed — rather than accepting IBM's renewal proposal at face value. The advisory team provided renewal benchmarking data and negotiation strategy for KNPC's next renewal cycle, targeting additional savings through improved renewal terms based on the reduced scope.

Results Summary and Strategic Impact

The assessment delivered clear results across cost, compliance, and operational governance — establishing KNPC as a model for IBM licence management in the Gulf Cooperation Council (GCC) oil and gas sector.

Key Lessons: IBM Licensing in Oil and Gas and Industrial Environments

KNPC's experience distils lessons applicable to any oil and gas company, refinery operator, or industrial enterprise with significant IBM Maximo and middleware deployments.

Wider Context: IBM Licensing Optimisation Results Across Industries

KNPC's $1.3M optimisation adds to a consistent pattern of IBM licensing savings across industries and geographies — demonstrating that proactive assessment reliably uncovers significant waste in IBM estates of all sizes.

The pattern is consistent: large IBM estates contain 15 to 40% recoverable waste, whether in financial services, technology, telecommunications, or oil and gas. KNPC's engagement demonstrates that even mid-sized IBM estates ($3 to $10M annual spend) in industrial environments carry significant optimisation potential — particularly where Maximo is the dominant product and capital project procurement has driven licence accumulation over many years.

Action Plan: IBM Licensing Optimisation for Oil and Gas Companies

Whether you operate refineries, petrochemical plants, upstream production, or midstream pipelines, here is the action plan that delivers consistent results for oil and gas IBM licensing optimisation.

Frequently Asked Questions