Licensing

The licensing of PTV xServer depends on the use types, which are going to be described in the next chapters. Altogether, PTV provides user, asset, seat and transaction licence models according to the specific use types.

This page succinctly describes the use and licence types. For more detailed information, please contact your sales partner.

Use types

This section describes the general varieties of use which can be licensed.

Mobile Asset Management

Mobile Asset Management (MAM) applications are information and planning systems for the following situations:

• tracking and tracing
• routing and sequencing with single mobile assets
• planning or optimizing complete tours using a specific number of assets
• cluster respectively territory planning
• load space optimization

In this context, an "asset" is a vehicle, any kind of living thing, a container etc.

Private Network

This use covers simple mapping and routing functionalities that can be integrated into a Private Network solution. It mainly comprises applications for calculating distances, visualising addresses, etc. Routing cannot be licensed as a standalone functionality in Private Network solutions; it must be licensed in combination with geocoding. Routing cannot be accessed without prior geocoding (at least one geocode). The management of assets is also not permitted.

Public Network

This use covers simple mapping and routing functionalities that can be integrated into a Public Network solution. It mainly comprises applications for calculating distances, visualising addresses, etc. Routing cannot be licensed as a standalone functionality in Public Network solutions; it must be licensed in combination with geocoding. Routing cannot be accessed without prior geocoding (at least one geocode).

Telematics

This use covers the running of PTV xServer within a telematics application. It includes the following functions: concierge services, e-calls (emergency calls), b-calls (breakdown calls), stolen vehicle recovery and pay-as-you-drive applications.

Call Centre

This use covers the running of PTV xServer to process customer inquiries at call centres. For example, call centres may perform POI searches to help a caller find the nearest service provider to the caller's current location. Example: a phone book publisher offers a call centre service to help callers find the nearest company using a map application based on PTV xServer. For this use, the prices are set per seat. This use does not include supplementary telematics services, such as concierge services, e-call, b-call, vehicle tracing or MAM. In this case, a seat is defined as follows: a single licence available on a hardware device, which can be provided to several users.

Licence Models

These are default licence models for the developer components offered by PTV.

Transaction-based Licensing

The price is generally defined per month and 1,000 transactions, which is primarily used for the "Public network" use type.

What is a typical Public Network application?

"In the context of use types, Public Network solutions are open portals which integrate PTV xServer as developer components for web services covering simple geocoding, mapping (also POI display) and routing functionalities. Typical examples are dealer locators, route planning or corridor search. This licence model doesn't include vehicle-related applications such as sequencing, trip planning, tracking and tracing, call centres or other telematic applications. This use type can neither be licensed for applications connecting hardware devices with the corresponding sensors, such as navigation systems, nor used as a commercial product or as an in-vehicle component."

Asset-based Licensing

Assets must always be licensed if a use case can be traced back to assets (mobile objects such as HGVs, cars, caterpillar vehicles, people, etc.) or a fleet, regardless of whether or not the licensee owns or possesses the assets. Typical use cases for licensing assets would be, for example, the visualisation of mobile assets in map or automated route planning (manual, semi-automatic or automatic allocation of orders/shipments to one or more routes).

How do I calculate the number of assets?

"Every asset that may be shown or planned as part of the use case (regardless of whether it is part or not) must be counted on a monthly basis. The sum of the assets equals the number of assets which must be licensed for the given month."

Third-party vehicles
"If third-party vehicles are included in your own system, then the regulation described under own vehicles applies. For use cases in which the trips are planned but where the assets (vehicles) being used are unknown, the trips are counted as assets according to the model below:"

User-based Licensing

According to the licence conditions, the application is permitted to be used by a fix number of "named" users, who have exclusive access to the application. This licence model is generally used for Private Network applications.

What is a typical Private Network application?

"Private Network solutions are applications in a company network with precisely defined user groups or applications which have controlled access for a closed user group on the Public Network. They include the integration of mapping and routing in a CRM system and the mapping of customer addresses in an in-house system. Sequencing and tour planning is generally excluded."

