CIO Playbook for IBM Maximo and Industry Solution Licensing

The Maximo Licensing Landscape

IBM Maximo has been the dominant enterprise asset management (EAM) platform for asset-intensive industries for more than three decades. Utilities managing power grid infrastructure, oil and gas operators controlling pipeline assets, airlines tracking aircraft maintenance, and transit authorities managing rolling stock all rely on Maximo as their operational backbone. That installed base gives IBM extraordinary pricing leverage — and the shift to the Maximo Application Suite (MAS) has restructured the commercial terms in IBM's favour.

The licensing transformation from legacy Maximo to MAS is not a simple product upgrade. It is a fundamental change in how entitlements are structured, how costs accumulate over time, and how IBM monetises the platform going forward. CIOs who treat MAS migration as a technical decision rather than a commercial negotiation risk locking their organisations into structures that increase total cost by 40 to 80 percent over a five-year horizon.

This playbook addresses every dimension of the Maximo licensing equation: legacy models, the AppPoints currency, Industry Solution premiums, ILMT compliance obligations, migration traps, and the negotiation strategies that deliver materially better commercial outcomes. The analysis draws on more than 120 Maximo licensing assessments across asset-intensive sectors in North America, Europe, and the Middle East.

Legacy Maximo: The User-Based Foundation

Understanding where organisations currently stand on licensing requires a precise grasp of the legacy Maximo licensing structure that most enterprises have operated under since the mid-2000s. IBM Maximo's commercial terms before MAS were organised around three primary dimensions: user type, module, and processor-based components for underlying middleware.

User Licence Types in Legacy Maximo

Legacy Maximo offered four primary user licence categories, each corresponding to a different level of application access and carrying a materially different price point:

Authorised User licences grant full access to all Maximo applications and modules the organisation has licensed. This is the highest-cost user type, typically priced between $1,800 and $3,500 per named user depending on negotiation history, contract vintage, and volume. Maintenance planners, reliability engineers, and procurement personnel who live in Maximo daily should hold Authorised licences. In practice, many organisations have over-assigned Authorised licences to occasional users who require only Limited access, creating a structural overpayment that persists until renegotiated.

Limited Use licences restrict access to specific modules agreed at contract time — typically three modules excluding Administrative applications. They carry a price roughly 40 to 50 percent below the Authorised rate and suit supervisors, department managers, and field supervisors who need work order approval or asset viewing capabilities without full platform access.

Express licences provide access to a constrained subset of Maximo functionality for self-service workflows — primarily work request submission and status tracking. These are appropriate for the broad population of operational staff who initiate maintenance requests but do not manage them. Express licences are typically priced at 15 to 25 percent of the Authorised rate.

Self-Service licences cover the lowest tier of access, typically restricted to raising service requests and viewing status. They are appropriate for end-user populations and contractors in portals, and are priced at or below 10 percent of the Authorised rate.

Module and Industry Solution Add-Ons

Base Maximo — which IBM calls Maximo Asset Management or Maximo Manage in MAS — covers the core work order management, asset registry, purchasing, and inventory functions. Industry Solutions are separately licensed add-on modules that extend Maximo with vertical-specific functionality. In the legacy model, Industry Solutions were licensed as standalone products purchased against the same user count as base Maximo.

The six legacy Industry Solutions correspond directly to the six verticals IBM continues to target in MAS: Oil and Gas (Maximo for Oil and Gas), Utilities (Maximo for Utilities), Transportation (Maximo for Transportation), Aviation (Maximo for Aviation Maintenance), Nuclear Power (Maximo for Nuclear Power), and Civil Infrastructure (Maximo for Civil Infrastructure). Each carries its own licence fee on top of the base Maximo entitlement, typically adding 25 to 60 percent to per-user costs depending on the vertical and negotiating leverage applied.

Processor-Based and S&S Fees

Maximo itself is licensed on a per-user basis, but the IBM middleware on which it ran — WebSphere Application Server, IBM Db2, and in some deployments IBM MQ — was historically licensed on a Processor Value Unit (PVU) basis, requiring ILMT tracking. Organisations running Maximo in virtualised environments on VMware, Hyper-V, or IBM PowerVM needed correct ILMT configuration to claim sub-capacity PVU entitlements rather than paying for full server capacity.

