IBM Concurrent User Licensing

IBM Concurrent User Licensing Overview:

• Allows multiple users to access the software
• Licenses are shared across a network
• Users access based on available seats
• Ideal for teams with varied usage needs
• Cost-effective for flexible access

What is IBM Concurrent User Licensing?

Concurrent User Licensing refers to a model where software licenses are shared by multiple users, with a restriction based on the number of people who can use the software at the same time.

The license count controls the number of users who can access the software simultaneously, making it an effective, cost-saving solution for teams that do not all require access simultaneously.

In IBM’s case, this model is employed across various software offerings, allowing organizations to maximize the utility of their investments.

Key Features of IBM’s Concurrent User Licensing

• Shared Licensing Pool: Licenses are pooled and shared across multiple users, allowing efficient distribution.
• Usage Flexibility: Users can access the software if they do not exceed the total number of allowed concurrent users.
• Scalable for Different Needs: This model is particularly beneficial for organizations with fluctuating user numbers or for software that is not used consistently by all employees.

How Does IBM’s Concurrent User Licensing Work?

IBM’s Concurrent User Licensing works on a simultaneous access basis. Here’s a breakdown of how it operates:

1. License Pooling:
   • IBM software licenses are grouped in a central pool, and users from the organization can pull from this pool when they need access.
   • For example, if an organization purchases 10 concurrent licenses of IBM SPSS, up to 10 people can use the software simultaneously.
2. Tracking and Enforcement:
   • IBM uses a License Manager to monitor active users. The License Manager monitors how many users are concurrently accessing the software.
   • If all licenses are in use, any additional user trying to access the software will be blocked until one of the current users logs out or closes the application.
3. License Checkout and Release:
   • Users typically “check out” a license when they open the application. When they are done, they “release” it, making it available for someone else.
   • Example: Imagine a company with 20 data analysts sharing five licenses of IBM Cognos Analytics. As long as no more than 5 analysts are using the software simultaneously, all is well. When a sixth analyst attempts to access Cognos, they must wait until one of the existing users releases their license.

Benefits of IBM’s Concurrent User Licensing

IBM’s Concurrent User Licensing comes with several key advantages for organizations:

• Cost Efficiency: This licensing model can significantly reduce costs, particularly for teams where not everyone needs simultaneous access. Instead of purchasing a license for every user, companies only need to purchase enough licenses to cover typical peak usage.
• Flexibility: The concurrent model is ideal for organizations with users in different time zones or working shifts, as it ensures everyone gets access when needed.
• Reduced License Waste: With individual licensing, many licenses might be idle when the user isn’t working. Concurrent licensing reduces this waste by allowing others to utilize those licenses.

Key Considerations When Using IBM’s Concurrent User Licensing

While the concurrent user model provides flexibility and cost savings, there are important considerations to ensure smooth operations:

• Peak Usage Planning:
  • Organizations must determine how many users typically need simultaneous access. Undercutting the number of licenses can lead to accessibility issues during peak times.
  • Example: If you have 30 engineers but only 5 licenses, and there’s a spike where 10 engineers need the software, some will experience delays.
• License Availability Monitoring:
  • IBM tools, such as the IBM License Key Server, can be used to monitor license utilization. This helps identify patterns and allows organizations to adjust the number of concurrent licenses accordingly.
• Geographical Distribution:
  • If your organization operates in multiple regions, consider time zone differences. Concurrent licensing is beneficial when users work at different times, effectively using fewer licenses.
  • Example: A multinational company with offices in New York and Tokyo could leverage concurrent licensing effectively since the usage hours between these locations rarely overlap.

IBM Software That Uses Concurrent User Licensing

IBM offers concurrent user licensing for several of its popular software solutions. Here are a few notable examples:

1. IBM SPSS Statistics:
   • Widely used for data analysis, SPSS is a prime candidate for concurrent licensing. Typically, not all data analysts need access simultaneously, making it possible for a smaller number of licenses to support a larger team.
2. IBM Cognos Analytics:
   • Cognos is a business intelligence tool that supports reporting and analytics. Concurrent licensing helps optimize costs for teams using Cognos occasionally for specific reporting tasks.
3. IBM Rational Software:
   • Rational Software’s concurrent user licensing model is used for software development and testing. It is suitable for developers who may only need temporary access to certain tools during specific stages of the development lifecycle.

Concurrent vs. Named User Licensing

It’s also useful to understand how concurrent licensing differs from named user licensing:

• Named User Licensing: In this model, a license is assigned to a specific individual. It doesn’t matter if the user is actively using the software—the license remains occupied. This approach is often more costly for teams with occasional users.
• Concurrent Licensing: Instead of individual licenses for each user, concurrent licensing allows anyone in the organization to use the software, provided the total number of concurrent users does not exceed the license limit.

