License Management > Entitlements Management

In Raynet One, an entitlement is the operational record of a licensed usage right. It defines the product scope, license model, metric, quantity, and validity period that the system uses for allocation, reconciliation, ELP calculation, and compliance reporting.

In most cases, entitlements are derived from license contracts. The license contract provides the commercial source data, while the entitlement is the object used by the platform for license processing. If entitlement data is incomplete or incorrect, allocation results, ELP values, and compliance evaluations become unreliable.

Access

Open the Entitlements section from License Management, then go to Entitlements.

Overview

The Entitlements overview displays all entitlement records in a single list. Each row represents one entitlement and exposes the attributes relevant for license availability and compliance calculation:

Products: Product associated with the entitlement. A vendor icon is displayed if available. Products are typically created and maintained through license contracts.

Name: Display name of the entitlement record.

Model: License model assigned to the entitlement, for example, Perpetual, Subscription, or Maintenance. The selected model is part of the entitlement definition and influences entitlement assignment.

Metric: License metric used for counting, for example Core-based, Device-based, or User-based. Together with the license model, the metric determines how the entitlement is identified and processed.

Quantity: Total licensed quantity stored for the entitlement.

Allocated: Quantity currently assigned or consumed within the system.

Remaining: Unallocated quantity. Calculated as Quantity - Allocated. This value is relevant for license availability and compliance review.

License start: Start date of the entitlement validity period. This date is also used for automatic purchase event generation.

Maintenance quantity: Quantity covered by maintenance or Software Assurance.

Activation: Date on which the entitlement became active in the system.

Expiration: End date of the entitlement validity period. If no expiration date is defined, the entitlement is treated as non-expiring in the record.

Last demand synchronization: Timestamp of the most recent synchronization with license demand data.

Managed by: Responsible owner or managing system for the entitlement record.

Available actions

The toolbar in the Entitlements overview provides the following actions:

Refresh: Reloads the list using the latest available data.

Add: Creates a new entitlement record manually.

Edit: Modifies the selected entitlement.

Remove: Deletes the selected entitlement.

Search: Filters the list using a text search.

Be aware:
Manual entitlement creation via + Add should only be used when no corresponding license contract exists in the system. Contract-driven entitlement creation is always preferred to ensure source traceability and consistent lifecycle processing.

Contract-driven entitlement generation

Entitlements are typically created from License Contracts. Product records are maintained through the contract context, and entitlement generation is evaluated when the related product data is saved.

Be aware:
The fields License model and License metric are mandatory for correct entitlement generation and assignment. These fields determine which entitlement is created or linked. If either value is changed, the entitlement assignment may change as well. In technical terms, a different entitlement identity can be produced.

This behavior is especially relevant when switching between models such as:

•Perpetual

•Subscription

•Maintenance

Some products require a dedicated Maintenance entitlement, while for others a Perpetual entitlement is sufficient.

Manual entitlement creation should only be used if no corresponding license contract exists in the system. Contract-driven entitlement creation is the preferred approach because it preserves source traceability and supports consistent lifecycle processing.

Event generation and lifecycle behavior

Several events are created automatically based on contract and entitlement data.

Invoice date

When an Invoice date is entered in Add License Contract, the system automatically creates a corresponding contract invoicing event.

If the invoice date is left empty, the current date is used by default.

Be aware:
If the invoice date is left empty, Raynet One automatically uses today's date. Always enter the correct invoice date explicitly to ensure accurate lifecycle event generation and contract timeline integrity.

When the contract is updated later, the automatically generated contract invoicing event is updated accordingly.

License start

When an entitlement is linked and License start is defined, the system automatically creates a Purchased Event.

For the first purchase of an entitlement, a purchase event is created. If an additional purchase is recorded for the same entitlement later, the system creates a Purchased Renewal instead.

This behavior is relevant for both contract processing and entitlement lifecycle tracking.

License end

The License end date controls the end of the entitlement validity period. It also used for expiration-related event handling, including:

•License Expiration Warning

•License End Event

On the last valid day, the final expiration state is reached. After that point, the entitlement is no longer considered valid for further license coverage.

Automatic events

Automatically generated events are information events and cannot be edited manually.

This applies in particular to:

•contract invoicing events

•purchase events

•renewal events generated for the same entitlement

If the source contract is changed, the related automatic events are updated by the system.

What the user sees

The entitlement page provides a consolidated view of all operational license rights currently stored in Raynet One. From this page, the user can verify:

•which products are covered

•which license model and metric apply

•which quantity is stored

•how much quantity is already allocated

•how much quantity remains available

•when the entitlement starts and expires

This makes the page relevant both for operational validation and for troubleshooting incorrect compliance results.

Calculation and compliance notes

The accuracy of the entitlement depends primarily on these fields:

•License model

•License metric

•Quantity

•License start

•License end

Be aware:
Incorrect values in these fields directly affect entitlement identity, allocation behavior, ELP calculation, event generation, and compliance reporting. The Remaining value is calculated automatically from Quantity - Allocated and should be reviewed regularly.

Downgrade rights

Compliance processing can consider downgrade scenarios.

Example: a license for newer product version can cover usage of an older version. In this case, quantity may be transferred between compatible versions for compliance evaluation.

Upgrade rights

Upgrade handling will be updated soon.

Best practice:
After importing, creating, or changing a license contract, verify the resulting entitlement data. Especially: product assignment, license model, license metric, quantity, license start and license end.

These values control both the entitlement record shown in the UI and the downstream calculation logic used by the compliance engine. Also check the Calendar to confirm that all automatic lifecycle events were generated correctly and reflect the intended entitlement timeline.