Software and Support (S&S) fees — IBM's annual maintenance charge — were standardised at 20 percent of the original licence value. For a large utility that purchased $2 million of Maximo licences in 2012, the annual S&S fee has been running at $400,000 per year for over a decade, totalling $5.6 million in support payments on a licence that may no longer reflect actual operational needs.

Maximo Application Suite: The AppPoints Revolution

IBM launched the Maximo Application Suite in 2020 as its strategic container-based successor to legacy Maximo. MAS unifies what were previously separate products — Maximo Asset Management, Maximo Monitor, Maximo Predict, Maximo Visual Inspection, Maximo Health, Maximo Assist, and the six Industry Solutions — under a single entitlement and a single licensing currency called AppPoints.

What AppPoints Are

An AppPoint is a unit of licensing currency within the MAS ecosystem. Organisations purchase a pool of AppPoints — think of it as a rechargeable credits balance — and draw from that pool to provision users, activate applications, and deploy environments. IBM describes this as a "flexible, concurrent consumption model." Understanding the mechanics in precise commercial terms is essential before signing any MAS contract.

All AppPoints operate on a concurrent model. When a user logs into a MAS application, the required number of AppPoints for their entitlement level are drawn from the pool. When the user logs out, those AppPoints are released back to the pool. This concurrent structure is genuinely different from legacy named-user licensing, where licences were assigned per person regardless of simultaneous usage.

The concurrent nature of AppPoints can work in an organisation's favour — a workforce of 500 Maximo users who do not all work simultaneously may need only 200 to 300 AppPoints at peak rather than 500 named licences. However, IBM's AppPoint pricing is set to recover equivalent revenue to legacy licensing, and the concurrent advantage is often smaller in practice than IBM's sales materials imply, particularly in organisations running 24/7 operations where simultaneous users at peak are close to total user population.

AppPoint Entitlement Tiers

Within MAS, each user is assigned one of four entitlement levels, each consuming a different number of AppPoints per concurrent session:

Premium entitlement provides unrestricted access to all MAS applications the organisation has activated, including AI-powered capabilities (Predict, Health, Visual Inspection) and all Industry Solution modules. Premium users consume the highest number of AppPoints per session. This tier equates approximately to legacy Authorised User licences, with the important addition that Industry Solution access is now embedded in the Premium tier rather than separately licensed.

Base entitlement covers the core Maximo Manage (asset and work management) application suite, without access to AI and predictive capabilities. This tier equates approximately to legacy Limited Use licences. Most organisations find that 60 to 75 percent of their Maximo population needs only Base entitlement.

Limited entitlement provides restricted access for self-service workflows — work request submission, status viewing, and approval workflows. This tier maps to legacy Express and Self-Service licences combined.

None is the unentitled state for users provisioned in the directory but not yet consuming AppPoints. IBM does not charge for None-tier users until they are activated to any consuming tier.

Application-Level AppPoints Reservations

Beyond user entitlements, certain MAS applications and add-ons require an upfront reservation of AppPoints at the time of application deployment, independent of user activity. Maximo Visual Inspection, for example, requires a fixed AppPoints reservation to run the image recognition inference engine regardless of whether any user is actively processing images at that moment. Maximo Predict similarly requires computational resource reservations for AI model execution.

This application-level reservation model is a material departure from legacy licensing. Organisations deploying MAS with AI capabilities must budget for both the user entitlement pool and the static application reservations, which can account for 15 to 30 percent of total AppPoints purchased. IBM's pre-sales AppPoints sizing models frequently underestimate application reservations, leading to AppPoints shortfalls within 6 to 12 months of go-live.

Deployment Options: Client-Managed vs SaaS

MAS is available in two deployment configurations. Client-managed (on-premises or private cloud) gives the organisation full control over infrastructure and deployment cadence, with IBM licensing provided as a software subscription. SaaS (IBM Maximo Application Suite as a Service) has IBM manage the infrastructure, platform, and upgrade cycle, with the organisation consuming the service on a per-AppPoint subscription basis.

