PTV xCluster Server / PTV xTerritory Server


The PTV xCluster Server divides existing orders or customer calls into homogeneous territories. This is particularly useful for customers who are called upon several times within the planning period. The groups are put together using the geographical regiion and other criteria such as the call duration so that a perfect utilisation of personnel and fleet with an optimum customer call frequency is achieved.

PTV xCluster Server creates clusters that fulfil two goals:

  • Geographically compact territories: orders or customer calls are grouped into the most geographically compact territories possible, which produces shorter trips. Customers located near one another are assigned to the same territory wherever possible. The calculation is based on road distances or travel times.
  • Well-balanced clusters: the clusters should be roughly equivalent to one another in terms of activity measures (e.g. number of calls, revenue potential, call duration).

Example trip planning:

A two-week plan consists of ten day trips (two weeks with five business days each). PTV xCluster Server will split up all the customer calls scheduled for these two weeks into ten clusters - one cluster per day trip. Afterwards it considers visiting patterns during the week (e.g. Monday and Thursday) and across several weeks (e.g. every 14 days). The clusters are beeing created in a way that each call is assigned to one, and only one, cluster. That means if customers are visited twice a week, they will be assigned to four different clusters in our example. Once the clusters are generated, the ideal sequence of stop-off points can be determined with the PTV xTour Server.


  • Create clusters of (repeating) orders or customer calls on the basis of route or driving time
  • Plan new territories from scratch
  • Re-assign existing locations to territory centres
  • Improve an existing territory structure
  • Compact territories for short trips
  • Balanced clusters for balanced employee workloads, sales potential etc.
  • Certain relationships can be defined as fix, if needed
  • Simple integration using standardised interfaces (XML/SOAP/JSON)
  • Scalable Performance
  • Active support of Multi-processor systems

 System requirements

Please find the latest system and hardware requirements in the Online Manual which is located in our DeveloperZone.