APIs & SDKs for geographical & logistic needs
We know developers want two things: seamless integration and satisfied software users. PTV xServer equips developers with the tools they need to do just that. Select from and combine a large range of components, plugins, and APIs for all your logistical and geospatial needs including geocoding, digital maps, routing, optimisation and much more.
Geocoding API
Convert addresses to geocoordinates and vice versa with high accuracy
What is the purpose of geocoding?
Geocoding is the process of converting addresses into sets of latitude and longitude coordinates and vice versa. It’s a prerequisite for all geolocation-based applications: It enables you to search and precisely display geographic locations on digital maps. Therefore, geocoding is the foundation for all mapping and vehicle routing and optimisation tasks.
Why geocode with PTV Geocoding API?
The PTV Geocoding API is a software developer component, available as a cloud-based web service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing software architecture. It handles geocoding requests quickly – for individual locations as well as for entire databases. The PTV Geocoding API offers maximum flexibility and highest precision: It allows you to enter address information without specific formatting requirements. We provide a highly accurate database, enabling perfect matching of geocoordinates and geolocations. Moreover, we supply detailed geocoding documentation as well as continuous training and support.
Enter information using either free-form or structured input
As user of the PTV Geocoding API, you benefit from maximum flexibility: Use free-form input to enter addresses without considering the order of address elements, or use the structured input to determine the match quality of the single address elements.
Use forward and reverse geocoding
In forward geocoding, you start with an address or point of interest and end up with the corresponding coordinates consisting of a latitude and longitude. In reverse geocoding, you request a geographic location based on its coordinates. Our geocoding web service matches geocoordinates and addresses with highest precision.
Use batch geocoding to process large amounts of data at once
Batch geocoding enables you to group addresses and geocode them together. Due to less protocol overhead, you benefit from reduced network traffic and are able to geocode your whole database at once.
Apply address verification to spot errors before they cause problems
Address validation checks your input data and evaluates the match quality of input and output to help you choose the correct address. This way you can be sure that you’re always working with up-to-date and clean data and avoid inefficiencies.
Rooftop accurate geocoordinates
The precise physical geocode of a delivery point may differ from the interpolated geocode for that same address. Thanks to rooftop geocoding with the PTV Geocoding API, you identify the exact latitude and longitude of an address, and are able to “put the pin” right in your customers’ driveway. This way, you can be certain that your drivers arrive exactly where they need to go and avoid searching for delivery entrances at their destination.
Postcode search API that handles all available formats
Regardless of length and formatting: Our postcode search API reliably locates postcodes globally.
Geocoding API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn't switched APIs recently? Then you're most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it's designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Digital Maps API
Display geographical data and traffic information on interactive and customisable maps
What are digital maps good for?
Digital rendering – often referred to as digital mapping – is the process of visualising geographic data on digital maps. While early digital maps contained the same cartographic information as scanned versions of paper maps, the expansion of GPS has added many functionalities to digital maps, like the possibility to include points of interest and other location-based datasets. Digital rendering is a prerequisite for all geographical and logistical functions and crucial for tasks such as vehicle routing and optimisation.
Why integrate PTV xServer Digital Maps API?
PTV looks back on four decades of experience in the field of digital maps and works closely with leading data and maps providers. Additionally, we have been solving challenges within transportation logistics for international customers for 40 years. We offer highest data quality and level of detail, a large amount of extended content and functionalities, and many options for customisation and individual tailoring of map look and feel. For instance, our map data includes highly detailed and accurate truck-specific information like weight limits for bridges, height restrictions for tunnels and access restrictions for trucks – particularly relevant in urban areas. Our Digital Maps API is a software developer component, available as an easy-to-use and integrable on-premise solution or a cloud-based web service. Due to its standardised interface, the component can be easily integrated into an existing software architecture. Additionally, as developer, you benefit from abundant documentation as well as continuous support.
Configure your map display or use pre-defined map profiles
Our Digital Maps API enables you to configure the map display based on your requirements and taste. You would like to start working with the API immediately without making any modifications? No problem. We offer several pre-defined map profiles that are carefully designed to fit most standard use cases as an out-of-the-box-feature.
Visualise time-dependent data
Choose between different options for displaying time-dependent data: Either pick a point in time or a time span and visualise all valid data that matches your time preference.
Localise your digital map with country-specific map configuration
We offer standard map profiles for different countries and continents. In these standard map profiles, the visible icons and descriptions are localised accordingly.
Build hybrid maps with single map layers
Request single layers to build your own hybrid map. Choose between pre-defined layers (e.g. background, labels, additional content layers displaying information like truck-specific attributes or live traffic information). Change the order of layers to draw the polyline of a route between streets and labels.
Display additional content data
We provide a lot of additional premium content and data such as statistical and time-dependent absolute speeds, truck-specific driving restrictions and real-time or forecasted traffic events. The Digital Maps API enables you to visualise this premium content to make optimum use of our logistical algorithms.
Digital Maps API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it’s designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Route Planning API
Plan and optimise truck-specific routes
Why truck-specific routing?
Various online-platforms offer free and easy-to-use route calculation. Professional truck and vehicle routing, however, provides much more than that. Many specific requirements and challenges need to be taken into account when optimising routes for commercial vehicles: Truck attributes like size, weight and speed profiles, access restrictions in inner-city areas, toll costs, legal provisions like driving times and rest periods as well as time restrictions such as opening hours of ramps and depots are just a few examples. Additionally, the route with the shortest travel time may not be the fastest or most fuel-efficient route. All these factors turn route optimisation for trucks into a real challenge. In transport logistics, however, efficiency is key in ensuring profitability and sustainable business success. Therefore, it is crucial to ensure that commercial vehicles always take the optimal route available.
Why plan routes with PTV xServer?
The difference between freely available online tools and the routing optimisation components by PTV xServer lies in their ability to factor in all truck-related data and requirements: Since our founding four decades ago, we have accumulated abundant truck-specific data and acquired expert knowledge in optimising truck-specific routing. PTV xServer offers developer components that can be easily integrated into your existing system architecture and expands the routing capacities of your transport logistics software. The components are available as easy-to-use and integrable on-premise solution and as an even more powerful cloud-based web service for the most advanced use cases. Additionally, as developer, you benefit from abundant documentation as well as continuous support.
Customise vehicle profiles to your needs or use standard reference profiles
Our Route Planning API allows you to customise vehicle profiles to your requirements or work with standard reference profiles. The standard reference profiles include continent-specific features like official weight classes in Europe, North America or Australia (EUR, NAM, AUS).
Calculate exact freight and tolls costs
Calculate exact toll costs based on vehicle attributes when planning routes and determine when toll-free routes are a viable alternative.
Time consideration modes
Factor start or desired arrival times into your routing. Specify schedules and timespans for longer periods, such as roadworks, to be considered in your planning.
Use on- and off-road waypoint types as part of your routing
Define waypoints on the road or off the road (e.g. buildings or facilities beside the road). Determine whether the distance between on- and off-road waypoints should be calculated as part of the route.
Consider relevant truck attributes
The PTV Route Planning API considers all relevant truck-specific attributes like length, height, weight, special cargo and access restrictions when calculating the optimum truck route. Additionally, it factors in live traffic information and traffic patterns to avoid congestion and circumvent bottlenecks.
Calculate exact emissions
Calculate exact emissions based on vehicle attributes and recognised standards like CEN, HBEFA, CO2e, COPERT.
Plan breaks under consideration of official or your own set of rules
Consider legal or your own set of rules regarding break and rest times and factor them into your route planning.
Route Planning API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn't switched APIs recently? Then you're most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it's designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Toll Calculation API
Make sure your trucks are always driving on the most economic route
Why calculate toll in advance?
Since toll roads and tunnels have become common in most of Europe and North America, toll constitutes a significant share of overall transport costs. By reducing tolls, transportation costs can be decreased considerably. Precise toll calculation is the first step in this: Already factor applicable toll charges in when planning truck routes, compare alternatives, avoid toll roads if it makes sense and thereby make sure your trucks are always on the most economic available route.
Why calculate tolls with the Toll Calculation API by PTV xServer?
The PTV xServer Toll Calculation API is a software developer component, available as a cloud-based web service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing software architecture. It exactly and reliably determines applicable tolls when planning truck routes. Our database contains precise and up-to-date information on toll roads in most of Europe and North America. As soon as future increases are announced, they are updated in our database and considered for future trips. Sometimes it may make sense to take a small detour to avoid toll roads. The PTV Toll Calculation API balances time savings of toll roads and cost savings of detours and suggest the optimum route for your preferences.
Precisely calculate toll costs
Calculate precise toll costs based on the vehicles’ specifications. Forecast toll costs for future trips by factoring in soon-to-come toll cost increases.
Consider different payment methods
Toll charges often vary depending on the payment method chosen (e.g. cash, credit card, electronic toll collection). The PTV Toll Calculation API takes the specified payment method into consideration and calculates your exact toll tariffs based on that.
Figure out when to avoid toll roads
Use the PTV Toll Calculation API to recognise and – if it makes sense – avoid toll roads within the route calculation.
Toll Calculation API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it’s designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Emissions Calculation API
Calculate and report your fleet’s emissions
What are the benefits of emissions calculation and reporting?
Between the Diesel scandal and the Paris Agreement, the last few years have been characterised by an increase of public scrutiny with regards to pollution control. What does this mean for the logistics sector? It means that more restrictive transport policies, especially regarding nitrogen and carbon emissions, are on the horizon. Curbing fuel consumption by optimising vehicle routing and minimising mileage is of course an integral part of reducing your fleet’s carbon footprint. However, we can expect more and more countries to implement mandatory emissions reporting programmes to systematically measure and monitor emissions. By then, the ability to accurately calculate and report all emissions, specifically CO2 and nitrogen, will become a deciding factor in your company’s success.
Why work with the Emissions Calculation API by PTV xServer?
The PTV xServer Emissions Calculation API is a software developer component, available as a cloud-based web service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing software architecture. It takes a wide range of relevant factors into account: Actual mileage, truck attributes, vehicle classes, fuel consumption, the load and further important conditions like the gradient of a route. It calculates your fleet’s emissions footprint based on relevant standards, such as HBEFA or CEN, and gives you a detailed and exact overview of your emissions. This way, you can be sure to be in line with current regulations – and prepared for stricter legislation in the future. Moreover, the demand for CO2-neutral products and services is steadily growing. Using the Emissions Calculator API by PTV xSercer enables you to tap into this attractive new market and offer green logistics to environmentally-conscious customers.
Features
Detailed information on usage and emissions
Use the PTV xServer Emissions Calculation API to receive detailed information about energy usage, CO2, Methane and Nitrous Oxide.
Calculate emissions based on all relevant standards
- The CEN calculation based on values from 2011/2012
- The French CO2 decree no. 2011-1336, Article L.1431-3:2011.
- The emissions calculation based on the Australian National Greenhouse Accounts (NGA), factors July 2011 and December 2015.
- The emissions calculation based on the emissions factors provided by the Department for Environment, Food & Rural Affairs in the United Kingdom, factors 2014 (UK DEFRA).
- The emissions calculation based on the Handbook Emission Factors for Road Transport (HBEFA), versions 2.1, 3.1 and 3.2
- The emissions calculation based on the Computer Programme to calculate Emissions from Road Transport (COPERT) Australia software version 1.2
Emissions Calculation API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it’s designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Traffic Information API
Use live traffic and historical traffic data to avoid delays and optimise route calculation and scheduling
Why consider traffic information?
Roadworks, road closures and congestion can cause delays and lead to longer journey times. Circumventing bottlenecks is therefore key in ensuring optimised route calculation and scheduling. Two types of traffic information should be considered in routing: historical and live traffic. Historical traffic information, also known as traffic patterns, represent traffic flows as static speed profiles for specific road networks. To give one example: A road has a speed limit of 80 km/h. However, the actual average speed driven on this road on weekdays between 5 and 7 pm is 30 km/h. Since the delay occurs regularly - at the same time of any weekday – it is referred to as a traffic pattern. By factoring traffic patterns into route calculation, detours can be planned beforehand to minimise the need for spontaneous replanning. Live traffic data, on the other hand, delivers information on traffic incidents, road closures and delays that occur unexpectedly. Including live traffic information into route calculation minimises delays in journey times.
Why should you use the Traffic Information API by PTV xServer?
The PTV xServer Traffic Information API is a software developer component, available as a cloud-based web service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing software architecture. It considers both live traffic and traffic patterns: Live traffic information is visualised on customised digital maps. Traffic patterns are visualised as hydrographs showing the rate of flow versus time of the day. This enables you to gain quick insight into traffic patterns, and based on this knowledge, plan detours before bottlenecks occur. A detour around a bottleneck is not possible or would not make sense? Then, the expected delay is factored into your route plan and the estimated time of arrival is revised.
Consider both historic and live traffic information in your route planning
Historic traffic information, also known as traffic patterns, represents driven speeds on road segments in the past. The live traffic information includes current road restrictions and incidents as well as planned road maintenance and closures in the future.
Save time by automating your data updates
The PTV Content Update Service (CUS) automatically downloads additional data like live traffic information, manages the data status and deletes obsolete data. You can choose both the update method and update frequency.
Visualise traffic information with standardised or customised maps
Configure the visualisation of traffic information on personalised maps based on your requirements and taste. You would like to start working with the API immediately without making any modifications? No problem. We offer standardised map profiles that are carefully designed to fit most standard use cases as an out-of-the-box-feature.
API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it’s designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at API Version 2
Fleet Planning & Optimisation API
Plan, schedule and optimise truck routes to ensure the most efficient use of your fleet
Why use software to plan and optimise fleet use?
Route optimisation is a complex challenge: Imagine you want to plan the optimum trip for one driver who is to carry out five orders in one trip. Even in this seemingly simple scenario, 120 different routes are available. With more vehicles and stops as well as other relevant factors like truck attributes, traffic patterns and time restrictions to consider, the routing problem becomes much more complex and challenging to solve. Optimisation and scheduling software enables you to find the optimum route more easily and to schedule pickups and deliveries for most optimal fleet use.
Why use the Fleet Planning & Optimisation API by PTV xServer?
PTV xServer is global market leader in dynamic route optimisation. No other tool delivers optimal trips that consider both rush hours and roadworks. Our software solutions for route optimisation and scheduling are built on the knowhow and experience from four decades in transport and logistics planning.
No matter how complex your optimisation and scheduling problem – the Fleet Planning & Optimisation API by PTV xServer is up for the challenge. The API is available as a cloud-based web service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing software architecture.
Plan and optimise routes for any fleet size
The Fleet Planning & Optimisation API factors all vehicles, tractors and trailers at your disposal as well as all combination possibilities into route planning.
Factor time restrictions into route planning
Consider legal or your own set of rules regarding break and rest times and factor them into your route planning. Consider additional time restrictions such as opening hours of depots and ramps.
Define your personal optimisation goal
Do you want to minimise vehicle deployment? Distribute the workload equally on your drivers? Regardless of your preferences - the Fleet Planning & Optimisation API calculates the optimum result for your goal.
Consider traffic patterns and ongoing construction
PTV xServer is global market leader in dynamic route optimisation. This means that the software considers rush hours as well as ongoing construction already while planning routes.
Flexibly change trips thanks to live dispatching
Did an accident just occur on your planned route? Did an order got cancelled or added last minute? No problem! The Fleet Planning & Optimisation API enables you to intervene manually when things don’t go as planned to make sure that your vehicles stick the most optimal schedule and route.
Consider relevant truck attributes
Define your vehicles’ attributes (e.g. size, length and weight as well as loading capacity, special cargo and speed profiles). The API delivers the optimum route that considers all truck-specific attributes as well as access restrictions in inner-city areas as well as toll charges.
Fleet Optimisation API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it’s designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Fleet Tracking API
Use GPS tracking to locate your fleet in real-time
What are the benefits of using GPS tracking?
Whether you operate a fleet of rental cars, manage field service staff, optimise routes or oversee high-security transports: GPS tracking enables you to always locate the position of every vehicle in your fleet. This way, you can always keep an eye on your vehicles and cargo.
Why should you employ the Fleet Tracking API by PTV xServer?
The PTV xServer Fleet Tracking API is a software developer component, available as a cloud-based web service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing software architecture. Vehicle trackers transfer the GPS locations to a central system at regular intervals, which then displays them on a digital map. In effect, this means that dispatchers and fleet managers have the data they need, when they need it. This increased level of transparency facilitates the identification of inefficiencies and a more efficient fleet use.
The Fleet Tracking API enables many additional applications, such as:
- Monitoring driving behaviour and performance
- Receiving notifications about punctual arrivals at checkpoints as well as deviations from defined routes or areas (also see Geofencing)
- Comparing planned and driven routes
- Verify bills from subcontractors and toll invoices
- Search for clients, depots and fuel stations in the nearby area
- Emergency buttons (Emergency- and Breakdown-call) and event-driven actions like notifications when vehicles are moved at unauthorised times
Configure your tracking profiles based on your needs or use pre-defined standard profiles
The Fleet Tracking API enables you to configure tracking profiles based on your needs. You would like to start working with the API immediately without making any modifications? No problem. We offer several pre-defined standard profiles, including adapted profiles for dense or sparse signals, that are carefully designed to fit most standard use cases as an out-of-the-box-feature.
Display only the current location or the whole track history of your vehicles
The Fleet Tracking API offers different tracking modes: You can choose to display single GPS points or the vehicles’ whole track history. When displaying full vehicle tracks, you have the option to also show driving direction and speed.
Fleet Tracking API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 will follow soon!
PTV Drive&Arrive API for PTV xServer
Integrate ETA relevant features into your software with the PTV Drive&Arrive API
Connecting the transportation chain with a reliable ETA
Calculating the Estimated Time of Arrival (ETA) of trucks at their destination creates a benefit for all stakeholders of the transportation chain – from shipper, to haulier, to ramp operator (yard or transport manager). It keeps them up-to-date on delays and expected arrival times. Thereby, it enables them to intervene in case of disruptions, plan resources accordingly and reduce idle times. This results in more efficiency for everyone: Ramp operators know when to expect incoming transports and are able to ensure an efficient and balanced use of their resources, hauliers reduce long and unproductive waiting times at ramps, and shippers avoid contractual penalties, while maintaining a high service quality.
Boost supply chain resilience and operational excellence with PTV Drive&Arrive API
The PTV Drive&Arrive API calculates the ETA based on tour information logged in the haulier’s transport management software in combination with the truck's position data (for example collected by the PTV Driver App, available for Android or iOs). In addition, the PTV Drive&Arrive API makes position and arrival information available to all stakeholders of the transportation chain. Offered as part of the PTV xServer Developer Kit, the PTV Drive&Arrive API can be integrated into most transport, fleet, yard and dock management software solutions easily and quickly.
Reliable ETA calculation
PTV Drive&Arrive calculates the ETA based on tour information and position data as well as traffic information and all truck-relevant attributes and restrictions.
Comprehensive data hub
PTV Drive&Arrive bundles position data from the PTV Driver App and other telematics solutions and makes it available to all stakeholders in the transportation chain.
Easy and quick integration
PTV Drive&Arrive comes with a RESTful JSON API that can be integrated into your existing infrastructure to enrich it with ETA relevant features.
Geofencing API
Prevent theft and keep high-security transport safe
What are the benefits of geofencing?
A geofence is a virtual fence for a real geographic area. Geofences can be dynamically generated as a radius around a location, or predefined based on a set of boundaries. A geofence serves as a geographical perimeter: As soon as a vehicle or other valuable objects equipped with a GPS transmitter enter or are moved outside the geofence, managers receive an automatic notification. Geofencing is particularly relevant for high-security transports and functions as an effective deterrent against cargo theft.
Why implement the Geofencing API by PTV xServer?
Due to its standardised interface, the Geofencing API by PTV xServer can be easily integrated into any existing fleet monitoring solution. It enables both geofencing and corridor fencing: While geofencing ensures that vehicles cannot leave a defined territory, with corridor fencing they must stick to a specific route. As soon as the geofencing system detects the GPS signal outside the defined area or route, an automatic action is initiated. This action may be a message, an alarm screen, or even interventions in the vehicle's electronics to prevent it from starting. Our Geofencing API is already in use for the following applications:
- Monitoring of agricultural and construction equipment to prevent unauthorised removal
- Area control for rental cars to prevent driving outside of the agreed upon boundaries
- High-security transports and transportation of money and valuables
- Time-critical transports
Area fencing based on locations
Apply fences around given locations to recognise vehicles entering or leaving your defined area.
Corridor fencing based on routes
Calculate corridors along your calculated routes to determine if your vehicles are leaving the predefined paths.
Geofencing API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 will follow soon!
Field Service Management API
Increase productivity of sales and field force by optimally planning locations, territories and visits
Why is field planning essential?
Determine the ideal location of your next branch, depot or distribution office. Cluster sales and distribution territories that facilitate efficiency. Plan customer visits in a way that minimise driving times: As many different scenarios are possible, solving these optimisation problems is challenging. PTV xServer helps balancing the different factors to find the optimum solution.
The PTV xServer Field Service Management API is a software developer component, available as a cloud-based service or an on-premise solution. Due to its standardised interface, the component can be easily integrated into an existing field management architecture.
Make the best use of your sales resources with smart territorial planning
The PTV xServer Field Service Management API determines the optimal number and distribution of sales territories for you. It factors in sales potential, turnover, number of customers and employee workload and suggests balanced sales territories. Additionally, the API allows you to include framework criteria like existing customer relationships, area size and residential locations of the sales resources. Even natural barriers like mountains, lakes and rivers without bridges or adequate road connection can be considered by using the underlying road network.
Ensure your field staff spends most of their time with your customers
Create visit plans that consider all relevant restrictions, customer requests and visit frequencies. Receive exact daily and weekly schedules, optimised to reduce your employees’ driving times.
Plan optimal locations
Plan depots, branches and offices that are optimally located based on your customers’ location or determine the accessibility based on spatial and temporal distances around your existing location.
Field Service Management API Documentation
API Version 1 is our established solution that is widely used in the market. Your company has been a customer for a while and hasn’t switched APIs recently? Then you’re most likely interested in the documentation on
If you want to see integration samples, you can check them out in the xServer API Version 1 Code Sample Browser.
API Version 2 is the future of PTV xServer as it’s designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
Load Space Optimisation API
Optimise cargo loadings by minimising free volumes and considering unloading sequence
Why use software to plan truck loading?
When transporting less than truckload (LTL) shipments or different container types, optimising use of loading volumes and loading sequence is crucial to remain efficient: Every run a vehicle’s loading volume is not fully utilised, is a loss of revenue. Every extra minute spent at an unloading point, is time lost. Transporting time-sensitive freight as well as fresh and frozen food products, introduces additional constraints since these goods must be delivered within a limited time. Keeping an overview of cargo loadings is difficult. Matching loading sequences with stops along routes further increases the complexity of the loading process.
Why should you optimise load space with PTV xServer?
The PTV xServer Load Space Optimisation API automatically and quickly solves these complex optimisation problems: You simply define the characteristics of the truck's loading space and the transport units. The system automatically delivers a loading space layout, which shows the wall distribution and the location of the individual transport units under consideration of all restrictions. Due to its standardised interface, the API perfectly integrates into other software solutions. For example, you can easily connect it with other PTV xServer components or use it as a stand-alone component with your existing system architecture.
Consider sequencing constraints
Load packages in an order that enables quick and easy unloading and group items together that are destined for the same delivery stops.
Visualise your packing plan in 3D
The PTV xServer Load Space Optimisation API allows you to visualise your packing plan interactively and in 3D. This way, you can view the results from all directions and angles.
Ensure your cargo arrives safely
Take both the allowed orientation of each item or item type and its weight carrying capacity into consideration. This way, you can make sure that your cargo is placed safely for transportation.
Different packing modes
Choose between two packing modes to reduce either the loading meters or your packing time.
Load Space Optimisation API Documentation
API Version 2 is the future of PTV xServer as it's designed in a completely new framework. It is easier to understand and as a programmer, you will benefit from improved flexibility and consistency. If your company recently integrated PTV xServer into their software solution, is still in the middle of it or is planning an integration soon, you should look at
PTV xServer Business Connector for use with SAP©
Integrate geocoding, routing and scheduling APIs into SAP environments with ease
Why you should work with the PTV xServer Business Connector for use with SAP©
The PTV xServer Business Connector is the right tool for you if you want to:
- enhance your SAP-based software system with geographical and logistical functionalities, all while
- keeping installation and configuration time at a minimum,
- mitigating risk of failure, and
- considerably reducing implementation costs.
Integrating the PTV xServer software components into SAP environments such as SAP ERP and SAP TM can easily take a skilled developer a few days. The Business Connector for use with SAP cuts down development efforts considerably and reduces the risk of failure. Both installation and configuration are typically done within less than one day - for on-premise or cloud-based solutions. For you, this leads to significant cost savings.
Moreover, as part of your contract, you receive professional guidance during the integration process as well as ongoing maintenance. We are here for you whenever you need us - with our worldwide support 24/7.
Use cases
- Master database cleansing and address verification
- Routing & scheduling
- Calculation of transport costs
- ETA calculation for lane transports and long-haul trucking
- Invoicing
Benefits
- Seamless integration of geographical and logistical functionalities into SAP systems
- Less development effort and significant cost savings
- Optimal connectivity both as on-premise or cloud solution
- Outstanding service support (24/7) worldwide and professional consultation
- Compatibility between PTV xServer and SAP NetWeaver versions and minimised risks for future enhancements
How does the PTV xServer Business Connector for use with SAP© work?
The PTV xServer Business Connector is designed in two tiers: A developer kit and out-of-the-box solutions.
The developer kit forms the foundation of the out-of-the-box solutions realised as a SAP SDK for ABAP development. In other words, the PTV xServer APIs are transformed into SAP ABAP by using the SAP NetWeaver environment. The APIs are modularly designed and can easily be orchestrated for geocoding, routing and optimisation applications such as address qualification, ETA and cost calculations and optimisation services for fleet or field service management.
Out-of-the-box solutions help implement a performant routing service in SAP ERP and SAP TM embedded in each individual supply and process chain.
The PTV xServer Business Connector is designed in two tiers: A developer kit and out-of-the-box solutions.
The developer kit forms the foundation of the out-of-the-box solutions realised as a SAP SDK for ABAP development. In other words, the PTV xServer APIs are transformed into SAP ABAP by using the SAP NetWeaver environment. The APIs are modularly designed and can easily be orchestrated for geocoding, routing and optimisation applications such as address qualification, ETA and cost calculations and optimisation services for fleet or field service management.
Out-of-the-box solutions help implement a performant routing service in SAP ERP and SAP TM embedded in each individual supply and process chain.
How does the PTV xServer Business Connector for use with SAP© visualise routes?
The PTV xServer Business Connector offers the Shipment Planner, a routing cockpit specifically designed for SAP ERP systems. It enables users to clearly visualise delivery stops, calculate routes and determine related toll costs and emissions. Thanks to real-time visualisation, transport managers can easily identify each trip by adding the incoming shipments. Exact distances, travel times and costs can be computed and provided for any reporting considering a bundle of legal and physical restrictions such as live traffic incidents, vehicle-specific profiles or attributes.