The licensing cost differential between client-managed and SaaS is less significant than most CIOs expect — typically 10 to 20 percent premium for SaaS. The more material cost difference lies in infrastructure: client-managed MAS requires Red Hat OpenShift Container Platform, which carries its own subscription cost ($5,000 to $15,000 per node per year depending on tier and negotiation). Organisations comparing client-managed MAS against SaaS MAS must include OpenShift in the total cost of ownership comparison, not just the MAS AppPoints licence.

Industry Solutions: The Premium AppPoints Layer

Industry Solutions represent one of the most commercially significant — and least transparently communicated — aspects of MAS licensing for asset-intensive organisations. Understanding how Industry Solutions consume AppPoints, and how IBM prices the premium access they require, is critical for any CIO in an affected vertical.

The Six Industry Verticals

IBM maintains six dedicated Industry Solution modules within MAS, each extending the core Maximo Manage functionality with vertical-specific data models, regulatory compliance tools, and operational workflows:

Maximo for Oil and Gas adds regulatory permit management, safe work authorisation, isolation management, and pipeline integrity workflows optimised for upstream, midstream, and downstream operations. It is the most widely deployed Industry Solution by contract value, with customers including major integrated oil companies and national oil companies.

Maximo for Utilities provides tailored tools for transmission, distribution, power generation, water and wastewater treatment, vehicle fleet, and facilities management within the regulatory frameworks governing utility operations. It includes network asset management capabilities specific to grid operations and utility regulatory reporting.

Maximo for Transportation addresses recall and upgrade campaign management, warranty cost recovery, industry-specific service codes, and depot fuel tank management for rail, road, and multimodal transportation operators. It includes fleet lifecycle management tools not available in base Maximo Manage.

Maximo for Aviation is the most compliance-intensive of the Industry Solutions, incorporating airworthiness directive management, engineering order processing, parts traceability, and regulatory compliance reporting for Part 145 Maintenance, Repair and Overhaul operations and airline technical operations.

Maximo for Nuclear Power provides the most restrictive access controls, audit trail depth, and procedural workflow enforcement of any Industry Solution, aligned with NRC and international nuclear regulatory requirements for corrective action programmes, maintenance rule compliance, and technical specifications management.

Maximo for Civil Infrastructure covers bridge, road, dam, and public infrastructure asset lifecycle management with GIS integration and condition assessment workflows aligned with government infrastructure asset management standards.

How Industry Solutions Inflate AppPoints Costs

In legacy Maximo, Industry Solutions were additive costs stacked on top of base Maximo licensing. In MAS, Industry Solutions are accessible only to users provisioned at the Premium entitlement tier. This structural change has a material impact on total AppPoints cost for organisations whose primary user population needs Industry Solution functionality.

Consider a utilities organisation with 400 Maximo users, 300 of whom are field technicians and supervisors who need Maximo for Utilities functionality for regulatory reporting and distribution network asset management. Under legacy Maximo, these users might have been Licensed Use users for base Maximo plus Maximo for Utilities module licences. Under MAS, every user requiring Industry Solution access must be provisioned at the Premium tier — the most AppPoints-intensive entitlement level.

IBM's internal AppPoints sizing models for Industry Solution-heavy deployments consistently produce AppPoints requirements 40 to 60 percent higher than equivalent legacy named-user deployments. This is not simply an artefact of the pricing model — it reflects the genuine cost of migrating legacy Limited Use users with Industry Solution access to the Premium AppPoints tier.

Multi-Industry Deployments and Double-Counting Risk

Some organisations — particularly diversified utilities, integrated energy companies, and government infrastructure agencies — operate across multiple IBM Industry Solution verticals simultaneously. A power utility with gas distribution assets may need both Maximo for Utilities and Maximo for Oil and Gas. A government infrastructure authority may need Civil Infrastructure and Transportation.

In legacy Maximo, each Industry Solution was a separately licensed product with its own per-user fee, creating a stacking cost for multi-vertical organisations. MAS theoretically addresses this through the unified Premium AppPoints pool — a Premium user has access to all activated Industry Solutions without separate module fees. However, the AppPoints cost of provisioning the entire relevant population at Premium tier is typically higher than the stacked legacy module costs, particularly when combined with the OpenShift infrastructure costs not present in legacy deployments.

