New toll tarrifs for Germany (dec2023 / july2024)

[clvo]

Hi Bernd,
thanks for all the information!
One question from my side - as I understand, in the future, there has to be used a different weight for calculating the toll (sorry, I only found it in german):

Mit der Einführung der CO2-Emissionsklassen ändert sich die Grundlage für die Zuordnung zu einer Gewichtsklasse.
Bisher: Es wird das maximal zulässige Gesamtgewicht herangezogen.
Siehe Zulassungsbescheinigung Teil I Ziffer F2.
Neu ab 1.12.2023: Die technisch zulässige Gesamtmasse der Zugmaschine und gegebenenfalls des Anhängers.
Siehe Zulassungsbescheinigung Teil I Ziffer F1.

Is there a new propery for this kind of weight or how can I make the correct calculation in PTV?
Thanks in advance!
BR Claus

[Bernd Welter]

Here's what I receved from PM (Stephan, translated by me):

Currently we consider just one value for the weight and that is the technical legal total weight. There's a backlog item but it's not been prioritized so far. Therefore you'd either experience an inaccurate routing or an inaccurate toll calculation - depending on which weight you assign to the current parameter.

So stay tuned - it stays suspenseful!

[Bernd Welter]

One more statement about this whole topic:

From the statements above you can see that we prepared the forecasts only for the HERE provider map:

• We didn't prepare these forecasts for TOMTOM and we won't do this.
• Once the tarrifs are finalized by the German Bundestag we will produce the regular toll updates for both providers, TOMTOM and HERE.
• Update 25.10.2023: afaik the government has approved this and now after a grace period of 2 weeks the data team will create new data files for TT and HERE.

Bernd

[clvo]

Hello Bernd,
if I understand it correct, the change of the parameter "co2EmissionClassEU" should result in different amount of toll - correct?
But if I change it in the following request from i.e. "1" to "3" the toll-amount does not change. But if I change the emissionStandardEU the value changes. Additonally the TollOnlyTimeConsideration has no effect either. (changed i.e. from 2022 to 2024)
Am I missunderstanding something?
Thanks in advance!
BR Claus

Code: Select all

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://xroute.xserver.ptvgroup.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <xs:calculateRoute>
      <request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns3="http://xroute.xserver.ptvgroup.com" xsi:type="ns3:RouteRequest" scope="globalscope" storedProfile="truck11_99t" coordinateFormat="EPSG:4326">
        <requestProfile>
          <vehicleProfile electronicTollCollectionSubscriptions="NONE">
            <engine engineType="COMBUSTION" fuelType="GASOLINE" fuelConsumption="10.0" emissionStandardEU="EURO_6" co2EmissionClassEU="1"/>
            <weight totalPermittedWeight="20000" />
            <axle numberOfAxles="5" />
          </vehicleProfile>
          <routingProfile>
            <course>
              <toll tollPenalty="0"/>
            </course>
          </routingProfile>
        </requestProfile>
        <waypoints xsi:type="ns3:OffRoadWaypoint">
          <location sideOfStreetRestriction="ANY_SIDE">
            <offRoadCoordinate x="8.88653" y="53.034517"/>
          </location>
        </waypoints>
        <waypoints xsi:type="ns3:OffRoadWaypoint">
          <location sideOfStreetRestriction="ANY_SIDE">
            <offRoadCoordinate x="13.690029" y="51.074713"/>
          </location>
        </waypoints>
        <routeOptions>
			<timeConsideration xmlns:ns4="http://timeconsideration.xserver.ptvgroup.com" xsi:type="ns4:TollOnlyTimeConsideration" referenceTime="2024-06-29T09:15:21.000"/>
          <geographicRestrictions/>
          <polylineOptions elevations="false"/>
          <emissionOptions/>
          <tollOptions useDetailedToll="true" returnZeroCosts="false"/>
          <tourRestrictions/>
        </routeOptions>
        <resultFields waypoints="false" nodes="false" polyline="false" emissions="false" report="false" tourReport="false" encodedPath="false" guidedNavigationRoute="false" monetaryCostsReport="false" alternativeRoutes="false" providerIds="false">
          <legs enabled="false" polyline="false" tollSummary="false" emissions="false" providerIds="false"/>
          <segments enabled="false" emissions="false" polyline="false" descriptors="false" roadAttributes="false" id="false" providerId="false"/>
          <eventTypes>TOLL_EVENT</eventTypes>
          <toll enabled="true" sections="false" systems="false"/>
        </resultFields>
      </request>
    </xs:calculateRoute>
  </soap:Body>
