Licensing

OpSee features are licensed per install through a cryptographically signed license token issued by your vendor. The License Overview screen shows what your license includes, which equipment uses it, and when it expires — and is where you install new or renewed tokens.

Navigate to Admin → Platform Settings → Licensing (requires admin role).

How OpSee licensing works

Your license token defines three kinds of entitlements:

Group	Scope	Examples
Foundation	Whole install, included with any paid license	Historian & data layer, AI chatbot, API, Personnel, Material, Kaizen & Gantt
Feature slots	Per equipment — Pro (all 7 feature modules) or Starter (pick 1)	KPI & OEE, Production Execution, Workflow & Forms, Batch & Process, Quality, Alerts & Events, ML / Analytics
Add-ons	Whole install, with a quantity limit	HMI screens, Integrations Hub connectors

The token carries the limits (how many Pro and Starter slots you bought); you decide which equipment occupies which slot on this screen. Mixed tiers are supported — for example 5 equipment on Pro and 15 on Starter.

notitie

Application-level alerts are a licensed module, but safety- and PLC-level alarms are never license-dependent — they live in your PLC/SCADA layer and are unaffected by OpSee's license state.

The License Overview screen

• Current license — status (valid, expiring, grace, expired), customer name, expiry date and days remaining. The diagnostics line underneath shows the signature check, clock state, install ID, token ID and the install's Identity — the fingerprint of this installation's own keypair, generated on first start. Hover it to see whether your current token is bound to the keypair (proof-of-possession) or to the legacy install ID.
• Usage — Pro/Starter slots and add-ons: how many your license allows vs. how many are in use.
• Licensed equipment — every equipment holding a slot, its tier, enabled modules, and slot status.

Assigning equipment to slots

Use Activate equipment to bind an equipment to a free Pro or Starter slot. Pick the line itself: enterprise, site and area nodes (and the root of the tree) cannot hold a slot, because a slot automatically covers everything beneath the equipment it is bound to. Those nodes are greyed out in the picker. For Starter slots you pick the one feature module that equipment gets. Existing assignments can be upgraded (Starter → Pro), downgraded, switched to another module, or released back to the pool.

:::tip Find equipment by module Use the Find by module button to list every equipment for a given feature module — whether the module is enabled, available in the equipment's tier but not enabled, or the equipment is not licensed at all. Useful when auditing "which lines are licensed for OEE?" or planning slot assignments. :::

Frozen slots

If your license is renewed with fewer slots than are currently assigned, OpSee never deletes your assignments. Instead, the most recently assigned equipment beyond the new limit shows as frozen. Frozen equipment keeps its configuration but its licensed modules stop working once enforcement is active. To resolve, release other slots, rebalance, or contact your vendor for a larger license.

Installing a license token

1. Receive the token string from your vendor.
2. Open Admin → Platform Settings → Licensing and paste it into the token form.
3. OpSee verifies the signature, the install binding, and the expiry before activating it. If your new license includes more Pro modules than before, they are granted to existing Pro equipment automatically.

A token is bound to exactly one install — tokens cannot be shared between servers. Newer tokens bind to the install's own keypair (shown as Identity on this screen), which the server must physically hold to pass verification; see Concepts → Licensing for what that means when moving or restoring an install.

Renewing

For how the two renewal channels work conceptually (and the underlying cryptography), see Concepts → Licensing (Cloud & Offline).

Licenses expire and include a grace window (typically 30 days) so a late renewal never interrupts production abruptly.

Connected installs renew automatically when the cloud renewal service is configured.

Offline / air-gapped installs renew by challenge–response:

1. On the Licensing screen, click Export renewal request. This produces a signed request text containing your install identity and current usage — no production data leaves the system.
2. Send it to your vendor by email or carry it out on a USB stick.
3. The vendor returns a renewed token; paste it into the token form as in the install procedure above.

When something is wrong

Status	Meaning	What to do
Expiring soon	Within the warning window before expiry	Start the renewal now
Grace	Expired, but inside the grace window — everything still works	Renew immediately
Expired	Past the grace window	Renew; with enforcement active, licensed features stop until a valid token is installed
Invalid	Signature or install binding failed	Re-paste the token; if it persists, contact your vendor
Clock tamper	The system clock moved backwards past a recorded mark	Fix the server clock; contact your vendor if the status persists

The license screen itself always remains accessible to admins, so a renewal can be installed even when everything else is locked.