VoiceConsole Licensing

License Delivery

When VoiceConsole 6.2 or later is first accessed it is necessary to visit the Configure License page and select a license option. After a license option is selected, the appropriate license actions are displayed. Follow the instructions at the link above for the selected option to ensure VoiceConsole is licensed.

Licensing for VoiceConsole is now handled via the Honeywell Software Licensing Portal.

  • For VoiceConsole SaaS deployments, a cloud connection to the Honeywell Software Licensing Portal is used. A Cloud Server ID is provided for entry on the Configure License page.
  • For VoiceConsole On Prem deployments, a Local License Server is now installed. Requests to activate and deactivate licenses are made using Activation IDs. The requests are made from the local server to the Honeywell Software Licensing Portal and the Honeywell Software Licensing Portal provides a response for the local server.

License management is split between two functions.

  1. The License Administrator accesses the Honeywell Software Licensing Portal to view license details. This person is generally a Honeywell Voice partner or a Honeywell direct customer. However, a Voice partner may elect to allow their customers access to the Honeywell Software Licensing Portal to perform this function.

  2. The VoiceConsole Administrator is an end customer of VoiceConsole. The License Administrator provides this person the details (Cloud Server ID or Activation ID) to enter in VoiceConsole.

Legacy licensing (a license provided by Honeywell and imported into VoiceConsole in previous releases) is deprecated for VoiceConsole 6.2 and later.

When installing or upgrading in a clustered environment, contact Honeywell for assistance with licensing.

Advantages of the Honeywell Software Licensing Portal

Legacy licensing focuses on device type (A700x, A700, A500) and features (Pick Up & Go, TTS, etc.). The legacy license is specific in what is supported via the license and the license is only available on the specific server used to import the license.

Cloud and Local licensing through the Honeywell Software Licensing Portal is a higher level licensing and adds flexibility to the licensing deployment:

  • Rather than licensing 100 A700x devices and 50 A500 devices as would be done with Legacy licensing, this method issues 150 licenses that could be used by any supported device type.
  • Users can split the license among different servers. A license for 200 devices could be split between two servers by using the Activation ID to request and activate 150 copies of the license on one server and then activate the remaining 50 copies on a second server. If needs change, unused licenses can be deactivated on one server. Later these licenses can be activated on another server.
  • Ramp ups (an increase in licenses over time, for example adding operators monthly to build capacity) and seasonal operators (licenses active for a period of three months for example) can be handled by adding additional Activation IDs with a corresponding subscription beginning and end.

License Term

Licensing for VoiceConsole is available as:

  • Perpetual licensing for VoiceConsoleOn Prem deployment
  • Subscription licensing for VoiceConsoleOn Prem deployment or VoiceConsoleSaaS deployment

License Architecture

VoiceConsole 6.1 and later uses a new application-level licensing architecture. VoiceConsole 5.x and earlier used hardware-type licensing which prevented the ability to use multiple device types with the same license.

Application Types

It is important to distinguish between the two types of applications that may be used with VoiceConsole.

  • DevKit based applications are built from DevKit and may be referred to as Guided Work Solutions or branded for a specific solution such as a WMS. These applications run on multiple device types including A700x and Android devices.

    • Applications must be built from DevKit 1.15 or later for VoiceConsole SaaS deployments.

    • Applications must be build from DevKit 1.5 or later for VoiceConsole On Prem deployments. However, DevKit 1.15 is recommended.

  • Directed work applications are built from TaskBuilder and VoiceArtisan. These applications run on A500, A700, and A700x.

VoiceConsole 6.x License Support

VoiceConsole 6.1 introduced application-level licensing. Application-level licensing used with VoiceConsole supports both DevKit based and directed work applications:

  • DevKit based applications are licensed through VoiceConsole. The license to run DevKit based applications is separate from the license to develop applications with DevKit. A separate license may be required for GWS Connector. The application is licensed with VoiceConsole 6.x. This allows any supported device to use the license. VoiceConsole 5.x licensed the device, so a different device required a new license.
  • Honeywell continues to support TaskBuilder and VoiceArtisan based (directed work) solutions for A500, A700, and A700x. A DevKit based license is required to support these devices and applications on VoiceConsole 6.1 and later, even if the customer is not currently using a DevKit based application. Also, note that A500 and A700 are supported only in VoiceConsole On Prem deployments.

Customers without a DevKit based license can continue using VoiceConsole 5.x where prior VoiceConsole and VoiceCatalyst product licenses are still valid.

Honeywell recommends that customers using DevKit based applications upgrade to VoiceConsole 6.2.1 to avoid potential compatibility problems with future software releases.

Available features may depend on licensing tier. Contact your customer service representative for details.

VoiceConsole
Function
Application Type
DevKit Based Directed
Work
Honeywell Software Licensing Portal Available Requires DevKit based license
VoiceConsole On Prem Deployment Available Requires DevKit based license for VoiceConsole 6.1 or later, without DevKit based license must use VoiceConsole 5.x
VoiceConsole SaaS Deployment Available A700x only, requires DevKit based license
Operational Intelligence Asset Insights Available A700x only, requires DevKit based license
Performance+ for GWS Workflow Insights Requires GWS Connector Not available
Log Analyzer Available Not available

License Consumption

A valid license must be in place before a device can load a profile, operator, or task package. VoiceConsole operates on a floating license principle that shares the licenses over a pool of devices running the licensed application. Licenses are requested from the server (either the Local License Server or the Cloud License server depending on deployment) and if a license is available it is assigned to that device.

In general, licenses are consumed:

  • When a device loads an operator or a task package

  • When an app requests a specific licensed feature.

If a device is previously licensed, it does not consume another license if it loads an operator or task again. Likewise, if a device is currently licensed for a feature requesting that feature again does not consume another license.

In general, licenses are released:

  • When a device is placed in a cradle, placed in a charger, or turned off

  • When a devices has remained inactive for an extended period of time

  • When a device is deleted from VoiceConsole.