The PTV xServer Family

The PTV xLocate Server finds the geographic coordinates for addresses (geocoding) or provides the addresses that are closest to geographic coordinates (reverse geocoding). The results obtained with the PTV xLocate Server can be used for further processing in other applications, e.g. with other PTV xServer. For instance, the data will be shown in the form of addresses on a digital map, used as a start, via or destination point for route calculation.

Moreover, the PTV xLocate Server can be used to search for POIs that are close to a coordinate.

The PTV xLocate Server is a software component, i.e. it has interfaces that allow the transfer of data to the PTV xLocate Server, call functions and transfer results back to another system.

The PTV xLocate Server can be integrated into your existing application environment.

The big five

1. Address classification: Use the additional fields to validate your candidates in relation to the input or put your result in an order according to the total score.
2. Batch geocoding: Define the locations for a huge amount of addresses in one call in order to update your specific address database.
3. Reverse geocoding: List the best candidates depending on town categories (capital city, big, medium or small cities etc.).
4. Fuzzy search: Consider misspelling and find the correct address.
5. Choose between multi- and single-field search.

The PTV xRoute Server calculates routes between several points for further use in other applications. The routes are generally provided via network connections. The digital maps are based on PTV map material.

The PTV xRoute Server is deployed where distances, driving times or route costs must be calculated. Live traffic information, traffic patterns, toll scenarios and emissions (HBEFA 3.1) can be taken into account. Furthermore, functionalities like RoadEditor, combined transports, isochrones calculation with time-distance events and matrices computations are part of PTV xRoute Server.

The PTV xRoute Server is a software component, i.e. it has interfaces that allow the transfer of data to the PTV xRoute Server, call functions and transfer results back to another system.

The PTV xRoute Server can be integrated into your existing application environment.

The big five

1. Dynamic routing: Calculate alternative routes according to the historical traffic information based on FCD or actual traffic incidents via TomTom HD Traffic.
2. Benefit from PTV's premium data such as tolls, truck attributes, emissions, preferred routes and much more.
3. Define your specific vehicle profiles (car or truck) to receive the best routing results.
4. Calculate your tour taking your driver regulations into account.
5. Define your corridor along a route and add all reachable objects according to time or distance.

The PTV xMap Server uses digital maps to create map sections for further use in other applications. The map sections are generally provided via network connections. The PTV xMap Server interacts with other applications: This allows users to enlarge maps, move them, etc. The digital maps are based on PTV map material.

The map sections created are defined by:

• One or several points that shall be displayed in the map center;

• A rectangle that limits the size of the map section.

The PTV xMap Server is deployed (frequently together with other PTV xServer) where information must be displayed on a map: e.g. customer addresses, locations, routes, vehicle positions or sales territories.

The PTV xMap Server is a software component, i.e. it has interfaces that allow the transfer of data to the PTV xMap Server, call functions and the transferring of results back to another system.

The PTV xMap Server can be integrated into your existing application environment.

The maximum default image size is 3840 x 2400 (4 x 1920 x 1200).

The big five

1. Design your own map profile.
2. Profit from "on-the-fly" rendering at considerable speed.
3. Draw all specific data content such as routings, municipal boundaries, LOS (level of service regarding the traffic flow), preferred routes, customer specific objects etc. onto your map. Select between server- and client-side drawing.
4. Use the international codes drawing the country specific characters (Cyrillic, Greek characters etc.).
5. Integrate map controls such as AJAX Maps or frameworks such as PTV xServer .NET to interact with the PTV xMap Server.

The PTV xMapmatch Server matches a list of geocoordinates (aka a track) to a given map, thus connecting the input positions to the given road network. The results obtained with PTV xMapmatch Server can be used for further processing in other applications, e.g. with other PTV xServer. For instance, it is possible to show the data in the form of a list of segments on a digital map, or use it to verify where exactly a specific vehicle was driving.

The PTV xMapmatch Server is a software component, i.e. it has interfaces that allow transferring data to the PTV xMapmatch Server, call functions and transfer results back to another system.

The PTV xMapmatch Server can be integrated into your existing application environment.

The big five

1. Match the exact route from your GPS trace.
2. Check your speed in comparison to the legal rules.
3. Switch between local (matching without considering previous positions) and global mode (consider historical data/GPS positions).
4. Pay as you drive: local matching and data processing in view of real distance driven.
5. Fleet management solution: match and post data processing in your own data center. Detailed cost analysis by using PTV xRoute Server for target/actual comparison.

The PTV xDima Server calculates distances and driving periods between many different locations. The calculation results are in the form of distance matrices. These matrices store the calculated routing results and can be called up from other systems without the need to calculate the routes again.

A distance matrix consists of the following elements:

• Locations
  A location is a geographical point. The position is described by x and y coordinates of the relevant planning objects.

