Stay Informed on IBM Licensing
Join enterprise IT leaders receiving our monthly advisory on IBM licensing changes, audit tactics, and contract negotiation strategies.
01 Understanding Floating (Concurrent User) Licensing
In a floating or concurrent user model, the software is not tied to a specific named user. A set number of licences can be used simultaneously by anyone in the organisation up to the purchased limit at any given time. IBM implements floating licensing via a licence server that tracks current usage, checking out licences when applications launch and returning them when applications close.
| Aspect | Floating (Concurrent) Licence | Named User Licence |
|---|---|---|
| Assignment | Not tied to any individual. Any authorised person can use the software if a slot is available. | Assigned to a specific named individual. Only that person can use the software. |
| Simultaneous use | Limited to purchased pool size (e.g. 10 concurrent users). 11th user blocked until someone exits. | All named users can use simultaneously. No concurrency limit beyond total named licences. |
| Per-licence cost | Higher per licence (reflects shared flexibility). | Lower per licence (fixed to one person). |
| Total cost | Usually far lower. Buy 15 licences for 40 users instead of 40 named. | Must buy one per user regardless of usage frequency. |
| Best for | Large teams with occasional or rotational usage. Engineering, analytics, training environments. | Users who need guaranteed, always-available access. Heavy daily users. |
| Infrastructure | Requires licence server (IBM Licence Key Server, Flexera FlexLM). Must ensure high availability. | No licence server needed. Licence tied to individual or machine. |
02 Token-Based Licensing Explained
Token-based licensing is a flexible model IBM provides for certain product families, notably IBM Rational/Engineering Lifecycle Management, IBM Maximo Application Suite, and some Cloud Paks. Instead of buying X licences of each product, you buy a pool of licence tokens. These tokens act as credits consumed in different quantities by different software products or features.
One Pool, Multiple Products
A token pool covers multiple tools from the same suite. IBM defines how many tokens each product consumes per user session. For example, DOORS might cost 1 token per session while Rhapsody costs 2 tokens. An 80-token pool can run 80 DOORS users, 40 Rhapsody users, or any combination totalling 80 tokens.
Dynamic Allocation
When one product's usage drops, those tokens are immediately available for another product. This prevents unused licences for one product while another is short. Tokens return to the pool when users close applications. They are not permanently consumed.
Breadth Drives Value
If you only use one product heavily, token licensing may be more expensive than direct licensing. But if you have many products with sporadic use, tokens add enormous flexibility. An organisation buying 100 Maximo tokens can use various modules by consuming tokens per module's active users.
03 Benefits of Floating and Token Licences
| Benefit | Floating Licences | Token Licences |
|---|---|---|
| Cost savings | Prevent paying for idle capacity. Buy for peak concurrent usage, not total headcount. | Avoid purchasing separate fixed licences for multiple products, some of which sit unused. |
| Flexibility | Accommodate shifting usage within a team for a single product. | Accommodate shifting usage across different applications in a suite. |
| Simplified management | One pool per product to track. | One pool covering an entire product family. Simplifies compliance tracking. |
| Scalability | Add more licences to pool. Everyone benefits immediately. No named reassignment needed. | Add more tokens. Capacity distributed automatically across all covered products. |
| ELA integration | Can be included in enterprise agreements for team-level flexibility. | IBM sometimes includes token pools in ELAs for cross-product agility and simplified cost distribution. |
04 Challenges and Compliance Considerations
| Challenge | Impact | Mitigation |
|---|---|---|
| Licence server uptime | If the server goes down, users cannot start software. Work stoppages. | Run redundant licence servers or maintain backup licence keys for emergencies. Ensure high availability. |
| Usage tracking | Audits require proof that purchased count matches peak usage. Over-usage blocked in real time but records must be maintained. | Monitor peak usage via licence server logs. Track denials (frequent denials signal need for more licences). Archive logs for audit readiness. |
| Geographic restrictions | Some floating licences constrained by geography or network subnet. Global teams may need separate pools. | Verify licence agreement matches deployment geography. Consider regional pools or follow-the-sun models if permitted. |
| Token conversion rates | IBM defines how many tokens each product consumes. Rates can change with versions or updates. | Always reference the latest IBM token usage table. Monitor for changes at version upgrades that could increase consumption. |
| Higher entry cost | Token packs often have minimum purchase requirements (e.g. 100 tokens). Floating licences cost more per unit than named. | Size appropriately. For very small user counts who use software constantly, named licences may be cheaper. |
| Audit evidence | IBM audits require proof of entitlements plus usage logs. ILMT does not cover user-based metrics. | Retain proof of purchase. Configure IBM token licence server reports. Use SAM tools to integrate usage data from licence server logs. |
See IBM Audit Defence Service for expert support with IBM compliance requirements.
05 Best Practices for Maximising Value
Analyse Usage Patterns Before Purchasing
Study user behaviour over at least one month. Find peak concurrent usage to size the pool. If peak was 18 users once but normally 10, buy 12-15 concurrent licences and manage the occasional spike through scheduling. Data-driven sizing prevents over-buying "just in case."
Leverage Time Zone Sharing
Global teams can share floating licences across time zones. Europe and Americas use licences at different times of day. Ensure licensing terms allow this and implement a follow-the-sun licence server. This extracts additional value from the same pool without additional purchases.
Right-Size Token Pools at Renewal
Review IBM's token reports showing maximum tokens in use. If you consistently use 50 of 100 tokens, reduce the pool at renewal. If you are hitting 100 and getting denials, plan to add tokens before productivity is affected. See IBM ELA Renewal Service.
Configure Idle Timeout Features
Educate users to close applications when not actively using them. Configure idle timeout so licences automatically return to the pool after a set period of inactivity. This prevents users from holding licences unnecessarily and reduces apparent peak consumption.
Manage Licence Borrowing Carefully
IBM Rational and some other products allow "borrowing" a floating licence for offline use (e.g. an engineer going offsite). Borrowing temporarily reduces the available pool and can complicate compliance tracking. Use borrowing sparingly, keep borrow periods short, and monitor borrowed licences in the server admin console.
Centralise Licence Management
Assign a dedicated licence manager or SAM role to oversee pools. They should check usage reports frequently, update licence files when purchasing more, and coordinate with IBM on changes. A centralised approach avoids departmental conflicts over shared licences.
Integrate with Monitoring Tools
ILMT does not manage user-based licences, but SAM tools like Flexera or ServiceNow can integrate licence server log data for a complete picture. Automated monitoring alerts you when pools approach capacity, enabling proactive expansion before users are affected.
Vendor Shield: Ongoing IBM Licensing Governance
Continuous advisory, audit readiness, and pool optimisation for your IBM floating and token-based licences. Fixed monthly fee. Complete vendor independence.
06 Use Cases: When These Models Are Ideal
| Use Case | Recommended Model | Why |
|---|---|---|
| Engineering / technical teams | Floating licences | Engineers, developers, and analysts use heavy software sporadically. 10 floating licences can serve 30+ engineers. |
| Multi-product suites | Token licensing | Organisations using multiple IBM products (Maximo Suite, Engineering Lifecycle, Cloud Pak) with variable usage across components. |
| Consulting / project-based teams | Floating licences | Different project teams use software at different times. Concurrent pool accommodates rotation without per-person licensing. |
| Training environments | Floating licences | Classes of users need software only during sessions. One pool serves different trainees over time rather than licencing each individual. |
| Cost-constrained departments | Floating licences | Budget supports 5 concurrent licences but not 20 named. Shared model stretches budget for broader team access. |
| Global operations | Floating with time-zone sharing | Follow-the-sun usage pattern allows a single pool to serve teams in different regions at different times of day. |
07 Recommendations for CIOs and Licence Managers
Conduct a Usage Audit Before Implementing
Audit current software usage to identify peak concurrent needs and unique user counts. This data determines the optimal pool size that balances cost with user satisfaction. See IBM Licensing Assessment Service.
Start with a Modest Pool
If uncertain, begin with a slightly smaller pool. You can add licences or tokens quickly if you underestimated. Starting lean and monitoring is better than over-investing from day one and discovering you purchased 40% more than needed.
Negotiate Token Flexibility in Agreements
When establishing a token agreement, negotiate the ability to reallocate tokens as needs change. Ensure entitlements cover all products you intend to use, including new modules IBM may release under the programme. See IBM Negotiations Service.
Ensure Licence Server High Availability
A downed licence server means no one can work. Run redundant servers or maintain backup licence keys. Have at least two IT staff trained on operating IBM licence management tools, with documented procedures for updates and troubleshooting.
Consider Mixing Floating and Named Licences
For the same product, heavy daily users may warrant named licences while occasional users share a floating pool. For example: 10 constant SPSS users get named licences. 20 occasional users share 5 floating licences. Track compliance for each group separately.
Plan for Growth and Re-Evaluate Annually
10 floating licences for 30 users works until the team grows to 60. The concurrent-to-total-user ratio may shift as teams become more dependent on tools. Re-evaluate pool sizing annually or with any major staffing changes.
Maintain Audit-Ready Documentation
Retain proof of entitlements showing purchased counts. Archive licence server usage logs (IBM typically requests 12 months for audits). For token pools, maintain records of any reallocation or trades. See IBM Audit Defence Service.
Engage Independent Expertise for Optimisation
IBM licensing specialists can identify opportunities to consolidate separate product licences into a token model for savings (or vice versa), right-size pools based on usage data, and structure agreements that maximise flexibility. A short engagement typically yields significant ROI. See IBM Advisory Services.
📚 Related Reading
IBM Licence Information: Everything You Need to Know → IBM Subscription Licensing → IBM Non-Production Licensing → IBM Cloud Pak Licensing → IBM Licensing Assessment Service → IBM Audit Defence Service → IBM Negotiations Service → IBM Licensing Knowledge Hub →IBM Licensing Overview
Guide
Subscription Licensing
Guide
Non-Production Licensing
Guide
Cloud Pak Licensing
Guide
Licensing Assessment
Service
Audit Defence
Service
IBM Licensing Hub
Knowledge Hub
IBM Assessment Tools
Tools
Need Help Optimising IBM Shared Licence Models?
Redress Compliance provides independent IBM licensing advisory including usage analysis, floating and token pool sizing, agreement negotiation, and audit defence. We help enterprises identify the optimal licensing model for each product and right-size pools to deliver 30-50% savings vs. named-user equivalents.