ILMT and Sub-Capacity Compliance in Maximo Environments

While the shift to MAS and AppPoints fundamentally changes how Maximo itself is licensed, organisations running Maximo in virtualised environments retain sub-capacity compliance obligations for IBM middleware components — and these obligations extend to any IBM software in the MAS technology stack that retains PVU or VPC-based licensing.

Why ILMT Remains Critical for Maximo Organisations

IBM's ILMT (IBM License Metric Tool) is mandatory for any organisation claiming sub-capacity licensing rights under PVU or VPC metrics. Sub-capacity licensing allows organisations to licence IBM software based on the peak usage within virtual machines rather than the full physical server capacity. For a large enterprise running IBM software on a 96-core physical server but allocating only 16 vCPUs to IBM workloads, sub-capacity licensing can reduce the PVU or VPC requirement by 80 percent or more.

The consequence of not maintaining correct ILMT deployment is severe: IBM treats the entire physical server as fully licensed, reverting to full capacity pricing. In an IBM Software Survey (IBM's term for a software audit), ILMT data gaps automatically trigger full-capacity licence calculations for the periods where data is absent. IBM requires organisations to retain 90-day ILMT reports and maintain a two-year history of continuous ILMT data. Gaps in that history are not treated charitably.

Common ILMT Configuration Failures in Maximo Environments

Maximo environments are particularly prone to ILMT configuration failures because Maximo deployments tend to grow organically over time, with new application servers, database servers, and middleware nodes added without corresponding ILMT agent updates. The most common failures observed in Maximo-related IBM audits include:

Agent deployment gaps: ILMT agents are installed on the servers present when ILMT was initially configured, but new VMs and physical hosts added subsequently are not captured. IBM's Software Survey will identify servers running IBM software not covered by ILMT reports — and charge full capacity for those servers retroactively.

Stale ILMT version: IBM requires that ILMT be kept current. Running an outdated ILMT version that does not support the virtualisation platforms in use (particularly newer VMware vSphere releases or IBM PowerVM logical partitions) can invalidate sub-capacity claims for the environments using those platforms.

LPAR boundary misconfiguration: IBM's sub-capacity rules for IBM Power Systems LPAR environments have specific requirements for how maximum LPAR sizes are set and enforced. Organisations that dynamically resize Power LPARs without ILMT tracking those maximum sizes lose sub-capacity rights for those partitions.

Report generation gaps: IBM requires ILMT reports to be generated and retained at least every 90 days. Organisations that automate ILMT but fail to verify that reports are being generated and stored correctly have discovered, only during audit, that their automated process silently failed months earlier.

The financial exposure from ILMT non-compliance in a mid-sized Maximo environment is substantial. Non-compliance reaching full-capacity pricing can result in back charges of $500,000 to $5 million or more, depending on server count, IBM software stack, and the period of the gap. IBM audit resolution almost always includes two years of back maintenance fees in addition to the compliance true-up.

The Legacy-to-MAS Migration Trap

The commercial mechanics of migrating from legacy Maximo to MAS are where most CIOs encounter their largest and least expected cost surprises. IBM's migration programme has been carefully designed to convert an installed base paying per-user S&S fees into an installed base paying recurring AppPoints subscription fees — at a higher long-term cost in most cases.

The Structural Cost Escalation Pattern

IBM's migration offer typically presents a credit structure: the remaining value of existing on-premises licence S&S payments is credited towards the first-year MAS AppPoints subscription. IBM frames this as "protecting your investment." The credit may make year one of MAS appear cost-neutral or modestly lower than the legacy S&S run rate. The trap lies in years two through five.

MAS AppPoints subscriptions are structured as annual or multi-year subscriptions with built-in escalation rates, typically 3 to 7 percent annually. Legacy Maximo S&S fees were contractually stable — the 20 percent of original licence value was a fixed calculation that remained constant regardless of how old the contract was. MAS subscriptions grow every year. Over a five-year term, an organisation that accepted a seemingly neutral migration in year one will typically be paying 30 to 40 percent more than their legacy S&S run rate by year five.

The Red Hat OpenShift Hidden Cost

Client-managed MAS deployments require Red Hat OpenShift Container Platform as the underlying Kubernetes orchestration layer. IBM acquired Red Hat in 2019, and OpenShift is now a mandatory infrastructure dependency for on-premises MAS. OpenShift is separately licensed from MAS AppPoints, with subscription costs typically ranging from $5,000 to $15,000 per node per year depending on tier (OpenShift Platform Plus, OpenShift Container Platform) and negotiation outcome.

A mid-sized Maximo MAS deployment running five to ten OpenShift worker nodes adds $25,000 to $150,000 per year in infrastructure licensing on top of the MAS AppPoints subscription. IBM's migration cost models presented to customers frequently omit or understate the OpenShift cost, framing it as an "infrastructure decision" separate from the software licensing comparison. CIOs comparing total legacy Maximo costs against MAS costs must include OpenShift in the MAS column.

Migration Credits and Trade-In Programmes

IBM offers formal migration credit programmes for legacy Maximo customers transitioning to MAS. The mechanics vary by contract vintage, remaining S&S value, and commercial relationship, but the core structure involves trading in existing perpetual Maximo licences and applying a credit (typically expressed as a percentage of original licence value) towards the first year of MAS AppPoints subscription.

Migration credits are negotiable, and IBM's initial offer is rarely optimal. Organisations with large perpetual licence bases, long maintenance histories, or strategic importance to IBM's enterprise reference accounts have meaningful leverage. We have seen migration credits ranging from 10 percent to 45 percent of original licence value, with the higher credits available to organisations that negotiate early in IBM's fiscal year (before IBM's internal deadline pressure sets in) and demonstrate credible alternative options.

