IBM Licensing Models: Maximo, TRIRIGA, Sterling
📐 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 — 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.
👤 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 — exceeding the licensed number creates a compliance issue.
📚 Related Reading
CIO Recommendations — Licensing Basics
Map Products to Metrics
Identify the licensing model used by each IBM system in your portfolio (PVU, authorised user, concurrent user). This clarity helps align management efforts and toolsets — e.g. ILMT for PVU tracking, Licence Usage Monitor for user-based products.
Choose the Right Model
When procuring or renewing, evaluate whether PVU-based or user-based licensing is more cost-effective. Consider user count stability, growth projections, and infrastructure changes. A deployment with thousands of occasional users may be cheaper on PVU; a small fixed team is cheaper per-user.
Educate Stakeholders
Ensure IT operations and asset management teams understand the licensing terms for each system. Misunderstanding metrics can lead to inadvertent compliance breaches — and expensive audit findings.
Leverage IBM Enterprise Agreements
If you have multiple IBM industry solutions, explore enterprise agreements or bundled licensing options. Engaging IBM about flexible licensing across products can yield cost savings or simplified terms.
Need help choosing the right IBM licensing model?
IBM Licensing Assessment →Optimising User Licence Types in Maximo
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 — with specific access rights and cost — allow CIOs to mix and match according to user roles:
🔷 Authorised User (Full)
Full-access licence. Can use all Maximo modules and functionality. Assign to power users: system administrators, asset managers, and others who need comprehensive access. Most expensive per user — only grant where broad access is essential.
🔶 Limited Use Authorised User
Cost-reduced licence limited to a maximum of 3 modules (e.g. work orders, assets, inventory). Blocked from core administrative modules (system configuration, security). Ideal for operational staff in a defined area. IBM requires a ratio of full to limited licences — historically at least 1 Full for every 3 Limited. Significantly lower cost than full authorised user.
📄 Express User
Lighter user type for read-only, approval, and review access. Can run/view reports, read records, change status, and approve work orders or POs. Generally cannot create new records (except limited updates to assigned items). IBM often allows up to 25 Express users per 1 Authorised User. Priced much lower — great for managers and supervisors who need oversight but aren't daily hands-on users.
✅ Self-Service User
IBM grants unlimited self-service usage with at least one full licence in place. These users can submit service requests, initiate help tickets, check status, or create simple requisitions. Capabilities strictly limited to basic requests and views. No licence cost. Anyone who only needs to file a request (e.g. report maintenance issue) should be categorised here rather than consuming a paid licence.
| Licence Type | Access Level | Module Limit | Typical Ratio | Relative Cost |
|---|---|---|---|---|
| Authorised (Full) | All modules, full CRUD | Unlimited | Baseline | $$$$ |
| Limited Use | Defined subset | Max 3 modules | 3:1 (Limited:Full) | $$ |
| Express | Read, approve, status | View/approve only | 25:1 (Express:Full) | $ |
| Self-Service | Submit requests, check status | Self-service only | Unlimited (with 1 Full) | Free |
CIO Recommendations — User Licence Optimisation
Inventory and Validate User Access
Regularly review all Maximo user accounts. Categorise by licence type and validate that business role matches licence capabilities. Flag any misalignment immediately.
Run Usage Reports to Identify Downgrades
Use Maximo's Licence Usage Monitor to identify users who could be downgraded to cheaper licence types without impacting work. Also flag limited users showing access attempts beyond their allowance — they may need an upgrade.
Enforce Provisioning Policies
Create a provisioning checklist that assigns the minimum necessary licence type to each new user. Default most users to limited or express unless a strong case for full access is approved by management.
Communicate Cost Differences
Educate department heads on licence types so they request the correct access. Transparency on cost differences (full vs limited vs express) encourages cooperation in controlling licence expenses.
Leveraging Token-Based Licensing in IBM Environments
🎫 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 aren't all at peak simultaneously. IBM's token licensing is often time-bound and requires running a Licence Server (e.g. IBM Rational Licence Key Server).
📱 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.
CIO Recommendations — Token Licensing
Evaluate Fit for Tokens
Analyse usage variability across multiple IBM products. If you have multiple solutions or highly fluctuating user counts, ask IBM about token-based options or Maximo Application Suite. The flexibility could save costs if managed well.
Pilot Before Full Commitment
Run a proof of concept with token licensing for a subset of users or non-production environment. This reveals practical consumption rates and management overhead before a full switch.
Implement Monitoring Tools
Use IBM's Rational Licence Key Server reports or third-party tools to track token consumption. Set thresholds to alert the IT team when usage is high, allowing proactive purchasing or usage curtailment.
Stay Current on IBM Offerings
Token models evolve constantly. Maintain communication with your IBM account manager or licensing partner about the latest options — Cloud Paks, AppPoints, MAS — that may benefit your organisation.
Considering a migration to Maximo Application Suite?
IBM Negotiations Service →Managing Licensing in Customised or Integrated Deployments
🔧 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 (e.g. 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) — 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 wasn't originally purchased — e.g. using Maximo Scheduler (an add-on) without that licence. Regularly audit the system's modules and features in use and cross-check with entitlements.
🔗 Integrated Systems and User Counts (Multiplexing)
If Maximo integrates with external applications (e.g. a web portal submitting requests into Maximo), be clear about how external users are counted. IBM's rules can be strict about "multiplexing" — many users funnelling 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 licence at no additional cost, provided they are used solely for testing/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 don't double-count users or PVUs.
CIO Recommendations — Customised Environments
Embed Licence Checks in Change Management
Whenever a new customisation or integration is proposed, require a licensing impact assessment as part of the project checklist. This prevents surprises where a technical enhancement leads to compliance issues.
Use Automation for Tracking
Configure automated reports from Maximo's Licence Monitor and ILMT. Receive reports regularly and review anomalies — sudden user count or PVU increases after a new integration should be investigated immediately.
Document All Integrations
Maintain up-to-date documentation of which external systems connect to Maximo/TRIRIGA/Sterling. For each, note data flows and whether it introduces indirect users. Use this to determine if additional licences or a different model is warranted.
Conduct Regular Internal Audits
Don't wait for IBM. Periodically engage a third-party licensing specialist to review deployments and identify areas of non-compliance proactively — corrections on your own terms are always cheaper than audit findings.
Preparing for IBM Licence Audits
🔍 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: licence certificate details, metrics (e.g. 100 Authorised Users for Maximo, 500 PVUs for WebSphere), purchase dates, and current support status. Track any changes — transfers, special terms granted in writing. In an audit, you'll 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's far better to discover these yourself than have IBM's auditors do so.
🔎 Key Audit Areas for Maximo & 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've prepared, this should be a matter of pulling existing reports and documentation rather than a frantic scramble.
CIO Recommendations — Audit Readiness
Maintain Audit Readiness Documentation
Keep an easily accessible repository of all IBM licence entitlements and up-to-date usage reports. Update whenever changes occur (new purchases, user count changes, environment changes).
Run ILMT and Archive Reports
Ensure ILMT is running for all applicable IBM software. Archive quarterly reports — they are your evidence for PVU sub-capacity compliance. Missing reports can result in full-capacity licence claims by IBM.
Clean Up User Accounts Regularly
Implement an offboarding process that includes deactivating Maximo/TRIRIGA user accounts when staff leave or change roles. Fewer dormant accounts means a clearer compliance position and reduced licence costs.
Engage IBM Proactively
If you anticipate changes impacting licensing (merger increasing users, cloud migration), notify IBM and discuss implications. Being proactive can lead to more favourable terms and prevents adversarial audit findings.
Budget for True-Ups
Set aside a reserve budget for licensing updates. Despite best efforts, internal reviews may discover under-licensing. A reserve budget ensures compliance can be restored swiftly without operational impact.
IBM Maximo and industry solution licensing requires the same strategic attention as any major enterprise platform. The combination of PVU and user-based metrics, tiered user types, evolving token models, complex integrations, and the certainty of IBM audits creates a landscape where proactive management is the only viable strategy. CIOs who invest in understanding their licensing position, optimising user licence assignments, deploying the right monitoring tools, and preparing continuously for audits will control costs, avoid compliance pitfalls, and maintain their negotiating leverage with IBM.
📂 IBM Case Studies
🔧 IBM Advisory Services
📄 White Papers & Resources
Need Help with IBM Maximo or Industry Solution Licensing?
Whether you need a comprehensive Maximo licensing assessment, help optimising user licence assignments to reduce costs, guidance on migrating to Maximo Application Suite and AppPoints, audit preparation or defence, or contract negotiation support for IBM ELA renewals — our independent IBM licensing specialists have the deep expertise to deliver results.
💡 Download our white papers on IBM licence optimisation strategies
View White Papers →