</soap:Envelope>

[Bernd Welter]

Here's a sample computed on XServer2 Internet PROD:

in groups of 5 "CO2Emission classes" I iterated over the different EU Emission classes (NONE, EURO_0, EURO_1, ...)

WIthin a given com.ptvgroup.xserver.vehicleprofile.EmissionStandardEU the toll is equal.

Looks "strange"...

Which environment did you use?

[Bernd Welter]

here's how it should look like... (retrieved on my local map)

We are investigating the issue's cause

[Bernd Welter]

Meanwhile we performed a rollback to the 2023.2H map on the european cluster (XServer2-EU) and the scenario's are ok now:

calculated on https://xserver2-eu.cloud.ptvgroup.com/

[AlexanderL]

I calculated some routes in december with xServer Internet and the toll results look good so far.
But.. Is there any update planned before december?
The "co2EmissionClassEU" field is currently experimental.
I would like to avoid connecting the experimental API to a production system.
Thanks.
Alex

[Bernd Welter]

Hello Alexander,

here's some feedback from Stephan = Product Manager:

We do not plan to change the API but at this stage we can't guarantee as we depend on TollCollect.
The law has been signed this week by the German authorities.
If they decide to change anything at the beginning of November we will have to update the data again.
But with a 95% probability the API is stable...

Bernd

[Bernd Welter]

Here's a quick status update:

• Our data department is preparing the new toll scenarios for German Detailed toll. If everything works according to the plan then the new scenario files for the 2024.1H map will be available on Nov. 27.
• But please consider the process: the underlying data has to find it's way into the Layer Delivery Server (LDS) and from there via CUS (Content Update Service) into the xServer / PTV Developer.
• Right now (14.11.2023 / 15:28) the xServer internet 2 hosts:
  • https://xserver2-europe-eu-test.cloud.ptvgroup.com : 2024.1H on Test
  • https://xserver2-europe-eu.cloud.ptvgroup.com : 2023.2H on Production

So this means: we try to be as quick as possible... but we can't guarantee the road map.

And :

• The CO2Emission Class property is still "experimental in v2.30"
• We also work on "stabilizing the parameter": best case it will be "released in v2.31 (available not before end of Nov 2023) - if not: you would need to wait at least till 2024.

[Bernd Welter]

Just an info: as this topic triggers many of us I'd like to offer a webinar series in the next weeks to

• share latest status
• answer open questions

Dates: German version : 4pm , English version : 5pm

• 16.11.2023
• 23.11.2023

Bernd

[Bernd Welter]

Here's the output of yesterday's webinar:

• 20231116-TollStatus.pptx

  (9.26 MiB) Downloaded 4766 times

• German Youtube video
• EnglishYoutube video

QUestion	Answer
Which combination of xServer1 and 2 with which map versions will support the new toll calculation?	We will provide updated toll data for Germany for the following maps and combinations xServer1 : only basic toll xServer2 : basic toll plus detailed toll We will prepare data packages for the German National toll for the 2024.1H, 2023.2H and 2023.2T. Though we decided (in summer) to restrict the “forecast version” to HERE 2023.2H the new versions will cover the TOMTOM map as well. If you are on 2023.2H you are not forced to migrate – but we recommend the update from a generic perspective.
When will the 2024.1H be available for download?	It is already available for download on request. Please be aware to use the CUS for the underlying toll updates!
Will xServer 1 also support the calculation of the new toll tariffs?	xServer 1 is restricted to BASIC toll and therefore less flexible by design. Please consider to switch to PTV Developer or PTV xServer2 to get access to detailed toll. Furthermore the xServer1 API won’t grant access to the new CO2EMissionClass property of a vehicle’s engine. Instead all routings of xRoute1 will apply the most expensive CO2EmissionClass 1. You won’t be able to compute basic toll for CO2EmissionClass 2,3,4,5 with xServer1.
When will the content update server get access to the new data files?	The data files themselves are supposed to be ready on 27.11.2023. Data will forward them to “LDS” (Layer Delivery Server) team as quick as possible. Best case: 27.11.2023.
Is there a difference between the toll data in the Forecast and the ones in the finalized version?	Yes. Forecast had a plausibility of less than 100% which means that the prices were neither confirmed nor did we ever give a 100% accuracy for any forecast.The prices for CO2 Emissionclass 2-4 were adjusted during the production of the update.
We use xServer2. Shall we use BASIC toll?	For xServer2 users we recommend to use DetailedToll which is enabled by default. Basic toll is only accessible through the experimental API.