True-down provisions — contractual rights to reduce AppPoints subscription quantities at annual renewal without penalty — are critical for any multi-year MAS deal. IBM's default position is that AppPoints subscriptions are fixed commitments for the term. Without explicit true-down language, an organisation that right-sizes AppPoints conservatively in year one has no mechanism to reduce commitment if usage comes in below projection. Conversely, organisations that over-buy to be safe face paying for unused AppPoints with no contractual path to reduction.

End-of-Support Pressure and IBM's Timeline

IBM has communicated end-of-support dates for legacy Maximo versions to create urgency around MAS migration. Maximo Asset Management 7.6.1.x reached standard support end in September 2023, with extended support available through 2025 at additional cost. This end-of-support timeline is a negotiating tool IBM uses to accelerate migration decisions — organisations that feel pressure to upgrade before support ends are less likely to extract optimal commercial terms.

CIOs should treat IBM's end-of-support timeline as a commercial negotiating variable, not an immovable technical constraint. IBM has historically extended support for strategic accounts when presented with a credible migration timeline and a commercially competitive offer. The question is not whether you must migrate — you do, eventually — but whether you migrate on IBM's timeline or yours.

Negotiation Strategies for CIOs

IBM Maximo negotiations differ structurally from many enterprise software renewals because IBM occupies a unique position: it sells both the application and the infrastructure it runs on, both the platform and the professional services to implement it, and both the current version and the migration path to the next. Understanding IBM's commercial architecture is prerequisite to developing effective negotiation strategy.

Establish Your Leverage Before You Need It

The single most important preparation for any Maximo commercial negotiation is establishing credible alternatives before IBM believes you need them. For most organisations, the realistic alternative to Maximo is one of four options: SAP PM/EAM (Plant Maintenance embedded in S/4HANA), Infor EAM (now Infor CloudSuite Asset Management), IBM's own MAS SaaS (as leverage against client-managed pricing), or a fit-for-purpose alternative specific to your vertical (IFS in aviation, Ellipse in utilities, SmartPlant in oil and gas).

None of these alternatives are trivial to implement. Maximo's depth of Industry Solution functionality, its installed regulatory compliance tooling, and the organisational investment in Maximo-centric workflows make genuine platform replacement a multi-year commitment. IBM knows this. But IBM also knows that the threat of replacement, supported by visible RFP activity and reference checks, changes the commercial dynamic significantly. The goal is not to replace Maximo — it is to negotiate as if you might.

