A more detailed descripton about this Feature Layer and what you have to do to use it, you can find on our blog post How to use Feature Layer Truck Traffic Patterns. If you have any further questions about the Truck Traffic Patterns don’t hesitate to contact the Support Team
The new Feature Layer TruckTrafficPatterns was released recently with the new PTV Europe City Map Premium 2016.1H. Everything you have to know to get started is explained here:
The Truck Traffic Patterns are derived from (car) Traffic Patterns, influenced by many other data like height data, truck speed limits or passing restrictions. Route calculation for trucks considering typical traffic situation at a certain week day and a certain time of day can be done with this Feature Layer. To visualize this traffic situation the according route segments are colored. But because of the reason that the focus of truck routes is on major roads the coloring of segments is not realized for lower street levels. Moreover it is important to use either the TruckTrafficPatterns or the (car)TrafficPatterns at the same time!
Furthermore you have to know that TruckTrafficPatterns and TruckSpeedPatterns are the same Feature Layer and that they are used synonymously. TruckSpeedPatterns is used for the theme name and all including files. In every other case the name TruckTrafficPatterns is used.
What do I need to use it?
- It is important to know that you have to adapt the vehicle profiles truckfast.xml, truckslow.xml, default.xml and trafficinfoloader.xml to use this Feature Layer. In the Dynamic Routing section you have to deactivate/delete the SpeedMapping because this would falsify the routing times. Furthermore there is a new Feature Layer Theme available, called PTV_TruckSpeedPatterns
- License: Each Feature Layer theme must be licensed separately and for each PTV xServer
Where can I get it?
The Feature Layer can be downloaded from the customer area of the PTV Developer Zone (login required). Soon, there will be the documentation How to use Feature Layer TruckTrafficPatterns in the online manual of the PTV xServer. If you need further information or support please contact the Support Team.
The Truck Traffic Patterns are derived from (car) Traffic Patterns, influenced by many other data like height data, truck speed limits or passing restrictions. Then, considering of traffic situations in the route calculation will be also available for trucks.
More detailed information about this Feature Layer, e.g. when it is available and how to use it, you will get in this blog and in the manual on time.
Incompatibilities ensure that certain locations are kept separate to certain territories during the location assignment. A typical use case are sales representative that should not serve certain customers or field worker with specific qualifications. So an incompatibility is a property that disqualifies a location for certain territories.
Needs and Benefits
To distribute locations with incompatibilities a PTV xTerritory Server has to be installed and if applicable, a High-performance routing network for calculating routes. With these prerequisites you have the possibility that during the distribution of locations to territories, incompatibilities between locations and territories can be taken into account.This enables you to depict real customer relationships during the planning process. The incompatibilities have to be set as properties in the locations.
There is also an use case documentation for this new feature available. This was the last post of our PTV xTerritory Blog Series and if you want to know more about the PTV xTerritory features and also about the other new features of the PTV xServer 1.20.1 release I recommend you to join our webinar that will be presented on Tuesday. During the webinar you have the opportunity to ask your questions that you might have after the blog series or you maybe will get in the webinar.
Further information about all PTV xServer you can find on our product site.
In our last post we indicated that activity limits can have a major impact on the tour estimation by setting for example TourPeriodLimits for each territory. By setting activity limits in general you ensure that the sum of all its activities is roughly constrained. Because a territory can only have exactly one limit assigned, the entire territory will be limited by this single constraint on the basis of the sum of all its activities. Having multiple limits constraining one and the same territory is therefore not possible. Furthermore one limit has to be uniquely assigned to one territory.
Why is this useful?
- Limits give more fine-grain control over the calculation process during territory planning, location assignment and change territories by optionally limiting the sum of activities within territories.
- Limits constrain the sum of activities of territories (for each territory individually by a unique limit) to fit to individual site conditions or employee experience.
Activity limits when planning territories
The following sample scenario will help you to understand how territories can be limited right from their initial planning by using exact limit values.
- There are three existing locations, each given with the following
- Location A:
activity = 60.0
- Location B:
activity = 50.0
- Location C:
activity = 30.0
This totals to an overall sum of activity of 140.0 for all three existing locations.
- Location A:
- Furthermore, the number of territories to be planned (not yet existing) are:
exactNumberOfTerritories = 3.
- Finally, the three activity limits (as many as
exactNumberOfTerritories) that you want to be considered by the PTV xTerritory server for the three future territories are:
- Activity limit for future territory I:
maximumValue = 30.0
- Activity limit for future territory II:
maximumValue = 60.0
- Activity limit for future territory III:
maximumValue = 50.0
All three activity limits must not carry any territory assignment, since there are no assignable territories yet.
- Activity limit for future territory I:
After getting to know about the activity limits of the PTV xTerritory Server, you will get a glance at considering of incompatibilities of locations and territories in the next post of our blog series tomorrow.
The output format (time in seconds) can be split in service period and driving period. The service period is the activity value of a location interpreted as time in seconds spent for providing service by an employee at a particular location. A driving Period is the server calculated time from one location to another within a territory. It is estimated by the average distance to a location’s nearest neighbouring locations. The estimated driving time from a territory’s center to the territory itself is the average distance to the territory center’s nearest five locations.
Why is this useful?
- It is very difficult to consider driving periods between locations and service periods at locations in the tour estimation for exactly one territory. For this reason tour estimates on basis of the PTV xTerritory Server are helpful to plan better calculated tours with the PTV xTour Server. So it can be regarded as a prior step for a more fine-grained tour calculation by the PTV xTour server with many more parameters.
- The PTV xTerritory Server is able to interpret activity values as service periods. For example you can use the activity value as a service period for a service employee who provides at certain service at a location or for a truck driver who unloads certain goods at a location.
- The PTV xTerritory server allows constraining tour periods by setting a single
TourPeriodLimitfor each territory. With this, a service tour period can be limited to, for example 8 hours of a typical work day.
How it works
Estimating tour periods for territories is a concept by which activity values of locations are interpreted as service periods, e.g. working hours of a service employee, and driving periods between locations are summed up. This sum then represents an estimated round trip time for a tour through all locations of a territory. This concept provides the basic mechanism for planning, distributing and changing territories according to a tour estimate. It can be regarded as a prior step for a more fine-grained tour calculation by the PTV xTour server with many more parameters. In general, for an estimate of a round trip tour period within a territory, service times and driving times are the only time contributions that are considered. The driving period from a territory center to the territory itself is not considered by the PTV xTerritory’s tour estimation. Nonetheless, this particular driving time is provided within the territory summary as additional value.
Tour estimation and activity limits
Setting limits with the PTV xTerritory server is possible for each territory and the three use cases: territory planning, location assignment and change territories. Limiting the duration of a tour period for a territory can have a major impact on the calculation results in all use cases. However, when limits are applied, it can become impossible to find a valid calculation result. If this occurs, more reasonable values for the limits themselves or other planning parameters within the
planningProfile need to be considered. For further information of activity limits read the next post of our PTV xTerritory 1.20.1 Blog Series.
Additionally to this post you can read its use case documenation here.