Seat-based Licensing

An authenticated seat is defined as follows: a single named workstation, which can be used by several users. This licence model is generally used for call centre applications.

What is a typical call centre application?

"This use type covers the running of PTV xServer to process customer inquiries at call centres, with the exception of telematics services."

Special Licensing Notes

PTV xServer internet consists of a subset of PTV xServer, specific maps and data content with "free access for test purposes". Free access means there is no technical restriction or limitation, like with a licence file. Test purposes are only defined by the transaction volume listed in the table below.

For PTV customers with a product licence, the limitations are valid as described in their individual purchase contract. PTV control is by log file analysis. Depending on the unlimited access, the use of additional data content with costs will be invoiced. More details are described in the Data Content section.

Definition of a transaction

A transaction is simply a specific billing request sent to the corresponding PTV xServer component. The equivalent (successful) response will be used for the invoicing. The quarterly reports are therefore required to count the number of transactions which are to be invoiced. All these lists of relevant billing information are stored in log files which are automatically generated by the PTV xServer. In principle, a transaction is counted for billing purposes when a service method is called. But there are exceptions, as shown below! The following tables provide a list of existing methods, with their corresponding numbers of transactions subject to invoicing (=0: no costs; =1: each call is one transaction; >1:

PTV xLocate Server

Example

// Headline
2012-02-09 12:59:39,442;INFO;RequestTimes;id;client host;user;port;clusterId;
service;success;log1;log2;log3;profile;pool instance;deserialization;input trafo;
module queueing;module time;output trafo;serialization;total inner;total outer;
transaction;use-cases;ref-coord 1;ref-coord 2;dynamic provider;dimensions;
additionalInfo;errorType;errorCode;errorMsg

// Transaction
2012-02-09 13:02:17,779;INFO;RequestTimes;req-44-1328788937604;127.0.0.1;warmup;
50020;unknown-cluster;XLocate.findAddress;true;;;;default;xlocate.1;1;0;150;23;0;
1;173;175;NO-TXN;locating-NL-4;4315187.91094791,5582915.029649917;;;1;;-;-;-

PTV xMap Server

Example

// Headline
2012-02-08 14:37:56,966;INFO;RequestTimes;id;client host;user;port;clusterId;
service;success;log1;log2;log3;profile;pool instance;deserialization;input trafo;
module queueing;module time;output trafo;serialization;total inner;total outer;
transaction;use-cases;ref-coord 1;ref-coord 2;dynamic provider;dimensions;
additionalInfo;errorType;errorCode;errorMsg

// Transaction
2012-02-08 14:37:56,967;INFO;RequestTimes;req-1-1328708269452;127.0.0.1;unknown-
http;50010;unknown-cluster;XMap.renderMap;true;;;;default;xmap.1;319;91;0;6673;
3;418;6767;7504;NO-TXN;geodatasource: default.points-of-interest.restaurants;
4303250,5486055;4303250,5486055;;400,400;;-;-;-

PTV xRoute Server

Example

// Headline
2012-02-09 13:12:54,709;INFO;RequestTimes;id;client host;user;port;clusterId;
service;success;log1;log2;log3;profile;pool instance;deserialization;input trafo;
module queueing;module time;output trafo;serialization;total inner;total outer;
transaction;use-cases;ref-coord 1;ref-coord 2;dynamic provider;dimensions;
additionalInfo;errorType;errorCode;errorMsg

// Transaction
2012-02-09 13:12:54,710;INFO;RequestTimes;req-1-1328789567645;127.0.0.1;unknown-
http;50030;unknown-cluster;XRoute.searchForReachableObjects;true;;;;default;
xroute.1;181;0;0;6670;100;93;6770;7044;NO-TXN;traffic: default.traffic, 
geodatasource: default.points-of-interest.restaurants;;;;;;-;-;-

PTV xServer add-on AJAX Maps

Copyright © 2024 PTV Logistics GmbH All rights reserved. | Imprint