IBM Maximo and Industry Solution Licensing

PVU (Processor Value Unit) Licensing

PVU is a unit assigned by IBM to each processor core based on hardware performance. Maximo, TRIRIGA, and Sterling can all be licensed by purchasing PVUs to cover server processing capacity. This model is attractive for deployments with high or fluctuating user counts, as costs are tied to hardware rather than individual logins. However, PVU licensing demands careful capacity tracking: if you add CPU cores or upgrade processors, your PVU entitlement must be adjusted. IBM requires ILMT (IBM Licence Metric Tool) for sub-capacity licensing in virtualised environments. Sterling often uses PVU licensing because it handles backend processes where cost correlates with processing power. For a deeper look at PVU mechanics, see our guide on navigating IBM VPC licensing complexities.

Authorised User (Named User) Licensing

An Authorised User licence grants access to a specific person regardless of how often they use the system. This model fits well when you have a known set of regular users, for example a maintenance team of 50 who regularly use Maximo. Each distinct person requires their own licence. It provides predictable per-user costs but can become expensive if user counts grow rapidly.

Concurrent User Licensing

Concurrent licensing allows a pool of users to share licences: a licence is consumed only when a user is actively logged in. Example: 30 maintenance technicians on different shifts might share 10 concurrent licences if at most 10 are online simultaneously. Ideal for shift workers or global teams across time zones. However, concurrent licences require monitoring peak usage, as exceeding the licensed number creates a compliance issue.

IBM’s industry solutions built on Maximo (Maximo for Oil & Gas, Maximo for Utilities, and others) and related platforms like TRIRIGA generally follow similar metrics with variations. Purchasing an industry solution licence often includes the base platform entitlement. However, if a user accesses multiple IBM solutions, separate licences may be required for each. Confirm whether combined licensing agreements (such as an ELA) might simplify management across multiple IBM products. For broader context on IBM’s evolving licensing strategy, see our playbook on IBM’s shift to subscription and SaaS.

IBM Maximo offers a tiered structure of user licences to fit different usage levels. Not every user needs a full-power (and high-cost) licence. The common types allow CIOs to mix and match according to user roles.

Conduct an analysis of Maximo user accounts and actual usage patterns. Organisations often find that users with expensive authorised licences only ever use a couple of modules. Those could potentially be downgraded to limited licences. Regularly review new user requests to assign the minimum necessary licence type. IBM’s Maximo allows administrators to assign user types in the system. Maintain this diligently and audit periodically. For strategies on reducing IBM shelfware across your estate, see our IBM cost optimisation and shelfware reduction playbook.

Token Licensing Concepts

Token licensing is a consumption-based approach: you purchase a pool of licence tokens (“credits”) dynamically allocated to different products or users as needed. Instead of buying fixed user or PVU licences, an organisation buys a block of tokens. Each active user or module usage consumes a certain number from the pool. The flexibility lies in reassigning tokens: if user counts drop, those tokens can be used elsewhere, even for other IBM software participating in the token programme.

When Tokens Make Sense

Token-based licensing is advantageous if usage patterns are highly variable or you utilise multiple IBM products. Example: a company using Maximo Asset Management, Maximo for Transportation, and TRIRIGA. With traditional licensing, separate entitlements are needed for each. With a token model, a shared pool covers all, allocating tokens to whichever product is in use at a given time. This reduces total licences needed if systems are not all at peak simultaneously. IBM’s token licensing is often time-bound and requires running a Licence Server (for example IBM Rational Licence Key Server). For context on how IBM’s Cloud Paks relate to token models, see our overview of IBM Cloud Paks and VPC licensing.

Maximo Application Suite (MAS) and AppPoints

IBM’s strategy is moving toward unified licensing. The Maximo Application Suite (MAS) uses a form of token licensing called “AppPoints”. You purchase a quantity of AppPoints consumed by various applications (Maximo Manage, Monitor, Health, Predict) based on usage. This allows fluid use of different capabilities without separate licences per module. New deployments might consider MAS AppPoints from the start; existing Maximo 7.6 users can migrate if value is demonstrated. Note: IBM’s token model for Maximo 7.6.x cannot be mixed with regular licences on the same instance. You must choose one method.

Complex Environments, Complex Licensing