[Bernd Welter]

Looks like more and more partners are approaching support or order management with

we need new toll data files for our OnPremise installation - please provide a download of the zip's!

Let me drag your attention to this separation of xserver2 scenarios:

• Many users are using the Content Update Service to update their onPremise environment. Once this tool is installed it automatically checks the Layer Delivery Server for download files and patches the local map.
• Some users can't use the "100% automatic" version with the CUS because they need to decide manually when to patch the environment. Many of those users approach PTV with the request described above.

What many users do not know:

• There's also a manual CUS based approach where the patch procedure is triggered on demand. I have described this approach in this article Content Update Service: update on demand (xServer2).

This might be relevant these days because the new German National tariffs seem to trigger too many of the manual order management approaches.

Bernd

[Bernd Welter]

Sidenote: xServer 2.31 is released:

CO2EmissionClassEU is released!

• Improvement: The field 'co2EmissionClassEU' in the type 'Engine' of the vehicle profile is no longer experimental.

[danper]

Hi Bernd,
A quick question for you: how to deal with xRoute 1 and new german toll; co2EmissionClassEU is not present. So, is it based on date + "parameter": "EMISSION_CLASS"? I tried without success.
Kind Regards

[Bernd Welter]

Hi Daniele,

all xRoute1 routings with a toll date after 1.12.2023 will apply CO2EMissionClassEU=1... (check the posts above).

Let's be very specific:

• If you mean "EMISSION_CLASS" such as EURO_1, EURO_2, ... EURO_5, EURO_6... the prices will change between the classes. But the will ALL be based on CO2EmissionClassEu=1.

  

  Also some example based on xRoute1 (prod HERE) ... Same waypoints and profile, I just iterated over the EMISSION_CLASS = EURO_0, EURO_1....

• In xServer2 the EMISSION_CLASS is com.ptvgroup.xserver.vehicleprofile.EmissionStandardEU
• And the CO2EmissionCLassEu exists as a new property of VehicleProfile.Engine:

  

  New property in xServer2 "VehicleProfile.Engine"

[Bernd Welter]

Here's some announcement which affects the "availability of the new German National Toll (1.12.2023) through a released API (v2.31)" as discussed in this thread. Unfortunately the initial 16.12.2023 has to be replaced by 16.1.2024.
Sorry for that ...

Bernd

Dear Customer, Dear Partner,
We would like to inform you that we rescheduled the maintenance on the PTV World City Map [Here] production clusters with API Version 2.
The production clusters will be updated according to the new schedule.

• January 16th, 2024: Update on xserver2-eu production cluster
  • Update to PTV World City Map 2024.1H
  • Update to PTV xServer version 2.31
• January 17th, 2024: Update on xserver2-us production cluster
  • Update to PTV World City Map 2024.1H
  • Update to PTV xServer version 2.31
• January 18th, 2024: Update on xserver2-au production cluster
  • Update to PTV xServer version 2.31

The test system xserver2-eu-test is updated already, please test your application during the test phase and report any faults immediately to our support.xServer support.de@xserver.ptvgroup.com.
Yours sincerely,
Your Operation Support

[Bernd Welter]

Quick status from our system administrators:

Dear Customer, Dear Partner,
We would like to inform you regarding status of the maintenance on the PTV World City Map [Here] production clusters with API Version 2.
The production clusters will be updated according to the new schedule:

• January 16th, 2024: Update on xserver2-eu production cluster - completed.
  • Update to PTV World City Map 2024.1H
  • Update to PTV xServer version 2.31
• January 17th, 2024: Update on xserver2-us production cluster - completed.
  • Update to PTV World City Map 2024.1H
  • Update to PTV xServer version 2.31
• January 22nd, 2024: Update on xserver2-au production cluster – rescheduled.
  • Update to PTV xServer version 2.31
• January 23rd, 2024: Update on xserver2-us2 production cluster
  • Update to PTV World City Map 2024.1H
  • Update to PTV xServer version 2.31
• February 6th, 2024: Update on xserver2-dps production cluster
  • Update to PTV xServer version 2.31
  • Update to PTV World City Map 2024.1T

The test system xserver2-eu-test is updated already, please test your application during the test phase and report any faults immediately to our support.xServer support.de@xserver.ptvgroup.com.
Yours sincerely,
Your Operation Support