AppPoints Sizing: The Critical Variable

AppPoints sizing is the central commercial variable in any MAS negotiation. IBM's sales team will produce an AppPoints sizing model based on your user count, entitlement tier distribution, and Industry Solution requirements. This model almost always reflects IBM's commercial interests rather than your actual usage requirements. Three strategies improve the outcome:

First, conduct your own usage analysis before engaging IBM. Maximo's built-in License Usage Monitor (available from Maximo 7.6.0.6 onwards) tracks active sessions, user types, and peak concurrent usage. This data is your evidence base for challenging IBM's AppPoints sizing. If IBM sizes for 400 concurrent users and your peak concurrent usage across 400 named users is 180, you have a documented basis for a more conservative AppPoints purchase.

Second, negotiate the concurrent usage rate explicitly. IBM's AppPoints models often assume conservative concurrency ratios. For organisations with clear shift patterns, global follow-the-sun operations, or documented asset-intensive workflows, the concurrency ratio may be significantly lower than IBM's default assumption.

Third, build genuine headroom into your initial purchase, but at a discounted rate. Buying AppPoints headroom at the initial negotiated rate (which should reflect full-volume pricing) is far cheaper than purchasing additional AppPoints later at standard rates when IBM has less incentive to discount.

IBM Fiscal Year Mechanics

IBM's fiscal year ends December 31. The fourth quarter (October through December) is IBM's most aggressive selling period, and the one where IBM has the most flexibility to apply commercial concessions to close deals before year-end. Organisations entering renewal or migration discussions in Q4 with a clear decision timeline can extract materially better terms than those who engage in January when IBM has 12 months of patience.

IBM's sales teams also have internal quarterly quotas. Understanding IBM's specific quarter-end date for your account team and structuring your engagement to close in the final weeks of a strong IBM quarter provides additional leverage beyond the fiscal year mechanics.

Enterprise Licence Agreement Structuring

For organisations with significant IBM footprint beyond Maximo — IBM middleware, IBM Cloud, IBM Security products, or IBM consulting relationships — the MAS negotiation should be explicitly linked to the broader IBM commercial relationship. IBM's ELA (Enterprise Licence Agreement) structure and its Passport Advantage contract framework both provide mechanisms for cross-product bundling that can deliver MAS pricing 20 to 35 percent below standalone MAS rates.

The risk of ELA bundling is reduced negotiating granularity: once Maximo is embedded in a broad IBM ELA, it becomes harder to separate for future competitive analysis. CIOs should structure bundles that preserve the right to exclude Maximo from future ELA renewals if commercial terms diverge from market rates.

Eight Maximo Licensing Mistakes to Avoid

Accepting IBM's AppPoints Sizing Without Challenge: IBM's pre-sales AppPoints models reflect IBM's commercial interests. Always conduct internal usage analysis using Maximo's License Usage Monitor before accepting any AppPoints proposal. Peak concurrent usage in a typical Maximo environment is 40 to 60 percent of total named user population, not the 70 to 80 percent IBM's models typically assume.

Treating MAS Migration as a Technical Decision: The commercial terms of MAS migration have more long-term cost impact than any technical architecture choice. Before engaging IBM's technical pre-sales team, engage your commercial and procurement specialists. The decision to migrate — and the terms under which you migrate — is a strategic commercial decision, not a technical upgrade.

Ignoring OpenShift Costs in the MAS TCO: Client-managed MAS requires Red Hat OpenShift, which is a separate subscription cost not included in MAS AppPoints. Any comparison of legacy Maximo total cost against MAS total cost must include OpenShift in the MAS column. Failure to include OpenShift leads to year-two cost shock when the infrastructure bill arrives.

Locking in Multi-Year MAS Without True-Down Rights: IBM's default MAS contract structure fixes AppPoints subscription quantities for the term. Without explicit true-down rights, you cannot reduce your AppPoints commitment if usage comes in below projection. True-down rights are negotiable — IBM will resist, but will agree with sufficient leverage and advance planning.

Allowing ILMT to Lapse During Migration: The migration from legacy Maximo to MAS does not eliminate sub-capacity compliance obligations for IBM middleware components. ILMT must continue to run through the entire transition period. Organisations that pause ILMT during MAS implementation create unintended compliance gaps that IBM will identify in a subsequent Software Survey.

