OpenLM License

To see which subscriptions and features your OpenLM license includes, open OpenLM License. You can also update the license when your entitlements change. The two main workflows are:

• Check license status: Review your subscriptions, the feature records they include, and the usage against licensed limits. This workflow is the same in OpenLM Platform and in on-premises deployments.
• Update the license: In OpenLM Platform, trigger a license synchronization to update your license from OpenLM Licensing and the CRM (subscription system). In on-premises deployments, upload a new license file on the Settings page.

To open OpenLM License, select Navigation (the grid icon in the OpenLM Platform header), then Platform Administration, then OpenLM License.

For related tasks, see OpenLM Products.

How licensing is organized

OpenLM licensing follows a three-level hierarchy:

• Plan: A purchasable offering from OpenLM, such as Engineering Automation or SaaS Management Automation. A subscription is a regular payment for a plan, and each customer subscription maps to an OpenLM license.
• Product: A group of related functions within a plan, such as Alerts, Directory Sync, or License Access Control.
• Feature: An individual licensed item inside a product. For example, SLM_LicenseManagers controls the number of license-server connections you can monitor, DM_UniqueDongles limits the number of unique dongles tracked, and PM_OfflineMonitoring turns on offline monitoring for Process Manager.

The Subscriptions and License Summary pages work the same way in both deployment models. The difference is how you update the license: OpenLM Platform uses synchronization, and on-premises deployments use license file upload.

Each plan contains a predefined set of products and features. The Subscriptions page lists the subscriptions in your environment. A customer can have multiple subscriptions, and their combination represents the full OpenLM license the customer owns. The License Summary page shows the individual feature records that the subscriptions provide.

View your subscriptions

To see your subscriptions, open Subscriptions. The page lists the subscriptions in the environment. A customer can hold multiple subscriptions, and together they define the customer's full OpenLM license.

The following image shows the subscriptions with their status, quantity, and expiration date:

Subscriptions with status, quantity, and expiration date

Subscriptions page columns

To filter subscriptions by name, use the search bar. To reload the list from the server, select the refresh icon.

The following table lists the columns of the Subscriptions page:

Column	Description
Name	The display name of the subscription.
Plan	The plan template associated with the subscription, such as Engineering Automation or OpenLM Trial License.
Status	The state of the subscription: Licensed (active) or Deleted (no longer active).
Quantity	The licensed count for the subscription, based on the main measurable feature of the plan. For example, for Engineering plans the quantity reflects the number of engineering users (the SLM_Users_Engineering feature).
Expiration	The date and time when the subscription expires.
Features	Select Show Features to inspect the individual feature records included in the subscription.

View licensed features

To see every feature record licensed in the environment, open License Summary. The page aggregates the records across all active subscriptions.

The following image shows the feature records with their license type, usage, and status:

Feature records with license type, usage, and status

License Summary page columns

The following table lists the columns of the License Summary page:

Column	Description
---	---
Name	The unique identifier for the feature record, such as Alerts_AlertRules or DS_Domains.
License Type	The license model applied to the feature. For more information, see Feature license types.
Usage Status	Whether the feature is Available or Unavailable in the environment.
Quantity	The licensed limit for the feature, such as the number of allowed domains or rules.
Total Usage	The consumption count for features that track usage, such as unique resources or activation-with-usage features.
Token Price	The token cost per unit of consumption for reusable-token-priced features.
Expiration	The date and time when the feature license expires.
Status	The overall license state of the feature: Licensed or Unlicensed.

Sync the license (cloud only)

To refresh your license data, run a sync. License synchronization updates the license data in the UI from OpenLM subscription and licensing systems. A sync pulls updated data from the CRM, which tracks subscriptions and payments, and from the License Generator, which stores the OpenLM licensing model. On the Settings page, you can view the last sync result and start a new sync manually.

Note

On-premises deployments don't use license synchronization. Instead, they use license file upload. For more information, see Upload a license file (on-premises only).

The following image shows the last sync result and the Sync License button:

Last license synchronization result and the Sync License button

Start a manual sync

If a subscription or feature is missing from OpenLM License, for example after you purchase a new subscription or after OpenLM adds features to your plan, run a manual sync:

1. Select Management, then Settings.

2. Select Sync License to start a new synchronization.

3. Wait for the sync to complete.

   The result updates automatically.

4. Check the Last Sync time, the Initiated By user, and the Result status.

Upload a license file (on-premises only)

To apply a new license in an on-premises deployment, upload a license file on the Settings page. On-premises deployments don't synchronize with the OpenLM licensing systems in the cloud. The Settings page has a Licenses tab that lists your available license files and an Upload New License File button.

Upload a new license file

If OpenLM renewed or changed your license, or added features to it, upload the new license file to apply the changes:

1. Select Management, then Settings.
2. Select Upload New License File.
3. Browse to the license file you received from OpenLM and confirm the upload.

After the upload completes, the new license file appears in the Available Licenses list. The Subscriptions and License Summary pages update to reflect the new license.

The following image shows the Licenses tab with the license file and the upload button:

Licenses tab with the license file and the upload button

Feature license types

Each feature record in OpenLM License has a license type that determines how the feature is metered and enforced. The following table describes the license types that appear in the License Type column on the License Summary page:

License type	What it means	Examples
Activation on/off	The feature is either available or not available for the plan. No usage tracking.	Alerts_SystemEvents, Product_Audit, Product_Compliance
Activation with usage	The feature is turned on and also has a licensed usage limit. The Total Usage column tracks consumption.	DS_Domains, LAC_Rules, Projects_Count, VLM_Licenses
Unique resource	Each license consumption is tied to a specific resource identifier, for example a username, a dongle ID, or a license-server ID. You can see the exact resource names consuming the license on the License Summary page.	OLM_Users, PM_Users, DM_UniqueDongles
Reusable token pool	OpenLM Platform has a shared pool of reusable tokens that token-priced features can consume.	OpenlmReusableTokens, PM_ReusableTokens
Reusable token price	The feature consumes tokens from a reusable token pool. The Token Price column shows the cost per use.	PM_ReusableTokens_Autocad (400), PM_ReusableTokens_Matlab (400)
Check-in/out	The feature uses a checked capacity instead of a simple on-or-off state.	SLM_LicenseManagers

Product-to-feature mapping

To check that a product is licensed in your environment, find it in the following table:

Note

OpenLM licensing model changes over time, with added features, added products, and renamings. The following mapping might change. Check OpenLM License in your environment for the information that applies to you.

Product	Related feature records	What to expect
Alerts	Product_Alerts, Alerts_SystemEvents, Alerts_AlertRules	A product-level feature and alert-specific feature records.
Directory Sync	Product_DS, DS_Domains	A base product feature and a domain-based usage feature.
Dongle Monitoring	Product_DM, DM_OfflineMonitoring, DM_UniqueDongles	The base feature, offline monitoring, and a unique dongle count.
Identity	Product_Identity, Identity_ExternalProviders, Product_IdentityAlignment	The base product, external identity provider support, and identity alignment.
License Access Control	Product_LAC, LAC_Policies, LAC_Rules	The base product plus policy and rule features.
Process Manager	Product_PM, PM_OfflineMonitoring, PM_Users	The base product, offline monitoring, and user-based limits.
Projects	Product_Projects, Projects_Billing, Projects_Count	The base product plus billing and project count features.
Software License Monitoring	Product_SLM, SLM_LicenseManagers, SLM_Allocations, SLM_Denials, SLM_Features, SLM_Usage	Core monitoring, license manager ports, allocations, denials, features, and usage tracking.
Virtual License Manager	Product_VLM, VLM_Licenses	The base product and the virtual license count.
Website Monitoring	Product_WSM, WSM_OfflineMonitoring	Website monitoring and offline monitoring.
Users and Groups	OLM_Users, SLM_Users_Engineering, SLM_Users_SaaS	Shared and product-specific user counters.

Reusable token pricing reference

Features that use the Reusable Token Price license type consume tokens from a shared pool each time they are invoked. The token price for each feature is defined inside the customer's license, so it is fixed for a given license file. The following table shows the token cost for each supported application:

Feature	Token price per use
PM_ReusableTokens_ActualUsage	50
PM_ReusableTokens_AgentProcedure	100
PM_ReusableTokens_SuspendResume	100
PM_ReusableTokens_ArcGis	400
PM_ReusableTokens_ArcGisPro	400
PM_ReusableTokens_Autocad	400
PM_ReusableTokens_Matlab	400
PM_ReusableTokens_Solidworks	400
PM_ReusableTokens_CATIA	1,000
PM_ReusableTokens_Harmony	1,000
PM_ReusableTokens_Kingdom	1,000
PM_ReusableTokens_Petra	1,000

Check entitlements in a customer environment

To verify that the expected license entitlements are in place:

1. On the Subscriptions page, confirm that the expected plans are present and not in a Deleted state.
2. On the License Summary page, confirm that the required product-level features are licensed and show a status of Licensed.
3. Check usage-based features, such as DS_Domains, LAC_Rules, Projects_Count, or VLM_Licenses. Verify that the Quantity value is enough for the deployment.
4. Check unique resource features, such as OLM_Users, PM_Users, or DM_UniqueDongles. Compare the Total Usage against the licensed Quantity.
5. If the UI doesn't match your license state in the cloud-hosted OpenLM Platform, select Settings, then Sync License.
6. If the UI doesn't match your license state in an on-premises deployment, upload the license file instead.

Products without separate feature records

Some products and UI areas are not individually licensed as separate feature records. They fall into three groups:

• Items that map to features under a parent product, such as Denials under Software License Monitoring.
• Items that are part of core OpenLM infrastructure and do not require separate licensing, such as Broker Hub, OpenLM License, and core Identity.
• Items that are not licensed but might be licensed if they are not considered core infrastructure.

The following table describes how each item is represented:

Product or area	How it appears in the entitlement model
Denials	Represented as the SLM_Denials feature under Software License Monitoring.
License Servers	Covered by Software License Monitoring and the SLM_LicenseManagers capacity feature.
Licenses	Covered by Software License Monitoring features such as SLM_Features and SLM_Usage.
Notifications	Aligns with alerts-related entitlements. No separate feature record.
Process Sessions	Related to Process Manager. Not exported as a separate feature record.
Products	A UI navigation area. Not a separate licensed feature record.
Agent Activity Manager	Not represented as a separate feature record in the license template.
Agents Hub	Not represented as a separate feature record in the license template.
Broker Hub	Core OpenLM infrastructure that handles communication between platform services. Not exposed as a separate feature record.
License Manager	Core infrastructure that manages the license itself. Not exposed as a separate feature record.
Identity (core)	Core Identity functionality (baseline authentication and user identity) is OpenLM infrastructure and is always available. Advanced Identity capabilities such as external provider support (Identity_ExternalProviders) and identity alignment (Product_IdentityAlignment) are separately licensed. See the product-to-feature mapping earlier on this page.