Authorised User, Floating, Token, and SaaS Models. Cost Drivers, Optimisation, and Compliance Strategies for DOORS, Team Concert, Rhapsody, and ClearCase.
This article is part of the IBM Licensing Knowledge Hub. Related guides include IBM Db2 Licensing, IBM WebSphere Licensing, and IBM MQ Licensing.
IBM Rational tools form the backbone of engineering lifecycle management at enterprises in aerospace, automotive, defence, financial services, telecommunications, and manufacturing. Products like IBM DOORS (requirements management), Rational Team Concert / Engineering Workflow Management (collaborative development), Rational Rhapsody (systems modelling), and Rational ClearCase (configuration management) support critical workflows that organisations cannot easily replace.
Yet the licensing that underpins these tools is among the most complex in the IBM portfolio. Multiple licence metrics, role-based token consumption, floating pool mechanics, and SaaS subscription models create a landscape where ITAM teams routinely overspend by 30–50% through mismatched licence types, over-provisioned pools, idle shelfware, and compliance gaps that become expensive during IBM audits.
The most expensive IBM Rational licensing mistake is not over-buying a single metric. It is using the wrong metric for the wrong user population. Authorised User licences for occasional users, floating pools sized for theoretical peaks that never materialise, and token pools purchased without understanding consumption rates all produce the same result: significant waste that compounds through annual support fees year after year.
IBM Rational products are available under four primary licensing models. Each has distinct mechanics, cost structures, and suitability for different usage patterns. Choosing the optimal model is the highest-impact decision ITAM teams can make.
| Dimension | Authorised User | Floating (Concurrent) | Token-Based | SaaS Subscription |
|---|---|---|---|---|
| How it works | Dedicated licence tied to one named individual. Only that person may use the software. | Shared pool. Any user can draw a licence, up to the pool limit at any given time. | Generic "token currency" pool shared across multiple IBM tools. Each tool/role consumes a defined number of tokens per session. | Cloud-hosted by IBM. Monthly subscription based on active or concurrent users. |
| Availability | Perpetual or term subscription | Perpetual or term subscription | Term subscription only (OpEx) | Subscription only (OpEx) |
| Flexibility | Low. One licence per person. Reassign when staff changes. | Medium. Shared across users but limited to one product. | High. Floats across users and across different tools in the IBM Engineering suite. | High. Exceeding subscription triggers overage fees rather than hard lockout. |
| Price positioning | Base price per user | 1.5–2× authorised user price per concurrent seat | High upfront pool cost. Economical when spread across multiple products. | Premium per-user monthly cost. Includes support and hosting. |
| Best suited for | Core team members who use a tool daily and need guaranteed access | Large/global teams with staggered usage across time zones. Infrequent users. | Organisations using multiple Rational/ELM tools with variable, project-driven usage patterns | Distributed teams needing quick access. Organisations preferring OpEx. |
While all four models apply across the Rational portfolio, usage patterns differ significantly between products. Matching the right licence model to each product's typical usage is essential for cost efficiency.
Requirements management involves many stakeholders. Floating or Token licences are typically optimal, allowing multiple contributors to access DOORS without dedicated seats. Authorised User suits core requirements engineers who work in DOORS daily. Token licensing works well because requirements activity fluctuates with project phases.
Collaborative development tools serve diverse roles. A mixed approach works best: Authorised User for full-time developers, Floating or Token for part-time team members and offshore contractors. Token consumption varies by role: Developer ~8 tokens, Contributor ~5 tokens.
Systems modelling tools serve a smaller, specialised user base. Authorised User or Token licensing is typical. Tokens are efficient when the same engineers also use DOORS or testing tools at different times. Rhapsody carries a higher token consumption rate.
Configuration management tools are typically licensed as Floating, since not every developer performs version control operations simultaneously. If ClearCase is your only IBM Rational tool, floating is typically more cost-effective than a token pool.
Token licensing is IBM's most flexible model for organisations using multiple Rational tools. But its economics depend entirely on understanding the token consumption rates that determine how many tokens are checked out per user session.
| Product / Role | Typical Tokens | Use Pattern | Pool Sizing |
|---|---|---|---|
| DOORS Next — Analyst | ~9–10 per user | Active requirements creation and management | High consumption. Size for peak requirements phase. |
| DOORS Next — Contributor | ~3–5 per user | Review, commenting, limited editing | Lower consumption. Many contributors at lower cost. |
| RTC / EWM — Developer | ~8 per user | Full development workflow: planning, coding, build | Core consumption. Typically most persistent users. |
| RTC / EWM — Contributor | ~5 per user | Task tracking, work item updates | Moderate. Shared with other occasional users. |
| Rhapsody — Modeller | ~10+ per user | Systems and software modelling | Highest consumption. Significant pool impact. |
| Quality Manager — Tester | ~6–8 per user | Test planning, execution, defect management | Variable. Peaks during testing phases. |
| Stakeholder / Viewer | ~1–2 per user | Read-only access, dashboards, reporting | Minimal. Large viewer populations cost little. |
The critical calculation is peak simultaneous token consumption. A well-sized token pool is typically 20–30% smaller than the equivalent set of individual product licences, because not all users are active simultaneously and tokens float across tools.
Aerospace Company — Token Pool Saves $340K vs Individual Licences
An aerospace company with 200 engineers used DOORS Next (80 users), RTC (120 users), Rhapsody (30 users), and Quality Manager (50 users). Under individual floating licences, the combined annual cost was $1.1M for 280 floating seats across four products.
Usage analysis showed peak simultaneous consumption never exceeded 140 users. A token pool sized for 140 concurrent users replaced the 280 individual licences, reducing annual cost to $760K. A $340K saving (31%).
Five primary cost drivers account for the majority of avoidable IBM Rational licensing spend.
Using Authorised User licences for occasional users who should be on floating or token pools. Every AU licence that sits idle 80% of the time represents ~80% wasted spend, including the 20% annual support fee. Measure actual usage, match licence types to patterns, and rebalance at every renewal.
Former employees' AU licences, floating pools for decommissioned tools, and token entitlements from expired projects all generate annual support fees with zero value. Quarterly reviews typically identify 15–25% shelfware in mature IBM environments.
IBM's annual S&S at approximately 20% of licence list price is permanent on perpetual licences. Over 5 years, cumulative support exceeds the original licence cost. Paying support on shelfware or over-provisioned licences compounds waste annually.
Separate licence servers in each region (US, Europe, Asia-Pacific), each provisioned for its own peak, prevent "follow-the-sun" sharing. Result: 2–3× more licences than a consolidated global pool requires. Consolidating can reduce total licence requirements by 30–40%.
IBM can adjust token consumption rates when new versions release. A tool consuming 6 tokens in v7.0 might consume 8 in v7.1, inflating your requirement by 33% without usage change. Monitor IBM's token consumption tables with every version upgrade.
| Dimension | On-Prem (Perpetual + Support) | On-Prem (Term/Token) | SaaS Subscription |
|---|---|---|---|
| Cost model | CapEx (licence) + OpEx (20% annual support) | OpEx: annual or multi-year term fee | OpEx: monthly or annual per-user subscription |
| 3-year cost | Year 1 high (licence + support), Years 2–3 support only | Flat annual cost across all 3 years | Flat or increasing. Potential overage premiums. |
| Infrastructure | Customer manages servers, licence key servers, upgrades | Customer manages servers, licence key servers, upgrades | IBM manages everything. No infrastructure. |
| Compliance risk | High. Must track users, floating pools, ILMT. | High. Same tracking obligations. | Lower. IBM manages metering. Overage billed automatically. |
| 5+ year economics | Typically lowest total cost if usage is stable | Middle ground: flexibility with moderate cost | Typically highest total cost. Premium for convenience. |
Telecommunications Company — SaaS vs On-Prem 5-Year TCO
300 ELM users compared SaaS subscription ($420/user/month = $1.51M/year) against on-premises perpetual ($2.8M upfront + $560K/year support). Over 5 years: SaaS totalled $7.56M. On-premises totalled $5.6M. The on-premises approach saved $1.96M over 5 years. However, SaaS eliminated 2 FTEs managing infrastructure ($300K/year), narrowing the gap to $460K. The company chose a hybrid approach: on-premises for the stable 200-user core, SaaS for 100 variable project-based users.
Power users (daily) get AU licences. Regular users (weekly) go on Floating/Token. Occasional users (monthly) use Token pool or SaaS overage. Misclassifying 20 users can represent $50–100K in annual waste.
Deploy IBM's Rational Licence Key Server Administration and Reporting Tool. Track peak concurrent usage, average utilisation, and denial events. Review monthly. Denial logs warn of under-licensing. Low utilisation signals over-provisioning.
Configure floating licence idle timeouts (30–60 minutes). Inactive sessions release licences back to the pool. This single measure can reduce effective peak concurrent usage by 15–25%.
"Follow-the-sun" sharing between time zones can reduce total licence requirements by 30–40% compared to regionally siloed pools. Verify IBM's geographical use terms before consolidating.
Identify AU licences assigned to inactive accounts, floating pools exceeding peak by >20%, and token entitlements from completed projects. Every unused perpetual licence costs 20% annually in support.
If using three or more Rational tools, model converting individual product licences to a unified token pool. Token pools typically deliver 20–35% savings for multi-tool environments.
Compare 12 months of usage data against current entitlements. Present IBM with evidence-based proposals: reducing over-provisioned pools, converting metrics, or adding capacity where denial logs show shortfalls.
2–3 year commitments can yield 10–20% discounts over annual renewals. Lock in pricing, token values, and support rates. Avoid over-committing on quantities.
SaaS is 20–40% more expensive over 5 years, but offers flexibility for project-based or seasonal usage. A hybrid approach (perpetual core + SaaS variable) often delivers the best economics.
Maintain complete records (Passport Advantage certificates, purchase orders) alongside RLKS ART data. Conduct internal audits annually. Proactive compliance management strengthens your position.
| Pitfall | How IBM Identifies It | Consequence | Prevention |
|---|---|---|---|
| Untracked AU | Comparing AD/LDAP user lists against entitlements | True-up at list price + backdated support | Quarterly user account audit. Immediate reassignment on staff departure. |
| Floating pool exceeded | Licence server logs for peak checkout and denial patterns | Additional floating licences at list price | Monitor RLKS ART monthly. Maintain 10–15% pool buffer. |
| Token over-consumption | Peak simultaneous token checkout vs purchased pool | True-up at per-token list price for excess | Track consumption daily. Alert at 80% pool utilisation. |
| Unauthorised servers | Network scans for FlexLM servers vs registered files | All users on unauthorised servers counted as unlicensed | Centralise all licence management. Prohibit unofficial servers. |
| Geo/affiliate misuse | User locations vs licence agreement scope | Additional licences for out-of-scope entities | Verify contract covers all subsidiaries and regions. |
Gather 12 months of RLKS ART usage data. Map entitlements against actual peak consumption. Identify shelfware and calculate the cost of your current metric mix versus alternatives. IBM's negotiating team will have internal data if they have audited you. You need your own data.
IBM's quarter-end and fiscal year-end (December) create urgency for their sales teams. Demonstrating awareness of alternatives (Jira, Azure DevOps, Jama Connect) creates competitive pressure that makes IBM more flexible on pricing.
Negotiate licence transfer rights (M&A scenarios), geographical use flexibility, and metric conversion at renewal. Request a "soft landing" clause for true-up at negotiated rates. Secure fixed token consumption rates for the term.
Usage data (12 months). Shelfware identified. Metric comparison modelled. Competitive alternatives researched. IBM fiscal calendar leveraged. Transfer/conversion rights requested. Support uplift capped (vs IBM's standard ~3% annual increase).
Gather every IBM Rational licence entitlement by product, type, quantity, and assignment. Simultaneously collect 90 days of usage data: peak concurrent usage for each pool, token consumption reports, and active user lists for AU licences.
Deploy across all licence servers. Configure to log usage, capture denial events, and generate automated reports. Set alerting at 80% pool utilisation. This monitoring pays for itself immediately through optimisation decisions.
Compare entitlements against actual peak usage to identify over-provisioned pools (reduce), under-provisioned pools (increase or convert), and shelfware (eliminate). Model token conversion economics for multi-tool environments.
Meet with engineering tool owners, procurement, and finance. Align on which tools remain on-premises, which move to SaaS, which metrics to target, and the renewal negotiation position. Stakeholder buy-in prevents optimisation conflicting with productivity.
Start 6–9 months before contract expiry. Build a specific position: quantities, metrics, conversion requests, and target pricing. Engage IBM early with data-backed proposals. Prepared organisations achieve 15–30% better outcomes.