• Distance tableA distance table contains the distances and driving periods between all locations included in the distance matrix. These data are persistent and can be extended with distances and driving periods between additional locations if required.

• Profile
  A profile consists of the distance calculation settings, such as the vehicle type or speed configurations.

This is important, for example in the case of an optimisation problem like trip planning. The distances and driving periods between the planning objects like depots or customers are called up millions of times by the algorithms. A pre-calculated distance matrix reduces the calculation time enormously.

PTV xDima Server

• calculates and manages distance matrices efficiently

• provides fast access to distances and driving periods between different locations

• imports distance matrices from external sources to use them in PTV products

• exports distance matrices that can be used by other systems without the need to access PTV xDima Server

The PTV xDima Server is a software component, i.e. it has interfaces that allow the transfer of data to the PTV xDima Server, call functions and transfer results back to another system.

The PTV xDima Server integrates into your existing application environment.

Please note that the distance table does not include detailed route descriptions like polygons.

The PTV xDima has been developed to calculate distances and driving periods between many different locations efficiently. In doing so, the calculation considers the selected routing parameters (e.g. the vehicle profile or the speed profile). The result of the calculation is a quadratic nxn matrix.

This matrix is permanently stored on the hard disk. So you have access to the distances and driving periods between the locations at any time, even after a restart of the PTV xDima Server. The PTV xDima Server is therefore a stateful server.

A service for clustering a certain number of orders according to the defined rules (number of clusters to be created, considering weekday patterns or multi week rules). The order contains a set of parameters to define various values such as quantity, location, visits per week or weekly rhythm. Furthermore, the order contains one or more visits in compliance with the selected method. The following methods are selectable to fullfil various requirements:

Type	Description
Basic: plan clusters	A set of orders will be clustered according to the defined number of clusters. An order corresponds to one visit. The clustering performs the best compactness and best balance of the total quantity (potential value such as service period or turnover) for each cluster.
Advanced: plan visits for one week	A set of visits will be clustered for one week according to the specified weekday patterns. An order contains one or more visits within that week. Each visit is therefore assigned to one weekday.
Advanced: plan visits for more than one week	A set of visits will be clustered for multi-week according to the weekly rules. Again, an order contains one or more visits within these weeks. Each visit is therefore assigned to one day and every day corresponds to one cluster.

A tour is usually depot-related, that means a vehicle starts at a depot, then serves transport orders and finally returns to a depot. Besides the planning of round tours more tour structures like start-depot-free tours are possible. Furthermore the planning considers multiple depots, so the PTV xTour Server assigns transport orders to depots and groups the orders to vehicle tours. After that, the sequence of the orders within the vehicle tours is calculated.

During the optimisation, there are a lot of restrictions to consider: Vehicle capacities and equipment, trailer and trains, customer and depot opening hours, dynamic loading period calculation, break and rest rules, additional break intervals, tour limits like a maximum transport order count, transport order priorities and product incompatibility to mention a few examples.

The tour planning algorithm permanently needs the distances and driving periods between all locations. As it is too time consuming to calculate the routes again and again in every planning step, the PTV xTour Server creates a distance matrix immediately before the tour planning and stores it on the hard drive.

The PTV xTour Server is a software component, i.e. it has interfaces that allow the transfer of data to the PTV xTour Server, call functions and transfer results back to another system. The PTV xTour Server can be integrated into your existing application environment.

The big five

1. Select between sequence and tour optimisation considering several constraints such as time windows, driver regulations, capacities etc. Take the rest and break rules into account in line with the EU or German regulations.
2. Use high-performance routing for fast distance matrix calculations which are the basis for any tour planning.
3. PTV provides a set of heuristics to plan and optimise the complex requirements of a tour (planning in the open countryside, considering an input plan, area planning, balancing etc.), and give results near to the optimum solution.
4. Use the proposal functions to receive a computed proposal for several use cases, such as to find the right vehicles for a tour or the best matching tours for one vehicle.
5. Calculate overnight tours based on a single vehicle.

The big five

1. Calculate a desired number of clusters in accordance with the specified locations. In this way, large amounts of data are processed efficiently and quickly.
2. Add the customer locations, thereby calculating new areas, or fill in existing clusters.
3. Please note the activity measurements and create compact, coherent and balanced clusters.
4. Use the free (CBC) or commercial solver (Gurobi) in order to achieve either convenient or quick optimal territories.
5. There are no limitations with regards to the planning size.

The big five

1. The cargo space is optimised within a few seconds after the route is planned.
2. Find the suitable configuration in order to produce the required temperature zones.
3. Consider the order of the transported goods in accordance with the principle "last in, first out".
4. Configure the dimensions of your vehicle. In this case, note the number of available containers and the number of required chambers, taking the position of the cooling units into account.
5. Map standard transport units, such as palettes or roll containers.