Many enterprises heavily customise Maximo or integrate it with ERP, supply chain, and mobile applications. Customisations and integrations complicate licence tracking because they extend how the software is used. A heavily customised Maximo may have additional modules or screens embedded into other workflows. An integration (for example Maximo linked with SAP or a mobile workforce app) might use a single system account to handle many behind-the-scenes transactions. That integration account might require an authorised user licence if it makes calls equivalent to a user’s actions.

Licence Tracking Tools and Techniques

In Maximo, IBM provides the Licence Usage Monitor application (introduced in v7.6.0.6). It tracks the number of users per licence type and reports on usage vs entitlements. Ensure this is enabled in production. For PVU-based licences, deploy ILMT on all relevant servers. ILMT scans and calculates PVU consumption in virtualised environments, critical for sub-capacity compliance. Ensure ILMT reports are reviewed quarterly and retained. IBM audits often request 2 years of ILMT data.

Customised Functionality and Licence Implications

When developing custom features, always consider the licensing impact during design review. Check if a custom Maximo module falls under existing licences or inadvertently triggers an add-on licence. A common oversight: using a Maximo feature that was not originally purchased, for example using Maximo Scheduler (an add-on) without that licence. Regularly audit the system’s modules and features in use and cross-check with entitlements. For strategies on managing licensing during corporate restructuring, see our guide on managing IBM licensing in mergers, acquisitions, and divestitures.

Integrated Systems and User Counts (Multiplexing)

If Maximo integrates with external applications (for example a web portal submitting requests into Maximo), be clear about how external users are counted. IBM’s rules can be strict about “multiplexing”, where many users funnel through one account. IBM states that if an external system enables multiple individuals to use IBM software functionality, each individual might require a licence. Document such integrations and discuss with IBM if uncertain. Better to clarify than be surprised in an audit.

Environment Management

Customised deployments often span multiple environments (dev, test, training, production). IBM typically allows non-production environments to be covered under production licences at no additional cost, provided they are used solely for testing and QA. Keep non-prod systems properly tagged and separated to avoid being counted incorrectly. If you clone production data for testing, ensure licence monitoring tools do not double-count users or PVUs.

IBM Audits: An Inevitable Event

IBM conducts regular licence compliance audits. High-value enterprise systems like Maximo, TRIRIGA, and Sterling are frequent targets because non-compliance can result in significant licence revenue for IBM. CIOs should assume an audit will happen and prepare continuously. Preparation avoids financial penalties and reduces disruption when an audit is requested.

Know Your Entitlements

Keep a Licence Entitlement Register: an up-to-date inventory of all IBM software entitlements including licence certificate details, metrics (for example 100 Authorised Users for Maximo, 500 PVUs for WebSphere), purchase dates, and current support status. Track any changes, transfers, or special terms granted in writing. In an audit, you will be asked to provide proof of entitlements; having them organised saves time and strengthens your position.

Continuous Compliance Monitoring

Adopt continuous monitoring rather than one-time true-ups. Track licence consumption (user counts, PVU usage) month-by-month. If you exceed entitlements, catch it early: purchase additional licences or scale back usage before an official audit flags the issue. Integrate licence compliance into IT operational dashboards and quarterly governance meetings.

Audit Simulation (Mock Audits)

Periodically conduct internal “mock audits”: gather user lists, pull ILMT reports, verify deployments against entitlements. This often reveals dormant accounts (former employees still enabled, counting against licences) or overlooked servers. If issues are found, remediate immediately and document the fix. It is far better to discover these yourself than have IBM’s auditors do so. For comprehensive audit defence strategies, see our IBM audit defence service.

Key Audit Areas for Maximo and Industry Solutions

IBM auditors typically scrutinise: User-based: list of all user accounts with assigned licence type vs purchase records; inactive or service accounts; misclassified users (using more modules than their licence allows). PVU-based: deployed environment’s CPU configuration and ILMT reports for sub-capacity claims. If ILMT is not running correctly, IBM may assume full-capacity usage, significantly inflating requirements. Add-ons: verify enabled industry modules or add-ons have corresponding entitlements.

During an Audit

When an official audit notice arrives, engage stakeholders immediately. Involve legal and procurement to review audit scope and communications. Share data in a controlled manner: provide what is asked, nothing more, and ensure accuracy. Designate a single point of contact (IT asset manager) to coordinate responses. Because you have prepared, this should be a matter of pulling existing reports and documentation rather than a frantic scramble.