License Details

License Details

Overview

Use these datasheets when planning a hi installation or preparing a purchase request. Each page describes the license capabilities and scope, identifies its dependencies, and links to the relevant workflow or integration documentation.

The Product Code identifies the software entitlement in the hi licensing catalog; it is not a price. License Type classifies an entitlement as Perpetual, Per-Session, or Per-Client. Entitlement Basis states what quantity to count: an installation, simultaneous session, active third-party client, peer connection at each hiMesh endpoint, or project-specific deployment.

This catalog includes current, pre-release, replaced, and discontinued non-OEM software bundles. Lifecycle describes commercial availability, not whether an already-issued license continues to work. Issued licenses remain valid and continue to work; pre-release features may change.

For new orders, hiCore satisfies the hiBase foundation requirement shown on the add-on datasheets. A hiBase requirement refers to an existing hiBase installation; the separately named add-on license is still required unless its datasheet says it is included in hiCore.

How to Use These Datasheets

1. Identify the installation's core entitlement: hiCore for the current foundation license bundle, or hiBase for an existing hiBase installation.

2. Select add-on licenses by the capability or integration required for the installation.

3. Use License Type and Entitlement Basis to distinguish installation-wide capabilities from session or panel capacity.

4. Open the linked datasheet to confirm included capabilities, required combinations, scope boundaries, and planning considerations before preparing a purchase request.

In the catalog, Lifecycle means Released (released license), Pre-release (features or availability may change), Replaced (superseded for new packaging), or Discontinued (not offered for new packaging). Previously issued licenses remain valid and continue to work. Requires identifies a separate entitlement dependency; Includes identifies entitlements supplied with a license; Replaces and Replaced by describe license bundle transitions. A floating entitlement returns to its pool when the associated panel is disabled or removed. For installation, session, and peer-endpoint counting examples, see Licensing.

Licensing Workspace Columns

For the fields and Option-row columns in System > Licensing, use License Status and Warnings Reference. Each row is an Option resolved from a purchased bundle; it is not a separate pricelist license.

License Collections

Browse the datasheets by lifecycle status:

• Active Licenses: licenses with a Released or Pre-release status.

• Retired Licenses: licenses marked Replaced or Discontinued.

Each collection lists Product Codes, entitlement details, primary use, and links to the individual datasheets.

Combination Rules

• These combination rules describe the established hiBase bundle combinations. For new orders, hiCore replaces the hiBase + hiAccess pairing; existing combinations remain valid.

• Native hi Hardware Panels and supported RIEDEL 1200 Series SmartPanel workflows require hiGlue and one user session per panel. Add hiUser licenses when simultaneous sessions exceed the available included capacity.

• hiContact GPIO boxes require hiGlue but do not consume a hiUser session.

• The external control gateway requires hiDock.

• Third-party clients, which are Northbound clients or supported third-party Hardware Panels, require installation-wide hiDock and one hiLink license per active client. A supported third-party Hardware Panel also uses one user session. hiBase/hiCore includes two user sessions, one reserved for the administrator; add hiUser only for simultaneous sessions beyond the included capacity. Native hi Hardware Panels and RIEDEL 1200 Series SmartPanel devices follow the requirements in the hiGlue datasheet.

• A multi-server deployment requires hiSwarm and a commissioned deployment design. See High Availability for the standard architecture.

For the license bundle lookup, see Feature Matrix. For license-file procedures, see Applying a License File.

Service Entitlements

Riedel Care Enhanced and Riedel Care Premium are service entitlements that govern access to software updates and new software features. They are not software bundles in this catalog and are not included in the product-code datasheets above. Confirm the applicable service agreement during system planning.

Trademarks