Example:

• If you have 15 data scientists and need SPSS access, Named User Licensing would require 15 licenses. However, with Concurrent Licensing, you might only need 5-7 licenses, assuming not everyone needs access simultaneously.

Best Practices for Implementing IBM Concurrent Licensing

To make the most of IBM’s concurrent user licensing model, consider these best practices:

• Understand Your Usage Patterns:
  • Analyze your team’s usage patterns to understand peak times and average number of concurrent users.
  • IBM tools like the IBM License Metric Tool (ILMT) can be used to gather detailed usage statistics.
• License Management Tools:
  • Utilize tools like IBM License Key Server to effectively manage and monitor license distribution.
  • Set up alerts to notify you if the number of concurrent users approaches the limit frequently, signaling the need for more licenses.
• User Training:
  • Educate users on releasing licenses when they are no longer needed. This helps avoid unnecessary delays for others who may need access.
• Consider Shifts and Time Zones:
  • If your organization operates across multiple time zones, you can optimize license usage by staggering shifts or encouraging users to use the software during less busy periods.

Real-World Example: Concurrent Licensing in Action

Consider a consulting firm with 50 employees who need access to IBM SPSS for client projects. Not all consultants work on data analysis simultaneously, so the firm decides to purchase 10 concurrent licenses instead of buying a license for each user. Here’s how they optimize:

• License Pooling: The 10 licenses are pooled centrally. On a typical day, only 5-8 consultants need SPSS simultaneously.
• Cost Efficiency: Instead of purchasing 50 individual licenses, the firm saves significantly by leveraging concurrent licensing’s flexibility.
• Monitoring Usage: The IT department monitors license usage via IBM’s License Key Server. They identify that 9 or 10 licenses are occasionally in use, and an 11th user needs access. With this data, they decide to purchase one additional license to cover peak usage.

When to Choose IBM Concurrent User Licensing

Concurrent user licensing is ideal in the following scenarios:

• Occasional Users: When software is only needed occasionally by users, concurrent licensing helps ensure that the company isn’t overpaying for idle licenses.
• Large Teams with Shared Needs: Teams that share access to the same software tools benefit by reducing redundant costs.
• Varying Workloads: When the workload fluctuates significantly, such as during certain projects or increased activity, concurrent licenses allow teams to ramp up without needing dedicated licenses for each user.

Common Challenges and How to Overcome Them

• Overuse During Peak Hours: One challenge with concurrent licensing is that there might be more demand than available licenses during peak hours. The solution is to carefully monitor peak usage times and adjust the number of licenses accordingly.
• User Education: Users may forget to close applications, unnecessarily keeping licenses occupied.
• Solution: Educate users on properly releasing licenses and consider implementing time-out policies where licenses are automatically released after a period of inactivity.

FAQ for IBM Concurrent User Licensing:

What is IBM Concurrent User Licensing?
IBM Concurrent User Licensing allows multiple users to share a pool of licenses, where the number of available licenses determines access.

How does it differ from a per-user license?
A per-user license assigns a license to one specific user, while concurrent licensing shares licenses among multiple users.

Can users access the software anytime?
Yes, users can access the software, but access depends on the number of available licenses at that moment.

Is concurrent licensing cost-effective for large teams?
It can be more cost-effective for teams with fluctuating usage, as it reduces the need for individual licenses for every user.

What happens if all licenses are in use?
If all licenses are being used, additional users must wait until a license becomes available.

Does the software installation count against the license?
No, the installation doesn’t count. Licensing is based on the number of active users at a given time.

How is a concurrent license managed?
A license manager monitors and controls access to ensure that only the permitted number of users use the software concurrently.

Can licenses be shared across multiple locations?
Yes, concurrent licenses can be used across different locations as long as the software is accessible through a shared network.

Is there a limit to the number of users that can share licenses?
The number of users who can share the license is unlimited, but the number of active users is restricted by the number of available licenses.

Do concurrent licenses apply to all IBM products?
No concurrent licensing is available for specific IBM software. Check the product documentation for details.

What are the technical requirements for concurrent licensing?
You need a license server to manage the pool of licenses and ensure users access the software based on availability.

Can I increase the number of concurrent licenses?
Yes, additional licenses can be purchased if your team’s usage increases.

Are concurrent licenses renewable?
Yes, they typically require renewal at the end of the contract term, based on your agreement with IBM.

How do I know if my team is exceeding license usage?
The license manager provides reports showing how often all licenses are in use and when users cannot access the software.

Can concurrent licensing be used for remote teams?
Yes, as long as remote users are connected to the network where the license manager is installed, they can access the software.

Is concurrent licensing suitable for seasonal work?
Yes, concurrent licensing is flexible for businesses with seasonal or fluctuating software usage needs.