Migrating All Users to Premium Tier by Default: Not all Maximo users require access to Industry Solutions or AI-powered MAS capabilities. A detailed analysis of actual usage by user role will identify a significant population — often 30 to 50 percent of total users — who need only Base or Limited entitlement. Migrating the entire user base to Premium tier "for flexibility" is IBM's preferred outcome, not yours.

Missing Migration Credit Opportunities: IBM's migration credit programmes have application windows and eligibility requirements. Organisations that allow legacy Maximo contracts to lapse or allow S&S to go delinquent before migrating lose migration credit eligibility. Monitor your contract status and engage IBM on migration credits well before any potential lapse.

Accepting IBM's End-of-Support Timeline as Fixed: IBM's end-of-support dates are commercial pressure tools, not immovable technical constraints. Extended support is available at additional cost, and IBM has extended standard support for strategically important accounts when presented with realistic migration plans. Do not allow support timeline pressure to drive an unconditional migration decision.

Seven Priority Recommendations for CIOs

1. Commission an Independent Maximo Licensing Assessment Before Any MAS Engagement: Before IBM presents its MAS migration proposal, obtain an independent assessment of your current licensing position. This should include a reconciliation of actual user counts against contracted entitlements, a review of Industry Solution usage against contracted modules, an ILMT health check for sub-capacity compliance, and a benchmark of your current S&S cost against comparable organisations. This assessment takes four to six weeks and will change the commercial conversation fundamentally.

2. Conduct Detailed AppPoints Modelling Before Accepting IBM's Sizing: Use Maximo's internal License Usage Monitor to extract at least three to six months of peak concurrent usage data across all user types and application modules. Model AppPoints requirements using your actual concurrency profile, not IBM's theoretical maximum. The difference between IBM's model and reality is typically 20 to 40 percent of total AppPoints — translating directly to annual subscription savings.

3. Separate the Industry Solution AppPoints Decision from the Base MAS Decision: If your organisation's Industry Solution user population is smaller than its total Maximo population, negotiate AppPoints tiers explicitly by user role. Not every Maximo user needs Premium AppPoints. Base and Limited tier users should be explicitly sized and priced independently to prevent IBM from applying Premium-tier rates across your entire user base.

4. Audit Your ILMT Configuration Before IBM Raises the Subject: Conduct a proactive ILMT health assessment covering agent deployment completeness, reporting continuity, LPAR configuration, and version currency. Identify and remediate any gaps before they become IBM audit findings. An ILMT gap discovered during an IBM Software Survey is addressed on IBM's terms. An ILMT gap discovered and remediated proactively is addressed on yours.

5. Build Genuine Competitive Tension Before MAS Negotiation: Initiate a structured market assessment of alternative EAM platforms six to twelve months before your MAS negotiation window. SAP EAM, Infor CloudSuite EAM, IFS, and vertical-specific alternatives all have legitimate positions for different organisational profiles. The goal of this assessment is to create documented, credible IBM negotiating pressure — not necessarily to execute a replacement. IBM's commercial response to visible competitive evaluation is materially more favourable than IBM's response to a customer who has communicated unconditional commitment to Maximo.

6. Negotiate True-Down Rights and Annual AppPoints Flexibility as Non-Negotiables: Make true-down rights and annual AppPoints adjustment provisions a condition of any multi-year MAS deal. IBM will propose fixed-term subscriptions. Accept nothing less than the right to reduce AppPoints at annual review by a defined percentage (typically 10 to 20 percent) without penalty. This provision protects against over-sizing and preserves flexibility as your operational requirements evolve.

7. Use Specialist Advisory Support for the Commercial Negotiation: IBM Maximo commercial negotiations involve the intersection of EAM domain knowledge, IBM licensing expertise, sub-capacity compliance obligations, and enterprise commercial negotiation strategy. IBM's account team has all of these capabilities on their side of the table. Equalising that capability asymmetry with specialist independent advisory support — buyer-side only, with no IBM commercial relationship — is the most reliably high-return investment in your Maximo commercial programme.