This page is a guide for engineers working for the U.S. government agencies and for procurement officers to understand the OpenLM GSA pricing structure.
The sections below will guide you through the steps towards completing the pre-procurement research so you reach the procurement officer in your agency with all the GSA pricing information needed.
Knowing the OpenLM GSA pricing structure and actual GSA prices is only one step in the process. Whether you are from the engineering department or procurement, if you have any questions we are here to answer them.
OpenLM General Services Administration Important Information
Contractor details : OpenLM Contractor on GSA Advantage
Products: OpenLM Products on GSA Advantage (first click on the link, then on the Go button by the GSA Advantage search window). But before you do, look at the steps on this page. If you haven’t yet seen GSA Contract Holder, OpenLM it’s worth going there first.
Ask about existing federal customers: Contact us.
1. Find out if OpenLM is What you Need?
OpenLM is on the GSA schedule but there’s not much point in checking out the part numbers if OpenLM isn’t what you need. First understand how OpenLM works as a solution for monitoring, reporting and auditing of engineering software licenses. We suggest starting with our Products page and coming back here to investigate special GSA pricing once you know what OpenLM can do.
2. Understanding the OpenLM GSA Pricing Structure
The first time you look at the list of OpenLM products on GSA Advantage, you might be confused. We hope this page will put you on track with GSA Pricing for OpenLM.
The pricing structure used for the GSA is identical to that used for any other customer, except that the prices themselves have been adjusted to include the GSA discount. OpenLM has one main product called OpenLM and a selection of optional extensions that add functionality to the main product. We sometimes refer to the main product without extensions as OpenLM Core.
OpenLM is listed on our price list in several different ‘dimensions’
- By initial number of vendors and users
- By additional vendors and users
- By business model
These are explained below.
OpenLM by Initial Number of Vendors and Users
Initial Number of Vendors and Users
The first step is to select the implementation that fits that number of vendor daemons you want to monitor and the number of users that will be pulling engineering software licenses from the pool. The options are listed below.
As you would expect, the price per vendor daemon and per user drops as the number increases.
- Up to 5 vendors and up to 50 users
- 1 vendor and up to 100 users
- Up to 5 vendors and up to 150 users
- Up to 10 vendors and up to 250 users
- Up to 20 vendors and up to 2000 users
- Up to 30 vendors and up to 3000 users
- Up to 40 vendors and up to 4000 users
- Up to 50 vendors and up to 5000 users
- Up to 60 vendors and up to 6000 users
- Up to 70 vendors and up to 7000 users
- Up to 80 vendors and up to 8000 users
- Up to 90 vendors and up to 9000 users
- Up to 100 vendors and up to 10000 users
If you want a configuration that falls between these standard packages, no problem. You just take the closest one down and then add the extra units of vendors and/or users from the list below:
OpenLM by Additional Vendors and Users
Additional Vendor Daemons
You pay only for the exact number of additional vendor daemons you need. The more you add, the lower the price, according to the following groups:
You pay only for the exact number of additional users you need. The more you add, the lower the price, according to the following groups:
You want 11 vendors and 350 users, so you’ll need 3 parts:
- Up to 10 vendors and up to 250 users
- 1 additional vendor at the price per vendor for 1-10 additional vendors
- 100 additional users at the price per user for 51-100 additional users
Now you need to consider the business model
By Business Model
Whatever configuration you choose, you must decide whether to purchase a term license for one year or a perpetual license. If you purchase a perpetual license, there is an additional maintenance fee to pay including the first year. In other words, every product option list above appears 3 times:
- 132-32 Annual (term) – all of these products have ‘ANN’ in the product name
- 132-33 Perpetual – all of these products have ‘PER’ in the product name
- 132-33 Maintenance (for the perpetual license purchased) – all of these products have ‘MNT’ in the product name
Now you have a general picture of OpenLM’s GSA pricing structure you can go to GSA Advantage and get the price for the configuration you need. Contact us if you have any questions.
3. Finding the Right Part Numbers on GSA Advantage
Once you have become familiar with the OpenLM GSA pricing structure (see above), you will want to identify the part numbers you need. There are several different ways to do this, the main one is as follows:
- Search GSA Advantage for OpenLM
- When you get the results, sort by NSN/mfr. part number
- You will see that the configurations are listed in threes, in increasing combinations of vendors and users. The product name includes the number of vendors and users. There is a separate part number – perpetual (permanent) license (PER), yearly maintenance (MNT) and annual license (ANN) – for each configuration. Part numbers range from 1000 up to 13170.
- After all the configuration and business models for the initial purchase of the main product, come the part numbers for additional vendor daemons (parts 2000 – 20190). Just like the main product described above, these also come in threes – perpetual, maintenance and annual. Note that the price for each part is per vendor daemon so you decide on the exact number you need.
- Then come the additional users in a similar format to the additional vendors from part number 21000 – 21310
- From part number 30000, the items listed are extensions, which are enhanced functionality modules that can be added if needed. Some of these are one per OpenLM installation and others are per workstation. Again, there are part numbers for perpetual, maintenance and annual licenses.
- Project Usage 3000 – 30010
- Active Agent 31000 – 31250
- External Database 32000 – 32010
- Roles and Permissions 33000 – 33010
- Alerts 34000 – 34010
- Directory Synchronization 35000 – 35010
- Group Usage 36001 – 36010
- License Allocation Manager 37000 – 37010
- Actual Usage 38000 – 38010
- Reporting Hub New 39010 – 39030