The service includes the use of the software, essential maintenance and the downloading of updates during the subscription period.
If the subscription is not renewed, usage rights will terminate at the end of the corresponding period, and the license and usage rights of the licensed products will expire.
Licensing Model Subscription
The OnPremises model enables the owner of the license to install the products on their own servers. In this case usage rights shall apply to both users (who use the products) and systems (where programs are installed). The license does not include the costs of infrastructure, the database backend or additional software.
The OnDemand model provides licensing of applications which Deister provides access to via the Internet. The license costs include use of the applications, infrastructure and additional software. In this case, the licenses are applied per user, as licenses per system are included as part of the OnDemand model.
Definition of License Elements
Licensing per User of Applications
Users of applications are defined as those that use any end applications of the “BUSINESS SOLUTIONS” product family, such as Axional ERP or Axional WMS, as well as products belonging to the “MOBILE SOLUTIONS” family.
The licensing model for these applications is by “nominal” user. Depending on their usage, it’s possible to distinguish three different types of users:
An authorized user is a physical person who is granted access to the program. The program can be installed on any number of computers or servers, and each authorized user may have simultaneous access to many instances of the program. The license holder must grant individual rights to each user with access to the program directly or indirectly (e.g. via a multiplex program, device, or application server). The usage rights of each authorized user are personal and non-transferable. They can only be transferred to another person, and the transfer must be permanent.
Client devices which require the execution of the program, receive the results of executing program commands, processes and applications, or are managed by the program are also considered Program Users. These devices need to be granted usage and licensing rights as a physical user would.
The licensee must have, at minimum, as many licenses for authorized users as the number of client databases. For example, if the licensee can access 25 different databases, they must license at least 25 authorized users.
A Flexible User is a natural person granted access to the program for usage during a limited period of his working hours. This is an special type of licensing only available for some modules and processes in Deister’s product portfolio. It is intended for environments in which many users only use the program sporadically, at most forty hours per month.
A Simultaneous User is a natural person or a device who accesses the system during a specific period of time.
Licensing by Runtime Users
Runtime users, like authorized users, are natural persons granted access to the developments created with Axional Studio’s tools. All licensed users of applications also possess a runtime license, which allows them to make use of developments built by the client. Additional runtime user licensing is only required for those natural users who do not have application usage license and who use “in-house” developments of applications or processes made with Axional Studio’s development tools.
In the “OnPremises” licensing model, in which the program is installed on the licensee’s equipment and facilities, the licensee must also register the equipment and servers. Licensing of the servers depends on the number of processing cores of the equipment on which the program is installed. This type of license is called Licensing by Processor Value Unit (PVU).
Licenses for authorized users and flexible users also grant the right to included PVU licenses. The licensee may acquire additional PVU licenses to reinforce the processing capacity of his equipment, with a maximum of either 200 PVUs or 25% more PVUs than would correspond to the number of licensed authorized users. For example, if the licensee licenses 200 authorized users of a product, which would give him server usage rights up to 400 PVUs, then the licensee could acquire up to 200 additional PVUs.
If the processing capacity required for the servers would make the use of additional PVUs over the “25% more” limit necessary, then the licensee will need more authorized user licenses to cover licensed servers’ requirements. Referring back to the previous example, if the licensee needed to license servers for 1000 PVUs, then he would need to license a total of 400 authorized users and 200 additional PVUs, despite the fact that the number of natural users on the system will be fewer than the 400 licensed authorized users.
In view of the n-tier architecture of the program, each one of the servers on which it is installed functions as a redundant copy of the others. Therefore, special cases of unlicensed backup servers are not allowed. The licensee should license a sufficient number of servers for normal operation and to support the burden if one server fails.
PVU, or Processor Value Unit, is a unit of measurement by which each program in the OnPremise model must be licensed. The number of usage rights per PVU required is based on processor technology (defined in the PVU Table) and the number of processors available. For the purposes of PVU-based licensing, ‘processor’ is defined as each processing core within a chip. For example, a dual-core chip has two processors. The licensee must acquire enough PVU usage rights to cover all activated cores within the hardware available to or managed by the program.
The licensing rules associated with product use on virtual servers also use the Processor Value Unit (PVU) method, treating the virtual cores assigned to a virtual server as if they were physical server cores. Therefore, to license virtual servers, each guest server must be licensed according to its number of assigned cores, regardless of the actual number of cores available to the physical host server. The PVU value of each virtual server core is equal to the value of the type of processor installed on the host machine. In exceptional cases when justified, Deister can explicitly grant a particular client a type of peripheral licensing for exclusive use, in which only the host server cores will be licensed regardless of the number of virtual guest machines.
Licensing of the Development Platform (Axional Studio)
Axional Suite provides a platform for users who want to develop custom applications. For that purpose, the users must have an Axional runtime license.
Source Code Licensing
Certain products in the portfolio are delivered along with the source code that comprises them. This source code is protected by a reference license and is considered confidential information. It is delivered exclusively to the licensee as a reference for examination and review, but its modification, distribution or disclosure are not permitted by any means.
The ability to review the source code and make changes or adjustments to the programs does not grant the licensee rights to technology developed at the time of licensing, or any rights to possible later developments. Improvements, alterations and developments made using the existing source code do not grant any intellectual property rights to the licensee, nor do they permit the formulation of patents, redistribution or resale, even if rights are restricted to existing developments.
|Axional ERP Lite|
|Axional Studio Runtime|
Available Not Available Required
Prices as of January 2015
|Product Family||onPremises Software Rental||onDemand Software Rental|
|Metric||Monthly price per user||Monthly PVU price||Monthly price per user|
|Axional ERP||Nominal Users||200 €||–||250 €|
|Axional ERP Flexible||Nominal Users||50 €||–||60 €|
|Axional ERP Lite||Nominal Users||60 €||–||80€|
|Axional Analytics||Nominal Users||90 €||–||150 €|
|Axional Mobile SFA, PUD||License by Device||49 €||–||59 €|
|Axional Mobile POS||License by Device||49 €||–||59 €|
|Axional Mobile WMS||License by Device||49 €||–||59 €|
|Axional Middleware||Nominal Users||100 €||–||110 €|
|Axional Studio Runtime||Nominal Users||40 €||–||75 €|
|Integration Bus||Remote Connections||15 €||–||25 €||Server Backend||PVUs||–||5 €||–|
|Server Frontend||PVUs||–||5 €||–|
|Axional VLDB||PVUs||–||100 €||–|
Support and Maintenance Service
Deister includes support for its programs in the various subscription-based licensing models. While subscription-based licensing is in effect for licensed programs:
- Deister will provide and authorize the use of the latest commercially-available version of the licensed Product.
- Deister will provide routine assistance: respond to simple questions about installation or use of the product and code-related issues (“Support”). This support for a specific version of the program will be available only for as long as [Deister] or a third party, if applicable, keeps supporting that version (See the Product Life Cycle Policy). When the supported version’s life cycle ends, an upgrade to a new version of the program is required in order to continue receiving support.
- Deister offers telephone assistance as well as, if available, remote connection to the staff or advanced users during the support center’s hours of operation.
- Deister may ask the licensee for access to their computer systems via remote connection in order to isolate the cause of the problem. The licensee remains responsible for adequately protecting their systems and all data contained therein when Deister accesses remotely with their consent. This clause is not applicable to the onDemand licensing model, as in that case the equipment and infrastructure are supplied by Deister.
The support and maintenance service does not include assistance with:
- The design and development of applications and new product functionalities.
- The use of the program outside of the agreed-upon environment.
- Errors caused by programs for which [Deister] is not directly responsible according to this agreement.
Glossary of Terms
To help clarify the meaning of terms used in this document, please read the “Licensing Glossary“.